Tunnel between browser and Janus over TCP 443 possible?

[Alex Y]

Hi fellas!

Since webRTC video is UDP-based, it can be filtered/blocked by firewall. And we already seen this. Many of our users can't connect to Janus because of their corporate firewalls or public wifi firewalls.

We talked about this problem with guys from Flashphoner. They told it's possible to solve. Solution is to make tunnel over https TCP. That's what they said. Still, issue is not solved at flashphoner (work in progress without release date). Question is, do you guys think it's good idea making webrtc videochat over TCP? If no, why? If yes, is it possible to implement in Janus?

[Lorenzo Miniero]

This is a generic WebRTC question, and not Janus related. It's best to look for discussions about this on discuss-webrtc, e.g.

https://groups.google.com/forum/#!topic/discuss-webrtc/bq2tUi_guE4

L.

[Robert Silný]

Hi Lorenzo,

i am trying to solve, the same problem...client is behind a corporate firewall/proxy. I tried to dump a comunication and standartd Janus WebRTC communication is running over UDP.

Is there a any way to turn it in TCP? Standard peer-to-peer WebRTC communication is allways trying both ways UDP and TCP. I implemented a STUN and TURN server on TCP(443) and configured it into janus.cfg.

Do i need to directly sent in script that i want to use a TURN server, or is the main configuration in janus.cfg enough?

Do you have some other tips how to solve problemt with client behind proxy with only tcp 443 and 80 allowed.

Thanks in advance.

Rob

 

Dne sobota 17. prosince 2016 13:33:01 UTC+1 Lorenzo Miniero napsal(a):

[Lorenzo Miniero]

Il giorno mercoledì 1 marzo 2017 12:24:33 UTC+1, Robert Silný ha scritto:

Hi Lorenzo,

i am trying to solve, the same problem...client is behind a corporate firewall/proxy. I tried to dump a comunication and standartd Janus WebRTC communication is running over UDP.

Is there a any way to turn it in TCP? Standard peer-to-peer WebRTC communication is allways trying both ways UDP and TCP. I implemented a STUN and TURN server on TCP(443) and configured it into janus.cfg.

Do i need to directly sent in script that i want to use a TURN server, or is the main configuration in janus.cfg enough?

Do you have some other tips how to solve problemt with client behind proxy with only tcp 443 and 80 allowed.

As the FAQ says, #27:

https://janus.conf.meetecho.com/docs/FAQ

and as I believe the janus.cfg text says as well, that's NOT something you configure in Janus. Janus is supposed to be always publicly reachable somehow. It's users that may need TURN support, to communicate with Janus. Configure the TURN servers on the client side, not Janus.

L.