WebRTC and SIP both carry live voice to an AI agent. Voice AI platforms list them side by side, so teams building an AI receptionist often expect to pick one or the other for connecting callers to the agent. In practice, each protocol serves a different way
On September 22–23, I was in Chicago for the IIT Real-Time Communications Conference at Illinois Tech, an annual IEEE conference where industry engineers and academic researchers present work on real-time communications. This year’s tracks covered programmable networks, WebRTC applications, emergency communications, and AI in real-time communications. I
A production voice agent has a latency budget of roughly 800 milliseconds before a conversation starts to feel slow. That budget is spent across eight sequential stages, typically split across three to five different vendors depending on how the stack is assembled. This post maps that voice
Once again, WebRTC Live broadcasted direct from the RTC.ON conference in Kraków, Poland where WebRTC.ventures CTO Alberto Gonzalez interviewed two speakers: And one guest: WebRTC Live #117: Live from RTC.ON 2026 Episode highlights below the video. Episode Highlights Pratim Mallick, Staff Software Engineer at Stream Charles Duyk,
