p
Hi! I'm experiencing audio quality issues during production calls that are impacting both the AI voice output and the user's audio capture. In some moments, the AI audio becomes distorted or cuts out, and the user’s voice is also affected, making the conversation difficult to follow. Call ID: 019be227-9d9a-7006-84a1-269bde24ed12 Timestamp of the issue: AI Error between 00:00:13 – 00:00:15 Could you please help investigate what might be causing this? Let me know if you need more logs or technical details. Thanks in advance!
v
To investigate the audio quality issue for Call ID
019be227-9d9a-7006-84a1-269bde24ed12
, start by reviewing the Call Logs in your Vapi dashboard:
1. Go to your dashboard and navigate to
Observe > Call Logs
. 2. Select the specific call and check the transcript and error messages around the 00:00:13–00:00:15 mark. This will help you pinpoint where the audio distortion occurred and provide clues for further troubleshooting. Let me know if you need help interpreting the logs or want to share more details! (Reference: Vapi [Debugging Guide](https://docs.vapi.ai/debugging)) Source: - [Debugging Guide](https://docs.vapi.ai/debugging)
j
Thanks for the details, audio cutting out on both sides usually points to network jitter, packet loss, or media stream instability. I’ll review the call segment you shared. Does this happen across multiple calls or just this one? Also, what telephony provider and audio codec are you using? @pedromacedol
p
Yes, this has been happening across multiple calls, not just this one. Our current configuration is: Telephony provider: Daily Transcriber: Deepgram (model: nova-2) Voice: eleven_multilingual_v2 (11Labs)
Other example: 019be1f7-8fe2-7ccb-9cc9-cb8a5699f1e9 (00:00:18–00:00:20) 019be1f6-8254-7112-a65c-f77257358375 (00:03:18 - 00:03:23) 019be241-ab6a-7006-84ce-2c5ae41be1bc (00:00:25–00:00:27)
@Vapi @User
o
Is this live calls or in the testing / vapi browser UI enviroment
p
Live calls
c
Hi Pedromacedol, thanks for sharing your details. Our team will look into it and get back to you soon with an update.
Hi, Here's my analysis: I'll classify this task and get the necessary context first. Task Classification: DEBUG - This is an investigation/analysis task ("debug this call"). Let me first fetch the Slack context to understand what needs to be debugged.Now I have the context. This is a DEBUG task involving: • 4 Call IDs to investigate: 1.
019be227-9d9a-7006-84a1-269bde24ed12
2.
019be1f7-8fe2-7ccb-9cc9-cb8a5699f1e9
3.
019be1f6-8254-7112-a65c-f77257358375
4.
019be241-ab6a-7006-84ce-2c5ae41be1bc
• **Issue reported**: AI audio became distorted or cut out, and user's voice was also affected • **Expected**: Clear, uninterrupted AI audio output and proper voice capture • **Timestamps of issues**: Various points in the calls (00:00:13–00:00:15, 00:00:18–00:00:20, 00:03:18–00:03:23, 00:00:25–00:00:27) Let me delegate this to the debug-agent:The debug-agent has completed the investigation. Here's a summary of the findings: Investigation Summary for VAP-11454 Root Cause Identified: Denoiser Pipeline Initialization Failure All 4 calls experienced the same core issue - the denoiser (audio noise filtering) component failed to initialize at call startup. This caused: 1. Raw unfiltered audio flowing through the system 2. Environmental noise affecting both directions - AI output AND user voice capture 3. Perceived "distortion" due to noise interference Additional Issues Found • ElevenLabs empty audio chunks - TTS provider returned silence (causing audio dropouts) • Deepgram audio drift warnings - Sync issues in speech recognition Recommendations 1. **Immediate**: Investigate denoiser service health during the affected time period 2. **Short-term**: Check ElevenLabs empty audio handling 3. **Long-term**: Implement graceful degradation if denoiser fails, add monitoring/alerts
p
Thanks! We’ll review the issues identified and share an update.
p
did you find any fix? i am getting same issues https://discord.com/channels/1211482211119796234/1468504819110252584
p
Hi @Pranav FE , we are investigating. In my case, most occurrences happen behind a restricted corporate firewall and/or when latency exceeds 2500 ms. I have already changed the ElevenLabs model to reduce latency, and I am waiting for the client's test before proceeding to the next step.
p
we tried similar stuff still nothing helpful came out. it is nothing from our en.. issue is entirely on vapi to daily end. check my thread above how you can prove it. you have to listen to both vapi's and daily's recording
p
I saw your report. Great work on the investigation, really well done. Quick question: where did you get access to the Daily recording?
p
you can enable video recording and in response you get daily's url where whole conversation is recorded in video format, its built in the box. we need to just get it from vapi's call api response