The components of myContactCenter connect over fixed TCP ports. Each table shows who establishes a connection and who accepts it. Only the local SIP port, the port for SNMP traps and the ports of mail servers and databases can be configured. How the components fit together is shown in System architecture.
Between the components
| Port | From | To | Purpose |
|---|---|---|---|
| 5000/TCP | Agent, Wallboard, Routing Service, Logger | Dispatcher | ask which server is currently active |
| 6000/TCP | Agent | Server | main connection of the Agent |
| 6007/TCP | Agent | Server | second connection for individual messages, see Messages and errors |
| 6001/TCP | Administration | Server | management; the Administration connects directly to the server, not via the Dispatcher |
| 6002/TCP | Routing Service | Server | one connection per conversation |
| 6009/TCP | Routing Service | Server | management connection of the Routing Service |
| 6003/TCP | Wallboard | Server | real-time values |
| 6005/TCP | Dispatcher | master and standby | state of the servers |
| 6006/TCP | Server | partner server | synchronization of master and standby |
| 6016/TCP | Logger | Server | login of the Logger |
| 514/TCP | all programs and services | Logger | log messages |
| 6012/TCP | Routing Service | ExternalDatabase on the same computer | flows’ access to external databases |
| 6017/TCP | Server | SwyxCDS service on the same computer | connection to SwyxWare and SwyxON |
Phone system and voice
| Port | From | To | Purpose |
|---|---|---|---|
| 5060 — UDP; with SwyxWare and SwyxON, optionally TCP | Routing Service, the Agent’s softphone | phone system | SIP: registration and calls |
| Base Port to Base Port + Port Range, default 53000 to 55000 | phone system | Routing Service, softphone | local SIP port, see Phone system |
| UDP, in both directions | phone system | Routing Service, softphone | voice data (RTP) |
| 443/TCP (HTTPS) | Server | Wildix | users and presence |
With SwyxWare and SwyxON, the SwyxCDS service connects to the configuration interface of the phone system. With IlogixxUC and SipOnly, the server checks by ping whether the phone system can be reached.
Databases, email and internet
| Port | From | To | Purpose |
|---|---|---|---|
| SQL Server port, 1433/TCP for the default instance | Server; Agent and Administration for reports and dashboards | Microsoft SQL Server | configuration database |
| 5432/TCP or the SQL Server port | Server | PostgreSQL or SQL Server | Monitoring Database |
| port of your database | ExternalDatabase | your databases | external databases in flows |
| 993/TCP or 143/TCP | active Routing Service | mail server | collecting email from mailboxes (IMAP) |
| 25/TCP (default) | Routing Service | mail server | sending emails (SMTP) |
| 6010/TCP (HTTP) | your customers’ browsers | Routing Service | web chat and web callback |
| 6008/UDP | your monitoring system | Server | SNMP queries |
| 162/UDP (default) | Server | your monitoring system | SNMP traps for alarms |
| 443/TCP (HTTPS) | Server, Routing Service | Microsoft Azure | speech synthesis, speech recognition, translation, transcription |
| 443/TCP (HTTPS) | Server | ilogixx activation server | licenses, optionally via a Web Proxy |
Firewall
The installation packages add rules for their ports to the Windows Firewall of the respective computer — see Firewall. Check these rules against the tables, especially if the server, Routing Services, database and phone system are on different computers or in different networks. Also remember the voice data: it runs over UDP between the phone system, the Routing Services and the agents’ workstations.