5 ms·
In some cases a TURN server is still required[0] Until ICE supports TLS/DTLS it is worth deploying. I hope to fix this in the near future though! [0] https://
by Sean-Der 4y ago
In some cases a TURN server is still required[0]
Until ICE supports TLS/DTLS it is worth deploying. I hope to fix this in the near future though!
[0] https://stackoverflow.com/questions/61287054/understanding-sfus-turn-servers-in-webrtc/61300033#61300033 https://stackoverflow.com/questions/61287054/understanding-s...
- moron4hire 4y agoI see, so the TURN server negotiates the access authorization (and provides a single connection point), but then the SFU handles the routing between peers. Is there a way to get a standard TURN server to reuse outbound streams for 3+ user chat? E.g. I have a CoTURN install that is strictly used for audio and while I'm not too concerned about bandwidth at my server, I'm very concerned about uplink bandwidth for users with asymmetric connections (which is practically all of them). I'm sorry to bug you here, but it's so hard to find anyone who actually knows much of anything about WebRTC who isn't just parroting stuff they read on Stack Overflow. Half the time I get the same, subtly-wrong answers about basic signaling, even when my question isn't even about signaling.
- Sean-Der 4y agoYea! TURN can just be the authorization/entry point into your network. The SFU is in charge of actually shuffling the packets between peers. You will need to use a SFU to reuse outbound streams unfortunately. Happy to help more on https://pion.ly/slack https://pion.ly/slack! I come back to HN once or twice a day, but will see your questions instantly. I am `Sean-Der` in `#pion`