SIP Outbound byo-phone-number - Not e164
# support
f
I followed the [SIP Outbound Guide](https://relieved-yuzu-73a.notion.site/SIP-Outbound-Guide-997d66df35284295b7149fc10c82f3e8) But this doesn't work with Twilio, as far as I can tell. When creating a call for a "byo-phone-number" type. The to URI in is an 11 digit phone number instead of an e164 number. This doesn't work with SIP trunks like Twilio: The attached image is the error log from twilio for a call initiated by VAPI using a "byo-phone-number" configured for a twilio SIP trunk. https://cdn.discordapp.com/attachments/1330942465531969546/1330942465724645497/image.png?ex=678fd043&is=678e7ec3&hm=1e4354677a4cfd3534c9bd0945e175990f3e073a7ed3b1817785673fbd888914&
v
message has been deleted
You can continue this conversation by mentioning me in the message.
@falseVacuum I'm sorry to hear that you're experiencing issues with integrating Twilio SIP trunks with our BYO-phone-number feature. It sounds like the format of the phone number might be causing the problem. Twilio typically requires phone numbers to be in E.164 format, which includes the country code and is formatted like
+1234567890
. To resolve this issue, please ensure that when you're setting up the call with VAPI, you format the 'to' URI with the E.164 number format. If you've already done this and are still facing issues, it might be necessary to review the configuration on both VAPI and Twilio to ensure they are compatible. If you need further assistance with the configuration or if there's anything specific you'd like me to do to help you with this integration, please let me know! If the issue persists, I would recommend reaching out to support for more detailed guidance.
f
@Vapi When I create the call in the vapi API via
/call
, I am using the e164 version of the number. VAPI seems to be stripping the "+" before sending it to the SIP trunk.
v
@falseVacuum It seems like there might be an issue with how the VAPI is handling the number formatting when interfacing with the Twilio SIP trunk. The '+' symbol is crucial for E.164 formatting, and if it's being stripped out, that could indeed cause the call to fail. To address this, please double-check the configuration on the VAPI side to ensure that the '+' is not being removed when the call is initiated. If the configuration appears correct and the issue persists, this may require further investigation by our support team. If you need me to assist you with checking the configuration or if there's any other action you'd like me to take, please provide me with the necessary details. Otherwise, if this is a technical issue that requires a deeper dive, I would recommend contacting our support team for a more thorough resolution.
s
@falseVacuum could you share the phone number id so I can take a look?
4 Views