5 min readlatest
WebRTC behind a firewall: TURN over TLS on port 443
Calls that fail on corporate networks usually need TURN over TLS on 443. How to configure it, confirm it works, and why it should stay the last resort.
turnice
A field guide to WebRTC in production
Practical tips, tricks, and hard-earned tweaks to make your WebRTC stack connect faster, handle edge cases, and run better in production.
Latest
All articles6 min read
WebRTC E2EE with SFrame: what your SFU can still read
SFrame hides WebRTC media from the SFU, not the metadata. Your server still sees who spoke, when and how loudly, from the audio level header extension.
dtls
6 min read
WebRTC bitrate stuck low? maxBitrate is only a ceiling
You set maxBitrate to 2.5 Mbps and WebRTC sends 700 kbps. The congestion controller picks the rate. How GCC decides, and which getStats fields show why.
rtp
6 min read
Why WebRTC video freezes, and how getStats tells you
WebRTC video freezes come from loss, keyframe waits, jitter or dropped frames. The getStats counters that tell them apart, and the fix for each.
rtp
5 min read
WebRTC DTLS handshake failed: how to find out why
ICE says connected, then connectionState goes to failed. That is the DTLS handshake, and RTCDtlsTransport's error event names the exact cause.
dtls
The stack
Four places a call goes wrong