Mitel MiVoice Connect 20.0 SP1 Release Notes

About

Release Note (RN) is intended for Customer Service and Installation Personnel involved in the installation and maintenance of MiVoice Connect 20.0 SP1.

®, ™ Trademark of Mitel Networks Corporation © Copyright 2025, Mitel Networks Corporation. All rights reserved.

Overview

Release Notes contain the most current information on the MiVoice Connect 20.0 Service Pack 1 release and the supported solution lineup.

The release note includes the following:

• Software Enhancements
• Functional Changes
• Installation and Upgrade information
• Fixes for Customer reported issues
• Known Issues

Disabling of Anonymous FTP

Mitel recommends that all customers disable anonymous FTP on all MiVoice Connect servers. As of version 19.3, this can be done from Director via Administration > System > Additional Parameters. This change affects Windows Servers only. Please see the Security Advisory page on mitel.com for more information.

Deprecation of Microsoft Basic Authentication

Connect Client contacts, calendar, and meetings synchronization will stop working on or after October 1st, 2022, when Microsoft disables basic authentication. To continue using calendar integration in the Connect client, customers must upgrade to 19.3 SP1 or greater and use modern authentication (OAuth2) Azure application to leverage Office 365. For detailed integration notes, refer to the MiVoice Connect Application Registration with Azure AD for MS Office 365 and Connect Client Application Registration with Azure AD For MS Office 365 guides.

NOTE: Carefully review the requirements for stepped upgrade in the "Installation and Upgrade Notes" section PRIOR to migrating or upgrading the system.

Microsoft Internet Explorer Notice: Discontinuation of Support

MiVoice Connect 19.3 SP2 does not support the Internet Explorer browser, as Microsoft stopped supporting it on June 15, 2022.

Functional changes to Connect Client in Release 19.3 and Higher

In MiVoice Connect 19.3, the Connect Client was upgraded to the latest Chromium version. As a result, the Outlook voicemail add-in has been deprecated, and it is no longer possible to play voicemail messages from Outlook mail. Two workarounds exist:

• Use Connect Client to play Voicemails.
• Send the Voicemail as an attachment and play it as a media file. This option can be enabled from Director.

The Outlook Contacts Plugin and Outlook UCB Plugin are supported with Single Sign On logins to the Connect Client. These features will NOT work with basic Connect Client PBX authentication. If this functionality is required, disable Automatic Client updates before upgrading to 19.3.

Product Enhancements and Functional Changes

MiVoice Connect PBX 23.30.4100.0

Rocky Linux Edge Gateway

The Edge Gateway has been moved from CentOS to Rocky Linux. This requires a migration to a new virtual appliance. For more information, please see the MiVoice Connect Administration Guide for Edge Gateway.

SG-24A Switches

Starting in version 20.0, SG-24A switches must be configured to boot in FTP mode due to the limited storage on older switches.

Connect 6900 Phone Series Features

6915d Phones Support

Beginning with release 20.0-SP1, MiVoice Connect natively supports 6915d phones with firmware 6.4.0.2014. For more information, see the Sip Phone Guides here.

6900 Phone Firmware

Beginning with release 20.0-SP1, all 69XX phones run on the same firmware 6.4.0.2014. For more information, see the Sip Phone Guides here.

MiVoice Connect Client 214.100.3236.0

Chromium Update for Connect Client

The Connect Client was updated to support the latest Chromium. The updated Connect Client supports Mac OS 14 “Sonoma”.

Before upgrading, please review the Connect Client User Guide and the section "Differences between Old and New Client Interface" before upgrading to 20.0, as some functionality has changed.

Connect IP400 Phone Series Features

Disable SSH on 400 Series phones

SSH has been disabled on 400 phones for security hardening. For information on how to re-enable SSH, please reach out to TAC.

Software Release History

Software and Firmware Versions

Release 20.0 SP1 Build Dates

• PBX Build: Mar 19, 2025
• 6900 Series firmware: Mar 19, 2025
• IP400 series firmware: Mar 19, 2025
• Client Software: Mar 19, 2025

PBX and Client Versions

• PBX Engineering Build number: 23.30.4100.0
• Distributed Voice Server (DVS) version number: 23.30.4100.0
• Connect Client Software version: 214.100.3236.0

PBX Switch Versions

Phone Versions

Application Requirements

Accessing the Latest version of MiVoice Connect Software

All MiVoice Connect releases can be found in Mitel Access Website. Follow the steps below to download the latest version of MiVoice Connect 20.0-SP1:

1. Log in to Mitel MiAccess
2. Click on the Software Download Center in the leftmost pane.
3. You can search by name or Navigate by Categories and find the MiVoice Connect category.
4. Select the appropriate version and follow instructions on the software download page.

Documentation

The documentation mentioned below can be found Here, in the Mitel Document Center.

• Mitel MiVoice Connect Migration Guide
• Mitel MiVoice Connect System Administration Guide
• Mitel MiVoice Connect Planning and Installation Guide
• Mitel MiVoice Connect Maintenance Guide
• Mitel MiVoice Connect Release Build Notice
• Administration Guide for Connect Edge Gateway
• Connect Client User Guide
• Mitel Virtual Mobility Router Installation Guide
• Mitel MiVoice Connect Contact Center Installation Guide
• RAY BAUM’S General Overview and Solution Deployment Guide
• RAY BAUM’S General Overview and Solution Deployment Guide for RedSky
• RAY BAUM’S General Overview and Solution Deployment Guide for Intrado
• MiVoice Connect Ingate SIParator as Teleworker Gateway for MiVoice Connect 6900 Series Configuration Guide
• MiVoice Connect Integration with Microsoft Office 365 using Modern Authentication guide.

The documentation mentioned below for the 6900 IP Series phones can be found Here

• 6900 SIP Phones and Accessories
• Mitel 6900 and IP400 Series IP Phones for MiVoice Connect Functionality Differences

Training

Mitel University Training

Important Links

The MiVoice Connect Release Notes provide essential, current information to ensure a successful migration and installation. This includes supplemental information to the current Mitel documentation suite available on the Mitel support web site MiVoice Connect (Mitel.com).

Mitel product enhancements are submitted to Mitel User Voice. Due to the current lifecycle of MiVoice Connect enhancements are no longer being accepted.

Mitel MiVoice Connect software downloads are available via the Software Download Center. Mitel MiVoice Connect software download require MiAccess login, as well as Export Control Disclaimer completion and submission.

Mitel 6900 and 6900w general desktop release notes can be found on the Mitel KMS site. Select this link

Installation and Upgrade Notes

1. Microsoft Updates

Mitel tests MiVoice Connect with all available Microsoft security patches up to the release date of each MiVoice Connect software version. After installation, Mitel recommends that customers follow their own company's security guidelines for maintaining the Windows Server OS. If a phone system problem occurs, customers may be asked to roll back one or more security patches as a troubleshooting step if it appears to be related to the issue under investigation. To reduce potential impact, it may be advisable to apply only critical and high importance updates.

Note: Mitel strongly advises customers to back up their MiVoice Connect system before opting for any Microsoft updates. Please refer to the Mitel Connect System Administration Guide for backup instructions.

This build was tested with all available and automatically installed Microsoft Windows Server updates (important and recommended) as published on or before April 20, 2024. If you are an existing MiVoice Connect customer, please review the table below to find whether you can install the tested Microsoft updates on your server without upgrading the entire Connect system.

Note: Do not install Windows updates KB5036896 and KB5036899. If you have already installed these updates, remove them immediately as they make it so some services cannot be started.

2. Starting with R20.0 (22.28.8300.0) Features & Changes

• Linux CentOS to Rocky Linux Migration – This is a mandatory migration that will require rebuilding current CentOS devices as Rocky Linux. For more information see the Planning and Installation guide. This change impacts the following devices:
• Linux DVS
• Virtual Service Appliances
• Virtual Switches

3. R1801 and Greater - Windows Server 2016 Installer Prerequisites ISS Version Support

Note: Scripts are available to address the issue that 2016 Server ships with IIS 10 and these PBX prerequisites fail to recognize it as a higher version than IIS 7.0.

• Review Read_first_for_2016.txt and, if necessary, run the following: SetIIS_version.vbs, and ResetIIS_version.vbs, in MiVC_Connect_PBX_Build zip, 2016 Scripts\ folder)

4. Starting with R1711 (21.86.1828.0) Features & Changes

• Linux WindRiver to Linux CentOS Migration – This is a mandatory migration and configuration changes are required to the SCSI Controller before or during the upgrade to this build. It is highly recommended to review the SCSI Change Controller video before upgrading virtual appliances to this build. These changes impact:
• Virtual switch (IP Phone to SIP Trunk)
• Virtual Service Appliance (Collaboration)
• Service Appliance (Collaboration) SA-100 and SA-400
• Linux DVS
• Packaging Changes: There will be no standalone installer for Linux DVS. Linux DVS software will be integrated into HQ and Staging Firmware installers; this will streamline the installation process.

• Virtual appliances (Switches, Linux DVS, and Service Appliance (Collaboration)) will use .iso instead of .ova packaging.
• Administrators are encouraged to follow the updated references for virtual appliances installation, upgrades and backup/recovery:
• Mitel Connect Migration Notes
• Planning and Installation Guide Installation Guide

5. Mitel ST Switches

Dual stage upgrade is not an option on the first migration to MiVoice Connect.

6. Mitel IP Phones

Automatic phone firmware upgrades are on by default. System administrators will need to disable this feature from Director if manual upgrade of IP Phones is desired.

7. Disable the IP Phone Failover

• Disable the IP Phone Failover feature in Director when upgrading from ST13/ST13.x/ST14/ST14.x; otherwise, a failover condition will be induced upon the upgrade. The failback is not automatic. It is a manual process to move the users back to their primary switch and not the spare switch.
• Steps to temporarily disable IP Phone Failover across Sites:
1. Log into Director
2. Go to Quick Look page
3. Ensure the checkbox is checked “Temporarily Disable IP Phone Failover Across Sites”

8. Migration Paths

The following direct server upgrade paths are supported for this release:

NOTES:

• Ensure to upgrade the build to 19.1 SP2 before going to any more recent builds due to database changes.
• Direct Upgrades from ShoreTel releases prior to ST14.2 are not supported.
• Sites running ST14.2 GA30 MUST Migrate to 19.1 SP2 prior installing MiVoice Connect 19.2.
• Please study the updated 14.2-to-Connect Migration Guide for more details.

Older ST 14.2 versions require HQ and DVS Upgrade to latest 14.2 GA30 - 19.50.1000.0

ST14.2 < GA30 → ST14.2 GA30 → MiVC 19.1 SP2 → 19.2 SP3 → 19.3 SP3+ → MiVC 20.0+

ST14.2 GA30 requires a stepped System Upgrade to MiVC 20.0

• Endpoints do not require this intermediate step.
• Voice Switches do not require this intermediate step.

ST14.2 GA30 → MiVC 19.1 SP2 → 19.2 SP3 → 19.3 SP3+ → MiVC 20.0+

All ShoreTel Connect ONSITE and MiVoice Connect versions from 19.1 SP1 or earlier must first upgrade to 19.1 SP2, then to 19.2 SP3+, and finally upgrade to 19.3 SP3 before going to 20.0+.

Any MiVC or Connect ONSITE → MiVC 19.1 SP2 → 19.2 SP3 → 19.3 SP3+ → MiVC 20.0+

Direct MiVoice Connect migrations from versions prior to those listed above are not supported. Prior versions must first upgrade to a supported direct migration path.

In addition,

Mobility versions 7 or 8 must upgrade Mobility version 9:

Mobility 7,8 → Mobility 9 → Mobility 20.0

Contact Center 8 or 9 must upgrade to Connect Contact Center:

Contact Center 8,9 → Connect Contact Center

Migration from Windows Server 2008 (32 bit) or earlier to a supported Windows Server OS version must be done prior to migrating to MiVoice Connect.

9. The UC20 Windows server is not supported with MiVoice Connect. For more information, please refer to the Mitel Connect Migration Notes that can be found here:

10. Upon the release of CentOS 7.5 it has been discovered that some LDVSs will have a maximum MTU size of 1400. This will cause communication issues with the HQ server. For more information please see our knowledgebase article for partners here, and for enterprise customers here.

NOTE: Some systems were upgraded to Connect from earlier versions of 14.2 and did not perform an interim upgrade to 14.2 GA30. Admins may find these fail a Connect-to-Connect upgrade directly to 19.2 or higher, and the installation rolls back unexpectedly. Performing an intermediate upgrade stop at 19.1 SP2 before moving to 19.2 or higher has been proven to resolve the issue and allow the upgrade to complete. After the stop at 19.1 SP2 customers can continue to 19.2 or higher without incident.

Mitel 6900 Phone Upgrades from 19.2 GA or older

When upgrading the Mitel 6900-series phones to phone firmware 6.0 or greater which was first released with 19.3, some phones may fail to upgrade. The problem occurs because temporary log files are not cleared before downloading the new firmware, which can cause insufficient internal working storage for the update.

To prevent this problem, Mitel recommends upgrading all 6900-series phones to updated firmware build version 5.2.1.2130 before the system upgrade to 19.3. Administrators may also choose to manually reboot the phones then promptly upgrade to the new 19.3 firmware before the log files accumulate. In some cases, multiple phone reboots have been required.

DHCP Scope Considerations for 6900 Phone Series

MiVoice Connect 19.3 requires the DHCP scope changes announced in Release 19.2. In releases of MiVoice Connect before 19.2, the recommended guidance for DHCP option 156 was to configure the “Config Server” parameter with IP address of HQ Server. In Release 19.2 and onward, an FQDN is now required in the DHCP record if Subject Alternate Name (SAN) is root Certified. In cases where DHCP Scope 156 is not used, administrators must update the config server setting on 6900 sets manually, from IP to FQDN. If the IP address is used, users may encounter 6900 registration or boot issues after the upgrade to 19.3 or later.

• NTP Server settings must also be specified in Option 42 of the DHCP scope for 6900 phones to validate certificate expiration dates. For more information, see the MiVoice Connect Maintenance Guide.

Resolved Issues

The list below contains resolved issues for MiVoice Connect 20.0-SP1

Known Product Limitations

Document Revisions