WebRTC Weekly Issue #662

Tsahi Levent-Levi from WebRTC WeeklyOct 28, 2026

WebRTC Weekly Issue #662

Native SDKs running old libwebrtc, Signal's hang-up bug, and Element's exit from Big Tech calls

Oct 28

Chrome now ships a new libwebrtc every two weeks, and the native SDKs inside your video app have not kept up: Ckristian Zoli’s scoreboard has them anywhere from 1.5 to 30 months behind. Elsewhere, Element launched MatrixRTC as its way out of Big Tech calls, and a bug in Signal’s calling library left a call running after the user hung up.

Thanks for reading WebRTC Weekly! Subscribe for free to receive new posts and support my work.

Subscribed

⭐ Tsahi’s Pick

Your browser runs WebRTC M156. Your video app might be running M124. (Ckristian Zoli on LinkedIn)
Ckristian checked which libwebrtc milestone the native SDKs of seven video platforms ship against Chrome’s M156. The results are... all over the place. It is also a question I get from time to time from vendors - when to upgrade libwebrtc itself. Since Chrome moved to a two-week cycle with M153, counting milestones misleads, so he counts time instead: about 1.5 months behind for Daily, about 30 months for Twilio and Jitsi. He works on the Vonage Video API and says so, and he applied the same method to everyone. Newer isn’t automatically better and more updates aren’t always great, so know each vendor’s upgrade strategy and pick the one that fits yours, not the one with the highest number.

📰 This Week in WebRTC

Inside Stream AI Moderation for Live Video & Audio (Stream) - an architecture walkthrough of how Stream moderates live video and audio
How to Choose a Server-Side WebRTC Implementation (WebRTC.Ventures) - a guide to picking a server-side WebRTC library, from Pion and aiortc to GStreamer
How Dicode built private video calls on OpenVidu (OpenVidu) - a case study of a Finnish software company building private calls for non-profits
Operator, I need an exit from Big Tech calls (Element) - Element announces MatrixRTC, its decentralised, end-to-end encrypted group calling
Signal flaw could expose audio and video even after users hang up (Help Net Security) - a write-up of CVE-2026-113380, a hang-up bug in Signal’s WebRTC-based RingRTC library
ElevenLabs wants to run your voice agent. Here’s what developers give up. (The New Stack) - on ElevenLabs’ managed voice-agent models, and yes - it is WebRTC-based
Your homegrown getStats() collector is already out of date (rtcStats) - on the maintenance burden of a homegrown getStats() collector

📣 Sponsors

vCon: The PDF for Your Conversations
An open standard for transcripts, metadata, and consent. Learn vCon.

Stop reading webrtc-internals by hand.
rtcStats reads it for you now.

💭 This Week’s Thought

Who is contributing to libwebrtc? That’s Google’s “pet project” we all use. A few things to note here. There are less commits. We’re now well into maintenance mode for this project. The portion of external contributors isn’t large, and Philipp Hancke is one person doing at least half of all external commits into this project. It would be nice to see other vendors pitch in (instead of complaining).

📢 Releases

mediasoup now ships its own built-in BWE (bandwidth estimation) module! - mediasoup 3.32.0 (Node) and 0.33.0 (Rust) replace the bundled libwebrtc BWE with their own
How AI Made SRS 8 Run Natively on Windows - SRS 8 now runs natively on Windows, with WebRTC WHIP and WHEP support

✍️ This Week on BlogGeek.me

Azure Communication Services is retiring: now what - Microsoft started limiting onboarding to Azure Communication Services. By September 30, 2028, the standalone services retire and calling stays only for Teams-tied use. I looked at what it means if you’re on ACS, and what it says about hyperscalers and Video APIs.

Thanks for reading WebRTC Weekly! Subscribe for free to receive new posts and support my work.

Subscribed

💡 Want to sponsor on WebRTC Weekly, WebRTC Glossary or webrtcHacks? Check out our media kit (reply back for questions)