(ASCEND) MAX TAOS 8.0.0 Release

[Matt Holdrege <matt@ascend.com>]

The MAX TAOS 8.0.0 software for the MAX family has been given to Customer 
Support and Manufacturing. Please note that the MAX MultiVoice loads are 
not available at this time. This release contains the following:

New Features

Two attributes added to call-logging packets
Specify passwords for CLID and DNIS authentication
OSPF supports a 16-character key for MD5 authentication
RFC 1850 trap support for OSPF
MAX supports Area Border Functionality (ABR)
Console State Change trap displays IP address
R2 signaling for Mexico
Dual CSMX slot card support
Configuring V.110 modems
SNMP Fatal Log table
Syslog changes
MAXTap option available
Configuring Personal Handyphone Service (PHS)
Support for multiple Virtual Routers introduced
L2TP timer parameters added to L2 Tunneling Options
Store Voice Announcements on pc-flash file system
Quiesce trunks on unregistered Gateways
Real-Time Fax enhancements
Set audio codec selection policy
Delay charges until a call is answered (true connect)
Make T1/T3 DSP inter-digit timer user-configurable
Allow ANI/CLID substitution
Enable early ring-back
New fields in the callStatus and callActive tables
Support for DNS list attempts introduced for L2F and L2TP
Identify record type in Syslog when backoff queue full
Grep-like capability added to the terminal server
Tunnel attribute sets with tags and preferences
Booting the MAX 6000 from a PCMCIA card
Support for SNMPv3 User-based Security Model
RADIUS WINS server parameters
RADIUS bootup server supported
Configure RIP settings on a second Ethernet interface
Limiting excess RADIUS traffic
Serial Console Password Protection
RADIUS authentication for DNIS and Rlogin
Enhanced support for MS-CHAP
Support for European ISDN on 8-port Host/BRI cards
Network Terminating (NT) support for European ISDN PRI
Bidirectional CHAP support
PIAFS protocol version 2.1 support
Tunnel attributes sets with tags and preferences

Corrections

TR Problem corrected
-- -----------------
NA Upgrading from 7.2.3 to 8.0 removed configured IP information and 
displayed incorrect server IP information from the IP FAX menu.
NA MAX occasionally failed to dialout because of an IP Route entry problem.
NA MAX failed to boot when installed with two CSM/3 cards.
NA When an analog and a digital call were made simultaneously to the same 
interface on a BRI card in a MAX3000, the second call caused the first one 
to fail.
NA M3000 E1 CZECH signaling did not work.
NA Nailed calls over T1 Inband only worked at 56k.
NA V.110 protocol was missing from MAX 3000 BRI software loads.
NA MAX 3000 incorrectly displayed an Ethernet IF menu.
NA Non-ISDN calls were occasionally routed to a V.110 device.
NA Occasionally, the MAX failed to create L2TP sessions.
NA Occasionally, the MAX was not able to re-establish nailed connections 
correctly.
NA MAX sent RADIUS state attribute lengths that were non-compliant with RFC 
2138.
NA RADIUS Username & Password lengths were non-compliant.
NA After changing the ethernet interface's second IP address, the subnet 
route for the old address was sometimes left in the routing table.
NA Any modems that are on the Suspect, Warning 195 or Disabled modem lists 
when the modem slot is disabled are left on those lists plus added to the 
Disabled list.
NA When direct routes (over serial/frame relay links) came up, the MAX unit 
did not populate the static routes supporting that interface into the 
routing table.
2712 Radius Call-Filters stopped working when one or more MP+ channels were 
brought up.
2987 MAX4000 was running without V.110 card, but it answered a V.110 call.
3828 You could not disable modems via SNMP if the MAX was answering too 
many incoming calls.
4612 Modem MIB (RFC 1696) support was not in the MAX 800. Modem requests 
could not be obtained even though there were no modem cards.
4679 MAX reset occasionally with FE8 when PPTP was used from PIAFS terminal.
4724 Occasionally, the MAX was not replying to the ARP-Request from the 
remote bridged site machine.
4879 Protection violation errors related to IPX were occurring.
4888 Max units with L2TP configurations would have some configuration 
corruption when upgrading to 7.0+ software.
4922 EchoSuppressToneDisable parameter disabled tone for all calls.
5005 The index of connections in the SNMP Interface Table kept changing on 
reboot/reconnect.
5181 RADIUS accounting was not working when Auth-Type was set to 
RADIUS/LOGOUT.
5201 lanModemGroup MIB had not been implemented on the MAX 800.
5202 The advancedAgent MIB had not been implemented on the MAX 800.
5221 The size of the Calling-Station-Id attribute was incorrect for the 
Radius Access-Request packets sent by the MAX.
1000221 After reboot, the MAX 6000 would not accept or send calls.
250283 Using different trunk numbers for each BRI channel did not work.
258640 The MAX unit was not setting the M-BIT during data transfer between 
the modem client and the X25 Host.
258648 Overlap receiving ISDN mode option was missing in the febk.m40 
software load.
258836 The Max units reset with a FE29 after having received multiple 
Warning 104 messages.
258851 The MAX unit reported incorrect baud rates for L2TP and PPTP sessions
258864 SNMP trap was not being sent when E1/PRI went from DF status to TE 
status.


The following Conexant (formerly Rockwell) firmware versions are supported 
in this release:
--Series56 Digital Modem Modules support Conexant V2.098-K56_2M_DLP_CSM 
firmware, which includes support for V.90, K56flex, K56plus, and all 
slower, standard modem speeds.
--V.34 Digital Modem Modules support Conexant V1.610G24-V34_DP (V.34 
Modem-12) and V1.610G19-V34_DS (V.34 Modem).
The 2.098 Conexant firmware includes a workaround in V.8bis for Lucent 
interoperability, and improved Lucent client V.90 modem connectivity. Users 
still should upgrade their Lucent client modems with new Lucent firmware as 
available.
The 2.098 Conexant firmware also provides the following user features:
--Added S202/bit6 to control V90 high power after V8.
--Added S220 to control answer tone length on Server. By default, S220= 11, 
corresponding to 5 seconds of answer tone. Each unit in S220 corresponds to 
450 ms, because each phase reversal is 450 ms long. For example, S220 = 19 
will increase the answer tone time to 8.6 seconds. S220 = 03 will decrease 
the answer tone time to 1.4 seconds.
--Fixed semicolon (;) handling with +MS command.
The V5.8173 firmware include a fix for synchronization rate failures with 
some PCtel chipset modems. The V5.8173 firmware also provides a fix for 
synchronization failures observed with some Lucent winmodems.


Notice of Modified RADIUS username and password lengths
The following changes were made to bring MAX TAOS 8.0.0 into compliance 
with the IETF RADIUS draft version draft-ietf-radius-radius-v2-03.txt:
--MAX units now send username and password strings without any extraneous 
characters. This brings the unit into compliance with the IETF RADIUS 
draft. Further, the reported username and password lengths are now correct.
--MAX units no longer submit a RADIUS authentication request if the 
password exceeds 128 characters in length. Instead, the unit considers this 
an authentication failure and disconnects the call.

Known Issues:
Issues you should be aware of before loading release 8.0.0 include the 
following:
--MAX 3000 users might need to upgrade memory and firmware before loading 
TAOS 8.0.0. If you have a MAX 3000 unit that is Rev A, Rev B, or a numeric 
revision, you need to order the 32MB SDRAM upgrade kit, part number 
MX30-HO-32MB, before you load TAOS 8.0.0 onto your unit. The unit's 
revision number (Rev) is noted on the large label on the bottom of the 
unit. Call 510-769-6001 (8am - 5pm PST) and ask for order administration to 
obtain the upgrade kit free of charge. The upgrade kit includes a 32MB 
SDRAM DIMM and important instructions for obtaining and loading new boot 
firmware on the MAX 3000 before installing the memory upgrade.

--Change in Call-logging packet format
In releases prior to 7.2.0, the format of Call-logging packets are 
identical to RADIUS Accounting packets. With the introduction of 7.2.0, 
Call-logging will no longer be compatible with RADIUS, although Lucent's 
NavisAccess product fully supports Call-logging. The MAX continues to 
support RADIUS accounting, SNMP and SYSLOG functionality. Because of the 
proprietary nature of and potential modification to call-logging packets, 
you should not use call-logging packets with any application other than 
Lucent's NavisAccess.

--Some multimedia features are not supported in this release. Customers 
using the following features should not upgrade to 8.0.0:
AIM/BONDING
Time-of-day calling
Backup and overflow

--The default value for the parameter CBCP Trunk group was out of the valid 
range. The default value has been changed from 0 to 4. This correction 
might cause a previously saved profile to yield a different value when this 
release is loaded.

--In MAX systems, data flows between T1/E1 WAN ports and host devices such 
as modems and HDLC ports using a limited group of internal data pathways. 
The capacity of these pathways is sufficient to accommodate the built-in 
WAN ports of the MAX. When BRI cards are installed in the system, pathways 
normally allocated for built-in T1/E1 ports are used to support the BRI WAN 
ports, and are not available for T1/E1 usage.

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>