Search results

Seems like this is a hardware issue. Please check Bitrate value in publishers statistics at left: If this is 0, it means the browser does not send media traffic at all. So disabling hardware acceleration in Firefox should help. Clean Use hardware acceleration checkbox and restart browser Or...

Hello We have updated demo server to Web SDK v.2.0.223 and WCS 5.2.1431 https://demo.flashphoner.com Issue seems not reproduced with Firefox 105.0.2 Ubuntu 22. Could you check from your end on our demo server? If it works on our demo server but does not work on your, please send...

You can try network interfaces bonding https://www.tecmint.com/configure-network-bonding-teaming-in-ubuntu/. In this case, WCS will see two interfaces as one. But the channels may be bottleneck.

Yes. It may work with 2 interfaces, for example, to capture RTSP streams from external network for viewers in internal one, so RTSP stream goes through one NIC and WebRTC stream go through another NIC. But it can't be configured to balance a network load between two interfaces.

No, settings for multiple adresses to bind to are not supported. But server is listening for websocket on all interfaces by default: wss.address=0.0.0.0 You should use CDN of two Edge servers in this case wicth 1 Gbps intefrace per each. Please read this doc: CDN 2.0 and this article...

Добрый день. Пожалуйста, обновите WCS до последней сборки 5.2.1431 и SFU SDK до 2.0.126. Проверьте, воспроизводится ли проблема. Если да, то соберите отчет: Сбор отладочных логов при помощи скрипта report.sh и пришлите, используя эту форму. Также уточните: 1. Какое количество одновременно...

Regarding multiple domains. Option 1 Web import does not support multiple SSL certs. You can try to import two or more SSL certificates using the command line. For example: 1. Import SSL certificate + private key for domain1.com 2. 1. Import SSL certificate + private key for domain2.com 3. As...

Hello Regarding Multiple NICs. The NIC is used when WCS binds a port for sending or receiving packets via particular protocol. For example, WebRTC can bind port 31001, 31002, etc. Websocket can bind port 8443. There are settings where you can specify what IP (NIC) address will be used for...

We fixed the issue in build 5.2.1430. Please update and check.

Good day. You should set up Prometheus integration: WCS integration to Prometheus. Then, collect streams_viewers metric and build a graph in Grafana as needed: 10 Important WebRTC Streaming Metrics and Configuring Prometheus + Grafana Monitoring

Good day. Seems like mistype (the third slash) in mixer uri. Try to use double slash "uri": "mixer://m_abc2".

Please find the stream using /rtsp/find_all query, then stop it using /rtsp/terminate.

Good day. We fixed the issue with switchCamera in iOS SDK build 2.6.103. Also, we modified GpuImageDemo Swift example code to test a camera switching.

Good day. Please update WCS to the latest build 5.2.1421. Check if the problem is reproducing. If yes, try to stop the stream using REST API POST /rest-api/rtsp/terminate HTTP/1.1 Host: localhost:8081 Content-Type: application/json { "uri":"rtsp://your_camera_url" } and then start again...

The stoppedRecording event is raised when recording is stopped by REST API or by media stream stopping, but before the resulting file is written because file write operation is asyncronous and relatively slow.

Good day. Since build 5.2.1416 it is possible to receive an events about a certain stream recording starting or stopping: REST hook for stream recording

Good day. Please check the screen share stream metrics using /stream/find REST API query: Stream parameters monitoring with REST API, or just play in in Medai Devices example to check a WebRTC statistics. If lost video frames and NACK counters are grow, it means the channel is not good enough to...

Good day. Seems you've missed a second participants video. Please use Custom layout displaying tool to check your layouts displaying.

Good day. You should use additional mixer to replace an audio: 1. Add video from existing stream to a new mixer: POST /rest-api/mixer/add HTTP/1.1 Host: localhost:8081 Content-Type: application/json { "uri": "mixer://m1", "remoteStreamName": "stream1", "hasVideo": "true", "hasAudio"...

Seems like React Native WebRTC implementation does not support TCP transport. To investigate a DTLS error, please collect a report on your server instance as described here including the traffic dump using report.sh script: Getting logs with report.sh script. Traffic dump must be started to...