When WebRTC calls are between parties who are not on the same network, have symmetric public-private pairing (NAT), or have firewall restrictions there are a number of protocols that can be used. This post describes relative QoS performance working with no ICE Servers, a public STUN server, and a self-hosted CoTURN server.
For use cases like telehealth where security and privacy are paramount, WebRTC developers use ICE servers to find their way through restrictive firewalls. In this blog post, we will review the signaling process, STUN and TURN servers, and share some tips on how to alleviate ICE issues that can be caused by certain network restrictions.