Cisco AS5850 - Cisco IOS Release 12.2 XB

Release Notes for Cisco AS5850 Universal Gateway for Cisco IOS Release 12.2(2)XB15

January 14, 2005

Cisco IOS Release 12.2(2)XB15

OL-1681-01 Rev. O2

These release notes for the Cisco AS5850 universal gateway describe the enhancements provided in Cisco IOS Release 12.2(2)XB15. These release notes are updated as needed.

For a list of the software caveats that apply to Cisco IOS Release 12.2(2)XB15, see the "Caveats for Cisco IOS Release 12.2 XB" section and Caveats for Cisco IOS Release 12.2. The caveats document is updated for every maintenance release and is located on Cisco.com and the Documentation CD-ROM.

Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.2 located on Cisco.com and the Documentation CD-ROM.

Cisco recommends that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/customer/tech_tips/index/fn.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html.

These release notes describe the following topics:

• Introduction

• System Requirements

• New and Changed Information

• MIBs

• Important Notes

• Caveats for Cisco IOS Release 12.2 XB

• Related Documentation

• Obtaining Documentation

• Obtaining Technical Assistance

Introduction

The Cisco AS5850 universal gateway provides the highest concentration of modem, voice, fax and Integrated Services Digital Network (ISDN) terminations available in a single remote access server product. The Cisco AS5850 gateway is specifically designed to meet the demands of large service providers such as Post, Telephone, and Telegraphs (PTTs), regional bell operating companies (RBOCs), inter-exchange carriers (IXCs), and large Internet service providers (ISPs).

For information on new features and Cisco IOS commands supported by Cisco IOS Release 12.2(2)XB15, see the "New and Changed Information" section and the "Related Documentation" section.

System Requirements

This section describes the system requirements for Cisco IOS Release 12.2(2)XB15 and includes the following sections:

• Memory

• Supported Hardware

• Determining the Software Version

• Feature Set Table

Memory

Table 1 Cisco AS5850 Universal Gateway Memory
Image Name	Software Image	Flash Memory	DRAM Memory
Service Provider Plus	c5850-p9-mz	32 MB	512 MB
Service Provider Plus IPsec 56	c5850-k8p9-mz	32 MB	512 MB
Service Provider Plus IPsec 3DES	c5850-k9p9-mz	32 MB	512 MB

Supported Hardware

Cisco IOS Release 12.2(2)XB15 supports the Cisco AS5850 universal gateway. Table 2 lists the supported feature boards.

For detailed descriptions of the new hardware features, see the "New and Changed Information" section.

For additional information about supported hardware for this platform and release, please refer to the Hardware/Software Compatibility Matrix in the Cisco Software Advisor at the following location:

http://www.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi

Table 2 Supported Feature Boards for the Cisco AS5850 Universal Gateway
Supported Boards	Product Description
Port Handling Cards	AS58-324UPC-CC
Route Switch Controller (RSC)	AS58-RSC-2GE
LAN Interfaces	Fast Ethernet 10/100BASE-T (RJ-45)¹ Dual Gigabit Ethernet
WAN Interface Options	Channelized T1 (AS58-24CT1) Channelized T3 (AS58-1CT3/216U) Channelized E1 (AS58-24CE1)

¹The Fast Ethernet is for management purposes only.

Note This release does not support the Enhanced Route Switch Controller (eRSC) card.

Determining the Software Version

To determine the version of Cisco IOS software running on your Cisco AS5850 universal gateway, log in to the Cisco AS5850 universal gateway and enter the show version EXEC command:

Router> show version

Cisco Internetwork Operating System Software

IOS (tm) 12.2 XB Software (c5850-p9-mz), Version 12.2(2)XB15, RELEASE SOFTWARE

Feature Set Table

The Cisco IOS software is packaged in feature sets consisting of software images. Each feature set contains a specific set of Cisco IOS features. Table 3 lists the Cisco IOS Release 12.2(2)XB15 features by technology area.

Cisco IOS Release 12.2(2)XB15 supports the same feature sets as Cisco IOS Release 12.1(5)XV, but Cisco IOS Release 12.2(2)XB15 can include new features supported by the Cisco AS5850 universal gateway. Cisco IOS Release 12.1(5)XV features are listed in the "Feature Set Tables" section of the Release Notes for Cisco AS5850 Universal Access Servers for Cisco IOS Release 12.1 XV at http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/5850/rn5850xv.htm.

Caution

Cisco IOS images with strong encryption (including, but not limited to, 168-bit Triple Data Encryption Standard [3DES] data encryption feature sets) are subject to United States government export controls and have limited distribution. Strong encryption images to be installed outside the United States are likely to require an export license. Customer orders may be denied or subject to delay because of United States government regulations. When applicable, purchaser and user must obtain local import and use authorizations for all encryption strengths. Please contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com.

Table 3 lists the features and feature sets supported by the Cisco AS5850 universal gateway in Cisco IOS Release 12.2(2)XB15 .

Note These release notes are cumulative and list features that are new to Cisco IOS Release 12.2 XB. One of the parent releases for Cisco IOS Release12.2 XB is Cisco IOS Release 12.2(1). To find information about inherited features in this release, refer to Cisco.com or Feature Navigator. For Cisco.com, go to http://www.cisco.com/univercd/home/index.htm, select the appropriate software release under Cisco IOS Software, and click Release Notes. If you have a Cisco.com login account, you can use the Feature Navigator tool at http://www.cisco.com/go/fn.

Table 3 Service Provider Plus Features for the Cisco AS5850
Technology Area	Feature	ED Release
Dial	RSC Handover Redundancy on the Cisco AS5850 Gateway	Cisco IOS Release 12.2(2)XB1
	V.44 LZJH Compression
	V.92 Modem on Hold
	V.92 Quick Connect
Voice	24 Port T1 Trunk Card for Cisco AS5850 Universal Gateway	Cisco IOS Release 12.2(2)XB1
	Full Functional Long Pound
	RADIUS Packet of Disconnect
	Voice H.323/SS7 and SIP Features on the Cisco AS5850 Universal Gateway
WAN	100% ISDN Coverage Using NextPort DSPs	Cisco IOS Release 12.2(2)XB1

New and Changed Information

The following sections list the new hardware and software features supported by the Cisco AS5850 universal gateway for Cisco IOS Release 12.2(2)XB15.

New Hardware and Software Features for Cisco IOS Release 12.2(2)XB2 to Cisco IOS Release 12.2(2)XB15

No new hardware and software features are supported by the Cisco AS5850 universal gateway for Cisco IOS Release 12.2(2)XB2 to Cisco IOS Release 12.2(2)XB15.

Note Cisco IOS Release 12.2(2)XB9 is not distributed for widespread availability. Cisco IOS Release 12.2(2)XB13 does not exist.

New Hardware Features in Cisco IOS Release 12.2(2)XB1

The following new hardware features are supported by the Cisco AS5850 universal gateway for Cisco IOS Release 12.2(2)XB1:

24 Port T1 Trunk Card for Cisco AS5850 Universal Gateway

The 24 Port T1 Trunk Card for the Cisco AS5850 universal gateway adds T1 support to the 24-port E1 card. The 24 channnelized T1/E1 trunk card has three T1/E1 interfaces and each interface supports eight channelized T1/E1 PRI ports. Each 24 channelized T1/E1 trunk card can be installed in the Cisco AS5850 server slots 0 to 5 or 8 to 13. The 24 channelized T1/E1 trunk card contains all necessary functionality to terminate as many as 576 DS0 channels in T1 mode and 720 DS0 channels in E1 mode and uses onboard High-Level Data Link Control (HDLC) controllers to terminate digital ISDN calls. You can use the bantam jacks on the face of the card to monitor a line.

Refer to the following documents for further information:

•Cisco AS5850 Universal Gateway Commissioning Guidelines

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/sw_conf/comm.htm

•Cisco AS5850 Universal Gateway Card Guide

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/hw_inst/5850cg/index.htm

•Cisco AS5850 Hardware Installation Guide

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/hw_inst/5850hig/index.htm

New Software Features in Cisco IOS Release 12.2(2)XB1

The following new software features are supported by the Cisco AS5850 universal gateway for Cisco IOS Release 12.2(2)XB:

100% ISDN Coverage Using NextPort DSPs

This feature provides full coverage for digital calls and performance enhancement for V.120 calls and to be able to terminate synchronous ISDN and V.120 ISDN sessions without any customer intervention. This feature allows the Cisco AS5850 universal gateway to terminate more than 256 ISDN sessions per channelized T3 (CT3) controller when operating in SS7 environments by adding ISDN capacity. This feature is mandatory for wholesale dial installations where ISDN is being used. This feature permits V.120 calls to operate on the NextPort DSP instead of the CT3 controller to reduce activity on the central processing unit and to increase the HDLC call capability.

Full Functional Long Pound

This feature allows an IVR application to detect a long pound (new call request) at any point after the gateway accepts the incoming call. When the calling-party presses "long #", the gateway terminates any current or pending call state and initiates a new call setup.

For further information, refer to the TCL IVR API Version 2.0 Programmer's Guide at:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/vapp_dev/tclivrv2.htm

RADIUS Packet of Disconnect

This feature consists of a method for terminating a call that has already been connected. This "Packet of Disconnect" (POD) is a RADIUS access_reject packet and is intended to be used in situations where the AAA server wants to disconnect the user after the session has been accepted by the RADIUS access_accept packet. This may be needed in at least two situations:

•Detection of fraudulent use, which cannot be performed before accepting the call.

•A price structure so complex that the maximum session duration cannot be estimated before accepting the call. This may be the case when certain types of discounts are applied or when multiple users use the same subscription simultaneously.

Refer to the following document for further information:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ft_pod.htm

RSC Handover Redundancy on the Cisco AS5850 Gateway

Route-Switch-Controller (RSC) Handover Redundancy on the Cisco AS5850 gateway, with its provision of handover-split mode, provides the first phase of high availability to the Cisco AS5850 platform.

If your gateway contains two route-switch-controller (RSC) cards, you can configure your Cisco AS5850 gateway into either of two split modes: classic split or handover split.

Classic-Split Mode

Classic-split (the default) mode maximizes system throughput by splitting slots between two RSCs. Each RSC controls a certain set of slots (slots 0-5 are owned by the RSC in slot 6 and slots 8-13 are owned by the RSC in slot 7), and operates as though slots other than those that it controls contain no cards because those cards are controlled by the other RSC. Configuration on each RSC affects only the slots owned by that RSC. Calls on a failed RSC are lost, but calls on the functioning RSC continue normally. Operating a Cisco AS5850 gateway in classic-split mode is the same as having two Cisco AS5850 access servers, each with a separate set of cards.

Handover-Split Mode

Handover-split mode maximizes system availability by allowing an RSC to automatically take control of the slots, cards, and calls of the other RSC should that other RSC fail. Each RSC is configured identically as appropriate for the full set of cards. During normal operation, both RSCs are active, handling their own slots, cards, and calls just as in classic-split mode. Should an RSC fail, the other RSC takes over control of the failed RSC's slots, goes into extra-load state, restarts the failed RSC's cards, and handles newly arrived calls on those cards—although calls on the failed RSC are lost at the moment of failure. The failed RSC, should it recover or be restarted, remains in standby state until you instruct the active RSC to hand back its newly acquired slots to the standby RSC. This is, in effect, split dial shelf with handover capability.

Refer to the following document for further information:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/handred.htm

V.44 LZJH Compression

V.44 LZJH is a new compression standard based on Lempel-Ziv that uses a new string-matching algorithm that increases upload and download speeds to make Internet access and Web browsing faster. The V.44 call success rate (CSR) is similar to V.42bis with significant compression improvement for most file types, including HTML files. V.44 applies more millions of instructions per second (MIPS) than V.42bis toward the same application data stream and yields better compression rates in almost any data stream in which V.42bis shows positive results.

V.44 supports automatic switching between compressed and transparent modes on NextPort DFC-108NP-bearing platforms. Automatic switching allows overall performance gain without loss in throughput for file streams that are not compressible.

V.44 is globally controlled through dialed number ID service (DNIS), calling line ID (CLID), and resource pool manager server (RPMS) virtual groups, and performance improvement is determined by the LZJH algorithms. The NextPort Dial Feature Card (DFC) is responsible for the ITU implementation of V.44 and the collection of statistics related to the new feature.

To support V.44 LZJH compression, the control switch module (CSM) has been modified. MIBs that show the status of V.42bis have been extended to show V.44 configuration status. New disconnect reasons help manage V.44 session status and debugging.

For further details, please see:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ft_v44.htm

V.92 Modem on Hold

V.92 Modem on Hold allows a dial-in customer to suspend a modem session to answer an incoming voice call or to place an outgoing call while engaged in a modem session. When the dial-in customer uses Modem on Hold to suspend an active modem session to engage in an incoming voice call, the Internet service provider (ISP) modem listens to the original modem connection and waits for the dial-in customer's modem to resume the connection. When the voice call ends, the modem signals the telephone system to end the second call and return to the original modem connection, then the modem signals the ISP modem that it is ready to resume the modem call. Both modems renegotiate the connection, and the original exchange of data continues.

For further details, please see:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ftv92moh.htm

V.92 Quick Connect

V.92 Quick Connect speeds up the client-to-server startup negotiation, reducing the overall connect time up to 30 percent. The client modem retains line condition information and characteristics of the connection to the Internet service provider (ISP), which reduces connect time by avoiding some of the initial signal handshaking. For further details, please see:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ftv92qc.htm

Voice H.323/SS7 and SIP Features on the Cisco AS5850 Universal Gateway

Voice H.323/SS7 and SIP Features on the Cisco AS5850 universal gateway include the following:

Note Although the documents listed below were not written specifically for the Cisco AS5850 gateway, they still apply to the Cisco AS5850 gateway.

•Call Admission Control for H.323 VoIP Gateways

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xa/122xa_2/ft_pfavb.htm

•Cisco H.323 Multizone Enhancements

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/12_2t/pul0244x.htm

•Cisco H.323 Scalability Interoperability Enhancements

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/fth323v3.htm

•Cisco H.323 Version 2 Phase 2

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t1/h323v2p2.htm

•Cisco H.323 VoIP with SS7 for the Cisco AS5300

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/sw_conf/voip/h3ss7_tv.htm

•Cisco High-Performance Gatekeeper

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121limit/121x/121xm/121xm_5/ft_0394.htm

•Configuring H.323 VoIP Gateway for Cisco Access Platforms

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/iosinfo/ios_mods/0044gw.htm

•Configuring Interactive Voice Response for Cisco Access Platforms

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5400/sw_conf/ios_121/pull_ivr.htm

•Configuring T1 CAS for Voice over IP on the Cisco AS5800 Universal Access Server

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/12_2t/ft_t1cas.htm

•Dual Tone Multifrequency Relay for SIP Calls Using Named Telephone Events

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ft_dtmf.htm

•E1 R2 Signaling for the Cisco AS5300 and Cisco AS5200

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/sw_conf/ios_121/5300r2.htm

•Enhancements to the Session Initiation Protocol for VoIP on Cisco Access Platforms

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dtsipgv2.htm

•Fax Relay Packet Loss Concealment

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dt_0393.htm

•Feature Group D Support

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dt_fgd.htm

•H.323 Call Redirection Enhancements

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ftcallrd.htm

•H.323 Version 2 Support

http:/www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/h323v2xb.htm

•Interactive Voice Response Version 2.0 on Cisco VoIP Gateways

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/12_2t/pulskynx.htm

•Inter-Domain Gatekeeper Security Enhancement

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xa/122xa_2/ft_ctoke.htm

•Interworking Signaling Enhancements for H.323 and SIP VoIP

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dt4t323.htm

•ISDN Network Side for ETSI Net5 PRI

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t1/dtpri_n5.htm

•Network Side ISDN PRI Signaling, Trunking, and Switching

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dtpri_ni.htm

•NFAS with D Channel Backup on the Cisco AS5800 Universal Access Server

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/12_2t/ft_nfas.htm

•Prepaid Distributed Calling Card via Packet Telephony

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/0134bowi.htm

•PRI/Q.931 Signaling Backhaul for Call Agent Applications

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/sw_conf/ios_121/0144cors.htm

•PSTN Fallback

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dtpstnfb.htm

•Session Initiation Protocol for Voice over IP on Cisco Access Platforms

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t1/0251clmb.htm

•SIP Gateway Support of RSVP an d TEL URL

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/vvfresrv.htm

•SIP User Agent MIB

–CISCO-SIP-UA-MIB

ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SIP-UA-MIB.my

–CISCO-SIP-UA-CAPABILITY

ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SIP-UA-CAPABILITY.my

•T1 CAS VoIP for Cisco Access Platforms

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/iosinfo/ios_mods/0048t1ca.htm

•T.38 Fax for Cisco Universal Gateways

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5400/sw_conf/ios_121/puldtfax.htm

•Universal Port Resource Pooling for Voice and Data Services

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xa/122xa_2/ftuprp.htm

•VoIP Call Admission Control Using RSVP

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dt4trsvp.htm

Refer to the following document for further information:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122 xb_2/pull_mys.htm

New Hardware and Software Features in Cisco IOS Release 12.2(2)XB

Cisco IOS Release 12.2(2)XB does not support the Cisco AS5850 universal gateway.

MIBs

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://tools.cisco.com/ITDIT/MIBS/servlet/index

If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:

http://www.cisco.com/register

The Cisco AS5850 universal gateway supports the following MIBs:

•CISCO-AAA-SERVER-MIB

•CISCO-ACCESS-ENVMON-MIB

•CISCO-CALL-HISTORY-MIB

•CISCO-CALL-RESOURCE-POOL-MIB

•CISCO-CALL-TRACKER-MIB

•CISCO-CALL-TRACKER-MODEM-MIB

•CISCO-CALL-TRACKER-TCP-MIB

•CISCO-CAS-IF-MIB

•CISCO-DIAL-CONTROL-MIB

•CISCO-ENTITY-FRU-CONTROL-MIB

•CISCO-ENTITY-VENDORTYPE-OID-MIB

•CISCO-ENVMON-MIB

•CISCO-ISDN-MIB

•CISCO-MEMORY-POOL-MIB

•CISCO-MODEM-MGMT-MIB

•CISCO-PING-MIB

•CISCO-POP-MGMT-MIB

•CISCO-PRODUCTS-MIB

•CISCO-QUEUE-MIB

•CISCO-VPDN-MGMT-MIB

•ENTITY-MIB

•IF-MIB

•OLD-CISCO-CHASSIS-MIB

•OLD-CISCO-CPU-MIB

•RFC 1406-MIB

•RFC 1407-MIB

Important Notes

The following sections contain important notes about Cisco IOS Release 12.2(2)XB15 that can apply to the Cisco AS5850 universal gateway.

Field Notices and Bulletins

For general information about the types of documents listed in this section, refer to the following document:

http://www.cisco.com/warp/customer/cc/general/bulletin/software/general/1654_pp.htm

•Field Notices—Cisco recommends that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/customer/tech_tips/index/fn.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html.

•Product Bulletins—If you have an account on Cisco.com, you can find product bulletins at http://www.cisco.com/warp/customer/cc/general/bulletin/index.shtml. If you do not have a Cisco.com login account, you can find product bulletins at http://www.cisco.com/warp/public/cc/general/bulletin/iosw/index.shtml.

•What's New for IOS — What's New for IOS lists recently posted Cisco IOS software releases and software releases that have been removed from Cisco.com. If you have an account with Cisco.com you can access What's New for IOS at http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml or by logging in and selecting Software Center: Cisco IOS Software.

Caveats for Cisco IOS Release 12.2 XB

Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats document.

This section contains only open and resolved caveats for the current Cisco IOS maintenance release.

All caveats in Cisco IOS Release 12.1(5)XV are also in Cisco IOS Release 12.2(2)XB15.

For information on caveats in Cisco IOS Release 12.1(5)XV, see the "Caveats" section in the Release Notes for the Cisco AS5850 Universal Gateway for Cisco IOS Release 12.1 XV at http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/5850/rn5850xv.htm.

Note If you have an account with Cisco.com, you can also use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and click Service & Support: Software Center: Cisco IOS Software: BUG TOOLKIT. Another option is to go to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.

Open Caveats—Cisco IOS Release 12.2(2)XB15

There are no open caveats specific to Cisco IOS Release 12.2(2)XRelease 12B15 that require documentation in the release notes.

Resolved Caveats—Cisco IOS Release 12.2(2)XB15

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB15. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 4 Resolved Caveats for Cisco IOS Release 12.2(2)XB15
DDTS ID Number	Description
CSCec87533	ios fw hang then crash with h323 corrupt packet Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml.

Open Caveats—Cisco IOS Release 12.2(2)XB14

There are no open caveats specific to Cisco IOS Release 12.2(2)XB14 that require documentation in the release notes.

Resolved Caveats—Cisco IOS Release 12.2(2)XB14

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB14. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 5 Resolved Caveats for Cisco IOS Release 12.2(2)XB14
DDTS ID Number	Description
CSCdx76632	as5300 crashed in MultiBitDecode Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml.
CSCea19885	Bus error at address 0xD0D0D0B, Process CCH323_CT Symptoms: A Cisco router that has a voice feature such as H.323 enabled may reload because of a bus error at address 0xD0D0D0B. Conditions: This symptom is observed on a Cisco 3700 series but may also occur on other routers. Workaround: There is no workaround.
CSCea27536	Router crash when H323v3/v4 pkts pass through NAT router Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml. NAT router (which is H323v2 stack aware) crashes when H323v3/v4 pkt is processed as "ip nat service h323all" is turned on. Workaround: Turn off "ip nat service h323all" or move to 12.3T image (which has NAT-H323v3/v4) support
CSCea32240	H323 crashes in strncpy when receiving invalid setup packet Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml.
CSCea33065	H323 Spurious memory access in h450ProcRcvdApdus Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml.
CSCea36231	Router hangs when receive in invalid h225 setup Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml.
CSCea46342	h.323 crashes in ACFnonStandardInfo DEC_ERR=13 Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml.
CSCea51030	h323: proxy crashes when malformed h225 setup message received Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml.
CSCea51076	h323: proxy crashes when processing invalid h225 setup messafe Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml.
CSCea54851	h323 proxy: crash at pxy_proc_recv_SETUP when invalid h225 setup rx Cisco products running IOS contain vulnerabilities in the processing of H.323 messages, which are typically used in packetized voice or multimedia applications. Features such as NAT and IOS Firewall must inspect H.323 messages and may be vulnerable as well. A test suite has been developed by the University of Oulu to target this protocol and identify vulnerabilities. Support for the H.323 protocol was introduced in Cisco IOS Software Release 11.3T, and all later Cisco IOS releases are affected if configured for various types of Voice/Multimedia Application support. The vulnerabilities can be exploited repeatedly to produce a denial of service (DoS). There are workarounds available that may mitigate the impact, but these techniques may not be appropriate for use in all customer networks. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040113-h323.shtml.
CSCea93727	Support for TI PCI bridge on 5850 Feature boards Symptom: On the Cisco AS5850 universal gateway, the protocol control information (PCI) to PCI bridge part used on the line cards will no longer be available. The older part will be replaced by a newer part from Texas Instruments. These changes are needed to support the line cards containing the newer parts, as well as the older line cards. Workaround: There is no workaround.
CSCeb78836	h323: software forced crash if bad packet received and debug opened Symptoms: Cisco IOS software may cause a Cisco router to reload unexpectedly when the router receives a malformed H.225 setup message. Conditions: This symptom is observed on a Cisco 1700 series that runs Cisco IOS Release 12.2(13c). The symptom occurs when the following debug privileged EXEC commands are enabled: •debug h225 asn1 •debug h225 events •debug h225 q931 Workaround: There is no workaround.

No Caveats—Cisco IOS Release 12.2(2)XB13

Cisco IOS Release 12.2(2)XB13 does not exist so no caveats are documented.

Open Caveats—Cisco IOS Release 12.2(2)XB12

This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB12 and describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 6 Open Caveats for Cisco IOS Release 12.2(2)XB12
DDTS ID Number	Description
CSCeb43411	dCEF packet drops with Virtual Profile users Symptom: On a Cisco AS5850 server with dCEF enabled and ISDN users that are terminating on a Virtual-Access interface (Virtual-Profile config), it is observed that after some uptime, users fail to receive IP traffic from a source other than the router itself. The client is still reachable from the NAS, and PPP/IPCP remains up, however all traffic that is forwarded from the GigE interface to the Virtual-Access interface appears to be silently dropped. Conditions: Currently, this issue is observed on Cisco AS5850 access servers, and only if distributed CEF (dCEF) is enabled. Furthermore, this is only observed with calls that are terminated on a Virtual-Profile Virtual-Access interface. Legacy calls that are terminated directly on the physical interface, or Multilink PPP calls, are not affected. Workaround: Reload the NAS.
CSCeb69182	Router reloads unexpectedly at pm_spe_busyout_cb() Symptom: A Cisco AS5850 access server may unexpectedly reload on OIR of FB. This is reproducible. This may be service impacting. Workaround: There is no workaround at this time.

Resolved Caveats—Cisco IOS Release 12.2(2)XB12

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB12. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 7 Resolved Caveats for Cisco IOS Release 12.2(2)XB12
DDTS ID Number	Description
CSCdp42990	Modem log shows false outgoing calls Symptom: On rare occasions, a Cisco AS5300 or Cisco AS5800 access server, with MICA modems, is seen to place spurious outbound calls, even if configured not to allow such calls. These calls fail to train up; an examination of the modem log shows them to be placed to garbage hexadecimal addresses. Sometimes these spurious outbound calls are placed while in the middle of an active modem session, often shortly following a speedshift. Any active call is terminated shortly following the dialout attempt. Here are some examples of such calls, as seen in the modem log: `02:59:57: ISDN outgoing called number: ADAADBADAC` `08:43:32: ISDN outgoing called number: DBDD2D` `01:28:33: ISDN outgoing called number: AAC102A` Workaround: If using an image with the CSCdw44612 fix (12.2(7.6+)*), and if there is no need to allow outbound calls, then configure modem dial in on the modem lines. This does not prevent the spurious outbound call events from hanging up the calls active on the affected lines, but does prevent an outbound call attempt from being signaled to the circuit network.
CSCdu53400	Incorrect count in sh call calltracker summ after digital call down Symptom: In the Cisco AS5800 access server environment with SS7 setup, the show call calltracker summary command is not showing the correct number of calls for MLPPP digital calls after the calls are being torn down. This occurs due to the sh call calltracker active still displaying some digital calls that have already been torn down. Async modem calls are working properly. Workaround: There is no workaround.
CSCdz80238	Modems suddenly download portware...portware download fails Symptom: MICA portware download fails on Cisco AS5300. Modems are marked bad. Conditions: The trigger for this issue is not yet known. Workaround: There is no workaround.
CSCea02945	Memory leak in AAA Attr List when EXEC author uses local RADIUS Symptom: A Cisco router may experience a memory leak if the AAA EXEC authorization method list is configured to use local then RADIUS. Workaround: Disable EXEC authorization or use RADIUS then local.
CSCea11487	Framed-callback with user defined callback number fails Symptom: When using Framed-callback and the callback number needs to be specified by user input, you get the next message: `*Feb 6 09:55:16: Se7/1:0 MCB: Callback not authorized for this user ww` The excepted behavior is that the NAS should proceed with Microsoft Callback and callback to user. However, the NAS negotiates Callback 'None'. `Feb 6 09:55:12: Se7/1:0 MCB: O Request Id 19 Callback Type None` This behavior is incorrect. Workaround: Using Callback with Cisco-AV-pair and the empty dial string option. Configuring MS Callback Between a Router and a Windows PC http://www.cisco.com/en/US/tech/tk801/tk36/technologies_configuration_example09186a0080094338.shtml Configuring PPP Callback with RADIUS http://www.cisco.com/en/US/products/sw/secursw/ps2086/products_configuration_example09186a0 080093dc9.shtml#output2 Configuring PPP Callback over ISDN with an AAA Provided Callback String http://www.cisco.com/en/US/tech/tk713/tk507/technologies_configuration_example09186a00800946ff.shtml
CSCea20210	sh controller E1 does not show the line status of DSOs (ABCD values) Symptom: Command show controller E1 does not display the line status of DSOs (ABCD values) on a Cisco Access Server AS5850 running Cisco IOS Release 12.2(2)XB10 and Release 12.2(13)T. This is a issue with only the show command and it does not effect any real-time performance nor hamper any call treatment. It just hampers an effective way to troubleshoot the line. Workaround: There is no workaround.
CSCea69547	Busied Out Modem counters not increasing upon firmware download Symptom: On a Cisco AS5300 access router, the busyout counter may not be incremented per port when the module is recovered by using maintenance action. Workaround: There is no workaround.
CSCea69740	Need to be able to SHUT down the NextPort modem in any state Symptom: When a bad port/SPE is shut down, the show spe command shows the port state as 'B' and not 's'. Conditions: A bad port/SPE when shutdown Further Problem Description: If a SPE in bad state is shut down, the show spe command shows the state as 'B' and not 's'. If a port/SPE is shut, then it really doesn't matter what state the modem is in. So the state displayed should be 's' and not 'B'. Workaround: There is no workaround.
CSCea75851	Attribute 195 reported as No Reason Symptom: Attribute 195 may report No Reason cause on Cisco AS5800 access server running Cisco IOS Release 12.2(2)XB10. Workaround: There is no workaround.
CSCea77220	Extra accounting STOP record generated if guard timer enable Symptom: An unexpected resource accounting stop record is being sent after the ISDN guard timer expires. Conditions: This occurs under some very specific conditions, namely: 1. ISDN guard timer is configured to accept on expiry; 2. Stop-failure resource accounting is configured; and 3. Pre-authentication is held up (e.g. due to the unavailability of the AAA server). Workaround: Configure the aaa session-id unique command.
CSCea79607	First Outgoing CONFREQ not received by Windows PPP clients Symptom: First outgoing CONFREQ is not received by the PPP Windows DUN client. Conditions: LCP negotiation takes a longer time. Workaround: Make all connections into the NAS dedicated by configuring the async mode dedicated command under the Group-Async interface.
CSCeb08802	DS0 info of CAS T1s not reported in RADIUS accounting Symptom: RADIUS accounting for CAS T1s may not report on the DS0 information. Conditions: This occurs on a Cisco AS5400 with CAS T1s provisioned. Workaround: There is no workaround.

Open Caveats—Cisco IOS Release 12.2(2)XB11

This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB11 and describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 8 Open Caveats for Cisco IOS Release 12.2(2)XB11
DDTS ID Number	Description
CSCea75851	Attribute 195 may report No Reason cause on Cisco AS 5800 running 12.2(2)XB10. Symptom: Attribute 195 may report No Reason cause on a Cisco AS 5800 that is running Cisco IOS Release 12.2(2)XB10. Workaround: There is no workaround.
CSCea27180	Symptom: Cisco AS5800 running Cisco IOS Release 12.2(XB)10 may reload with following error. `Feb 9 10:32:58.635: %SYS-3-OVERRUN: Block overrun at 203A4358 (red zone 00080000)` `-Traceback= 60580B48 60583B80 60585D78 60585FE8 6057414C 60574138` This happens due to memory corruption. Conditions: None found. Workaround: There is no workaround. More details: Customer is suggested to configure debug sanity and commands to write core files when system reloads due to unexpected events.
CSCea83232	Modems failing to negotiate data compression fail in autoselect Symptom: On a Cisco Systems AS5xxx access server running NextPort technology, some modem connections may exhibit failures where EC/DC negotiation fails. Workaround: There is no workaround.

Resolved Caveats—Cisco IOS Release 12.2(2)XB11

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB11. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 9 Resolved Caveats for Cisco IOS Release 12.2(2)XB11
DDTS ID Number	Description
CSCdr31105	Need to differentiate modem states of shut and busyout Symptom: A modem placed in shutdown state shows up in show modem as a busy out modem whereas its in the shutdown state. Conditions: Issuing a shutdown under the modem and then following it up with a show modem will exhibit the problem. Workaround: Issuing the command show line <nn> will show the modem in shutdown state. This issue is now resolved.
CSCdt58342	Excessive FIRMWARE_RUNNING/FIRMWARE_STOPPED messages Symptom: On a Cisco AS5300 with a "+" E1/T1 trunk card, the console may display the following error messages: `Feb 28 06:54:37 %DSX1-1-FIRMWARE_STOPPED: T1/E1 Firmware is not running` `Feb 28 06:54:38 %DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware is running` The FIRMWARE_RUNNING message appears a few seconds after the FIRMWARE_STOPPED message. This may recur irregularly at intervals of several minutes or hours. These messages are believed to be cosmetic only and not service impacting. Workaround: There is no workaround.
CSCdu15973	ISDN should reject V110 calls based on LLC octet 5a Symptom: When router receive a V.110 call with User rate = 0, even the call is an asynchronous call and not in-band negotiable, ISDN still passes the call to the application. Conditions: V.110 call, User Rate = 0, Async call AND NOT in-band negotiable Workaround: There is no workaround.
CSCdu47222	Modem status messages passed to EXEC process Symptom: When a user is logs in to a Cisco 3620 router using an external modem, the RING and CONNECT status messages pass to the EXEC process. An unknown command error results when the status messages that are passed to the EXEC process are interpreted as commands. Workaround: There is no workaround.
CSCdu58902	GW piggybacks when piggybacking turned off Conditions: This problem can occur when MGCP piggybacking is turned off and when the gateway is attempting to send an command at the same time as it is sending an Ack to a CA initiated command. Symptom: The Ack is piggybacked to the command. Workaround: There is no workaround.
CSCdu80540	System crashes when user tries to delete file with ciscoFlashMiscOpT Symptom: When a user tries to delete a file using ciscoFlashMiscOpTable with ciscoFlashMiscOpDestinationName set to a string that is greater than 33 characters, the system may crash. This caveat has been fixed in Cisco IOS Release 12.1(8)ES and later releases. Workaround: There is no workaround.
CSCdv29225	5300 returns channel state to IDLE after receiving GSM OOS from SC Symptom: On a Cisco AS5300 universal access server that is running Cisco IOS Release 12.2(2)XA1 in a Signaling System 7 (SS7) Interconnect for Voice Gateway solution, if a call is made ingress to the solution from a Public Switched Telephone Network (PSTN) and if a requested continuity test (COT) fails, the Cisco SC2200 signaling controller will send a group service message to the Cisco AS5300 and puts the associated channel on the access server into the maintenance state. However, the Cisco AS5300 puts the associated channel into the idle state a few seconds later. This behavior creates a mismatch in the channel state between the signaling controller and the Cisco AS5300. Workaround: There is no workaround.
CSCdw07873	modem dialout controller command not available on AS5800 and AS5850 Symptom: The line command modem dialout controller is not available on the Cisco AS5800 Access Server platform. Workaround: There is no workaround.
CSCdw18198	Parser cache entry may get deleted when in use Symptom: Under rare circumstances a router generates a traceback error or reload if both of the following conditions occur: •A background process is processing a parser command (for example: pre-clone command or no pre-clone command for vtemplate), and •Another command is issued at the console (most common is the show interface virt 1 command). Workaround: There is no workaround.
CSCdw24379	RADIUS attribute Framed-Filter attribute parsing incorrect Symptom: Framed-Filter attributes with a value which contains multiple "." characters is not parse correctly. Workaround: Do not use the "." character unless it is used to delimit the suffix with ".in" or ".out".
CSCdw86366	Router crashes during Callerid callback Symptom: With caller ID callback configurations, the server crashes. This doesn't happen when a single link is called back, but with multiple links. Workaround: There is no workaround.
CSCdw92035	Cisco IOS forces MICA to turn off EC and Compression with Modem pooling Symptom: Calls that are routed to nondefault modem pools may not be able to negotiate error correction or compression and may be limited to V.34 speeds. Conditions: This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(8)T and when multiple modem pools exist on the server. Workaround: Place all modems into the default modem pool or use the dedicated asynchronous mode on asynchronous interfaces to give client modems more time to fall back to asynchronous framing (this works only for PPP connections). First Alternate Workaround: Disable error correction or compression, or disable both, on client modems. Second Alternate Workaround: Use resource pooling instead of legacy modem pooling.
CSCdx10977	%SCHED-3-THRASHING:watched message event:AAA ACCT Proc Symptom: When the clear modem command is issued on the Cisco AS5800 that is running the Cisco IOS Release 12.2(02)XB05 image, there can be %SCHED-3-THRASHING at the watched message event in AAA accounting process. Workaround: There is no workaround.
CSCdx11089	Change password sequence broken: 12.2T + CS Unix Symptom: It may not be possible to activate the change password sequence through a Telnet session to a router that is using TACACS+ user authentication. Conditions: This symptom is observed on a Cisco router that is using a CiscoSecure UNIX (CSUNIX) TACACS+ server and that is running Cisco IOS Release 12.2 T. Workaround: There is no workaround.
CSCdx18084	spur mem access at np_dsplib_signaling_active_ntf on egress COT call Symptom: In an SS7 for interconnect on voice gateways configuration, a traceback is seen on the Cisco AS5850 if the customer is doing egress continuity test (COT). Conditions: If the customer is running Cisco IOS Release 12.2(02)XU and doing egress COT on a Cisco AS5850. Workaround: There is no workaround.
CSCdx28879	Spurious mem access due to preauth_do_author() for vpdn call initiat Symptom: When a virtual private dial-up network (VPDN) call is made with authentication, authorization, and accounting (AAA) preauthorization, a traceback is observed because of a spurious memory access made by a preauth_do_author function call. Conditions: This symptom is observed on a Cisco AS5300 when preauthorization is configured with only the aaa group server radius 7777 command. Workaround: Configure the dnis required customer profile configuration command.
CSCdx32763	RADIUS decode error when Filter-Id attribute is null terminated Symptom: A Cisco access server that is running Cisco IOS Release 12.2(4)T or later releases may reject a RADIUS authentication response from a RADIUS server when the profile includes the Filter-ID attribute which is terminated with a NULL. Workaround: Stop the RADIUS server from including the NULL character at the end of the Filter-ID attribute or to downgrade to mainline Cisco IOS Release 12.2 software.
CSCdx54449	router crashed when 100 concurrent x25 sync telnet sessions issued Symptom: Router reloads when 100 concurrent x25 sync telnet sessions issued. Conditions: Only happens with large number simultaneous X25 sync telnet sessions. Workaround: There is no workaround. This issue is now resolved.
CSCdx56527	Memory leak of 20M/Day until crash Symptom: A router may reload after a memory leak occurs. Conditions: This symptom is observed on any Cisco router that is running Cisco IOS Release 12.2 (or Cisco IOS Release 12.2B or Cisco IOS Release 12.2 T). The memory leak is triggered by authentication, authorization, and accounting (AAA) when AAA attempts to enable TCP header compression twice within the same user session. Workaround: Disable TCP header compression when a RADIUS or AAA database is used.
CSCdx72670	router reload in ip_build_outputQ on clear ip mroute Symptom: Between the PIM process and the timer wheel process, there is data corruption which causes crash. Workaround: There is no workaround.
CSCdy07358	Alignment errors in ipfrag_init process Symptom: A Cisco 7200 router that is running Cisco IOS Release 12.1(15.5) and is configured as an LNS in a VPDN environment may suffer alignment errors in the ipfrag_init function. The problem does not have any adverse reaction on the router but could impact performance slightly. Workaround: There is no workaround.
CSCdy34419	Getting %DS_MODEM-3-LOW_PARTICLES:Not enough particles messages Symptom: A Cisco AS5800 running Cisco IOS Release 12.2(10b) may exhibit following messages `2w2d: %DS_MODEM-3-LOW_PARTICLES: Not enough particles - modem number:15` `particles needed:1 available:0; CTS off` `Aug 12 02:47:46.804: %DIAL3-3-MSG:` `2w2d: %DS_MODEM-3-OUTPUT_DROP: Output drop - modem number:15 refunded 1;` `particle count 0, pool size 11429, queue size 80` `Aug 12 02:51:08.165: %DIAL4-3-MSG:` Conditions: Normal modem traffic can lead to these symptoms after few weeks of the router reload. Workaround: There is no workaround.
CSCdy51329	Problems with modem mgmt introduced by CSCdx48036 Symptom: With the debug csm mod command enabled, the following debug message is now output upon each modem call: `DAS_ST_MODEM_ERR(1/0): modem_mgmt_get_modem_parm: not MICA` Conditions: This message is from a Cisco AS5850 with no MICA boards. All ports are NextPort DSPs. Workaround: There is no workaround.
CSCdy63815	OLD-CISCO-TS-MIB tsLineUser empty with AAA RADIUS and local user Symptom: An empty value is returned for the tsLineUser value in the OLD-CISCO-TS-MIB MIB. Conditions: This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(2)XB6 with authentication, authorization, and accounting (AAA) RADIUS and that has a local user configuration. The tsLineUser value of the OLD-CISCO-TS-MIB is populated when Cisco IOS 12.1(5)T8 is used. Workaround: There is no workaround.
CSCdy72086	Torch RSC drops all digital calls after the 421st call is setup. Symptom: The 421st call cannot be made and existing calls thereafter drop. Conditions: With a configuration to bring up 450 digital calls, existing digital calls start dropping after the 421st call. Workaround: Need to configure 'dialer pool-member 1' on serial6/1:15
CSCdy73370	Invalid user info displayed in CallTracker Symptom: Calltracker records are incorrectly reported for modem calls. The userid, IP address and mask are wrong. Workaround: There is no workaround.
CSCdz00204	no aaa nas port extended has no effect Symptom: With the Cisco IOS Release 12.2(2)XB6 image, the NAS port format is the same (for example "Async1/01*Serial3/0:2") with and without the no aaa nas port extended command configured. With the Cisco IOS Release 12.2(2)XA5 image, this is not a case. Workaround: There is no workaround.
CSCdz00304	Acct-Authentic attribute not correct in some scenarios Symptom: RADIUS accounting attribute 45 (Acct-Authentic) may have a wrong value under some circumstances. Workaround: There is no workaround.
CSCdz01366	Multihop router Crashs with port flap: PPPoA/L2TP multihop Symptom: A multihop router may reload because of a port flap. Conditions: This symptom is observed when there are 940 PPP over ATM (PPPoA) sessions with 50 ingress and 10 egress tunnels configured on a Cisco router running Cisco IOS that is employed as a multihop router. Workaround: There is no workaround.
CSCdz02435	Autoselect PPP loop resulting in AOL client step 3 failures Symptom: PPP autoselect in a loop results in null username failures. Conditions: This bug will affect all AS5xxx series of Access Servers. Workaround: Enable flush-at-activation under the lines and load an image which has the fix for this DDTS.
CSCdz04349	User-name not included in accounting with nocallback-verify Symptom: When nocallback-verify is configured for a ppp microsoft callback client, dialing into a Cisco Access Server, it is possible that the username attribute is not included in the AAA accounting records. Workaround: There is no workaround.
CSCdz17327	NEAT firmware corruption:FIRMWARE_RUNNING/FIRMWARE_STOPPED Symptom: Intermittently the T1 controller firmware may stop running. Following message will indicate such a problem: `%DSX1-1-FIRMWARE_STOPPED: T1/E1 Firmware is not running` `%DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware is running` `%DSX1-1-FIRMWARE_STOPPED: T1/E1 Firmware is not running` `%DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware is running` `%DSX1-1-FIRMWARE_STOPPED: T1/E1 Firmware is not running` `%DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware is running` `%DSX1-1-FIRMWARE_STOPPED: T1/E1 Firmware is not running` `%DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware is running` Conditions: This is a very rare problem. When this happen the calls may stay up on the affected T1/E1. But it may make the graceful provisioning of new T1/E1 impossible. Workaround: Reloading the Cisco IOS will initialize the T1/E1 controller firmware.
CSCdz18330	Tacacs cmd authorization doesnt work with directed requests Symptom: TACACS+ command authorization on a Cisco router running Cisco IOS Release 12.2(11)T1 fails when used by users that logged in using the TACACS directed-requests feature (user@<address>). The router incorrectly uses the full username (including the @<address>) to authorize commands against the TACACS server. Workaround: There is no workaround.
CSCdz21534	T1 remote line loopback fails on CT3 card Symptom: A T1 in a channelized T3 port (CT3) dial feature card (DFC) goes into a loopback. This can cause the remote to receive Path Code Violations (PCVs) and sometimes Loss of Signal (LoS). Conditions: This symptom is observed on a CT3 DFC on a Cisco AS5400 router. Workaround: Cable a hard loop to test from the network to the T3 of the Cisco AS5400.
CSCdz23256	SYS-2-LINKED: Bad dequeue messages periodically reported on AS5800 Symptom: The following message has been periodically reported on all platforms running Cisco IOS Release 12.2(12.6): `Nov 6 09:22:17.364 CET: %SYS-2-LINKED: Bad dequeue of 62C3B194 in queue 69408DAC` `-Process= "<interrupt level>", ipl= 4` `-Traceback= 6055A354 604FFAFC 60398F10 60398E44 60B94720 60398C24 6039B380 6039A018 6000F8C4 6015EA80 601624CC 605BDD20 60162358 60B94484 60B92B68 60B295D8` Conditions: Problem happens on all platforms running Cisco IOS Release 12.2(12.6), with active X.25 or LAPB serial connections, when LAPB retransmissions are occurring with moderate-to-heavy traffic. Workaround: There is no workaround.
CSCdz27817	1Khz tone on ide CAS trunk -19.9 db Symptom: A T1 channel-associated signaling (CAS) trunk may produce a 1-kHz tone at 19.9 dB while the trunk is in the idle state. Conditions: This symptom is observed on a T1 CAS trunk that is running Cisco IOS Release 12.2(11)T. This symptom does not affect normal call operation. Workaround: The problem has been fixed in the latest releases.
CSCdz30790	T3 controller link up/down traps not sent for snmp Symptom: On a Cisco AS5400 router, Simple Network Management Protocol (SNMP) linkchange traps are not generated for a T3 controller up and down state changes. Conditions: This symptom is observed on a Cisco AS5400 router that is running a c5400-is-mz.122-2.XB9 image of Cisco IOS software and that is configured with the following router configuration command: snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart Workaround: There is no workaround.
CSCdz34487	tacacs+ password change sequence broken Symptom: The password change sequence does not work as expected when it is used with Cisco Secure Access Control Server software. The user can still access the router with the old password. User can change the existing password to a new password at a later time. Conditions: This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(11)T. This problem was not noticed in 12.2(13)T image with Cisco Secure Access Control Server running on an NT box. Workaround: There is no workaround.
CSCdz38708	5800 with E1R2 may not accept modem calls Symptom: When terminating incoming E1 R2 calls on a Cisco AS5800 Access Server with MICA modems, a large percentage (up to 100%) of calls may fail. Debugging on the NAS shows that ANI/DNIS collection succeeds and the call is cleared by the switch shortly after sending the line answer ABCD bits. Debugging on the switch side shows that the interregister signaling answer signal (B6 by default) is never terminated before sending the line answer signal. Conditions: This problem is seen on a Cisco AS5800 series Access server using MICA modems and configured for compelled E1 R2 signaling. The problem is not seen on Cisco AS5300 or AS5850 Access Servers or on Cisco AS5800 with NextPort card, and it does not occur with semi- or non-compelled E1 R2 signaling or any other signaling type. In addition, this problem only affects incoming calls. Workaround: There is no workaround.
CSCdz39284	SIP: PROTOS Test Group 5 - Test Cases 330 to 435 causes as5350 crash Symptom: Multiple Cisco products contain vulnerabilities in the processing of Session Initiation Protocol (SIP) INVITE messages. These vulnerabilities were identified by the University of Oulu Secure Programming Group (OUSPG) "PROTOS" Test Suite for SIP and can be repeatedly exploited to produce a denial of service. Conditions: This issue is observed on Cisco devices which contain support for the SIP protocol and are running vulnerable versions of software. Workaround: Cisco will be making free software available to correct the problem as soon as possible. Additional workarounds will be documented in the Security Advisory. This advisory is available at: http://www.cisco.com/warp/public/707/cisco-sa-20030221-protos.shtml
CSCdz40483	%SYS-2-WATCHDOG: Process aborted on watchdog timeout, process = IP I Symptom: A Cisco router permanently pauses with a watchdog timer under normal operation. Conditions: This symptom is observed when the router is a voice endpoint with active calls. Workaround: There is no workaround.
CSCdz44203	Dynamic Dialer map not created with aaa authentication if-needed Symptom: Users connecting to a Cisco AS5350, using a post dial terminal window for authentication, may not be able to ping the Cisco AS5350 after connecting. This problem only occurs with aaa authentication ppp <list> if-needed configured. The root of the problem is that a dynamic dial map is not created for the user. This can be seen with the show dialer map command. The other symptom of this problem is that there will be no output packets on the async interface to which the user is connected. Workaround: Reconfigure the router to use virtual-profiles, or remove "if-needed" from the AAA authentication command.
CSCdz45885	AAA POD not disconnecting client requests with 8-byte session id Symptom: An authentication, authorization, and accounting (AAA) packet of disconnect (POD) server may not disconnect a client request that has an 8-byte session ID. Conditions: This symptom may occur on a Cisco AS5400 or a Cisco AS5850 that is functioning as a triple A POD server. Workaround: There is no workaround.
CSCdz51403	NAS-port attribut 5 has been changed for format C Symptom: VTY interface is not supported with extended NAS-PORT format. Workaround: There is no workaround.
CSCdz51941	Call drops once the Card is OIRed in case of NFAS. Symptom: On a Cisco AS5800 when a trunk which has been configured for Primary NFAS is inserted back after OIR, the calls on the other cards, which are configured for NFAS of the same group, could fail, especially in the case of a TD/TV solution.
CSCdz54240	poor performance on MLP with h/w compression (single channel ISDN) Symptom: The transportation of files across a single BRI connection of an E1 line may result in poor performance. Conditions: This symptom is observed on a Cisco 3600 series router that is running Cisco IOS Release 12.2(02)XB7. Workaround: There is no workaround.
CSCdz56776	Outgoing PPP frames are stuck on MLPPP Symptom: If Multilink PPP call(MLPPP) is disconnected by cause except Normal call clearing, no frames are sent out on subsequent calls and the output queue may be stuck. Conditions: The symptoms occur under the following conditions: •You are running Cisco IOS Release 12.2 and Cisco IOS Release 12.2 T •MLPPP is enabled on ISDN interface (BRI and PRI). •Dialer profile and multiple dialer interfaces belonging to the same dialer pool number are configured. Workaround: Use the no fair-queue command on physical interfaces.
CSCdz61141	MPPE fails with RADIUS Symptom: Microsoft Point-to-Point Encryption (MPPE) does not work when RADIUS is used for authentication and authorization. The user is able to authenticate and MPPE is negotiated, but traffic will not pass through unless MPPE is disabled or local authentication is used. Conditions: This symptom occurs when MPPE is used with RADIUS to perform authentication and authorization. Workaround: There is no workaround.
CSCdz61543	Remove 64K rejection for 1AESS Symptom: Calls coming in on 1AESS trunks get rejected by the Cisco AS5x00 access servers. Conditions: Incoming calls on 1AESS trunk lines will fail to connect. Trunks coming from other switch types will not be effected by this bug. Workaround: There is no workaround.
CSCdz70933	Filter-Id from preauthentication not applied with auth-required=0 Symptom: When the Filter-Id attribute is provided during preauthentication, it is accepted, but not applied to the virtual access interface. When the same attribute is provided during PPP authentication, it is applied OK. Workaround: There is no workaround.
CSCdz71219	Input-queue wedge intermittently Symptom: Intermittent problem on Virtual-Access interfaces. The input-queue becomes wedge, for example: `input queue 11/10` Increasing the input-queue size does not help. Workaround: There is no workaround.
CSCdz72678	mgcp-nas-pkg calls generate zero values for RADIUS acct attributes Symptom: Media Gateway Control Protocol (MGCP) network access server (NAS) package calls may cause the following RADIUS accounting attributes to contain zero values: •Acct-Input-Octets •Acct-Output-Octets •Acct-Input-Packets •Acct-Output-Packets •Data-Rate •Ascend-Xmit-Rate •Presession-Packets-Input •Presession-Packets-Output •Presession-Octets-In •Presession-Octets-Out Conditions: This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(2)XB8 or Cisco IOS Release 12.2 T. Workaround: There is no workaround.
CSCdz88409	Router crashed during weak RADIUS service Symptom: Cisco C5800 Router running Cisco IOS Release 12.2(2)XB10 crashed during a period of weak RADIUS service that provocated high session flapping. Workaround: There is no workaround.
CSCdz89543	Missing accounting stop record with LSDO and Multilink PPP Symptom: In a Large-Scale Dial-Out (LSDO) setup in which the called site (remote site) is configured to add additional member links to the Multilink PPP (MLP) connection, the initial call to the remote site via LSDO may not trigger an accounting stop record when the call terminates. Conditions: This symptom is observed when the customer premises equipment (CPE) adds additional links to the multilink bundle that is built by the initial LSDO call. If there is only one LSDO call or if all member links are initiated by the remote site (LSDO is not used), stop accounting records are correctly generated for all member links. Workaround: There is no workaround.
CSCdz89669	AAA Accounting not sent for multilink isdn calls, when MSCB confd Symptom: When an ISDN dial-in client negotiates callback and multilink, and the callback is not configured for that user, the authentication, authorization, and accounting (AAA) records may not be sent. Conditions: This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2 T. Workaround: There is no workaround.
CSCea02355	rare ip packets may cause input queue wedge Cisco routers and switches running Cisco IOS software and configured to process Internet Protocol version 4 (IPv4) packets are vulnerable to a Denial of Service (DoS) attack. A rare sequence of crafted IPv4 packets sent directly to the device may cause the input interface to stop processing traffic once the input queue is full. No authentication is required to process the inbound packet. Processing of IPv4 packets is enabled by default. Devices running only IP version 6 (IPv6) are not affected. A workaround is available. Cisco has made software available, free of charge, to correct the problem. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml
CSCea04377	calltracker data leaks to the console when quiet option is set Symptom: When Calltracker call-record terse or verbose configured with "quiet" option, the Calltracker data leaks to the console. Specially with logging console and Calltracker call-record verbose quiet configured, the CPU utilization jumped up from ~10% to ~99%. Conditions: Calltracker call-record terse or verbose configured with "quiet" option. Workaround: Disable the logging console and the CPU utilization would dropped down to normal range. Also with image build from release which has CSCdy81947 integrated and provides support for [no] logging queue-limit [qsize] CLI, we can use this CLI to increase the queue-limit from default value of 100 to 1000 and we will not see this issue. This DDTS is still not available on Cisco IOS Release 12.2(2).XB images.
CSCea12136	AS5850: Silent packet drops from GigabitEthernet to Virtual-access Symptom: Some dial in users connecting to a Cisco AS5850 are unable to reach external destinations. The packets are sent, but the return packets entering the GigabitEthernet egress interfaces are silently dropped on the Cisco AS5850. Those drops are neither reported with show cef drop nor do any of the interface drop counters increase. The incoming packet counter on the GigE as well as the outgoing packet counter on the vaccess increase as packets arrive, but they do not arrive at the user. All CEF/FIB and adjacency entries look normal. This problem is seen only for some active sessions, other sessions are working normally. Multilink sessions (even with a single channel only) have not been reported failing. Conditions: This problem is only seen on a Cisco AS5850 running Cisco IOS Release 12.2(2)XB10. The problem is not seen on a Cisco AS5800 running the same software release. Workaround: The user must disconnect and reconnect to restore connectivity.
CSCea12966	function aaa_attr_list_ptr_copy_to_req does not support merged lists Symptom: Function aaa_attr_list_ptr_copy_to_req incorrectly strips off any additional attribute lists connected to the list passed in. This causes attributes lists to be lost, resulting in missing attributes being sent to AAA Servers. Workaround: There is no workaround.
CSCea14392	Need to commit NextPort Module Code 3.2.22.18 Request to commit new module code to bundle in Cisco IOS releases for the NextPort based Cisco AS5350/AS5400/AS5850 platforms. This module code 3.2.22.18 addresses the following issues for customers: •CSCdy55561 2 Modems marked BAD after V.110 CSM parameter failure •CSCdx71846 3 g.726 interop w/non-Cisco GW shows misordered 4 bit samples in Pload •CSCdx69453 3 Voice and Fax-Relay info field size range from 0 is invalid
CSCea19087	CALLTRKR-6-CALL_RECORD not displayed for a modem-pool call with CAS Symptom: A Cisco AS5300 may not display some Calltracker information for a modem call. Conditions: This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(2)XB10 or Cisco IOS Release 12.2(13)T and is configured for channel-associated signaling (CAS) with modem pooling. This is observed, in particular, when the call is routed to a configured modem pool instead of to the default modem pool. The Calltracker messages look like the following messages: `CALLTRKR-6-CALL_RECORD` and `CALLRECORD-3-MICA_TERSE_CALL_REC` However, when the symptom occurs, the first message is omitted. Workaround: Configure the Cisco AS5300 for ISDN (PRI) instead for CAS. First Alternate Workaround: Do not configure modem pooling. Second Alternate Workaround: Ensure that the call is routed to the default modem pool.
CSCea23484	VPDN rejecting 127.0.0.x address as source-ip Symptom: IP addresses of the "127.0.0.x" type may be rejected by a virtual private dial-up network (VPDN) to be used as the source IP address for VPDN tunnels. Conditions: This symptom is observed on a Cisco AS5400 or Cisco AS5800. Workaround: There is no workaround.
CSCea24574	VSA not processed if sent with tagged tunnel attributes Symptom: AAA may not process VSA if sent with tagged L2TP tunnel attributes. Conditions: This symptom is observed on a Cisco AS5400 or Cisco AS5800. Workaround: There is no workaround.
CSCea28396	AS5300 reloads while sending aaa accounting request Symptom: A router may reload when sending an authentication, authorization, and accounting (AAA) request to a TACACS+ server. Conditions: This symptom is observed on a Cisco AS5300 universal access server that is running Cisco IOS Release 12.2XB(10) and Cisco IOS Release 12.2 T. Workaround: There is no workaround.
CSCea28958	Function to manipulate attribute lists does not merge correctly Symptom: While copying an AAA attribute list into an event, the copy function strips off any additional attribute lists connected to the list passed in. This causes attributes lists to be lost, resulting in missing attributes being sent to AAA Servers. Workaround: There is no workaround.
CSCea41989	AS5400/AS5350 - ANI/DNIS Delimiter (sig-class) CAS for CT1 is broken Symptom: A user-configured signaling class template may not be not used during incoming and outgoing channel-associated signaling (CAS) calls. Instead, the default signaling template is used. Conditions: This symptom is observed in Cisco IOS Release 12.2 and Cisco IOS Release 12.2 T on a Cisco AS5350 and a Cisco AS5400. Workaround: There is no workaround.
CSCea45343	Not able to manually shutdown modem/spe in BAD state Symptom: When a modem in bad state is shutdown, the show modem command reports the state as BAD and not as SHUT. Further Problem Description: The states of busy out and shut were clubbed together as 'b'. The two were segregated as part of DDTS CSCdr31105. If a modem in bad state is shut down, the show modem command shows the state as 'B' and not as 'S'. But if a modem is shut down, it really doesn't matter what state the modem is in. So the state should be shown as 'S'. Workaround: There is no workaround.
CSCea49108	MICA Boardware does not recover after crash Symptom: If boardware crashes in some scenarios, Cisco IOS does not know and therefore cannot recover. Impact: Failed calls into that carrier card (up to 120 modems impacted). Workaround: Use the copy flash modem command with the file: system:/ucode/mica_board_firmware
CSCea52804	bus error at auth_tx_failure Symptom: A Cisco AS5350/AS5400 running Cisco IOS Release 12.2(2)XB7 crashes with bus error at auth_tx_failure. Workaround: There is no workaround.
CSCea53600	authorization failure for terminal login call with per-user DNS/WINS Symptom: Issue with terminal server login where a RADIUS assigned DNS or WINS server (i.e., per-user dns/wins) causes authorization to fail. Workaround: There is no workaround.
CSCea61814	bearer capability changed for outgoing hairpinned call Symptom: The bearer capability is changed for outgoing hairpinned call. Workaround: There is no workaround.
CSCea66630	COT_TP_IN test fail resulting channels in maintenence pending Symptom: The first COT_TP_IN test failed right after reload and the Cisco AS5300 never received COT_TP_OUT from Softswitch, putting the channel in maintenance pending state. The timer in COT_TP_IN test should bring the channel to idle even if it does not receive the COT_TP_OUT from Softswitch. Workaround: There is no workaround.
CSCea79604	buffer size mismatch between MICA boardware and Cisco IOS Symptom: The buffer size used by Cisco IOS to send data to the MICA carrier card is larger than the maximum buffer size defined by the carrier card software. If Cisco IOS sends a buffer which exceeds the maximum size set by the carrier card, the carrier card software may crash. If this software crashes, communication with all modems on the board will be lost. Conditions: This mismatch in buffer size affects all images starting with 12.2M and 12.2 T. Workaround: The router must be reloaded.
CSCin03921	The 872uut crashes inconsistently during cbwfq tests Symptom: Adding or removing a service policy to a dialer interface may infrequently cause a spontaneous reload of the router. Workaround: There is no workaround. However relying on experience with similar issues (involving reconfiguring a dialer on the fly), the suggestion is that either or both of the following steps might help: •Stop generating traffic through the interface •Shutdown the dialer interface when changing the service policy

Open Caveats—Cisco IOS Release 12.2(2)XB10

There are no open caveats specific to Cisco IOS Release 12.2(2)XB10 that require documentation in the release notes.

Resolved Caveats—Cisco IOS Release 12.2(2)XB10

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB10. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 10 Resolved Caveats for Cisco IOS Release 12.2(2)XB10
DDTS ID Number	Description
CSCdt64681	EIGRP route stuck in RT after neighbor down over ISDN: Symptom: Cisco 7200 running Cisco IOS Release 12.1(6) with PRI and multiple dialer interfaces. Two dialer neighbors advertise a prefix which is stuck in topology table/routing table once the neighbors are down. Workaround: Clearing the route makes it come back.
CSCdu26701	Compression & CEF on same int should not be allowed: Symptom: If you configure compress mppc on an interface and configure ip cef globally, IP fast switching is disabled. This affects connections that are not configured for compression to be process switched just like the compression connections, which adversely affects performance. If you disable compression, enable fast-switching, and re-enable compression, the interface incorrectly allows fast-switching simultaneously with compression. Workaround: Do not configure compression on interfaces you wish to have fast-switched.
CSCdv00338	Calls not disconnected (show isdn active) when idle time expires: all Symptom: ISDN calls on NFAS signaled E1/T1 which arrive on B-channel 16 (for E1) or 24 (for T1) are not purged from the call-history MIB shown by show isdn active upon disconnect but are still shown as active. This can cause the ISDN process to consume more and more memory and CPU load in order to maintain the growing list. Workaround: Deactivate call-history-mib using the commands: call-history-mib max-size 0 call-history-mib retain-timer 0
CSCdx62491	CISCO-AAA-SESSION-MIB casnActiveTable: getnext returns wrong OID: Symptom: The getnext command returns the wrong OID when retrieving an object from the casnActiveTable of the CISCO-AAA-SESSION-MIB and no instance is given. `> getnext -v2c 10.89.152.43 public casnUserId` `casnTotalSessions.0 = 2` `> getnext -v2c 10.89.152.43 public casnUserId.0` `casnUserId.1 =` `> getnext -v2c 10.89.152.43 public casnUserId.1` `casnUserId.2 = cisco` Conditions: This problem only occurs when no instance is given in the getnext request. Workaround: There is no workaround.
CSCdx86284	Resend OOS service message after RESTART: Symptom: If an ISDN B channel has been set out of service (via the D channel interface command isdn service), and if the router should subsequently receive from the switch a RESTART message for that channel, then the router will think that the channel is still OOS, while the switch thinks that it is not OOS any more. The result will be that the switch may offer a call to the router on that channel, which call will be rejected by the router with "Requested circuit/channel not available". Instead, after receiving the RESTART message for an OOS channel, the router should refrain from acknowledging RESTART, but instead should reissue the SERVICE message, to restore the channel to the out-of-service state. Workaround: There is no workaround.
CSCdx90988	Memory leak in ISDN: Symptom: A leak with the ISDN process may be observed on a router after about three days. The router reloads because of a lack of memory resources after about 14 days. Conditions: This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(10). Workaround: Reboot the router at a time when there is low traffic.
CSCdy34494	NAS-Identifier value isnt correct in attribute_32 test.: Symptom: The NAS-Identifier value is not correct because the value can only take 33 characters. Workaround: There is no workaround.
CSCdy48813	Outgoing call failed due to dialer DNS reverse-lookup failed: Symptom: For dialout, the outgoing call fails due to DNS reverse-lookup when dialer DNS is used on the dialer interface. The problem didn't appear in Cisco IOS Release 12.2(2)XB5. Workaround: There is no workaround.
CSCdy63815	OLD-CISCO-TS-MIB tsLineUser empty with AAA RADIUS and local user: Symptom: OLD-CISCO-TS-MIB tsLineUser is empty in Cisco IOS Release 12.2(2)XB6 with AAA RADIUS and local user configuration. The same configuration works with Cisco IOS Release 12.1(5)T8, and the tsLineUser value is populated. Workaround: There is no workaround.
CSCdy68133	Async Call fails to come up when no preauth is configured: Symptom: Modems calls will be rejected with no resource available. Conditions: This only happens if preauthorization is not configured. Workaround: Configure preauthorization for incoming calls. This may not be possible in all networks.
CSCdy85971	wrong SDP in 200 ok reply to a re-invite to conference: Conditions: This problem happens every time a mid-call INVITE is received to revert from a negotiated DTMF-rely payload type to Inband Voice. Symptom: In response to the mid-call INVITE, part of the old negotiated payload type is advertised in the 200 ok. The SDP looks as follows (Note the missing encoding name) : `a=rtpmap:96 /8000 a=fmtp:96 0-15` Workaround: There is no workaround.
CSCdz12110	ANI configured is not followed for E1-R2 outgoing call: Symptom: For an outgoing call, Cisco AS5400 running 12.2(12a) may send the same DNIS and ANI to PSTN switch without following the ANI configured under cas-custom under controllers
CSCdz12711	NAS timedout user reported with incorrect prog. /discon. code: Symptom: Incorrect progress / disconnect code is reported for a user timing out by NAS with no RADIUS response. Workaround: There is no workaround.
CSCdz19909	RADIUS interim-update records not being sent correctly: Symptom: The customer is using Cisco 7206VXR. The RADIUS interim-update records have been enabled with the following global command: `aaa accounting update periodic 1440` The DSL router is supposed to send an update record for every active session every 24 hours but is producing inconsistent results instead. For many sessions that are active for more than a day, no update records are ever sent. For sessions where update records are sent, the time interval between updates is inconsistent. Workaround: There is no workaround.
CSCdz19944	MGCP T38 inhibit does not suppress T38 capability: Symptom: On Cisco AS5400 with Cisco IOS Release 12.2(12.14)T or Cisco IOS Release 12.2(2)XB8, disabling T.38 through mgcp fax t38 inhibit and/or fax t38 inhibit under voice service voip does not suppress the gateway's advertisement of T.38 as a capability. Workaround: There is no workaround.
CSCdz24736	Multilink PPP reporting master channel with a progress code 65: Symptom: Multilink PPP should report the master channel with a RADIUS accounting progress code of 60. Workaround: There is no workaround.
CSCdz45885	AAA POD not disconnecting client requests with 8-byte session id: Symptom: AAA POD is not disconnecting client requests with 8-byte session id.
CSCin23107	Possible memory leaks during async callback: Symptom: On Cisco AS5400 universal access servers running Cisco IOS Release 12.2(2)XB8 or 12.2(12.14)T, memory leaks associated with async callback are possible. Workaround: There is no workaround.

Open Caveats—Cisco IOS Release 12.2(2)XB9

Cisco IOS Release 12.2(2)XB9 is not distributed for widespread availability.

Resolved Caveats—Cisco IOS Release 12.2(2)XB9

Cisco IOS Release 12.2(2)XB9 is not distributed for widespread availability.

Open Caveats—Cisco IOS Release 12.2(2)XB8

This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB8 and describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 11 Open Caveats for Cisco IOS Release 12.2(2)XB8
DDTS ID Number	Description
CSCds37794	Symptom: System may reload due to memory corruption when having traffic. Conditions: when TCP header compression and predictor compression are enabled. Tearing down calls from the caller side. Workaround: There is no workaround.
CSCdx05186	Symptom:- After about 30+ hours of stress testing, Cisco AS5800 and Cisco AS5850 gateways start rejecting calls and "%CSM-1-NO_CSM_CALL_INFO: NO call control block" traceback is seen. Conditions: This defect was seen on Cisco AS5850 and Cisco AS5800 gateways during stress testing. The Cisco AS5850 was handling about 500 sustained calls being placed at about 5cps. This problem is seen after about 30+ hours of stress testing. The trace backs are seen as the calls are being rejected. At this stage the system will be unable to sustain more than 50(approximately) calls. This is seen on systems handling SS7 calls and configured to get tunnel information from RPMS. Workaround: The only workaround is to reload the box. It has been seen that the box starts functioning at its capacity after reload.
CSCdx29945	Cisco AS5800 access server running Cisco IOS Release 12.2(2)XB5 can reload due to corrupted Program Counter at DEADBEEF under workload/stress.
CSCdx33071	V120 Calls fail when VPDN is enabled for DNIS screening. This might be service impacting. Workaround: There is no workaround.
CSCdx37301	Symptom: On reloading Cisco AS5850 access server route-switch controller (RSC), the universal port feature card (UP324) may unexpectedly crash. Conditions: Reload the Cisco AS5850 RSC. Workaround: There is no known workaround to this problem at this time.
CSCdx52766	In a multilink multichassis scenario, if there exists a route among the SGBP dial-in NASes that goes through a dial-in MLPPP client and back to a NAS, either through a dial-out NAS, a direct LAN, or other connection, we may hit a race condition leading to a stack overflow and subsequent software forced crash. A workaround is to ensure that such routes are not present.
CSCdz00534	Symptom: Cisco IOS Release 12.2.2XB7+ L2TP is incorrectly indicating "service up" to Calltracker with a service type of PPP. Conditions: This behavior happens for L2TP calls. Workaround: There is no workaround.

Resolved Caveats—Cisco IOS Release 12.2(2)XB8

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB8. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 12 Resolved Caveats for Cisco IOS Release 12.2(2)XB8
DDTS ID Number	Description
CSCdw59775	Symptom: After the aaa accounting send stop-record authentication failure global configuration command is configured, a successful PPP call may generate two stop records. Conditions: This symptom is observed on a Cisco AS5850 gateway that is running Cisco IOS Release 12.2(2)XB if Link Control Protocol (LCP) renegotiates after the authenticating phase has started. Workaround: There is no workaround.
CSCdw93992	A Cisco Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC) may fail to send accounting records for a PPP over ATM (PPPoA) call after the call has been forwarded via L2TP to an L2TP network server (LNS). The LNS drops the call by sending a Call Disconnect Notification (CDN) message to the LAC. Workaround: Clear the virtual access interface for the call on the LAC.
CSCdx07849	An attempt to update the startup-config file (by using the EXEC write memory command or equivalent) may fail with the following error: `router#write memory` `startup-config file open failed (Device or resource busy)` This problem can be caused by a process that is attempting to update NVRAM getting stuck for some reason. To track down the offending process, use the command show file descriptors: `router#show file descriptors` `File Descriptors:` `FD Position Open PID Path` `0 0 430A 157 nvram:` Now, using the show process command, find the process with the offending PID. If the PID belongs to a process called radius nvwrite, then this DDTS is the problem. Workaround: Save the current running config to a temporary file in flash or on a TFTP server. Reload. Immediately after reloading, copy the saved configuration to nvram:startup-config.
CSCdx47143	Symptom: Some E1 controller ports may remain down after a router is booted up. Conditions: This symptom is observed on a Cisco AS5800 access concentrator that is running Cisco IOS Release 12.2(2)XB5. Workaround: Enter the shutdown interface command followed by the no shutdown interface configuration command on the E1 controller that has paused indefinitely in the down state.
CSCdy00247	Symptom: The modemcap AT command string may be in the input buffer of a line when the line comes up. As a result, this string -—rather than actual user data received from the client modem-— may be used for character mode authentication. Conditions: This symptom is observed on a Cisco AS5800 that has autoconfiguration enabled on the modem lines. Workaround 1: Enter the flush-at-activation command. Workaround 2: Be sure that the modemcap entry configured on the line involves sending an AT command no longer than 58 characters.
CSCdy06029	When using MS-Callback with Cisco IOS Release 12.2(2)XB6 and the 'callback-noverify' option, the NAS fails to apply Framed-IP-Address or any AV-Pairs associated with that user.
CSCdy09417	Symptom: The output from the show process memory EXEC command indicates that the amount of memory held by the "PPP Events" process continues to increase. This indicates a memory leak. Conditions: This symptom is observed on a Cisco AS5850. User profiles that have a Link Control Protocol (LCP) attribute that is applied to an interface, For example, Timeout or Idle-Timeout, cause a leak of per-user request structures. Workaround: Use virtual profiles.
CSCdy21198	NAS is running almost 700 calls, a mixture of Analog, SYNC PPP, and multilink calls. After about 14-16 hours of stress testing, The NAS reloads @ muti_session_add_link.
CSCdy22040	Dead Virtual-Access interfaces might be seen on Cisco AS5800 under stress. This can be service impacting over a period of time as NAS will eventually run out of Virtual-Access interfaces.
CSCdy31636	Symptom: On a Cisco AS5850 Access server, upstream (ingress to egress) traffic through a single link async MLP call gets process switched instead of CEF switched. Can lead to higher CPU utilization on the RSC when forwarding MLP data. Data integrity is not affected. Conditions: Problems exists only on Cisco IOS special release version 12.2(2)XB6C. Only async single link MLP calls are affected. All digital calls, all non-MLP calls and all MLP calls with more than one link are NOT affected. Workaround: There is no workaround.
CSCdy35836	Symptom: On a Cisco AS5800 platform during long duration test, it is found that a Cisco AS5800 hits "No more SWIDB allowed" issue and calls fails. Workaround: There is no workaround.
CSCdy39663	Symptom: A Cisco AS5800 router crashed with outb-telnet_aaa_acct_get_dynamic_attrs routine. This crash looks like regression caused by CSCdx87139. If a router running IOS version which has fix for CSCdx87139, it can get crashed by this bug. Workaround: There is no workaround.
CSCdy50103	Symptom: Attributes 42 or/and 43 might carry negative values with the aaa accounting exec default none IOS command configured on the NAS. This frequency of occurrence of this bug is the range of one Accounting record out of ten. Workaround: There is no workaround.
CSCdy51116	Symptom: In Cisco IOS Release 12.2(12.5)T or later, a router which does not have AAA configured may unexpectedly reload when a user attempts to telnet from the router to another device. Workaround: Enable AAA.
CSCdy52842	Symptom: Failed MLP calls can cause phantom Virtual-access interface issues. Workaround: Use 'ppp timeout ncp x' but would like to see if we still have any side effect of this issue since some of these interface do get recycled if a call is received from the same user again.
CSCdy54989	Symptom: When the FIB is disable on a line card, all the packets that send to this line card will be queued up. All of this can be seen using the show cef line card command. Workaround: clear cef linecard <slot#>. If this does not help, apply OIR procedure to the particular line card.
CSCdy69192	Symptom: Cisco AS5300 server encounters system crash when RADIUS authentication is used for authenticating asynchronous call. Workaround is to use Local or TACACS+ authentication.
CSCdy71629	Symptom: The task_id attribute in AAA accounting record might be wrong if the task_id is greater then 9999. Workaround: There is no workaround.
CSCdy71923	Symptom: System reload when sending downstream traffic. Conditions: During stress test which has MLPPP call configuration and downstream traffic. Workaround: There is no workaround.

Open Caveats—Cisco IOS Release 12.2(2)XB7

This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB7 and describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 13 Open Caveats for Cisco IOS Release 12.2(2)XB7
DDTS ID Number	Description
CSCdy14689	In Cisco IOS Release 12.2(2)XB, Cisco IOS Release 12.2(4)T, and later Cisco IOS codes, the router does not send RADIUS connection accounting attribute 46 for TCP clear calls or for any outbound telnet connections from the router. The is issue is only with Telnet connections. Regular PPP calls accounting records do contain this attribute. Workaround: There is no workaround.
CSCuk34949	A Cisco router may generate a large number of alignment errors when TCP Header Compression is configured in conjunction with L2TP and Multilink PPP. Workaround: Disable header compression, both in the local configuration (use the interface command no ip rtp header-compression) and in any RADIUS/AAA database.
CSCdx47149	When we re-use the same 8 port number to configure 24 RLM groups per 5850-RSC (48 RLM groups per Cisco AS5850 chassis), only 8 RLM groups per RSC are ACTIVE at a time. Since we use 3 Loopback interfaces per RSC to divide each RSC into 3 virtual NASes (Extnode), we should be able to re-use the same 8-port number (3000-3016) for each virtual NAS and bring up all 24 RLM groups per RSC (48 RLM groups per Cisco AS5850 chassis).

Resolved Caveats—Cisco IOS Release 12.2(2)XB7

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB7. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 14 Resolved Caveats for Cisco IOS Release 12.2(2)XB7
DDTS ID Number	Description
CSCdk31736	PPP authentication requests with no username are not forwarded to the TACACS+/RADIUS server. This may prevent you from authenticating people by Caller ID.
CSCdv21918	A router may reload if netflow-data is exported to a multicast address. Workaround: Do not configure a multicast address; use a unicast address instead.
CSCdv27734	New PPP configuration commands are provided which provide control over the negotiation and application of the LCP configuration options for HDLC Address and Control Field Compression (ACFC) and PPP Protocol Field Compression (PFC).
CSCdw00055	The non-variable-length dial-plan matching character `$' permits a user to force a match on a destination-pattern consisting of a fixed number of digits. For example, use the following configuration: `!` `dial-peer voice 1 voip` `destination-pattern 01152....$` `session target ipv4:IP_ADDR_RTR1` `ip precedence 5` `!` `dial-peer voice 2 voip` `destination-pattern 01152......` `session target ipv4:IP_ADDR_RTR2` `ip precedence 5` `!` The user in this situation has calls to phone numbers which share the same first set of prefix digits but whose complete set of digits are different in number. In the example above, calls to RTR1 have nine digits starting with `01152' while calls to RTR2 have 11 digits starting with `01152'. To eliminate the ambiguity as to which dial-peer to match, the `$' is used so that a call to RTR2 will not match on dial-peer 1. This configuration works in Cisco IOS Release 12.1 images which support the `$' dial-peer matching character and Cisco IOS Release 12.2(1a). Starting in Cisco IOS Release 12.2(1.1) and in Cisco IOS Release 12.2(2)T, the dial-plan no longer permits a destination-pattern terminated with the `$' character to be matched at all, and hence no calls using that dial-peer will complete. Workaround: Configure the destination-patterns which end in `$' to end in `T?$': `!` `dial-peer voice 1 voip` `destination-pattern 01152....T?$` `session target ipv4:IP_ADDR_RTR1` `ip precedence 5` `!` `dial-peer voice 2 voip` `destination-pattern 01152......` `session target ipv4:IP_ADDR_RTR2` `ip precedence 5` `!`
CSCdw93050	The problem is transparent to the customer and is involved with the IOS MLP/PPP architecture.
CSCdx15859	Calltracker, show call calltracker active, and ... history commands display extraneous comma after authentication time.
CSCdx33166	During LSDOCallback, the sessions on the server side go down due to which callback already exists debugs can be seen in the logs inhibiting callback from occurring. Workaround: There is no workaround.
CSCdx41454	Symptom: Router applies the ip tacacs source-interface configuration only to the first tacacs server in the server list and fails to use the IP address for other configured servers. Conditions: When the primary TACACS server is not available, the router will attempt for the next TACACS server in the list. While connecting to the secondary TACACS server, the router ignores the IP tacacs source-interface configuration and it uses the IP address of the outgoing interface. The router is expected to use the IP address configured through ip tacacs source-interface command as source address, while connecting to the TACACS server, including the secondaries. Workaround: A workaround is possible using NAT. The user can apply NAT for the TACACS packets by the following configuration. `interface outbound interface to the tacacs server` `ip nat outside` `!` `ip nat inside source list 102 interface Loopback0 overload` `access-list 102 permit tcp any any eq tacacs`
CSCdx81130	Microsoft Callback negotiation may fail with particular clients. This is due to a minor difference between Cisco's implementation of the Microsoft Callback server and the original implementation by Microsoft in a detail that is not clearly specified in the draft RFC. While this particular problem does not seem to impact Microsoft Windows clients requesting for callback, it has been observed with a 3Com OfficeConnect LAN modem that failed to negotiate MS callback with a Cisco NAS. Workaround: There is no workaround.
CSCdx93324	The H.323 gateway may crash accessing invalid memory location. Workaround: There is no workaround.
CSCdy01787	When MTU configuration is manually overridden the EAP proxy client may not be able to appropriately size frames for the client's MRU. Workaround: Do not adjust the MTU on the router.
CSCdy05296	The port information provided on a Cisco AS5350 universal access server, Cisco AS5400 universal access server, or Cisco AS5850 universal access server on modems within RADIUS attribute 5 using either nas-port format a or b for async calls provide the true port information (as in slot/port) and not the TTY line number of the modem which previous generation dial platforms provided. This is causing problems for service providers using a variety of Cisco dial platforms as they are inconsistent in the information being relayed on the various platforms Cisco sells. Workaround: There is no workaround.
CSCuk36415	Symptom: RTP packets queued from the fast switching path will be sent uncompressed. Workaround: There is no workaround.
CSCdx72554	SPE recovery initiated when voice calls fail. Workaround: There is no workaround.

Open Caveats—Cisco IOS Release 12.2(2)XB6

This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB6 and describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 15 Open Caveats for Cisco IOS Release 12.2(2)XB6
DDTS ID Number	Description
CSCdx05186	%CSM-1-NO_CSM_CALL_INFO and traceback while teardown calls Symptom: After about 30+ hours of stress testing Cisco AS5800 and Cisco AS5850 start rejecting calls and "%CSM-1-NO_CSM_CALL_INFO: NO call control block" traceback is seen. Conditions: This defect was seen on Cisco AS5850 and Cisco AS5800 during stress testing. The Cisco AS5850 was handling about 500 sustained calls being placed at about 5cps. This problem is seen after about 30+ hours of stress testing. The trace backs are seen as the calls are being rejected. At this stage the system will be unable to sustain more than 50(approximately) calls. This is seen on systems handling SS7 calls and configured to get tunnel information from RPMS. Workaround: The only know workaround at this stage is to reload the box. It has been seen that the box starts functioning at its capacity after reload.
CSCdx52766	crash due to memory corruption In a multilink, multichassis scenario, if there exists a route among the SGBP dial-in NASes that goes through a dial-in MLPPP client and back to a NAS, either through a dial-out NAS, a direct LAN, or other connection, we may hit a race condition leading to a stack overflow and subsequent software forced crash. Workaround: Ensure that such routes are not present.
CSCdx60767	Unexpected packet forwarding thru MCMLP L2TP tunnel In case of an MCMLP call, twice the number of user data packets will be transmitted back and forth over the L2TP tunnel virtual-access interface. However the virtual-access interface of the multilink bundle will show the correct number of packets that were expected to be transmitted in both input and output directions. Apparently, the defect is not service impacting.

Resolved Caveats—Cisco IOS Release 12.2(2)XB6

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB6. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 16 Resolved Caveats for Cisco IOS Release 12.2(2)XB6
DDTS ID Number	Description
CSCdx07849	radius_saveident should use CSCdw51651 method to avoid write_memory An attempt to update the startup-config file (via the EXEC write memory command or equivalent) may fail with the following error: router#write memory startup-config file open failed (Device or resource busy) This problem can be caused by a process that is attempting to update NVRAM getting stuck for some reason. To track down the offending process, use the command show file descriptors: router#show file descriptors File Descriptors: FD Position Open PID Path 0 0 430A 157 nvram: Now, using show process, find the process with the offending PID. If the PID belongs to a process called radius nvwrite, then this DDTS is the problem. Workaround: Save the current running config to a temporary file in flash or on a TFTP server. Reload. Immediately after reloading, copy the saved configuration to nvram:startup-config.
CSCdx47143	Some E1 contrlrs remain down after bootup; Come up after shut/noshut Some e1 controller ports will remain down after bootup of Cisco IOS Release 12.2(2)XB5. A workaround is to shut/no shut the e1 controller that is stuck in down state. Consequently, the controller will come up.
CSCdx81388	Memory leak in PPP Events after stress test Memory Leak is seen in PPP Events after stress test on Cisco AS5400 running Cisco IOS Release 12.2(02)XB6. Workaround: There is no workaround.
CSCdw03288	UP324 card crash while handing over in handover-split mode Symptom: While handing over UP324 board from one RSC to another using the redundancy hand-over mode and reloading the RSC which was handling the UP324, the CPU utilization of the UP324 goes up to 100% and the board crashes when its handed to the other RSC. Conditions: This affects platforms which have redundancy hand-over mode support. Workaround: There is no workaround.

Open Caveats—Cisco IOS Release 12.2(2)XB5

All the caveats listed in this section are open in Cisco IOS Release 12.2(2)XB5. This section describes only severity 1 and 2 caveats and select severity 3 caveats

Table 17 Open Caveats for Cisco IOS Release 12.2(2)XB5
DDTS ID Number	Description
CSCdu79111	TCL APP processes take too much cpu when making +7cps debicard calls. Symptom: When system running debitcard application with bursty traffic of 15+ call per second back-to-back, IVR processes such as TCL APP take too much CPU causing a high overall CPU utilization. Workaround: Control incoming calls to avoid bursty traffic and turn on Call Admission Control to prevent catastrophic errors at high CPU utilization.
CSCdw73072	clear spe causes tracebacks at pm_spe_sm_shutdown Symptom: The clear spe command causes tracebacks. Workaround: There is no workaround.
CSCdw80521	RPM does not unbind dynamic template when call disconnects early If an access server is configured for resource-pooling with customer profile templates, a short, abnormal call may cause the next call on that modem/interface to bind to multiple profiles causing the configuration for the next call to be different than intended. Workaround: A workaround which works under some circumstances (but not all) is to make sure that each customer profile template explicitly specifies every configuration item which may be different on other customer profile templates to make sure the configuration items on the intended template overrides any configuration items on other templates which may be unexpectedly bound. The workaround does not work when multiple short, abnormal calls land on the same port consecutively.
CSCdw81168	5850 not answering more than 256 ISDN calls This problem is seen when using RPMS (Version 1.1) in SS7 environment. On RPMS server resource groups with name "rg_ss7_rpms_digital" is created, to be used for digital calls, when SS7 is used. Number of resources under the resource group are greater than the available HDLC resources for the trunk card. When all the resources on the trunk card are used the next call, which is 256th digital call, fails to terminate as the Nextport resources are not used. Workaround: There is no workaround.
CSCdw82637	Call failure rate for MFC-R2 signaling on Cisco AS5850 is high The Cisco AS5850 gateway is used as one of thee gateway in Cisco SS7 interconnect solution using SC2200 as Media Gateway Controller. We have seen that around 20% of the MFC-R2 signaling terminated calls failed during a load run. The call scenario is as follows: `PTE/SIGGEN----->SC2200--Ni2--->5400---h323---->5850--E1-R2 trunk---->PTE` Whereas the Call Completing Rate for R2 originated calls are high close to 99.8%. PTE complained that the seizure signal initiated by the Cisco AS5850 gateway aborted. PTE is a bulk call generator capable of making ISDN, CAS-FGD, MFC_R2 bulk calls and it can co-work with Siggen which is SS7 signaling bulk call generator, and work as a SS7 bulk call generator. PTE was employed for MFC_R2 call generation and we don't have any previous data for MFC-R2 signaling. We don't have any other call generators capable of doing MFC-R2 signaling in order to compare the results.
CSCdw83849	APS-B-BPX: AnxB: Lockout doesnt keep selector position. Conditions: Force switch WS1->WS2 on AXSM/B, Lockout on BXM side. Workaround: There is no workaround.
CSCdw85276	SERVICE_SET_RUNNING_PARAM/0xF201 NAKs; result code 0x800D/0x800E In a Voice/Fax environment, occasionally, a NAK message is seen (received from the SPE/DSP) with hex command/result codes as 0xF201 & 800E, respectively. Side Effect: Digit Relay may not work as expected. Workaround: There is no workaround.
CSCdx00921	CT3 board reloads in vpn_fs_lc during stress Sometimes the CT3 linecard reloads at vpn_fs_lc. Workaround: There is no workaround.
CSCdx03069	Memory leak on GW if AltEP present in ACF with dCSA 0.0.0.0 Memory leak on the H323 voice gateways noticed. If the Gatekeeper of the Gateway sends an Admission Confirm (ACF) message with the destination Call Signal Address (dCSA) field set to 0.0.0.0 and if the alternate Endpoint field is present in the message. Workaround: There is no workaround.
CSCdx05612	nexport does not handle ungraceful OIR Symptom: The Cisco AS5850 access server route-switch controller (RSC) might reload ungracefully during normal operation. Conditions: This could happen if one of the feature boards goes through a series of ungraceful OIR's mainly due to a HW problem with that feature board. Workaround: There is no known workaround at this time.
CSCdx09443	Atlas card crashed after normal RSC reload Symptom: After a normal RSC reload, STM1 card reloaded during bootup. However, it came up after resetting. Conditions: This happened with c5850-p9-mz.Mar16 image. Workaround: There is no workaround.
CSCdx13190	Hearing Loud pitch (1Khz) Tone with e&m-fgb mf dnis. Workaround: There is no workaround.
CSCdx22133	Huge TACACS+ performance problem During high call rate, users might not be able to connect anymore due to a tacacs performance problem in IOS.
CSCdx26331	SIP: Connect Timestamp missing in CallHistory when ACK is missing. Symptom: The Call History information generated by the SIP call leg does not have a valid (non-zero) duration while the POTS Call History for the same call has a non-zero duration. Conditions: This will happen when the ACK fails to reach the TGW following an answer (200 OK response). Workaround: There is no workaround.
CSCdx30203	TCP-Clear call drop due to DSIP-3-GETPAK Symptom: About five days into the stress test with 1192 TCP-Clear calls, DSIP-3-GETPAK failure messages occurred and a large number of calls were dropped. This might be related to CSCdu69880. Conditions: This happens with Cisco IOS Release 12.2(2)XB5 4.7.0 image. Workaround: There is no workaround.
CSCdx34297	CPUHOG by process=PIM, and by process=IGMP with #users>2000 Following CPUHOG messages may be see on a Cisco AS5850 NAS running Cisco IOS Release 12.2(2)XB5 pre-fcs IOS if IP multicast is turned on with a call load of about 2000 ds0's. `Apr 16 12:56:35.851: %SYS-3-CPUHOG: Task ran for 2008 msec (8/0), process = PIM Process, PC = 601DA990. -Traceback= 601DA998 6057E260 601C1204 601C11F0`
CSCdx34297	CPUHOG by process=PIM, and by process=IGMP with #users>2000 Following CPUHOG messages may be see on a Cisco AS5850 NAS running Cisco IOS Release 12.2(2)XB5 pre-fcs IOS if IP multicast is turned on with a call load of about 2000 ds0's. Apr 16 12:56:35.851: %SYS-3-CPUHOG: Task ran for 2008 msec (8/0), process = PIM Process, PC = 601DA990. -Traceback= 601DA998 6057E260 601C1204 601C11F0
CSCdx34841	PRI-to-PRI hairpin calls fail Symptom: PRI-to-PRI hairpinning functionality is broken with Cisco IOS Release 12.2(2)XB5 on the Cisco AS5850 gateway. Workaround: There is no known workaround to this problem at this time.
CSCdx37301	UP324 feature board crash at tdm_raiko_s4_generic_init() Symptom: On reloading the Cisco AS5850 access server route-switch controller (RSC), the universal port feature card (UP324) may unexpectedly crash. Conditions: Reload the Cisco AS5850 RSC. Workaround: There is no known workaround to this problem at this time.
CSCdx41351	Analog calls are being process-switched With Cisco IOS Release 12.2(2)XB5 Cisco AS5850 IOS, analog calls will be process switched. No workaround is identified yet.
CSCdx49365	Modem VPDN calls with configured from RPMS 1.1 fails Issue: Analog VPDN calls fails when VPDN configuration is downloaded from RPMS 1.1 server for Cisco 5XXX Access Server. Workaround: Configure VPDN on AAA or Access Server.
CSCdx49620	Cisco AS5400 crashes with bus error in free function
CSCdx50282	SIP GW: Calling party name presented to PSTN has problems When a display-name is presented in a From header of a SIP INVITE to a IOS SIP gateway, the DISPLAY IE setting in the outgoing ISDN message may not be interoperable with dms-100 ISDN switch type.
CSCdx50498	Local RPM CLI commands for VPDN profiles stripped out at bootup Symptom: The resource pooling VPDN CLI commands in startup config is not recognized by 5400 when it boots up. Workaround: Workaround is to manually enter that in the configuration after bootup.

Resolved Caveats—Cisco IOS Release 12.2(2)XB5

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB5. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 18 Resolved Caveats for Cisco IOS Release 12.2(2)XB5
DDTS ID Number	Description
CSCdu14530	Symptom: If the IP address is removed from a the PPP interface of a 7500, running Cisco IOS Release 12.1E IOS, and then the IP address is added, this change is not reflected immediately in CEF. This results in 50% packet loss until the background CEF process updates the adjacency. The workarounds are: •shut / no shut the PPP interface. or •disable CEF (not an option as the 7500 is a PE router).
CSCdv38563	Symptom: Client code does not add attributes 90 & 91 for the LAC Network access server (NAS) may fail to include attributes 90 and 91 when a router hostname is used as the tunnel ID and when the tunnel ID is not included in the user profile. Workaround: There is no workaround.
CSCdv54127	Missing Acct-Output-Packets & Acct-Input-Packets in STOP rec Symptom: The Acct-Output-Packets and Acct-Input-Packets attributes are missing in the STOP record while testing network accounting, even though they are seen in the debug output.
CSCdv66747	Traceback at l2tp_fixup_cached_header Symptom: Tracebacks occur with vpdn in Cisco IOS Release 12.2(02)XB, Cisco IOS Release 12.2(03)PI, & Cisco IOS Release 12.2.T.
CSCdv71454	l2tp_process_unsent_queue may cause CPUHOG Symptom: In Cisco IOS Release 12.2 T, "L2TP mgmt daemon" may cause CPUHOG if there are lots of packets in unsentQ.
CSCdw00924	MLP bundle transmit may jam when link departs bundle Symptom: On a PPP multilink bundle that has multiple links, if one of the links departs from the bundle while data is enqueued for output at the bundle interface, the output mechanism on the bundle may stall, halting any further output from that bundle. The output queue on the bundle becomes full, causing packets that are forwarded to that bundle to be dropped and the affected bundle to stop transmitting packets. Workaround: There is no workaround.
CSCdw06038	RPM:no profile found for call-type digital Symptom: With Resource Pooling and Resource Pooling AAA accounting configured, a customer profile may not be found for a particular DNIS group. Conditions: The access server may have a problem with incoming calls finding the customer profile depending on the order, size and value of the dnis entered; results may vary depending on whether the DNIS is manually entered or whether the wavl is set up from reload via the start-up config. Workaround: There is no workaround.
CSCdw39083	Calls being disconnected by gateway with cause code 47(resource una) Symptom: When running test calls in a ThunderVoice environment a small percentage of the calls are being rejected by the originating gateway with cause code 47 (resource unavailable, unspecified). Workaround: There is no workaround.
CSCdw45584	Cisco-AV pair lcp:send-secret=cisco not supported in XB VPDN authorization fails when "lcp:send-secret=xxxx" is sent in the access accept packet from RADIUS.
CSCdw62064	IKE Keepalives being dropped with MLPPP fragmentation Symptom: On a Cisco 7200 running Cisco IOS Release 12.2.6, it is seen that with T1 links combined in a Multilink PPP bundle, and MLPPP fragmentation enabled; ISAKMP keepalives are not being received by the box, even though the remote peer is sending out the keepalive messages. As a result each end thinks its peer is dead and deletes the IKE & IPSEC SA's. They then re-negotiate IKE and IPSEC and create new SA's. As a result, IKE and IPSEC are re-negotiated at each IKE keepalive interval and there is some traffic drop during this re-negotiation phase. Workaround: •Disable hardware crypto acceleration. With software crypto, this problem is not seen. •Disable MLPPP fragmentation. Without fragmentation, the IKE keepalives are received by the peers (even with hardware crypto)
CSCdw68757	Caller hear second dial-tones CHOM noise from Nortel PBX. Symptom: Caller on original GW of CAS hear the second dial-tone CHOM from the far end router which connected to Nortel PBX. This is only for CAS case. Workaround: There is no workaround.
CSCdw71752	Spurious memory access@CC_CHAN_GetStatepri during hw-module reload Symptom: Traceback appeared after executing hw-module slot <> reload command. `Feb 12 12:14:59.907: %ALIGN-3-TRACE: -Traceback= 608D9AC8 608DA37C 60C6A344 60C675B0 608F0D10 608F11A4 608F1178 00000000 Feb 12 12:14:59.907: %ALIGN-3-TRACE: -Traceback= 608D9ACC 608DA37C 60C6A344 60C675B0 608F0D10 608F11A4 608F1178 00000000#` Workaround: There is no workaround.
CSCdw80687	ip tcp compression-header passive is always compressing ppp traffic Symptom: Packets are process switched on an interface with fast switching configured. This can result in high CPU usage. Conditions: Header-compression must be configured, but only on one side. For example, in a dial-in situation, where header-compression is configured on the central switch, but not on the box that is dialling in. Also, the interface must not support FAST switched header-compression, e.g. most dial-in interfaces are currently not supported. Workaround: Remove header-compression from the configuration. Note If header-compression is configured on both sides of a link, and the interface does not support fast-switched header-compression, then process switching is normal and required for successful operation of the header-compression feature.
CSCdw85178	OJ:VSA incorrectly billing ip hops Symptom: Genuity is not able to bill multiple customers off of one proxy. Workaround: There is no workaround.
CSCdw89455	PPP authen failure with fourth method Symptom: All PPP Auth methods will not work with MSCHAP V2.
CSCdw91279	L2TP ZLB ACK not processed correctly (regress CSCdk57040) Symptom: A Cisco router that is running Cisco IOS Release 12.2(5.7)T or a later release and that is acting as a Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC) or L2TP network server (LNS) may fail to process valid L2TP Zero-Length Body Acknowledgement (ZLB ACK) packets. This behavior may cause sessions and tunnels to drop. Workaround: There is no workaround.
CSCdx00805	Memory Leak on PPP Hooks Process with 0.3.0 image Symptom: When making modem calls, memory leak will happen on PPP Hooks process Conditions:It is very easy to reproduce, just make a trunk of modem calls, the memory leak will be seen couple of times of calls. Workaround: There is no workaround.
CSCdx02102	Memory corruption with MPPE when MTU exceeds 8K Symptom: A Cisco router may experience memory corruption when configured with software encryption (MPPE) if the MTU size is greater than 8K (and if there are actually packets of length greater than 8K). Workaround:Configure MTU to less than 8K when doing software encryption (MPPE).
CSCdx04328	Significant mem leak in MLP causing a crash during stress test Symptom: Memory leak in process "Pool Manager". Conditions: Occurs with MLP async calls when passing traffic from egrees to ingress. Workaround: There is no workaround.
CSCdx05704	MSCB won't propose the skip CB option to peer with dialer profiles Symptom: When a user dials in, requests MSCB and is bound to a dialer profile, after authentication (problem won't happen if the profile is bound before PPP starts) then IOS does not propose the option to skip callback during CBCP even if we are configured for it (ppp callback accept and user has empty callback dial string). If the user opts to skip the callback anyway, we will drop the call because we did not propose that option, which is correct behaviour but has only been enforced since CSCdu55093, which is why this bug has been relatively hidden up until recently.
CSCdx05908	crash @move_cursor_to_next_attr after enable resource stop-fail acct Symptom: After enable the aaa account resource stop-failure configuration on NAS, experience several crash during over night 8 call per second stress test. Workaround: Workaround is disable this configuration
CSCdx09410	Local RPM CLI commands for VPDN profiles stripped out at bootup Symptom: A CLI command in startup config is not recognized by the Cisco AS5800 when it boots up. Workaround: Workaround is to manually enter that in the config after bootup.
CSCdx09435	RSC crashes after ip pool d/l from radius Symptom: The RSC will ungracefully reload upon modem call setup. Conditions: This will occur if the async interface is configured for interactive mode, and if the RADIUS server is configured to download an ip address pool to the NAS. Workaround: Do not configure for ip address pool download from the RADIUS server.
CSCdx11607	Enable pre-auth breaks digital calls AAA Pre-auth causes digital calls to break, because resource allocation fails. Workaround: There is no workaround.
CSCdx22886	SGBP functionality broken Symptom: SGBP forwarding does not work if VPDN is disabled. Workaround: A temporary workaround for this problem is to enable VPDN (issue the command 'vpdn enable') and then disable it immediately (issue 'no vpdn enable') on all the SGBP stack group members. This allocates the resources required to do SGBP, and at the same time does not require VPDN to be kept enabled.
CSCdx23473	%DIAL9-3-MSG:ADJ-3-ADJFIBIDB: Adjacency update with invalid fibidb(9 Symptom: Cannot bring up calls on a Cisco AS5850 gateway with 4 trunk cards and 8 UPC cards being managed by a single RSC in handover-split mode. Conditions: FIB errors will occur and calls will fail to connect as soon as calls are attempted in the system with the number of cards described + one RSC in "extra-load" state. The redundancy mode has to be "handover-split". Workaround: Reduce the number of trunk cards to 3 and UPC cards to 6, or run the system in "classic-split" mode.
CSCdx26331	SIP: Connect Timestamp missing in CallHistory when ACK is missing Symptom: The Call History information generated by the SIP call leg does not have a valid (non-zero) duration while the POTS Call History for the same call has a non-zero duration. Conditions: This will happen when the ACK fails to reach the TGW following an answer (200 OK response). Workaround: There is no workaround.
CSCdx37208	L2TP: Traceback at FM-3-TBLENT_NOT_FOUND, FCL-3-NO_STREAM_ID Symptom: Following Traceback messages may be seen while using L2TP on Cisco AS5850 with Cisco IOS Release 12.2(2)XB5 pre-fcs ios. Apr 19 14:21:32.974 PDT: %FM-3-TBLENT_NOT_FOUND: fm_marvel_get_unicast_streamid_guts -Process= "L2TP mgmt daemon", ipl= 0, pid= 123 -Traceback= 602A2D88 602A3028 602A3128 60857918 609BE130 607A23AC 607C0980 607BBCB0 607BCE28 601C1204 601C11F0 Apr 19 14:21:32.974 PDT: %FCL-3-NO_STREAM_ID: FCL unable to obtain stream id from FM for slot -1. Interface Name = Virtual-Access54 Interface type = 15 -Process= "L2TP mgmt daemon", ipl= 0, pid= 123 -Traceback= 6085793C 609BE130 607A23AC 607C0980 607BBCB0 607BCE28 601C1204 601C11F0
CSCdx40546	No ANI Infomation for T37 offramp fax Symptom: For T.37 offramp fax, the ANI information is currently available only from the message envelope of the email. But in the case that the mail has to be bounced (such as invalid fax machine number), the mail cannot be bounced back to the correct account. The call cannot be billed in this case.
CSCin03065	New L2TP Tunnel created with existing Tunnel to same LNS. Symptom: When an attempt is made to create an additional session that has similar tunnel parameters that are defined by a RADIUS profile (for the same domain, the same user, or a different user), instead of creating a session under the existing tunnel, a new tunnel and a session are created. This condition is observed in Cisco IOS Release 12.2(7.4)T and occurs if the tunnel parameters are defined by RADIUS without either of the following definitions: •Cisco-Avpair vpdn:tunnel-id = "xyz" •Tunnel-Client-Auth-ID = "xyz" Workaround: Define one of the following definitions under a RADIUS profile when tunnel parameters are defined: •Cisco-Avpair vpdn:tunnel-id = "xyz" •Tunnel-Client-Auth-ID = "xyz"
CSCin06313	RM/AUTH: Process (22) failed to register to VPDN message while boot Symptom: The Cisco AS5850 gateway pops out the following error message after boot up: 00:00:38: RM/AUTH: Process (22) failed to register to VPDN This message is seen with c5850-p9-mz-v122_2_xb_throttle_flo_t.0.4.0 image. Workaround: There is no workaround.
CSCuk32311	PPP: Only allow punt adjacencies to be installed until IPCP is open Symptom: When Cisco Express Forwarding (CEF) is enabled, adjacencies are erroneously added for sessions that have been forwarded using a tunnelling protocol such as L2TP or PPPoE. Adjacencies should only be added for sessions that terminate on the router, and only after the IP Control Protocl (IPCP) has been negotiated. Workaround: There is no workaround.
CSCuk33327	RADIUS fail during EAP should trigger LCP restart Symptom: After RADIUS failover, during EAP, the NAS would try to failover to a new RADIUS server. However, this is forbidden midway through authentication. As such, the NAS was required to restart the authentication process from scratch and allow the user another attempt to authenticate.

Open Caveats—Cisco IOS Release 12.2(2)XB4

All the caveats listed in this section are open in Cisco IOS Release 12.2(2)XB4. This section describes only severity 1 and 2 caveats and select severity 3 caveats

Table 19 Open Caveats for Cisco IOS Release 12.2(2)XB4
DDTS ID Number	Description
CSCdu69988	Symptom: Some modems may pause indefinitely in the VDEV state (0x00002000) and stop accepting calls. The modems become locked in the VDEV state (0x00002400) if an attempt is made to clear them. This condition affects only the Cisco AS5300 universal access server. Workaround: There is no workaround.
CSCdv38563	Symptom: Network access server (NAS) may fail to include attributes 90 and 91 when a router hostname is used as the tunnel ID and when the tunnel ID is not included in the user profile. Workaround: There is no workaround.
CSCdw34586	Symptom: Attribute 5 is included in the access-request twice and displayed with a wrong value. The access-accept has attribut 7 and 13 also missing.
CSCdw61066	Symptom: MICA modules might go BAD and then recover on its own, under normal conditions. This might be service impacting. Workaround: There is no workaround.
CSCin00405	Symptom: No RADIUS accounting start or stop record is sent by the NAS when ppp multilink and aaa accounting delay-start are configured. Workaround: Remove one of these two commands.

Resolved Caveats—Cisco IOS Release 12.2(2)XB4

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB4. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 20 Resolved Caveats for Cisco IOS Release 12.2(2)XB4
DDTS ID Number	Description
CSCdr47232	Set operation is not implemented for a few dsx1 specific MIB objects like dsx1LineType, dsx1LineCoding etc.
CSCdr85436	Description: This command can be used in the global config mode, to enable sending RADIUS attribute 32 (NAS-Identifier) in the accounting request. By default fully qualified domain name (FQDN) is sent in the attribute when the format is not specified. Syntax: `[no] radius-server attribute 32 include-in-accounting-req {format <A string that may have %i, %h or %d.>}` `%i = IP address` `%h = Hostname` `%d = Domain name` FQDN is sent by default if the format string is not configured. Examples: `manly(config)#radius-server attribute 32 include-in-accounting-req format cisco %h.%d %i` Following string will be sent in NAS-identifier as a part of accounting record. `cisco manly.nlab.cisco.com 10.0.1.67`
CSCdr93141	Symptom: The user-maxlinks feature (see http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/maxlink.htm) does not work when configured on a VPDN LNS/HGW.
CSCdt63321	Symptom: An IP route entry may fail to be updated properly when one-step and two-step translations are performed using the Serial Line Internet Protocol (SLIP). Workaround: There is no workaround.
CSCdu19432	Attribute Acct-Session-Time [46] in Exec Acct. Stop Record is zero. Workaround: There is no workaround.
CSCdu35843	Symptom: IP access lists are not installed when they are received from a RADIUS server. This condition is observed in Cisco IOS Release 12.2(1.2)PI.
CSCdu36862	A system accounting record needs to be sent when a RADIUS server is added or deleted.
CSCdu40402	Symptom: On Cisco AS5400, Cisco AS5800, and Cisco AS5850 access servers running Cisco IOS Release 12.2XB, executing the command show tdm mapping will not show resource s that are used for CAS calls. Workaround: There is no workaround.
CSCdu40615	Symptom: Some clients may fail to successfully complete IP Control Protocol (IPCP) negotiations when thousands of PPP sessions are simultaneously reestablished, as is the case when an interface with many links is recycled. All Layer 2 Tunneling Protocol (L2TP) sessions are established, but some client virtual access interfaces may not get a negotiated IP address. The missing IP address results in lost IP connectivity on that link. Workaround: There is no workaround.
CSCdu43689	Symptom: Currently, the Per-User Request buffer is limited to 600 bytes. If the user profile has more than 600 bytes of configuration information, the Per-User attributes are not processed, which results in rejecting the user. Workaround: There is no workaround.
CSCdu65125	Cisco AS5800 (NAS) does not negotiate multilink ppp over L2F tunnel.
CSCdu64847	CISCO-AAA-SESSION-MIB user disconnect feature doesn't work for vpdn connections on the LNS.
CSCdu67010	Symptom: Some TACACS+ attribute string names and attribute string values have changed slightly, e.g. "nas_rx_speed" is now "nas-rx-speed". This may cause problems for backend accounting applications trying to process records or authorization failures.
CSCdu74728	Symptom: No accounting records are generated for outbound Telnet sessions after connection accounting is configured. Workaround: There is no workaround.
CSCdu84692	Symptom: When using Cisco IOS Release 12.2(2.x) and Cisco IOS Release 12.2(3.x)PI code, local VPDN authorization does not failover to the next method in the method list if the domain/dnis profile is not found. The workaround is to only use RADIUS/TACACS+ vpdn authorization.
CSCdu86243	Symptom: The RADIUS attributes Ascend-Client-Primary-DNS and Ascend-Client-Secondary-DNS do not work in Cisco IOS Release 12.2(3.4)T or later. The Cisco-AVPair ip:dns-server also does not work. Workaround: There is no workaround.
CSCdv01412	Conditions under which the problem occurs: `FXS FastEthernet FXS(LoopBack)` `[Pots A]--------[1750_r1]--------\|-------[1750_r2]` `dial-peer voice 1 voip dial-peer voice 2 voip` `destination-pattern 300 destination-pattern 300` `session target ipv4:100.0.0.2 session target loopback:rtp` When A calls 300, no voice loopback occurs. Symptoms of the problem: silent. Workaround: There is no workaround.
CSCdv01555	Symptom: Spurious access may been seen when TACACS+ is enabled in Cisco IOS Release 12.2(3.4)T or later. Workaround: There is no workaround.
CSCdv02732	Symptom: A router that is running Cisco IOS Release 12.2(3.4) T or a later release may reload unexpectedly after the Terminal Access Controller Access Control System (TACACS+) command accounting is enabled and a config net privileged EXEC command is executed. Workaround: There is no workaround.
CSCdv03076	Symptom: A Cisco router running Cisco IOS Release 12.2(3.4)T or later will not process Ascend RADIUS server attributes even if "non-standard" is part of the RADIUS-server host configuration statement if the RADIUS-server is referenced through a aaa server group. The workaround is not to use a server-group and use group RADIUS instead.
CSCdv03689	Symptom: If a Point to Point Protocol (PPP) Multilink bundle interface goes down while data is flowing through it, a Cisco router may reload. Workaround: There is no workaround.
CSCdv04999	Symptom: The username, accounting record type, and service attributes in the command accounting record is do not have appropriate value. Workaround: There is no workaround.
CSCdv13634	Symptom: AAA Accounting is not done for the additional links added to Multilink PPP bundle when "aaa accounting delay-start" is configured. Workaround: There is no workaround.
CSCdv15409	Symptom: Router throughput decreases as memory consumption increases. Conditions: This happens when the customer is using RADIUS as an authentication protocol Analysis: A memory leak was found when using RADIUS. For each session a small amount of memory ~40 bytes gets leaked. This will cause the box to lock-up after thousands of sessions depending on the amount of available memory. Workaround: There is no workaround.
CSCdv19031	Symptom: Currently with RADIUS debugging turned on customers see a lot of debugs describing attributes in the packets sent and received. In order to reduce the amount of spewed out on the console a new option of 'brief' needs to be added the debug radius command. This option will only indicate I/O transactions with some packet header information. Customers not turning on debugging or, not doing RADIUS won't see this problem.
CSCdv19928	Symptom: When the Idle-Timeout attribute is received from RADIUS on an asynchronous interface, a vaccess interface is created and the timeout is not applied directly to the asynchronous interface. The Idle-Timeout attribute still works. The only side effect is that there is an extra vaccess created that is bound to the asynchronous interface. Workaround: There is no workaround.
CSCdv20977	Symptom: Incoming Multilink Point-to-Point Protocol (MLP) packets from an ATM interface are getting process switched when a virtual template is used for the MLP bundle configuration.
CSCdv22728	Symptom: During a Exec-virtual private dialup network (Exec-VPDN) shell-based login, a call is torn down if a user attempts to get authenticated by Network Access Solutions (NAS) before a PPP session is established. Workaround: There is no workaround.
CSCdv26709	Symptom: Certain values for Ascend-Disconnect-Cause and Ascend-Connect-Progress are recorded inaccurately in Stop messages. This is mainly observed in 122T train. This problem is observed with PPP sessions when using RADIUS Accounting. Workaround: There is no workaround.
CSCdv29468	Symptom: If a PPP client does not authenticate after agreeing to do so during LCP negotiation, the PPP session will continue to stay open in this limbo state until the client disconnects the session.
CSCdv33270	Symptom: Under certain conditions, resources may be associated with a virtual private dialup network (VPDN) group even when there are no active calls. Workaround: There is no workaround.
CSCdv33313	Symptom: When network accounting is performed for PPP over ATM (PPPoA) sessions, RADIUS "start" or "stop" accounting records may occasionally fail to be sent. There is no workaround. Under certain conditions on a LAC, if the session is a VPDN forwarded session and the connection to the LAC is a dedicated serial line, memory can be leaked because AAA misses the stop record, so it never cleans up the AAA data for the session. This will happen if the connection continuously tries to renegotiate then attempt forwarding, which never succeeds. Eventually, the client sends a TERMREQ which restarts the session, but AAA does not get a NET STOP event so memory is leaked.
CSCdv34768	Symptom: A Cisco router running IOS may show the following traceback when using "local-case" authentication: `00:05:16: %AAA-3-BADMETHOD: Cannot process authentication method 2160756888` `-Process= "AAA Server", ipl= 0, pid= 26` `-Traceback= 8016F170 8016A6C8 8016AED0 8016B048 8019A94C` Workaround: There is no workaround.
CSCdv35939	Symptom: Modems might be marked as BAD as a result of Port-Modem-Startup Test. Workaround: Disable Port-Modem-Startup test and reboot the Cisco AS5800 RS.
CSCdv40729	Symptom: In a plain bri-pri (Peer - NAS) scenario, when a call is disconnected with the command 'clear in serial0:23' on the NAS, the Ascend-Disconnect-Cause value generated is '0' (No-Reason). When the call is brought down by clearing the interface on the peer, it is given a value(63). If brought down by doing 'shutdown' on peer/NAS value 11 is generated. The problem occurs only with by doing clear interface on the NAS.
CSCdv40116	Symptom: Reverse-access Authorization fails if the method used is RADIUS. RADIUS mandatory attribute "port" is not properly obtained causing this authorization failure. Workaround: There is no workaround.
CSCdv41871	Symptom: Ping fails when non-mlppp call is up on B-channel previously used to terminate mlppp call.
CSCdv43136	Symptom: We may see some unexpected debug information during call suspend. Those debug information doesn't cause any side effect beside displaying unexpected debug information.
CSCdv43856	Symptom: aaa attr debug does not show the tag added. This is seen in Cisco IOS Release 12.2(4.2)PI. This is just a problem in debug and will not affect any other functionality.
CSCdv53233	Symptom: The console of a Cisco AS5800 router shelf may display several No active RADIUS servers found messages followed by RADIUS server is responding again (previously dead) messages when the server is working normally and authenticating users. This condition does not impact service. Workaround: Remove the radius-server deadtime minutes global configuration command from the router.
CSCdv54349	Symptom: When running Cisco IOS Release 12.2(5.2)T and later IOS images, you may be unable to do local AAA authentication. There is no workaround. Either do AAA to a remote server or downgrade to an earlier release of code.
CSCdv62424	Symptom: A port that has been marked as BAD by system processing engine (SPE) modem recovery after a call failure cannot be recovered using the clear spe EXEC command. Calls cannot be placed to the port. Workaround: Issue the clear port EXEC command.
CSCdv62649	Symptom: The command ip tacacs source-interface doesn't work properly. If configured to use loopback interface for tacacs packets, router may still use interface address.
CSCdv64668	Symptom: The first PAP authentication after a PPP renegotiation triggered by a CONFREQ from the client will fail even though the RADIUS/TACACS+ server returns a success. Workaround: There is no workaround.
CSCdv67009	Symptom: The following error message may be seen on a Cisco voice gateway running the Session Initiation Protocol (SIP): `Nov 24 20:24:12: %SIP-3-BADPAIR: Unexpected event 14 (SIPSPI_EV_CC_CALL_CONNECT) in state 8 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)` `-Traceback= 60DAD08C 60DAD7AC 6040ACD4 6040ACC0.` This indicates that the call was cancelled while it was in the process of being brought up. This message can be safely ignored.
CSCdv76649	Symptom: When the customer tries to use ^C to abort the copy operation when he prompted for confirmation, he can't break out of the copy process.
CSCdv77234	Symptom: On Cisco dial access concentrator routers, L2TP tunnels do not come up when the resource pooling feature is enabled. Workaround: There is no workaround.
CSCdv78693	Symptom: Spurious memory access messages appear on gatekeepers when an URQ without a call signal address in it is sent to the gateway. Workaround: There is no workaround.
CSCdv79210	Symptom: A Cisco router gradually looses memory when Media Gateway Control Protocol (MGCP) calls are originated on the router. Workaround: There is no workaround.
CSCdv80016	Symptom: After the OIR of DMM or HMM cards, some modems may become stuck in Download state. Conditions: This seems to happen if the OIR occurs shortly after a reload of the router. Workaround: Define spe firmware locations in config mode after the OIR event to clear the SPEs.
CSCdv80902	Symptom: PPP negotiation fails when you use digital PPP with dialer profiles and the serial interface on the Cisco AS5800 is reset (i.e., execute a shut / no shut on the serial interface 1/5/1:15). This problem only appears when the serial interface is reset. Workaround: There is no workaround.
CSCdv83040	Symptom: When using Ascend RADIUS attribute 242, IP protocols of 50 and 51 will not be accepted. This will cause users with these IPsec protocols set in their profile to be disconnected.
CSCdv83402	Symptom: A PPPoE/PPPoA aggregation router may unexpectedly reload when many PPP events happen in a short amount of time. The router will display a STACKLOW message before reloading.
CSCdv87754	Symptom: A Cisco AS5850 Route Switch Controller incorrectly attempts to repeatedly netboot a Cisco IOS image if it cannot find the specified boot system image on its compact flash. The system interprets the full path of the configured boot image that failed as the image it should netboot. Messages similar to the following are observed: `Sleeping for 2 secs before next netboot attempt` `%SYS-6-READ_BOOTFILE_FAIL: disk0:c5850-p9-mz File boot failed -- File not` `accessible.` The correct behavior for a bootloader if it cannot find any specified boot images at reload time is to fall back and request the system to run the first image it can find off disk0: or bootflash: Conditions: Cisco AS5850 Route Switch Controllers with Cisco IOS Release 12.2(2)XB1 or Cisco IOS Release 12.2(2)XB2 bootloaders may experience this problem at reload time if the boot system image configuration points to a file on disk0: that does not exist. Workaround: Ensure that the boot system image configuration points to an existing and valid image on disk0:, provide additional correct boot image locations in the configuration, or use a bootloader of version Cisco IOS Release 12.1(5)XV3.
CSCdv88723	Symptom: A memory leak may occur for Signaling System 7 (SS7) Continuity Test (COT) transponder calls at the egress gateway during stress testing. This is a voice-only system that is handling interactive voice response (IVR) calls. Workaround: There is no workaround.
CSCdv88831	Symptom: Low Call Success Rate on Cisco AS5800 accompanied by premature disconnects. Conditions: The Cisco AS5800 Voice Gateway running Cisco IOS Release 12.1(5)XM6 with IVR calls. This symptom is seen even with the Cisco IOS Release 12.2(2)XB2 image. Workaround: There is no workaround.
CSCdw00019	Symptom: Although SGBP tunnels will still be up, SGBP bidding itself might stop working after a router has been up for sometime. This problem only occurs if two routers in the stack group receive two links of a bundle at the same time. Removing, and reapplying the SGBP config was sufficient to get things working again.
CSCdw01330	Symptom: When an IPC324 dial feature card (DFC) is inserted and removed on an active Cisco AS5800 universal access server or when the Service Processing Element (SPE) is reinitialized using the clear spe EXEC command, some SPEs may become stuck in the "download" state. Workaround: There is no workaround.
CSCdw01642	Symptom: A Cisco AS5800 access server that is running Cisco IOS Release 12.2 may be restarted by a bus error at PC 0x603D2EC4, address 0xC. There is no workaround. After this fix, the counters on the Virtual-Access interface could show wrong values when IP CEF is enabled and used for the L2TP sessions, on high end routers. Please ensure that CSCdv57640 is also present in the image if this is an issue.
CSCdw01726	Symptom: A Simple Network Management Protocol version 3 (SNMPv3) user is created using message digest 5 (MD5) authentication using the following commands: •snmp group groupy v3 auth • snmp user abcdefghij groupy v3 auth md5 abcdefghij An SNMP walk is performed, the configuration is saved, and the router is reloaded. `newhope:~/src/wccp2# snmpwalk -v 3 -u abcdefghij -A abcdefghij -a MD5 -l` `AuthNoPriv 194.12.224.11` It is working and a debug snmp header shows this: `Incoming SNMP packet` `: v3 packet security model: v3 security level: auth` `username: abcdefghij` A second SNMP walk is performed: `newhope:~/src/wccp2# snmpwalk -v 3 -u abcdefghij -A abcdefghij -a MD5 -l` `AuthNoPriv 194.12.224.11` After the second SNMP walk is performed, the command does not return any output and the debug snmp headers show this: `Incoming SNMP packet` `: v3 packet security model: v3 security level: noauth` `: username: abcdefghij` Workaround: There is no workaround.
CSCdw02367	Symptom: Incoming E1-R2 calls will fail on Cisco AS5800 running 122-2.XB1 version, with UP324 card connected. Workaround: There is no workaround.
CSCdw02945	Symptom: Incoming calls may fail to create a virtual profile even though the router is configured for this. Conditions: This problem may occur in a dial up environment where a virtual profile virtual template is defined but where no AAA authorization has been enabled This issue only occurs in Cisco IOS Release 12.2 T. Workaround: A workaround is to configure AAA authorization e.g., aaa authorization network default local
CSCdw06322	Symptom: The following error message may be seen on a Cisco voice gateway running the Session Initiation Protocol (SIP): `Nov 24 20:24:12: %SIP-3-BADPAIR: Unexpected event 14 (SIPSPI_EV_CC_CALL_CONNECT) in state 8 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)` `-Traceback= 60DAD08C 60DAD7AC 6040ACD4 6040ACC0.` This indicates that the call was cancelled while it was in the process of being brought up. This message can be safely ignored.
CSCdw09542	Symptom: Before this fix, per-user authorization required a service type of Outbound in the RADIUS profile.
CSCdw11765	Symptom: PPP Link Control Protocol (LCP) is not accepting sent CONFACK negotiated on a asynchronous interface for a virtual profile. Workaround: There is no workaround.
CSCdw13432	Symptom: When the called party is busy in a two-stage call scenario, the calling party may not hear a busy tone and the call terminates immediately. This behavior is observed with Cisco IOS Release 12.2(2)XB, Release 12.2(7), and some earlier Cisco IOS Release 12.2 releases. Workaround: There is no workaround.
CSCdw18785	Symptom: When a 302 redirect is received after a 18x with a COntact header the outgoing INVITE will have the request uri of the Contact in the 18x. It should use the Contact of the 302. Workaround: Disable rel1xx on the router.
CSCdw22072	Symptom: In Cisco IOS Release 12.2(5.7)T, the virtual-profile if-needed global configuration command that is used to disable a virtual access interface for modem calls does not work. Workaround: There is no workaround.
CSCdw23836	Symptom: When a 18x is received which was sent reliably, a PRACK needs to be sent. Subsequent 18x's received that match the previous one's call leg do not receive a PRACK. Workaround: Disable reliable provisional responses.
CSCdw25746	Symptom: Cisco Voice Gateways may experience a reload especially when running high levels of traffic. Conditions: This problem may be experienced in Cisco IOS Release 12.2(2)XB2 and Cisco IOS Release 12.2 mainline releases. Workaround: There is no workaround.
CSCdw28786	Symptom: When the customer tries to use ^C to abort the copy operation when he prompted for confirmation, he can't break out of the copy process.
CSCdw30994	Symptom: When downloading IP pools from a AAA server, there is no way to define a non-contiguous range of addresses using multiple statements like this: `"ip:pool-def#1=aol-pool 192.168.232.0 192.168.237.255",` `"ip:pool-def#2=aol-pool 192.168.238.1 192.168.238.160"` When those statements are applied, the second pool-def overwrites the first one. Defining the pools on the command line yields the expected result. This only happens in Cisco IOS Release 12.2(2)XB ED release train. Cisco IOS Release 12.1/Cisco IOS Release 12.2 does not exhibit this behavior.
CSCdw32067	Symptom: It is noticed that when enabling RPM/RPMS, after some time of running, the Cisco AS5800 with Cisco IOS Release 12.1(11) will show modems in use while there are no active users connected.
CSCdw35046	Symptom: A Cisco router may reload when proxied RADIUS is used for authentication and accounting. Workaround: There is no workaround.
CSCdw35930	Symptom: The command aaa authentication attempts login <n> appears in the configuration if the command tacacs-server attempts <n> is present in the configuration. Changes to either command will be reflected in the other. Also, the number of attempts granted is actually one less than the number configured. Workaround: Configure one more attempt than the number you actually want.
CSCdw37055	Symptom: A Cisco AS5800 universal access server that is used as a voice gateway may display an assertion failed error message when a voice call is received. Workaround: There is no workaround.
CSCdw43862	Symptom: For some devices that are not conforming to V.110 async to sync padding requirements, this cli command allow the users to disable the padding.
CSCdw47450	Symptom: CPC tone is not being generated for a CLI (Caller Line identification) analog call terminating on a Cisco AS5800. The Information element in ISDN signaling is being ignored by the Cisco AS5800. This could be the probable cause. Workaround: There is no workaround.
CSCdw46065	Symptom: A Cisco router that is used as a gateway may reload if one of multiple record routes that are received on the gateway is invalid. Workaround: There is no workaround.
CSCdw51491	When using preauth and the 'autocommand' feature, some PPP calls may fail to come up.
CSCdw53243	Symptom: In a Cisco Signaling System 7 (SS7) Interconnect for Voice Gateways solution, if a Cisco AS5400 universal access gateway receives an incoming time-division multiplexing (TDM) call (NI-2, PRI, channel-associated signaling [CAS]) with a called number that does not match a configured dial-peer, the call will be connected to a modem, and a modem tone will be played back to the calling party. This is normal behavior, however there is no configurable option for such to be rejected instead of being treated as a modem call.
CSCdw53071	Symptom: If a second call is made after the first call is completely disconnected (by hanging up the phone instead of using the flash feature to switch between two calls), the second call may fail. Workaround: There is no workaround.
CSCdw58272	Symptom: Mica Modems might be marked BAD after a Cisco AS5800 has been running for more then 10 hours under stress conditions. Workaround: There is no workaround.
CSCdw58677	Symptom: A Cisco AS5800 may crash with the bus error exception when a particular vendor's IP phone tries to redirect the call. Workaround: There is no workaround.
CSCdw60334	Symptom: Following spurious memory access messages would be seen with a Cisco AS5800 running Cisco IOS Release 12.2(2)XB3 with incoming analog digital isdn calls. `Jan 30 14:57:12.591 PST: %ALIGN-3-TRACE: -Traceback= 60840840 607C25D4 607B6DAC 607E8D48 607E811C 607E8260 607E8E84 6055E0F4` `Jan 30 14:57:12.591 PST: %ALIGN-3-TRACE: -Traceback= 60840844 607C25D4 607B6DAC 607E8D48 607E811C 607E8260 607E8E84 6055E0F4` `Jan 30 14:57:12.591 PST: %ALIGN-3-TRACE: -Traceback= 6084084C 607C25D4 607B6DAC 607E8D48 607E811C 607E8260 607E8E84 6055E0F4` `Jan 30 14:57:12.591 PST: %ALIGN-3-TRACE: -Traceback= 60840850 607C25D4 607B6DAC 607E8D48 607E811C 607E8260 607E8E84 6055E0F4` `Jan 30 14:57:12.591 PST: %ALIGN-3-TRACE: -Traceback= 60840858 607C25D4 607B6DAC 607E8D48 607E811C 607E8260 607E8E84 6055E0F4` `Jan 30 14:57:12.591 PST: %ALIGN-3-TRACE: -Traceback= 60840844 607C25D4 607C69AC 607B6540 607B30C4 607B34C0 607E811C 607E8260` `Jan 30 14:57:12.591 PST: %ALIGN-3-TRACE: -Traceback= 60840850 607C25D4 607C69AC 607B6540 607B30C4 607B34C0 607E811C 607E8260` The problem is not service impacting, but it will cause performance issues. The following syslog message will also be seen with each call: `Jan 30 20:30:14.547 PST: XCSP:Slot 2 not initialized`
CSCdw62969	Symptom: A network access server (NAS) that is running Cisco IOS Release 12.2(02)XB3 or Release 12.2(8)T may reload when Layer 2 forwarding (L2F) virtual private dial-up network (VPDN) calls are placed using an authentication, authorization, and accounting (AAA) VPDN user profile that does not contain the RADIUS class (25) attribute. Workaround: Configure a dummy RADIUS class (25) attribute in the VPDN user profile on the AAA server.
CSCdw66251	Symptom: SIP gateway midcall INVITE requests in the called to calling party direction will have the Route header constructed incorrectly. ACK requests in the called to calling party direction will have the request URI constructed incorrectly. This could cause some operations such as T.38 fax relay to fail. This problem can occur only if two or more SIP proxies are in the SIP signaling path and the Record Route feature is enabled. Workaround: There is no workaround.
CSCdw67688	Symptom: UPC324 cards might reload after running for a while. This might trigger RS reload in some cases. This might be service impacting.
CSCdw68066	Symptom: A Cisco router that is configured as a Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC) may not free memory properly if the vpdn authen-before-forward VPDN group mode command is configured. Workaround: There is no workaround.
CSCdw68658	Symptom: The gateway will reject a mid-call Invite with hold sdp where the connection information (c line) is set to 0.0.0.0 and the port number of the media description (m line) is also set to 0. Instead of responding with a 200 OK response, the gateway will return a 488 Media Unacceptable response. The problem will not occur if the user agent placing the gateway on hold, sets the port number to a value other than 0. Workaround: There is no workaround.
CSCdw77524	Symptom: When rtp payload-type cisco-codec-fax-ind is changed from 96 to 99 then we ingress an invite with sdp rtp payload type 96 nte the gateway responds with an rtp payload type 97. These 2 payload types are chosen for the proprietary implementation of Cisco fax-relay. Per RFC2833, the gateway should not be doing this. This affects all Cisco fax gateways which support Cisco fax-relay. Workaround: Use the rtp payload-type command on the Cisco gateway to change the assignment of the payload types, but this command is broken.
CSCuk25642	Symptom: When using callin authentication on a LSDO call with RADIUS, PPP sends multiple authorization requests to AAA. This will slow down call setup but have no functional impact.
CSCuk25721	Symptom: RADIUS CLID attribute was missing for large scale dialout accounting.
CSCuk25947	Symptom: If PPP authentication is configured on an interface and if a user negotiates a callback during a Link Control Protocol (LCP) operation, the call will fail if the user does not have any callback information configured. Workaround: There is no workaround.
CSCuk26562	Symptom: AAA id debugging was not clear and displayed far too much information.
CSCuk26642	Symptom: RADIUS calls with a non-RFC supported value were accepted when they should be rejected.
CSCuk27924	Symptom: send-auth would not be applied on the NAS, but rather the value of auth-type would be used instead.
CSCuk28445	Symptom: We now store a generic 'wrapper' record which holds information in the tree, generic to all accounting records. This way, we are not impacted by the life-span of any one accounting record.

Open Caveats—Cisco IOS Release 12.2(2)XB3

There are no open caveats specific to Cisco IOS Release 12.2(2)XB3 that require documentation in the release notes.

Resolved Caveats—Cisco IOS Release 12.2(2)XB3

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB3. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 21 Resolved Caveats for Cisco IOS Release 12.2(2)XB3
DDTS ID Number	Description
CSCdw65903	Symptom: An error can occur with management protocol processing. Please use the following URL for further information: http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903

Open Caveats—Cisco IOS Release 12.2(2)XB2

All the caveats listed in this section are open in Cisco IOS Release 12.2(2)XB2. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 22 Open Caveats for Cisco IOS Release 12.2(2)XB2
DDTS ID Number	Description
CSCdv88831	Symptom: Low Call Success Rate on a Cisco AS5800 accompanied by premature disconnects. Conditions: The Cisco AS5800 Voice Gateway running Cisco IOS Release 12.1(5)XM6 with IVR calls. This symptom is seen even with the Cisco IOS Release 12.2(2)XB2 image. Workaround: There is no workaround.
CSCdw05780	Symptom: Some MGCP hairpinned call flows will require an additional MDCX to work properly. Conditions: The problem is that the MGCP state machine seems to behave differently for the two call flows below: 1. First is the "official" hairpinning call flow from the interface spec. The code seems more geared towards supporting this: 1B) CRCX(endpt B, nt:LOCAL) -> Created as hairpinned 1C) CRCX(endpt A, nt:LOCAL) -> Created as hairpinned 1D) MDCX(endpt B, nt:LOCAL) -> Tie the two together 2. Second is a call flow in which the first CRCX does not indicate hairpin (nt:IN) and that connection is later modified to be hairpinned (MDCX w/ nt:LOCAL): 2A) CRCX(endpt A, nt:IN) -> Starts out as non-hairpinned 2B) CRCX(endpt B, nt:LOCAL) -> Created as hairpinned 2C) MDCX(endpt A, nt:LOCAL) -> Changed to hairpinned 2D) MDCX(endpt B, nt:LOCAL) -> Tie the two together <Things should be okay at this point but they're not an extra message is required:> 2E) MDCX(endpt A, nt:LOCAL) -> EXTRA, unnecessary message. This is a duplicate of message 2C This caveat is the reason for "2E" message. Workaround: •Do not create to-be-hairpinned connections in a non-hairpinned manner (i.e., use "nt:LOCAL" from the initial CRCX). As stated above, the official hairpin callflow already behaves this way. •Do not use hairpinned connections at all. This will require more system resources but may be the only workaround if the call agent is unable to determine, from the first CRCX, that the connection will be hairpinned. Or •Use a call agent which will allow the second MDCX to be sent. This is an unlikely solution but may work for testing.
CSCdw14183	Symptom: Crash at clock_get_time(). This defect was seen after including port modem start-up test command on the Cisco AS5800 on Cisco IOS Release 12.2XB2 image. There is no workaround.
CSCdw19733	Symptom: A Cisco AS5800 is controlled by an MGC that support only RLM version 1 where only ISDN service messages and not Group Service Messages are supported. When a big number of controller flaps (for example when a T3 containing several T1 flaps) not all the ISDN service messages are sent. As a result the trunk (CIC) status on the MGC may be incongruent with the controller status on the Cisco AS5800. Workaround: Use an MGC that supports RLM version 2 and ISDN group service messages.

Resolved Caveats—Cisco IOS Release 12.2(2)XB2

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB2. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 23 Resolved Caveats for Cisco IOS Release 12.2(2)XB2
DDTS ID Number	Description
CSCdv35958	Symptom: MICA modems might be marked BUSIEDOUT or OOS after calls have been coming in and dropping Workaround: Doing shut/no-shut brings the modems back to ACTIVE state.
CSCdv35939	Symptom: Modems might be marked as BAD as a result of Port-Modem-Startup Test. Workaround: Disable Port-Modem-Startup test and reboot the Cisco AS5800 RS.
CSCdv54898	Symptom: Low Call Success Rate on Cisco AS5800 accompanied by abnormal and premature disconnects. Conditions: A Cisco AS5800 Voice Gateway running Cisco IOS Release 12.1(5)XM5 with COT enabled. Also no modem cards in the system. Workaround: Either disable COT or add a modem card to the system.
CSCdv58141	Symptom: When doing DTMF Relay tone testing, Nextport presents a power level difference between the 2 frequencies of each digit (1234567890ABCD*#). This problem happens with Inband Signaling DTMF Relay method RTP-NTE generating and detecting digits.
CSCdv74216	Symptom: A Cisco AS5800 Voice Gateway reboots with "Watchdog hard reset" error during load/stress test.
CSCdv88723	Symptom: There is a memory leak for SS7 COT transponder calls at the egress gateway on stress testing. Conditions: This is a voice only system and these are IVR calls. Workaround: There is no workaround.
CSCdw17239	Symptom: The decoded information in the NAS-port attribute for an incoming call does not match the trunk/timeslot on which the call is connected. Conditions: This problem occurs when using NAS-port formats A - C and E for calls using CAS & R2 signaling. Workaround: There is no workaround. CAS calls using NAS Port formats A through C can result in having incorrect or incomplete information provided. This is a result of the fact that no real interface exists (other than the Async) for a CAS call. This results in the AAA code either rejecting the interface information (format C) or not displaying the interface type (formats A and B), resulting in a backward compatibility problem.

Open Caveats—Cisco IOS Release 12.2(2)XB1

This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB1 and describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 24 Open Caveats for Cisco IOS Release 12.2(2)XB1
DDTS ID Number	Description
CSCdu82536	Symptom: This defect is observed in the latest Cisco IOS Release 12.2(03)PI image. Whenever the active analog calls are cleared, the resource manager does not send the message to the resource-pool analog call counter resulting in the resource-pool showing active calls. Workaround: There is no workaround.
CSCdu87596	Symptom: This defect is to be seen when there is a stress test which is performed and after the stress test, the calltracker counter and resource-pool counters still show active calls even after the calls are cleared on the Cisco AS5800. Workaround: The workaround for the calltracker counter is to disable the calltracker and then again enable it. For the resource-pool counter, the workaround is to reload the Cisco AS5800.
CSCdv35939	Symptom: Modems might be marked as BAD as a result of Port-Modem-Startup Test. Workaround: Disable Port-Modem-Startup test and reboot the Cisco AS5800 RS.
CSCdv35958	Symptom: MICA modems might be marked BUSIEDOUT or OOS after calls have been coming in and dropping Workaround: Doing shut/no-shut brings the modems back to ACTIVE state.
CSCdv41055	Symptom: When issuing a busy out of an entire CE1 card using "busyout 1/0", the service messages are only generated for the first four E1 ports plus four B channels of the fifth port for a total of 128 service messages. Workaround: The workaround is to busyout each E1 one at a time to ensure all B channels are taken out of service.
CSCdv54898	Symptom: Low Call Success Rate on Cisco AS5800 accompanied by abnormal and premature disconnects. Conditions: Cisco AS5800 Voice Gateway running Cisco IOS Release 12.1(5)XM5 with COT enabled. Also NO modem cards in the system. Workaround: Either disable COT or Add a modem card to the system.
CSCdv58141	Symptom: When doing DTMF Relay tone testing, Nextport presents a power level difference between the 2 frequencies of each digit (1234567890ABCD*#). This problem happens with Inband Signaling DTMF Relay method RTP-NTE generating and detecting digits.
CSCdv74913	Symptom: Following Spurious Memory Accesses will be recorded on a Cisco AS5800 with Cisco IOS Release 12.2(2)XB1 while using AAA idle timeout feature. `Oct 30 17:22:05.220 PST:%ALIGN-3-SPURIOUS: Spurious memory access made at 0x604AA6A8 reading 0x30` `Oct 30 17:22:05.220 PST: %ALIGN-3-TRACE: -Traceback= 604AA6A8 6049C6D0 607CFDBC 607D0308 607D02B0 607DC0E8 607DF268 607D0198` `Oct 30 17:22:05.220 PST: %ALIGN-3-TRACE: -Traceback= 604AA6B4 6049C6D0 607CFDBC 607D0308 607D02B0 607DC0E8 607DF268 607D0198` `Oct 30 17:24:05.260 PST: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x604AA6A8 reading 0x30` `Oct 30 17:24:05.260 PST: %ALIGN-3-TRACE: -Traceback= 604AA6A8 6049C6D0 607CFDBC 607D0308 607D02B0 607DC0E8 607DDA1C 607FE078` `Oct 30 17:24:05.260 PST: %ALIGN-3-TRACE: -Traceback= 604AA6B4 6049C6D0 607CFDBC 607D0308 607D02B0 607DC0E8 607DDA1C 607FE078` `NPE300-RS1#sh align` `Alignment data for:` `5800 Software (C5800-P4-M), Version 12.2(2)XB1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)` `TAC Support: http://www.cisco.com/tac` `Compiled Mon 29-Oct-01 17:18 by liha` `No alignment data has been recorded.` `Total Spurious Accesses 756, Recorded 4` `Address Count Traceback` `30 372 0x604AA6A8 0x6049C6D0 0x607CFDBC 0x607D0308` `0x607D02B0 0x607DC0E8 0x607DF268 0x607D0198` `214 372 0x604AA6B4 0x6049C6D0 0x607CFDBC 0x607D0308` `0x607D02B0 0x607DC0E8 0x607DF268 0x607D0198` `30 6 0x604AA6A8 0x6049C6D0 0x607CFDBC 0x607D0308` `0x607D02B0 0x607DC0E8 0x607DDA1C 0x607FE078` `214 6 0x604AA6B4 0x6049C6D0 0x607CFDBC 0x607D0308` `0x607D02B0 0x607DC0E8 0x607DDA1C 0x607FE078` Workaround: Do not use idle timeout feature through RADIUS.
CSCdv74216	Symptom: Cisco AS5800 Voice Gateway reboots with "Watchdog hard reset" error during load/stress test.
CSCdv76047	Symptom: A voice call fails at the egress gateway with COT transponder turned on. There is a failure in the COT functionality. Workaround: There is no workaround.

Resolved Caveats—Cisco IOS Release 12.2(2)XB1

All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB1. This section describes only severity 1 and 2 caveats and select severity 3 caveats.

Table 25 Resolved Caveats for Cisco IOS Release 12.2(2)XB1
DDTS ID Number	Description
CSCdv35939	Symptom: Modems might be marked as BAD as a result of Port-Modem-Startup Test. Workaround: Disable Port-Modem-Startup test and reboot the Cisco AS5800 RS.
CSCdv35958	Symptom: MICA modems might be marked BUSIEDOUT or OOS after calls have been coming in and dropping Workaround: Doing shut/no-shut brings the modems back to ACTIVE state.
CSCdv76047	Symptom: A voice call fails at the egress gateway with COT transponder turned on. There is a failure in the COT functionality. Workaround: There is no workaround.

Open and Resolved Caveats—Cisco IOS Release 12.2(2)XB

Cisco IOS Release 12.2(2)XB does not support the Cisco AS5850 universal gateway.

Table 26 Cisco IOS Release 12.1 Documentation Set
Books	Major Topics
•Cisco IOS Configuration Fundamentals Configuration Guide •Cisco IOS Configuration Fundamentals Command Reference	Configuration Fundamentals Overview Cisco IOS User Interfaces Cisco IOS File Management Cisco IOS System Management Cisco IOS User Interfaces Commands Cisco IOS File Management Commands Cisco IOS System Management Commands
•Cisco IOS Bridging and IBM Networking Configuration Guide •Cisco IOS Bridging and IBM Networking Command Reference, Volume I •Cisco IOS Bridging and IBM Networking Command Reference, Volume II	Using Cisco IOS Software Overview of SNA Internetworking Bridging IBM Networking
•Cisco IOS Dial Services Configuration Guide: Terminal Services •Cisco IOS Dial Services Configuration Guide: Network Services •Cisco IOS Dial Services Command Reference	Preparing for Dial Access Modem Configuration and Management ISDN and Signaling Configuration PPP Configuration Dial-on-Demand Routing Configuration Dial-Backup Configuration Terminal Service Configuration Large-Scale Dial Solutions Cost-Control Solutions Virtual Private Networks X.25 on ISDN Solutions Telco Solutions Dial-Related Addressing Services Interworking Dial Access Scenarios
•Cisco IOS Interface Configuration Guide •Cisco IOS Interface Command Reference	Interface Configuration Overview Configuring LAN Interfaces Configuring Serial Interfaces Configuring Logical Interfaces
•Cisco IOS IP and IP Routing Configuration Guide •Cisco IOS IP and IP Routing Command Reference	IP Addressing and Services IP Routing Protocols IP Multicast
•Cisco IOS AppleTalk and Novell IPX Configuration Guide •Cisco IOS AppleTalk and Novell IPX Command Reference	AppleTalk and Novell IPX Overview Configuring AppleTalk Configuring Novell IPX
•Cisco IOS Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Configuration Guide •Cisco IOS Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Command Reference	Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Overview Configuring Apollo Domain Configuring Banyan VINES Configuring DECnet Configuring ISO CLNS Configuring XNS
•Cisco IOS Multiservice Applications Configuration Guide •Cisco IOS Multiservice Applications Command Reference	Multiservice Applications Overview Voice Video Broadband
•Cisco IOS Quality of Service Solutions Configuration Guide •Cisco IOS Quality of Service Solutions Command Reference	Quality of Service Overview Classification Congestion Management Congestion Avoidance Policing and Shaping Signaling Link Efficiency Mechanisms Quality of Service Solutions
•Cisco IOS Security Configuration Guide •Cisco IOS Security Command Reference	Security Overview Authentication, Authorization, and Accounting (AAA) Security Server Protocols Traffic Filtering and Firewalls IP Security and Encryption Other Security Features
•Cisco IOS Switching Services Configuration Guide •Cisco IOS Switching Services Command Reference	Cisco IOS Switching Services Overview Cisco IOS Switching Paths Cisco Express Forwarding NetFlow Switching Multiprotocol Label Switching Multilayer Switching Multicast Distributed Switching Virtual LANs LAN Emulation
•Cisco IOS Wide-Area Networking Configuration Guide •Cisco IOS Wide-Area Networking Command Reference	Wide-Area Networking Overview Configuring ATM Configuring Frame Relay Configuring Frame Relay-ATM Interworking Configuring SMDS Configuring X.25 and LAPB
•Cisco IOS Configuration Guide Master Index •Cisco IOS Command Reference Master Index •Cisco IOS Debug Command Reference •Cisco IOS Dial Services Quick Configuration Guide •Cisco IOS Software System Error Messages •New Features in 12.1-Based Limited Lifetime Releases •New Features in Release 12.1 T •Release Notes (Release note and caveat documentation for 12.1-based releases and various platforms)

Obtaining Documentation

These sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com

Translated documentation is available at this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.

You can e-mail your comments to bug-doc@cisco.com.

You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:

•Streamline business processes and improve productivity

•Resolve technical issues with online support

•Download and test software packages

•Order Cisco learning materials and merchandise

•Register for online skill assessment, training, and certification programs

If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:

http://www.cisco.com

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Cisco TAC inquiries are categorized according to the urgency of the issue:

•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://www.cisco.com/register/

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Table Of Contents

Release Notes for Cisco AS5850 Universal Gateway for Cisco IOS Release 12.2(2)XB15

Contents

Introduction

System Requirements

Memory

Supported Hardware

Determining the Software Version

Feature Set Table

New and Changed Information

New Hardware and Software Features for Cisco IOS Release 12.2(2)XB2 to Cisco IOS Release 12.2(2)XB15

New Hardware Features in Cisco IOS Release 12.2(2)XB1

24 Port T1 Trunk Card for Cisco AS5850 Universal Gateway

New Software Features in Cisco IOS Release 12.2(2)XB1

100% ISDN Coverage Using NextPort DSPs

Full Functional Long Pound

RADIUS Packet of Disconnect

RSC Handover Redundancy on the Cisco AS5850 Gateway

Classic-Split Mode

Handover-Split Mode

V.44 LZJH Compression

V.92 Modem on Hold

V.92 Quick Connect

Voice H.323/SS7 and SIP Features on the Cisco AS5850 Universal Gateway

New Hardware and Software Features in Cisco IOS Release 12.2(2)XB

MIBs

Important Notes

Field Notices and Bulletins

Caveats for Cisco IOS Release 12.2 XB

Open Caveats—Cisco IOS Release 12.2(2)XB15

Resolved Caveats—Cisco IOS Release 12.2(2)XB15

Open Caveats—Cisco IOS Release 12.2(2)XB14

Resolved Caveats—Cisco IOS Release 12.2(2)XB14

No Caveats—Cisco IOS Release 12.2(2)XB13

Open Caveats—Cisco IOS Release 12.2(2)XB12

Resolved Caveats—Cisco IOS Release 12.2(2)XB12

Open Caveats—Cisco IOS Release 12.2(2)XB11

Resolved Caveats—Cisco IOS Release 12.2(2)XB11

Open Caveats—Cisco IOS Release 12.2(2)XB10

Resolved Caveats—Cisco IOS Release 12.2(2)XB10

Open Caveats—Cisco IOS Release 12.2(2)XB9

Resolved Caveats—Cisco IOS Release 12.2(2)XB9

Open Caveats—Cisco IOS Release 12.2(2)XB8

Resolved Caveats—Cisco IOS Release 12.2(2)XB8

Open Caveats—Cisco IOS Release 12.2(2)XB7

Resolved Caveats—Cisco IOS Release 12.2(2)XB7

Open Caveats—Cisco IOS Release 12.2(2)XB6

Resolved Caveats—Cisco IOS Release 12.2(2)XB6

Open Caveats—Cisco IOS Release 12.2(2)XB5

Resolved Caveats—Cisco IOS Release 12.2(2)XB5

Open Caveats—Cisco IOS Release 12.2(2)XB4

Resolved Caveats—Cisco IOS Release 12.2(2)XB4

Open Caveats—Cisco IOS Release 12.2(2)XB3

Resolved Caveats—Cisco IOS Release 12.2(2)XB3

Open Caveats—Cisco IOS Release 12.2(2)XB2

Resolved Caveats—Cisco IOS Release 12.2(2)XB2

Open Caveats—Cisco IOS Release 12.2(2)XB1

Resolved Caveats—Cisco IOS Release 12.2(2)XB1

Open and Resolved Caveats—Cisco IOS Release 12.2(2)XB

Related Documentation

Release-Specific Documents

Platform-Specific Documents

Feature Modules

Feature Navigator

Cisco IOS Software Documentation Set

Documentation Modules

Cisco IOS Release 12.1 Documentation Set

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center