The following is an excerpt from Avaya’s announcement:
End of Manufacturer Support (EoMS): Avaya will no longer provide on this software release Bug Fix, Patches, Design Root Cause Analysis, Feature Enhancements, or Security Updates (i.e. if a new vulnerability is identified customer must move to the current software release level for resolution).”
Once a system has reached EoMS, Avaya will no longer develop patches for it. Parts will also be difficult to acquire. Avaya will replace them, but only on a "best-effort" basis. Avaya support, therefore, may not be the most cost-effective option for users of systems past EoMS.
Many Avaya users have chosen to upgrade to the CM8. At the same time, other users are looking for a way to keep their systems running while reducing costs.
Most Avaya users will eventually transition to the cloud and deploy a unified communication (UC) solution. These include Microsoft Teams, Cisco WebEx, and Zoom. Transitioning to one of these solutions will take time, especially for large organizations.
Your organization will need to maintain communications during this transition. You can do so by continuing to use your Avaya system beyond its EoMS date. To maintain efficiency, however, you'll need to make sure it still runs with minimal downtime.
If you want to keep your CM7 after EoMS, you won't get the support you need from Avaya. You'll need help from a Third-Party Maintenance provider, like Continuant, to make sure it runs like the day you bought it. For more than 25 years, we have been offering world-class PBX support to organizations across the globe. We've helped them save money by dramatically extending the life of their legacy systems.
* Editor's Note: This article was originally published in April 2020 and has been revamped and updated for accuracy and comprehensiveness.
Chief Sales Officer and Co-Founder Bruce Shelby, began his career in the telecom industry in 1984, holding various positions in sales and sales management. In 1996, Shelby joined Doug Graham in founding the company that would later be known as Continuant: Telecom Labs, Inc. (TLI).