Vapi ends call during conversation with endedReaso...
# support
I have implemented a Vapi agent that makes outbound calls. Out of around 40 calls, two calls have suddenly ended in the middle of the conversation. Both times, endedReason is "customer-did-not-answer" (which is usually the endedReason if the customer does not answer the phone). Both times, is has happened with Singaporean Numbers (it never happened with european numbers).
Hi @Max28, 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**: * [Create Phone Call]() * [Call Ended Reason]() * [List Calls]() * [Get Call]() -----------------------------
### Answer The "customer-did-not-answer" endedReason you're encountering, especially in the context where conversations have already started, sounds unusual and not directly related to the typical scenario described by this termination reason. The documentation for Vapi provides various reasons for call termination, including "customer-did-not-answer," which implies that the called party didn’t answer the call [(1)]() . However, your situation, where calls are ending during a conversation with this reason, doesn't match the documented scenarios. Considering the specific context with Singaporean numbers, this might suggest a region-specific issue or an anomaly in how call statuses are being interpreted or reported. It's important to ensure that the implementation correctly handles different call events and that there hasn't been an oversight that could lead to misinterpretation of call statuses. Unfortunately, without more detailed logs or specific cases to analyze, it's challenging to provide a pinpoint solution. The information provided in the available documentation does not cover anomalies or exceptions that could lead to this behavior during an ongoing conversation. If the issue persists, it might require a more detailed investigation into the call logs or seeking direct assistance from Vapi's technical support for a deeper analysis, considering this behavior might be affected by regional telecommunication nuances or specific handling by the Vapi platform.
call id: faabc001-9333-443c-be66-9dffe28380a5
Vapi detected that call as "AnsweredBy":"machine_end_other". Disable this option you won't face this issue even it will be detected as machine the conversation will keep going on
turned it off, thanks! 🙂
Let me know if you still encounter this issue.
@Sahil I believe we are still encountering this issue, even with
voicemailDetectionEnabled: false
cc @jeffwinkle
Can you send me your call_id or something so that I can verify it?