432 Appendix A Patches and advisementsIP Trunk 3.01.22 patchesThe patches applicable to IP Trunk 3.01.22 are:• MPLR18142• MPLR18157MPLR18142FIN_WAIT_2 socket loss and related IXP restart avoidance.MPLR18157TLAN subnet info not recognized if QSIG uses 7-bit channel address.Interoperability with IP Trunk 3.01 (MPLR17662 patch)When upgrading an existing network of IP Trunk 3.0 (3.00.53) nodes toIP Trunk 3.01 (3.01.22), calls from the IP Trunk 3.0 node to the IP Trunk3.01 node may result in memory being corrupted, causing the IP Trunkapplication to malfunction or the IP Trunk card to reboot. One scenariowhere this problem might occur is:1. Two IP Trunk nodes, Node-1 and Node-2, are connected over the IPnetwork.2. Node-1 is running on IP Trunk 3.0. Node-2 is running on IP Trunk3.01, which includes message enhancements to avoid the blocking ofvalid anti-tromboning requests to prevent call swaps with the TrunkAnti-Tromboning (TAT) enhancement. The Endpoint ID (EPID) is new inIP Trunk 3.01.3. The EPID is sent, along with other information, in the SETUP andCONNECT messages. A call placed from Node-2 to Node-1 includesthis information in the SETUP message.4. The existing message decoding logic at Node-1, running on IP Trunk3.0, may incorrectly read the EPID information as ESN5 information.5. Calls from Node-1 to Node-2 do not have this problem.Patch MPLR17662, which is put into service on the IP Trunk 3.0 node,prevents this problem. It enables the node to parse and select the correctinformation and discard the rest. In this scenario, the patch must be loadedon Node-1.In general, to prevent malfunction or reboot, do one of the following:• upgrade all existing IP Trunk nodes to IP Trunk 3.01 in a singlemaintenance window; or• install patch MPLR17662 on all existing IP Trunks first. Only then canthe customer upgrade the existing IP Trunk nodes gradually, node bynode, to IP Trunk 3.01.Nortel Communication Server 1000IP Trunk FundamentalsNN43001-563 02.01 StandardRelease 5.5 21 December 2007Copyright © 2007, Nortel Networks.
