Search results

It seems you have got reports with TCP enabled. ice_tcp_transport = true in flashphoner.properties We don't see any issues with TCP enabled. Could you comment out this setting and prepare report for UDP configuration.

Hello First of all, test Media Devices sample with your server. https://demo.flashphoner.com/client2/examples/demo/streaming/media_devices_manager/media_device_manager.html Make sure publishing and playback resolutions are equal. If resolutions are not equal, try to change Content Hint to...

Hello Please follow the documentation Android SDK 1.1 and examples https://docs.flashphoner.com/display/ANDROIDSDK11EN/Overview

Hello This is REST API docs https://docs.flashphoner.com/display/WCS52EN/REST+API REST API Examples https://docs.flashphoner.com/display/WCS52EN/Examples Recorded video file is a static mp4 or mkv. There is no REST API to check file system. You can connect to server over SSH and download...

We added reports to the ticket.

We tested in Media Devices Swift and Two Way Streaming Swift: - click Connect - Publish - Disconnect before PUBLISHING status: no crash - click Connect - Publish - Stop - Disconnect: no crash too So we need a code to reproduce.

A stream is recorded with a real publishing resolution. Not with resolution set by constraints, because the real resolution may be lower if channel bandwidth is not enough. You can check the publishing resolution and other stream metrics by REST API: Receiving common stream information

Please also note we does not change WebRTC package in this build (only version is bumped) You should update FPWCSApi2 and FPWCSApi2Swift packages to 2.6.120 too because those packages contains actual changes (checking if renderer is created before deleting it).

We can't reproduce this in Media Devices Swift or Two Way Streaming Swift examples. Please modify any of the examples to stable reproduce the issue and send us the code using the form.

You don't need to close the ports if HLS server disabled. WCS will not listen the ports in this case.

Someone tries to DDoS the server by HLS requests. Maybe there is a vulnerability in some media servers they try to exploit. But WCS is proof, so you can ignore those logs or disable HLS at all if you don't use it: hls_server_enabled=false About NPE in logs: we raised the ticket WCS-4014 to...

The server is running. You should activate the license key to work with it: You can request a trial license here: http://flashphoner.com/get_trial/?product=wcs5

Good day. We added a check if renderer exists before deletion in iOS SDK build 2.6.120. Please update and check.

Seems like the startup script cannot detect IP addresses automatically. Use the command sudo /usr/local/FlashphonerWebCallServer/bin/webcallserver set-ip and answer the questions the command asks.

Check file /usr/local/FlashphonerWebCallServer/conf/flashphoner.properties Make sure ip = {Public AWS Instance IP} ip_local = {Private AWS Instance IP} Try to launch in standalone mode cd /usr/local/FlashphonerWebCallServer/bin sudo ./webcallserver start standalone Copy and past log output...

1. Try to set permissions sudo /usr/local/FlashphonerWebCallServer/bin/webcallserver set-permissions 2. If it does not help, try to set launch from root user sudo /usr/local/FlashphonerWebCallServer/bin/webcallserver set-root-mode enable

Use port 8444 for HTTPS queries. Port 8443 is for websocket connections only.

Seems like you have to wait before restarting the service: Wait at least 5 minutes then try to restart it again. If server still does not start, check the file /usr/local/FlashphonerWebCallServer/logs/startup.log for errors.

You should not use localhost here. Use a server URL: https://yourserver:8444/client/records/stream...

Try the following command: sudo systemctl restart webcallserver If the problem persists, check a system journal for details as systemd recommends: sudo journalctl -xeu webcallserver.service