Standard STUN/TURN WebRTC works fineinside browsers and on simple home Wi-Fi Cone NATs, provided you budget heavily for global TURN relay bandwidth on mobile calls. Wonek's proprietary port-prediction NAT traversal over QUIC / WebTransport achieves a much higher direct P2P connection rate across difficult 4G/5G mobile CGNAT networks—delivering lower call latency and faster direct file transfers, while retaining automatic latency-measured encrypted relay fallback when firewalls block UDP completely.
| NAT Pair Topology | Standard STUN / ICE WebRTC | Wonek Port-Predicted QUIC P2P |
|---|---|---|
| Home Wi-Fi <-> Home Wi-Fi (Full/Restricted Cone) | Direct P2P succeeds | Direct QUIC P2P succeeds (TLS 1.3 + MLS E2EE) |
| Home Wi-Fi <-> 4G/5G Mobile CGNAT | Mixed — frequently falls back to TURN relay | High-success direct P2P path established |
| 4G/5G Mobile CGNAT <-> 4G/5G Mobile CGNAT | Fails direct ICE most of the time -> cloud TURN relay | Frequently establishes direct device-to-device P2P link |
| Symmetric / Restricted Carrier Gateways | Assumes STUN port stays static; times out to TURN | Proprietary port-prediction algorithm finds direct link |
| Enterprise Firewall Blocking 100% of UDP | Falls back to TURN over TCP/TLS | Automatic latency-measured encrypted relay fallback |
| Wi-Fi-to-5G Mid-Call Roaming | Full ICE restart & media pause | Smooth QUIC path migration & fast re-validation |
Why Naive STUN Assumptions Fail on Cellular Networks
A classic STUN check asks one cloud server 'What external IP and port did you see me come from?' and assumes the mobile carrier's NAT gateway will reuse that exact external port when talking to a completely different peer IP. Modern Carrier-Grade NAT gateways frequently allocate fresh ports per destination—rendering the STUN coordinate obsolete before the first packet arrives.
Instead of immediately surrendering to a slow cloud relay, Wonek employs a proprietary port-prediction NAT traversal algorithm engineered for real-world CGNAT behavior, achieving direct encrypted QUIC peer-to-peer sessions at a markedly higher rate.
Dual-Layer Security Regardless of Direct or Relay Path
Whether traffic flows directly peer-to-peer across 5G or transitions automatically onto a latency-measured relay behind strict corporate Wi-Fi, every packet is protected twice: mandatory QUIC TLS 1.3 wire security plus client-side MLS (RFC 9420) end-to-end encryption.
| Architectural Layer | Wonek Stack | Classic WebRTC Stack |
|---|---|---|
| Transport Protocol | Unified QUIC / WebTransport (RFC 9000) | Split RTP/SRTP + SCTP + DTLS + separate WebSocket |
| Wire Security | Mandatory built-in TLS 1.3 from first handshake | Separate DTLS-SRTP media + TLS signaling |
| Application E2EE | Client-side IETF MLS (RFC 9420) in Rust core | Often hop-by-hop to SFU unless Insertable Streams/SFrame added |
| Round-Trip Call Latency on 5G | Shortest physical ISP peering route on direct P2P | Inflated by detour through nearest cloud TURN region |
| Multi-Gigabyte File Throughput | Full direct peer upload-to-download pipe + chunk resume | Throttled by TURN relay bandwidth caps & SCTP quirks |
Direct Bandwidth Unlocks Chunk-Resumable Large Transfers
Eliminating unnecessary cloud relays doesn't just shave voice latency—it lets Wonek stream multi-gigabyte files and photo albums directly between Apple devices with automatic chunk-level resumption.
| User Scenario | Winning Architecture | Why Users Feel It |
|---|---|---|
| Two people in the same city calling over 5G cellular | Port-Predicted QUIC P2P (Wonek) | Avoids hair-pinning voice packets through a foreign cloud region |
| Sending a 4 GB ProRes video shoot from iPhone on 5G to Mac | Port-Predicted QUIC P2P (Wonek) | Direct peer pipe runs at line rate with chunk-level resumption |
| Zero-install guest call inside a legacy desktop browser | Standard Browser WebRTC | Built into Chromium/WebKit without installing a native app |
| Screen sharing small 12pt code text with instant cursor response | Port-Predicted QUIC P2P (Wonek) | Lower RTT congestion loop keeps high-resolution frames crisp |
| Calling from locked-down hospital guest Wi-Fi | Both (via Encrypted Fallback) | Wonek automatically uses its latency-measured encrypted relay |
Frequently Asked Questions
Does direct P2P work on every single network on earth?
No physical UDP protocol can punch through a firewall that drops 100% of UDP packets—which is why Wonek pairs high-success port-predicted P2P with automatic latency-measured encrypted relay fallback so calls always connect.
Is my media still encrypted when flowing directly peer-to-peer?
Yes—doubly so: QUIC enforces TLS 1.3 transport encryption on the wire, and Wonek's Rust MLS (RFC 9420) core encrypts payloads end-to-end between authorized devices.
Why does reducing relay fallback improve voice quality?
Direct paths lower round-trip latency and jitter, preventing awkward talk-over collisions while Opus audio and echo cancellation keep voices crisp.
Related Comparisons & Deep-Dive Guide
QUIC & WebTransport Messengers vs Legacy TCP WebSocket Chat Apps
Compare native QUIC and WebTransport messaging against legacy TCP WebSockets: zero head-of-line blocking, 1-RTT TLS 1.3 setup, and Wi-Fi-to-5G migration.
IETF MLS (RFC 9420) vs Pairwise Double Ratchet for Group & Multi-Device E2EE
Compare IETF Messaging Layer Security (MLS, RFC 9420) against legacy pairwise Double Ratchet + Sender Keys for multi-device and group end-to-end encryption.