Search results

The reason for both the issues is the same: Chrome aggressive quality measure on publishing start. So the only workraound at the moment seems like to disable HW acceleration (this may not help in some Chromium based browsers, Yandex.Browser ror example) and wait for about 10 seconds after...

Добрый день. В настоящее время WCS поддерживает функцию HLS ABR, но эта функция работает только в CDN Origin + Transcoder + Edge, на отдельно стоящем сервере получить поток в различных качествах нельзя.

Good day. You can configure WCS media ports by the following parameters: media_port_from =51001 media_port_to =51200 and need to set up those ports forwarding for incoming connections on intranet firewall. Please note that 199 media ports may not be enough for all the...

В WCS 5.2 настройки логирования задаются в файле /usr/local/FlashphonerWebCallServer/conf/log4j.properties. Подробнее здесь. Этот файл не переписывается при обновлениях, поэтому при обновлении сервера настройки сохранятся. Изменения в файле применяются немедленно, без перезапуска сервера. О том...

This messages show how REST hooks work on WCS side. SEND REST OBJECT shows a query which will be sent to a backend. RECEIVED REST OBJECT shows a response from the backend. They may not be the same depending on backend implementation. In your case, internal WCS backend is used, that's why request...

This messages are useful for us to investigate a various publishing/playback issues in customets logs. So we will not move them to debug levele because not all the customers are familiar with log4j.properties format. You can use the workaround if you don't need this logs.

Good day. Just add the following line to /usr/local/FlashphonerWebCallServer/conf/log4j.properties file: log4j.logger.RestClient=warn This will reduce RestClient class logging without server restart.

We confirm this to be Chromium bug https://bugs.chromium.org/p/webrtc/issues/detail?id=12942&sort=-modified The workaround is to disable hardware acceleration in Chrome settings. There is also another workaround using experimental MediaTrack option. We will check this.

We reproduced the problem in Chrome 91.0.4472.164 and raised the ticket WCS-3257 to investigate the issue. Please use other browser as workaround.

Good day. You can set the desired publishing resolution and bitrate via constraints: session.createStream({ name: streamName, display: localVideo, cacheLocalResources: true, constraints: { video: { width: 1280, height: 720...

We'll let you know here when add those methods for payload access.

If you've stopped WCS before, yes is not needed. And if yiou've stopped WCS before updating, it should not restart automatically. We raised the ticket WCS-3256 to check this. Please install update as described here: wget...

You should deactivate old license key, then activate new one.

Your Trial license has expired

Set this to 3 for example <script>var _participants = 3</script> Note that you should add div elements to display all the additional participants. Please look at Conference example and its source code on GitHub

Good day. Since WebSDK build 2.0.177 screen sharing stream can be published without extension in all of the latest desktop browsers (Chrome, Firefox, MacOS Safari). Please read example description here. Please also note that Safari does not allow to change stream resolution and FPS for screen...

Good day. In iOS SDK, you have direct access to StreamEvent.payload members, but in Android SDK they are accessible through public methods only. We raised the ticket WCS-3251 to add an access method to incoming stream name. Will let you know here.

Please clarify from what version you've updated, and to what one (for example, from 5.2.780 to 5.2.993). We well check. Please note that current webcallserver script instance exits right after starts a new one. And, if you're running it as a service (normally), a new instance will start as...

The server is working, but you occasionally disabled healt checking endpoint, so it returns 404. Please replace the parameter in config http_enable_paths=rest,action,shared,embed_player,empty to http_enable_paths=rest,action,shared,embed_player,empty,health-check then restart WCS. In this case...

It may be issue on WCS side. Please provide 24/7 access to the RTSP stream using this form, so we could test and debug it on our servers. Yes, it can cause sync shift. But debug is needed, and we cannot do it on your server only. So we need an access to the stream.