Search results

Добрый день Автоскейлинг должен настраиваться уже поверх инстансов с WCS-сервером стандартными средствами AWS. Т.е. нужно создать Load balancer, Auto Scaling group, Scaling policy для скейлинга по CPU, и т.д...

Try this over ssh: sudo service webcallserver update It should update server to the latest one. It should be fixed in the latest build. Please check after update.

У вас выставлен слишком низкий битрейт для такого разрешения 240kbps. Попробуйте добавить '0', чтобы было: 2400000 или совсем убрать этот параметр. Вы ограничиаете битрейт. Браузер ухудшает качество сжатия. В chrome://webrtc-internals это выглядит так (красная полоса на графикке bweCompound)...

Could you check our default application? https://play.google.com/store/apps/details?id=com.flashphoner.wcsexample.phone_min We have tested this Android app with Bria 4 softphone and G.729 audio codec. Volume is not low on our tests. Could you provide SSH access to server and SIP details for...

Strictly, RTMP uses two handshakes to publish a stream: 1) Connection 2) Publishing stream by name. Example of connection URL rtmp://<ip>/live or rtmp://<ip>/live/_default_app Example of stream name: stream444 Therefore it does not seem to be correct. But your app may just parse stream name...

I'm sorry. I have missed that you are using your own Android application as RTMP streamer. Please checkout our Flash Streaming example: https://wcs5-eu.flashphoner.com/client2/examples/demo/streaming/flash_client/streaming.html As you can see we are able to publish RTMP stream and play this...

Hello Android application uses WebRTC for publishing. Therefore you have to set simple stream name and press 'Publish'. You should not use RTMP urls in the Android app. Example of Android application: https://play.google.com/store/apps/details?id=com.flashphoner.wcsexample.two_way_streaming...

We will check this on our end. I will inform you through this thread once we have any news.

We will check this on our end. I will inform you through this thread once we have any news.

http://host:8081?action=stat or http://host:8081?action=stat&params=connections,streams_webrtc_in to fetch desired parameters

Возможно из-за того, что кадр статический и долго не приходит ключевой фрейм. Нам нужно воспроизвести похожее поведение у себя, чтобы понять как исправить. Подскажите, какие мы шаги можем сделать, чтобы повторить у себя или пришлите доступ к вашей странице на logs@flashphoner.com Проверим с ней.

We had similar issue in previous builds. Try to 1. Update to the latest available build (2449) from https://flashphoner.com/download service webcallserver update 2. Add setting to WCS_HOME/flashphoner.properties: set_sync_time_from_ts=true This should fix the latency.

Hello You have to download latest Web SDK build from this page: https://flashphoner.com/wcs-web-sdk https://flashphoner.com/downloads/builds/flashphoner_client/wcs_api-2.0 Latest build: Today, 12 September 2017...

We have fixed this issue in build 2449. The disconnect should work properly now, at least by keep alive in 50 seconds by default.

Perhaps you have changed some Firefox flags or you have an add-on suppressing WebRTC on Firefox. Example of FF WebRTC flags: Peer flags: User media flags: Make sure your flags are default or try to revert them to defaults.

Нашли ошибку в WSPlayer-провайдере. PLAYING действительно вызывался два раза: один раз из сети, второй самим WSPlayer-ом. Исправили в последней сборке API...

Hello The memory leak is caused by disabled keep alive keep_alive.algorithm =NONE If you disable keep alive, websocket connections will utilize memory and can cause the memory leak. Recommended options: 1. Update to the latest available build https://flashphoner.com/download 2. Enable keep...

Low-latency streaming works out of the box, regardless the recording feature. Yes, you will able to stream between these three platforms with low sub-second latency: Android apps iOS apps WebRTC browsers (Chrome, Firefox, Edge, Safari 11)

Мы протестировали в нашем примере Player. Событие вызывается 1 раз. Проверьте, возможно вы добавляете listener 2 раза. Либо событие Playing приходит к вам 2 раза. Похожий баг был исправлен в августе. https://wcs5-eu.flashphoner.com/client2/examples/demo/streaming/player/player.html...

I have installed second USB camera and it works for me too. Please check your media settings in Firefox and check if camera is blocked. You can also check these links to check your webcam with FF: https://webrtc.github.io/samples/src/content/getusermedia/gum/ https://appr.tc/...