Search results

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 {...

Добрый день. Транслировать экран телефона можно только из нативного приложения под соответствующую платформу. Посмотрите описания примеров для Android SDK Android Screen sharing и iOS SDK iOS Screen Capturer Swift.

Good day. Probably, yes. Please check if hardware acceleration is enabled in browser settings. If yes, and software decoding still used, it means either Chrome on Windows 7 does not support hardware acceleration any more or it is not supported for hardware configuration you're using in tests.

Seems like you've removed WCS.version file occasionally. In this case, you can upgrade the instance by installing a new version over the old one: Updating 5.1 to 5.2 or one 5.2 build to another

Unfortunately, the logs you've provided contains no stream publising and no /mixer/startup or /mixer/add calls. So the logs have no any useful information to detect the issue. Please collect the report exactly as described in this doc: Collect debug logs and traffic dump 1. Enable client debug...

Unfortunately, the logs you've provided contains no stream publising (via RTMP or WebRTC) and no /push/startup call. So the logs have no any useful information to detect the issue. Please collect the report exactly as described in this doc: Collect debug logs and traffic dump 1. Enable client...

Good day. Please make sure the participants stream is shown in mixer output stream playing it as WebRTC directly from server. Please also check if the participant stream is correctly added to the mixer: /mixer/add query should return 200 OK. If above seems to be correct, please collect a report...

Please provide SSH access to the server using this form.