Search results

So, the scenario is as follows? - WebRTC stream is published from Chrome - The stream is pushed to AMS - The RTMP stream from AMS is played Which player is used for the RTMP stream? This scenario has been checked with our demo WCS and AMS servers – no video freezes. - WebRTC stream published...

Hi, you still have license, that expired, you can see exception in flashphoner.log

It's possible only for the rtmp stream.

Добрый день. Двойной PLAYING исправили в последней сборке, просьба обновиться. Так в этой сборке есть фиксы по статистике, в т.ч. и по "мертвым стримам". Причину можно найти в логах sdr.log (по имени стрима или media session id) и conndr.log (по session id)

Are you using custom objects on REST? Can you provide some rtmp urls for example?

Hi, You can open https://wcs5-eu.flashphoner.com/client2/examples/demo/streaming/player/player.html in mobile browser and play stream, published from desktop chrome.

Hello, We’ve checked WebRTC push to AMS with the latest WCS version. Could you please clarify if the “stuck” issue is that video freezes when the pushed stream is played, or something else? Also, please let know what type of stream is pushed, i.e. how it is published.

Can you provide access via SSH to your environment? If yes, send it, please, to logs@flashphoner.com

You can enable keep-alive algorithm only for specified protocols with: keep_alive.enabled=websocket Can you do clear install? 1) Backup conf- and database-directory. 2) Remove /usr/local/FlashphonerWebCallServer-5.0.2387 and symlink /usr/local/FlashphonerWebCallServer 3) Download latest build...

We will check it with MacOS.

There is a restriction for WS Player audio functionality in iOS Safari. Audio will be played only if playback is initiated by an action from the user. With the Embed player demo, audio will not be played when ‘Test now’ is tapped and playback is auto started, but it will appear if stop and then...

Which browser do you use?

Hi, Can you show your server.properties content (keep_alive.*)? Please, update your WCS to latest version, this issue should be fixed in 2384 build.

Hello, Please, update your WCS. This issue should be fixed in latest revision.

Hi, You can try to test our sip-as-rtmp-2 example, which uses new REST API. This example showing how to inject sound in RTMP-leg. Please, follow to https://wcs5-eu.flashphoner.com/client2/examples/demo/sip/sip-as-rtmp-2/sip-as-rtmp-2.html More details can be found in docs...

Это не будет работать. Правильно так: Flashphoner.createSession({urlServer: url, mediaOptions: {"iceServers": [ { 'url': 'turn:192.168.0.1:3478?transport=tcp', 'credential': 'password1', 'username': 'username1' } ], "iceTransportPolicy": "relay"}}) Смотрите пример...

Дублирование события PLAYING квалифицировали как некритичный, но все же баг. Поэтому будем убирать дублирование. Когда будет готов фикс, мы сообщим в этой ветке. Пока же нужно в коде предусмотреть возможность дублирования.

Hello Lately we didn't test RTMP re-publishing feature with AMS. Generally we tested with Wowza. What is your version of AMS and config files? Could you share your configuration. We will try to test with our AMS installation. I will let you know once we have any results. Yes it should work...

Hi It is out of our general licensing model. Please contact sales@flashphoner.com with any further licensing questions

По событию PLAYING, действительно есть такое поведение. Смогу уточнить в понедельник. Возможно это не баг и может приходить несколько PLAYING подряд, если меняется stream объект, который они несут.