VAPI support BYOC on Twilio
# support
j
Does anyone know if VAPI support BYOC on Twilio?
v
message has been deleted
@jpcapelo Yes, VAPI does support Bring Your Own Carrier (BYOC) on Twilio. This allows you to use your own voice carrier with Twilio's infrastructure while leveraging VAPI's capabilities for voice application development. If you need assistance with setting up BYOC on Twilio or have any specific questions about integration with VAPI, please let me know, and I'll be happy to help!
You can continue this conversation by mentioning me in the message.
n
I'm faced with the same issue. From what I understand, BYOC means that you can point another carrier's numbers at Twilio without having to port them to Twilio. However, BYOC on Twilio does not seem to have any way (that I can see) to set up a number within their portal that another carrier owns. Within the VAPI dashboard, I cannot import the number because it does not exist within the Twilio Phone Numbers. We would need a way of adding these numbers we have via BYOC. We have BYOC set up and working correctly within Twilio, and we can see the inbound call in the Twilio logs, which sends the call to VAPI. How do we set this up in VAPI or Twillio?
s
You can do it via SIP Trunking but you need be on enterprise plan. @Norman @jpcapelo