Search results

Good day. Please read this doc: Publisher and player channel quality control

Good day. First, please make sure the stream is published on WCS using /stream/find REST API query: /stream/find Then, please make sure you've set server parameters as described here: Periscope and Twitch If all seems to be correct. please collect a report as described here and send using this form.

Воспроизводится ли та же проблема в примере streaming-min-debug.apk на данном аппарате?

Также уточните: 1. Версию MIUI и версию Android на данном аппарате 2. Воспроизводится ли проблема с 2sessions-debug.apk из архива сборки 1.1.0.57 с подключением к demo.flashphoner.com (сборка WCS 5.2.1170)?

По данному сценарию проблема не воспроизводится на Xiaomi Redmi 9 (MIUI 12.5.4, Android 11). Уточните, пожалуйста. все модели телефонов, на которых это воспроизводится.

Good day. If you need to use any privileged ports (0-1000) in latest WCS builds, please set WCS to start as root by changing the following parameter in /usr/local/FlashphonerWebCallServer/bin/setenv.sh from WCS_NON_ROOT=true to WCS_NON_ROOT=false and restart WCS.

We recommend to update to the latest build 5.2.1181 if you're using VOD, because there was S3 VOD playback regression fixed after 5.2.1165.

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

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.