By Sagar Shankaran, Founder of CallSphere
RTCP Receiver Reports carry the only honest measurement of what your caller actually heard - jitter, loss, delay - reported by their device. Here is how to capture, decode, and dashboard them across a Twilio AI voice fleet.
Key takeaways
Server-side metrics tell you what you sent. RTCP Receiver Reports tell you what the caller received - and those numbers are different. A perfect outbound stream from your media server can arrive at the caller with 4% loss after a Wi-Fi roam. Without RTCP, you will never know.
Teams instrument their media server, see clean stats, and conclude calls are healthy. But the carrier hop, the last-mile, and the caller's device all add loss and jitter that only show up in RTCP RR coming back from the receiver. RFC 3611 RTCP-XR adds even richer per-block stats - if you can decode them.
The second trap: RTCP RR is sent every five seconds by default, so a one-second glitch never appears. RTCP-XR with VoIP Metrics Report Block fixes this with cumulative per-call stats but requires both endpoints to support it.
Configure your media server to emit RTCP RR every two seconds and parse incoming RR for fraction_lost, cumulative_lost, jitter, last_sender_report, delay_since_last_sr. Compute round-trip time as time_now - lsr - dlsr. Build the same loss/jitter/RTT panel for ingress (what we received) and egress (what they received). Compare - the worse leg is the one to investigate.
flowchart TD
A[Media server sends RTP] --> B[Receiver gets RTP]
B --> C[Receiver sends RTCP RR every 2s]
C --> D[Media server parses RR]
D --> E[Extract fraction_lost, jitter, lsr, dlsr]
E --> F[Compute RTT]
F --> G[Persist to TSDB]
G --> H[Grafana - ingress vs egress]
H --> I[Alert on egress > ingress + 1%]
CallSphere captures RTCP RR on both legs of every call across all six verticals. Our Pipecat-based media bridge runs alongside Twilio's edge; we parse RR every two seconds and persist into a per-call rtcp_samples table (one of 115+). The dashboard shows, per call, the receiver-reported loss and jitter - the metric the caller actually experienced. All 37 agents share the same observability path. Starter ($149/mo) gets aggregate RR stats; Growth ($499/mo) gets per-call drill-down; Scale ($1499/mo) gets RTCP-XR VoIP Metrics with R-factor MOS estimate. 14-day trial. Affiliates 22%.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
Why not just trust server-side stats? They show only what you sent. Receiver Reports show what arrived after carrier and last-mile. The two are different and the receiver number is the user experience.
Do I need RTCP-XR? For deeper analysis yes - VoIP Metrics Report Block adds discard rate, burst loss, R-factor, MOS-LQ, and signal/noise levels. If your endpoints support it, use it.
How often should RTCP fire? RFC default is roughly five seconds, but two seconds gives much better resolution for short glitches without significant bandwidth overhead.
Will Twilio send me RTCP for ingress? Twilio Voice Insights surfaces equivalent stats via API; native RTCP from Twilio's edge is not always exposed. Use Voice Insights as your "Twilio-side RR" source.
What is a healthy fraction_lost? Below 1% is excellent, 1-3% is acceptable, 3-5% is degraded, above 5% is broken. Twilio flags above 5% in their docs.
Start a 14-day trial, see pricing for RTCP-XR on Scale, or book a demo. Healthcare on /industries/healthcare gets 100% RR capture; partners earn 22% via the affiliate program.
RTCP Receiver Reports and Dashboards for AI Voice in 2026 forces a tension most teams underestimate: agent handoff state. A single LLM call is easy. A booking agent that hands a confirmed slot to a billing agent that hands a follow-up to an escalation agent — that's where context loss, hallucinated IDs, and double-bookings live. Solving it well means treating the conversation as a stateful workflow, not a chat.
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
The big fork is managed (OpenAI Realtime, ElevenLabs Conversational AI) versus self-hosted on GPUs you operate. Managed wins on cold-start, model freshness, and zero-ops; self-hosted wins on unit economics past a certain conversation volume and on data residency for regulated verticals. CallSphere runs hybrid: Realtime for live calls, self-hosted Whisper + a hosted LLM for async, both routed through a Go gateway that enforces per-tenant rate limits.
Latency budgets are non-negotiable on voice. End-to-end target is sub-800ms ASR-to-first-token and sub-1.4s first-audio-out; anything beyond that and turn-taking feels stilted. GPU residency in the same region as your TURN servers matters more than choosing a slightly bigger model.
Observability is the unglamorous backbone — every conversation produces logs, traces, sentiment scoring, and cost attribution piped to a per-tenant dashboard. HIPAA + SOC 2 aligned isolation keeps healthcare traffic separated from salon traffic at the storage layer, not just the API.
How does this apply to a CallSphere pilot specifically?
Real Estate runs as a 6-container pod (frontend, gateway, ai-worker, voice-server, NATS event bus, Redis) backed by Postgres realestate_voice with row-level security so multi-tenant data never crosses tenants. For a topic like "RTCP Receiver Reports and Dashboards for AI Voice in 2026", that means you're not starting from scratch — you're configuring an agent template that's already been hardened across thousands of conversations.
What does the typical first-week implementation look like? Day one is integration mapping (scheduler, CRM, messaging) and prompt tuning against your top 20 real call transcripts. Day two through five is shadow-mode running, where the agent transcribes and recommends but a human still answers, so you can compare side-by-side. Go-live is the moment your eval pass-rate clears your internal bar.
Where does this break down at scale? The honest answer: it scales until your tool catalog gets stale. The agent is only as good as the integrations it can actually call, so the operational discipline is keeping schemas, webhooks, and fallback paths green. The platform handles the rest — observability, retries, multi-region routing — without your team owning the GPU layer.
Want to see how this maps to your stack? Book a live walkthrough at calendly.com/sagar-callsphere/new-meeting, or try the vertical-specific demo at salon.callsphere.tech. 14-day trial, no credit card, pilot live in 3–5 business days.
Written by
Sagar Shankaran· Founder, CallSphere
Sagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
An honest 2026 guide to VoIP desk phones. Hardware vs softphone, top picks, when an internet phone is worth it, and where AI voice agents fit.
The best business phone app in 2026 is the one with an AI agent attached. Compare options, costs, and what an AI phone app actually does for a small business.
A founder's guide to business phone systems in 2026. Cloud vs on-prem, AI voice agents, small business pricing, and what actually works for under 100 seats.
MOS 4.3+ is the band where AI voice feels human. Drop below 3.6 and conversations break. Here is how to measure, improve, and alert on MOS in production AI voice using G.711, Opus, and the underlying packet loss / jitter / latency math.
Sentiment is not a single number per call - it is a curve. The shape (started positive, dropped at minute 4, recovered) tells you what your AI did wrong. Here is the per-utterance sentiment pipeline and the dashboards we ship by vertical.
Where every millisecond goes between caller and AI: PSTN, carrier, STT, LLM, TTS, and back. The component-level targets that ship in 2026 and how to hit them.
© 2026 CallSphere LLC. All rights reserved.