...
| Field | Description |
|---|---|
| ID | An automatically assigned ID from the system. |
| Name | A descriptive name for the trunk, which is used when selecting the trunk when configurations are made, for example in service numbers. |
| Incoming Number Pattern | Trunk groups can be matched based on the called number. For example, 49894614950% would match all incoming calls to the jtel main office in Munich. |
| SIP Source Server | Trunk groups can alternatively be matched based on the SIP source and destination server in the SIP From: and To: headers. This field affects the From: header match. Any match can be made here, but it is worth checking whether the incoming INVITE messages contain IP addresses or names (DNS) using wireshark. |
| SIP Destination Server | See SIP Source server. This field affects the To: header match. |
| SIP Invited Entity | Trunk groups can be matched on the invited entity in the INVITE message line (first line in the INVITE message). |
| Subscriber Country Code | For some number translators, the location of the system is used when converting numbers. This parameter is used to match the country code. For example, for jtel, 49 for Germany. |
| Subscriber Area Code | For some number translators, the location of the system is used when converting numbers. This parameter is used to match the area code. For example, for jtel, 89 for Munich. |
| Subscriber Prefix | For some number translators, the location of the system is used when converting numbers. This parameter is used to match the prefix (head number) of the system. For example, for jtel, 4614950, for the head number of the PBX. |
| Outgoing Trunk Selection Trunk Group for Internal Numbers | When an active call needs to start a further call (for example, an incoming call to the system results in a call to an agent), the trunk group specified here will be used to make that call, if an internal number is to be called. Internal numbers are identified by the Internal Number Length parameter. It is not recommended to set any other trunk than "Same Group" unless you know exactly what you are going. |
| Outgoing Trunk Selection Trunk Group for External Numbers | When an active call needs to start a further call (for example, an incoming call to the system results in a call to an external destination), the trunk group specified here will be used to make that call, if an external number is to be called. External numbers are identified by the Internal Number Length parameter. It is not recommended to set any other trunk than "Same Group" unless you know exactly what you are going. |
| General access for outbound calls | If this flag is set, this trunk can be matched (by any client) and used to make an outbound call. This setting should only be applied for systems which are not used by multiple tenants. |
| Number Translator - Incoming Caller | All numbers should be translated to E.164 before they can be used in the system internally. This setting affects how the system translates the From or Calling Party Number into E.164. For some settings, a converter parameter is required. See below, for a list of available translators. |
| Number Translator - Incoming Called | This setting affects how the system translates the To or Called Party Number into E.164. For some settings, a converter parameter is required. See below, for a list of available translators. |
| Number Translator - Outgoing Caller | This setting affects how the system translates the internal E.164 number back to the format required by the telephony system, when an outgoing call is made. This setting affects the From or Calling Party Number. For some settings, a converter parameter is required. See below, for a list of available translators. |
| Number Translator - Outgoing Called | This setting affects how the system translates the internal E.164 number back to the format required by the telephony system, when an outgoing call is made. This setting affects the To or Called Party Number. For some settings, a converter parameter is required. See below, for a list of available translators. |
| Outgoing send P-Asserted Identity | If this option is checked, the SIP header P-Asserted-Identity will be set when an outgoing call is made. |
| P-Asserted-Identity (Dialler / click to dial - leg to agent) | This is the value used for the P-Asserted-Identity field, when calls are made to agents. Please specify a fully qualified SIP URI for die P-Asserted-Identity field, for example "0123456" <sip:0123456@myjtelserver.com>. Typical value: <sip:%P.Asserted.Identity.Number%@myjtelserver> |
| P-Asserted-Identity (All other cases) | This is the value used for the P-Asserted-Identity field, in all other cases. Please specify a fully qualified SIP URI for die P-Asserted-Identity field, for example "0123456" <sip:0123456@myjtelserver>. Typical value: <sip:%IFEQUALSTR(%CALLDIRECTION%,0,%CALLER%,%Service.ServiceNumbersRootNumber_%)%@myjtelserver> |
| Loopback Prevention | When the system makes an outgoing call to an agent, SIP history information (SIP history header) is provided if this is setup in the ACD group. If the history information is subsequently detected on an incoming call, then a loop has been produced (by call diversion) in the PBX. The system will reject such calls if this flag is set. |
| Outside Line Prefix | If the system determines, that an external call is to be made, then this prefix will be applied to the beginning of the number to access an outside line. Note: this is not recommended - the target SIP or telephony system should use E.164 to make routing more transparent. |
| Internal Number Length | To distinguish between internal and external numbers, this field is used. Numbers which are longer than this setting are considered external numbers. |
| Generate Incoming CDR | This field is used to generate CDRs on this trunk, and is not used in standard installations. |
| Generate Outgoing CDR | This field is used to generate CDRs on this trunk, and is not used in standard installations. |
...
| Direction | Matching Order |
|---|---|
| Inbound | Incoming calls are routed to a particular telephony server by a PBX or SIP entity outside the scope of this document. It is recommended, that when more than one telephony server is present, load sharing between the active servers be configured. Also, it is important to note, that the reception of a TRYING in response to an INVITE does not indicate success, but only that matching process will be initiated. Additional steps should be taken on the providing server to ensure that after a timeout, the call is distributed to another server if at least not a final response, or a RINGING are received. Matching then takes place as follows:
|
| Outbound | First of all the telephony server is selected according to a "least used but active" convention. This means the telephony server must have set a keep alive timestamp in the system database. The active server with the least number of calls will be used. Next, the trunk group is matched as follows:
|
Incoming Number Translators
Note - translators which are not documented here should not be used, as they are considered legacy.
| Translator | Description |
|---|---|
| Portal Default - treat as ISDN | See ISDN below. |
| E.164 incoming | The incoming number is already in E.164 format. |
| E.164 with + incoming | The incoming number is in E.164 format, prefixed with a +. |
| ISDN | This translator uses the Number Type field to distinguish between subscriber (local), national and international calls, and applies the settings from the coutry code, area code and subscriber prefix to the number as required, to generate an E.164 number. |
| STARFACE | Calls from a starface PBX are typically prefixed by a routing parameter in the called party number. This prefix is removed, the result is the called number. |
| Telephone 0, 00 | This number translator assumes that all national calls come prefixed with 0, all international with 00, and subscriber calls have no prefix. The appropriate parameters from Country Code, Area Code and Subscriber Prefix are added to the number to generate E.164. |
| Telephone 00, 000 | Same as Telephone 0, 00, except with an additional 0 for accessing an outside line prepended to external numbers. |
| Telephone 90, 900 | Same as Telephone 0, 00, except with an additional 9 for accessing an outside line prepended to external numbers. |
Outgoing Number Translators
| Translator | Description |
|---|---|
| Portal Default - treat as E.164 | See E.164 below |
| E.164 outgoing | The number is called in E.164 format. For ISDN connections, the number type will be set to international. |
| ISDN | The number should be dialled in ISDN format. This is the reverse process of the incoming ISDN converter, a match on country code, area code and subscriber prefix determines the number type (international, national or subscriber). |
| Telephone | This is the reverse of the incoming Telephone 0, 00 converter. |
| Telephone with outside line prefix | This is the reverse of the incoming Telephone 00, 000 and Telephone 90, 900 converters. The set outside line prefix will be applied. |
| Universal Formatter | See below |
| VOIP - add prefix "sip:" then E.164 number and postfix | This creates a SIP URI from an E.164 number. |
| VOIP - add prefix "sip:+" then E.164 number and postfix | This creates a SIP URI from an E.164 number with a preceeding plus. |
VOIP Telephone - add prefix "sip:" then number in PBX format with prefix (0,00) | This converter matches the country code, area code and subscriber code, and builds a SIP URI accordingly, adding a prefix 0 and 00 as required. The converter parameter is appended (usually the SIP destination server). |
| VOIP Telephone - add prefix "sip:" then number in PBX format with prefix (0,00), no prefix for internal numbers | This converter matches the country code, area code and subscriber code, and builds a SIP URI accordingly, adding a prefix 0 and 00 as required. Internal numbers (determined by the internal number length parameter) are not prefixed. The converter parameter is appended (usually the SIP destination server). |
| VOIP Telephone - add prefix "sip:" then number in PBX format with prefix (0, 00,000), no prefix for internal numbers | This converter matches the country code, area code and subscriber code, and builds a SIP URI accordingly, adding a prefix 0, 000 and 000 as required. Internal numbers (determined by the internal number length parameter) are not prefixed. The converter parameter is appended (usually the SIP destination server). |
Universal Formatter
The universal formatter can be used to build outgoing numbers.
Trunks
This page is used to assign trunks to the trunk group.
...