https://vapi.ai/ logo
Join Discord
Powered by
TTS audio issue across all phone numbers in my org...
# support
v
Action Step: Please review the affected calls in your Vapi dashboard by navigating to 
Observe > Call Logs
. This will let you inspect the audio, transcripts, and any error messages for the first utterance, helping to pinpoint whether the issue is with TTS rendering or SIP delivery. If the problem persists across all providers and numbers, escalate by checking the [Vapi Status Page](https://status.vapi.ai/) and relevant provider status pages for ongoing incidents. This approach is recommended as the first step for systematic debugging of voice agent audio issues ([Vapi Debugging Guide](https://docs.vapi.ai/debugging)). Source: - [Debugging Voice Agents](https://docs.vapi.ai/debugging)
d
That definitely sounds like a platform-level TTS or call stream initialization issue especially since even Vapi’s own fallback audio is glitching on the first utterance. I’ve run into very similar “first packet/audio warmup” problems before and there are a few subtle fixes that usually resolve it cleanly. If you’re open, I can take a closer look with you and pinpoint exactly where it’s breaking. @BOBAGANOOSH
b
Sure. What would you need from me? Also there's a guy in here that sounds like he's scamming support tickets
m
Not really
d
To properly trace this, I just need one or two recent call IDs where the glitch happened, confirmation of which TTS provider is actually being used at runtime (not just configured), and whether you’re using streaming or buffered audio on Vapi’s side. With that, I can usually pinpoint if it’s a cold-start/audio chunking issue or something deeper in the SIP chain happy to dig in with you @User
b
Mod Anthony is sending a support ticket a discord and asking for defi wallets. Assuming that's not vapi
m
Are you new here.?
b
Yes
m
Well you should know about Mod Anthony
b
I don't. Again I'm new here
m
Okay
b
019d0332-3b42-711b-8944-1f9283024956 019d0330-b77c-711b-8920-4fa9b6f73f49
d
I sent a request
Perfect those call IDs help a lot. From what you described, this really looks like a classic first-chunk audio initialization issue I’ve seen it happen when the TTS stream hasn’t fully “warmed up” before playback starts, especially on SIP calls If you can confirm whether Vapi is sending audio as a live stream or waiting for the first buffer before playback and which TTS provider is actually hitting at runtime I can narrow it down pretty quickly and suggest a fix. @BOBAGANOOSH
b
Where can I find them at definitive answer for that. Sorry I'm still learning all this
d
I sent a message to your DM
You can usually confirm both from the Vapi dashboard: open one of those call IDs, check the logs/trace section, and look for the TTS events it should show the provider used and whether audio is being streamed in chunks or sent as a full response. If you want, you can share a screenshot or what you see there and I’ll help you interpret it.
b
I believe The logs show two ElevenLabs WebSocket connections opening simultaneously (websocketIndex 0 and 1) at timestamps 1773875117497 and 1773875117499 - within 2ms of each other. optimizeStreamingLatency is already set to 3 (maximum). Audio is being streamed in chunks via WebSocket, not buffered.
I can share the whole log. Is all just in testing right now
d
I replied already @BOBAGANOOSH
PreviousNext
Powered by