5.0Ap33 for the MAX and Pipeline products has been given to support and manufacturing. This release contains the following: For the MAXen: Corrections: TR# Description ------------------------------------------------------------------- TR 1925 Routes sometimes incorrectly went to WANIDLE. TR 2085 The MAX did not always support two incoming calls on the same BRI line from a 5ESS switch. TR 2259 DSS (Defender) accounting was inaccurately displayed on the MAX. TR 2478 Cannot get second channel into bind in a MAX stack using CHAP- TOKEN-PAP. TR 2533 MAX units running bridging in a MAX stack reset with a FE 2 or 29 and warning 175. TR 2538 The MAX 2000 E1 model did not interpret NET 5 charging information. TR 2554 MAX would not answer ISDN calls after running for 24 hours under heavy load. TR 2690 Fatal Error 2 after running 10 days. TR 2738 FE1 after some modem card failures. TR 2780 MAX didn’t connect to Motorola LifeStyle 28.8 modem. TR 250063 Intermittantly, the MAX stoped routing packets toward the dial-in client. TR 250066 DHCP missing from MAX 2000. TR 250110 MAX inserts additional bytes on backup frame relay PVC. TR 250128 MAX did not release modems running immediate modem sessions were cut off during data transfer. TR 250129 MAX sometimes produced excessive warnings when running TACACS+ accounting. n/a Accomodate HSRP for coredump n/a Rockwell K56 code 1.140 to fix abnormal disconnects n/a Net/T1 "Not Avail" after 5.0Ap32 upgrade Enhancements: ------------------------------------------------------------------------ B-Channel preference when MP+ or BACP adds bandwidth ATMP attributes in RADIUS Accounting Note1: This release contains V1.140A-K56_DLP_CSM of the Rockwell modem code. Note2: A new warning (179) has been added which indicates an anomolous event order occured in terminating a digtal call. These anomolies normally are harmless and have existed in previous releases, but until this release they were not reported. The purpose of the warning 179 is to provide debug information in the unlikely event of a fatal error immediately following the warning. No such fatal events have been observed during testing or early customer deployment. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ For the Pipelines: Correction: TR# Description ------------------------------------------------------------------- 250047 No dialtone in UK on the P75 and P25 with 5.0Ap1 and above -- Patti Kevin ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <HR> <STRONG>Follow-Ups</STRONG>: <UL> <LI><STRONG><A HREF="msg10225.html">Re: (ASCEND) 5.0Ap33</A></STRONG></LI> <UL> <LI><EM>From</EM>: Junichi Kurokawa <jun@sinfony.ad.jp></LI> </UL> </UL> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg10211.html">Re: (ASCEND) ASCEND wdDialout</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg10214.html">Re: (ASCEND) Ideas: Next Release Ap28 or Ap29</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg10223.html">Re: (ASCEND) Re: Suggested LQM settings?</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg10225.html">Re: (ASCEND) 5.0Ap33</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="maillist.html#10215"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd221.html#10215"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>