Making Sure Every Call Works

on YouTube ↗21m

" summary

Shows how to cut failed first calls by running three concrete pre-call checks: a device preview using enumerateDevices and getUserMedia with explicit deviceId constraints and an audio level meter; a connectivity check that counts relay vs reflexive candidates from ICE to verify TURN/STUN reachability; and a 15‑second GetStats snapshot to measure video bitrate, video packet loss and audio packet loss. Uses test.webrtc.org and recommends thresholds: audio bitrate >300 kb/s, video packet loss <3% (audio only if packet loss <5%) to decide audio+video, audio only, or fail.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 2:33Questions
3. 5:493 really quick checks inside your app
4. 6:35Part 1: Hardware setup
5. 8:45Constraints
6. 11:11Part 2: Checking connectivity

" related talks

• 37mWebRTC: From The Ground UpNick Chadwick · Demuxed 2016
• 21mOptimizing the customer experienceAMITHA PULIJALA · Kranky Geek WebRTC Show 2015
• 53mA Million Video Calls a Day, or Call Your MomAleksandr Tobol · HighLoad++ Siberia 2018
• 26m#javascript Audio/Video Streaming: #WebRTC APIs 101 explainedAlessandro Polidori · CityJS Athens 2023
• 56mYou're on Mute! WebRTC and our Lives on ScreenPhil Nash · Developers Summit 2021
• 21mA closer look at the WebRTC UX/UI APIArin Sime · Kranky Geek WebRTC Show 2015
• 21mDecisions & considerations in building your WebRTC appRob Brazier · Kranky Geek WebRTC Show 2015
• 27mWebRTC: Real-Time CommunicationsYlia Kasianenko · OdessaJS 2015