A STUN server allows a computer on the internet to determine its own public-facing IP address. STUN is a protocol for the self-discovery of a client's public IP address from behind a NAT. However, most clients do not know their own public IP address. To do so, a given client must be able to target the other client's public IP address and negotiated port. Now that we know what we want, how does this relate to STUN, TURN, and ICE? UDP - Direct Between Source and Target of Media Flowįor us to establish a UDP connection between two clients we need to be able to negotiate through a firewall. TCP/TLS - Indirect (relayed) between source and target of media flow, via TCP, with an extra layer of encryption.TCP - Indirect (relayed) between source and target of media flow, via TCP.UDP - Indirect (relayed) between source and target of media flow.UDP - Direct between source and target of media flow.This implies the following preferred precedence of network communication protocols: Ultimately, the goal of a real-time application is high throughput, low latency communication between various clients that may (or may not) be behind restrictive firewall rules. What are these things really? Why do they exist, and how are they used by LiveSwitch? The goal of this article is to demystify these technologies and their usage. We techies love our acronyms, but ICE, STUN, TURN, TURNS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |