Sip Trunking
  • 03 Aug 2021
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

Sip Trunking

  • Dark
    Light
  • PDF

Article Summary

Callable supports 2x mechanisms for sending/receiving SIP Trunk traffic, IP Authentication & Registration. Please refer to the getting started guides on how to build these call flows, this article refers to the client configuration.

IP Authentication

For the most majority of PBXs & SBCs communicating with Callable, they are able to receive traffic from multiple Callable SBCs. This allows us to provide diverse routing in each region.

Calls will be delivered from the following IP addresses:

Ireland

IPv4DNS
54.195.104.198eu-west-1.sbc-a.callable.io
54.74.169.84eu-west-1.sbc-b.callable.io
52.49.88.79eu-west-1.sbc-c.callable.io

US East

IPv4DNS
34.236.60.40us-east-1.sbc-a.callable.io
54.157.129.109us-east-1.sbc-b.callable.io

If your equipment can only accept from a single IP address, we recommend registration however if this is not possible, set voice cluster to "pluto", this will deliver calls from Ireland 54.169.84 and US East 34.236.60.40 only

Firewall Configuration

Individual configuration of firewalls is outside the scope of this documentation. If you do not use an SBC and require SIP traffic to traverse your firewall, please whitelist all IP addresses listed above and port forward UDP 5060 to your internal PBX IP address.

Registration

Registration allows for the most diverse routing, depending where you are situated globally. The domain you register against is determined by the account subdomain setting. For example, if you set the account subdomain to callablerocks then your domain will be callablerocks.connect.callable.io.

If you would like to know which SBC you are connecting to when registering, use the following command from (Windows) cmd prompt.

nslookup callablerocks.connect.callable.io

What's Next