Search results

We prefer not to fork any third party solutions and use them as is (except WebRTC library which often needs to be patched to work correctly).

As mentioned in official docs, CallKit is intended for VoIP calls handling, so SIP logic seems to be required. We raised the ticket WCS-3473 to investigate it. Please also clarify how do you sending a push notification? We implemented it on WCS side by receiving an incoming SIP call. What is...

Unfortunately, we use JSONModel and SocketRocket. Both of them supports only CocoaPods or Carthage. So we cannot migrate iOS SDK to Swift Package Manager until both packets supporters merge a corresponding pull requests.

Still have no news. We'll let you know in this topic.

Please clarify the following: 1. Did you update both SDK and WCS? 2. Is the issue reproducing in Call Kit Demo example built from the source? If not, please change the example source code to reproduce this and send the code using this form

Добрый день. По логам видно, что в одной из клиентских сессий поток 183FlhTIxWnTNy79Hm (видимо, поток ведущего, т.к. он один добавлялся в микшер) периодически публиковался со страницы с остановкой публикации через 2 секунды. Это может выглядеть, как мерцание, если подписчик смотрит поток...

Unfortunately, current version data file was occasionally deleted from web server. We fixed this, please try again.

Good day. We fixed rotation and display matrix issue in MP4 recordings in WCS build 5.2.1165, so Chrome versions without bug fix should play a new recordings correctly. For old recordings, waiting for Chrome fix.

Good day. We fixed rotation and display matrix issue in MP4 recordings in WCS build 5.2.1165, so Chrome versions without bug fix should play a new recordings correctly. For old recordings, waiting for Chrome fix.

Добрый день. Мы сделали пример на две Websocket сессии в одном приложении: Android 2 Sessions В этом примере описанная проблема не воспроизводится в наших тестах на Redmi 9 (MIUI 12.5). Проверьте, воспроизводится ли проблема у Вас в этом примере из сборки 1.1.0.57

Good day. We added iOS Call Kit Demo Swift example using Call Kit and push notifications to receive incoming SIP calls. Note that this example works with iOS SDK build 2.6.80 and WCS build 5.2.1164. Also, it cannot be tested with our demo server because APNs credentials should be set on the...

Seems this is hardware setup issue. In traffic dump we see big packets for all the streams every 30-40 seconds Perhaps it is keyframe. If this cannot be assembled, a stream will freeze. Please check the device settings: can keyframes be sent more often (every 5 seconds for example)? In this...

To capture audio from canvas, use AudioContext. See Canvas Streaming example on GitHub: function createCanvasStream() { var canvasContext = canvas.getContext("2d"); var canvasStream = canvas.captureStream(30); mockVideoElement = document.createElement("video")...

Seems like issue is reproduced on your server after 4 hours of testing. We downloading the traffic dump and will check it.

We successfully started to collect traffic dump and restarted all the streams capturing using private IP. Will check a bitrate periodically to detect the issue.

We tried to start traffic dump collection tcpdump -npi any -B 10240 -w log.pcap tcp port 554 But seems like tcpdump is not installed, and we have no sudo rights to install and launch this. Please add user to sudoers.

Unfortunately, we cannot connect to the server from EU host using credentials you've provided: ssh: connect to host **.***.***.*** port 22: Connection timed out.

We tried to reproduce the issue on our test WCS server (build 5.2.1162), and this is not reproduced during 6,5 hours test. If you provide SSH access to the server, we try to reproduce it in your environment and collect traffic dump to analyze. But it should not be a production server because we...

Please try to exclude router if WCS and the device are under the same NAT. Use private address, not public.

Unfortunately, we cannot play the stream from traffic dump because it's filtered by source address, and there are no requesats from WCS to RTSP camera (OPTIONS etc) Now, we trying to reproduce the issue on our test server with 16 RTSP cameras you've used in your test, and the issue still is not...