WebRTC Turn Servers

[Julian Ivanov]

Hi,

I have the following issue. In my config on client side I have several turn servers which are spread around the world. My client is located in Germany and wants to connect to the server which is also in Germany. The connection is only possible through turn. However, webRTC gives higher priority to the ice server which is first in the list of servers (see screenshot). So in my case, the turn server located in Japan is taken before the turn server located in Germany. Is there a way webRTC also considers the latency and not just the order when prioritising ice servers and how would you advise to solve this situation? 

[Philipp Hancke]

this is typically solved by using latency-based DNS (e.g. amazons route53) for TURN.

Am Sa., 4. Sept. 2021 um 14:36 Uhr schrieb Julian Ivanov <julsk...@gmail.com>:

Hi,

I have the following issue. In my config on client side I have several turn servers which are spread around the world. My client is located in Germany and wants to connect to the server which is also in Germany. The connection is only possible through turn. However, webRTC gives higher priority to the ice server which is first in the list of servers (see screenshot). So in my case, the turn server located in Japan is taken before the turn server located in Germany. Is there a way webRTC also considers the latency and not just the order when prioritising ice servers and how would you advise to solve this situation? 

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/f6f5156e-8533-4076-a7e6-534d74c88657n%40googlegroups.com.