Hello @kruss6867
-
call_b4d92a48936d37a5427938c8b06 — last turn 5186ms e2e
Not jitter. Component timings on that turn are clean: LLM TTFT 550ms, LLM total 673ms, TTS first-byte 231ms, ASR 168ms → sum ≈ ~1.0s. The remaining ~4s is endpointing/VAD silence wait, not model/TTS/network. The caller trailed off with “Which is” at 45.7s and the agent didn’t commit the turn until 51.0s because VAD was waiting for the sentence to finish. Dashboard “Estimated Latency” doesn’t include this wait, which is why LLM/TTS look fine but e2e is long.
Your agent (v254) hasinterruptionSensitivity: 0.7and no explicitresponsivenessset — raisingresponsivenesswill shorten that silence gate. That’s the fix for this specific call, not TTS/LLM. -
call_a3b085e6ca755dfb5c1671099ef — audio glitching
This one IS a media-path issue — the caller himself says at ~63s “the audio packets are being lost… around 20–30 seconds it started to get really glitchy, I can only hear every third word.” That’s a downstream audio degradation, not endpointing. Voice provider wasplatform(retell-Marissa) on Telnyx. to move on this we need the PCAP + Telnyx-side leg metrics for that call.
Thank You