Note: If you have signed up for your account after 24 April 2023, please visit the following article: What is Bring Your Own Carrier (BYOC)?
Prerequisites (mandatory to receive inbound calls)
- Send the list of numbers you want to use in the web application to [email protected].
Once we receive the numbers, SIP domains will be generated to identify each number.
For example, if your phone number is "xxx", your SIP address will be sip:user@xxx-sip.twilio.com. The SIP address ensures that the calls are forwarded to the web application. Once received, you can route these calls to your agents/teams.
Once you receive the SIP domains, you can send the domains to your carrier to ensure that your carrier forwards the calls to the right domains.
- Also, send the list of IP addresses that your carrier uses to forward the calls. This will be added to our whitelist.
Ensure that your carrier supports G.711/μ-law and G.711/a-law codec for sending calls.
Steps to configure BYOC for inbound and outbound calls
Note: For inbound calls, ensure to send the details requested in the above section.
Follow all the steps stated above for routing inbound calls. In addition to that,
- Log in to your web application.
- Go to Admin Settings > Channels > Phone > Phone Numbers and click on Manage caller IDs.
- Click on the Add new caller Id option and add the phone number with the country code as caller ID. For example, +1xxxxxxxxxx.
- You will receive a call to verify the phone number. The verification call is mandatory to ensure that the external number belongs to you.
- Once your number is verified, you can use it as your caller ID.
- Send the details of SIP URI or IP provided by your carrier for each number to [email protected]. Your carrier may provide one or more SIP URIs for a single number. If there are multiple SIP URIs, specify the priority order provided by the carrier with a range of 0 to 65535.
Firewall Restrictions - Whitelisting IP
If you currently have a firewall or any network restrictions, ensure that you whitelist the following IPs. For more information, refer to — https://www.twilio.com/docs/voice/api/sip-interface#sip-connection-technical-specifications
If you face any further problems, reach out to [email protected].
Region | Signaling IPs | Media IPs |
---|---|---|
North America Virginia | 54.172.60.0 to 54.172.60.3 Ports: 5060 (UDP/TCP), 5061 (TLS) | 54.172.60.0/23 34.203.250.0/23
|
North America Oregon | 54.244.51.0 to 54.244.51.3
| 54.244.51.0/24
|
Europe Ireland | 54.171.127.192 to 54.171.127.195 Ports: 5060 (UDP/TCP), 5061 (TLS) | 54.171.127.192/26 52.215.127.0/24 Port Range: 10,000 to 20,000 (UDP) |
Europe Frankfurt | 35.156.191.128 to 35.156.191.131 Ports: 5060 (UDP/TCP), 5061 (TLS) | 35.156.191.128/25 Port Range: 10,000 to 20,000 (UDP) |
Asia Pacific Tokyo | 54.65.63.192 to 54.65.63.195 Ports: 5060 (UDP/TCP), 5061 (TLS) | 54.65.63.192/26 Port Range: 10,000 to 20,000 (UDP) |
Asia Pacific Singapore | 54.169.127.128 to 54.169.127.131 Ports: 5060 (UDP/TCP), 5061 (TLS) | 54.169.127.128/26 Port Range: 10,000 to 20,000 (UDP) |
Asia Pacific Sydney | 54.252.254.64 to 54.252.254.67
| 54.252.254.64/26 Port Range: 10,000 to 20,000 (UDP) |
South America Sao Paulo | 177.71.206.192 to 177.71.206.195 Ports: 5060 (UDP/TCP), 5061 (TLS) | 177.71.206.192/26 Port Range: 10,000 to 20,000 (UDP) |