Requirements

The installation packages only check the .NET runtime. So have everything this page lists ready before you install.

Computers

• Windows 11 and Windows Server 2022 or later. The Agent, Administration and Wallboard run on Windows 11 at the workstations; the Server, Routing Service, Dispatcher and Logger run on Windows Server 2022 or later. All packages are built for 64-bit Windows.
• Administrator rights for the installation and for the configurators. The Agent, Administration and Wallboard then run with the rights of the logged-in user.
• .NET 9. Every computer on which you install a package needs the Microsoft .NET Desktop Runtime and the Microsoft ASP.NET Core Runtime in the current version 9. Each package checks both and stops with a message if they are missing. The Agent and the Routing Service bring the Microsoft Visual C++ runtime themselves. The SwyxCDS service also needs .NET Framework 4.8 if you connect SwyxWare or SwyxON.
• Space for logs and recordings. The Logger keeps older logs up to an adjustable size, 2,000 MB by default — see Logger. The Routing Service stores recordings and voicemails as WAV files, see Server tab.

Databases

Microsoft SQL Server

Configuration, statistics and license data are stored in a database on Microsoft SQL Server 2022 or later. The Express edition is sufficient but limits the size of each database. You specify the server and the database in the Server Configurator; it creates the database itself.

• Enable SQL Server authentication. The Server Configurator and the server log in with a SQL login, not with a Windows account. For this, SQL Server must run in mixed mode.
• A SQL login with extensive permissions. It must be allowed to create and back up databases as well as to create logins and grant permissions. The server works with the same login during operation, so it must remain in place.
• Reachable from all workstations. The Agent and the Administration read the data for reports and dashboards directly from the database. The name of the SQL Server must therefore also be resolvable on the workstations, and its port must be reachable from there — see Ports and connections.
• SQL Server Browser for named instances. It also provides the list of SQL Servers in the configurator; if a server is missing there, enter its name yourself.

Database for the conversations

The server stores tickets and conversations — emails, faxes, chats and calls — in a second database, the Monitoring Database. It is located either on Microsoft SQL Server as well or on PostgreSQL.

For PostgreSQL:

• The configurator only offers PostgreSQL servers that it finds in the network segment of its computer on port 5432 or 5433.
• The login must be allowed to create databases and roles. The server also works with this login during operation.

Service account

The Server, Routing Service, Dispatcher and Logger run under a Windows account that you enter in the respective configurator:

• a user account with a password, from the computer itself or from the domain. Accounts without a password, such as the local system account, cannot be entered.
• The configurator itself grants the account the Windows right “Log on as a service”.
• The account of the Routing Service must be allowed to write to the folder for recordings if a network share is entered there — see Server tab.
• With SwyxWare and SwyxON without a separate account for the phone system, the server logs in to the Swyx configuration with its service account — see Phone system.

If you distribute the services across several computers, a domain account is easiest.

Network

• Ports. Which connections between the computers must be open is listed under Ports and connections. The packages add rules for their own ports to Windows Firewall — see Firewall.
• Names. The names of the server, Dispatcher and SQL Server must be resolvable wherever they are entered — see Names and addresses.
• Internet. The server activates licenses via HTTPS at the ilogixx activation server, through a proxy if required; without access, it also works with a file — see Activation. myContactCenter reaches speech services and AI functions via HTTPS at Microsoft Azure.

Phone system

• A phone system that myContactCenter knows — see PBX types.
• A SIP account on the phone system with which the Routing Service logs in; multiple Routing Services share this account. You enter the user name and password in the Routingservice Configurator.
• One extension per agent; the agent’s softphone registers on the phone system with it.
• A headset, or a microphone and speakers, at the agents’ workstations — see Setting up workstations.

Licenses

A new database contains evaluation keys for trying out the system. For operation, you need purchased license keys or Pay-by-Use — see Licenses. A standby server needs its own licenses.