Search results

Если у вас обрывается, покажите пожалуйста скриншоты, как тестируете или пришлите логи сервера на logs@flashphoner.com

Публикую стрим https://wcs5-eu.flashphoner.com/demo2/two-way-streaming Играю стрим https://wcs5-eu.flashphoner.com/demo2/player Все на месте. Воспроизведение не отваливается. Chrome 60.

WCS is bundled with certbot /usr/local/FlashphonerWebCallServer/tools/certbot-auto So you can try: cd /usr/local/FlashphonerWebCallServer/tools ./certbot-auto certonly If it does not help, you can download and install official certbot from letsencrypt https://certbot.eff.org/

WCS does not bind port 80 Try to open this port on your Amazon instance in security settings. Perhaps letsencrypt uses this port to install ssl certs.

Hello You can see in flashphoner.log that the trial license has expired. So you have to activate a valid license to proceed. Another issue, you have red5pro running with 2g heap size, simultaneously with WCS. It is definitely bad idea for server with 2gb RAM. I would recommend either migrate...

1. You can temporary shutdown your service listening 80 port and allow letsencrypt certbot do its work. Then startup your service again. 2. As an option, you can run certbot manually and select options: # certbot certonly Saving debug log to /var/log/letsencrypt/letsencrypt.log How would you...

Please send SSH sudo access details, and dashboard password to logs@flashphoner.com We will check.

Make sure WCS server is up and running. Restart server if it is not running: https://forum.flashphoner.com/threads/troubleshooting.10768 What is your server spec? - RAM - CPU

Hello, Flashphoner 2.1 aka Flashphoner RTMFP SIP Gateway does not use Wowza server and is not bundled with Wowza. So you can ignore this message.

You can use /push/startup REST API method to re-publish one stream to two or many targets. Test 1. Publish a regular WebRTC stream without rtmpUrl paramerter. For example using Two Way Streaming page: https://wcs5-eu.flashphoner.com/demo2/two-way-streaming 2. Push the published stream to YouTube...

WebRTC ports are UDP ports in range [31001-32000] by default. You can configure media_port_from and media_port_to in flashphoner.properties config. Websocket default port is TCP 8443. It can be configured in server.properties config. Therefore you have to open following ports: UDP...

Perhaps you have to relaunch Chrome 60 browser after updating. Make sure your camera is not acquired by another application. I.e. if you test Chrome, make sure your cam is not used in Firefox or Skype, etc. Media Devices works well in my Chrome 60 on Windows.

да да И желательно это делать на остановленном сервере. Процесс активации / деактивации описан здесь: https://flashphoner.com/docs/wcs5/wcs_docs/html/ru/wcs-admin-guide/index.html?setup_and_testing-getting_license_and_activation.htm

We have tested Moto G, Android 5.1, Сhrome 55.0.2883.84 (downloaded as apk) - playing, not reproduced. Embed Player: WebRTC - playing. Win 8.1: playing. Trying to test on Samsung Galaxy J3 or another device in J-series with Chrome 55.

Your rtmpUrl is incorrect. The URL is not valid: rtmp://62.90.177.144/flashphoner conn=S:919580 conn=S:8 conn=S:2758034 conn=S:0 live=1 Valid URL rtmp://62.90.177.144/flashphoner WCS does not pass connection parameters. So valid invocation is: /rest-api/push/startup { "streamName":"show8"...

Просьба дать трафик на сервер. Сейчас там пусто.

rtmpUrl looks incorrect Try rtmp://host:1935/flashphoner Here 'host' is your AMS IP. Because stream name is 'show8' and the stream name will be used in the re-publishing.

Hello We have fixed Mac OS Safari 11 beta with WebRTC and it should work now on our player and streamer: Build 2370. Player https://wcs5-eu.flashphoner.com/demo/player Streamer https://wcs5-eu.flashphoner.com/demo/two-way-streaming Regarding iOS, it is currently under testing. I will let you...

Hello You can fix it using the troubleshooting page: https://forum.flashphoner.com/threads/troubleshooting.10768/#post-11518

We have RTMP pooling feature in our roadmap. I will inform you if we have any news about this. As an option you can try to pool WCS stream over RTSP. So if one WCS server has a publishing stream 'stream1', the stream is shared over RTSP: rtsp://host:554/stream1 Therefore you can pool this RTSP...