Important Update - Stun Server Configuration

[Selim Emre]

During last couple of days, some of our customers have been complaining about an issue on WebRTC publishing or playing. Based on our root cause analysis, we noticed that the issue is caused by external STUN server provided centrally by Google that is preconfigured and used by Ant Media Server. Till the issue become obsolete which is unknown for the time being, we have decided to share with you a solution to be protected in advance.

Here below are the list of technical instructions that can be followed to overcome this issue in case or before it’s faced. Please also note that, we propose three alternative configuration which has the same preventative impact and we leave it up to you which one to go with based on operational easiness.

 

Solution 1:

Please add the following line
settings.webrtc.stunServerURI=stun:stun1.l.google.com:19302

into the following file
/usr/local/antmedia/webapps/APP_NAME/WEB-INF/red5-web.properties
and restart the server.

Solution 2:

Please edit the following line in
/usr/local/antmedia/conf/red5.properties
server.name=SERVER_PUBLIC_IP_ADDRESS

Please add the following line
settings.replaceCandidateAddrWithServerAddr=true

into the following file
/usr/local/antmedia/webapps/APP_NAME/WEB-INF/red5-web.properties

and restart the server

Solution 3:

You can install your own TURN server and use it as a STUN server.
You can look this document to install TURN server:
https://github.com/ant-media/Ant-Media-Server/wiki/Turn-Server-Installation with this setting:
settings.webrtc.stunServerURI=stun:YOUR_TURN_SERVER_IP:3478 

In case you are curious about the details of this issue and technology behind, you can contact us directly to get more information.

[Nagendra Kumar1648581702]

Hi Selim,

    You mentioned about the issue of WebRTC publishing or playing. We are using enterprize edition and using webrtc for play and publish.  On further analysis, we found that the ic_connection_state changed to disconnected.  Very recently we have started getting the issues of dropouts. Is this stun server configuration could be the root cause? 

Thanks

Nagendra

[Selim Emre]

Hi Nagendra,

Actually root cause is the failure to obtain a public IP address from STUN server. We were using default Google Stun server -> stun:stun.l.google.com:19302. But we encountered an issue with STUN Server. That's why we published these details.

I hope, it's clear.

Best Regards,

Selim