Skip to main content

SIP Capture Example - Knowledgebase / Audio, Call Quality and Network Search / Troubleshooting - Help & Support

SIP Capture Example

Authors list

SIP capture example

SIP Peering (or SIP Trunking) enables you to statically connect an IP-PBX with our public IP.

Note: 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 unauthorized 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 Peering: Routes all Inbound and Outbound traffic on an account to a single nominated WAN IP linked to one phone number.

  • Single: A single DID is linked to your nominated WAN IP.

In the example below, a primary trunk number is presented with your WAN IP (1310824005@ however an alternate outbound CLI is presented by the “Contact” (<sip:1310824005@>).

971abb63f1063bde6915a16f0dff8db2.pngSelect Switchboard.

  1. Select the phone number to set SIP Peering against.

  2. Select Preferences.

  3. Select SIP Peering.

  4. Click Enable SIP Peering.

  5. Add Primary Trunk Host IP Address, and failover Trunk IP Address (optional).

  6. Select SAVE.

Standalone Peering

A Standalone peer is where the network admin connects an IP-PBX to a single number. Standalone peering is a convenient mechanism enabling administrators to connect multiple offices each with its own WAN IP.

This use-case supports the scenario where the customer has multiple offices, each with its own IP-PBX and separate internet connections.

  1. Select Switchboard.

  2. Select Preferences.

  3. Select Line SIP Peering Standalone > Enable.

  4. Add IP Address.

  5. Select SAVE.


In this example, a subscriber has a centralized 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 individualized 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 formatted in the header below:

X-Billable-Party: 13108240011

Helpful Unhelpful