All green but calls are broken #qoe #dashboards #webrtc

31 Jul 2026 · 2 min
1:40

In this presentation the speaker highlights a common mismatch between QoE dashboards that show all green indicators and users who experience terrible call quality. The core issue is that relying solely on server‑side metrics (packet loss, jitter) provides an incomplete view because it cannot detect client‑side problems such as maxed‑out CPU, Bluetooth headset disconnections, or Wi‑Fi to cellular handoffs. Conversely, collecting only basic client‑side metrics tells you that something failed but not where—whether the fault lies in the device, the network, the carrier, or the infrastructure. Without a detailed, layered breakdown, teams waste days chasing ghosts, reproducing issues that a proper client‑side diagnostic could pinpoint instantly. The speaker argues for dashboards that surface the specific layer that broke, enabling rapid, targeted fixes.

Chapters

More from Tsahi

9:15
youtube.com

After 15 years of WebRTC, here is when I drop peer-to-peer

1mo ago
1:39
youtube.com

Why UDP won the real-time war #programming #webrtc #shorts

1mo ago
1:37
youtube.com

The Difference Between SFU And TURN Servers #WebRTC #RealTimeCommunications

2mo ago
1:43
youtube.com

Why server logs are useless for WebRTC #webrtc #getStats #observability

2mo ago
1:49
youtube.com

How does WebRTC even know a packet was lost?

2mo ago
1:42
youtube.com

WebRTC gives you every tool to watch your calls, then collects nothing

2mo ago
14:03
youtube.com

Meta rebuilt AV1 for mobile scale. Should smaller teams follow? | Chats with Arin

2mo ago
1:16
youtube.com

Is your video API vendor ready for AI agents?

3mo ago
1:21
youtube.com

What "$4 per 1000 Minutes" Really Costs You (Video API Pricing)

3mo ago
1:30
youtube.com

How to Read the WebRTC Tools Hub in 90 Seconds

3mo ago
youtube.com

Advanced WebRTC: Where Every Course Stops

3mo ago
See all content