In order for the SwyxWare telephone system to operate smoothly, the existing network infrastructure is a deciding factor in addition to the basic software and hardware requirements described above. The following provides a description of an environment that offers optimal conditions for the functioning of SwyxServer.

It is assumed that we are dealing with a network which is based on a Windows Active Directory.

To create optimal conditions for SwyxServer, the following should be set up:

SwyxWare uses the Internet Protocol (IP) to transfer voice and control data. Each client and SwyxServer computer requires a unique IP address in the network.

A complete layer2 switched network guarantees an optimal transmission of the voice and control data, even in case of a large number of SwyxWare telephone calls or in a network with increased data traffic (e.g. file transfer, HTTP, FTP), however, this is not obligatory.

The SwyxServer computer or the SwyxGate which has been installed on a separate computer must be connected to a switch. This will ensure that there is sufficient bandwidth available for the data traffic between the telephony clients (SwyxIt! or SwyxPhone) and SwyxServer.

In order to improve the voice quality, the use of Quality of Service in the network is advantageous.

For further information see

Detailed and actual information about the ports used by SwyxWare see

The use of a DHCP server for the distribution of the IP addresses to the telephony clients offers the following advantages:

To find out how to install a DHCP server and how to configure it for the use of telephony clients see DHCP-Server (Dynamic Host Configuration Protocol).

An Active Directory requires a DNS Server located in the network. The Active Directory uses DNS as a locator service, which helps to assign the names of the client's FQDN (Fully Qualified Domain Name), domains, locations and services in the Active Directory of an IP address.

If the WINS resolution for DNS is activated on the DNS server, the WINS server will be queried if the name of the client cannot be resolved by the DNS server.

See DNS (Domain Name Service).

Enreach recommends not using SwyxWare on systems which are simultaneously DomainController or DNS Server. If you do run SwyxWare on a Windows DNS Server, Microsoft Security Fixes (patches KB951748 and KB951746) can cause the Microsoft DNS Server to occupy all IP ports so that SwyxWare is unable to allocate any more. To avoid such conflicts, a static range of ports can be reserved, excluding these for random port requests from applications/services.

For further information, please contact you specialist dealer.

If SwyxRemoteConnector is used, the company router (NAT gateway) has to be configured accordingly.

See Port forwarding via router.

 

The service WINS resolves NetBios names into IP addresses and is therefore an elementary component of a Windows network. Given this fact, this service should already be installed on the Windows Server located in the network.

See WINS (Windows Internet Name Service).

If the above mentioned components are correctly configured, SwyxWare will be provided with an optimal environment.