Label
|
Explanation
|
---|---|
Name
|
Trunk name
|
Type
|
Type of Trunk
|
Number of concurrent calls
|
Number of calls which may be routed via this Trunk at the same time
|
Activated
|
= The trunk is activated and can be used for incoming and outgoing calls.
= The trunk is locked, e.g. for maintenance.
|
Logged in
|
= Trunk is logged in
|
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 set up, the T.38 protocol is negotiated between the two 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
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 initial 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 device switches to T.38 after detecting the fax tone (CED tone, 2100Hz). Alternatively, the switch to T.38 can be carried out by the sending fax device. Some IP adapters don't support switching by the sender.
If this option is set, SwyxServer suppresses a switch to T.38 by the sender.
|
Label
|
Explanation
|
---|---|
Always suppress 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 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 Caller Number
|
Although the caller number is not configured for this trunk, the caller number is signaled to the person being called.
Example:
Customer A (number 88 333 44) calls employee B (number 55 666 77). Forwarding to his mobile phone is activated, i. e. an incoming call is routed outwards again. If the customer's number (88 333 44) should also be signaled externally, then 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
|
---|---|---|---|
Origination Number
|
Number of the transferor
|
|
|
|
Hide number
|
|
|
|
Don't use this trunk
|
|
|
|
Use the following number
|
|
Enter the desired phone number
|
Number of the transferor
|
Origination Number
|
Hide number
|
|
|
|
Don't use this trunk
|
|
|
|
Use the following number
|
Enter the desired phone number
|
|
Hide number
|
|
|
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 user is deactivated.
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 secure communication by SRTP between SwyxServer and the opposite terminal, a common key (PreSharedKey) must be defined and exchanged between them.
For all components that use the SwyxWare database (e.g. SwyxIt!, PhoneMgr, ConferenceMgr, Gateway), this key is automatically generated by SwyxServer and distributed to the respective component in encrypted form.
For 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
|