don wrote:The future:
Chrome 24 will introduce support for TURN which will allow us to tunnel UDP traffic for networks that block it and get around tricky NATs between two different clients.
(all following is regarding the WebRTC)
I'm trying it with Chrome Beta (24.0.1312.45), Chrome Dev (25.0.1364.5 dev) and even with the Chrome Canary (26.0.1373.0) and none of them seems to work behind the firewall (getting error message 1008).
They do work only when I open both TCP *AND* UDP ports 1024:65535, which, of course, defies the purpose of firewall.
What is still not clear to me - are future Chrome versions (>=24) going to work through the firewall without opening ANY TCP/UDP ports?
I understand that each firewall has its own inner workings which I have to figure out, but a precise description of which ports, in which direction should be opened would greatly help me.
And there's another thing that puzzles me - I don't have to open any ports for demo https://opentokrtc.com
to work, and it even works with the current Chrome (23.0.1271.101)...