Search results

Good day. WCS supports the following recording containers (see Stream recording doc): MP4 for H.264 + AAC codecs WebM for VP8 + Vorbis codecs TS for H.264 + ADTS MKV (since WCS build 5.2.1190) By default, the container is set automatically depending on codec published: MP4 for H264, webm for...

Добрый день. Если возникают какие-то сомнения в поведении именно сервера, необходимо проверять работоспособность с помощью заведомо работающих инструментов публикации, например ffmpeg или OBS. Если проблема воспроизводится и с ними, нужно собрать логи сервера и предоставить нам через кнопку...

Самое простое - это остановить Play поток и проиграть его заново с пониженным разрешением. >регулировать VideoConstraints (minBitrate, maxBitrate и videoFps)? Достаточно задать width и height - это снизит битрейт и нагрузку на канал плеера.

Здравствуйте. У нас в Google Play есть мини-приложения, которые используются в качестве примеров. https://play.google.com/store/apps/developer?id=Flashphoner Первое, что вы можете сделать, это взять приложение, которое подходит для вашего кейса и протестировать это приложение с нашим...

Good day. A stream is publishing with a low average FPS (but extremely changing, peaks are from 2 to 30 FPS). We raised the ticket WCS-3485 about this. This seems like H264 hardware acceleration issue in latest iOS. We will check if hardware acceleration can be disabled in WebRTC library. If...

Please update iOS to the latest build in 14 branch. Also, iOS 15 on iPhone 7 is working with demo. Please also try to publish and play stream in Media Devices example. If Packets lost and NACK statistic parameters grow, then you have a channel issues betweent the device and demo server. In this...

Good day. Seems like IP address resolved by DNS is no the same as CDN signaling port is bound to. Please try to set cdn_nodes_resolve_ip=false and set IP addresses, not DNS names, to cdn_ip and cdn_point_of_entry parameters.

When you publish a stream from browser, the stream frames are encoded by browser before sending them. So hardware encoding seems to be working. You can try to check if hardware accelerated decoding is enabled and enbale it if not: 1. Open chrome://flags/ 2. Type Hardware-accelerated video...

Воспроизведите проблему в streaming-min-debug.apk, соберите лог при помощи adb logcat или Android Studio и пришлите лог, используя эту форму.

We checked the report. Seems like you've changed HTTP port in flashphoner.properties file Please remove the line http.port =18081 then server should work correctly We do not see this in report provided. Please uninstall WCS completely sudo /usr/local/FlashphonerWebCallServer/bin/uninstall.sh...

If you cannot provide SSH access to the server, please collect a report as described here. Use report.sh script to collect the report cd /usr/local/FlashphonerWebCallServer/tools sudo ./report.sh --sysinfo --conf --stats --tar Then, send the report archive using this private form.

The channel quality checking method mentioned above is based on difference between bitrates on clent side and server side, both for publisher and player. If bitrate sent is bigger than received one, that means the channel is bad. This is the only method to check a channel quality.

If the recommendations above did not help, please provide SSH access to the instance using this private form.

Hello We recently checked with iPhone7 iOS 14.8.1 Safari, Windows 10 Chrome Version 101.0.4951.54 (Official Build) (64-bit). Works fine. Test 1. Open Two Way Video Chat on iPhone Safari https://demo.flashphoner.com/client2/examples/demo/streaming/video-chat/video-chat.html 2. Join. 3. Open...

Hello 1. It seems you have permission issues Try before starting: cd /usr/local/FlashphonerWebCallServer/bin sudo ./webcallserver set-permissions 2. Make sure port 8081 is listening and not bound by another software netstat -nlp | grep 8081 3. Make sure port 8081 is available from...

Good day. We reproduced the issue and raised the ticket WCS-3481. You have two options to workaround: 1. This session does not affect the server functions, so you can use the latest build 2. Or, if this concerns you, please downgrade to 5.2.1141.

Good day. Please collect a report as described here and send using this form. If you cannot collect a report, please provide SSH access to the server using this form.

Добрый день. Выглядит так, что проблема в канале между публикующим клиентом и Origin сервером. По логам, для потоков, публикуемых в указанное время, видны большие интервалы между ключевыми кадрами (до нескольких минут), также есть исключения при получении TCP пакетов. Скорее всего, не хватает...

Please check /usr/local/FlashphonerWebCallServer/logs/startup.log file. If there is permission error, fix permissions sudo /usr/local/FlashphonerWebCallServer/bin/webcallserver set-permissions then restart WCS sudo systemctl restart webcallserver If nothing helps, provide SSH access to the...

We checked the report. The problem is not reproducing with your /push/startup request parameters in the latest WCS build 5.2.1190: POST /rest-api/push/startup HTTP/1.1 Host: localhost:9091 Content-Type: application/json Content-Length: 154 {...