(ASCEND) 7.2 for the Max 1800, 2000 & 6000

[Matt Holdrege <matt@ascend.com>]

>TAOS Release 7.2.0 for MAX family has been given to customer support.
>TAOS 7.2.0 does not include binaries for MAX 4000 series. TAOS 7.0.x
>releases continue support for the MAX 4000 series.
>
>This release contains the following:
>
>NEW FEATURES
>
>                FEATURE
>*               OSPF supports MD5 authentication
>	          Enhancement to Telnet Security parameter
>*               Ascend-Data-Rate and Ascend-Xmit-Rate added to RADIUS
>Access Request packet
>*               TCP-Clear-Quiet value added to Login-Service attribute
>	          More information for Syslog End-of-Call message
>	          Log Call Progress parameter
>*               Ethernet linkUp and linkDown SNMP traps for MAX 6000
>	          Configuration Change added to Enable traps menu
>*               Restoring a configuration to flash memory 
>*               Copying binary images between PCMCIA Flash card memory
>and internal Flash memory
>	          IP multicasting added to Stack options
>	          Disabling and enabling digital connections
>	          Support for 64 switched Frame Relay connections
>	          Modifications to Id Auth parameter
>	          Show Filters command
>		   Personal Handy Phone Service (PHS) support (Japan and
>Asia only)
>	          ISDN NFAS support for Japanese switch types"
>		   R2 signaling for New Zealand, Thailand, Israel, and
>Kuwait
>*               Configuring a unique L2TP system name
>
>
>
>CORRECTIONS
>
>TR Number     Description
>---------     --------------
> *  2660      Dial in V.110 client could connect to PPTP server behind a
>MAX 
> *  3163      A MAX 2000 did not process a finger request from FreeBSD
>with TCP option selected.
> *  3425      A MAX 1800 showed No Circuit Available; it did not send a
>set up message to switch.
> *  3553      A MAX incorrectly forwarded limited-broadcast packets over
>a WAN link.
> *  3556      Normal Link Down traps were sent from a MAX.
> *  3617      MAX clients were not receiving a phone number. When
>dialing into a MAX using Bandwidth Allocation Control Protocol (BACP),
>the clients attempted to add bandwidth, the Call-Response packet's
>Phone-Delta option did not contain a usable phone number.
> *  3659      A MAX 200Plus did not complete a Zmodem transfer.
> *  3685      In the 50-700 status menu, the MAX showed the Enet I/F:
>AUI when it is plugged into a UTP connection.
> *  3693      A MAX was unable to complete call-by-call terminal server
>calls.
> *  3725      The Ascend Maximum Time attribute did not take affect for
>CBCP sessions.
> *  3757      Incoming calls were not routing properly through PBX-T1
>conversion when pbx type=data and answer service=none.
> *  3766      During a CBCP session, Ascend-Xmit-Rate and
>Ascend-Data-Rate were reported as zero.
> *  3772      A MAX 6000 did not establish more than one nailed
>connection.
> *  3784      A MAX-stacked Ascend unit failed with CLID authenticated
>MP calls.
> *  3845      A MAX did not send a busy signal when a modem dialed a
>busy line.
> *  3848      A MAX 1800 did not drop the second channel when ALU
>dropped below Idle PCT threshold.
> *  3928      During a Telnet session to A MAX, the Edit window
>displayed the Ethernet profile.
> *  3935      A MAX with two PRIs handling analog and IP calls reset
>with FE1.
> *  3940      A MAX incorrectly offered a Telnet connection for a
>broadcast IP address.
> *  3966      A MAX using control port would reset without FE.
> *  3975      A MAX did not send cause code 17 to Net/BRI line.
> *  4001      MAX units reported the wrong Acct-Multi-Session-Id and
>Link-Count values when stacking with MP.
> *  4034      A MAX configured for Pool Summary marked MP/MPP calls as
>non-private.
> *  4040      A MAX reset with FE1 when an encrypted tunnel password was
>sent through RADUIS.
> *  4044      A MAX did not recognize break signals.
> *  4061      A MAX 1800 did not adhere to MP+ thresholds when a call
>failed.
> *  4096      A MAX 6000 had a tload with checksum errors and it failed
>to restart.
> *  4097      When an external flash card was installed, progress
>indicators did not display.
> *  4150      When a customer turned on RADIUS authentication, server,
>accounting, and call logging simultaneously, the server process did not
>start properly.
> *  4169      A MAX reset with FE29.
> *  4191      A MAX 6000 reset without FE during SCM and ftp.
> *  4197      A MAX 2000 system software did not include support for
>OSPF. 
> *  4214      K56-16 modem cards were taking too many bad calls before
>resetting the modem slot with a WARNING 195.
> *  4222      Drop and insert was not working on WAN lines 3 and 4. 
> *  4261      When no IP address was assigned to a router's Ethernet
>interface, static routes based on information contained in profiles were
>not added to the routing table during initialization. 
> *  4303      Direct SecurID authentication was not working. 
> *  4311      When Auto Logout was enabled, the MAX was not falling back
>to the default privileges when a device disconnected from the MAX unit's
>Control port or when power was lost. 
> *  4323      When using PIAFS with RADIUS CLID authentication, calls
>were not connecting across a LAN.
> *  4325      The were 10- to 14-second delays between modem call
>disconnects and "no carrier" at calling modems.
> *  4390      MAX units failed when dialing out over ISDN lines using
>RADIUS-based permanent Connection profiles. 
> *  4417      CHAP authentication failures were resulting in invalid LCP
>responses.
> *  4514      Outgoing analog calls did not work over MPP.
> *  4556      The Novell Client32 IPX client (version 3.1 on Windows 95
>with service pack 1) rebooted when attempting to dial into a MAX with
>IPX header
>compression enabled.
> *  4564      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.
> *  4657      The end-of-call Syslog message did not support all
>tunneling protocols. 
> *  4663      SNMP was not reporting IP addresses correctly for 10Base T
>card ports.
> *  4670      With immediate modem server, in outbound sessions,
>subsequent to the first dialout, the username was not being included in
>RADIUS start records.
> *  4757      Enabling Call Logging without RADIUS accounting and
>authentication was resulting in UDP/IP packets with 0.0.0.0 destination
>address. 
> *  250094      The STOP packet logged on The RADIUS server for X.75
>calls did not contain valid entrAcct-Input-Packets, and
>Acct-Output-Packets. 
> *  250228      A MAX had only one value for Call Back with v.110
>attribute.
> *  250296      MAX sent SETUP for B-Channel before RELEASE was sent for
>that same B-Channel.
> *  258589      A MAX used incorrect Dialing Number and Dialed Number on
>PPTP.
> *  258656      A MAX 6000 did not respond to Appletalk ARP packets that
>were greater than 28 bytes.
> *  258672      A MAX backup PVC did not come up.
> *  258676      Bad clock source on a MAX caused the continuous modem to
>be retrained using DPNSS/DASS 2 lines.
> *  258791      When using ATMP, a FA/HA in the same unit would not
>fallover to a secondary HA when the home network was unreachable.
> *  258680      FE 1 was sent every hour on a MAX.
> *  258688      E1 channel 16 on a MAX 6000 could not be nailed when
>Signalling was set to None.
> *  258692      A MAX exhibited inconsistent x.75 behavior when v.42bis
>compression was used.
> *  258694      Data sent from a POS terminal was lost when the MAX did
>not buffer the 100 bytes.
> *  258701      ISDN overlap received numbers that were not in DNIS.
> *  258722      The avm command showed modems dropping off.
> *  258725      MP/MPP calls failed authentication in a MAX-stacked
>environment.
> *  258728      A MAX failed after running X.25 PAD for several hours.
> *  258730      A MAX reset with FE1 when two Immediate Telnet sessions
>used DNIS authentication.
> *  258748      Multipath external OSPF routes were not deleted from the
>MAX routing table.
> *  258770      When creating a RADIUS profile with CLID callback and
>associated filters, the filters were not applied for the connection.
> *  258772      The SourceIP Check parameter did not work for spoofed
>packets from the same network. 
> *  258776      A MAX was occasionally resetting with an FE 29 when
>using PPTP.
> *  258797      The MAX supported a maximum of 24 simultaneous X.25
>sessions.
> *  259798      The dirdo command failed because the terminal server
>security level was insufficient.
> *  1000032     ATMP automatically set the MRRU to equal The MRU, which,
>for MP/MPP connections, resulted in ATMP dropping many packets.
> *  1000085     MAX modem code would be corrupted, causing calls to
>fail.
> *  1000094     A MAX 6000 as an ATMP HA running IPX did not work.
> *  1000096     R2 signaling did not support a B-5 tone.
> *  1000105     When running IP over ATMP in gateway mode, if the HA's
>network included a NetWare server, the server's IPX/SAP packets were
>passed to the
>HA's ATMP gateway connection to the gateway router. 
> *  1000112     MAX 1800 MP connections failed.
> *  1000114     With Net5 and Aus PRAs on a single MAX, disabling one
>line caused D-channel failure in the other line.
> *  1000115     In an MP Connection profile, Base Ch Count was
>incorrectly read as Max Ch Count for received MP calls.
> *  1000120     Once the default values for highest and lowest X.25 PVCs
>or SVCs have been configured in an X.25 profile, the values could not be
>re-configured to the default (zero) through the menus.
> *  1000126     A MAX supporting both SNMP and ATMP generated Warning
>106 messages.
> *  1000137     On E1 R2 lines, a MAX did not time-out seize-request
>(toward switch) if it did not receive a seize-ack.
> *  1000139     A MAX ifAdminStatus object was not recognized.
> *  1000140     The user could not set the called and calling number
>when configuring an active Connection profile to use X.25/PAD
>encapsulation.
> *  1000145     A MAX rebooted with FE17, Warning 179, while running R2
>outdial connections.
> *  1000146     R2 outdial failed.
> *  1000150     Occasionally, a MAX 6000 reset and generated an FE18
>when supporting R2 call traffic 
> *  1000165     A MAX occasionally reset with an FE 1 when outbound
>calls were unable to connect to a carrier for reasons such as a busy or
>non-existent
>number.
> *  1000186      Occasionally, E1 lines remained in Red Alarm state
>until they were reset.
> *  1000192      On MAX units supporting Chinese R2 lines, CLID
>authentication did not work correctly.
>
>CONEXANT (FORMERLY ROCKWELL) FIRMWARE VERSIONS
>
>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, V.34, and
>all slower, standard modem speeds.
>
>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. 
>
>V.34 MODEM SLOT CARD SUPPORT DISCONTINUED
>
>Software support for The V.34 modem slot cards has been discontinued in
>this release. TAOS 7.0.x releases provide support for the V.34 modem
>slot cards.
>
>KNOWN ISSUES
>
>Issues you should be aware of before loading release 7.2.0 include the
>following:
>
>1. 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 Ascend'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 Ascend's NavisAccess.
>
>2. Some multimedia features are not supported in this release. Customers
>using the following features should not upgrade to 7.2.0:
>
>--AIM/BONDING
>--Time-of-day calling
>--Backup and overflow
>
>3. 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. 
>
>4. 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. The
>following table summarizes how the addition of BRI cards affects the
>availability of built-in WAN ports in various MAX models. These limits
>apply regardless of the type of BRI card used (Net, Host, IDSL, etc.).
>
>WAN ports available when BRI cards are in use: 
>Model           Number of BRI cards             WAN ports available
>MAX 6000        0                               1, 2, 3, 4
>                1                               1, 2, 3
>                2, 3                            1, 2 
>                4, 5, 6                         Unsupported
>
>MAX 2000        0                               1, 2
>                1                               2
>                2                               None
>
>MAX 1800        0                               1 - 8
>                1                               1 - 8
>                2                               Unsupported
>

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