Failed calls with no errors
# support
m
I'm seeing an issue where callers to my twilio number connected with vapi are getting call failed with two beeps after a few rings and being hung up on. the issue is transient. In the vapi logs I have a recording of my assistant saying the first message and I see the call end with "customer-ended-call". I don't see any errors in vapi or in twilio but I realize customers have being getting hung out on for the past few weeks. please help me debug.
v
To debug this issue, start by reviewing the detailed call logs in your Vapi dashboard under Observe > Call Logs. Look for the specific call IDs where the problem occurred and check for any disconnect events, webhook failures, or unexpected status changes. If nothing stands out, enable webhook and API logging for deeper insight, and consider sharing a problematic call ID with Vapi support for further investigation. Tip: Use the following cURL command to fetch call details for a specific call ID:
Copy code
bash
curl -X GET "https://api.vapi.ai/call/{call_id}" -H "Authorization: Bearer YOUR_API_KEY"
[More on debugging calls](https://docs.vapi.ai/debugging) Source: - [Debugging voice agents](https://docs.vapi.ai/debugging)
m
call ids 019a2d21-73c8-7aa1-9346-fa27efb297f4 019a2d19-2b84-755b-a79e-e7c99424a5d7 019a2d13-2085-722c-b947-554d1480e160
"customer-ended-call" but customer never actually connected.
c
Hi mike, It seems you're encountering issues with call transfers. To effectively troubleshoot, consider these steps: 1. Verify Forwarding Initiation: - Check if Vapi successfully initiated the forwarding by examining the call's
endedReason
. If it's
"assistant-forwarded-call"
, the forwarding was initiated correctly. 2. Configuration Check: - Ensure that
serverMessages
in your assistant configuration excludes
"phone-call-control"
unless using custom logic. - Set
phoneCallProviderBypassEnabled
to
false
for standard Vapi forwarding management. 3. Provider's Dashboard Verification: - Check your telephony provider's logs using the
phoneCallProviderId
to see if any errors occurred during the transfer. 4. SIP Trunk Check (if applicable): - Use Wireshark to capture and analyze SIP packets to confirm if the REFER request was sent. Look for errors if the transfer wasn't accepted. 5. Common Solutions: - Ensure the destination number is correct and calling it directly works. - Check for call blocking or configuration inconsistencies. For detailed guidance on each step, refer to the [Debug Call Forwarding Drops guide](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops).
m
hmm there were transfers on the call this happens before the customer even joined the call
they never actually join the call
I first started seeing this issue while providing hooks to the assistant to end the call based on customer not speaking how can I see if the hooks are causing this?
c
Thanks for the call ids. We are reviewing the details of your request and will reach out to you when we have an update or if we need additional information.
3 Views