Search results

Yes, IPv6 does not work with WebRTC TCP transport now. That's the issue. We already testing the fix.

We fixed the issue in WCS build 5.2.2197. Please update and check.

Добрый день. Выглядит так, что не проходит DTLS соединение Проверьте, что сервер также обновлен до последней сборки 5.2.2197. Также проверьте, воспроизводится ли проблема с примерами Android SDK из архива сборки 1.1.0.68. К сожалению, нет, поддержка ARM32 процессоров убрана Google из WebRTC...

You don't need external internet while using the software under Standalone License. However you would need internet connection at least one time during activation. Once license is activated, conf/flashphoner.license will be recorded. Then you will be able to disable external internet connection...

If you're using WebSDK in your custom extension, you should use flashphoner-webrtc-only.js bundle from WebSDK archive. The full bundle flashphoner.js includes obsoleted modules which contain some Javascript code Chrome claims as obfuscated.

The fix is on testing stage. Should be released this week.

Good day. Please update to the latest WCS build 5.2.2192. If any incident occurs, collect the report as described here and send it using this form.

We previously used a Chrome extension for screen sharing, but it seems that this is no longer necessary. Screen sharing can now be implemented without any extension.Could you please clarify which extension you are referring to? We would appreciate a bit more information to assist you better.

We raised the ticket WCS-4359 to investigate the issue, but it may take a time.

You always need an internet access to license server https://my.flashphoner.com/ unless you're using Standalone license. Please read the details here.

In this case you should deactivate the license on the old instance cd /usr/local/FlashphonerWebCallServer/bin sudo ./deactivation.sh then activate the new instance cd /usr/local/FlashphonerWebCallServer/bin sudo ./activation.sh your_license_code

Good day. We raised the ticket WCS-4358 to update the base Ubuntu image to 22.04 and JDK to 21 in WCS docker image. We'll let you know about progress.

Good day Please use a standard command to display server log to the stdout: tail -F /usr/local/FlashphonerWebCallServer/logs/server_logs/flashphoner.log

Good day. Yes, WCS is tested to run on CentOS Stream 9.

We assume you ask about Inject-VOD feature https://docs.flashphoner.com/static/WCS52/Streaming_video_functions/Captured_stream_management/Injecting_one_stream_into_another/?h=inject#injecting_a_vod_stream_from_file If you are doing this way, video VOD (mp4) will be injected from the first key...

Добрый день. Чтобы организовать трансляцию с низкой задержкой, необходимо использовать WebRTC. Это основной кейс применения WebCallServer. Один из примеров развертывания CDN для таких трансляций описан в статье, сам кейс описан здесь. Мы не предоставляем готовую облачную инфраструктуру для...

Попытались воспроизвести проблему в MacOS Safari 17.5 (Mac mini M1, MacOS 13.6.4), используя пример Media Devices, сборка WebSDK 2.0.254: 1. Подключили две веб-камеры по USB 2. Открыли страницу примера в Safari, в консоли отобразились две камеры 3. Опубликовали поток с камерой, выбранной по...

Добрый день. Уточните, пожалуйста, следующее: 1. Используемая версия WebSDK (судя по хэшу, не последняя) 2. Используемая версия Safari, MacOS/iOS 3. Устройство, на котором воспроизводится проблема (выглядит так, что Safari отдает всего одну камеру)

We tested the build 5.2.2178. flashphoner.properties (both ip and ip_v6 are local addresses): wcs-core.properties When WCS is started, it shows tcp6 only in netstat results: But actually it responds on IPv4 too: Have you tried to open the statistics page (or web admin page) using IPv4?

Hello According to the docs The following settings can be used to set comma separated IPv4 and IPv6 interfaces to bind https.address=0.0.0.0,2a00:1450:4001:829::200e for port 8444 wss.address=0.0.0.0,2a00:1450:4001:829::200e for port 8443