Communication Manager Software & Firmware Compatibility Matrix

April 3rd, 2006

Communication Manager Software & Firmware Compatibility Matrix

May 1st, 2006


Table of Contents

Communication Manager Release 3.1 & 3.1.1 Compatibility

Media Gateways and Media Modules

G700 Media Gateway

G350 Media Gateway

G250 & G150 Media Gateways

TN Circuit Packs

Telephones

Communication Manager Service Packs

S8500B SAMP Firmware

CM Software Upgrade Path

SES Compatibility

Communication Manager Release 2.2.2 Compatibility

Media Gateways and Media Modules

G700 Media Gateway

G350 Media Gateway

G250 & G150 Media Gateways

TN Circuit Packs

Telephones

Communication Manager Service Packs

S8500B SAMP Firmware

CM Software Upgrade Path

SES Compatibility

Software/Firmware Compatibility Matrix

Software/Firmware Compatibility Matrix

S8100 MEDIA SERVER

G150 MEDIA GATEWAY COMPATIBILITY

G250 (MGP only), G350, & G700 MEDIA GATEWAY COMMON FIRMWARE

G350 MEDIA GATEWAY SPECIFIC FIRMWARE

S8xx0 SERIES MEDIA SERVERS

DEFINITY SERVER SI / CSI / R

Communication Manager 1.x Releases

Supported Communication Manager Upgrade Paths

Field Load Upgrade Paths

Upgrade Paths for CM 3.1.1 and Earlier Releases

SIP Enablement Services & CM Compatibility

General Software / Firmware Compatibility Guidelines

E-Notifications

Circuit Pack Firmware Compatibility

IP Interface Circuit Pack Firmware Available on the Communication Manager 3.x Software CD

The Latest Firmware for all Programmable TN Circuit Packs:

TN2214CP

TN2224CP

TN2302AP

TN2312AP

TN2313AP

TN2464BP

TN2501AP

TN2602AP

TN464GP

TN771DP

TN793CP

TN799DP

Media Gateway, LSP/ESS, & Primary Server Compatibility

Gateway/Server/LSP/ESS Compatibility Matrix

G700 Media Gateway Compatibility Issues

Media Module 711 Firmware and Hardware Dependencies

Telephone Software Compatibility

2400 Digital Telephones

All 46xx IP Telephones

6400 Digital Telephones

8400 Digital Telephones

IP Agent

IP Softphone

IP Softphone for Pocket PC

Softconsole

Telephone Software Dependencies

Service Pack Compatibility

Service Packs for all releases:

Communication Manager 2.0

Communication Manager 2.0.1

Communication Manager 2.1

Communication Manager 2.1.1

Communication Manager 2.2

Communication Manager 2.2.1

Communication Manager 2.2.2

Communication Manager 3.0

Communication Manager 3.0.1

Communication Manager 3.1

Communication Manager 3.1.1

Communication Manager Installations & Upgrades

Communication Manager 1.x to Communication Manager 3.x Upgrades

Communication Manager 2.x to Communication Manager 3.x Upgrades

Integrated Management

Fault and Performance Manager

MultiSite Administration

Network Management

Proxy Agent

Site Administration

Voice Announcement Manager

VoIP Monitoring Manager

Integrated Management Dependencies

Communication Manager Release 3.13.1.1 Compatibility

If Communication Manager 3.1 or 3.1.1 is running on a primary server, the following information is used for detailed compatibility information. All software and firmware updates shown are available on support.avaya.com.

Media Gateways and Media Modules

G700 Media Gateway

Component / G700 Gateway / MM760 / MM720 / MM717 / MM712 / MM711 / MM710 / MM312 / P330 FW / P330 Device Manager
Firmware Vintage / 25.23.0 / 60 / 6 / 4 / 7 / HW 30+: NA
HW 20-29: 68
HW 7-19: 24
HW 3-6: 17 / 14 / 4 / 4.1.6 / 4.6.6 or 4.6.9

G350 Media Gateway

Component / G350Gateway / MM
722 / MM
720 / MM
717 / MM
714 / MM
712 / MM
711 / MM
710 / MM
312 / Analog / Embedded Web
Firmware Vintage / 25.23.0 / 2 / 6 / 4 / 68 / 7 / HW 30+: NA
HW 20-29: 68
HW 7-19: 24
HW 3-6: 17 / 14 / 4 / 68 / 3.1.8

G250 & G150 Media Gateways

Component / G250Gateway / G150 Gateway
Firmware Vintage / 25.23.0 / 3.0(104)

TN Circuit Packs

TN Board / TN
2602 / TN
2501 / TN 2464 / TN
2313 / TN
2312 / TN
2302 / TN 2224 / TN
2214 / TN
799 / TN
793 / TN
771 / TN
464
FW Vintage / Duplex: 23
Simplex: 12 or 23 / 10 / 18 / 48 / 30 / HW 3-10: 93
HW 11+: 110 / 15 / 15 / 17 / 7 / 19 / 18

Telephones

Phone / 2400 / IP Soft-phone / SIP Soft-phone / IP Agent / IP Soft-phone Pocket PC / Soft-console / 4601
4602
4602
SW
4620 / 4602
4602SW
4610SW
4620SW
4621SW / 4610SW
4620SW
4621SW
4622SW / 4625
SW / 4630
4630SW / 4690 / 4606
4612
4624
Phone
SW / 2420: R4
2410: R2 / 5.2 / 2.1 / 6 / 2.3.1 / 1.5.3 / 2.3 / SIP 2.2.2 / 2.4 / 2.5 / 2.0.3 / 2.0 / 1.8.3

Communication Manager Service Packs

The latest Communication Manager 3.1.1 Service Pack is 11640 (01.1.628.7-11640). For S8720 Media Servers running Communication Manager 3.1.1 using Software Duplication, Service Pack 11641 (01.1.628.7-11641) should be used instead of 11640. The latest CM 3.1 Service Pack is 11410 (01.0.628.6-11410).

S8500B SAMP Firmware

The required S8500B SAMP firmware for Communication Manager 3.1/3.1.1 is SAMP FW R2.

CM Software Upgrade Path

Media Servers running Communication Manager 3.1 can upgrade to 3.1.1 and later releases only. Media Servers running CM 3.1.1 can upgrade to 3.1.2 (not yet launched) and later releases only.

SES Compatibility

Media Servers running CM 3.1/3.1.1 are compatible with SES 2.1 (Presence/IM-Only), 3.0, and 3.1.
Communication Manager Release 2.2.2 Compatibility

If Communication Manager 2.2.2 is running on a primary server, the following information is used for detailed compatibility information. All software and firmware updates shown are available on support.avaya.com.

Media Gateways and Media Modules

G700 Media Gateway

Component / G700 Gateway / MM760 / MM720 / MM717 / MM712 / MM711 / MM710 / MM312 / P330 FW / P330 Device Manager
Firmware Vintage / 25.23.0 / 60 / 6 / 4 / 7 / HW 30+: NA
HW 20-29: 68
HW 7-19: 24
HW 3-6: 17 / 14 / 4 / 4.1.6 / 4.6.6 or 4.6.9

G350 Media Gateway

Component / G350Gateway / MM
722 / MM
720 / MM
717 / MM
714 / MM
712 / MM
711 / MM
710 / MM
312 / Analog / Embedded Web
Firmware Vintage / 25.23.0 / 2 / 6 / 4 / 68 / 7 / HW 30+: NA
HW 20-29: 68
HW 7-19: 24
HW 3-6: 17 / 14 / 4 / 68 / 3.1.8

G250 & G150 Media Gateways

Component / G250Gateway / G150 Gateway
Firmware Vintage / 25.23.0 / 3.0(104)

TN Circuit Packs

TN Board / TN
2602 / TN
2501 / TN 2464 / TN
2313 / TN
2312 / TN
2302 / TN 2224 / TN
2214 / TN
799 / TN
793 / TN
771 / TN
464
FW Vintage / 12 or 23 / 10 / 18 / 48 / 30 / HW 3-10: 93
HW 11+: 110 / 15 / 15 / 17 / 7 / 19 / 18

Telephones

Phone / 2400 / IP Soft-phone / SIP Soft-phone / IP Agent / IP Soft-phone Pocket PC / Soft-console / 4601
4602
4602
SW
4620 / 4602
4602SW
4610SW
4620SW
4621SW / 4610SW
4620SW
4621SW
4622SW / 4625
SW / 4630
4630SW / 4690 / 4606
4612
4624
Phone
SW / 2420: R4
2410: R2 / 5.2 / 2.1 / 6 / 2.3.1 / 1.5.3 / 2.3 / SIP 2.2.2 / 2.4 / 2.5 / 2.0.3 / 2.0 / 1.8.3

Communication Manager Service Packs

The latest Communication Manager 2.2.2 Service Pack is 11543 (02.2.122.0-11543).

S8500B SAMP Firmware

The required S8500B SAMP firmware for Communication Manager 2.2.2 is SAMP FW R1.

CM Software Upgrade Path

Media Servers running Communication Manager 2.2.2 can upgrade to 3.1.2 (not yet launched) and later releases only.

SES Compatibility

Media Servers running Communication Manager 2.2.2 are compatible with SES 2.1, 3.0, and 3.1.

Software/Firmware Compatibility Matrix

The information presented in the matrix shows the latest firmware available and recommended at the time this document is published. Due to the frequency that new firmware becomes available it is possible that this document is temporarily out of date. Therefore, support.avaya.com should always be checked for the very latest software and firmware available:

Communication Manager 2.0 and later releases are not available for the DEFINITY Server R.

Communication Manager 2.1 and later releases are not available for the S8100 Media Server.

Communication Manager 2.1 and later releases do not install or run on an S8300A Media Server. An S8300B or later server must be used.

Communication Manager 3.0 and later releases are not available for the DEFINITY Server SI.

Communication Manager Software / Firmware Compatibility Matrix

S8100 MEDIA SERVER

CM
Release / Launched Load / TN799DP
(C-LAN)
FW / TN2302AP (Prowler)
FW / TN2501AP (VAL)
FW
CM 2.0 / R012c.00.0.219.0
Offer S8100-2.0-219.0 / V15 or later
See TN799DP: Link / HV3-6: V93 or later
HV11+: V107 or later
See TN2302AP: Link / V10 or later
See TN2501AP: Link
CM 2.0.1 / R012c.00.1.222.0 Offer S8100-2.0.1-222.0 / V15 or later
See TN799DP: Link / HV3-6: V93 or later
HV11+: V107 or later
See TN2302AP: Link / V10 or later
See TN2501AP: Link
CM 2.1 and Later Releases / Not Available

G150 MEDIA GATEWAY COMPATIBILITY

CM
Release / G150 Media Gateway Version
CM 2.2 and Later / 3.0(104)

G250 (MGP only), G350, & G700 MEDIA GATEWAY COMMON FIRMWARE

CM Release / G250 G350 G700 FW / MM 710 FW / MM 711 FW / MM 712 FW / MM 717 FW / MM 720 FW / MM 760 FW / P330 FW DM
CM 2.0 / G350: V25.23.0
G700: V25.23.0 / V14 / HV3-6: V17
HV7: V24
HV20+:V68 / V7 / N/A / V6 / V60 / 4.1.6
4.6.6
CM 2.0.1 / G350: V25.23.0
G700: V25.23.0 / V14 / HV3-6: V17
HV7: V24
HV20+:V68 / V7 / N/A / V6 / V60 / 4.1.6
4.6.6
CM 2.1 / G350: V25.23.0
G700: V25.23.0 / V14 / HV3-6: V17
HV7: V24
HV20+:V68 / V7 / V4 / V6 / V60 / 4.1.6
4.6.6
CM 2.1.1 / G350: V25.23.0
G700: V25.23.0 / V14 / HV3-6: V17
HV7: V24
HV20+:V68 / V7 / V4 / V6 / V60 / 4.1.6
4.6.6
CM 2.2 / G350: V25.23.0
G700: V25.23.0 / V14 / HV3-6: V17
HV7: V24
HV20+:V68 / V7 / V4 / V6 / V60 / 4.1.6
4.6.6
CM 2.2.1 / G350: V25.23.0
G700: V25.23.0 / V14 / HV3-6: V17
HV7: V24
HV20+:V68 / V7 / V4 / V6 / V60 / 4.1.6
4.6.6
CM 3.0 / All: V25.23.0 / V14 / HV3-6: V17
HV7: V24
HV20+:V68 / V7 / V4 / V6 / V60 / 4.1.6
4.6.6
CM 3.0.1 / All: V25.23.0 / V14 / HV3-6: V17
HV7: V24
HV20+:V68 / V7 / V4 / V6 / V60 / 4.1.6
4.6.6
CM 3.1 & 3.1.1 / All: V25.23.0 / V14 / HV3-6: V17
HV7: V24
HV20+:V68 / V7 / V4 / V6 / V60 / 4.1.6
4.6.6

G350 MEDIA GATEWAY SPECIFIC FIRMWARE

CM Release / G350 Analog FW / MM312 FW / MM714 FW / MM722 FW
CM 2.0 / V68 / V4 / V68 / V2
CM 2.0.1 / V68 / V4 / V68 / V2
CM 2.1 / V68 / V4 / V68 / V2
CM 2.1.1 / V68 / V4 / V68 / V2
CM 2.2 / V68 / V4 / V68 / V2
CM 2.2.1 / V68 / V4 / V68 / V2
CM 3.0 / V68 / V4 / V68 / V2
CM 3.0.1 / V68 / V4 / V68 / V2
CM 3.1 & 3.1.1 / V68 / V4 / V68 / V2

S8xx0SERIES MEDIA SERVERS

CM Release / Launched Load / S8500B SAMP FW / Latest Service Pack / TN799
(C-LAN)
FW / TN2302 (IP Media Processor)
FW / TN2312 (IPSI)
FW / TN2501 (VAL) FW / TN2602 (IP 320) FW
CM 2.0 / R012x.00.0.219.0 / 6999
See
Communication Manager 2.0
Link / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V30
See TN2312AP: Link / V10
See TN2501AP: Link / Not Available
CM 2.0.1 / R012x.00.1.221.1 / 8182
See
Communication Manager 2.0.1
Link / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V30
See TN2312AP: Link / V10
See TN2501AP: Link / Not Available
CM 2.1 / R012x.01.0.411.7 / 7561
See
Communication Manager 2.1
Link / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V30
See TN2312AP: Link / V10
See TN2501AP: Link / Not Available
CM 2.1.1 / R012x.01.1.414.1 / 8400
See
Communication Manager 2.1.1
Link / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V30
See TN2312AP: Link / V10
See TN2501AP: Link / Not Available
CM 2.2 / R012x.02.0.111.4
S8500B SAMP FW = R1 / 10218
See
Communication Manager 2.2
Link / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V30
See TN2312AP: Link / V10
See TN2501AP: Link / Not Available
CM 2.2.1 & 2.2.2 / R012x.02.1.118.1
R012x.02.2.122.0
S8500B SAMP FW = R1 / 2.2.1: 10885
2.2.2: 11543
See
Communication Manager 2.2.1
Communication Manager 2.2.2
Links / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V30
See TN2312AP: Link / V10
See TN2501AP: Link / Not Available
CM 3.0 / R013x.00.0.340.3
S8500B SAMP FW = R1 / 10678
10673 (SIP)
See
Communication Manager 3.0
Link / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V30
See TN2312AP: Link / V10
See TN2501AP: Link / V12 or V23
See TN2602AP: Link
CM 3.0.1 / R013x.00.1.346.0
S8500B SAMP FW = R1 / 10986
See
Communication Manager 3.0.1
Link / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V30
See TN2312AP: Link / V10
See TN2501AP: Link / V12 or V23
See TN2602AP: Link
CM 3.1 & 3.1.1 / R013x.01.0.628.6
R013x.01.1.628.7
S8500B SAMP FW = R2 / 3.1: 11410
3.1.1: 11640
See
Communication Manager 3.1
Communication Manager 3.1.1
Links / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V30
See TN2312AP: Link / V10
See TN2501AP: Link / V12 or V23
See TN2602AP: Link

DEFINITY SERVER SI / CSI / R

CM Release / Launched Load / TN799DP
(C-LAN)
FW / TN2302AP
(IP Media Processor)
FW / TN2501AP
(VAL)
FW
CM 1.3.2 / R011r.03.2.536.1
R011i.03.2.536.1 / See TN799DP: Link / See TN2302AP: Link / See TN2501AP: Link
CM 2.0 / Not available for R
R012i.00.0.219.0 / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V10
See TN2501AP: Link
CM 2.0.1 / Not available for R
R012i.00.1.221.1 / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V10
See TN2501AP: Link
CM 2.1 / Not available for R
R012i.01.0.411.7 / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V10
See TN2501AP: Link
CM 2.1.1 / Not available for R
R012i.01.1.414.1 / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V10
See TN2501AP: Link
CM 2.2 / Not available for R
R012i.02.0.111.4 / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V10
See TN2501AP: Link
CM 2.2.1 & 2.2.2 / Not available for R
R012i.02.1.118.1
R012i.02.2.122.0 / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V10
See TN2501AP: Link
CM 3.0 / Not available for R
Not available for SI
R012i.00.0.340.3 / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V10
See TN2501AP: Link
CM 3.0.1 / Not available for R
Not available for SI
R012i.00.1.346.0 / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V10
See TN2501AP: Link
CM 3.1 & 3.1.1 / Not available for R
Not available for SI
R013i.01.0.628.6
R013i.01.1.628.7 / V17
See TN799DP: Link / HV3-6: V93
HV11+: V110
See TN2302AP: Link / V10
See TN2501AP: Link

Communication Manager 1.x Releases

Communication Manager 1.x releases are now End of Manufacturer Support. However, 1.3.2 information is included in the compatibility matrix above for the DEFINITY Server R because it is the last load supported on a DEFINITY Server R.

Supported Communication Manager Upgrade Paths

Due to the overlapping nature and timing of Communication Manager Release launches, it is not always possible to upgrade from a lower release to a higher release without the possibility of encountering corruption or having a needed fix or enhancement not be availablein the higher release. Therefore, not all Communication Manager upgrade paths are supported. The information presented in this section should be used to determine supported Communication Manager upgrade paths.

Field Load Upgrade Paths

Communication Manager Field Load upgrade paths are not covered in this document due to the large number of field loads that are available. When upgrading from a Communication Manager Field Load to a later release/load the upgrade path should be verified by escalating to Global Technical Services (GTS) prior to the upgrade to ensure the upgrade path is supported.

Upgrade Paths for CM 3.1.1 and Earlier Releases

A server running thisrelease… / …can upgrade to this release.
A primary server running this release… / …requires LSP/ESS to beonthe same release as the primary server, or else on this release.
CM 2.0 (R012x.00.0.219.0) / Same or CM 2.1 & Later (R012x.01.0.411.7 & Later)
CM 2.0.1 (R012x.00.1.221.1) / Same or CM 2.1 & Later (R012x.01.0.411.7 & Later)
CM 2.1 (R012x.01.0.411.7) / Same or CM 2.2 & Later (R012x.02.0.411.7 & Later)
CM 2.1.1 (R012x.01.1.414.1) / Same or CM 2.2 & Later (R012x.02.0.411.7 & Later)
CM 2.2 (R012x.02.0.111.4) / Same or CM 3.0 & Later (R013x.00.0.340.3 & Later)
(CSI Only: R013i.00.0.340.5 & Later)
CM 2.2.1 (R012x.02.1.118.1) / Same or CM 3.0.1 & Later (R013.00.1.346.0 & Later
CM 2.2.2 (R012x.02.2.122.0) / Same or CM 3.1.2 (not available yet) & Later (R013i.01.2.632.0 & Later)
CM 3.0 (R013x.00.0.340.3)
(CSI Only: R013i.00.0.340.5) / Same or CM 3.0.1 & Later (R013i.00.1.346.0 & Later)
CM 3.0.1 (R013i.00.1.346.0) / Same or CM 3.1 & Later (R013i.01.0.628.6 & Later)
CM 3.1 (R013i.01.0.628.6) / Same or CM 3.1.1 & Later (R013i.01.1.628.7 & Later)
CM 3.1.1 (R013i.01.1.628.7) / Same or CM 3.1.2 (not available yet) & Later (R013i.01.2.632.0 & Later)

Note: It is recommended that an LSP or ESS only run on a more recent release/load of Communication Manager than the primary Media Server for a limited time. The expectation is that in systems with many LSP/ESS servers Communication Manager software upgrades might occur slowly over a period of time, and that eventually the primary Media Server will be upgraded to the same release running on the LSP/ESS servers.

SIP Enablement Services & CM Compatibility

CM & SES / CM 3.1.x / CM 3.0.x / CM 2.1.1 & 2.2.x / CM 2.0 back to DEFINITY R9.5
SES 3.1 / YES / YES / YES / IM-Only
SES 3.0 / YES / YES / YES / IM-Only
SES 2.1 / IM-Only / YES / YES / IM-Only

A value of YES indicates support for both telephony and Presence/IM. A value of IM-Only indicates support for stand alone SES deployments with Presence/IM only.

General Software / Firmware Compatibility Guidelines

The G150, G250, G350 & G700 Media Gateways, media modules, embedded P330 Ethernet switching system, various circuit packs, and many endpoints are designed to allow remote firmware upgrades once they’ve been installed in the field. Furthermore, the S8xx0 Series Media Servers allow Communication Manager software to be updated via downloadable service packs.

New versions of firmware for media gateways, media modules, circuit packs, and endpoints continue to be developed and made available on the support web pages on an ongoing basis. New versions of firmware usually contain support for new functionality as well as fixes for known issues with previous firmware vintages. Therefore, it is strongly recommended to update firmware as new vintages become available. However, it is not required, especially if a system is experiencing no problems on the current version of firmware and new functionality is not desired.

Whenever updating vintages of firmware and software, it is extremely important to review the readme file or Product Correction Notice (PCN) associated with the firmware or software update. Readme files and PCNs document any known caveats or issues with compatibility. While the general rule is that the latest firmware is backwards compatible with older Communication Manager releases, there are sometimes exceptions and these exceptions, when known, are documented in readme files and/or PCNs. Refer to specific sections in this document for additional compatibility details.

When upgrading Media Servers, LSPs, and ESSs to new releases of Communication Manager, the upgrade path must be checked to ensure the currently running release can upgrade to the new release without experiencing translation corruption or loss of functionality. See the Supported Communication Manager Upgrade Pathsand Gateway/Server/LSP/ESS Compatibility Matrixsections for additional details.

For S8xx0 Series Media Servers the latest service pack must be applied. For additional information see the Service Pack Compatibilitysection.

E-Notifications

To be automatically notified via e-mail when new service packs and firmware updates are available, you can subscribe to receive all PCN notifications via My E-Notifications on support.avaya.com.

Circuit Pack Firmware Compatibility

IP Interface Circuit Pack Firmware Available on the Communication Manager 3.x Software CD

The latest circuit pack firmware available at the time of launch is on the Communication Manager software CD. However, it is possible that the firmware on the CD is out-of-date, so the support web pages should always be checked for the latest firmware.

Avaya’s support web site should be checked for the latest firmware available for the following programmable circuit packs:

  • TN2214CP
  • TN2224CP
  • TN2302AP for hardware vintages 3 and 11
  • TN2312AP and BP
  • TN2313AP
  • TN2464BP
  • TN2501AP
  • TN2602AP
  • TN464GP
  • TN711DP
  • TN793CP
  • TN799DP

For firmware downloadable (programmable) circuit packs, the latest firmware available for the circuit pack should be used regardless of the release of Communication Manager software being used. However, it is not necessary to update firmware that is working well unless there is a compelling reason to do so.

Whenever firmware is updated, the readme file should be checked for specific Communication Managercompatibility issues. The latest IP Interface circuit pack firmware, readme files, and instructions for installing downloadable firmware are found at the links given below:

The Latest Firmware for all ProgrammableTN Circuit Packs:

TN2214CP

TN2224CP

TN2302AP

TN2312AP

TN2313AP

TN2464BP

TN2501AP

TN2602AP

TN464GP

TN771DP

TN793CP

TN799DP

Media Gateway, LSP/ESS, & Primary Server Compatibility

When upgrading configurations with a Media Gateway, the Media Gateway firmware should always be upgraded before Communication Manager Software is upgraded.

In general, media gateway and media module firmware is compatible with the current major release of Communication Manager and the previous major release (also known as N–1 compatibility). For example, media gateway and media module firmware released with Communication Manager 3.0.1 is intended to be compatible with Communication Manager 3.x and 2.x software releases. However, in practice, this is not always the case. Therefore, theinformation in this section provides more detailed compatibility information.

When upgrading configurations with an LSP or ESS, the LSP/ESS Communication Manager Software should always be upgraded after all Media Gateways are upgraded and before the primary Media Server Communication Manager Software is upgraded.

LSP and ESS upgrades are constrained by valid Communication Manager upgrade paths. This means that if an LSP or an ESS is being upgraded to a more recent release of Communication Manager than is running on the primary server, the more recent release must be a valid upgrade path for the release running on the primary server. See the Supported Communication Manager Upgrade Paths section for a mapping of valid Communication Manager upgrade paths.

The latest media gateway and media module firmware available at the time of launch is on the Communication Manager software CD. However, it is possible that the firmware on the CD is out-of-date, so the support web pages should always be checked for the latest firmware.

Whenever firmware is updated, the readme file or PCN should be checked for specific Communication Managercompatibility issues. Avaya’s support web site should be checked for the latest firmware available for a given media module. The latest G250, G350, & G700 Media Gateway firmware, media module firmware, readme files, and instructions for installing media gateway firmware are found at the following link:

The G350 Media Gateway is not supported in configurations with primary Media Servers and LSPs running Communication Manager Releases earlier than 2.0.

The G250 Media Gateway is not supported in configurations with primary Media Servers and LSPs running Communication Manager Releases earlier than 3.0.

The G150 Media Gateway is not supported in configurations with primary Media Servers and LSPs running Communication Manager Releases earlier than 2.2.

Gateway/Server/LSP/ESS Compatibility Matrix

YES = Compatible
NO = Not Compatible / Primary Media Server Running 1.3.x CM Software / Primary Media Server RunningCM 2.x Software / Primary Media Server RunningCM 3.x Software / LSP on 1.3.x CM Software / LSP on 2.x CM Software / LSP/ESS on 3.x CM Software
23.xx.x Gateway Firmware / G250 = NA
G350 = NA
G700 = NO / G250 = NA
G350 = YES
G700 = YES / G250 = NO
G350 = NO
G700 = NO / G250 = NA
G350 = NA
G700 = NO / G250 = NA
G350 = YES
G700 = YES / G250 = NO
G350 = NO
G700 = NO
24.xx.x Gateway Firmware / G250 = NA
G350 = NA
G700 = NO / G250=NA
G350 = YES
G700 = NO / G250 = YES
G350 = YES
G700 = YES / G250 = NA
G350 = NA
G700 = NO / G250 = NA
G350 = YES
G700 = NO / G250 = YES
G350 = YES
G700 = YES
25.xx.x Gateway Firmware / G250 = NA
G350 = NA
G700 = NO / G250 = NA
G350 = YES
G700 = YES / G250 = YES
G350 = YES
G700 = YES / G250 = NA
G350 = NA
G700 = NO / G250 = NA
G350 = YES
G700 = YES / G250 = YES
G350 = YES
G700 = YES
LSP Running 1.3.x CM Software / *YES / NO / NO
LSP Running 2.x CM Software / **Only if the Primary Media Server is running CM 1.3.2 or later / *YES / NO
LSP/ESS Running CM 3.x Software / ** Only if the Primary Media Server is running CM 1.3.2 or later / *YES / *YES

* As long as the LSP or ESS is running a release equal to or more recent than the primary server and the LSP/ESS release is a valid upgrade path for the release running on the primary server. LSP and ESS upgrades are constrained by valid Communication Manager upgrade paths. This means that if an LSP or an ESS is being upgraded to a more recent release of Communication Manager than the primary media server, the more recent release must be a valid upgrade path for the release running on the primary server. See the Supported Communication Manager Upgrade Paths section for a mapping of valid Communication Manager upgrade paths. In some cases when upgrading an LSP or ESS to a more recent release of CM than the primary server, firewall changes are required to support filesynchronization between the servers.

** Primary Media Servers running Communication Manager Releases earlier than 1.3.2 are not compatible with LSPs running later releases of Communication Manager Software.

Note: The following order of upgrading a distributed configuration with a primary server, media gateways, LSPs, and ESSs should be followed:

  1. Media Gateways (MGP and Media Modules). The order in which the Media Gateway (MGP) and Media Modules (MM) are upgraded does not matter.
  2. LSPs/ESSs
  3. Primary Media Servers

If an LSP or ESS is to be upgraded to a new version of Communication ManagerSoftware, all Media Gateways supported by that LSP/ESS must be running the appropriate new vintages of media gateway firmware. In addition, before a primary server is upgraded to a new release of CM software, all media gateways, media gateway media modules, LSPs, and ESSs in the configuration must be upgraded appropriately before an upgrade of the primary server is attempted.