Search results

Good day. You should add sfuApp application using CLI: add app -m com.flashphoner.sfu.handler.SFUHandler -c com.flashphoner.sfu.handler.SFUCallbackHandler sfuApp sfuApp "http://localhost:8081/apps/EchoApp" or just adding application description to apps section of database.yml file apps...

Добрый день. Мы тестировали WCS CDN в AWS и Google Cloud: Настройка балансировки нагрузки с масштабированием при помощи AWS ELB Настройка балансировки нагрузки с масштабированием в GCP Для AWS также есть заготовка шаблона для CloudFormation: Развертывание WCS при помощи CloudFormation По...

Good day. You should use standalone license in this case. But the license key must be activated once on the server instance. So activation server https://my.flashphoner.com must be available from the instance for activation. You should do the following: 1. Connect the server to internet 2. Run...

Hello We will try to reproduce issue on our Asterisk server. You can also provide 4 (four) SIP extensions for our tests with your Asterisk. Private form for SIP accounts.

If you don't receive REGISTERED, it seems your PBX works over SIP/TCP. WCS works over SIP/UDP by default. 1. Add this line into /usr/local/FlashphonerWebCallServer/conf/flashphoner.properties sip_force_tcp=true 2. Restart process. service webcallserver restart Therefore you can force SIP...

Hello Please describe how to reproduce issue step-by-step. Example: 1. Scheme Browser1 <> WCS <> Asterisk <> WCS <> Browser1 Asterisk extensions: 2001 2002 2003 2004 2. Calls using Phone Min. https://demo.flashphoner.com/client2/examples/demo/sip/phone/phone.html 1) Call from 2001 to...

Hello Works now. The demo server has been restarted. Please try again. Please note. The demo server is under load. Anyone can test any feature on this server in parallel with your tests. Video Chat uses the same script conference.js. It works too.

To fix the problem, we need to reproduce it. That's why we asked to provide access to your environment. We recommend the following: 1. Always update entry point node first. 2. If no connections to node in /cdn/show_nodes result: 2.1. Check if node is running 2.2. Check CDN port availability...

Did restart helps? Please also note that CDN consisting of Docker instances on the same host is not recommended for production/ We use that case for testing purposes only. If you use a such configuration consider migration to VPS or physical servers.

You should set the following fields: /push/startup { "streamName": "stream", "rtmpUrl":"rtmp://a.rtmp.youtube.com/live2/aaaa-aaaa-aaaa-aaa", "rtmpTransponderFullUrl": true, "rtmpFlashVersion": "LNX 76.219.189.0" } See also supported REST query parameters list here. We...

Please provide SSH access to all the nodes using this form.

Please check if TCP port 8084 is available both from D on A and from A on D nodes. This is CDN signaling port, it must be available on all nodes from all nodes. Check also which nodes are connected to D using /cdn/show-nodes query.

There is the ticket WCS-3051 to implement secure RTSP (RTSPS). But we found no RTSP cameras supporting it. If you provide a such RTSP URL like rtsps://user:passwd@rtsp_server/rtsp_stream, we'll change this ticket state to active.

Good day. Yes, WebRTC specification strongly requires data encryption. That's why WebRTC signaling works only via secure websocket connection (except localhost, for debugging purposes) RTSP supports basic authentication only, so yes, credentials should be passed in URL. But you can hide...

Good day. That's the problem. You should set an actual RTMP publisher version rtmp_flash_ver_subscriber=LNX 76.219.189.0 disable RTMP stream name prefix rtmp_transponder_stream_name_prefix= and use full RTMP URL rtmp_transponder_full_url=true A final set of server parameters that should work...

Good day. Please clarify: do you have the only entry node per CDN (node A)? In this case, when node A is restarted, you should either restart other nodes to enter CDN again, or try to reset all CDN connections on all the nodes using REST API: Connection reset using REST API This is default...

The issue was fixed in WebSDK build 2.0.217. Please update @flashphoner/websdk package and check.

This should work in any environment. But all the filesystems are virtual in docker, so any disk I/O operations may be slower, and this is impredictable. In docker environment, we recoddems to inscrease a maximum snapshot taking interval, for example twice snapshot_taking_interval_ms=6000 Also...

Yes, the parameters are applied to REST API query. The CPU is not a bottleneck in this case, but disk I/O is. You can set up RAM drive and assign snapshots dir to it: snapshot_auto_dir=/ramdrive to prevent disk I/O issues.

No. Video Chat example works with 5.2.1131 on demo server.