Released June 4, 2012

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW63 to a board, the download will be rejected by the board.

This version of Firmware Vintage 63 (tn2602ap-h20-f63-sig.bin) can be applied to all HV20 and greater boards and contains the following fixes and enhancements:

• Previously on hairpinned calls when an endpoint pressed a DTMF digit, the TN2602AP board could send the wrong digit in the rtp-event. This has been corrected.
• In some rare Ethernet network configurations using HSRP and asymmetric routing, both the active and standby board could receive the same incoming rtp packets to the virtual address. If these packets were associated with a hairpinned call, the standby board could erroneously transmit these packets. This has been corrected and the standby board will not transmit any rtp packets.
• Previously a gratuitous ARP with the virtual MAC address was only sent when a board transitioned from standby to active state. The active board would then send an ARP request for the virtual address every 60 seconds to detect IP address conflicts. Now the active board in an active/standby pair will send this gratuitous ARP every 60 seconds which serves to detect address conflicts and to also continually update network equipment with the presence of the virtual interface.
• Previously when a board switched a call from voice mode to modem/fax/tty pass-thru mode, the rtp sequence numbers would jump by a significant number. This could be interpreted as packet loss during troubleshooting. This has been corrected.
• Previously when a TN2602AP board was sending RFC2833 DTMF digits, the redundant packets' RTP sequence number did not increment. A voip-parameter option (68) has been made available which can activate a mode of operation that increments the sequence number of the redundant packets.
• Previously, a T.38 interoperation issue could occur with certain third party fax servers which could result in intermittent fax failure for faxes transmitted by the fax server. This has been corrected.
• Previously when transmitting a fax on a circuit containing a very long echo path, the Message Confirmation Report (MCF) message from the receiving fax machine might be ignored. This could result in only one page being sent. A Voip parameter option (53) has been added which can be used to resolve this issue.
• Previously some very rare T.38 fax events, could impair some of the DSP resources on the board resulting in decreased board capacity. This has been corrected.
• VOIP parameter 53 (T.38/fax relay echo suppression period) has been added. This parameter is used by services personnel to resolve T.38 fax relay issues that can arise with very long echo paths.
• VOIP parameter 68 (RFC 4733/2833 Transmitter Redundancy Option) has been added. This parameter is used by services personnel to further tune the transmission of (RFC4733/RFC2833) DTMF redundant packets.

Read Me

TN2602AP Vintage 63 - Read Me

Released June 4, 2012

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW63 to a board, the download will be rejected by the board.

This version of Firmware Vintage 63 (tn2602ap-h2-f63-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fixes and enhancements:

Previously a gratuitous ARP with the virtual MAC address was only sent when a board transitioned from standby to active state. The active board would then send an ARP request for the virtual address every 60 seconds to detect IP address conflicts. Now the active board in an active/standby pair will send this gratuitous ARP every 60 seconds which serves to detect address conflicts and to also continually update network equipment with the presence of the virtual interface.

Previously when a board switched a call from voice mode to modem/fax/tty pass-thru mode, the rtp sequence numbers would jump by a significant number. This could be interpreted as packet loss during troubleshooting. This has been corrected. 

Previously when a TN2602AP board was sending RFC2833 DTMF digits, the redundant packets' RTP sequence number did not increment. A voip-parameter option (68) has been made available which can activate a mode of operation that increments the sequence number of the redundant packets.

Previously, a T.38 interoperation issue could occur with certain third party fax servers which could result in intermittent fax failure for faxes transmitted by the fax server. This has been corrected.

Previously when transmitting a fax on a circuit containing a very long echo path, the Message Confirmation Report (MCF) message from the receiving fax machine might be ignored. This could result in only one page being sent. A Voip parameter option (53) has been added which can be used to resolve this issue.

Previously some very rare T.38 fax events, could impair some of the DSP resources on the board resulting in decreased board capacity. This has been corrected.

VOIP parameter 53 (T.38/fax relay echo suppression period) has been added. This parameter is used by services personnel to resolve T.38 fax relay issues that can arise with very long echo paths.

VOIP parameter 68 (RFC 4733/2833 Transmitter Redundancy Option) has been added. This parameter is used by services personnel to further tune the transmission of (RFC4733/RFC2833) DTMF redundant packets.

Read Me

TN2602AP Vintage 63 - Read Me

Released March 5, 2012

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW62 to a board, the download will be rejected by the board.

This version of Firmware Vintage 62 (tn2602ap-h20-f62-sig.bin) can be applied to all HV20 and greater boards and contains the following fixes:

• After some rare TN2312AP/BP IPSI board clock glitch conditions on active Port Network (PN) clock and an IPSI interchange resulting in a Communication Manager (CM) warm restart of a PN, the TN2602AP board would not recover and would stay out of service until manually reset. This is now corrected and the board will recover automatically.
• Some types of corrupted packets were discovered to cause talk-path issues and CM would log error code MEDPROPT 769. If multiple corrupted packets were received while the board was processing call traffic, CM could show the port out-of-service for an extended time. The resiliency of the TN2602AP to corrupted packets has been improved and they will no longer cause errors and ports out-of-service.
• In some country codes, the DSP gain for talk and listen path was not always correct. This did not affect US, ETSI or TIA settings. Settings are now correct. For boards programmed to operate with the following country codes, users might hear a slight volume change. Belgium (6), France (12), Germany (13), Netherlands (5), Nordic (24), S. Africa (25), Spain (11), and UK (10).

Read Me

TN2602AP Vintage 62 - Read Me

Released March 5, 2012

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW62 to a board, the download will be rejected by the board.

This version of Firmware Vintage 62 (tn2602ap-h2-f62-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fixes:

• After some rare TN2312AP/BP IPSI board clock glitch conditions on active Port Network (PN) clock and an IPSI interchange resulting in a Communication Manager (CM) warm restart of a PN , the TN2602AP board would not recover and would stay out of service until manually reset. This is now corrected and the board will recover automatically.
• Some types of corrupted packets were discovered to cause talk-path issues and CM would log error code MEDPROPT 769. If multiple corrupted packets were received while the board was processing call traffic, CM could show the port out-of-service for an extended time. The resiliency of the TN2602AP to corrupted packets has been improved and they will no longer cause errors and ports out-of-service.
• In some country codes, the DSP gain for talk and listen path was not always correct. This did not affect US, ETSI or TIA settings. Settings are now correct. For boards programmed to operate with the following country codes, users might hear a slight volume change. Belgium (6), France (12), Germany (13), Netherlands (5), Nordic (24), S. Africa (25), Spain (11), and UK (10).

Read Me

TN2602AP Vintage 62 - Read Me

Released October 3, 2011

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW61 to a board, the download will be rejected by the board.

This version of Firmware Vintage 61 (tn2602ap-h20-f61-sig.bin) can be applied to all HV20 and greater boards and contains the following fix:

• The handling of TTY calls using Pass-through mode have been improved. Previously any TN2602AP Medpro board that processed large amount of TTY calls, could log MEDPROPT and IPMEDPRO alarms and errors, this has been corrected.

Read Me

TN2602AP Vintage 61 - Read Me

Released October 3, 2011

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW61 to a board, the download will be rejected by the board.

This version of Firmware Vintage 61 (tn2602ap-h2-f61-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fix:

• The handling of TTY calls using Pass-through mode have been improved. Previously any TN2602AP Medpro board that processed large amount of TTY calls, could log MEDPROPT and IPMEDPRO alarms and errors, this has been corrected.

Read Me

TN2602AP Vintage 60 - Read Me

Released July 11, 2011

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW60 to a board, the download will be rejected by the board.

This version of Firmware Vintage 60 (tn2602ap-h20-f60-sig.bin) can be applied to all HV20 and greater boards and contains the following fix:

• In certain instances, RTCP messages were not being sent correctly. This has been corrected.

Read Me

TN2602AP Vintage 60 - Read Me

Released July 11, 2011

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW60 to a board, the download will be rejected by the board.

This version of Firmware Vintage 60 (tn2602ap-h2-f60-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fix:

• In certain instances, RTCP messages were not being sent correctly. This has been corrected.

Read Me

TN2602AP Vintage 60 - Read Me

Released June 6, 2011

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW59 to a board, the download will be rejected by the board.

This version of Firmware Vintage 59 (tn2602ap-h20-f59-sig.bin) can be applied to all HV20 and greater boards and contains the following fixes:

• It was found that in some instances, TN2602AP could incorrectly calculate round-trip delay, resulting in false round-trip delay alarms. This has been corrected.
• Previously, TN2602AP's operating in standby mode could experience numerous MEDPROPT minor alarms. This has been corrected.
• In certain very rare conditions, during board insertion, sometimes the DSP capacity could be reported incorrectly. This has been corrected.
• In lab testing it was observed that with long periods of extremely high traffic coupled with certain highly unusual conditions (e.g., clock errors in the port network) that TN2602AP could go out of service and require manual intervention to recover. FW59 avoids this out of service condition.

Read Me

TN2602AP Vintage 59 - Read Me

Released June 6, 2011

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW59 to a board, the download will be rejected by the board.

This version of Firmware Vintage 59 (tn2602ap-h2-f59-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fixes:

• It was found that in some instances, TN2602AP could incorrectly calculate round-trip delay, resulting in false round-trip delay alarms. This has been corrected.
• Previously, TN2602AP's operating in standby mode could experience numerous 
  MEDPROPT minor alarms. This has been corrected.
• In lab testing it was observed that with long periods of extremely high traffic coupled with certain highly unusual conditions (e.g., clock errors in the port network) that TN2602AP could go out of service and require manual intervention to recover. FW59 avoids this out of service condition.

Read Me

TN2602AP Vintage 59 - Read Me

Released December 6, 2010 - 
Readme File updated June 21, 2011 

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW58 to a board, the download will be rejected by the board.

This version of Firmware Vintage 58 (tn2602ap-h20-f58-sig.bin) can be applied
to all HV20 and greater boards and contains the following fixes:

• *** Previously, it was reported that all TN2602AP's had to be upgraded to FW58 or greater prior to Nov 13, 2011 to avoid rejection of any new SSH sessions. This information was incorrect.
  
  In fact, firmware download files issued prior to May 13, 2011 have digital signatures that will expire on November 13, 2011. After the expiration date, the signed firmware download file cannot be downloaded to a target board. Note that Once the firmware is installed on a board, the board firmware will continue to operate normally after the digital signature expiration date.
  
  Avaya will be issuing newly signed firmware download files for many firmware releases with new digital signatures that will be valid for ~5 years. These newly signed files, once loaded onto a target board, are identical to the previous files except for the digital signature. Consequently, there is no need to re-download a board with the same vintage of firmware. ***
• The TN2602AP echo cancellation feature has been improved to allow better modem pass-through operation.
• Previously, in sniff traces, occasionally one could observe that the TN2602AP would send an ARP with a non-zero target MAC address. This has been corrected.
• VoIP Parameter 67 was added to allow UDP source port validation to be disabled.

Read Me

TN2602AP Vintage 58 - Read Me

Released December 6, 2010 -
Readme File updated June 21, 2011

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW58 to a board, the download will be rejected by the board.

This version of Firmware Vintage 58 (tn2602ap-h2-f58-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fixes:

• *** Previously, it was reported that all TN2602AP's had to be upgraded to FW58 or greater prior to Nov 13, 2011 to avoid rejection of any new SSH sessions. This information was incorrect.
  
  In fact, firmware download files issued prior to May 13, 2011 have digital signatures that will expire on November 13, 2011. After the expiration date, the signed firmware download file cannot be downloaded to a target board. Note that Once the firmware is installed on a board, the board firmware will continue to operate normally after the digital signature expiration date.
  
  Avaya will be issuing newly signed firmware download files for many firmware releases with new digital signatures that will be valid for ~5 years. These newly signed files, once loaded onto a target board, are identical to the previous files except for the digital signature. Consequently, there is no need to re-download a board with the same vintage of firmware. ***
• The TN2602AP echo cancellation feature has been improved to allow better modem pass-through operation.
• Previously, in sniff traces, occasionally one could observe that the TN2602AP would send an ARP with a non-zero target MAC address. This has been corrected.
• VoIP Parameter 67 was added to allow UDP source port validation to be disabled.

Read Me

TN2602AP Vintage 58 - Read Me

Released October 4, 2010

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW57 to a board, the download will be rejected by the board.

This version of Firmware Vintage 57 (tn2602ap-h20-f57-sig.bin) can be applied to all HV20 and greater boards and contains the following fixes:

• Previously, under a severe denial of service attack containing TCP packets, the Ethernet receive buffer could fill up and not clear, causing the board to go out of service. Now, the board will recover after such events.
• The Ethernet handling routines have been made more robust.
• Previously, near capacity DSP usage caused by a concentration of calls using a combination of G.729a with echo cancellation, encryption, DTMF, etc., could
  result in clicking, robotic-sounding voice or, in more severe cases, one-way talk path. The processing of this traffic has been optimized to avoid these issues.
• The digit detection routine has been enhanced to better handle mal-formed incoming digits. Previously, a single digit could be detected as two digits if the incoming digit message had DTMF tone leakage in the voice stream prior to the signaled start of the digit.
• Previously, a stand-by TN2602AP could send RTCP messages using both physical and virtual IP address when none should be sent at all. This could cause "port-flapping" on the upstream Ethernet switch. This has been corrected.
• Previously, with CM6.0 and later, with SIP trunk traffic, and the Early Media Feature enabled, about 8% of SIP call traffic may experience distorted ringback. Note that the distortion was subtle and did not affect voice quality. FW57 eliminates the ringback distortion.
• Previously, TN2602AP could erroneously send a "DSP Over-Allocation" message to software. This has been corrected.
• Previously, RSVP could send a ResvConf message with an invalid ERROR_SPEC sub-message. Now this message correctly contains the sender's IP address.

Read Me

TN2602AP Vintage 57 - Read Me

Released September 7, 2010

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW57 to a board, the download will be rejected by the board.

This version of Firmware Vintage 57 (tn2602ap-h2-f57-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fixes:

• Previously, near capacity DSP usage caused by a concentration of calls using a combination of G.729a with echo cancellation, encryption, DTMF, etc., could result in clicking, robotic-sounding voice or, in more severe cases, one-way talk path. The processing of this traffic has been optimized to avoid these issues.
• Call allocation to the Digital Signal Processors (DSP) on TN2602AP hw0 through hw19 has been optimized to help prevent overloading individual DSPs.
• The digit detection routine has been enhanced to better handle mal-formed incoming digits. Previously, a single digit could be detected as two digits if the incoming digit message had DTMF tone leakage in the voice stream prior to the signaled start of the digit.

Read Me

TN2602AP Vintage 57 - Read Me - Issue 2

Released June 7, 2010

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW55 to a board, the download will be rejected by the board.

This version of Firmware Vintage 55 (tn2602ap-h2-f55-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fixes:

• Previously, a small percentage of customers experienced distorted ringback on some SIP trunks. This problem only occurred with CM5.2.1 and later with SIP trunk traffic with the Early Media feature enabled. This has now been corrected.
• In Communications Manager 6.0 systems with RSVP enabled, Service Pack 0 or later must be loaded to use FW55.
• Previously, large conference calls (8 or more parties) could experience clicking sounds if the conference bridge connection had significant jitter. This has been corrected.
• Previously, the IP address sent in a RTCP packet to VMM could contain incorrect information. This is now fixed.
• Previously, hairpinned tandem IP trunk calls could have occasional call failures. This has been fixed.
• Previously, when using the Uniphone 1140 TTY phone and TTY relay, sometimes the first character of the call was missed by the TN2602AP. FW55 corrects this issue.

Read Me

TN2602AP Vintage 55 - Read Me

Released June 7, 2010

NOTE!!! There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW55 to a board, the download will be rejected by the board.

This version of Firmware Vintage 55 (tn2602ap-h20-f55-sig.bin) can be applied to all HV20 and greater boards and contains the following fixes:

• Previously, a small percentage of customers experienced distorted ringback on some SIP trunks. This problem only occurred with CM5.2.1 and later with SIP trunk traffic with the Early Media feature enabled. This has now been corrected.
• In Communications Manager 6.0 systems with RSVP enabled, Service Pack 0 or later must be loaded to use FW55.
• Previously, large conference calls (8 or more parties) could experience clicking sounds if the conference bridge connection had significant jitter. This has been corrected.
• Previously, the IP address sent in a RTCP packet to VMM could contain incorrect information. This is now fixed.
• Previously, hairpinned tandem IP trunk calls could have occasional call failures. This has been fixed.
• Previously, when using the Uniphone 1140 TTY phone and TTY relay, sometimes the first character of the call was missed by the TN2602AP. FW55 corrects this issue.

Read Me

TN2602AP Vintage 55 - Read Me

TN2602AP - Firmware Vintage 54 Hardware vintage 0 - 19

File name - tn2602ap-h2-f54-2-sig.bin
File size - 5.47 MB (5,612 KB)
MD5 Sum - ffa3c62e3572b185e64f80f2acde19f2

Released March 8, 2010

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW54 to a board, the download will be rejected by the board.

This version of Firmware Vintage 54 (tn2602ap-h2-f54-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following enhancement and fixes:

• Previously, certain network jitter conditions could impact voice quality. This has been improved.
• Previously, if hairpinning was enabled and a hairpinned call was transferred, occasionally there could be no talk path. This has been corrected.
• Previously, under certain rare conditions using codecs with silence suppression, TN2602AP could stop sending RTCP messages, this could lead to dropped calls. This has been corrected.
• FW54 provides enhanced incoming media packet validation.
• VOIP parameter 91 (DTMF detection control) has been enhanced. This parameter is used by services personnel to further tune DTMF detection.

Read Me

TN2602AP Vintage 54 - Read Me

Released March 8, 2010

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW54 to a board, the download will be rejected by the board.

This version of Firmware Vintage 54 (tn2602ap-h20-f54-sig.bin) can be applied to all HV20 and greater boards and contains the following fixes:

• Previously, certain network jitter conditions could impact voice quality. This has been improved.
• Previously, if hairpinning was enabled and a hairpinned call was transferred, occasionally there could be no talk path. This has been corrected.
• Previously, under certain rare conditions using codecs with silence suppression, TN2602AP could stop sending RTCP messages, this could lead to dropped calls. This has been corrected.
• FW54 provides enhanced incoming media packet validation.
• VOIP parameter 91 (DTMF detection control) has been enhanced. This parameter is used by services personnel to further tune DTMF detection.

Read Me

TN2602AP Vintage 54 - Read Me

TN2602AP - Firmware Vintage 53 Hardware vintage 0 - 19

File name - tn2602ap-h2-f53-2-sig.bin
File size - 5.48 MB (5,613 KB)
MD5 Sum - f2832090737f9825ce84d6eee09cf131

Released February 1, 2010

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW53 to a board, the download will be rejected by the board.

This version of Firmware Vintage 53 (tn2602ap-h2-f53-sig.bin) can be applied
to production vintage boards from HV0 through HV19 and contains the following
enhancement and fixes.

• Previously, large packet timestamp changes could cause voice quality issues. FW53 has been enhanced to handle these network induced changes more quickly.
• TTY operation has been made more robust in the presence of many very rapid packet delay changes. Previously, some characters could be lost as a result of rapid network delay changes.
• FW53 corrects a rare problem with HV8 where it may appear that a firmware download did not complete correctly.

Read Me

TN2602AP Vintage 53 - Read Me

Released February 1, 2010

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW53 to a board, the download will be rejected by the board.

This version of Firmware Vintage 53 (tn2602ap-h20-f53-sig.bin) can be applied to all HV20 and greater boards and contains the following fix:

• Previously, large packet timestamp changes could cause voice quality issues. FW53 has been enhanced to handle these network induced changes more quickly.
• TTY operation has been made more robust in the presence of many very rapid packet delay changes. Previously, some characters could be lost as a result of rapid network delay changes.
• Previously, certain extremely rare network conditions could cause the Ethernet transmitter to stop working. Now, if these network conditions occur, the Ethernet transmitter is restarted and the event noted in the board event log. Additionally, a new state of health parameter has been added to generate an alarm if the TN2602 can no longer communicate with its gateway via ARP.

Read Me

TN2602AP Vintage 53 - Read Me

Updated December 7, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW52 to a board, the download will be rejected by the board.

This version of Firmware Vintage 52 (tn2602ap-h20-f52-sig.bin) can be applied
to all HV20 and greater boards and contains the following fix:

• Previously, TN2602AP HW20+ boards configured with the Ethernet interface locked-down to 100-M/Full duplex, the board could randomly switch to 100-M/Half duplex. This could result in a link-down condition to the board, thus causing IPSI interchanges. This has been corrected.
• Boards configured for auto-negotiate are not affected.

Read Me

TN2602AP Vintage 52 - Read Me

TN2602AP - Firmware Vintage 51 for Hardware Vintage 0 through 19 circuit packs

File name - tn2602ap-h2-f51-2-sig.bin
File size - 5.47 MB (5,738,160 bytes)
MD5 Sum - d0d705da0c845700198de519e3b3177c

Released November 9, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW51 to a board, the download will be rejected by the board.

• Previously, some badly formed incoming DTMF digits would not be detected. FW51 greatly improves DTMF detection.
• The echo canceller has been modified to allow tuning to help eliminate double-talk (both ends "speaking" at the same time) induced corruption of DTMF
  digits. This improves IVR performace. See new VOIP parameters 18 and 19. The default settings may not yield a noticeable change.
• The echo canceller has also been improved to reduce the echo of low level signals, such as light breathing into the handset.
• New VOIP parameters 17, 18 and 19 have been created to allow tuning by services personnel. VOIP parameter 34 has been enhanced.

- Parameter 17: Echo Canceller Alternate Comfort Noise Option
- Parameter 18: Echo Canceller DTMF Transparency Option
- Parameter 19: Echo Canceller Heavy Double Talk Option
- Parameter 34: Modem Pass-Through Ecan Override

• VoIP parameter 34 allows STE phones to successfully re-key.
• Improved TTY and Special Information Tone (SIT) tone detection.
• Previously, in certain configurations, the RTP-Event DTMF marker bit on TN2602 was not being sent. This now adheres to RFC 2833.
• FW51 supports new Communication Manager 5.2.1 Early Media Detection feature. "Early Media" refers to the ability in SIP for a called user agent to play
  media to a caller prior to answer, instead of locally generated ringback.

Read Me

TN2602AP Vintage 51 - Read Me

File name - tn2602_ap-h20-f51-2-sig.bin
File size - 5.58 MB (5,854,440 bytes)
MD5 Sum - 40acb45a843c5a617a12fbc05409ca64

Updated November 9, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW51 to a board, the download will be rejected by the board.

This version of Firmware Vintage 51 (tn2602ap-h20-f51-sig.bin) can be applied to all HV20 and greater boards and contains the following enhancements and fixes:

• Previously, some badly formed incoming DTMF digits would not be detected. FW51 greatly improves DTMF detection.
• The echo canceller has been modified to allow tuning to help eliminate double-talk (both ends "speaking" at the same time) induced corruption of DTMF
  digits. This improves IVR performace. See new VOIP parameters 18 and 19. The default settings may not yield a noticeable change.
• The echo canceller has also been improved to reduce the echo of low level signals, such as light breathing into the handset.
• New VOIP parameters 17, 18 and 19 have been created to allow tuning by services personnel. VOIP parameter 34 has been enhanced.

- Parameter 17: Echo Canceller Alternate Comfort Noise Option
- Parameter 18: Echo Canceller DTMF Transparency Option
- Parameter 19: Echo Canceller Heavy Double Talk Option
- Parameter 34: Modem Pass-Through Ecan Override

• VoIP parameter 34 allows STE phones to successfully re-key.
• Improved TTY and Special Information Tone (SIT) tone detection.
• Previously, in certain configurations, the RTP-Event DTMF marker bit on TN2602 was not being sent. This now adheres to RFC 2833.
• FW51 supports new Communication Manager 5.2.1 Early Media Detection feature. "Early Media" refers to the ability in SIP for a called user agent to play
  media to a caller prior to answer, instead of locally generated ringback.

Read Me

TN2602AP Vintage 51 - Read Me

TN2602AP - Firmware Vintage 49 for Hardware Vintage 0 through 19 circuit packs

File name - tn2602ap-h2-f49-2-sig.bin
File size - 5.46 MB (5,728,424 bytes)
MD5 Sum - 43a560ad3ef8557a96b53c84f17c80e0

Released July 1, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW49 to a board, the download will be rejected by the board.

This version of Firmware Vintage 49 (tn2602ap-h2-f49-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following enhancement and fixes:

• FW48 had an issue where it did not properly handle UDP headers with a null checksum. This could cause one-way and / or no-way talk paths.
• TN2602 FW49 properly handles UDP headers with a null checksum. FW49 fixes a Hairpin voice path issue introduced in FW47.
• This TN2602 firmware contains an enhancement for the MLPP feature.

Read Me

TN2602AP Vintage 49 - Read Me

File name - tn2602ap-h20-f49-2-sig.bin
File size - 5.64 MB (5,917,040 bytes)
MD5 Sum - 15a88466fef74002ad7b3f0238d07639

Updated July 1, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW49 to a board, the download will be rejected by the board.

This version of Firmware Vintage 49 (tn2602ap-h20-f49-sig.bin) can be applied to all HV20 and greater boards and contains the following enhancements and fixes:

• TN2602AP FW48 supports the Communication Manager 5.2 feature Simple Voice Network Statistics (SVNS).
• Very rarely, the "enable session" command would appear to be successful but in fact, would fail. This would cause FTP sessions to fail thus preventing firmware upgrades. This has been fixed.
• FW48 had an issue where it did not properly handle UDP headers with a null checksum. This could cause one-way and / or no-way talk paths.
• TN2602 FW49 properly handles UDP headers with a null checksum.
• FW49 fixes a hairpin voice path issue introduced in FW49.
• Previously, in extremely high traffic conditions, the board could reset. This has been corrected.
• This TN2602 firmware supports an enhancement for the MLPP feature.

Read Me

TN2602AP Vintage 49 - Read Me

TN2602AP - Firmware Vintage 48 for Hardware Vintage 0 through 19 circuit packs

File name - tn2602ap-h2-f48-sig.bin
File size - 5.45 MB (5,725,720 bytes)
MD5 Sum - 16f2520036f40ecb3ffebb694ac89e46

Released May 4, 2009
Read Me File updated May 21, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW48 to a board, the download will be rejected by the board.

This version of Firmware Vintage 48 (tn2602ap-h2-f48-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following enhancement and fix. G860 Media Gateway users should not use FW48 (see the Known Issue below):

• TN2602AP FW48 supports the Communication Manager 5.2 feature Simple Voice Network Statistics (SVNS).
• Very rarely, the "enable session" command would appear to be successful but in fact, would fail. This would cause FTP sessions to fail thus preventing firmware upgrades. This has been fixed.

Known Issue:

• Communication Manager systems that connect to a G860 Media Gateway should NOT use TN2602AP FW48. Instead, these systems should use FW47. FW48 has an issue where it does not properly handle UDP headers with a null checksum. This can cause one-way and / or no-way talk paths. When released, TN2602 FW49 will properly handle UDP headers with a null checksum. Producing a UDP header with a null checksum is unusual, but not prohibited. Avaya is currently not aware of any other endpoints that produce null checksum UDP headers.

Read Me

TN2602AP Vintage 48 - Read Me

TN2602AP - Firmware Vintage 47 for Hardware Vintage 20+ Circuit packs

Firmware not yet available.

Updated May 4, 2009

TN2602AP HV20+ Firmware Vintage 48, which supports the new Communication Manager 5.2 feature "Simple Voice Network Statistics (SVNS)", is not yet available for hardware vintage 20+ circuit packs. However, FV48 IS available for TN2602AP circuit packs with hardware vintages less than HV20.

HV20+ Firmware Vintage 48 or greater will be available in the near future. In the meantime, HV20+ Firmware Vintage 47 can be used and is compatible with Communication Manager 5.2 but does not support the new feature.

Read Me

TN2602AP Vintage 48 - Read Me

TN2602AP - Firmware Vintage 47 for Hardware Vintage 0 through 19 circuit packs

File name - tn2602ap-h2-f47-sig.bin
File size - 5.67 MB (5,948,420 bytes)
MD5 Sum - 3356f387fcab070503551036ec96eb75

Released April 6, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW47 to a board, the download will be rejected by the board.

This version of Firmware Vintage 47 (tn2602ap-h2-f47-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fixes:

• Jitter Buffer operation has been improved. This will greatly reduce or eliminate clicks and pops on connections to endpoints such as Message Manager, IA770, etc.
• Previously, when the first sequence number of an arriving packet is greater than 32768 and SRTP is enabled with sHA-1 authentication of RTP packets, then one way talk path could occur. This has been corrected.
• Previously, in certain rare circumstances, there was a slight possibility that one or more digits in a DTMF Relay outpulsing string could be incorrectly transmitted as the digit zero. This has been corrected.
• Under high traffic conditions (e.g greater than 150 endpoints using a single TN2602AP in a 5 minute window), boards equipped with FW40 through FW46 could reset. This has been fixed.

Read Me

TN2602AP Vintage 47 - Read Me

TN2602AP - Firmware Vintage 47 for Hardware Vintage 20+ Circuit packs

File name - tn2602ap-h20-f47-sig.bin
File size - 5.61 MB (5,886,868 bytes)
MD5 Sum - 541de574b3920f5089b6db7830b7ea55

Released April 6, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW47 to a board, the download will be rejected by the board.

This version of Firmware Vintage 47 (tn2602ap-h20-f47-sig.bin) can be applied to all HV20 and greater boards and contains the following fixes:

• Jitter Buffer operation has been improved. This will greatly reduce or eliminate clicks and pops on connections to endpoints such as Message Manager, IA770, etc.
• Previously, when the first sequence number of an arriving packet is greater than 32768 and SRTP is enabled with sHA-1 authentication of RTP packets, then one way talk path could occur. This has been corrected.
• Previously, in certain rare circumstances, there was a slight possibility that one or more digits in a DTMF Relay outpulsing string could be incorrectly transmitted as the digit zero. This has been corrected.
• Under high traffic conditions (e.g greater than 150 endpoints using a single TN2602AP in a 5 minute window), boards equipped with FW40 through FW46 could reset. This has been fixed.

Read Me

TN2602AP Vintage 47 - Read Me

TN2602AP - Firmware Vintage 46 for Hardware Vintage 0 through 19 circuit packs

File name - tn2602ap-h2-f46-sig.bin
File size - 5.66 MB (5,945,944 bytes)
MD5 Sum - c1f0c03b777f3178b2a13c75f77a249e

Released March 2, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW46 to a board, the download will be rejected by the board.

This version of Firmware Vintage 46 (tn2602ap-h2-f46-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fix and enhancement:

• Previously, if both DTMF and TTY were programmed to use relay, DSP core crashes could occur which would cause dropped calls and / or one-way talk path. In this situation, CM software would log errors MEDPROPT 513 and 769-2000 . This has been corrected in FW46.
• Previously, if a remote system terminated its transmission with a high volume level (e.g. at the end of a DTMF tone), the TN2602AP's Comfort Noise Generator (CNG) would generate a high level of comfort noise. This was perceived as a audible hiss immediately following the terminated transmission. FW46 introduces the ability to limit the maximum level of CNG via a new tunable VOIP parameter, Parameter 65 which is accessible via a TN2602AP telnet session.
• Parameter 65: Maximum CNG Level
  value = (1 - 1000) - Change maximum CNG level to a specific value.
  value = -1 (or 0xffffffff) - DSP will use the default setting of 1000.
• Parameter 65 detailed description:
  The comfort noise level generated by he TN2602AP is based on the estimated noise floor. Consequently, its level scales with background noise. A ceiling is imposed so that is not allowed to drift higher than a certain maximum level. In previous releases the ceiling is fixed at "1000" (approx. -30dBm) and cannot be adjusted.
• With Fw46, the default maximum remains at 1000. Thus default operation remains the same as previous releases.
• To change the ceiling, parameter 65 can be used to set the maximum to a lower value. For example a value of 100 is approx -50dBm, which is a reasonable compromise that provides adequate comfort noise, yet not so loud to be disconcerting. If hiss is an issue, we recommend initially setting parameter 65 to a value of 100. A low non-zero value is preferred as a value of zero essentially shuts comfort noise off altogether.
• Example TN2602AP telnet session commands to override the CNG ceiling with a new (lower) value of 100:
  setVoipParam 65, 100 (prepare to override default CNG ceiling with the value 100)
  sendVoipParams (send new parameter to the DSPs, thus activating new ceiling for new calls)
  saveVoipParams (saves the programmed parameter to non-volatile memory)

Read Me

TN2602AP Vintage 46 - Read Me

TN2602AP - Firmware Vintage 46 for Hardware Vintage 20+ Circuit packs

File name - tn2602ap-h20-f46-sig.bin
File size - 5.61 MB (5,885,096 bytes)
MD5 Sum - 363cd8e91007c95008644b286c94b6fe

Released March 2, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW46 to a board, the download will be rejected by the board.

This version of Firmware Vintage 46 (tn2602ap-h20-f46-sig.bin) can be applied to all HV20 and greater boards and contains the following fix and enhancement:

• Previously, if both DTMF and TTY were programmed to use relay, DSP core crashes could occur which would cause dropped calls and / or one-way talk path. In this situation, CM software would log errors MEDPROPT 513 and 769-2000 . This has been corrected in FW46.
• Previously, if a remote system terminated its transmission with a high volume level (e.g. at the end of a DTMF tone), the TN2602AP's Comfort Noise Generator (CNG) would generate a high level of comfort noise. This was perceived as a audible hiss immediately following the terminated transmission. FW46 introduces the ability to limit the maximum level of CNG via a new tunable VOIP parameter, Parameter 65 which is accessible via a TN2602AP telnet session.
• Parameter 65: Maximum CNG Level
  value = (1 - 1000) - Change maximum CNG level to a specific value.
  value = -1 (or 0xffffffff) - DSP will use the default setting of 1000.
• Parameter 65 detailed description:
  The comfort noise level generated by he TN2602AP is based on the estimated noise floor. Consequently, its level scales with background noise. A ceiling is imposed so that is not allowed to drift higher than a certain maximum level. In previous releases the ceiling is fixed at "1000" (approx. -30dBm) and cannot be adjusted.
• With Fw46, the default maximum remains at 1000. Thus default operation remains the same as previous releases.
• To change the ceiling, parameter 65 can be used to set the maximum to a lower value. For example a value of 100 is approx -50dBm, which is a reasonable compromise that provides adequate comfort noise, yet not so loud to be disconcerting. If hiss is an issue, we recommend initially setting parameter 65 to a value of 100. A low non-zero value is preferred as a value of zero essentially shuts comfort noise off altogether.
• Example TN2602AP telnet session commands to override the CNG ceiling with a new (lower) value of 100:
  setVoipParam 65, 100 (prepare to override default CNG ceiling with the value 100)
  sendVoipParams (send new parameter to the DSPs, thus activating new ceiling for new calls)
  saveVoipParams (saves the programmed parameter to non-volatile memory)

Read Me

TN2602AP Vintage 46 - Read Me

TN2602AP - Firmware Vintage 45 for Hardware Vintage 20+ Circuit packs

File name - tn2602ap-h20-f45-sig.bin
File size - 5.98 MB (6,277,108 bytes)
MD5 Sum - df46cba1fa3c9c7e7348144da7443552

Released January 26, 2009

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW44 to a board, the download will be rejected by the board.

***Firmware Vintage 45 (tn2602ap-h20-f45-sig.bin) or greater MUST be applied to all HV20 and greater boards.***

Firmware Vintage 45 corrects an issue that, in rare circumstances, could cause the TN2602AP board to not boot up or reset correctly. This could happen during initial install, firmware updates, after changing IP parameters, or after a board reset.

If loading firmware vintage 45 to a HV20+ board is not successful, repeat the download. If repeated attempts to upgrade a board fail, replace that board.

TN2602AP boards LESS than HV20 do NOT have this issue and do not need this upgrade.

Read Me

TN2602AP Vintage 45 - Read Me

TN2602AP - Firmware Vintage 44 for Hardware Vintage 0 through 19 circuit packs

File name - tn2602ap-h2-f44-sig.bin
File size - 5.66 MB (5,945,868 bytes)
MD5 Sum - 86a3e7174fb5d95efcbe6f63601b060b

Released December 8, 2008

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW44 to a board, the download will be rejected by the board.

This version of Firmware Vintage 44 (tn2602ap-h2-f44-sig.bin) can be applied to production vintage boards from HV0 through HV19 and contains the following fixes:

• Previously, if the TN2602AP simultaneously received a redundant DTMF tone (via both RTP payload and in-band), the tone might not be processed properly. FW44 correctly processes these redundant tones
• Previously, if a system experienced packet bus problems that caused CRC errors, duplicated TN2602AP's could unexpectedly interchange. This has been corrected.
• With firmware vintage 40 and 41, the active TN2602AP in a duplicated configuration would send RTCP packets to VMM containing the board physical IP address instead of its virtual (shared) IP address. This has been corrected.

Read Me

TN2602AP Vintage 44 - Read Me

TN2602AP - Firmware Vintage 44 for Hardware Vintage 20+ Circuit packs

File name - tn2602ap-h20-f44-sig.bin
File size - 5.98 MB (6,277,108 bytes)
MD5 Sum - cd03a63f247482f4b781b88f046cbbe7

Released December 8, 2008

NOTE: There are now TWO different versions of TN2602AP; Hardware Vintage 0 through 19 (HV0-19) and Hardware Vintage 20 and higher (HV20+). Each hardware version requires a unique firmware file.

Note that these different hardware versions have been designed to interoperate with each other in duplicated systems. Hardware and firmware version / vintage matching is not needed.

Note also that if one attempts to download the incorrect version of FW44 to a board, the download will be rejected by the board.

This version of Firmware Vintage 44 (tn2602ap-h20-f44-sig.bin) can be applied to production vintage boards from HV20 and greater.

This is the first Generally Available firmware release for TN2602AP HV20 and greater. This is the minimum firmware vintage available for TN2602AP HV20+.

Read Me

TN2602AP Vintage 44 - Read Me

TN2602AP - Firmware Vintage 41

File name - tn2602ap-h2-f41-sig.bin
File size - 5.66 MB (5,942,436 bytes)
MD5 Sum - bcd4328f3744b6b97c670bf4e40fcb89

Released August 11, 2008

Firmware Vintage 41 can be applied to all production vintage boards (HV2, HV4 through HV8) and contains the following enhancements and fixes:

• Firmware Vintage 41 combines the new Communication Manager 5.1 syslogging feature introduced in FW 40 with the fixes introduced in FW35 (listed below).
• This firmware has enhanced DTMF detection that should reduce spurious touch-tone digits (talk-off) during active calls.
• Previously, TTY calls could cause DSP resets, potentially causing one-way or no-way talk paths. This has been corrected
• Previously, when performing relay of TTY and/or DTMF tones, a jitter buffer overflow condition could occur. This could cause gaps in tones which could cause endpoints to detect repeated digits.
• Previously, when a H.323 phone and SIP trunk are in a call and the call is hairpinned through a crossfire board, an initial DTMF signaling tone (such as the first digit of a password for a conference bridge or voice mail system) could be dropped. All subsequent DTMF tones were passed correctly. Now, all digits are sent correctly.

Read Me

TN2602AP Vintage 41 - Read Me

TN2602AP - Firmware Vintage 40

File name - tn2602ap-h2-f40-sig.bin
File size - 5.66 MB (5,942,416 bytes)
MD5 Sum - 54c23a626965b20ef8e2930d879a2341

Released June 30, 2008

This release applies to all production vintage boards (HV2, HV4 to HV8).

Firmware Vintage 40 supports the Communication Manager 5.1 syslogging feature.

The intent of the syslogging feature is to provide increased capability to debug network problems and to support a centralized server as a collection point for ease of access and management of historical log data.

FV40 also corrects the following problem:

• Previously, when a H.323 phone and SIP trunk are in a call and the call is hairpinned through a crossfire board, an initial DTMF signaling tone (such as the first digit of a password for a conference bridge or voice mail system) could be dropped. All subsequent DTMF tones were passed correctly. Now, all digits are sent correctly.

Note that there will be two loads of future firmware to be released for TN2602AP:

• FV35, which is scheduled be released mid-July, will contain a number of field fixes. However, FV35 does NOT contain the Communication Manager 5.1 syslog feature. The field fixes include improved DTMF detection - which will reduce or eliminate spurious tones inserted into the voice path - and the elimination of rare DSP resets induced by TTY calls.
• FV41, scheduled for mid-August, will contain the field fixes contained in FV35 plus the Communication Manager 5.1 syslog feature.
• FV40 is recommended for those customers that require the fix included in FV40, or for Communication Manager 5.1 customers who wish to implement the syslog feature at this time. All other customers are encouraged to implement FV35 or FV41 when they become available.

Read Me

TN2602AP Vintage 40 - Read Me

TN2602AP - Firmware Vintage 35

File name - tn2602ap-f35-sig.bin
File size - 5.04 MB (5,289,272 bytes)
MD5 Sum - 2ddfa8228b227e3bc0b304e0aa776664

Released July 11, 2008

NOTE: TN2602AP Firmware Vintage 35 does NOT support the Communication Manager 5.1 syslogging feature recently delivered in FW40.

FW41, scheduled for mid-August 2008, will contain both the FW35 fixes and the Communication Manager 5.1 syslog feature. FW35 is recommended for customers who do not require the Communication Manager 5.1 syslogging feature. Supports Communication Manager 3.0 or greater.

Firmware Vintage 35 can be applied to all production vintage boards (HV2, HV4 through HV8) and contains the following enhancements and fixes:

• This firmware has enhanced DTMF detection that should reduce spurious touch-tone digits (talk-off) during active calls.
• Previously, TTY calls could cause DSP resets, potentially causing one-way or no-way talk paths. This has been corrected.
• Previously, when performing relay of TTY and/or DTMF tones, a jitter buffer overflow condition could occur. This could cause gaps in tones which could cause endpoints to detect repeated digits.
• Previously, when a H.323 phone and SIP trunk are in a call and the call is hairpinned through a crossfire board, an initial DTMF signaling tone (such as the first digit of a password for a conference bridge or voice mail system) could be dropped. All subsequent DTMF tones were passed correctly. Now, all digits are sent correctly.

Read Me

TN2602AP Vintage 35 - Read Me

TN2602AP - Firmware Vintage 34

File name - tn2602ap-f34-sig.bin
File size - 5.04 MB (5,288,868 bytes)
MD5 Sum - d372b3277cd110df45b9f88e991a417c

Released April 7, 2008

This release applies to all production vintage boards (HV2, HV4 to HV8).

FW 34 contains the following fixes and enhancements relative to FW 33:

• FW34 limits the output amplitude of DTMF relay tones to -12dBm as the default. This prevents receiver saturation with DTMF relay with other non-Avaya gateways that may use a louder RFC2833 volume level when relaying digits. This change helps ensure accurate reception of relayed DTMF tones in those environments. A VoIP parameter has been added to allow programmability for this override as well.
• FW34 corrects a problem introduced in FW33 that in some instances could cause inter-digit timing between regenerated DTMF relay tones to be less than 40 milliseconds, but only when the original inter-digit timing of the detected signal is less than 80 milliseconds. In certain call routing configurations, this could occasionally lead to DTMF detection problems on the PSTN, resulting in call completion failures.
• FW34 contains an updated tone detection algorithm which improves overall DTMF detection performance
• FW34 adds AES/AEA encryption support for fax-relay and T.38.
• FW34 disables TTY detection if the far-end does not support TTY.
• Additional VoIP parameters can now be tuned to improve STU phone operation.

Read Me

TN2602AP Vintage 34 - Read Me

TN2602AP - Firmware Vintage 33

File name - tn2602ap-f33-sig.bin
File size - 5.04 MB (5,285,828 bytes)
MD5 Sum - 1516e2f2e6fee52a9da8657b1b54031c

Released December 3, 2007

This release applies to all production vintage boards (HV2, HV4 to HV8).

FW 33 contains the following fixes and enhancements relative to FW 32:

• TN2602AP FW32 introduced a DTMF digit relay problem that can result in DSP buffer exhaustion and DSP resets. This can lead to one-way, no-way, and bridged talk paths. This problem has been corrected.
• DTMF relay operation has been improved by making the RTP-Payload transmission more robust. Previously, if the DTMF relay string was missing an "end-of-digit" indication, subsequent digits would not be transmitted. Also, individual digits may have been dropped.
• DTMF digit detection has been enhanced to better accommodate poor quality DTMF digits. Frequency tolerances and signal-to-noise ratio requirements have been modified.
• Previously, a flood of ICMP redirect messages could cause DSP and board resets. This could result in one-way and no-way talk paths and dropped calls. This has been corrected.
• TN2602AP IP network jitter tolerance has been improved, resulting in better voice quality at jitter levels above 200 ms.
• Previously, large delay changes in an IP network could cause one-way talk path. This has been corrected.
• Hairpinning operation has been improved. Previously, tandem IP trunk calls that hairpinned on a TN2602AP could have no talk path and might not free all resources, potentially resulting in one-way and no-way talk paths.
• Previously, TN2602AP did not properly decode and play g.729 rtp streams if the padding bit was set and padding was included in the rtp packet. This has been corrected.
• A change has been made (an index was added to the end of the RTCP string) to enhance compliance with the RTCP protocol.

Read Me

TN2602AP Vintage 33 - Read Me

TN2602AP - Firmware Vintage 32

File name - TN2602AP-f32-sig.bin
File size - 5.03 MB (5,279,524 bytes)
MD5 Sum - e36e4bc00c14161ad8a9cb2951ed0e90

Released September 7, 2007

This release applies to all production vintage boards (HV2, HV4 to HV8).

FW 32 contains the following fixes and enhancements relative to FW 31:

• FW 32 corrects a problem with G.729/G.729A codec operation that could cause DSP resets when encryption and silence suppression is used with 97xx type phones.

• Hairpinning operation has been improved thus preventing boards from sending UDP packets to unreachable ports. This caused resources to be consumed and not released.

• Previously, an ARP flood Denial of Service (DoS) attack could cause the board to reset. Now, the board stays in service and recovers cleanly from the DoS attack.

• Occasionally, when a call is redirected, e.g. covered to Intuity Audix, a single click might be heard at the moment the call is redirected. This has been corrected.

• DTMF digit transmission has been modified to make it more robust.

• Improved operation with Fax Relay and T.38 Fax

• In duplicated TN2602AP applications, the stand-by board will recover quicker from a DSP reset.

• Improved VMM statistics.

Read Me

TN2602AP Vintage 32 - Read Me

TN2602AP - Firmware Vintage 31

File name - TN2602AP-f31-sig.bin
File size - 5266212 Bytes (5.02 MB)
MD5 Sum - 3caf5741ef97cd24c11ca0ab0c664782

Released May 7, 2007

This release applies to all production vintage boards (HV2, HV4 to HV8).

FW 31 contains the following fixes and enhancements relative to FW 30:

• Previously, with duplicated TN2602AP boards, when hairpinning and RSVP were both enabled, some DSP channels could lock-up causing one-way talk path. This has been corrected.

• Jitter management has been improved. This results in better voice quality in networks with high levels of jitter.

• Jitter and packet loss reporting has been improved.

• T.38 Fax operation with some fax machines has been improved.

• Previously, TN2602AP fax-relay / T.38 operations could fail if a terminal generated short or no CED tone. This would caused fax time-out or failures. This has been improved.

Read Me

TN2602AP Vintage 31 - Read Me

TN2602AP - Firmware Vintage 30

File name - tn2602ap_f30-sig.bin
File size - 5263604 bytes
MD5 Sum - 78a0d6fe043c57eb71092cb019cde6a8

Released March 19, 2007

This release applies to all production vintage boards (HV2, HV4 to HV8).

FW 30 contains the following fixes and enhancements relative to FW 25:

• TN2602AP firmware vintage 30 supports the Communication Manager 4.0 features SRTP media encryption and disable all background pings.

• The robustness of Fax and Data calls have been improved.

• Fax pass-through operation has been improved.

• RTCP reporting to Avaya VoIP Monitoring Manager (VMON / VMM), has been improved.

Read Me

TN2602AP Vintage 30 - Read Me

TN2602AP - Firmware Vintage 25
File name - tn2602ap_f25-2-sig.bin

MD5 Sum - 8a684d17fd52185098a71f88382ae78b

File size - 5183148 Bytes

Released November 9, 2006

FW 25 contains the following fixes and enhancements relative to FW 24:

• Modem and Fax operations have been improved:

Echo Cancellation defaults to "disabled" on modem pass-through calls.

Previously, if AES encryption was enabled and the Modem codec was set for pass-through or relay, fax calls (pass-through or relay) would fail to connect. This has been corrected.

Fax operation with AES encryption has been improved.

• Modem tone detection has been enhanced to prevent voice talk-off to modem mode.
• Previously, a traceroute timeout could cause duplicated TN2602AP configurations to interchange. Also, TN2602AP sometimes would not respond to pings or traceroute packets from other equipment. These issues have been corrected.
• Now, "list trace" commands report accurate information for FAX/Modem pass-thru calls.
• Jitter and packet loss reporting for Fax/Modem/TTY calls has been improved.
• Previously, systems using Fax, Modem, and/or TTY pass-through needed to have the same redundancy values for all three modes. This is no longer required.
• Previously, some third-party DTMF relay could cause DSP failures. This has been corrected.
• Round Trip Time (RTT) reporting to VMM has been improved.
• Debugging capabilities for services personnel has been enhanced to capture information on fax events and DSP resets.

Read Me

TN2602AP Vintage 25 - Read Me

TN2602AP - Firmware Vintage 24

MD5 Sum - e77d3b193d5c38b98be052d68d1513fb

File size - 5165200 Bytes

Released June 5, 2006

TN2602AP Firmware Vintage 24 (FW24) is recommended for all customers.

Improvements have been made to modem, fax, encryption, ping, and VMON/VMM operations. Also, the Time-To-Live (TTL) value for media packets has been increased. See the Read Me file for more information.

Read Me

TN2602AP Vintage 24 - Read Me

Vintage 23

Released April 21, 2006

TN2602AP Firmware Vintage 23 (FW23) is only required for customers who wish to use the TN2602AP bearer duplication feature introduced in Communication Manager 3.1 OR that have a problem addressed by FW23 (see the read me file).

All other customers should use TN2602AP FW12 until further notice.

tn2602ap_f23-sig.bin

TN2602AP Vintage 23 - Signed Firmware

Vintage 21

Released March 20, 2006

TN2602AP Firmware Vintage 21 (FW21) is only required for customers who wish to use the TN2602AP bearer duplication feature introduced in Communication Manager 3.1. All other customers should use TN2602AP FW12 until further notice.

All systems with bearer duplication using FW20 should upgrade to FW21.

tn2602ap_f21-sig.bin

TN2602AP Vintage 21 - Signed Firmware

Vintage 12

Released March 9, 2006

TN2602AP Firmware Vintage 12 (FW12) is HIGHLY recommended for all TN2602AP in simplex or load balancing configurations. FW12 does NOT support the TN2602AP bearer duplication feature introduced in CM3.1!

FW12 contains the following fixes and enhancements:

• FW12 corrects problems that could cause boards to temporarily go out of service. Formerly, these problems caused MEDPROPT 769 2000 and IPMEDPRO 513 4358 errors to be logged.
• Firmware level parameters have been added to allow services personnel to control some settings. E.G. now, comfort noise generation (CNG) can be disabled.
• Previously, some calls on IP stations had static-on-hold problems.
• Corrected echo canceller operation that sometimes caused the remote speaker volume level to drop.
• Previously, when using G729 codecs, very high levels of fax-relay traffic could cause DSP resets. This would result in failed faxes, one-way, and no-way talk paths.
• Improved operation during a denial-of-service (DoS) attack.
• Improved DTMF operation with Cisco SIP phones.

tn2602ap_f12-sig.bin

TN2602AP Vintage 12 - Signed Firmware

Vintage 9

Released November 17, 2005

TN2602AP FV9 is HIGHLY recommended for ALL systems.

The following issues have been corrected:

• Previously, TN2602AP might not properly reconfigure itself in response to certain packet bus failures, potentially causing call processing outages. This has been corrected.
• RTCP reporting, used by Avaya VoIP Monitoring Manager -- aka VMON / VMM, no longer causes one-way and no-way talk paths. Customers should upgrade all their TN2602APs to FV9 before enabling RTCP reporting.
• Hairpinning now works properly.
• When TN2602AP was loaded to near capacity using G.729 encoding, voice quality could degrade. FV9 corrects this condition.
• TN2602AP error reporting has been improved.

tn2602ap_f9-sig.bin

TN2602AP Vintage 9 - Signed Firmware

tn2602ap_f9.bin

TN2602AP Vintage 9 - Firmware

Vintage 7

Released October 21, 2005

TN2602AP Firmware Vintage 7 (FV7) is HIGHLY recommended for ALL systems.

See the Known Issues section below for highly recommended RTCP reporting modifications.

TN2602AP firmware vintage 7 corrects loss of service due to UDP packets that appear to be invalid fax traffic. This condition causes the board test IPMEDPRO 1506 to FAIL with code 1002, taking the board out of service.

tn2602ap_f7-sig.bin

TN2602AP Vintage 7 - Signed Firmware

tn2602ap_f7.bin

TN2602AP Vintage 7 - Firmware