Each package can be installed on its own computer. Some parts belong together, however:
- ExternalDatabase always runs on the computer of the Routing Service; it is installed with it.
- SwyxCDS runs on the computer of the server.
The Dispatcher, Logger, Routing Service and SQL Server can be on any computers, as long as the connections from Ports and connections are open.
Names and addresses
Every name that you enter anywhere must be resolvable on the computers that use it:
| Name | Entered in | Used by |
|---|---|---|
| Registration point — name or address of a Dispatcher | the configurators of Logger, Routing Service and Wallboard; in the Agent | all programs and services where it is entered |
| Master and standby for the Dispatcher | Master server, Standby server in the Dispatcher Configurator | the Dispatcher |
| Master and standby for all others | Master, Standby and Alternative name for Master or Alternative name for Standby in the server configuration, see Master and standby | Agent, Wallboard, Routing Service and Logger: the Dispatcher gives them this name as the address of the active server. |
| Server for the Administration | Connect to server in the Administration | the Administration |
| SQL Server | SQL Server in the Server Configurator | the server and the workstations for reports, see Setting up the server |
| Phone system | PBX server in the server configuration | Routing Service and Agents |
The default for Master and Standby is the computer name of the server. If not all workstations resolve this name, enter the fully qualified DNS name there. For workstations in another network that reach the server under a different name or address, there are Alternative name for Master and Alternative name for Standby: if the connection under the first name fails, the programs try the alternative one.
Firewall
The packages add rules to the Windows Firewall of their computer for the connections that arrive there — for all network profiles and every sender. Among them:
| Package | Ports |
|---|---|
| Server | 6000 to 6003, 6005 to 6008 and 6016/TCP; 6008/UDP |
| Dispatcher | 5000/TCP |
| Logger | 514/TCP |
| Routing Service | 53000 to 55000 TCP and UDP for SIP, 6010/TCP for web chat and web callback |
| Agent | 53000 to 55000 TCP and UDP for SIP |
No package creates a rule for port 6009, through which the Routing Service registers with the server. If the Routing Service runs on a different computer than the server, open 6009/TCP on the server itself.
The rules only apply to the Windows Firewall of the respective computer. If there are firewalls in the network in between, open the same connections there — including the voice data that flows via UDP between the phone system, the Routing Services and the workstations of the agents; see Ports and connections.
A second Dispatcher
If the only Dispatcher fails, Agents, Wallboards and Routing Services that reconnect can no longer find the server. A second Dispatcher on another computer prevents this:
- Install the Dispatcher package on the second computer and enter the same servers under Master server and Standby server as for the first one.
- Enter both Dispatchers as registration points everywhere: for the Logger, Routing Service and Wallboard as Registration point 1 and 2 (Wallboard: Registration Point 1 and 2), in the Agent as Point 1 and Point 2.
Status of services shows one row per Dispatcher.
Multiple Routing Services
If you install the Routing Service package on further computers, all of them register with the server. Exactly one is active and accepts calls, chats, web callbacks, emails and faxes; the others wait passively and take over when it logs off. You can switch over in Status of services.
- In each Routingservice Configurator, enter the registration points and the same SIP account as for the first Routing Service.
- Recordings and voicemails must be stored in a folder that all Routing Services can reach — see Server tab.
Standby server
A second server takes over if the master fails or you switch over — see High availability. To set it up:
- Install the Server package on a second computer. In the Server Configurator, give it its own database, preferably on its own SQL Server.
- Connect the Administration to the standby server. There, first enter its Server: Base key — this makes it the standby server — then its other standby licenses, and activate them — see Licenses for the standby server.
- On the master, enter the standby server in the server configuration, Standby tab, and synchronize it — see Master and standby.
- In each Dispatcher Configurator, enter the standby server under Standby server.
You switch over in the Administration with Make Server Active and Make Server Passive — see Making a server active or passive.