(ASCEND) 7.0.26 for Max

[Matt Holdrege <matt@ascend.com>]

MAX TAOS 7.0.26 software for the MAX family has been given to Customer 
Support. This release contains the following:

Corrections
TR 2987 A MAX unit showed V.110 modems available to process V.110 calls 
when it did not have V.110 modems available.
TR 3828 A MAX unit managed by SNMP did not disable a specified modem.
TR 3940 Telnet users could not connect to a MAX unit when telnetting to a
broadcast IP address by way of a WAN line.
TR 4210 A MAX unit sent ATMP RIP when "ATMP RIP=Off" for Home Agent (HA).
TR 4214 A MAX unit did not use free modems.
TR 4303 Direct SecureID authentication was not supported, and dial-in users 
to a MAX received a Remote Authentication Timeout message.
TR 4323 A MAX unit did not complete a CLID-authenticated, RADIUS connection 
to a PIAFS terminal.
TR 4390 After several hours, a MAX unit supporting permanent ISDN 
connectivity stopped working.
TR 4417 When a Windows user entered an incorrect ID or Password during CHAP
authentication, they did not receive an authentication failure message.
TR 4508 One voice call failed when a MAX placed two simultaneous outgoing 
voice calls on a T1 or T1-PBX line.
TR 4514 A MAX 800 unit installed with PCMCIA modems cold not support 
multiple channel MP or MP+ calls.
TR 4556 IPX header compression caused dialup Windows clients to crash or 
reboot.
TR 4569 MAX unit with RADIUS accounting enabled occasionally reported 
records with an incorrect session ID.
TR 4616 A MAX unit configured to support X.25 reset with an Fatal Error 29.
TR 4679 MAX reset occasionally with FE8 when PPTP was used from PIAFS 
terminal.
TR 4694 A MAX 6000 unit occasionally reset, generating a Warning 179.
TR 4867 In diagnostic mode, a MAX unit generated IPX protection violation
errors.
TR 4888 A system software upgrade corrupted a MAX unit's L2TP configuration.
TR 4926 A MAX unit incorrectly reported Ascend-Num-In-Multilink as zero (0)
whenever a session timed out.
TR 5055 A user could not ping the MAX unit when their connection was
authenticated through a RADIUS server configured to include the
Ascend-PPP-Address attribute.
TR 5075 A stacked-Max unit displayed incorrect Show User's information.
TR 5181 RADIUS accounting was not working when Auth-Type was set to
RADIUS/LOGOUT.
TR 250298 TCP host and dial-in MAX units reported inauthentic values for
accounting attributes Acct-Input-Octets, Acct-Output-Octets, 
Acct-Input-Packets, and Acct-Output-Packets.
TR 258608 Data call from a Multiband VSX to a MAX 2000 Host/Dual call was
cleared with ISDN code 16.
TR 258639 A MAX unit generated an Fatal Error 101 when it initiated a CLID
authenticated connection to a Pipeline unit.
TR 258640 A MAX unit did not complete a transfer between a modem client and 
an X.25 host.
TR 258648 A MAX unit's Overlap Receiving, PRI Prefix, Trailing Digits, and 
T302 Timer parameters were not included in the unit's system software load.
TR 258756 A MAX unit failed to maintain a FTP connection when it used 
Firewall and NAT on the same dialout profile.
TR 258738 During call setup a MAX unit did not allow for network-provided 
CLID authentication.
TR 258766 After sustained usage, a MAX unit stopped creating PPTP tunnels.
TR 258770 RADIUS filtering was not applied to a MAX unit after a
CLID-authenticated callback.
TR 258772 SourceIP Check did not work on some spoofed packets.
TR 258776 A MAX unit reset as it created a point-to-point tunnel, 
generating a Fatal Error 29.
TR 258787 On a Max 200Plus, the Filter-ID setting did not function.
TR 258791 Without referring to a secondary home agent, a MAX terminated a 
tunnel registration process when a primary home agent was unavailable.
TR 258813 A MAX 4000 unit listed unused, available modems as busy.
TR 258836 A MAX unit issued Warning 104, Fatal Error 29 and then reset.
TR 258878 When a user selected X.32 Encapsulation in the Encaps Options
subprofile, a MAX unit did not provide a Password parameter.
TR 1000211 A MAX unit accepted and processed calls on E1 ports that the 
user had set to be disabled.
TR 1000223 A MAX configured to support E1/PRICalls failed to process 
Interface ID information in SETUP message sent from a switch.
TR 1000243 A MAX unit in a stacked environment rebooted with an Fatal Error 8.
TR 1000256 A MAX unit reset when configured as an ATMP Foreign Agent, 
generating a Fatal Error 38.
TR 6000082 Truncated TCP packets lead a MAX unit to infrequently reset with 
an Fatal Error 38.

The following Conexant (formerly Rockwell) firmware versions are supported 
in this release:
Series56 Digital Modem Modules support Conexant V2.098-K56_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).

Known issues:
* 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 is no longer be compatible with RADIUS, although Lucent 
Technologies' 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 Technologies' NavisAccess.
* Some multimedia features are not supported in this release. Customers 
using the following features should not upgrade to 7.0.26: 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 units, 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 unit. 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>