WebRTC support of 300 ALTERNATE-SERVER TURN error code

[Oleg Moskalenko]

TURN is inherently a difficult protocol to load-balance. Full correct load balancing requires deep-packet-inspection and a load balancer integrated with TURN. But there is simpler way: 300 ALTERNATE-SERVER error code mechanism that makes it simple and it was specially designed for that purpose. But as far as I understand, the WebRTC TURN client does not support ALTERNATE-SERVER, yet. I'd like to ask whether there are definite plans for supporting that.

Currently, if you are using the very basic TURN (like no RTCP TURN streams) then a simple network load-balancer would work with TURN and WebRTC. But eventually those more complex TURN features (like mobile streams) will be used by the clients, and the primitive load balancers will stop working. I guess that the WebRTC client has to solve the problem for the future by supporting the 300 error code. 

Thanks
Oleg

[Philipp Hancke]

https://code.google.com/p/webrtc/issues/detail?id=1986 -- it's mostly a matter of someone investing the energy.

[Dmitry Zhukov]

Good to see that Google is aware of this. What about Firefox?

среда, 20 ноября 2013 г., 9:01:07 UTC-8 пользователь Oleg Moskalenko написал:

[Justin Uberti]

We are planning to support this in the near future.

[andrey.s...@gmail.com]

Hi Justing! Does WebRTC M70 release support    300 ALTERNATE-SERVER ?
What is the best way to load balance TURN servers?


четверг, 21 ноября 2013 г., 8:10:10 UTC+4 пользователь Justin Uberti написал: