Search results

Please do tree /usr/local/FlashphonerWebCallServer/lib/so And paste or attach output here.

Try sudo chmod -R 775 /usr/local/FlashphonerWebCallServer/lib Or sudo chown -R flashphoner:flashphoner /usr/local/FlashphonerWebCallServer/lib

Please also check the log file /usr/local/FlashphonerWebCallServer/logs/startup.log when start fails. It should display what file permissions are wrong.

Hello Try to set permissions immediately before launch sudo ./webcallserver set-permissions sudo ./webcallserver start

Hello. Please use the command to get more details about service failure: journalctl -xe Try to fix a file write permissions cd /usr/local/FlashphonerWebCallServer/bin sudo ./webcallserver set-permissions Also try to detect IP addresses manually cd /usr/local/FlashphonerWebCallServer/bin...

Hello We have checked logs. It looks like WebRTC connection issue. Please make the report 1. Try to play stream. 2. Then gather the report: cd /usr/local/FlashphonerWebCallServer/tools sudo ./report.sh --sysinfo --conf --tar

Good day. Since build 5.2.2022, WCS supports hardware acceleration using NVIDIA GPU while decoding and encoding video. See details here: Hardware acceleration support for video transcoding

Good day. Since build 5.2.2022, WCS supports hardware acceleration using NVIDIA GPU while decoding and encoding video. See details here: Hardware acceleration support for video transcoding

Добрый день. Начиная со сборки 5.2.2022, WCS поддерживает аппаратное ускорение при декодировании и кодировании видео с использование NVIDIA GPU. Подробности здесь: Поддержка аппаратного ускорения при транскодинге видео

Good day. The function is not quite ready to production use yet, so we have not documented it. We will let you know when it will be ready.

Yes. But we recommend to use the latest SDK with the latest server.

Good day. We changed logging to reduce an excessive output. Also in the latest builds there are some fixes to prevent RTCP feedback issues/ Please update to the latest build 5.2.2036.

Good day. You're using too old WCS build. Some new events are added on a client side, so the old WCS build cannot handle them. Please update to the latest WCS build 5.2.2036.

Good day. In the latest Web SDK builds, Flashphoner.init() is async function. So you should use await or Promise returned: Flashphoner.init({}).then(() => { ... });

You should use STREAM_STATUS.STOPPED event after stream.stop() call to disconnect the session, for example session.createStream({ name: streamName, display: remoteVideo }).on(STREAM_STATUS.PENDING, function (stream) { ... }).on(STREAM_STATUS.PLAYING, function...

Good day. Use the session.disconnect() method to close the websocket session, for example function connect() { var url = $('#urlServer').val(); //create session console.log("Create new session with url " + url); Flashphoner.createSession({urlServer...

Hello You would need something like Flutter HLS Player Like this https://pub.dev/packages/video_player_web_hls WCS has a good HLS and Low Latency HLS support therefore you can embed HLS players for video playback https://docs.flashphoner.com/display/WCS52EN/In+a+browser+via+HLS

Good day. When you're connecting through Load Balancer DNS, the client uses its endpoint to establish a websocket session. Not a server endpoint directly. Then, you're detaching the server from the Load Balancer. When detaching is finished, Load Balancer closes the websocket connection because...

Добрый день. Совершенно верно, нужно изменить политику для хука /publishStream в rest_client_config.json: ... "publishStream" : { "clientExclude" : "", "restExclude" : "", "restOnError" : "FAIL", "restPolicy" : "NOTIFY", "restOverwrite" : "" }, ... По умолчанию...

Good day. You should have an external IP on every WCS instance and should have media ports available to establish WebRTC connection. So if your instances have only a private address and have no external one you get an ICE error. Yes, this is appropriate. Anyway, you should use your license key...