Search results

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.

В том, что в 1.0 более старая версия WebRTC библиотеки, которая хуже работает с новыми API. А в более новых версиях библиотеки Google повысили требования к Level API, потому и пришлось разделить Android SDK. Мы не разрабатываем и не поддерживаем WebRTC библиотеку сами, а используем готовые...

Уточните, пожалуйста: при каком количестве подписчиков начинаются проблемы? Если на одном потоке было много подписчиков, и у части из них воспроизводилась эта проблема при подключении, а при массовом переподключении не воспроизвелась, похоже, что требуется оптимизация раздачи потока подписчикам...

This message is displayed if WCS did not respond to health check query http://wcs:8081/health-check. Please check if WCS listens to all the ports necessary and web admin dashboard is accessible. Ports can be checked by the following command: sudo netstat -nlp | grep java Also you can check if...

We checked your server. Seems like WCS is successfully updated to 5.2.983 and running: Unfortunately we cannot test streaming because web interface ports 8444 and 8888 seems to be closed by security group, but server listens them

You can add 1935/TCP port forwarding to load balancer too. But, if you want to know on which server the stream is published, you have to set up a separate backend server and use REST hook /publishStream to detect this. Then, you should pass to playing client the server address to connect.

Это будут два разных apk, каждый со своей библиотекой, см здесь, шаг 3. Для того, чтобы опубликовать несколько APK в зависимости от требований Level API, Google Play поддерживает multiple APK.

Please see at this page (hidden by spoiler).