-
-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question about multiple coturn servers in selfhosted #1286
Comments
Hi @Fantu, They are all used at the same time. It always connects to all the URLs there and checks them for connectivity. If one is able to connect, it will use it. |
the agent will connect to all TURN servers, and them it will use these connections to check if it can communicate with the other peers. If one responds faster, it will use it instead of the other, but there is no way to order these checks besides how you configure them. Once a turn is selected and used for the connection, the agents periodically send checks to validate if they are still available; if something goes wrong with the checks, the negotiation is restarted. There is no use of the next relay server in this case (not yet) In that sense, ICE chooses the faster one to reply to the initial check. Which, in many cases, is the one with a lower latency |
thanks to all for the replies |
Hi, now is possible set multiple coturn server, FWIK for example:
How are these used?
Is each request sent to a random coturn server on the list or does it follow the order and use the subsequent ones if the first one is not reachable?
The text was updated successfully, but these errors were encountered: