Enter a name.

The name must be unambiguous within SwyxWare.

Enter a description, if applicable.

Select a trunk group of the required type to which the trunk is to be assigned:

The trunk assigned to this trunk group gets the property from the corresponding type.

If no matching trunk group or SwyxLink group exists yet, click on Create Trunk Group or Create SwyxLink group.

Each cross-site connection is managed by exactly one SwyxLinkManager.

If you want to manage the SwyxLink on this side of the connection, choose Locally managed SwyxLink trunk. This SwyxLink must then be set up "remotely managed" on the other side.

Enter the name (FQDN) or IP address of the SwyxServer to which this SwyxLink trunk should be configured.

Make sure that there is a transparent TCP/IP connection between the server running the LinkManager service (local SwyxLink) and all remote clients and the SwyxServer.

If a standby scenario is used on the other side, enter the name of the standby server as well.

Click the button to test the connection to the remote SwyxServer.

Enter here the SIP account data with which the SIP gateway should log on to SwyxServer via this trunk.

This logon data must be entered in the same format as when was configured.

SIP User ID is the user ID that together with the realm forms the SIP address (URI).

Select whether the gateway should authenticate itself.

The user name and password are required for user authentication.

SIP Provider Profile. This property is inherited from the assigned trunk group.

Enter the user data you obtained from your SIP provider:

SIP User ID is the user ID that together with the realm forms the SIP address (URI).

The user name and password are required for user authentication.

If necessary, enter the country code.

If necessary, enter the area code.

Enter the part of the phone number that follows the area code and precedes the extension (internal phone number).

Enter the first extension (internal phone number) of the phone number range.

Enter the Last extension extension (internal phone number) of the phone number range.

If necessary, enter the SIP addresses (URIs) that this trunk should manage. A SIP has the following format:

SIP:<Username>@<Realm>

For simplification, you can use '*' as a placeholder here,

The realm is already specified by the selection of the trunk group, but can be overwritten.

Select the type of compression to be used on this trunk:

You can disable unwanted codecs:

Voice, high bandwidth (G.711a, G.711µ)

The voice data is slightly compressed. This keeps the packet delay time in the LAN (Local Area Network) to a minimum.

Voice, highest bandwidth (G.722)

HD quality

Voice, low bandwidth.

High compression.

The special fax protocol T.38 takes into account the conditions of an IP network.

If necessary, enter how many calls may be made simultaneously via this trunk.

Basically, the maximum number of channels depends on the available bandwidth, as well as the codec setting, i.e. the bandwidth per call.

Using a SIP Trunk, the provider will define how many connections at the same time will be possible.

Specify whether status information ("Logged off", "Away", "Do not disturb", "Currently speaking" etc.) should be exchanged between users of different SwyxServers. Furthermore, users are shown in the Global Phonebook of the connected servers.

 

Select this option if you do not want user status information to be published via this link.

Select this option if the remote SwyxServer is in the same organization as the SwyxServer you are currently administering.

With this connection type, all groups and users on all connected sites are visible in the Global Phonebook. The relationships within the user and group properties must be used to specify precisely who should be signaled about the status of a user or group.

Select this option if the remoteSwyxWare is located in a different organization than the SwyxServer you are administering.

With this type of connection you can define individual groups of your SwyxServer which should be visible on SwyxServer of the other organization. The relationships within the user and group properties must be used to specify precisely who should be signaled about the status of the users of a group. The administrator of the other server can do this accordingly in the opposite direction, so that groups of his SwyxServer become visible on your side. Status signaling thus occurs only between users in selected groups. The users in these groups will also be displayed on both sites in the Global Phonebook.

Activate this option to display only the internal phone number of the users in the Global Phonebook on both pages.

Enable this option to display only the public phone number of the users in the Global Phonebook on both pages.

Enable this option to display only the public phone number of the users in the Global Phonebook on both pages.

Specify whether the user images stored by the user should also be synchronized between the different servers. To save bandwidth, you can deactivate this option.

 

The trunk should be used for the transmission of:

If you do not allow calls, the Video, Collaboration and SwyxIt! meeting features are automatically disabled. If you deactivate the status information button, you are not able to choose Instant Messaging

Apply the default computer name.