Outbound calls fail with customer-did-not-answer r...
# support
m
When performing outbound calls, 2 calls failed with ended-reason
Customer Did Not Answer
. Here are the call ids:
Copy code
04e3a08f-bdee-41a6-a55f-ded7ef164919
c1e650f3-57ad-4b27-b361-db7c6663260a
It's sent from a twilio number from customer so I don't have access to twilio logs. Can you give me the real reason of the error?
v
I understand you're looking for the specific reason behind those failed outbound calls. Since these calls were made through a Twilio number that you don't have access to, I can't determine the exact cause without the Twilio logs for those specific call IDs. I've escalated your query to our technical support team who can help investigate these specific call failures in more detail. They may reach out for additional information to help diagnose the issue. While we wait for their response, there are several common reasons for the
Customer Did Not Answer
error, including voicemail detection issues, telephony handshake problems between Twilio and Vapi, network connectivity issues, or incorrect AMD (Answering Machine Detection) settings. In some cases, a very low
machineDetectionTimeout
setting can cause legitimate calls to be cut off prematurely. Our team will get back to you soon with more specific information about your call IDs. 👍
k
Maybe the customer didn't answer?
m
I don't know, In that case that would go to voicemail instead, no? Or you mean some customers don't have voice mail?
Sorry, seems good, We manually called back these 2 numbers and none of them have a voicemail. thanks @kolbykskk for the insight, it was so obvious we did not thought about it 😅
s
Marking this ticket as Solved ✅