Search results

Скачайте последнюю версию с этой страницы (с версии 5.1.3487 было довольно много различных фиксов) и просто установите ее поверх уже установленной. При этом рекомендуется сохранить содержимое каталога WCS_HOME/client2/examples, если Вы использовали и как-то модифицировали примеры веб-приложений...

To locate a problem, we need a description of reliable conditions to reproduce it, and/or client debug logs when problem occurs. Thread dump shows what (probably) happens, but not why.

Добрый день. Некоторое количество сборок назад был исправлен баг с похожими симптомами, при условии использования декодера по умолчанию (на основе FFMPEG). Поэтому прежде всего рекомендуем обновиться до последней версии с этой страницы. Если у Вас включено декодирование входящих потоков по...

Hello, 1. There are some "Failed by ICE keep alive" streams. Connection to WebRTC publisher may be closed if there were no STUN packets in timeout specified by stun_freshness_timeout property (it is 15000 - 15 seconds - by default). Try adding stun_freshness_timeout=1000000000 to...

There is no issue with the directory name. If the config files you sent are from this server when 5.1.3511 was already installed, there should have been 5.1.3511-ebcbd3628aba5ea472cb91e6ae3d17e1a3e7efa7 in the WCS.version file yet there is 5.1.3253. Then that is why the directory was not...

No, we don't recommend to use 5 mixers in your case. Playback of 4 streams on page is simpler to impelement and requires less CPU resources comparing to 5 mixers. Mixer uses stream transcoding, so it can use one CPU core on stream.

Good day. You can playback non-mixed streams to all the presenters. Each presenter plays 4 streams from another presenters, so they can listen to each other, and they can see a screenshare. Mixer stream, in its turn, goes to the viewers.

You have too old version. It is strongly recommended to download latest version from this page and make clean installation (uninstall current version and install newest). In your WCS manager log files (you didn't sent us WCS core logs that should be created at WCS_HOME/logs/server_logs) we see...

Please clarify again: 1. You boot your Ubuntu machine. 2. You start WSC with service webcallserver start 3. WCS starts as described here, you can see 2 processes (WCS core and manager) If you try to open WCS web interface https://host:8888, what happens on this step? 4. You restart WCS with...

Мы тестировали эту возможность на нашем примере Streaming-min. Прозрачность и изменение цвета в нашем примере работали после накладывания патча на исходный текст (прилагается). Возможно, если у Вас в коде есть такая строка surfaceView.setZOrderMediaOverlay(true); она мешает.

The message itself means that server does not pull incoming STUN packets from buffer for some reason. By default, STUN socket buffer size is 100: stun_socket_buffer_size=100 This is small enough to buffer exhausted message appear sometimes, but, if this message spams log, and all incoming...

Hello, Please clarify – the issue is not reproducible anymore? Here is a similar thread. What URL is used to access the dashboard? Does the server hostname resolve to IP?

After our tests, there was only one other stream published and it didn’t fail but was stopped by publisher. Checked again and successfully streamed WebRTC as RTMP to Facebook on your WCS using macOS Firefox for 15 minutes. Please recheck to confirm if the issue is still reproducible.

Checked the server – it is working. Installed haveged apt-get install haveged update-rc.d haveged defaults and activated a license to check streaming - the dashboard is available, and streaming is working. WCS does start up after restart. The license is deactivated now. Please activate your...

Looks like some temporary issue with connections to Facebook. Has successfully published WebRTC as RTMP to Facebook on your WCS using macOS Firefox. Please recheck.

And it would be great if you reproduce it with client debug logs enabled.

Hello. One customer reported a similar issue, but we can't reproduce the problem in its case. If you find a reliable way to reproduce, it will help us to find a resolution. And, what WCS version you use now? Is this problem occured on latest version 5.1.3578?

What shows WCS_HOME/logs/server_logs/flashphoner.log? Please send SSH credentials to access yuor server to support@flashphoner.com, we will check.

Прерывание публикации от ffmpeg воспроизводится на версии 5.0.3500 при включенной записи flash-потока. С последней версией 5.1 (5.1.3580) эта проблема не воспроизводится. Процедура обновления с 5.0 до 5.1 описана здесь. При необходимости можно попробовать с 5.1 без удаления 5.0.

Hello 409 Conflict status means you already have a SIP call with the same callId on the server-side. Try to generate new and unique callID for each new call.