Comments on: WebRTC, TURN and Geolocation. How to Pick the Best Server to Work With?

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Thu, 12 Sep 2019 18:08:06 +0000

I probably didn’t finish that thought on the screen 🙂

In the context of this post, it is probably enough and should work. But once you add the media servers into the mix, then this is where things get tricky – relying on ICE is too late in the process to allocate a media server, as you need the media server’s public IP addresses to begin with.

The initial SDP that starts the whole ICE procedure already gets connected to a media server, and that connection is the one determining the server location – over HTTPS and not SRTP.

By: Aswath Rao

Aswath Rao — Thu, 12 Sep 2019 17:53:06 +0000

I am missing your point of being complicated and risky. Doesn’t the spec allow for multiple ICE servers being included and the clients getting multiple relay addresses and let the ICE procedure select one among them? The only difference between that and what I am suggesting is that the multiple servers will be identified by a single domain name and DNS query will identify the individual addresses. I don’t think procedurally there is no difference between the two,

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Thu, 12 Sep 2019 05:08:21 +0000

In reply to Aswath Rao. Aswath, How are you going to map the responses? You are essentially opening a single peer connection in front of 3 different media servers in order to run ICE negotiation against all 3 at the same time using the same algorithm which is supposed to take place on a single machine on the server side. Seems somewhat complicated and risky.

By: Aswath Rao

Aswath Rao — Thu, 12 Sep 2019 00:13:19 +0000

Apropo Nicholas’suggestion, can we not use Multivalue answer option provided by AWS Route 53? Then the browser can gather ICE candidates from each one and let ICE sort out the best candidate.

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Tue, 26 Dec 2017 08:16:43 +0000

In reply to Bobo. Yes they can. It doesn't occur often, but it can happen.

By: Bobo

Bobo — Mon, 25 Dec 2017 08:48:32 +0000

can two webrtc Clients use two different Turn Servers (cascading) to set up audio/video session ?

By: Misi

Misi — Wed, 30 Nov 2016 15:02:37 +0000

In reply to Nicholas Reid.

Hi Nicholas,

May anycast as an alternative of split horizon dns discovery, could help to find the closest TURN server PoP.
As it is written in turn discovery:
https://tools.ietf.org/html/draft-ietf-tram-turn-server-discovery-10#section-6

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Tue, 29 Nov 2016 21:20:56 +0000

In reply to Warren McDonald. Warren, that should work. You'll still need to configure the backend properly and take care of situations where sessions are made direct or "via" STUN to a media server in your backend.

By: Warren McDonald

Warren McDonald — Tue, 29 Nov 2016 21:17:00 +0000

What about Nicholas’s approach, but just include the 3 closest in iceServers array and let ICE sort out the best. My understanding is that fastest response is at the head of queue for negotiation.

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Tue, 29 Nov 2016 16:27:23 +0000

In reply to Nicholas Reid.

Nicholas,

Thanks. I am a fan of simple approaches, but in this case, I guess I’d go for an elegant one if one is to be found 🙂

I am wondering if anyone went the length of putting up such a system in place.