Avaya will be deleting all software below 6.3.11 3

[jimbojimbo]

Just as an FYI,

Avaya is supposed to be deleting all software below CM6.3.11 in September from PLDS. For everyone out there I strongly suggest you download archive, copy, backup, store, and use any other process to maintain a copy of your software (including phone firmware). For those on some version of 6.x below 6.3.11.1 I strongly suggest you plan on upgrading immediately. I would recommend changing from the .124 base load to the .141 base load (6.3.111 or higher). Do not expect to receive reasonable support from Avaya for any release below the 6.3.11. For those on CM5.x who have any PCI-DSS compliance requirements I would suggest you plan now for an upgrade to CM7. Even for those without PCI-DSS requirements I suggest the same.

Some things to keep in mind for upgrading

1. MCC/SCC/CMC cabinets are not longer supported and must be replaced when upgrading to CM7.x. NOTE: After extensive back and forth with Avaya this was clarified in the latest CM7 Offer Definition.
2. AES 6.3 deprecated the Client 4.2 SDK. Many legacy CTI integrations will fail when AES is upgraded. Plan to upgrade your adjunct CTI applications accordingly. (NOTE: AES Machine Preserving High Availability (MPHA)is available on AES 6.3 running on System Platform but is not available when migrating to VMware or Avaya's Appliance Virtualization Platform (AVP). Geo-Redundant High Availability (GRHA) is available on VMware.
3. CMS 17 or 18 is required with CM7.x. Unlike the last several releases of CMS the current version is not backwards compatible. CMS 18 is only compatible back to CM5.2.1
4. Be prepared to have a lengthy discussion with your vendor on the use of certificates, TLS 1.0 versus 1.1/1.2 (PCI-DSS 3.2 requires migration off of TLS 1.0 by 2018), SRTP (AES encryption standards relative to the November update of DISA SP800-131Ar1), and the use of personal certificates with one-X Communicator and the upcoming release of Avaya Communicator 3.0 and the Availability of Client Certificate Validation on Session Manager. For those in a Microsoft AD environment I strongly suggest using System Manager as a SubCA of the Enterprise RootCA or as a stand alone CA with the System Manager RootCA certificate imported into the default Group Policy Object.
5. Upgrading of Hardphones and the requirement to import Root Certificates vi the 46xxsettings.txt file and the limitation of importing (6) CA certificates.

These are just a few of the majors.

 

[gwebster]

Full PSN from Avaya can be read at

http://support.avaya.com/css/P8/documents/101026404.

 

[janni78]

You'll still be able to get older software with latest service pack until Nov 30 2017, although planning to upgrade is a good idea.

For CM 5.x and 6.x releases earlier/lower than 6.3, the base ISO images and final Service Packs within each release will still be
available for download on Avaya Support and PLDS until November 30th, 2017. In addition, the latest vintage firmware for the
G250/G350, G700 and IG550 Media Gateways will be available until November 30th, 2017. This includes the following:

 CM 6.3.0.0 ISO image
 CM 6.2 ISO image and Service Pack 8 (21388)
 CM 6.0.1 ISO image and Service Pack 11.01 (21061)
 CM 6.0 ISO image and Service Pack 3.01 (18856)
 CM 5.2.1 ISO image and Service Packs 13 (19880) and 18 (21656)
 CM 5.2 ISO image and Service Pack 4 (17834)
 CM 5.1.2 ISO image and Service Pack 4 (17871)
 CM 5.1.1 ISO image and Service Pack 3 (17105)
 CM 5.1 ISO image and Service Pack 1 (15962)
 CM 5.0 ISO image and Service Pack 3 (15759)
 G250/350 Media Gateway firmware vintage 30.27.1
 G700 Media Gateway firmware vintage 30.27.1
 IG550 Integrated Gateway firmware vintage 30.27.1

"Trying is the first step to failure..." - Homer

 

[jfh9219]

jimbojimbo,

thanks for the valuable info. can you give a link to the CM7 Offer Definition that speaks to the MCC issue?
It's not that I want to keep them it is just a lot of work to do at the same time as a CM5.2 to CM7 upgrade.

 

[jimbojimbo]

jfh9219

The Avaya Product Definitions are on the Partner Portal and only available to the Avaya Business Partners. Here is the specific section. Also note the G700/G350/G250 do not support the new S8300E.

6.7.7. Gateways
Supported gateways include the following:
G430
G450
G650
The following legacy gateways were tested with Aura 7.0 but they are no longer under manufacturer support.
G350 + S8300D
G250 + S8300D
G700 + S8300D
Note that MCC and SCC are not supported with Avaya Aura® 7.0