SIP Peering

SIP Peering (also called SIP Trunking) enables you to statically connect your IP-PBX public interface (WAN IP) with our public IP while we inturn limit access to your nominated static IP.

NB – Peering differs from Registration which relies on an authenticated UserName, Password to connect to our voice proxy.

Once you have enabled SIP Peering we whitelist your WAN IP blocking any other IP from communicating with our Voice service. To harden your public IP address from unauthorised intrusion we advise restricting access to your SIP port to our public IP. See also Ports and IPs.

We support two modes of Peering:

  • Global: All Inbound and Outbound traffic is routed to a single nominated WAN IP
  • Single: A single DID is linked to your nominated WAN IP

Enabling a global SIP Peer

In this use-case a primary trunk number is presented with your WAN IP. If you want to present an alternate outbound CLI use the “contact” within your FROM (eg FROM: “61289707609” <sip: 61289707600@>). In this example the Trunk ID is 61289707600 while the CLI is 61289707609.

  1. Log into 2talk Cloud PBX.
  2. Select 2talk Cloud PBX > select number > Preferences > SIP Peering
  3. Click Enable SIP peering
  4. Add Primary Trunk Host IP Address, and failover Trunk IP Address (Note: this is optional)

Exception Route

An Exception Route covers the scenario where you have a main office holding the majority of phone numbers and a regional office with its own WAN IP. The Exception Route is therefore a convenient mechanism that enables you to attach an alternate Peering IP to that the regional office (for example).

Single Peers

This use-case supports the scenario where the customer has multiple offices, each with their own IP-PBX and separate internet connections. In this example you can optionally configure a single phone or group of phone numbers to point to the specified IP (see screenshot below).

  1. Log into 2talk Cloud PBX.
  2. Select Line Number Select > (hover over proposed Peering line)
  3. Add Primary Trunk Host IP Address, and failover Trunk IP Address (Note: this is optional)


In this example a subscriber has a centralised IP-PBX which itself hosts multiple customers. The requirement is to provide each customer with their own billing statement. In a SIP Peering environment the challenge is the Peer presents to our SBC using a single trunk number and doesn’t include the required billing detail.

While the customer could easily produce the individualised bills if using Registration the scalability advantages of SIP Peering mean the Service Provider would prefer to continue using SIP Peering as the connection type.

To use the X-Billable-Party the Service provider will configure their IP-PBX to pass the billable number formated in the header below:

X-Billable-Party: 61289707609

Was this article helpful?

Related Articles