Search results

Good day. We found a probable reason for SocketException and fixed it in build 5.2.1963. We also added some logging to detect a problem if it persists. Please update and check.

Good day. This is a known issue: a fixed 5 seconds timeout is used to check if a build is available to download. This timeout is enough in most cases, but may be not enough if there are som temporary network issues between server to update and the builds file storage. There is the ticket...

Send indication is sent by client. If client stops sending suck packet it probably stops sending a media traffic too.

Yes. According to the dump and explanation provided, a problem is between TURN server and publishing client, not between WCS and TURN сервер.

No. This is definitely a problem between publishing client and TURN server. Yes, the bottleneck may be in network settings.

Good day. Unfortunately, you've not provided any additional information to the dump: 1. TURN server address, WCS server address, client address 2. Was it publishing or playing client? We see in dump a periodic Previous segment not captured messages with TCP retransmission. It seems like a packet...

We checked publishing and playback on your server. When using a valid server domain name (we get it using reverse DNS lookup), a test stream is playing successfully in Player example in iOS Safari 17.4.1. But Safari refuses to connect to secure Websocket when connecting by IP address So you...

This is WebRTC library implementation behaviour. We can't change that.

Good day. We fixed the issue in WCS build 5.2.1960. Please update and check.

We tested WebRTC playback in iOS Safari 17.4.1 (iPhone 12 mini) on our demo server (WCS build 5.2.1917, WebSDK build 2.0.240): 1. Published a test stream in Media Devices example in Windows Chrome 123 2. Played the test stream in Player example in iOS Safari 17.4.1 The stream is playing...

Good day. Please read this article about RTSP streams load testing: How many RTSP cams can I connect to the WebRTC server?

Is the issue reproducing with the latest WebSDK build 2.0.242? Please update and check What iOS version (not phone model, iOS version and build, you can see it in Settings - General - About) do you test?

Please read this doc: How to reconnect to a stream automatically. A more complex example to restore publishing/playback: Streaming Auto Restore.

Please clarify the following: 1. What WCS and WebSDK versions do you use? 2. What iOS version do you test? 3. What do you try to test in Safari browser: publishing or playback? 4. Is the issue reproducing in pure Javascript Two Way Streaming example (demo server...

We raised the ticket WCS-4113 to investigate if IDecodedPcmInterceptor implementation can be placed to a separate package like IDecodedFrameInterceptor. Will let you know about progress here.

The dump contains no RTSP streams at all: But the file bad.txt contains the 400 Bad request error message: Seems like the bad camera declines OPTIONS or DESCRIBE request. Please check the camera or DVR setup.

Настройка ll_hls_time_min указывается в миллисекундах, в вашем случае ll_hls_time_min=1900 Настройка hls_time_min сейчас не используется.

Hello For bad RTSP URLs, please gather pcap - logs with VLC player for each bad URL. 1) Make sure the bad stream is playing in the VLC player 1. Launch VLC player on your PC. 2. Click Menu Media > Open Network Stream 3. Copy and paste the "bad" RTSP URL there. 4. Click Play. 1) Launch...

Please build the example according to step by step manual: Server audio processing. Is it building successfully or not?

Seems you've excluded H265 codec in settings: If you want to play H265 stream, you should remove it from exclusions list: codecs_exclude_streaming =flv,telephone-event