The Trunks feature allows you to forward calls made to an Account to a specified path (IP based forwarding).


The trunk may be triggered in two call scenarios:

  1. Call from a DID number to the number registered on the Account device. This is the scenario when a call arrives from a DID number (in the DID Pool section) and the softswitch routes it to the registered account. The web GUI has an option inside Incoming Routing that allows you to forward calls from a DID number to the number selected in the Incoming Routing section of the Account TRUNK/PBX server

  2. When an Onnet call (e.g. from Account to Account) arrives on an Account and the system routes it to a specified Trunk 


Use of fields on the Trunks page:

  • Main Destination - the main field on the Trunks page that requires input of the IP address (or hostname) of the system where the calls will be forwarded

  • Main Username/Main Password - enter the appropriate information needed for digest authentication (in case your Trunk requires it). "Main" means that the system will attempt it for the "Main destination"

  • Backup Destination - the backup IP that may be attempted if the "Main Destination" is unreachable or if a 5xx error is received

  • Outbound CLD - optional parameter that gives you the ability to convert/translate the incoming CLD into some other number

  • Main Outbound IP - specify the appropriate IP address from the list of IPs assigned to your environment. Thus, Sippy would route SIP requests to the Trunk via the selected IP. It is useful when your PBX demands an exact IP for the authentication of traffic from Sippy

  • Backup Outbound IP - specify the appropriate IP address from the list of IPs assigned to your environment. Thus, Sippy would route SIP requests to the Trunk via the selected IP if the "Backup Destination" is triggered

  • From Domain - changes the IP address in the "From" header field of the INVITE request (made to a PBX/vendor) to a domain name  

  • Random Call-id - optional setting that will allow outbound call IDs to be randomized.  This prevents PBX/vendor from seeing the IP addresses when UAs include them in the call IDs


How to setup a Trunk:


1) Open the Accounts page and press the drop-down "Action" menu (see screenshot below):

2) Select the Trunks sub-menu (marked as 2 on the screenshot)


3) On the opened Trunks page, press the "Add New" button to create a new Trunk:


4) Fill-in at least the following fields: Name, Main Destination 

Or fill-in all fields with your information following the format used in the screenshot below (description for each field see at the top of the page)


Don't forget to fill-in "Main Username" and "Main Password" if digest authentication is required on the Trunk's end.


Scenario #1: Onnet calls -> Trunk


When the Trunk is created, open the "Incoming Routing" page (marked as 3 on the "How to set up a Trunk" screenshot)  and select the Trunk required for the Source: On-Net Calls (as shown below):

FWD DID Mode is not compatible with the configuration above and will not work


The Self Managed checkbox permits the management of Trunks on the Account's web self-care interface 

So, end-users/Accounts may Route all incoming On-Net calls that arrive on the Account to the desired Connection.



Click on the diskette icon to apply routing changes (see the screenshot above).



Scenario #2: DID -> Trunk


When the Trunk is created, open the "Incoming Routing" page (marked as 3 on the "How to set up a Trunk" screenshot)  and select the Trunk required for the Source: DID <exact DID number>:

FWD DID Mode allows you to keep the original CLD number forwarded to the selected Trunk


Selecting the Self Managed option allows you to manage Trunks on the Account's web self-care interface.

So, end-users/Accounts may route all incoming On-Net calls that arrive on the Account to the desired Connection (screenshot shown in scenario #1).


Click on the diskette icon to apply routing changes (see the screenshot above).