Search results

Опишите пошагово процесс воспроизведения, пожалуйста.

This should be fixed at WebRTC library side, so there is no fix in SDK. Please use Info.plist tweak as mentioned above.

Good day. This is a known Chrome bug, but fix is not released yet. So we fixed the issue at WCS side, please update to the latest build 5.2.1181. The recordings which are already been saved with previous build may be fixed by ffmpeg ffmpeg -i stream_bad.mp4 stream_fixed.mp4

Hello Please check this doc https://docs.flashphoner.com/display/WCS52EN/Starting+and+stopping#Startingandstopping-Folderpermissionssettingwhenstartingfromflashphoneruser Server is starting as flashphoner:flashphoner by default. So you can correct rights using script: sudo ./webcallserver...

Good day. You should use Basic authorization, for example: curl -u user:password -H "Content-Type: application/json" -X POST http://localhost:8081/rest-api/stream/find -d '{"published":true,"display":["metrics"]}' You should use the same user credentials as in web dashboard (admin and demo...

Чтобы получить доступ к srcObject, нужно получить доступ к video тэгу. Этот тэг создается (если Вы не используете собственный тэг) при вызове Stream.publish для публикации или Stream.play для воспроизведения. Пример доступа к этому тэгу есть в исходных текстах Two Way Streaming. Получить...

Добрый день. Как правило, возможностей объекта Stream достаточно для управления потоком. Если Вам необходимо использовать собственный видео тэг, посмотрите здесь: Использование собственного HTML5 video элемента для публикации Использование собственного HTML5 video элемента при воспроизведении

We found in dump a bad timestamp sent by device: the sequence number of packet is correct, but timestamp is less than previous one This device behaviour does not seem to be normal. However, on our test server with latest release build 5.2.1174 such streams playing from the dump are not freeze...

We investigated the issue. Seems like no changes needed on server side or in iOS SDK. There is a method in CXProvideDelegate protocol func provider(_ provider: CXProvider, didActivate audioSession: AVAudioSession) We implemented it to answer the SIP call, see ProviderDelegate.swift module...

Thanks for clarification. It seems possible to implement without SIP, but this requires changes a WCS server side. We'll let you know in this topic when release the feature.

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