WebRTC: ICE, STUN and Peer Connections
WebRTC supports real-time audio, video and data exchange in browsers and applications. Signaling, connectivity checks and media transport are related but separate parts of a session.
Updated · Editorial approach and simulation limits
Signaling exchanges session descriptions
Peers need a signaling channel to exchange session descriptions and connectivity information. WebRTC does not standardize that application signaling service; a website or application chooses how to deliver an offer, answer and candidate updates.
An SDP offer or answer describes media sections and supported parameters. It does not prove that a network path has been established. Separate the signaling messages from the ICE checks that test candidate paths.
ICE, STUN and TURN find a usable path
Interactive Connectivity Establishment gathers local and server-reflexive candidates, then tests candidate pairs. STUN helps a peer learn how it appears from a server’s perspective; TURN can relay traffic when a direct path is unavailable or policy requires relaying.
A successful WebRTC session is therefore not necessarily a direct peer-to-peer connection. NAT behavior, firewall rules, network policy and TURN availability affect which candidate pair is selected.
Media security and troubleshooting
WebRTC media uses secure transport mechanisms including DTLS-SRTP, while data channels use SCTP over DTLS in the standardized stack. The actual packet path can include UDP or a relay and may be encrypted, so a network capture often cannot reveal the conversation content.
If a call has no audio or video, inspect signaling completion, ICE candidate exchange, selected pair, relay reachability and media counters separately. Protocol Explorer’s WebRTC overview is a conceptual sequence rather than a live call.
Explore WebRTC interactively
Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.
Specification and source
For exact protocol requirements, consult the primary document: RFC 8825: Overview: Real-Time Protocols for Browser-Based Applications. This page summarizes selected behavior and is not a substitute for the specification.
Related protocol lessons
Browse all application protocols · Trace application setup separately from media transport