How TURN Servers Facilitate WebRTC Media Relay

WebRTC technology is designed to establish direct peer-to-peer connections for real-time audio, video, and data streaming. However, strict firewalls and complex network configurations often block these direct paths, causing connection failures. This article explains how a TURN (Traversal Using Relays around NAT) server solves this problem by acting as a media relay, ensuring reliable communication when direct peer-to-peer connections are impossible.

In an ideal WebRTC scenario, two devices connect directly using STUN (Session Traversal Utilities for NAT) to discover their public IP addresses. However, about 10% to 15% of WebRTC connections encounter strict security barriers, such as Symmetric NATs. Symmetric NATs restrict incoming traffic unless the internal device has previously sent data to that specific external IP and port. This security measure prevents direct peer-to-peer connections, leaving the devices unable to communicate directly.

When the ICE (Interactive Connectivity Establishment) protocol determines that a direct connection is blocked, it falls back to a TURN server. The TURN server acts as a neutral intermediary located on the public internet. Instead of attempting to send media packets directly to each other, both peers establish a secure connection with the TURN server.

Once these connections are established, Peer A sends its media stream directly to the TURN server. The TURN server receives the packets and immediately forwards them to Peer B. Conversely, Peer B sends its media to the TURN server, which relays it back to Peer A. Because both peers are initiating outbound connections to a public server rather than receiving unsolicited inbound traffic, firewalls and NAT devices permit the packets to pass through, bypassing the connection restrictions.

While TURN servers guarantee connection success, they require significant bandwidth and server resources because they must process and relay every packet of the call in real time. Because of the associated hosting costs, WebRTC applications use TURN servers only as a last-resort fallback, relying on the ICE framework to prioritize direct peer-to-peer routes whenever possible.