We are getting an increase in errors where it says...
# support
n
This is not an error on our side, everything seems to be working fine and most calls dialed to that number go through fine, however a few calls are dropped. This is somewhat intolerable on our side. Twilio logs show no problem with the numbers themselves, it appears to be an issue solely on the Vapi side. Can someone help us? Here's an example call ID where it happened: 019a31b6-6c4d-7223-84b2-f4f6c906b60a
v
To help escalate this issue, fetch the call details for the problematic call and include them in your support request. Use the following code snippet to retrieve the call information:
Copy code
bash
curl -X GET "https://api.vapi.ai/call/019a31b6-6c4d-7223-84b2-f4f6c906b60a" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"
Share the output and Call ID with Vapi support—they can investigate backend logs for this intermittent "twilio-reported-customer-misdialed" error, especially since Twilio logs show no issues and most calls succeed. Sources: - [Call ended reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Issue reporting](https://docs.vapi.ai/issue-reporting)
n
I sent this via email
c
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.
2 Views