Something is certainly wrong today. I've never had only Customer Did Not Answer results coming for all of my outbound calls. Using Twilio for my outbound numbers. I do see one error in my Twilio account: Message Request to https://api.aws-us-west-2-backend-production1.vapi.ai/twilio/status timed out

Thank you for sharing the details. To help narrow down the cause, could you confirm if you have recently changed any Twilio webhook URLs or Vapi configuration before these "Customer Did Not Answer" results and timeout errors started appearing? Sources: - [Call ended reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management) - [Vapi outbound call not triggering (Discord)](https://discord.com/channels/1211482211119796234/1372358449761091584)

Might be able to help with this, kindly provide me with your location.

The only thing that changed was moving to an elastic SIP with Twilio, but I did test calls without issue before resuming volume today.

Suggestion: Please double-check your Twilio Elastic SIP trunk configuration—ensure that the termination SIP URI is set correctly and that Vapi's static IPs (

44.229.228.186

,

44.238.177.138

) are whitelisted in your Twilio trunk settings. Also, verify that your webhook URLs in Twilio point to the correct, publicly accessible endpoints and are not being blocked by a firewall. If you recently changed to Elastic SIP, a misconfiguration here is a common cause of outbound call failures and timeouts. Example:

plaintext
Twilio Console > SIP Trunks > [Your Trunk] > Termination > Allowed IP Addresses: Add Vapi IPs

For more details, see the [Twilio SIP Integration guide](https://docs.vapi.ai/advanced/sip/twilio). Source: - [Twilio SIP Integration](https://docs.vapi.ai/advanced/sip/twilio)

@Vapi Support Bot I verified those are whitelisted as I did follow the guide when setting up.

Thank you for confirming that the Vapi IPs are whitelisted and that you followed the setup guide for your Twilio Elastic SIP trunk. Since you mentioned that test calls worked before resuming higher volume, and you are now consistently seeing "Customer Did Not Answer" results along with a timeout error, this suggests the core configuration steps have been addressed. Based on the information I have, there are no additional troubleshooting steps or specific causes identified beyond what has already been discussed. If you have already verified the SIP trunk settings, whitelisted IPs, and webhook accessibility, and are still experiencing the issue, I do not have further details available at this time. If you have any new symptoms or error messages, please share them, as that could help narrow down the cause. Otherwise, I do not have more information to provide right now.

Do you really want some human help at all?

Hey! To help track down this issue, could you share: \- The call ID \- When exactly this happened (the timestamp) \- What response you expected to get \- What response you actually got instead This would really help us figure out what went wrong!

Just got this back from Twilio today: "I can see these calls are not passing Via our Elastic Sip trunk". I'm attaching yesterday's calls which I stopped once I saw they were all going the same way. https://cdn.discordapp.com/attachments/1423688116367003668/1425199075476635870/Yesterdays-Calls.xlsx?ex=68fa7e12&is=68f92c92&hm=3bed7985486669763f5a93a97cc7aece08d804425ff6a93415dd62d82ad3a99d&

I could provide you with solutions on this: Provide me the following to begin with 1. Sip Provider Name 2. Phone Number ID 3. Vapi Assistant ID Lets begin working from there.

Were you able to look at my logs I attached yesterday?

We are currently reviewing the details of your request. Thank you for sending the logs

Thanks, Kyle. I wonder if it has anything to do with me importing the numbers from Twilio and using them for a while before I created the Elastic SIP in Twilio.

Hey, Would you be available to schedule a brief call at your earliest convenience so that we may discuss this matter in detail? Please use the following link to book a suitable time:

Kyle, I got the calls working today for outbound by adding the SIP and numbers via the API, but apparently I need to add an IP for inbound to work. Twilio is unsure what IP address is it Vapi could be wanting.

You will need to use the IP address of the termination SIP URI that you define after you have created an elastic SIP trunk on Twilio. To find that IP address, just use terminal or command prompt to ping your SIP URI and it will give you an IP. Make sure when you create the elastic SIP trunk in Twilio to add the IP addresses to whitelist as the IP access control lists under the authentication section. Also set your origination SIP URI to

sip:+1xxxxxxxxxx@sip.vapi.ai

and replace the +1xxxxxxxxxx with the phone number you associate the SIP Trunk with on Twilio. If you need additional assistance setting this up, feel free to add some time on my calendar