|
Table Of Contents
Release Notes for Cisco AS5300 Universal Access Servers for Cisco IOS Release 12.2(2)XB15
Determining the Software Version
Microcode and Modem Code Software
New Hardware and Software Features in Cisco IOS Release 12.2(2)XB6 to Cisco IOS Release 12.2(2)XB15
New Hardware Features in Cisco IOS Release 12.2(2)XB5
New Software Features in Cisco IOS Release 12.2(2)XB5
New Hardware and Software Features from Cisco IOS Release 12.2(2)XB1 to Cisco IOS Release 12.2(2)XB4
New Hardware Features in Cisco IOS Release 12.2(2)XB
New Software Features in Cisco IOS Release 12.2(2)XB
Deprecated and Replacement MIBs
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)XB4a
Resolved Caveats—Cisco IOS Release 12.2(2)XB4a
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 and Resolved Caveats—Cisco IOS Release 12.2(2)XB1
Open Caveats—Cisco IOS Release 12.2(2)XB
Resolved Caveats—Cisco IOS Release 12.2(2)XB
Cisco IOS Software Documentation Set
Obtaining Technical Assistance
Release Notes for Cisco AS5300 Universal Access Servers for Cisco IOS Release 12.2(2)XB15
January 14, 2005
Cisco IOS Release 12.2(2)XB15
OL-1678-01 Rev. N2
These release notes for the Cisco AS5300 universal access servers 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.
Contents
These release notes describe the following topics:
• MIBs
• Caveats for Cisco IOS Release 12.2 XB
• Obtaining Technical Assistance
Introduction
The Cisco AS5300 is a versatile data communications platform that performs two functions in a single modular chassis, depending on the installed feature cards and IOS images:
•Remote Access Server
•Voice Gateway
The remote access server is intended for Internet service providers (ISPs), telecommunications carriers, and other service providers that offer managed Internet connections and medium to large sites that provide both digital and analog access to users on an enterprise network. By terminating both analog and digital calls on the same chassis simultaneously, the gateway provides a clear, simple, and easy migration path from analog dial access services to digital dial access services.
The Cisco AS5300 Voice Gateway is a versatile data communications platform that provides the functions of a gateway, router, and digital modem(s) in a single modular chassis. The Cisco AS5300 includes three feature card slots: one holds a T1/E1/PRI feature card, and the other two support modem feature cards or voice digital signal processor (DSP) feature cards. When equipped with modem cards, the Cisco AS5300 serves as a remote access concentrator for dial-up (modem or ISDN) Internet access. When equipped with voice feature cards and Voice IOS, the Cisco AS5300/Voice Gateway serves as a Voice over IP (VoIP) gateway. By using one slot for modems and the other for voice DSPs, the Cisco AS5300 can serve in both capacities. Modem, voice, or fax calls are routed to the appropriate cards/resources via Dialed Number Identification Service (DNIS).
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:
• Determining the Software Version
• Microcode and Modem Code Software
Memory Recommendations
Supported Hardware
Cisco IOS Release 12.2(2)XB15 supports the Cisco AS5300 universal access servers.
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, 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
Determining the Software Version
To determine the version of Cisco IOS software running on your Cisco AS5300 universal access servers, log in to the Cisco AS5300 universal access servers and enter the show version EXEC command:
Router> show version
Cisco Internetwork Operating System Software
IOS (tm) 12.2 XB Software (c5300-is-mz), Version 12.2(2)XB15, RELEASE SOFTWARE
Microcode and Modem Code Software
Microcode software images are bundled with the system software image. Bundling eliminates the need to store separate microcode images. When the router starts, the system software unpacks the microcode software bundle and loads the proper software on all the interface processor boards. To obtain the latest Cisco IOS software release compatible with Cisco MICA portware, refer to Cisco AS5x00 MICA 6-Port and 12-Port Modem Module Portware/Cisco IOS Software Compatibility Matrixes at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/sw_conf/sw_ports/compmat/mca12prt.htm
You could have received a later version of modem code than the one bundled with the Cisco IOS software. The modem code in Flash memory is mapped to the modems. Unless you fully understand how Cisco IOS software uses modem code, it is important to keep the factory configuration.
The modem code release notes are on Cisco.com and the Documentation CD-ROM:
On Cisco.com at:
Technical Documents: All Product Documentation: Access Servers and Access Routers: Firmware and Portware Information
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Firmware and Portware Information
Feature Set Tables
The Cisco IOS software is packaged in feature sets consisting of software images—depending on the platform. Each feature set contains a specific set of Cisco IOS features.
Cisco IOS Release 12.2(2)XB15 is based on the following releases:
•Cisco IOS Release 12.1(5)XM
•Cisco IOS Release 12.2(1)
•Cisco IOS Release 12.2(2)XA
All features in the above releases are in Cisco IOS Release 12.2(2)XB15. Their features are listed in the "Feature Set Tables" sections of the following release notes:
•Release Notes for Cisco AS5300 Universal Access Server for Cisco IOS Release 12.1 XM at http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/5300/rn5300xm.htm
•Cisco IOS Release 12.2 Cross-Platform Release Notes
Click Platform-Specific Information and Cisco AS5300 Universal Access Server at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122relnt/xprn122/index.htm
•Release Notes for Cisco AS5300 Universal Access Server for Cisco IOS Release 12.2 XA at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122relnt/5300/rn5300xa.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 and Table 4 list the features and feature sets supported by the Cisco AS5300 universal access servers in Cisco IOS Release 12.2(2)XB15 and uses the following conventions:
•Yes—The feature is supported in the software image.
•No—The feature is not supported in the software image.
•In—The number in the "In" column indicates the Cisco IOS release in which the feature was introduced.
Note These release notes are not cumulative and only 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.
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco AS5300 universal access servers for Cisco IOS Release 12.2(2)XB15.
New Hardware and Software Features in Cisco IOS Release 12.2(2)XB6 to Cisco IOS Release 12.2(2)XB15
No new hardware or software features are supported by the Cisco AS5300 universal access servers for Cisco IOS Release 12.2(2)XB6 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)XB5
No new hardware features are supported by the Cisco AS5300 universal access servers for Cisco IOS Release 12.2(2)XB5.
New Software Features in Cisco IOS Release 12.2(2)XB5
The following new software features are supported by the Cisco AS5300 universal access servers for Cisco IOS Release 12.2(2)XB5:
EAP RADIUS Support
The EAP RADIUS Support feature allows users to apply to the client authentication methods that may not be supported by the network access server; this is done via the Extensible Authentication Protocol (EAP). Before this feature was introduced, support for various authentication methods for PPP connections required custom vendor-specific work and changes to the client and NAS.
EAP is an authentication protocol for PPP that supports multiple authentication mechanisms that are negotiated during the authentication phase (instead of the link control protocol [LCP] phase). EAP allows a third-party authentication server to interact with a PPP implementation through a generic interface.
MS CHAP Version 2
The MS CHAP Version 2 feature in Cisco IOS Release 12.2(2)XB5 introduces the ability of Cisco routers to utilize Microsoft Challenge Handshake Authentication Protocol Version 2 (MSCHAP V2) authentication for PPP connections between a computer using a Microsoft Windows operating system and a network access server (NAS). MSCHAP V2 authentication is an updated version of MSCHAP that is similar to, but incompatible with MSCHAP. MSCHAP V2 introduces mutual authentication between peers and a change password feature.
New Hardware and Software Features from Cisco IOS Release 12.2(2)XB1 to Cisco IOS Release 12.2(2)XB4
No new hardware and software features are supported by the Cisco AS5300 universal access servers from Cisco IOS Release 12.2(2)XB1 to Cisco IOS Release 12.2(2)XB4.
New Hardware Features in Cisco IOS Release 12.2(2)XB
No new hardware features are supported by the Cisco AS5300 universal access servers for Cisco IOS Release 12.2(2)XB.
New Software Features in Cisco IOS Release 12.2(2)XB
The following new soft features are supported by the Cisco AS5300 universal access servers for Cisco IOS Release 12.2(2)XB:
Call Transfer Capabilities Using Refer
Call transfer allows a wide variety of decentralized multiparty call operations. These decentralized call operations form the basis for third-party call control, and thus are important features for Voice over IP (VoIP) and SIP. Call transfer is also critical for conference calling, where calls can transition smoothly between multiple point-to-point links and IP level multicasting.
Refer to the following document for further information:
Configurable PSTN Cause Code to SIP Response Mapping
For calls to be established between a SIP network and a PSTN network, the two networks must be able to interoperate. One aspect of their interoperation is the mapping of PSTN cause codes, which indicate reasons for PSTN call failure or completion, to SIP status codes or events. The opposite is also true: SIP status codes or events are mapped to PSTN cause codes. Event mapping tables found in this document show the standard or default mappings between SIP and PSTN.
However, you may want to customize the SIP user agent software to override the default mappings between the SIP and PSTN networks. The Configurable PSTN Cause Code to SIP Response Mapping feature allows you to configure specific map settings between the PSTN and SIP networks. Thus, any SIP status code can be mapped to any PSTN cause code, or vice versa. When set, these settings can be stored in the NVRAM and are restored automatically on bootup.
Refer to the following document for further information:
DTMF Relay using NTE
The SIP NTE DTMF relay feature is used for the following applications:
•Reliable DTMF Relay
•SIP Phone Support
Note The SIP NTE DTMF relay feature is implemented for SIP calls only on Cisco Voice-over-IP (VoIP) gateways.
Reliable DTMF Relay
The SIP NTE DTMF relay feature provides reliable digit relay between Cisco VoIP gateways when a low bandwidth codec is used. Using NTE to relay DTMF tones provides a standardized means of transporting DTMF tones in Real-Time Transport Protocol (RTP) packets according to section 3 of RFC 2833, RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals, developed by the Internet Engineering Task Force (IETF) Audio/Video Transport (AVT) working group. RFC 2833 defines formats of NTE RTP packets used to transport DTMF digits, hookflash, and other telephony events between two peer endpoints.
Note The SIP NTE DTMF relay feature does not support hookflash generation for advanced features such as call waiting and conferencing.
SIP Phone Support
The SIP NTE DTMF relay feature adds SIP phone support. When SIP IP phones are running software that does not have the capability to generate DTMF tones, the phones use NTE packets to indicate DTMF digits. With the SIP NTE DTMF relay feature, Cisco VoIP gateways can communicate with SIP phones that use NTE packets to indicate DTMF digits. The Cisco VoIP gateways can relay the digits to other endpoints.
Refer to the following document for further information:
Full Functionality 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
MGCP Based Fax (T.38) and DTMF (IETF RFC 2833) Relay
The MGCP Based Fax (T.38) and DTMF (IETF) Relay feature adds support for fax relay and DTMF relay with MGCP. The fax relay component conforms to ITU-T T.38, Procedures for real-time Group 3 facsimile communication over IP networks, which determines procedures for real-time facsimile communication in various gateway control protocol (XGCP) applications. The DTMF relay component conforms to RFC 2833, RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals, developed by the Internet Engineering Task Force (IETF) Audio/Video Transport (AVT) working group. Per RFC 2833, DTMF is relayed using Named Telephony Events (NTEs) in Real-Time Transport Protocol (RTP) packets.
This feature provides two modes of implementation for each component: gateway (GW)-controlled mode and call agent (CA)-controlled mode. In GW-controlled mode, GWs negotiate DTMF and fax relay transmission by exchanging capability information in Session Description Protocol (SDP) messages. That transmission is transparent to the CA. GW-controlled mode allows use of the MGCP Based Fax (T.38) and DTMF (IETF) Relay feature without upgrading the CA software to support the feature.
In CA-controlled mode, CAs use MGCP messaging to instruct GWs to process fax and DTMF traffic. For MGCP T.38 Fax Relay, the CAs can also instruct GWs to revert to GW-controlled mode if the CA is unable to handle the fax control messaging traffic; for example, in overloaded or congested networks.
Refer to the following document for further information:
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:
RFC2782 Compliance for DNS SRV
SIP on Cisco VoIP gateways uses Domain Name System Server (DNS SRV) query to determine the IP address of the user endpoint. The query string has a prefix in the form of "protocol.transport." and is attached to the fully qualified domain name (FQDN) of the next hop SIP server. This prefix style, from RFC 2052, has always been available; however, with this release, a second style is also available. The second style is in compliance with RFC 2782, and prepends the protocol label with an underscore "_"; as in "_protocol._transport.". The addition of the underscore reduces the risk of the same name being used for unrelated purposes. The form compliant with RFC 2782 is the default style.
Use the srv version command to configure the DNS SRV feature.
For further information, refer to the RFC2782 Compliance (Style of DNS SRV Queries) section at:
SIP Gateway Support for Bind Command
In previous releases of Cisco IOS software, the source address of a packet going out of the gateway was never deterministic. That is, the session protocols and VoIP layers always depended on the IP layer to give the best local address. The best local address was then used as the source address (the address showing where the SIP request came from) for signaling and media packets. Using this nondeterministic address occasionally caused confusion for firewall applications, as a firewall could not be configured with an exact address and would take action on several different source address packets.
However, the bind interface command allows you to configure the source IP address of signaling and media packets to a specific interface's IP address. Thus, the address that goes out on the packet is bound to the IP address of the interface specified with the bind command. Packets that are not destined to the bound address are discarded.
When you do not want to specify a bind address, or if the interface is down, the IP layer still provides the best local address.
Refer to the following document for further information:
SIP Gateway Support of RSVP and "tel" URL
The SIP Gateway Support of RSVP and TEL URL feature provides the following SIP enhancements:
•RSVP
•Telephone URL Format in SIP Messages
•Interaction with Forking Proxies
•SIP Hairpinning
•Reliability of SIP Provisional Responses
•Configurable Screening Indicator
•RFC2782 Compliance (Style of DNS SRV Queries)
RSVP
In previous Cisco IOS releases, SIP applications over IP networks functioned as best-effort services — their media packets were delivered with no performance guarantees. However, SIP Gateway Support of RSVP and TEL URL ensures quality of service (QoS) by coordinating SIP call signaling and RSVP resource management. This feature reserves sufficient network-layer resources to guarantee bandwidth and bounds on packet loss, delay, and jitter; thus ensuring that the called party's phone rings only after bandwidth required for the call has been successfully reserved.
Telephone URL Format in SIP Messages
The SIP Gateway Support of RSVP and TEL URL feature also supports Telephone Uniform Resource Locators or TEL URL. Currently SIP gateways support URLs in the SIP format. SIP URLs are used in SIP messages to indicate the originator, recipient, and destination of the SIP request. However, SIP gateways may also encounter URLs in other formats, such as TEL URLs. TEL URLs describe voice call connections. They also enable the gateway to accept TEL calls sent through the Internet, and to generate TEL URLs in the request line of outgoing INVITEs requests.
Interaction with Forking Proxies
Support for call forking enables the terminating gateway to handle multiple requests and the originating gateway to handle multiple provisional responses for the same call. Interaction with forking proxies applies to gateways acting as a user agent client (UAC), and takes place when a user is registered to several different locations. When the UAC sends an INVITE message to a proxy, the proxy forks the request and sends it to multiple user agents (UAs). The SIP gateway processes multiple 18X responses by treating them as independent transactions under the same call ID. When the relevant dial peers are configured for QoS, the gateway maintains state and initiates RSVP reservations for each of these independent transactions. When it receives an acknowledgment, such as a 200 OK, the gateway accepts the successful acknowledgment and destroys state for all other transactions.
The forking functionality sets up RSVP for each transaction only if the dial peers are configured for QoS. If not, the calls proceed as best-effort.
SIP Hairpinning
SIP hairpinning is a call routing capability in which an incoming call on a specific gateway is signaled through the IP network and back out the same gateway. This can be a public switched telephone network (PSTN) call routed into the IP network and back out to the PSTN over the same gateway. Similarly, SIP hairpinning can be a call signaled from a line (for example, a telephone line) to the IP network and back out to a line on the same access gateway. With SIP hairpinning, unique gateways for ingress and egress are no longer necessary.
Reliability of SIP Provisional Responses
SIP reliable provisional responses ensure that media information is exchanged and resource reservation can take place prior to connecting the call. Provisional acknowledgement (PRACK) and conditions met (COMET) are two methods that have been implemented.
PRACK allows reliable exchanges of SIP provisional responses between SIP endpoints. COMET indicates if the pre-conditions for a given call or session have been met.
Configurable Screening Indicator
Screening Indicator (SI) is a signaling-related information element found in octet 3a of the ISDN SETUP message that can be used as an authorization mechanism for incoming calls. Enhancements have been made to the Tool Command Language (TCL) Interactive Voice Response (IVR) 2.0 command set that allow SIP terminating gateways to assign a specific value to the screening indicator through the use of TCL scripts.
RFC2782 Compliance (Style of DNS SRV Queries)
SIP on Cisco VoIP gateways uses Domain Name System Server (DNS SRV) query to determine the IP address of the user endpoint. The query string has a prefix in the form of "protocol.transport." and is attached to the fully qualified domain name (FQDN) of the next hop SIP server. This prefix style, from RFC 2052, has always been available; however, with this release, a second style is also available. The second style is in compliance with RFC 2782, and prepends the protocol label with an underscore "_"; as in "_protocol._transport." The addition of the underscore reduces the risk of the same name being used for unrelated purposes. The form compliant with RFC 2782 is the default style.
Refer to the following document for further information:
SIP INVITE Request with Malformed Via Header
A SIP INVITE requests that a user or service participate in a session. Each INVITE contains a Via header that indicates the transport path taken by the request so far, and where to send a response.
In the past, when an INVITE contained a malformed Via header, the gateway would print a debug message and discard the INVITE without incrementing a counter. However, the printed debug message was often inadequate, and it was difficult to detect that messages were being discarded.
The SIP INVITE Request with Malformed Via Header feature provides a response to the malformed request. A counter, Client Error: Bad Request, increments when a response is sent for a malformed Via field. Bad Request is a class 400 response and includes the explanation Malformed Via Field. The response is sent to the source IP address (the IP address where the SIP request originated) at User Datagram Protocol (UDP) port 5060.
Note This feature applies to messages arriving on UDP, because the Via header is not used to respond to messages arriving on TCP.
Refer to the following document for further information:
SIP T.37 and Cisco Fax
SIP T.37 is an ITU specification that enables store and forward fax applications, as well as toggling from voice to fax, for example, providing an IVR front-end to a fax store and forward application.
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dtfaxrly.htm
SIP T.38 Fax Relay
The SIP T.38 Fax Relay feature adds standards-based fax support to SIP and conforms to ITU-T T.38, Procedures for real-time Group 3 facsimile communication over IP networks. The ITU-T standard specifies real-time transmission of faxes between two regular fax terminals over an IP network.
Refer to the following document for further information:
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 Cisco MICA portware 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 Cisco MICA portware 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:
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:
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:
MIBs
Current 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:
Deprecated and Replacement MIBs
Old Cisco MIBs will be replaced in a future release. Currently, OLD-CISCO-* MIBs are being converted into more scalable MIBs without affecting existing Cisco IOS products or network management system (NMS) applications. You can update from deprecated MIBs to the replacement MIBs as shown in Table 5.
Important Notes
The following sections contain important notes about Cisco IOS Release 12.2 XB that can apply to the Cisco AS5300 universal access servers.
VCWare Compatibility
Cisco IOS Release 12.2(2)XB supports VCWare Version 9.15 for the Cisco AS5300 universal Access server.
H.323 and SIP Coexistence
Cisco IOS Software Release 12.2(2)XB provides support for session initiation protocol (SIP) and H.323 coexistence on the Cisco IOS gateway. SIP and H.323 coexistence is supported for the Cisco AS5300 and Cisco AS5350 platforms. The following H.323, SIP, and other features function simultaneously on the Cisco IOS gateway.
H.323 Features
•Cisco SS7 Interconnect for Voice Gateways Solution features
•Netspeak interoperability (Internet call waiting)
•PC-to-phone interoperability (Click to dial)
•Netspeak Cleartoken object ID (OID)
•Q.SIG
•Call deflection (H.450.3)
•Call transfer (H.450.2)
•H.235 call security
•Dual Tone Multi-Frequency (DTMF) tunneling
•Public Switched Telephone Network (PSTN) fallback based on Voice Over IP (VoIP) network congestion
•Call admission control; programmable call treatment
•T.38 fax relay and fax relay reliability
•Time division multiplex (TDM) hairpinning
•Programmable interactive voice response (IVR)
•Rotary dial peers
•Alternate gatekeeper support on the gateway
•Multiple redirecting numbers (RDNs)
•IP address bind
•New resource availability indication (RAI) algorithm
•Frame size negotiation
•Codec negotiation and support
SIP Features
•SIP via user datagram protocol (UDP)
•Primary rate interface (PRI)
•Call transfer
•Call hold
•UDP connected socket
•Privacy indicator
•Mapping PRI within 180/183 SIP messaging
•Call control redirect/diversion
•Domain name server (DNS)
•Codec negotiation and support
Other Features
•Call history
•Quality of Service: IP precedence and Priority Queue Weighted Fair Queuing (PQWFQ)
•AAA/RADIUS server
•Network side PRI for 5ESS, DMS100, NI2, and NET5 switch types
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)XM, Cisco IOS Release 12.2(2)XA and Cisco IOS Release 12.2(1) are also in Cisco IOS Release 12.2(2)XB15.
For information on caveats in Cisco IOS Release 12.1(5)XM, see the "Caveats" section in the Release Notes for Cisco AS5300 Universal Access Server for Cisco IOS Release 12.1 XM at http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/5300/rn5300xm.htm.
For information on caveats in Cisco IOS Release 12.2(2)XA, see the "Caveats" section in the Release Notes for Cisco AS5300 Universal Access Server for Cisco IOS Release 12.2 XA at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122relnt/5300/rn5300xa.htm.
For information on caveats in Cisco IOS Release 12.2(1), see Caveats for Cisco IOS Release 12.1, which lists severity 1 and 2 caveats and select severity 3 caveats and is located on Cisco.com and the Documentation CD-ROM.
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)XB15 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 6 Resolved Caveats for Cisco IOS Release 12.2(2)XB15
DDTS ID Number DescriptionCSCec87533
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 7 Resolved Caveats for Cisco IOS Release 12.2(2)XB8
DDTS ID Number DescriptionCSCdx76632
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.
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.
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 9 Resolved Caveats for Cisco IOS Release 12.2(2)XB12
DDTS ID Number DescriptionCSCdp42990
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 dialin 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 behaviour 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 dialstring 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 couner may not be incremented per port when the module is recovered by using maintenance action.
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 recieved by the PPP Windows DUN client.
Conditions: LCP negotiation takes a longer time.
Workaround: Make all connection into the NAS dedicated by configuring async mode dedicated 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.
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 11 Resolved Caveats for Cisco IOS Release 12.2(2)XB11
DDTS ID Number DescriptionCSCdt58342
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 logs in to a Cisco 3620 router by 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 Media Gateway Contol Protocol (MGCP ) piggybacking is turned off and when the gateway is attempting to send an command at the same time as it is sending an acknowlegement 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.
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".
CSCdw69092
5400 crashes at CCPMSG_RejectMsg after SC2200 failover
Symptom: Supercell Testing in Cisco IOS Release 12.2(2)XU on a Cisco AS5400 involved doing a switchover test on the SC2200 by killing one of the UNIX processes. This caused one of the Cisco AS5400 servers to crash. The server was processing approximately 5cps with approximately 200 active calls (all egress) at the time.
Workaround: Do not manually kill the process on the supercell, use MML instead.
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.
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: Betweenthe 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.
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 extende 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 Cisco 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 sem- 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 AS58500 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.
CSCdz52059
cmIncomingConnectionFailures are not correct on 5350
Symptom: cmIncomingConnectionFailures from cmLineStatisticsTable of CISCO-MODEM-MGMT-MIB sometimes decrease on the Cisco AS5350 access server.
Workaround: There is no workaround.
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 send 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.
CSCdz58910
CT3-DFC does not provide ATT TR 54016 performance data
Symptom: The internal DSU for a T1 in a Cisco AS5400 access server's CT3-DFC may fail to provide performance data when queried through ATT FDL (per ATT document TR 54016.)
Workaround: Monitor through SNMP instead of ATT FDL.
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.
CSCdz69604
5400 E1/R2 is not sending answer signal group A
Symptom: Calls may be dropped after 10 seconds because a Cisco AS5400 does not answer.
Conditions: This symptom is observed when a Cisco AS5400 does not send answer signal A6 for incoming calls. Outgoing calls work fine. The symptom may also occur on other platforms.
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.
CSCdz73060
kSmall buffer leak at mica_generate_digits
A Cisco AS5300 running Cisco IOS Release 12.2(2)XB8 may experience I/O memory allocation failures that cause the router to freeze and stop passing traffic.
Workaround: A reboot is required to restore memory.
CSCdz85925
PPP Async interfaces not updated in routing table
Symptom: Non-Multilink PPP (non-MLP) asynchronous users may not get a connected route in the IP routing table.
Conditions: This symptom is observed with non-MLP asynchronous users that are on an asynchronous interface that was previously used for MLP.
Workaround: Configure the router to use virtual profiles by entering the following sequence of commands:
Router(config)# interface virtual-template 1
Router(config)# virtual-profile virtual-template 1
Router(config)# no virtual-profile if-needed
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
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
CSCea49565
no ip pool download via AAA for terminal login call
Download of IP pools is not initiated for terminal login async PPP call in test image. Download works correctly in Cisco IOS Release 12.2(2)XB10.
Workaround: There is no workaround.
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 (ie. per-user dns/wins) causes authorization to fail.
Workaround: There is no workaround.
CSCea54013
Two simultaneous boardware downloads cause bus error exception
If the copy system:/ucode/mica_board_firmware modem command is executed on a Cisco AS5300 series Access Server before a previous boardware download has completed, the system may reload unexpectedly with a Bus Error Exception.
Workaround: Before attempting a boardware download, make sure that any previous boardware download attempts have been completed.
CSCea61814
bearer capability changed for outgoing hairpinned call
Symptom: The bearer capability is changed for outgoing hairpinned call.
Workaround: There is no workaround.
CSCea66514
Assertion Failure on PRI Layer2 Up in 12.2XB
Symptom: Assertion failure seen when the T1 controllers configured for ESF are commanded for shut and no shut on the remote end.
Conditions: T1 controllers configured for ESF.
Workaround: On the controllers where the Assertions failures are seen, enter the commands fdl ansi followed by no fdl ansi.
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.
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.
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.
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.
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.
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.
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.
Open Caveats—Cisco IOS Release 12.2(2)XB5
This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB5 and describes only severity 1 and 2 caveats and select severity 3 caveats.
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.
Open Caveats—Cisco IOS Release 12.2(2)XB4a
There are no open caveats specific to Cisco IOS Release 12.2(2)XB4a that require documentation in the release notes.
Resolved Caveats—Cisco IOS Release 12.2(2)XB4a
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(2)XB4a. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
.
Open Caveats—Cisco IOS Release 12.2(2)XB4
This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB4 and describes only severity 1 and 2 caveats and select severity 3 caveats.
.
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.
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 24 Resolved Caveats for Cisco IOS Release 12.2(2)XB3
DDTS ID Number DescriptionCSCdw65903
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
This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB2 and describes only severity 1 and 2 caveats and select severity 3 caveats.
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.
Open and Resolved Caveats—Cisco IOS Release 12.2(2)XB1
Cisco IOS Release 12.2(2)XB1 does not support the Cisco AS5300 universal access servers.
Open Caveats—Cisco IOS Release 12.2(2)XB
This section documents possible unexpected behavior by Cisco IOS Release 12.2(2)XB and describes only severity 1 and 2 caveats and select severity 3 caveats.
Resolved Caveats—Cisco IOS Release 12.2(2)XB
There are no resolved caveats specific to Cisco IOS Release 12.2(2)XB that require documentation in the release notes.
Related Documentation
The following sections describe the documentation available for the Cisco AS5300 universal access servers. These documents consist of hardware and software installation guides, Cisco IOS configuration guides and command references, system error messages, feature modules, and other documents.
Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online on Cisco.com and the Documentation CD-ROM.
Use these release notes with these documents:
• Cisco IOS Software Documentation Set
Release-Specific Documents
The following documents are specific to Cisco IOS Release 12.2 and are located on Cisco.com and the Documentation CD-ROM:
•Cross-Platform Release Notes for Cisco IOS Release 12.2
On Cisco.com at:
Cisco Product Documentation: Cisco IOS Software: Cisco IOS Release 12.2: Release Notes: Cross-Platform Release Notes
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2: Release Notes: Cross-Platform Release Notes
•Product bulletins, field notices, and other release-specific documents on Cisco.com at:
Technical Documents
•The "Caveats for Cisco IOS Release 12.2 XB" section
As a supplement to the caveats listed in "Caveats for Cisco IOS Release 12.2 XB" in these release notes, see Caveats for Cisco IOS Release 12.2, which contains caveats applicable to all platforms for all maintenance releases of Cisco IOS Release 12.2.
On Cisco.com at:
Cisco Product Documentation: Cisco IOS Software: Cisco IOS Release 12.2: Release Notes: Caveats
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2: Caveats
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.
Platform-Specific Documents
These documents are available for the Cisco AS5300 universal access servers on Cisco.com and the Documentation CD-ROM:
•Quick Start Guide Cisco AS5300 Universal Gateway Install and Configure
•Hardware installation documents for Cisco AS5300
•Configuration documents for Cisco AS5300
•Regulatory Compliance and Safety Information
On Cisco.com at:
Cisco Product Documentation: Cisco Product Documentation: Access Servers and Access Routers: Access Servers: Cisco AS5300
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Access Servers: Cisco AS5300
Feature Modules
Feature modules describe new features supported by Cisco IOS Release 12.2(2)XB15 and are updates to the Cisco IOS documentation set. A feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference. As updates, the feature modules are available online only. Feature module information is incorporated in the next printing of the Cisco IOS documentation set.
On Cisco.com at:
Cisco Product Documentation: Cisco IOS Software: Cisco IOS Release 12.2: New Feature Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2: New Feature Documentation
Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, 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:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
http://www.cisco.com/cgi-bin/Support/FeatureNav/FN.pl
Cisco IOS Software Documentation Set
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents. The Cisco IOS software documentation set is shipped with your order in electronic form on the Documentation CD-ROM—unless you specifically ordered the printed versions.
Documentation Modules
Each module in the Cisco IOS documentation set consists of one or more configuration guides and one or more corresponding command references. Chapters in a configuration guide describe protocols, configuration tasks, and Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide with its corresponding command reference.
On Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.2: Configuration Guides and Command References
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2: Configuration Guides and Command References
Cisco IOS Release 12.2 Documentation Set Contents
Table 28 lists the contents of the Cisco IOS Release 12.2 software documentation set, which is available in electronic form and in printed form if ordered.
Note You can find the most current Cisco IOS documentation on Cisco.com and the Documentation CD-ROM.
On Cisco.com at:
Cisco Product Documention: Cisco IOS Software: Cisco IOS Release 12.2
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2
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:
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-9883We 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:
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:
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.
Posted: Fri Jan 14 20:04:46 PST 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.