Search results

Здравствуйте. ESTABLISHED - это успешный коннект к вебсокету REGISTERED - это успешная регистрация на Asterisk В вашем случае регистрация не проходит. Проблема в настройках демо-сервера, там указан TCP протокол для SIP. sip_force_tcp=true Мы временно отключили эту настройку. Поэтому...

Good day. You should register a suitable domain name using GoDaddy, Google.Domains or other service, and bind the name to a server address using Internet.bs or other domain management tool. Then, you should buy an SSL certificate for the domain name form any CA service. You can also get a free...

About the report: there are no client debug logs provided, so we cannot parse traffic dump. But in publisher client logs we see that audio RTP activity timeout is reached. So we suppose there is no audio traffic from publuisher. We tried to reproduce the issue using latest WCS build 5.2.1126 and...

We fixed the issue in build 5.2.1126. Please update and check.

Also, when we tried to register on your PBX from our test server, registration fails due to Certificate unknown error. So please check if you've done the steps described here: SIP calls via SIP PBX server with self-signed SSL certificate

Unfortunately we have not received your report. Please modify iOS Two Way Streaming example application code minimally to reproduce the issue and send using this form

Good day. No. The user action must be performed to unmute the audio when autoplaying. If audio playing volume changing after publishing a stream fro the same page. please do this two steps: Audio playback tuning in iOS Safari

Please check /usr/local/FlashphonerWebCallServer/bin/setenv.sh file. Seems like LANG is set explicilty in the file. If not, please provide SSH access to the server using this form

We checked SIP registration from your server. Seems like your SIP PBX is unreachable from your WCS server Please check your NAT/router or PBX firewall setup.

Good day. This is a known iOS Safari bug fixed in 15.2. Please read the details here (p. 17)

We checked the report. Unfortunately, the test stream (streamtest we suppose) is published from Chrome 94 on Windows 10, but you mentioned the problem is in iOS SDK application. Also, the server where report collected is the Origin, but test stream seems to be playing from some Edge server, so...

We reproduced the issue and already testing the fix. Please be patient.

Please check if WCS build, configuration and JDK are the same on both servers. If not, make the problem server setup identical to a good one. If this does not help, collect a report from the problem server as decsribed here using report.sh script, and send using this form.

Please try to reproduce the issue in Media Devices example: 1. Choose 640x480 from resolution picker in iOS example or set width to 640, height to 480 in Android example. Please note that width should be set to 640 and height to 480, see code on GitHub. 2. Publish a stream 3. Check stream...

Please read here about receiving an error info: WebSDK error handling Also, please red this article What kind of server do you need to run a thousand WebRTC streams? about tuning and testing WCS for a huge number of subscribers. See the "Preparing for testing" chapter for a useful tweaks for...

Good day. You should set the same resolution as original stream, i.e. 640x480, not 480x640.

Please reproduce the issue and collect a report on server side as described here using report.sh script. Also collect traffic dump (the collection must be started before stream publishing). Send the treport using this form.

Проверили настройки сервера и логи. По логам не видно каких-либо проблем. Проблемы, которые вы описываете, похожи на нехватку битрейта (скорости канала) между пользователем и сервером. Рекомендации: 1. Выставить минимальное разрешение видео при публикации. Например, если ваше приложение...

Пришлите SSH доступ к серверу через эту форму. Проверим настройки сервера. Также опишите пожалуйста как технически работает ваше приложение: один ко многим, многие ко многим, вебинар, трансляция, и т. д.

Hello You can manually accept not trusted certificate in browser if you open page directly: https://ip:8443 Once you accepted server's certificates, you will be able to connect by IP. wss://ip:8443 Example: