The server(s) must meet the minimum requirements described here.

Operating Systems

• Windows 10 Pro/Enterprise 64-bit
• Windows 11 Pro/Enterprise
• Windows Server 2012 R2 Standard/Datacenter 64-bit
• Windows Server 2016 Standard/Datacenter 64-bit
• Windows Server 2019 Standard/Datacenter 64-bit
• Windows Server 2022 Standard/Datacenter 64-bit

SQL Server Requirements

SQL Server 2019 is installed during a new installation of MiVoice Office Application Suite. During MiVoice Office Application Suite upgrades, the version of SQL Server is not updated. The following versions of SQL are supported for use with MiVoice Office Application Suite:

• SQL Server 2014
• SQL Server 2016
• SQL Server 2019
• SQL Server 2022

Hardware Requirements

The minimum required hardware is dependent on the call rate, the number of Phone Manager clients that will be connected and the Application Suite features in use.

Select the size of system which will cover all of the systems limits.

Software Requirements

The following software is required to be installed:

• Microsoft .NET Framework 3.5 SP1
• Microsoft .NET Framework 4.8
• Windows PowerShell 1.0

Virtualization Environments

Mitel Communication Service is supported in a virtual environment. The supported environments are listed in the table below.

Environment	Supported?
VMWare vSphere ESXi v5.1 or greater
Hyper-V 2012 R2 or greater

Co-Hosting with Xarios Call Recorder

If the MCS is being installed on the same server as a Xarios Call Recorder, it is advisable to change the following settings so that there are no clashes between the products:

Website Port

By default, both products will host their websites on port 80. To access the products individually, one of the websites must be reconfigured within IIS to use a different port. The website can then be accessed by appending the port to the URL:

http://[server_name]:81

Database Backup & Log Archive Directories

By default, both Xarios Call Recorder and MCS use the same folders for database backups and log archives. Both of these locations need to be changed otherwise files will be overwritten.

The MCS requires a 100Mb/1Gb LAN connection that has access to the telephone system. Phone Manager clients will also need access to the MCS over the network. If the server is installed into a Microsoft Active Directory environment then it should be added to the domain, ideally before the MCS software is configured.

To enable users to easily access the server with the website role a valid DNS entry should be created that can then be used when browsing to the server, for example http://communicationserver.

The sections below provide information on all ports used by the system that may need to be opened on server or network based firewalls. Which ports will depend on the features and system configuration.

For information on configuring remote connections through an MBG, please refer to the Engineering Guidelines.

MiVoice Office Application - Host Server

Incoming Ports

The following ports need to be opened on the firewall of the server running the MiVoice Office Application Suite:

Outgoing Ports

MiVoice Office Application Suite makes outgoing connections to the ports listed in the table below. The local port used by the server when making these request will be random.

Internal Use Ports

The following ports are used by internal services on the MiVoice Office Application. Traffic on these ports will not leave the server.

Phone Manager Desktop Client

The table below outlines the network connections made by Phone Manager Desktop clients.

Phone Manager Mobile Client

The table below outlines the network connections made by Phone Manager Mobile clients.

6900 Handsets

The table below outlines the network connections made by 6900 handsets.

Anti-virus software can be installed onto the servers, but the following exclusions must be configured:

• Exclude the server logs
  • %ProgramData%\Mitel\Mitel Communication Service\logs
  • File extensions to exclude: *.log

• Microsoft IIS 7.0 Server
  • Web Server log files should be excluded from scanning. By default, IIS logs are saved in C:\inetpub\logs

• Disable real time / on demand scanning

• Microsoft SQL Server 2008 R2
  • %ProgramFiles%\Microsoft SQL Server\MSSQL\Data (File extensions to exclude: *.mdf,*.ldf, *.ndf, *.bak, *.tm)
  • %ProgramFiles%\Microsoft SQL Server\MSSQL10_50.<Instance Name>\MSSQL\Binn\SQLServr.exe
  • %ProgramFiles%\Microsoft SQL Server\MSSQL10_50.<Instance Name>\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
  • %ProgramFiles%\Microsoft SQL Server\MSSQL10_50.<Instance Name>\OLAP\Bin\MSMDSrv.exe
• Microsoft SQL Server 2014                
  • %ProgramFiles%\Microsoft SQL Server\MSSQL12.MCS\MSSQL\Data (File extensions to exclude: *.mdf,*.ldf, *.ndf, *.bak, *.tm)
  • %ProgramFiles%\Microsoft SQL Server\MSSQL12.MCS\MSSQL\Binn\SQLServr.exe

For servers with the call recording role:

• Disable real time / on demand scanning

• Exclude the recording paths (default path shown)
  • C:\Recordings (or D:\Recordings if there is a 'd' drive)
  • Local <Archive Location>

The system uses email as a key alert, notification and messaging system and needs to be configured correctly. There are five main areas where email is used:

1. Internal Monitoring: There is an internal monitoring system that can report any potential problems or issues when they occur and the system can also send out emails to alert the administrator about these problems.
2. New account details, password reminders for users.
3. Phone Manager Mobile user invitations.
4. For sending reports out from the scheduler
5. For emailing call recordings

See the Email & SMTP section for details.

The system uses the concept of Users to control security and access to the system and to assign a Phone Manager license class in the user's profile.

Each user can have multiple agent IDs and/or extensions associated to it. When a call is handled by this agent/extension the "User" is tagged against this call.

Users can either be created manually, via Active Directory or automatically whenever a new agent ID/extension is created on the PBX. User creation choice needs to be determined before installation to ensure that all calls are tagged correctly.

See the Users and Business Units section for details.

When a call is logged the outside number (caller ID or dialed number) and the inbound direct dial number will be logged against the call. The numbers that are logged may not contain all the digits expected or show extra digits that are not required.

• For outbound calls the dialed number may contain LCR (least cost routing) or Automatic Route Selection (ARS) digits if this is used by the customer
• For outbound calls the number may not have the local area code dialed if this was not dialed when the call was made
• For inbound calls the direct dial number may only contain the last 4 or 6 digits depending on how many digits that the line provider sends

See the Dial Plan section for more details.

The solution integrates with the MiVoice Office 250 PBX system either directly or through a CT Gateway. The solution monitors devices through the System OAI Protocol and logs all call information as well as acting as a proxy for any Phone Manager clients.

See the Phone Systems section for details.

The system stores all of the information relating to the calls and the configuration of the system in a Microsoft SQL Server database installed on the server with the Database role. The system will back up the database every night to a user defined location. This needs to be set to a location that is NOT on the server itself.

If the database fails or becomes corrupted and this backup is available then the database can be easily restored. If the database backup is not available then the call information may be permanently lost.

See the Database Maintenance section for details.

If using the call recording features of the solution then recorded calls need archiving separately from the database. Please refer to the Call Archiving section for more information.