Any fix for this ? seems to be happening during and after the recent outage @Vapi @Vapi Incident @Vapi Support Bot

Thanks for reaching out! To help diagnose the issue with inbound Twilio calls not reaching your voice agent, could you confirm if your Twilio SIP trunk's Origination settings include the correct Vapi SIP URI and that both Vapi static IPs (

44.229.228.186

and

44.238.177.138

) are whitelisted as described in the [Vapi Twilio SIP integration guide](https://docs.vapi.ai/advanced/sip/twilio)? This will help narrow down whether the problem is related to configuration or something else post-outage. Source: - [Vapi Twilio SIP integration guide](https://docs.vapi.ai/advanced/sip/twilio)

@Vapi Support Bot Yes they are whitelisted

Thanks for confirming that the Vapi static IPs are whitelisted. Since the configuration appears correct on your end, and this issue started during or after the recent outage, it may be helpful to double-check if your Twilio SIP trunk's Origination settings are still pointing to the correct Vapi SIP URI, as outages can sometimes cause settings to revert or require re-saving. If everything looks correct and the issue persists, there may be a temporary disruption or a need to refresh the connection between Twilio and Vapi. Unfortunately, I do not have additional troubleshooting steps based on the information I have found. If you have any more details about error messages or call logs, feel free to share them, and I can help look into it further.

The origination settings are pointing to sip.vapi.ai . No recent configurations have been changed on Twilio side @Vapi Support Bot

Thanks for confirming that your origination settings are pointing to sip.vapi.ai and that no recent configurations have been changed on the Twilio side. Since the static IPs are also whitelisted and the configuration appears correct, it sounds like you've already covered the main setup steps. Based on the information I have found, I do not have additional troubleshooting steps to suggest at this time. If you have any specific error messages or call logs, sharing those details could help narrow down the issue further.

could you please confirm if your calls are working now?