External STUN/TURN server

OpenVidu v2 Issues with deployment
1

Hi all!

We are using two external STUN/TURN servers (based on coturn) in our deployment. openVidu is deployed on another dedicated server as described in the docs. We are passing our two own coturn servers to the openvidu-browser via “OpenVidu.setAdvancedConfiguration” and can confirm that they are used on the client side.

Is there anything else we have to do on the server side? Is it OK that coturn is running on the openVidu-Server and that it is not used?

In the logfiles of KMS we can see some warnings:

info KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:566 WebRtcEndpointImpl() STUN port not found in config; using default value: 3478
info KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:574 WebRtcEndpointImpl() STUN server not found in config; remember that NAT traversal requires STUN or TURN
info KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:597 WebRtcEndpointImpl() TURN server not found in config; remember that NAT traversal requires STUN or TURN

Can we ignore these warnings or do we have to tell KMS somehow to use our two external STUN/TURN servers?

Thanks and kind regards!

2

Hi. There is no problem with such logs. It’s OpenVidu Server the one which configure the stun server to be used by KMS to autodiscover its own public ip:

But to have everything working you have to:

  1. Keep Coturn running in your deployment to be used by Kurento to autodiscover its own IP
  2. Configure in the browser side other coturn with OpenVidu.setAdvancedConfiguration

This warning is because the stun IP is not configured in the configuration parameters and there is no need to worry about.

3

Hi! Thank you very much for your answer. Just to clarify: there is really no scenario/special network setup where it is better that Kurento also uses the same STUN server as the clients do?