Define Trunk Groups
A trunk group represents all the trunks of the same type which are grouped together in it.
To define a Trunk Group
The “Trunk Groups” list will appear.The “General” tab appears.
Call permissions of a trunk group only apply to incoming calls!
The advanced call permissions (more than "internal calls") could, depending on the configured forwarding entries, be misused by external callers. Protect your SwyxServer by only allowing the possibility of routing incoming calls back to the outside via a trunk in exceptional cases.
The advanced call permissions (more than "internal calls") could, depending on the configured forwarding entries, be misused by external callers. Protect your SwyxServer by only allowing the possibility of routing incoming calls back to the outside via a trunk in exceptional cases.
Name | Enter the name of the Trunk Group. The name must be unambiguous within SwyxWare. |
Description | If applicable, enter a brief description. |
Location | Select a defined Location to which the new Trunk Group should be assigned. |
Type | Select the Type of the Trunk Group:  ISDNSIPSIP Gateway |
Profile | Select the Trunk Group profile. A trunk group profile specifies how the trunk interprets and handles the call numbers. Depending on the trunk type, a number of predefined profiles are available. For each of these profiles, the number format is specified. For SIP trunks in particular, the profile specifies the provider and the necessary SIP parameters. Please contact your specialist dealer for an overview of compatible SIP providers and the functions they offer in relation to SwyxWare. The Swyx knowledge base contains a related entry, which is constantly updated. Simply visit: |
Calling Right | Specify what rights a call has when coming in via this trunk. This determines whether and which other trunk groups it may use to leave this SwyxServer installation, provided that its destination is not a user of this SwyxServer. deny all callsinternal callsLocal callsNational destinationsEuropean destinationsno call restrictions |
Enable Trunk Recording | If you activate the "Record calls via trunks" checkbox, all calls made via this trunk group will be recorded in the way that is activated in the settings of the SwyxServer. |
Please note that the option pack “SwyxMonitor“ must be installed to activate recording on a trunk.
The Registrar port must match the selected transport protocol. Leave the field empty if you did not receive information on the port by your provider. The port is determined via DNS query.
Make sure that the selected transport protocol is supported by your provider.
Enable SIP registration | Activate the check box to permit SIP registration. |
Registrar | Enter the registrar. REGISTER messages are sent to this address. If no value is entered here, the value configured under proxy will be applied. |
Registrar Port | In the “Port” field you define the port on which the configured registrar receives the registration request. |
Re-registration Interval | Enter a value in seconds. The "Re-Registration Interval" defines how often the registration must be updated. A small value will allow you to quickly recognize the loss of the SIP connection to the provider. A high value results in lower network burden in standby. |
Enable STUN support | Activate the check box to permit STUN support. STUN is a network protocol that recognizes the existence and type of firewalls and NAT routers and takes this information into consideration. It enables the uncomplicated use of devices (e. g. SIP telephones) and programs in networks that should receive information from the internet. |
STUN Server | Specify the STUN server and the associated port for use by the SIP devices. |
STUN Server Port | |
Outbound Proxy | Some providers require an outbound proxy and a port. You should have received this data from your provider. |
Outbound Proxy Port | |
Proxy | Enter the SIP proxy and the port for outgoing calls. |
Port | The SIP proxy server takes over the connection setup to the appropriate subscriber, first checking which SIP registrar the relevant subscriber is logged on with. From this it requests and receives the current IP address of the subscriber, and can thus deliver the call to this address. |
Realm | Define the SIP realm of the provider. An SIP URI (userId@realm) is derived from the user ID (userId), the configuration of the SIP account, and the realm of the provider (realm). If this field is left blank, the value registrar or proxy will be used. |
DTMF mode | Select the DTMF method. This mode defines how the provider proceeds with the keyboard input of a user during a call (DTMF signalling). None DTMF signalization is deactivated RFX2833 Event RFC2833_Event: DTMF signalization, based on the event mechanism described in RFC2833, will be used. Info Method DTMF Relay DTMF signalling as recommended by Cisco (application type DTMFRelay) will be used. |
Transport Protocol | Select the transport protocol that you want to assign the Trunk Group: Automatic The transport protocol is determined automatically by DNS lookup. UDP This transport protocol is supported by most SIP providers. It requires the lowest bandwidth, however, it carries a higher risk of data loss. TCP This transport protocol is known to be reliable, however, it requires higher bandwidths. TLS This transport protocol has TCP characteristics and supports encryption. When selecting this protocol SIP packets are transmitted encrypted. |
Encryption | This option will only make sense if you select TLS as the transport protocol. Activate the check box to make sure that the voice data is encrypted between SIP provider and SwyxLinkManager. |
Procedures for converting outgoing numbers and interpreting incoming numbers are defined within a trunk group. In the properties of a trunk group, the selected protocol contains a detailed definition of which numbers (outgoing/incoming and calling/called number) are converted into which formats. This mapping of formats can be modified subsequently by administrators.
Conversion for inbound calls: Calling party number | Select a number formatting profile Canonical with plusCanonical without plusCLIP no screeningDial as a PBX userExtensionFixed SubscriberISDN ItalyISDN Netherlands CLINationalSubscriber NumberTransparentType and PlanFor information about the number formatting formats please refer to Number formats. |
Conversion for inbound calls: Called Party Number | |
Conversion for outbound calls: Calling party number | |
Conversion for outbound calls: Called Party Number |
The new Trunk Group appears in the list.Last modified date: 05/31/2024