3 ms·
It sounds like the only thing you did was signaling, not STUN and TURN. If you do both STUN and TURN it works on most networks. I've worked at really restricte
by SahAssar 6y ago
It sounds like the only thing you did was signaling, not STUN and TURN.
If you do both STUN and TURN it works on most networks. I've worked at really restricted work sites, and while STUN fails at those if you have a TURN server then it almost always works.
These sort of comments are why people think webRTC is unstable while the same people use slack calls which literally use webRTC.
I might be wrong, but please don't talk about network reliability in webRTC without specifying if you have a working STUN and/or TURN setup.
- lovedswain 6y agoWhat has WebRTC got to do with me personally? Please try to speak to the topic, it makes for better reading, and threads much less likely to lead in the wrong direction. > If you do both STUN and TURN it works on most networks TURN requires clean outbound UDP/TCP connectivity which is far from ubiquitous, there are numerous corporate firewalls where "CONNECT <x>:443" is the best that could be hoped for, and even in some of those, where if the resulting connection did not include an obvious SSL handshake the connection would be immediately reset.