This article provides steps on how you can Bring Your Own Carrier (BYOC) into Freshcaller.
Before proceeding, check if your carrier supports the following BYOC technical requirements.
Note: BYOC can only be configured if your carrier supports the following prerequisites.
Requirements for inbound BYOC:
- Check if your carrier supports SIP forwarding of incoming calls to SIP domains in the format number@[customer-name].sip.us1.twilio.com over the Public Internet.
- Check if your carrier supports G.711/μ-law or G.711/a-law codec for VOIP calls.
- Send us the list of IP addresses your carrier uses to send calls (SIP invite and media signals) so that we can whitelist them.
- Make sure your carrier sends the SIP invite in the format we send. You will receive a SIP domain in the format user@xyz.sip.twilio.com for each number that your carrier would need to send the SIP invite and media traffic.
Requirements for outbound BYOC:
- Check if the carrier can whitelist the list of IP addresses we send for uninterrupted connection and communication.
- As we do not support username/password authentication for outbound calls, check if the carrier can work without this.
- Send the SIP domain or IPs that will be used for forwarding outbound calls generated using Twilio's APIs sent from Twilio SBC.
We have the capability to forward outbound calls to multiple SIP domains or IPs. If there are two outbound SIP domains or IPs, then once SIP domain 1 (IP 1) is loaded with the maximum number of calls, calls will be forwarded to SIP domain 2 (IP 2).
Once the carrier has confirmed that they support the BYOC prerequisites, then please follow the below steps.
Configuring BYOC for inbound calls only
- Send the following details to numbers@freshcaller.com:
- The list of phone numbers you want to use in Freshcaller.
- The list of IP addresses that your carrier uses to forward the calls. These IP addresses will be added to our whitelist.
Once we receive the numbers, we will generate SIP domains 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 Freshcaller.After you receive the SIP domains, send the domains to your carrier so that they forward the calls to the right domains.
Ensure that your carrier supports G.711/μ-law and G.711/a-law codec for sending calls.
Configuring BYOC for inbound and outbound calls
Note: For inbound calls, make sure to send the details requested in the above section.
- Go to Admin Settings > Channels > Phone.
- Click Manage Numbers and choose Caller IDs.
- Click on the Add new caller ID option.
- Add the phone number with the country code as the 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 numbers@freshcaller.com. 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
The following table gives you the list of IP addresses that we recommend you to whitelist. However, you can choose to whitelist the IPs based on your preferred region to route calls. For example, if you want to route calls from North America Virginia region, you can choose to whitelist only the IPs and ports mentioned for that region and leave the rest.
For more information, refer to — https://www.twilio.com/docs/voice/api/sip-interface#sip-connection-technical-specifications
If you face any issues, reach out to numbers@freshcaller.com.
Note: If you are not familiar with whitelisting, contact your carrier for the same
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) |