eastern-cyan•2y ago

voicemailDetectionEnabled not working?

I am making phone call requests with voicemailDetectionEnabled: true however I do not see any effect. I was expecting the endedReason in the End of Call Report to be voicemail but I receive customer-did-not-answer.
Using a twilio phone number. When using a Vonage phone number the ended reason is something like phone-call-provider-closed-websocket

12 Replies

Ask Inkeep•2y ago

Hi @darwin911, I'm an AI assistant for Vapi. I'll analyze available sources and get back to you shortly. ----------------------------- While I generate an answer, here are some sources that might be helpful: * List Calls * Get Call * Create Phone Call * Call Ended Reason -----------------------------

Ask Inkeep•2y ago

Answer Regarding the voicemailDetectionEnabled: true parameter not working as expected, there are several aspects to consider: 1. Voicemail Detection with Twilio: If you're expecting the endedReason to be voicemail but instead receive customer-did-not-answer, it suggests that the call was not detected as reaching a voicemail service. This can happen for various reasons, including network issues, the configuration of the called number, or the voicemail service not activating in time for the call detection mechanisms. Ensure that your settings for voicemail detection are correctly configured and that the called party's voicemail system activates promptly. 2. Issues with Vonage Number: The endedReason of phone-call-provider-closed-websocket when using a Vonage number might indicate connectivity issues between Vapi and the Vonage service. This error points to an interruption in the connection, possibly due to network issues, configuration errors, or limitations in the Vonage service handling the call (1) . To address these, ensure that your configurations for both Twilio and Vonage numbers are correct, including any relevant settings on the Vapi platform and within the Twilio and Vonage services themselves. For specific troubleshooting regarding connectivity with Vonage and the phone-call-provider-closed-websocket error, you may need to examine the network connection quality and configurations within your Vonage account. Unfortunately, the provided information sources don't directly address the issue of voicemailDetectionEnabled not working as expected. It's crucial to review the setup and configurations of your assistants and numbers in Vapi, as well as on the Twilio and Vonage platforms, to ensure they align with your call handling objectives.

Sources [1] Call Hangup with Ended Reason phone-call-provider-closed-websocket

ambitious-aqua•2y ago

Can you show the Twilio request logs so that I can help you with it?

eastern-cyanOP•2y ago

I do not have a twilio request log, I have a call id dd7cb0e0-9b07-4a15-97ea-7642cfa3fc2c Let me know if I can provide anything else to help

ambitious-aqua•2y ago

Did you buy the phone number from Vapi?

eastern-cyanOP•2y ago

No, it was imported into Vapi; I believe this number came with the current Twilio account. Would buying a number directly through Vapi improve voicemail detection?

ambitious-aqua•2y ago

Nope. It just that I would have directly checked your logs from my end. But, since you imported that twilio number from your side I don't have any access to it.

eastern-cyanOP•2y ago

We have a similar but different issue when using a Vonage number, also imported via Vapi API; the vonage number results in phone-call-provider-closed-websocket but based on quick research it seems that might be caused by latency in 11labs

ambitious-aqua•2y ago

I will confirm it with Nikhil once meanwhile the reason for hang is Possible Reasons for hang

- Lot of BG noise or foriegn language. Endpointing buffer resetted 27 times
- Known issue. 11labs slow in speaking foreign languages

- Lot of BG noise or foriegn language. Endpointing buffer resetted 27 times
- Known issue. 11labs slow in speaking foreign languages

eastern-cyanOP•2y ago

Thanks: here is the .wav file of the call in question: https://auth.vapi.ai/storage/v1/object/public/recordings/1714576337378-6829dacb-07fa-4dfe-849e-b6ed4d925286.wav

ambitious-aqua•2y ago

Okay. So, basically ended-reason as voicemail comes up only when you have set up a voice message otherwise it shows as customer-did-not-answer Also, we don't have any voicemail detection model we use twilio

eastern-cyanOP•2y ago

Ah ok that helps, thank you! Did not realize that voicemailMessage was required

voicemailDetectionEnabled not working?

Did you find this page helpful?