https://vapi.ai/ logo
Join Discord
Powered by
Outbound calls successfully registered, then stuck...
# support
o
Hey support, this morning I had four calls scheduled to go out, and I received a success status for each request. However, three calls stayed in "queued" status and never went out to the customers. I've since made outbound calls successfully, so the issue seems to have been resolved, but those three calls still appear to be hung or stuck in that status. Is there a way to terminate the hung calls via the API so they don't go out? Or is that something that you can do on your end? The call ids are: - 0a35f501-0b9a-472b-9759-2b35a0a1f2f3 - 9a940534-c959-4346-b997-c50f10af3537 - 1159bf52-e75a-4e8b-bd1d-ed59fe3b5f8e I appreciate your help!
v
You can try terminating the calls by sending an 
end-call
message type within 
ClientInboundMessage
. According to the documentation, include a message with the 
type
property set to 
"end-call"
when sending inbound messages to the client:
Copy code
javascript
// Example of ending a call
{
  "type": "end-call"
}
If this doesn't work, please contact Vapi support at support@vapi.ai with the call IDs you provided, as they can directly help resolve calls stuck in the system. Sources: - [Terminating calls using ClientInboundMessage](https://docs.vapi.ai/changelog/2025/1/14) - [Contact Vapi Support for Assistance](https://discord.com/channels/1211482211119796234/1326262542858850445)
k
Looking into it 👀
For these shared call IDs, you never executed because the Twilio transport provider never connected with us. Using the Twilio call SID, you have to check with the Twilio team and then get back to us with their response so we can continue further investigation 🔵 13:07:16:855 Call 
0a35f501-0b9a-472b-9759-2b35a0a1f2f3
Waited 300s But Transport Never Connected. https://cdn.discordapp.com/attachments/1365703402146758657/1366350522948517908/image.png?ex=6810a096&is=680f4f16&hm=de7a834e3c5c8d7acbb512187265317016f6ecbd9e110a0787bd0159e3887233&
o
Thanks @Kings_big💫 - I had three more calls like that happen today. One of the calls (11572e10-665b-4c64-88f4-3a29ab91340e) gave me a "Twilio connection failed" error on the dashboard in the ended reason column. What I'm trying to figure out is if this is consistently a Twilio issue. If so, why do the other failed calls in the dashboard show 'unknown' and appear as queued in the API? Shouldn't we expect a consistent error?
@Kings_big💫 - I was able to sort out what the issues were for all of these hung calls - the one that returned the error in the dashboard was an error: "32017 - PSTN: Carrier blocked call due to calling number (caller ID)", the other unknown ones were error: "10004 - Call concurrency limit exceeded". It required me to verify my business profile to increase my concurrency limit. I hope closing the loop here helps others who might be new to the Twillio VAPI space. Hopefully, Vapi can integrate more useful error messages about why the calls fail. 🙂
k
Nice 😊 Thanks Oms
2 Views
PreviousNext
Powered by