Introduction
A typical installation of the jtel system consists of one or more telephony and application servers to provide services to its users.
Trunks and Trunk Groups are the logical way telephony resources are organised and connected to the system and it servers.
Trunks
The telephony server provides SIP connectivity at the base level for a certain number of channels. When using SIP, each telephony server has one SIP connection (usually UDP on port 5060), which is capable of addressing any remote telephony service using a domain name or an IP address. This SIP connection is known as a Trunk.
On an ISDN based machine, there may be more than one trunk, for example one for each primary rate connection the system provides. Each of these connections is an individual trunk on a particular server.
Trunks are configured using the System Settings ... Trunks menu, and the following fields are configured:
| Field | Description |
|---|---|
| MachineID | Each telephony server has a unique ID within each installation. This is assigned in the telephony server system settings menu, under the option "General". As a convention, we recommend that the final number of the IPv4 address is used. This number must match the number assigned in the trunk for the system to be able to select and identify trunks appropriately. |
| Controller | Each SIP controller has a unique ID. This is configured in the files giAculab.cfg and StdCall_MCP.cfg in the telephony server. In giAculab.cfg numbering starts at 0, wheras in the jtel telephony server, numbering starts with 1. Usually, the SIP provider will be configured as netport 0 in giAculab.cfg and Controller 1 in StdCall_MCP.cfg. |
| Name | The trunk can be given a descriptive name for identification purposes. |
Trunk Groups
Trunk groups are used to group trunks together, and provide number translation services for incoming and outgoing calls.