https://vapi.ai/ logo
Join Discord
Powered by
VAPI Twillio Inbound connection hanging
# support
u
Inbound calls through twillio have started failing most of the time. Is the Twillio inbound degraded at the moment?
Im still having this issue? any idea? it was working fine earlier and seems to have gone to a degraded state again
@Vapi Support Bot
v
Thanks for your patience. To help diagnose the Twilio inbound connection issue, could you share any specific error messages or call logs you see when the inbound calls fail? This will help pinpoint whether it's a configuration or provider issue. If you have a recent error code or message (e.g., 
401 Unauthorized
, 
twilio-failed-to-connect-call
), please provide it for a more targeted solution. Let me know, and I can guide you through the next troubleshooting steps! Sources: - [Twilio SIP Integration Guide](https://docs.vapi.ai/advanced/sip/twilio) - [Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason)
u
Copy code
Twilio error (from the Twilio Debugger):
  ▎ - Error code: 11200 ("HTTP retrieval failure")
  ▎ - Request URL: https://api.vapi.ai/twilio/inbound_call (the default Voice URL set by VAPI on imported Twilio numbers)
  ▎ - Response headers:
  ▎   - x-envoy-upstream-service-time: 15002
  ▎   - x-twilio-reason: Request total timeout reached
  ▎   - x-twilio-webhookerror: 11203 HTTP communication total time out triggered
  ▎ - Response body: "Twilio was unable to fetch content from: http://api.vapi.ai/twilio/inbound_call. Error: Total timeout is triggered. Configured tt is 15000ms and we attempted 1 time(s)"
  ▎ - Example Twilio Alert SID: NO2ce3f0c3efb387ce466e7bbc3abc7044 (date 2026-06-01T20:33:04Z, Twilio CallSid CAfe82685c911e2b284a4849451cb76899)
  ▎
  ▎ VAPI error (from the corresponding VAPI call record):
  ▎ - endedReason: twilio-reported-customer-misdialed
  ▎ - startedAt: null
  ▎ - endedAt: null
  ▎ - messages: []
  ▎ - i.e. the call never started on VAPI's side because the /twilio/inbound_call response didn't complete within Twilio's 15s cap.
@Vapi Support Bot
v
Your Twilio inbound calls are failing because Twilio cannot reach the Vapi webhook within the 15-second timeout, resulting in the 
twilio-reported-customer-misdialed
error. To escalate this, copy your Call ID from the Vapi dashboard and send it to support for log investigation. Example:
Copy code
Call ID: [your-call-id-here]
Issue: Twilio inbound call times out (error 11200), Vapi call record shows 'twilio-reported-customer-misdialed'
This will help the support team quickly pinpoint the cause and assist you further. [More details here](https://docs.vapi.ai/issue-reporting) Sources: - [Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Issue Reporting](https://docs.vapi.ai/issue-reporting)
u
@Vapi Support Bot how do i communicate with the support team?
v
To contact the Vapi support team, send an email to 
support@vapi.ai
with your Call ID and a brief description of your Twilio inbound call timeout issue. Example:
Copy code
Subject: Twilio Inbound Call Timeout Issue

Call ID: [your-call-id-here]
Issue: Twilio inbound call times out (error 11200), Vapi call record shows 'twilio-reported-customer-misdialed'
This will help the support team investigate your logs and respond promptly. (Reference: Vapi support documentation at https://docs.vapi.ai/support) Source: - [Vapi Support Documentation](https://docs.vapi.ai/support)
c
Hey, Your setup is sending Vapi JSON event payloads back into https://api.vapi.ai/twilio/inbound_call, but that endpoint is only meant to receive Twilio’s inbound webhook payload. Because of that, Vapi is rejecting those requests with 400 Bad Request, which is why inbound behavior is breaking. The fix is to remove https://api.vapi.ai/twilio/inbound_call from any custom serverUrl/webhook configuration on your side and point those callbacks to your own endpoint instead. If you’re not intentionally using a custom server, removing that callback config should resolve it. let me know if it works Regards, Priyanshu
u
Ill give it a try and see. Only concern is that the issue is sporadic
I am not getting a 400 though?
Copy code
Twilio's call notifications also explicitly log HTTP 502 (not 400), and Vapi's own call records for the failed calls show:

    endedReason: call.in-progress.error-providerfault-transport-never-connected
Everything points to the fact that the apis are being throttled at peak hours. All calls going to vapi take exactly 27 seconds with twillios timeout being 15 hence the 'application error'
@User would appreciate some support here
c
Can you confirm Claro’s actual public signaling source IP and add it as a gateway with inboundEnabled: true? The IP in the SIP Via header may differ from the source IP reaching Vapi, which would cause the 401 Unauthorized. Please try this and let me know if it resolves the issue.
hey, There was an incident related to high DB read latency, causing call failures. It has been resolved. Now, let me know if you face this issue again
u
The issue is still there, can u just confirm if maybe there is some sort of throttling happening?
Twillio logs constantly say theres a timeout. The call goes through maybe 5 percent of the time
c
can you see the twilio logs + response timing?
Hi can you please share your call id, so we can investigate?
u
019e96c9-63bf-788d-8b27-6e53c9ca2e7f 019e96c4-7622-7000-8810-0061cbc9540e 019e96c1-a40b-733e-ab55-9156f62e4d41 019e96c1-9d1d-7aa8-86d4-b8e88155ee8a 019e96c0-e6c6-7bb2-8a71-5a5e59bd5024 019e96c0-df9e-7667-b6e2-35fd81331527
c
Hi, The call ended with the reason 
twilio-reported-customer-misdialed
, which means Twilio reported that the destination number was invalid or could not be reached. This is a Twilio-side issue rather than a Vapi issue. Please check the following: • Verify that the destination number is in the correct E.164 format (for example, 
+1XXXXXXXXXX
). • Confirm the number is valid by calling it outside of Vapi. • Review your Twilio Call Logs for more detailed error information. • Check for any typos, missing digits, or incorrect country codes. • Ensure the destination country/region is enabled in your Twilio geographic permissions. If the number appears correct and the issue persists, we recommend contacting Twilio support with the corresponding Twilio Call SID for further investigation. Thank you.
u
The twillio logs -> Twilio Notification on CallSid CAf32c2a503023bcfe8ca584105c52847a (verbatim from Twilio API): { "call_sid": "CAf32c2a503023bcfe8ca584105c52847a", "date_created": "Fri, 05 Jun 2026 07:52:13 +0000", "error_code": "11200", "message_text": "Msg=Got+HTTP+502+response+to+https%3A%2F%2Fapi.vapi.ai%2Ftwilio%2Finbound_call&ErrorCode=11200&LogLevel=ERROR", "more_info": "https://www.twilio.com/docs/errors/11200", "request_method": "POST", "request_url": "https://api.vapi.ai/twilio/inbound_call", "sid": "NO8c23e6afed440a29e41f2c81a00aeec8" } URL-decoded message: "Got HTTP 502 response to https://api.vapi.ai/twilio/inbound_call" --- Twilio Call record CAf32c2a503023bcfe8ca584105c52847a (relevant fields): { "sid": "CAf32c2a503023bcfe8ca584105c52847a", "direction": "inbound", "from": "+19292449735", "to": "+12065695133", "forwarded_from": "+12065695133", "date_created": "Fri, 05 Jun 2026 07:51:58 +0000", "start_time": "Fri, 05 Jun 2026 07:51:58 +0000", "end_time": "Fri, 05 Jun 2026 07:52:18 +0000", "status": "busy", "duration": "0" }
Also fro twilio
Copy code
{
      "request": {
          "method": "POST",
          "url": "https://api.vapi.ai/twilio/inbound_call",
          ...
      },
      "response": {
          "date_created": "Fri, 05 Jun 2026 07:52:13 +0000",
          "request_duration": 15011,
          "response_body": "Twilio was unable to fetch content from: http://api.vapi.ai/twilio/inbound_call\nError:
  Total timeout is triggered. Configured tt is 15000ms and we attempted 1 time(s)\nAccount SID: 
  AC89b9ff486a3e37831fa3017256484d4b\nSID: CAf32c2a503023bcfe8ca584105c52847a\n...\nRequest URI: 
  http://api.vapi.ai/twilio/inbound_call",
          "response_code": 502
      }
  }
c
For the call id's shared by you before. Please confirm if this error is for same for them? If yes please check the following: • Verify that the destination number is in the correct E.164 format (for example, 
+1XXXXXXXXXX
). • Confirm the number is valid by calling it outside of Vapi. • Review your Twilio Call Logs for more detailed error information. • Check for any typos, missing digits, or incorrect country codes. • Ensure the destination country/region is enabled in your Twilio geographic permissions. Also contact Twilio support with the corresponding Twilio Call SID for further investigation. Thank you.
PreviousNext
Powered by