Label | Explanation |
---|---|
Name | Trunk name |
Type | Type of Trunk |
Number of concurrent calls | The number of calls that may be made simultaneously via this trunk |
Activated | = The trunk is activated and can be used for incoming and outgoing calls. = The trunk is blocked, e.g. for maintenance. |
Logged in | = Trunk is logged in |
Whether a trunk has been enabled or disabled is not recorded in the change log. |
Label | Explanation |
---|---|
Trunk is activated | Check the box to unlock the trunk for incoming and outgoing calls. |
Label | Explanation |
---|---|
Behavior during fax transmission | When a fax connection is established, the T.38 protocol is negotiated between the devices involved. Certain variants of this negotiation may not be supported by some IP adapters. Use the following filter options to establish compatibility with such devices: Remove T.38 codec from initial invite (SIP invite) Some IP adapters cannot correctly interpret an initial connection request which includes T.38 as well as voice Codecs. If this option is set, SwyxServer removes T.38 from the first connection request. The fax devices first set up a voice connection and then switch to the fax protocol T.38 because of the fax tone (CED tone, 2100Hz). Prohibit T.38 reinvite by sender The receiving fax machine switches to T.38 after detecting the fax tone (CED tone, 2100Hz). Alternatively, switching to T.38 can be done by the sending fax machine. Some IP adapters do not support switching by the sender. If this option is set, SwyxServer suppresses switching to T.38 by the sender. |
If the receiving side involves a combined phone/fax device (fax switch), a fax data transmission is impossible when the option "Prohibit T.38 reinvite by sender" is activated. |
During a new installation of SwyxWare or during an update the option "Use server default" is activated by default. The selection of the Codec filters, as of the options of the area "Action on fax receipt", is accordingly deactivated. The options cannot be selected. |
Label | Explanation |
---|---|
Always suppress phone number | Select whether and how the phone number for outgoing calls should be signaled via this trunk. Select this option if the called party is not to be signaled (XXX), regardless of the phone number configured for this trunk. |
Always use this phone number | Enter a call number in canonical format or a SIP URI that is always signaled to the called party (e.g., the number of the central office), regardless of the call number configured for this trunk. |
Signal the caller's phone number | Although the caller number is not configured for this trunk, the caller number is signaled to the person being called. Example: Customer A (call number 88 333 44) calls employee B (call number 55 666 77). Call forwarding to its cell phone is activated, i.e. an incoming call is forwarded back to the outside. If the customer's call number (88 333 44) is now to be further signaled externally, this can be allowed here, although this number was not defined for this trunk. |
Use | Specify which phone number this trunk uses. You can define the behavior for phone numbers that are assigned to this trunk as well as for phone numbers that have not been assigned, see the table: |
Use | When assigned to this trunk | If assigned to this trunk, otherwise: | Required input |
---|---|---|---|
Caller number | Number of the transferor | ||
Suppress phone number | |||
do not use this drink | |||
use the following phone number | Enter the desired phone number | ||
Number of the transferor | Caller number | Suppress phone number | |
do not use this drink | |||
use the following phone number | Enter the desired phone number | ||
Suppress phone number |
For Number Signalling via a SIP trunk, the provider must support the feature "ClipNoScreening". For further information see https://service.swyx.net/hc/en-gb/articles/360000011599-Support-of-feature-ClipNoScreening-for-SIP-trunks- |
If "No encryption" was set within the server properties, the mode here is also set to "No encryption"; if "Encryption required" was configured there, the setting "Encryption required" is also found here. In both cases, the mode cannot be changed. The field is then deactivated. |
Label | Explanation |
---|---|
Encryption mode | No encryption If "No encryption" is selected, the voice data going via this trunk is not encrypted. If the encryption mode was set to "No encryption" within the server properties, the mode is likewise set to "No encryption" here, and cannot be changed. The field is disabled. Encryption preferred When "Encryption preferred" is selected, the voice data is only encrypted if the opposite terminal likewise supports encryption. If this is not the case, the voice data is not encrypted, but phoning is still possible. Encryption mandatory When "Encryption mandatory" is selected, voice data encryption is obligatory. This means that either encryption always occurs or the call is aborted with the reason "Incompatible encryption settings". This can be the case, for example, if the opposite terminal does not permit any encryption. |
Key | To ensure a secure communication via SRTP between SwyxServer and remote station a shared key (PreSharedKey) has to be defined and exchanged between them. For all components using the SwyxWare database (e.g. SwyxIt!, PhoneMgr, ConferenceMgr, Gateway) this key is automatically generated by SwyxServer and distributed encrypted to the respective component. At SIP Gateway, ENUM type, the key must be entered manually. In addition, the stored key must also be entered at the remote terminal. |
Repeat key |