Outbound calls kept getting hung up after approximately 10 seconds and then updated on vapi platform with 'customer didnt answer' status with this specific voicemail detection. When switching to twilio it fixed the error. Might want to look into this

Hi there! 👋 I understand you're experiencing an issue with Google Voicemail Detection where outbound calls are being hung up after about 10 seconds and marked as "customer didn't answer" on the Vapi platform. You're right that this is something we should look into, and I appreciate you bringing it to our attention! While I can't pinpoint the exact root cause of this specific error without more details, I can definitely help explain some potential causes and solutions based on similar issues we've seen. Several factors could be causing this behavior with Google Voicemail Detection: 1. **Configuration Settings**: The voicemail detection parameters might need adjustment. Parameters like

machineDetectionSilenceTimeout

,

machineDetectionSpeechThreshold

, and

machineDetectionSpeechEndThreshold

can affect how the system detects voicemail and when it decides to hang up a call. [According to our documentation](https://docs.vapi.ai/phone-calling/voice-mail-detection), these settings may need fine-tuning for optimal performance. 2. **Endpointing Behavior**: The endpointing feature in Vapi uses audio-text models to determine when a user has finished speaking. If these settings aren't configured optimally, it might lead to delays in recognizing silence, affecting the hang-up behavior. [This has been noted in previous similar cases](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344633027925377064). 3. **Sensitivity Issues**: The system might be misinterpreting transfer beeps as answering machines. [Some users have reported](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342302988709924865) that disabling the "machine_end_beep" setting resolved similar problems. As for why switching to Twilio fixed the issue, there are a few possible explanations: 1. Twilio's voicemail detection might have different default sensitivity settings that work better with your specific call flow.

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

Sorry shub I don't have those informations anymore. Call ID - n/a when - n/a (couple days ago when i submitted) Response expected - N/A Response Got - phone call got hungup 5x in a row with the stamp 'customer didnt answer'

Marking this ticket as Solved ✅