----------------------------- **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.