I am trying to import a number (via dashboard) from Twilio and assign to an assistant, the number once assigned to the assistant is not connecting. Import completes successfully but no ringy dingy. I setup a qiick twml bin to test it and it works fine. If I add a number I procure from vapi everything works as it should... 70e7ed53-aeb2-4380-9086-f974ad2b8994 9e5aba8f-ff0f-4124-a54e-3d626b9a7525 70e7ed53-aeb2-4380-9086-f974ad2b8994 1c3825b9-5e99-4e38-9676-18255cbc8d0c Twilio config seems fine United States (US1) Region call routing is: Active Inbound call webhook is set to https://api.vapi.ai/twilio/inbound_call Call status changes to https://api.vapi.ai/twilio/status Any help here would be greatly appreciated.

@Snapsonic It sounds like you've done a thorough job of setting up and testing the integration with Twilio. Since the assistant works fine with a number procured from VAPI, but not with the imported Twilio number, there might be an issue with the configuration or routing on the VAPI side for the imported number. Here are a few steps you can take to troubleshoot the issue: 1. Double-check that the imported Twilio number is correctly assigned to the assistant with the ID

70e7ed53-aeb2-4380-9086-f974ad2b8994

. Ensure there are no typos or mismatches in the configuration. 2. Verify that the webhook URLs for inbound calls and status changes are correctly set up in Twilio and are pointing to the correct endpoints on the VAPI side. 3. Ensure that the Twilio number has the correct permissions and is active for making and receiving calls in the United States (US1) Region. 4. Check if there are any logs or error messages on the VAPI dashboard that could provide more insight into why the calls are not connecting. 5. If possible, test the Twilio number with a simple "Hello World" TwiML Bin to ensure that Twilio is routing calls to external URLs correctly. 6. Since the issue seems to be specific to the imported number, you may also want to review any differences in the configuration between the VAPI-procured number and the Twilio-imported number. If after these steps the problem persists, it might be necessary to look into more detailed logs or reach out to VAPI support for further assistance. If you would like me to assist you with any specific checks or configurations, please let me know, and I'll be happy to help.

Did all that, and still no luck.

@Snapsonic I apologize for the inconvenience you're experiencing. The endpoint you've mentioned,

https://api.vapi.ai/twilio/inbound_call

, seems correct based on the information you've provided. However, if the logs do not show the inbound call, it does suggest there might be an issue with the webhook configuration or network routing. Here are a few additional steps you can take: 1. Confirm that there are no typos in the URL you've set in Twilio's webhook configuration. 2. Make sure that the HTTPS certificate for

api.vapi.ai

is valid and not causing any issues with Twilio connecting to the endpoint. 3. Check if there are any IP whitelisting or firewall settings that might be blocking the webhook requests from Twilio to VAPI. 4. Use Twilio's debugger or logs to see if there are any errors on Twilio's side when attempting to send the webhook. 5. If you have access to the VAPI dashboard or any administrative tools, check if there's a way to verify the endpoint's availability or if there are any additional settings that need to be configured for the imported number. If you've confirmed all of the above and the issue still persists, it would be best to reach out to VAPI support directly for human intervention. They would have the necessary tools and access to investigate the issue further and provide a resolution. Would you like me to guide you on how to contact VAPI support or assist you with any other specific action?

yes, contact support

@Snapsonic I understand that you're encountering a 404 error when Twilio attempts to reach the VAPI inbound call endpoint. This indicates that the URL is not found on the server, which could mean there's an issue with the endpoint configuration on VAPI's side. Since this requires human intervention and access to the backend systems to resolve, I recommend reaching out to VAPI support directly. They will be able to look into the server configuration, verify that the endpoint exists, and ensure that it's correctly set up to handle incoming webhook requests from Twilio. Please provide VAPI support with the error details, including the Debug event SID, Timestamp, and the exact message you're receiving. This information will help them to diagnose the issue more quickly. If you need assistance with contacting VAPI support or if there's anything else I can do to help, please let me know.

@Sahil ^^ not sure if you are the guy but hoping you can help get this in front of whomever is the right guy

Can you send a call_id?

there is no call id because your webhook is 404

send me your account email address

thx for your help marking as solved, you might want to get dev to edit that import call and set the vapi api call to POST, just a thought.