Avaya Support Agreement

In writing the “Crossroads” blog, I wanted to point out that Avaya Third Party Maintenance (TPM) and support are sometimes the best choice for Avaya system owners, but there are times when this is not the case. Where TPM is well suited, service levels can be higher and costs lower. We believe TPM is ideal for all Avaya system owners who use systems that are at the end of Manufacturer Support (EoMS) as they consider moving to a unified communications solution like Microsoft Teams. Avaya makes available to end users a software license in accordance with Avaya`s license agreement (“EULA” or “Software License Terms”) and in accordance with its contractual relationship with its distribution partners. Under these agreements, all channel partners are required to extend the applicable software license terms to the end user. Still, there are times when the best choice is to stay with Avaya for maintenance and support of Avaya systems. Some Avaya system owners consider the Avaya solution to be the best long-term choice and often choose to upgrade their Avaya systems, which inevitably means they acquire the mandatory software support that comes with each upgrade. As the latest version of Avaya (currently CM 7) is what we call “patch-dependent”, Avaya is actively developing patches for this system. To obtain these fixes, the system owner must have an Avaya software support contract. United States – bpccexpress@avaya.comAmericas International – CobcCala@avaya.com Asia Pacific – apacbillindia@avaya.comEMEA – emeacc@avaya.com Count on ScanSource to teach you all about the latest Avaya Office IP support offering.

For older systems, Avaya has made it clear that no further patches will be developed. If the owners of the Avaya system remain at the OEM for system maintenance and support, Avaya will naturally continue to require those customers to acquire avaya-support with an Avaya support contract, although the owner of the old Avaya system will not pay anything in the end. .

Comments are closed.