Search results

Добрый день Возможно, это будет реализовано в следующей мажорной версии WebSDK. Для текущей версии конфликты, решаемые исключением или переименованием пакетов, можно разрешить, собрав WebSDK из исходных текстов по этой инструкции с необходимыми изменениями.

Добрый день. 1. Имя потока можно изменить на бэкенде при помощи REST hook /publishStream 2. Если два и более подписчиков смотрят поток с камеры с одним и тем же адресом, будет использовано одно подключение к камере.

There is one possible way to escape this error: use UDP transport for WebRTC from Firefox as described here, for example (stream publishing) session.createStream({ name: streamName, display: localVideo, cacheLocalResources: true, receiveVideo: false, receiveAudio: false...

We work on it (internal ticket WCS-1894) and let you know when find a fix.

Good day. You likely use Firefox browser to publish or play WebRTC stream via TCP. Try to switch off any additional networks and VPNs on your PC/Mac. If this did not help, use Chrome browser for streaming. Firefox can not work stable with TCP ICE candidates.

Good day. You are trying to send HTTPS request to HTTP port. Please try to change request URL to HTTP http://server:9091/rest-api/push/startup or change port to HTTPS https://server:8888/rest-api/push/startup

Добрый день. Получить список всех потоков с их параметрами можно при помощи REST запроса http://server:8081/rest-api/stream/find_all Данный запрос возвращает список в формате JSON, например [ { "appKey": "defaultApp", "audioBitrate": 0, "audioCodec": "opus"...

Good day. It depends on server capabilities. For example, c4.4xlarge AWS instance (16 virtual CPU cores, 30 Gb RAM) should be enough to handle up to 100 publishing users. For 2000 viewers 64 GB RAM, 2 x CPU Xeon 8-10 cores, 10 Gbps link is required. If you need more viewers, you shouid deploy...

Hello. Please set the following parameter in flashphoner.properties file rtp_activity_detecting=false,0 Also, we recommend you to update to latest build 5.2.63.

We've checked your report. As we mentioned, the message "Failed to send, channel is not available" appears when playing client has dropped the connection, and some data left to send to. So, it is not a bug, but symptom. Please, comment out or remove the following string in your...

We've received your report. It contains no configuration (empty folder) and client debug logs (empty folder). The information is not enough to diagnose and try to reproduce problem. So we recommend you to update to latest build from this page, check if problem persists and, if yes, prepare full...

Good day. We've checked your server and strongly recommend you to do the following: 1. Update WCS to latest build from this page. Now you have an outdated test version that is not intended for production use 2. Increase server RAM to allocate more Java heap memory for WCS. Now, you have default...

We've reproduced the problem. It occurs when VP8 codec priority is higher then H264: codecs=opus,...,vp8,h264,... We work on it to prevent server crashes and let you know when fix it. As workaround, you can disable H264 on MS Edge side using stripCodecs option: session.createStream({...

Good day. Please prepare a report as described here and send to support@flashphoner.com, we will check

Good day. Please update WCS to the latest build from this page and check if the problem still persists. If yes, please prepare report as described here and send to support@flashphoner.com, we will check.

Спасибо за уточнение, мы проверим

Добрый день. Воспроизводится ли проблема в последней официальной сборке Chrome 73? Мы проверим работу WebSDK в Chrome Canary 75. О результатах сообщим. Отметим, что совместимость с релизом Chrome 75 в любом случае потребует проверки, т.к. разработчики могут внести еще изменения.

Hello. Please send SSH credentials to support@flashphoner.com. We will check.

Good day. Please check if the problem persists on latest WCS build from this page and Web SDK build from here. If the problem persists, try to reproduce it on example web application such as Two Way Streaming. Also check if the problem reproduced on our demo server...

Добрый день. Настройки по умолчанию (1 Gb Java Heap) предназначены скорее для тестирования сервера в минимальной конфигурации, но не для эксплуатации. 32 Gb должно хватить. Логи высылайте, если в дальнейшем проблема воспроизведется. Состав отчета об ошибке приведен здесь.