Recent content by Max

Hello 5.2 version works on Ubuntu 18.04, 20.04, 22.04, 24.04 See also for 5.3: https://docs.flashphoner.com/static/WCS53/Installing_and_testing/Requirements_and_prerequisites/#system CentOS 7.6, 7,8, 8, Stream Ubuntu 18.04, 20.04, 22.04, 24.04 Fedora 31, 32, 33 and newer Debian 9, 10 and...

Добрый день. Вы используете очень старую версию сервера. Рекомендуем обновиться до актуальной сборки в ветке 5.2 (5.2.2309) или 5.3 (5.3.222)

Good day. Seems like distribution archive is not fully downloaded. Please try to download it again. Please also make sure you have enough disk space to unpack the archive.

Good day. First, please update WCS to the latest build 5.3.194. Please note that JDK must be updated to 21 in this case. If you prefer to use a ready to lauch AWS image, please deploy a new instance based on the latest Marketplace image. It includes JDK 21, so WCS may be updated to the latest...

Hello Please double check flashphoner.properties #server ip ip =XXXX ip_local =XXXX And make sure that ip_local is 127.0.0.1 or local interface address like 192.168.1.10 Example: ifconfig wlp1s40f3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500...

Seems like audio codecs negotiation does not pass: Please try to set the following WCS option allow_outside_codecs=false if this does not help, please collect a full report and traffic dump on the server side. Send the report using this form.

Good day. Please update WCS to 5.3.165 and test again. The issue may be in DTLS handshake on callee browser side. Please also note that actual 5.3 docs are here: https://docs.flashphoner.com/static/WCS53/

The issue was in DTLS handshake when WCS initiates DTLS connection (incoming SIP call case).

Good day. We fixed the issue in WCS build 5.3.165. Please update and check.

We reproduced the issue with SIP calls and raised the ticket WCS-4631.

We have updated WebSDK to build 2.0.265 on our demo server. Media Devices example now uses exact when choosing a camera. You can test it in your browsers.

Good day. We tested the latest WCS build 5.3.163 with Chrome 140. DTLS negotiation passes without any issues, WebRTC publishing/playback works. So you can use latest Chrome with latest WCS builds.

This modifier should be compatible with all browsers supporting getUserMedia call. Please see media track constrains description. Yes.

Good day. This is Chrome issue since 139. The exact modifier should be set when setting a camera Id via constrains, or Chrome will use a default camera from browser settings: session.createStream({ name: streamName, display: localVideo, constraints: { video...

The minimal JDK version supported by WCS 5.3 is now 17. Usually, we recommend JDK 21 because this is latest LTS version yet (JDK 25 is just released, so it probably brings a new issues).