help | 8 Trunks | Edit trunk groups
8.2 Edit trunk groups
You can customize the settings you specified when you created the trunk group. You can also specify other settings.
To edit a trunk group 
1 In the menu, select Connections | Trunks.
2 Select Trunk groups.
3 A list appears with all Trunk Groups.
Label
Explanation
Name
Name of the Trunk Group
Description
Description of the Trunk Group
Type
Type of Trunk Group
Profile
Trunk Group Profile
Location
Location of Trunk Group
Calling Rights
Defines where incoming calls of this trunk group may be forwarded to if the call destination is not a user at the same SwyxServer
4 In the row of the desired trunk group, click .
*The following tab appears General.
5 You can edit name, description, location and profile, see Create trunk groups. You can also edit the following Settings:
* 
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 allowing the possibility to route incoming calls back to the outside via a trunk only in exceptional cases.
 
* 
The string for the selection prefix must not begin with the outside line access code and must not begin with an existing internal telephone number. It is recommended to let the selection prefix start and end with * or # to achieve a better differentiation to the destination number.
 
* 
If a user has used the selection prefix to specify a trunk group through which the call should be routed, no forwarding rules are applied to that call.
 
* 
If a project code number is used in addition to the selection prefix, enter it first. The project code always begins with * and ends with #.
 
* 
If a selection prefix has been entered by the user, only trunks in this trunk group will be selected and no further attempt will be made to route the call through other trunks.
 
Label
Explanation
Calling Rights
Select where incoming calls received via this trunk group may be forwarded to. This way you define if and which other trunk groups the call may use to leave this SwyxWare installation if its destination is not a user of this SwyxServer:
*Internal connections only (default value)
*International connections
*Calls within Europe
*National connections
*local calls
*Deny all calls
 
If a user has been called on this SwyxServer and the call is forwarded by his Call Routing, the call gets the permissions of the called user.
Selection prefix for the trunk group
Set a prefix that allows a user to route the call specifically through this trunk group.
The selection prefix must be uniquely assigned to a trunk group, it cannot be assigned more than once, it may only consist of the characters '01234567890#*' and may not begin with '##'.
 
Examples:
In the following, the project code *1234# and the selection prefix **34#
<*Project code#><Selection prefix><Canonical call number>
*1234#**34#+44123555777
 
or if using a public line access
<*Project code#><Trunk Groups prefix><Public line access><National number>
*1234#**34#00123555777
 
or if using an internal number
<*Project code#><Trunk Groups prefix><Internal number>
*1234#**34#123555777
 
or if using an SIP URI (always beginning with sip:)
<*Project code#><Trunk Groups prefix><SIP:URI>
*1234#**34#sip:han.solo@millenium-falcon.com
Public line access of the superior PBX
If SwyxWare is configured as a sub PBX, enter the outside line access of the parent PBX.
6 Click on Save.
7 Select the tab Phone number formatting.
Label
Explanation
Conversion for outgoing calls
Procedures for converting outgoing numbers and interpreting incoming numbers are defined within a trunk group. In the properties of a trunk group, the selected profile is used to specify in detail which phone number (outgoing or incoming and calling or called number) is converted into which format. This mapping of formats can be modified subsequently by administrators.
 
For the available phone number formats, see section "Supplied configuration files" under
Conversion for incoming calls when number type is unknown
8 Click on Save.
9 If necessary, select the tab SIP (SIP and ENUP types only).
10 You can change the SIP registration data for a SIP trunk group, see Create trunk groups. You can also specify other settings:
Label
Explanation
STUN support
Check the box to enable STUN support.
STUN can be used to determine the current public IP address of the connection so that the remote station can address and return its call data correctly.
STUN server
If your SIP provider supports STUN, enter the name or IP address of your provider's STUN server and the corresponding port.
Alternatively, you can use the free STUN server "stunserver.org" with port "3478".
STUN server port
Outbound proxy
(SIP only)
Some providers have an outbound proxy before the SIP proxy. If necessary, enter these parameters according to your provider's specifications.
Outbound proxy port
(SIP only)
Proxy
(SIP only)
Enter the address and port of the proxy server.
The SIP proxy server takes over the connection setup to the appropriate subscriber, first checking which SIP registrar the relevant subscriber is logged in with. Upon request, the subscriber then receives the current IP address of the subscriber and can thus deliver the call to this address.
Proxy port
(SIP only)
Realm
(SIP only)
If necessary, enter the realm area 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 not specified, the Registrar or Proxy value is used.
DTMF method:
(SIP only)
Select a DTMF method if necessary.
This mode is used to specify how the provider handles keystrokes from the user (DTMF signaling).
 
None.
DTMF signalling is deactivated.
 
RFC2833_Event:
DTMF signaling is used based on the event mechanism described in RFC2833.
 
Info Method DTMF Relay
DTMF signaling is used as suggested by Cisco (applicationtype DTMFRelay).
11 Click on Save.
12 If necessary, select the tab Encryption (SIP type only).
* 
Make sure that the selected transport protocol is supported by your provider.
 
* 
When "Encryption mandatory" is selected, voice data encryption is obligatory. This means that encryption is either always performed or the call is terminated with the reason "Destination does not support encryption".
 
* 
The encryption mode for a SIP trunk group has no influence on the SRTP encryption configuration for SwyxServer.
 
Label
Explanation
Transport protocol
Select the transport protocol to be assigned to the trunk group:
 
Automatic (Standard)
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 packet are transmitted encrypted.
Encryption mode
Select the encryption mode.
This setting is enabled only if you have selected the "TLS" transport protocol. You can define if voice data will also be encrypted when using the secure TLS connection.
No encryption
The voice data is not encrypted.
 
Encryption mandatory
The voice data is encrypted between SIP provider and SwyxLinkManager.
13 Click on Save.
*The trunk group settings have been updated.
Last modified date: 01/19/2024