Search results

Good day. Since WebSDK build 2.0.250 a media devices labels are URI encoded to prevent a possible parsing issues at backend side for non-latin characters. Please update WebSDK and check.

Hello Please check the pricing page WCS is a self-hosted software. The number of connections is limited by network bandwidth and hardware of your VPS or physical server. There is no program limitation. Rough calculation. 1 stream 720 p = 2 Mbit per second 250 streams will utilize 500 Mbit per...

Please try one of the following approaches: 1, 2, 3

Hello The issue is confirmed on our end. According our tests it does not parse this character properly ó We are working on a fix. Will keep you informed.

Hello What is the server port where TLSv1 in use? WCS default secure ports 8444 HTTPS 8443 WSS (Websocket SSL) Nginx secure ports 443 (?) If you are using Nginx as a reverse proxy Browser > [TLSv1] > Nginx 443 > [HTTP not encrypted] > WCS 8080 Then the TLSv1 issue is on Nginx end. To fix...

A possible problem may be in non-latin characters in camera or microphone device name Predeterminado - Micrófono de los auriculares con micrófono (2- Jabra EVOLVE 20 MS). We raised the ticket WCS-4249 to encode such characters before sending them to server for debug purposes. As workaround, try...

This is not the same error: Seems like the camera is captured correctly, but WebRTC connection failed. We can't reproduce this on Windows 11 with Video Chat and Screen Sharing example in MS Edge 129 on our demo server...

Good day. Unfortunately, the logs contain a different events: the flashphoner.log file contains events since 13:03 to 13:07 according to the server clock but sdr.log contains the event happened in 15:21 according to the server clock So we can't match neither time nor RTSP URL nor media session...

Good day. The message SERVER_PORTS is not defined does not mean any error. It means WebSDK uses default Websocket port (8444) to connect to server. But Could not start video source means the browser (MS Edge in your case) cannot capture the web camera chosen. Usually this is due to the camera is...

We fixed both the issues in build 5.2.2096. The streams /channel/101 and /channel/201 should now play correctly. Please update and check.

We reproduced a new issue and raised the ticket WCS-4248 to fix it. This seems to be not the same issue as WCS-4246. Please keep the stream available to check whats wrong.

WCS-4246 Internal ticket has been raised We will inform once we have any progress Please use a workaround with H.264 codec for a while

UPD This does not look like a freeze. Timing is running. So we assume this is an issue with H.265 codec on WCS end. If you leave the stream reachable in 24 hours, we will be able to check what is wrong. As a quick fix you can change codec from H.265 to H.264 on camera end. Please note. Even...

Hello We can watch a freeze while playing with VLC. Codec is MPEG-H Part2/HEVC (H.265) (hevc)

Обратите внимание, что пример Media Devices запрашивает доступ к камере при открытии страницы (и в этот же момент формирует список устройств для переключения между ними). Вероятно, в вашем коде также необходимо запросить разрешения при помощи метода Flashphoner.getMediaDevices() при открытии...

We updated jQuery to latest version 3.7.1 in build 5.2.2095.

Добрый день. Уточните, пожалуйста, следующее: 1. Какая версия Web SDK используется? Воспроизводится ли проблема с последней сборкой 2.0.249? 2. На каких ОС воспроизводится проблема: Android, iOS, версия? 3. Воспроизводится ли проблема в примере Media Devices? Если нет, просим модифицировать код...

5.2.1959 https://docs.flashphoner.com/static/ru/WCS52/WCS_5.2_release_notes/#wcs_52_release_notes https://docs.flashphoner.com/static/WCS52/Streaming_video_functions/Playing_a_video_stream_from_the_server/In_a_browser_via_HLS/#passing_a_custom_parameters_when_requesting_a_playlist

You can pass any additional parameters for your backend like this https://wcs:8445/streamName/streamName.m3u8?aclAuth=1254789&param1=1&param2=2 Another way is to hex encode the parameters string, in this case you should decode it on backend...

Good day. There are no differences between 5.2.2071 and 5.2.2093 concerning HLS segments forming. So it seems like server setup or client code issue. Please try to comment some parameters and use default settings like this: hls_access_control_headers=Access-Control-Allow-Origin...