Failed by ICE timeout

[Ajinkya Kulkarni]

We have recently setup ICE server which is different from our existing WCS server. We decided to go for TURN server as web rtc was failing in some networks intermittently.
When I try to create a media session with that ICE server, it times out saying failed by ICE timeout. But on the TURN server logs it shows connection succes.
After setting up the TURN server, do we need to configure anything on the WCS server?

 

[Max]

Unfortunately WCS will not work with a separate ICE server.

To deploy the TURN server, you have two options:
1. Deploy a separate TURN server
2. Use the built-in WCS TURN server

Please note that if you're using a separate TURN server, all the UDP media ports from media_port_from-media_port_to range must be opened between TURN server and WCS server.
How to check port availability see here.

Read more about installing and configuring TURN server to work with WCS here.

 

[Ajinkya Kulkarni]

I have sent an email with error report. We are getting session Disconnected from Android.
We tried using the internal TURN server which works with Chrome on desktop but fails with Android client. It fails in case of a mobile network connection but works in case of Wifi connection. Please check the email with error report and let us know the path forward.

 

[Max]

As an option you can try to switch server to the TCP protocol.

Publishing and playing stream via WebRTC over TCP - Web Call Server 5.2 - EN - Flashphoner Documentation

docs.flashphoner.com

It should help on mobile networks.

ice_tcp_transport=true

In WCS_HOME/conf/flashphoner.properties

 

[Ajinkya Kulkarni]

I have already set that property to 'true'.
You will be able to find that in my mail with attached error report.

 

[Max]

In the logs provided we see the work in the mobile network is based on the IPv6 protocol.
There are two options for troubleshooting:
1. Convert the entire workflow to IPv4 only. To do this, ask your hosting provider for server with IPv4 public static IP or change hosting.
2. Configure your WCS server to work in IPv6 network as described here:

IPv6 support for WebRTC - Web Call Server 5.2 - EN - Flashphoner Documentation

docs.flashphoner.com

 

[Ajinkya Kulkarni]

1. If we change the entire workflow to IPv4 with static IP, we would be able to access the WSS URL with IP only. In such case it won't work under https web page
2. I checked the steps to use IPv6, I did not understand what needs to be done in this step -

Tje following settings can be used to set comma separated IPv4 and IPv6 interfaces to bind

• hls.address
• http.address
• https.address
• rtmfp.address
• rtmp.address
• rtsp.address
• rtsp_client_address
• ws.address
• wss.address

How to use the above setting to bind addresses?Can you please explain with an example.

 

[Max]

1. If we change the entire workflow to IPv4 with static IP, we would be able to access the WSS URL with IP only. In such case it won't work under https web page

You can (and should) attach domain name to static IPv4 address.

How to use the above setting to bind addresses?

You can just leave those settings default if you have not set them earlier.