iSlinger
11/10/2025, 6:58 AMChiranjeet Mishra
11/10/2025, 6:59 AMVapi Support Bot
11/10/2025, 6:59 AMsip:YOUR_TWILIO_NUMBER@sip.vapi.ai as the origination URI in your Twilio SIP trunk, or are all numbers pointing to the same SIP URI? This detail will help determine if routing issues are due to URI configuration.
Source:
- [Twilio SIP Integration with Vapi](https://docs.vapi.ai/advanced/sip/twilio)Vapi Support Bot
11/10/2025, 7:24 AMiSlinger
11/10/2025, 7:55 AMVapi Support Bot
11/10/2025, 7:57 AMbash
curl -X POST "https://api.vapi.ai/phone-number" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_VAPI_API_KEY" \
-d '{
"provider": "byo-phone-number",
"name": "Twilio Number 1",
"number": "YOUR_TWILIO_NUMBER",
"numberE164CheckEnabled": false,
"credentialId": "YOUR_CREDENTIAL_ID"
}'
This ensures each number routes correctly—no need for separate SIP trunks per number. Make sure your Twilio origination URIs match the format sip:YOUR_TWILIO_NUMBER@sip.vapi.ai for each number.
Source: [Twilio SIP Integration with Vapi](https://docs.vapi.ai/advanced/sip/twilio)iSlinger
11/10/2025, 7:59 AMVapi Support Bot
11/10/2025, 8:02 AMbash
curl -X POST "https://api.vapi.ai/phone-number" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_VAPI_API_KEY" \
-d '{
"provider": "byo-phone-number",
"name": "Twilio Number 1",
"number": "YOUR_TWILIO_NUMBER",
"numberE164CheckEnabled": false,
"credentialId": "YOUR_CREDENTIAL_ID"
}'
Make sure your Twilio SIP trunk's origination URIs are set to sip:YOUR_TWILIO_NUMBER@sip.vapi.ai for each number—this will route inbound calls correctly to Vapi.
Source: [Twilio SIP Integration with Vapi](https://docs.vapi.ai/advanced/sip/twilio)Chiranjeet Mishra
11/12/2025, 7:44 PMiSlinger
11/23/2025, 11:06 AMChiranjeet Mishra
11/26/2025, 4:36 AM