Inbound Trunks

The Inbound Trunks section allows you to add and configure inbound trunks, which connects the phone.systems™ to VoIP service providers.

Inbound trunks forward your third-party DID numbers directly to phone.systems™ for further call processing.

To access and manage your inbound trunks, click Trunks in the sidebar menu and select the Inbound Trunks tab.

../../_images/fig190.png

Fig. 1. Inbound Trunks

Forwarding calls to phone.systems™

Note

phone.systems™ creates a default inbound trunk named “Default,” which can be used to receive SIP traffic from your third-party providers.

A default inbound trunk is presented by phone.systems™, and this trunk may be renamed, configured or deleted. In addition, multiple inbound trunks can be added and configured as per the requirements specified by the selected VoIP providers.

Incoming domain addresses of the format xxxxxxxxxxxxx.in.phone.systems will automatically be assigned to all inbound trunks configured in a phone.systems™ account. These are unique domain addresses, and are used by 3rd party VoIP providers to route traffic to the phone.systems™ PBX. Therefore, VoIP service providers should configure inbound traffic to be forwarded to these SIP URI addresses.

The SIP URI address “phonenumber@xxxxxxxxxxxxx.in.phone.systems” has the following components:

  • phone number is the VoIP provider’s phone number in E.164 format (for example, 14169233346 for Toronto, Canada, and 442034116446 for London, the United Kingdom). Additionally, this number must be added in E.164 format to the phone.systems™ environment.

  • xxxxxxxxxxxxx.in.phone.systems is the unique domain address allocated by phone.systems™ to the specific inbound trunk.

We recommend that you consult your VoIP provider/s for more details on how inbound traffic should be forwarded from your DID numbers to the phone.systems™ environment

Adding and Configuring Inbound Trunks

Step 1. To add a new inbound trunk, click on the +-symbol button. Alternatively, click on the Edit button to modify a previously configured trunk.

../../_images/fig532.png

Fig. 1. Editing And Creating Trunks

Step 2: Input General Settings:

  • Friendly Name: Enter a name for the trunk to help identify it.

  • Transport Protocol: Select either UDP or TCP for the connection.

  • Allowed Codecs: Multiple codecs may be added for call negotiation between the VoIP service provider and the PBX environment. Codec options that may be selected from the dropdown list are:

    • OPUS

    • G722

    • PCMU

    • PCMA

    • G729

    • GSM

    • telephone-event

Note

You can arrange the codec priority by dragging the listed codecs into the desired position. The left-most codec will have the highest priority.

Important

To use DTMF codes for events such as Interactive Menu options or Feature Codes, ensure that the telephone-event codec is included in the Allowed Codecs list.

../../_images/fig260.png

Fig. 2. General Settings

Step 3: Enable Optional SIP Registration.

If your provider requires registration, you may enable it on the phone.systems™ UI.

Optional SIP registration may be enabled with parameters such as the Domain, Port, Username, Password, and Contact user being obtained from the service provider or system administrator.

Note

By default, the Registration settings feature is disabled.

../../_images/fig340.png

Fig. 3. Registration Settings

Step 4: Configure CLI Rules (Optional):

CLI Rules are used to override the Source Caller Name and Destination number. This functionality allows flexible Caller Name configurations and may be used to differentiate SIP calls received from phone.systems™.

CLI Rules will help you to identify which Inbound Trunk is being used to carry the call.

../../_images/fig435.png

Fig. 4. CLI Settings

Note

Knowledge in using POSIX Regular Expressions is required in order to use this feature.

Step 5: Click Save to finalize and create or edit your inbound trunk.