-
1
- #1
juandebobo
MIS
If you have not updated your firmware on the TN2602's this is a great load. More so if you are using MedPro resources across a network, and having call quality issues.
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.
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.