https://vapi.ai/ logo
Join Discord
Powered by
BYO SIP - direct extension dial
# support
j
I have setup a BYO SIP successfully and my SIP provider is properly receiving the dial numbers. I am using VAPI to dial internal extensions direct but VAPI forces me to enter the phone number in the E.164 format. Is there a way to bypass this? My extension numbers are 9 digits long
When I try and enter an extension number to dial I get a Outbound Call Failed message
v
Hi there! 👋 I understand you're trying to dial 9-digit internal extensions directly through VAPI, but you're running into the E.164 format requirement. While I don't have a guaranteed solution, I can share several potential approaches that might help bypass this requirement. Here are some possible ways to bypass the E.164 format requirement in VAPI: 1. **Disable E.164 Check**: According to [Telnyx documentation](https://docs.vapi.ai/advanced/sip/telnyx), you can set the 
numberE164CheckEnabled
parameter to 
false
when creating a phone number associated with a SIP trunk:
Copy code
curl -X POST https://api.vapi.ai/phone-number \
        -H "Content-Type: application/json" \
        -H "Authorization: Bearer your-vapi-private-api-key" \
        -d '{
            "provider": "byo-phone-number",
            "name": "Telnyx SIP Number",
            "number": "your-sip-phone-number",
            "numberE164CheckEnabled": false,
            "credentialId": "your-new-trunk-credential-id-which-you-got-from-previous-step"
        }'
2. **Use SIP URIs for Call Transfer**: When creating a tool to transfer a call, you can specify the extension directly and disable the E.164 check as shown in [this Discord post](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339709058587820132):
Copy code
curl -X POST https://api.vapi.ai/tool \
        -H "Authorization: Bearer " \
        -H "Content-Type: application/json" \
        -d '{
     "type": "transferCall",
     "function": {
       "name": ""
     },
     "destinations": [
       {
         "type": "number",
         "number": "insert-number-here",
         "extension": "insert-ext",
         "numberE164CheckEnabled": false
       }
     ]
   }'
3. **Use a Tech Prefix**: With providers like Telnyx, you can use a tech prefix to format phone numbers without the '+' sign, effectively bypassing the E.164 format according to [Telnyx documentation](https://docs.vapi.ai/advanced/sip/telnyx). 4. **Use the Format Plan**: The Format Plan allows you to customize how numbers are formatted when spoken, including converting E.164 format to a local format as mentioned in [this Discord post](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342514332604432424). 5. **Send Call Requests to a Webhook**: According to [Telnyx documentation](https://docs.vapi.ai/advanced/sip/telnyx), you can configure VAPI to send call requests to a webhook instead of an assistant, potentially allowing you to handle the dialing logic outside of VAPI's standard E.164 requirement. I recommend testing these different approaches to see which one works best for your specific setup with 9-digit internal extensions. Would you like me to elaborate on any of these potential solutions? Sources: - [Telnyx documentation](https://docs.vapi.ai/advanced/sip/telnyx) - [Discord post about transferCall tool](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339709058587820132) - [Discord post about Format Plan](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342514332604432424)
j
Disabling the e.164 check did it …. Thank you👍
a
checking if this is resolved/solved for you?
j
this was resolved
thank you
a
Marking this ticket as Solved ✅
11 Views
PreviousNext
Powered by