help , Inbound calls to my imported Twilio number ...
# support
f
Inbound calls to my imported Twilio number +447700100216 are failing with Twilio error 11200 — "Got HTTP 502 response to https://api.vapi.ai/twilio/inbound_call, total timeout 15000ms." My setup: number imported from Twilio, assigned to assistant "Inbound CRM Receptionist" (ID 9a552682-ec32-4be9-8420-df48cdb46b55). Twilio voice webhook correctly points to https://api.vapi.ai/twilio/inbound_call. Credits available (7+). Vapi status page shows all operational. I've tried deleting and re-importing the number, and removing all tools — still 502. A call DID work earlier today, then started failing. Twilio Account SID AC8812d52eadf62e215fd352461d15a26e. Can you check why my number's inbound calls are getting a 502 from your endpoint?
c
Thanks for reaching out about your SIP Trunking setup! You can find step-by-step troubleshooting help here: 👉 [Vapi SIP Trunking Guide](https://docs.vapi.ai/advanced/sip/sip-trunk) If that doesn’t resolve it, please reply with: • Your Call ID • The exact error message or behavior (e.g. 401 Unauthorized, timeout, etc.) • Whether it’s happening on inbound, outbound, or both trunks • Any recent configuration changes Once we have that info, we can help pinpoint the issue faster.
f
It's not SIP — it's a Twilio-imported phone number for inbound calls. • Call ID: CA4b9dd2d471f8cd87411925dc737dd4eb • Error: Twilio error 11200 — "Got HTTP 502 response to https://api.vapi.ai/twilio/inbound_call, total timeout 15000ms." Twilio waits 15 seconds, Vapi returns a 502, call fails before connecting. • Happening on: inbound only • Setup: Twilio number +447700100216 imported to Vapi, assigned to assistant "Inbound CRM Receptionist" (ID 9a552682-ec32-4be9-8420-df48cdb46b55). Twilio voice webhook correctly points to https://api.vapi.ai/twilio/inbound_call. Credits available. Vapi status shows all operational. • Recent changes: I deleted and re-imported the number, and removed all tools from the assistant — still 502. A call worked earlier today, then started failing with this 502. Can you check why inbound calls to this number get a 502 from your endpoint?
c
Hey, Direct imports sometimes aren't reliable can you configure to use via sip as per the docs here https://docs.vapi.ai/advanced/sip let me know if you are still facing any issue afer that