On 12/16/2014 09:22 AM, James Knott wrote:
On 12/16/2014 12:08 PM, James Knott wrote:
On 12/16/2014 11:58 AM, Carlos E. R. wrote:
Firewall/nat traversal is done with the help from stun servers.
http://en.wikipedia.org/wiki/STUN
That direct conversation happens is obvious when you setup the whole thing yourself, and the server simply does not have the internet pipe to hold all the bandwidth of the simultaneous conversations it handles. Being a private setup, you control it fully. I'm aware of STUN, but haven't investigated WebRTC enough to see what it uses.
Ah...
From the article: http://www.webrtc.org/faq "Includes and abstracts key NAT and firewall traversal technology using STUN, ICE, TURN, RTP-over-TCP and support for proxies."
And the heavy lifter here is TURN. Go read about that. It does EXACTLY what I said it does. Man in the Middle. Google probably uses excess bandwidth all over the world to supply TURN servers, just like every sip provider has been doing for years. WEBRTC has no real magic of its own other than bundling it into the browser. I bet they even forgo encryption, relying on SSL alone. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org