SIP Trunking - Register Method

SIP Trunks that use the registration method require authentication from the pilot number on the trunk.

There are two steps to configure a SIP Trunk using the register method with 2talk

Step One: Inbound Trunking

By default inbound calls are delivered to a device which has logged in against that same number. However if you are using a PBX and need to register instead of peer with 2talk then you will need to use the Inbound Trunking setting.  This setting allows you to send inbound calls for this phone number to the registration or login of a different number on your account. By using this option you can create one or more inbound trunks for your incoming calls. If you enter a number here which is not on your account  this setting will  be ignored and removed. The number format should be the same as the registration ID. e.g. 092314357

Quick Guide

  1. Select CloudPBX | Inbound Calls > Call forwarding or trunking
  2. Select Inbound trunk number
  3. Log into each restricted line and use Inbound trunking to point each required line to your terminated trunk DID.

Step Two: Outbound Trunking

Outbound trunking is a feature that allows you to present other direct dial-in (DDI) numbers as Caller ID on your registered trunk relieving phone administrators the onerous task of individually registering large blocks of numbers to preserve CLI.

After you’ve enabled outbound trunking in the portal you can present another number on the account as your Caller ID by configuring your PBX to send the SIP headers described in the Registered Trunk section of 'SIP Trunking - Outbound Caller ID'. 

Quick Guide

  1. Select CloudPBX | Outbound Calls | Select Number >> Outbound Trunking
  2. Click Enable outbound trunking on the line you wish to configure as the accounts Outbound Trunk DID.
  3. Click Save settings to update.


  • Display name: Most devices such as soft phones and IP Phones refer to the name part as the Display name.
  • Asterisk based PBX systems the name part can be set in the SIP or IAX2 configuration with the callerid= field – or if you wish to present it in the dial plan then you use the CALLERID (name) variable. By changing this name part to the number you wish to present on the call you can achieve multiple caller ID presentations for each DDI over a single registration or login.
  • P-Asserted-Identity: see also a P-Asserted-Identity header (RFC 3325) to define the Caller ID as an alternate to manipulating the name field (subject to your system support for RFC 3325).