Table Of Contents
Resolved Caveats—Cisco IOS Release 12.2(11)T11
Resolved Caveats—Cisco IOS Release 12.2(11)T10
Resolved Caveats—Cisco IOS Release 12.2(11)T9
Resolved Caveats—Cisco IOS Release 12.2(11)T8
Resolved Caveats—Cisco IOS Release 12.2(11)T6
Resolved Caveats—Cisco IOS Release 12.2(11)T5
Resolved Caveats—Cisco IOS Release 12.2(11)T4
Resolved Caveats—Cisco IOS Release 12.2(11)T3
Resolved Caveats—Cisco IOS Release 12.2(11)T2
Resolved Caveats—Cisco IOS Release 12.2(11)T1
Resolved Caveats—Cisco IOS Release 12.2(11)T
Resolved Caveats—Cisco IOS Release 12.2(8)T10
Resolved Caveats—Cisco IOS Release 12.2(8)T8
Resolved Caveats—Cisco IOS Release 12.2(8)T7
Resolved Caveats—Cisco IOS Release 12.2(8)T5
Resolved Caveats—Cisco IOS Release 12.2(8)T4
Resolved Caveats—Cisco IOS Release 12.2(8)T3
Resolved Caveats—Cisco IOS Release 12.2(8)T2
Resolved Caveats—Cisco IOS Release 12.2(8)T1
Resolved Caveats—Cisco IOS Release 12.2(8)T
Resolved Caveats—Cisco IOS Release 12.2(4)T7
Resolved Caveats—Cisco IOS Release 12.2(4)T6
Resolved Caveats—Cisco IOS Release 12.2(4)T5
Resolved Caveats—Cisco IOS Release 12.2(4)T3
Resolved Caveats—Cisco IOS Release 12.2(4)T1
Resolved Caveats—Cisco IOS Release 12.2(4)T
Resolved Caveats—Cisco IOS Release 12.2(2)T4
Resolved Caveats—Cisco IOS Release 12.2(2)T3
Resolved Caveats—Cisco IOS Release 12.2(2)T2
Resolved Caveats—Cisco IOS Release 12.2(2)T1
Resolved Caveats—Cisco IOS Release 12.2(2)T
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Resolved Caveats—Cisco IOS Release 12.2(11)T11
Cisco IOS Release 12.2(11)T11 is a rebuild of Cisco IOS Release 12.2(11)T. The caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T11 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
Symptoms: A description of what is observed when the caveat occurs.
Conditions: The conditions under which the caveat has been known to occur.
Workaround: Solutions, if available, to counteract the caveat.
•
CSCdz84583
A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.
All Cisco products which contain TCP stack are susceptible to this vulnerability.
This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software.
A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml.
•
A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.
All Cisco products which contain TCP stack are susceptible to this vulnerability.
This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software.
A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml.
•
Symptoms: A router may reload unexpectedly after it attempts to access a low memory address.
Conditions: This symptom is observed after ACLs have been updated dynamically or after the router has responded dynamically to an IDS signature.
Workaround: Disable IP Inspect and IDS.
•
A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.
All Cisco products which contain TCP stack are susceptible to this vulnerability.
This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software.
A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml.
•
A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.
All Cisco products which contain TCP stack are susceptible to this vulnerability.
This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software.
A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml.
Resolved Caveats—Cisco IOS Release 12.2(11)T10
Cisco IOS Release 12.2(11)T10 is a rebuild of Cisco IOS Release 12.2(11)T. The caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T10 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
•
•
•
Basic System Services
•
Symptoms: A router may indicate a watchdog timeout instead of a parity error.
Conditions: This symptom is observed on routers that have a different memory map compared to the Cisco 7200 router. In the case reported for a Cisco 12000 series Internet router, KuSeg addresses start at 0x50000000 instead of 0x60000000, which is where they start for a Cisco 7200 router.
Workaround: There is no workaround.
•
Symptoms: The cache error recover function (CERF) is disabled after a Cisco 7200 series router is reloaded. This symptom is observed after CERF is enabled, written into the startup configuration, and the router is reloaded.
The output of the show memory cache error-recovery EXEC command may indicate that the commands are disabled after the router is reloaded:
no memory cache error-recovery L3 data
no memory cache error-recovery options nvram-report
no memory cache error-recovery options parity-check
memory cache error-recovery options window 0
memory cache error-recovery options max-recoveries 0Conditions: This symptom is observed on a Cisco 7200 series router that is using a Network Processing Engine (NPE-300) that has 32 MB of memory in the dual in-line memory module (DIMM2).
Workaround: Install 64 MB of memory in the DIMM2.
•
Symptoms: A Cisco 7500 series router may reload because of a software condition after an online insertion and removal (OIR) of a Versatile Interface Processor (VIP) that is configured with an ATM OC-3c/STM-1 port adapter (PA-A3- OC3) and after the following error message has been generated:
%SYS-6-STACKLOW: Stack for process OIR Handler running low, 12/3000Conditions: This symptom is observed on a Cisco 7500 series router that is running Cisco IOS Release 12.2(7) and occurs with a VIP2-50, VIP4, and VIP6. The symptom is related to the PA-A3-OC3 and occurs only during an OIR.
Workaround: Do not perform an OIR on any VIP that is configured with a PA-A3- OC3.
Miscellaneous
•
Symptoms: The "speed 57600" configuration entry may be added to the line configuration on a router.
Conditions: This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(5e).
Workaround: Remove the configuration entry from the line configuration.
•
Symptoms: H.323 disconnect cause codes are incorrect. Debug output displays codes of "211" instead of "11."
Conditions: This symptom is observed if the location in the cause information element (CAUSE_IE) is anything other than "USER."
Workaround: There is no workaround.
•
Symptoms: A Cisco AS5400 may reload unexpectedly and a high rate of Processor Memory Parity Errors (PMPE) may occur.
Conditions: This symptom is observed on a Cisco AS5400 that runs any Cisco IOS release.
Workaround: There is no workaround.
•
Symptoms: Two routers that are connected via serial interfaces may reload unexpectedly. The following message may be displayed when the show version EXEC command is entered:
System was restarted by bus error at PC 0x6103B948, address 0xFFFFFFFCConditions: This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(15)T.
Workaround: There is no workaround.
•
Symptoms: When the integrated Signaling Link Terminal (SLT) functionality is running on a Cisco AS5350 or Cisco AS5400, the Signaling System 7 (SS7) links will not come into service. Using an SS7 analyzer indicates that Link Status Signal Units (LSSUs) are not being transmitted from the Cisco AS5350 or Cisco AS5400 to the SS7 network.
Conditions: This symptom is observed when the Cisco AS5350 or Cisco AS5400 is configured with a 2-, 4-, or 8-port PRI board that contains the D4 version of an MPC860 processor. You can verify the version of the MPC860 processor by entering the show chassis slot detail EXEC command. The symptom occurs when the board hardware version is version 4.0 or a later version.
Workaround: Install a PRI board with a board hardware version earlier than 4.0.
•
Symptoms: A Cisco IAD2420 series may not collect digits properly. One number 2 may become two number 4s in the dialed digits that are detected by a voice telephony service provider (VTSP).
Conditions: This symptom is observed on a Cisco IAD2420 series that is interconnected via a digital interface to a BTS10200 softswitch that runs software release 3.5.1v01. When the Cisco IAD2420 series is rebooted and sends Restart in Progress (RSIP) messages to the call agent (CA), the trunks are automatically brought back into service. The symptom occurs when a PBX goes off-hook, then on-hook (without dialing digits), then off-hook again on the same channel, and then begins dialing.
Workaround: There is no workaround.
•
Symptoms: The Media Gateway Control Protocol (MGCP) is too slow in acknowledging the delete connection (DLCX) parameter on a Cisco AS5400. The output of the show mgcp stat EXEC command indicates that the CreateConn rx counter is increasing.
Conditions: This symptom is observed when a DLCX is received on a Cisco AS5400 under a heavy call volume with calls on different slots but on the same port number and DS0 number.
Workaround: There is no workaround. The symptom will clear when the call volume decreases.
•
Symptoms: No audio may be heard on a Voice over IP (VoIP) call from the public switched telephone network (PSTN) to an H.323 application of a third-party vendor.
Conditions: This symptom is observed on a Cisco AS5350 that runs Cisco IOS Release 12.2(11)T9. The symptom may also occur in other releases.
The symptom occurs because no Real-Time Transport Protocol (RTP) stream is created on the Cisco AS5350 when the RTP sequence number is altered by the H.323 application of the third-party vendor during a previous call. Once the RTP sequence number has been altered, all subsequent calls fail.
Workaround: To enable the Cisco AS5350 to process a single call properly, reboot the Cisco AS5350. However, once the RTP sequence number has been altered, all subsequent calls fail.
•
Symptoms: A Media Gateway Control Protocol (MGCP) gateway may send Restart In Progress (RSIP) messages with a very low delay to a call agent (CA), and with a low delay between the RSIP messages. The delay may be much less than one second, which is the minimum value that is permitted by the MGCP standard. The resulting flood of RSIP messages may cause the CA to overload, and may prevent the overloaded CA from recovering.
Conditions: These symptoms are observed on a Cisco AS5400 that has not received a timely acknowledgement (ACK) response to a delete connection (DLCX) message that the Cisco AS5400 sent to the call agent (CA); an overloaded CA may send highly delayed responses.
Workaround: There is no workaround.
•
Symptoms: When a Cisco router boots up, the following messages appear and the router is unusable:
Process= "MIPC Periodic Timer", ipl= 0, pid= 32
%PIF-3-READ_IMEM_ERROR: NULL response for READ_IMEM MIPC msg to, XPIF2 Process= "FDM Forwarding Stats Process", ipl= 0, pid= 35
%PIF-3-READ_PHY_ERROR: NULL response for PIF_PHY_REG_SEND_CMD MIPC msg to, XPIF2Conditions: This symptom is observed on a Cisco AS5850 gateway that has a Route Switch Controller (RSC) card with revision 8.9 or later, and that is running Cisco IOS Release 12.2(11)T4, Release 12.2(11)T9, Release 12.3(1), Release 12.3(1a), or Release 12.3(3a).
Workaround: Load a working Cisco AS5850 image of Cisco IOS software (images other than those listed in the Conditions section) and then reload the gateway with the newer image of the software without turning off power and turning on power to the router.
•
Symptoms: An IP route may not be properly downloaded, preventing the IP route from being installed on a network access server (NAS).
Conditions: This symptom is observed on a NAS that is configured for RADIUS authorization when the user profile contains IP routes that include interface information, as shown in the following example of a Framed Route:
x.x.x.x/32 Dialer1 200 name dialout2Workaround: Use IP routes that include a gateway address, as shown in the following example of a Framed Route:
1.1.1.0/24 1.1.1.254 200•
Symptoms: A Cisco AS5400 may reload unexpectedly while running Media Gateway Control Protocol (MGCP) in normal mode of operation.
Conditions: This symptom is observed on a Cisco AS5400 that runs Cisco IOS Release 12.2(11)T8 and occurs because of incorrect memory management.
Workaround: There is no workaround.
•
Symptoms: A router may pause indefinitely or reload unexpectedly when modem relay calls are made.
Conditions: This symptom is observed on a Cisco 3600 series that is running Cisco IOS Release 12.2(11)T9 or Release 12.3(13)T9.
Workaround: There is no workaround.
Wide-Area Networking
•
Symptoms: An asynchronous dialer interface may not come up as expected.
Conditions: This symptom is observed when a service policy is attached to an asynchronous dialer interface.
Workaround: Use a dialer rotary configuration instead of a dialer profile configuration for the service policy on the dialer interface.
Resolved Caveats—Cisco IOS Release 12.2(11)T9
Cisco IOS Release 12.2(11)T9 is a rebuild of Cisco IOS Release 12.2(11)T. The caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T9 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
•
•
•
Miscellaneous
•
A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, please refer to this advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
•
Symptoms: A Cisco AS5300 that is functioning as a voice gateway may reload because of an incoming bus error exception.
Conditions: This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(6d).
Workaround: There is no workaround.
•
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.
•
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
•
Symptoms: A Real-Time Transport Control Protocol (RTCP) packet may cause an input queue wedge on a Cisco voice gateway.
Conditions: This symptom is observed on a Cisco router that functions as a voice gateway and that is configured as an originating, terminating, or IP to IP (IPIP) gateway.
Workaround: There is no workaround.
•
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
•
Symptoms: Memory corruption may cause a router to reload.
Conditions: This symptom is observed on a Cisco 3600 series that is handling Voice over IP (VoIP) T.38 fax calls under load conditions.
Workaround: There is no workaround.
•
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.
•
Symptoms: A Cisco IAD2420 series that is processing calls may reload.
Conditions: This symptom is observed on a Cisco IAD2420 series when the voice local-bypass global configuration command is configured.
Workaround: There is no workaround.
•
Symptoms: Entries in the tag forwarding table may disappear from a provider edge (PE) router.
Conditions: This symptom may be observed on a Cisco 7200 series or Cisco 7513 router that is running Cisco IOS Release 12.2(11)T2 or Release 12.2(15)T3 in a Multiprotocol Label Switching (MPLS) over ATM environment with the multi- virtual circuit (Multi-VC) feature turned on. The label protocol is Label Distribution Protocol (LDP.)
Workaround: Use the clear ip route prefix EXEC command. This command must be entered on each PE that has this symptom. The prefix to be used in the command is the loopback address of the remote PE.
•
Symptoms: A digital signal processor (DSP) may time out on a Cisco IAD2420 series because of a Host Port Interface (HPI) error.
Conditions: This symptom is observed on a Cisco IAD2420 series that is running Cisco IOS Release 12.2(11)T4 every time a call is placed or received.
Workaround: Use the command-line interface (CLI) to issue the following command to the DSPs that have a timeout symptom:
[no] voice dsp waitstate ws dsp_id
where ws is in the range of 1 to 3 with 1 being the default and dsp_id is a 1-based DSP number. The recommended ws value to set in this particular case is 2. Do not set the ws value higher than 2. The issuance of the CLI command will not take effect until the next DSP reset occurs either through an automatic mechanism or through test commands.
•
A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, please refer to this advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
•
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.
•
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.
•
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.
•
Symptoms: Two Cisco routers that are running Cisco fax relay over a Voice over IP (VoIP) connection may reload after approximately 8 hours of operation.
Conditions: This symptom is observed in a test using a Cisco 3640 router and a Cisco 3660 router, although the symptom may be platform independent.
Workaround: There is no workaround.
•
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.
•
Symptoms: On a Media Gateway Control Protocol (MGCP) gateway, when a T1 controller or the serial interface that is bound to an ISDN User Adaptation (IUA) Application Server (AS) is disabled (via a shutdown command or because of an error condition), the call agent may not be aware that the T1 controller is disabled and may still attempt to set up calls on the T1 link.
When the T1 controller or the serial interface is disabled, the MGCP gateway sends a release indication message for the corresponding D channel to the call agent. However, the "Reason" field is lacking from this message, preventing the call agent from recognizing the message as a release indication message and from marking the interface as disabled.
Conditions: This symptom is observed on a Cisco platform that is functioning as an MGCP gateway, that is configured for IUA backhaul, and that is running Cisco IOS Release 12.2(11)T or Release 12.2(13)T.
Workaround: There is no workaround.
•
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.
•
Symptoms: A Cisco gateway stops responding to delete connection (DLCX) messages from the call agent when T.38 fax calls are sent.
Conditions: This symptom is observed on a Cisco AS5850.
Workaround: There is no workaround. Most call agents should allow the timeout value to be configured. This timeout value may need to be as high as 5.5 seconds. If the call agent is also configured to retransmit unacknowledged messages, such as DLCX, the total time before the message times out needs to be at least 5.5 seconds. For example, three retries with two seconds between each retry would be sufficient.
•
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.
•
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.
•
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.
•
Symptoms: A call may be rejected on the plain old telephone service (POTS) leg with cause code "0x2F" that indicates that there is no resource for the call.
Conditions: This symptom is observed on a Cisco AS5300 that is functioning as a terminating gateway when the call reaches the "progress/alerting" stage and the Cisco AS5300 has no available time-division multiplexing (TDM) resource to connect the call to the digital signal processor (DSP), which can be verified in the output of the show tdm pool privileged EXEC command:
Dynamic Backplane Timeslot Pool:
Req
------------------------
Grp ST Ttl/Free Cur/Ttl/Fail Deallocated
0 0-3 120 0 120 27726 3745 0
1 4-7 0 0 0 0 0 0The output of the show isdn active user EXEC command displays how many active calls there are. There should be one TDM resource in use for every active call. If the total number of TDM resources minus the total number of active calls does not indicate the correct number of available TDM resources, a TDM resource leak has occurred.
Workaround: Reload the Cisco AS5300.
•
Symptoms: The Session Definition Protocol (SDP)/Media Gateway Control Protocol (MGCP) parser may not function properly while parsing local parameters "red" and "siren."
Conditions: This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(11)T or Release 12.2(13)T when an MGCP create connection (CRCX) message is sent with a local parameter setting "red" and "siren."
Workaround: There is no workaround. Note that the symptom does not occur in Release 12.2(15)T.
•
Symptoms: A Cisco IAD2420 series may not generate a crashinfo file and store in it the Flash disk.
Conditions: This symptom is observed when the Cisco IAD2420 series reloads unexpectedly.
Workaround: There is no workaround.
•
Symptoms: A memory leak in the "MGCP Application" process may occur on a Cisco router.
Conditions: This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(11)T6 and that is configured for Media Gateway Control Protocol (MGCP) when the call agent signals the Visual Message Waiting Indicator (VMWI).
Workaround: If possible, configure the call agent not to use VMWI.
•
Symptoms: After a "%VTSP-3-DSP_TIMEOUT" error message is generated, the affected digital signal processor (DSP) may not automatically recover.
Conditions: This symptom is observed on a Cisco IAD2420 series, but may not be platform specific.
Workaround: There is no workaround. To recover the affected DSP, reload the router.
•
Symptoms: Calls from a Cisco S5850 may be rejected by a Cisco Resource Policy Management System (RPMS) with following error message:
Msg:Error: Inconsistent session detected. No Active Call with Call-Id:Conditions: This symptom is observed when a Cisco AS5850 is configured for preauthentication and Virtual Private Dialup Network (VPDN) forwarding.
Debugging the failed call on the Cisco AS5850 indicates that no unique ID was used when the "access accept" for the preauthentication request was received.
Workaround: There is no workaround.
•
Symptoms: On a Cisco AS5300, restart in progress (RSIP) messages may be sent only to the first address in a host list. When this first address does not respond, the Cisco AS5300 reattempts to access this first address but does not move on to subsequent addresses. This situation prevents the call agent from being aware of conditions that are present on the Cisco AS5300, such as an E1 failure.
Conditions: This symptom is observed only when the Cisco AS5300 is running Cisco IOS Release 12.2(11)T8, is functioning as a gateway, and is configured for multiple call agent addresses.
Workaround: Ensure that a call agent is active at the first address in the list.
•
Symptoms: A Cisco IAD2420 series may reload when it is processing calls.
Conditions: This symptom is observed when an analog port receives two incoming calls simultaneously.
Workaround: There is no workaround.
•
Symptoms: A Cisco gateway does not send open logical channel (OLC) messages to the Cisco H.323 Signaling Interface (HSI) for tunneled H.245 calls.
Conditions: This symptom is observed in a test situation on a Cisco 3640 that is running Cisco IOS Release 12.2(11)T8 and that has H.245 enabled.
Workaround: There is no workaround.
•
Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–
–
–
–
–
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
•
Symptoms: Under a heavy call load, a Foreign Exchange Station (FXS) port fails to return to the DORMANT state.
Conditions: This symptom is observed on a Cisco IAD2420 series, Cisco 2600 series, and a Cisco 3600 series when a call setup fails. The FXS port is left in an UP state after the call is cleared.
Workaround: Use the shutdown interface configuration command followed by the no shutdown interface configuration command to restore the function of the FXS port.
Wide-Area Networking
•
Symptoms: A Cisco AS5800 may reload.
Conditions: This symptom is observed during a period of inconsistent RADIUS service that causes sessions to flap.
Workaround: There is no workaround.
•
Symptoms: An analog call to a digital service 0 (DS0) line may fail.
Conditions: This symptom is observed when an analog call is placed to a digital service 0 (DS0) line that has just serviced a digital call. The analog call may fail because of unavailable resources.
Workaround: There is no workaround.
Resolved Caveats—Cisco IOS Release 12.2(11)T8
Cisco IOS Release 12.2(11)T8 is a rebuild of Cisco IOS Release 12.2(11)T. The caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T8 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
•
•
•
Basic System Services
•
Symptoms: 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.
•
Symptoms: 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.
Miscellaneous
•
Symptoms: A hung time slot may be observed on a Cisco voice gateway.
Conditions: This symptom is observed when a call is made after it has just been disconnected in quick succession on the same time slot on a Cisco voice gateway that is running E1 R2 signaling.
Workaround: There is no workaround.
•
Symptoms: Calls that come in on 1AESS trunks may be rejected by the Cisco AS5000 series access servers.
Conditions: This symptom is observed when incoming calls on 1AESS trunk lines fail to connect. Trunks that come from other switch types are not affected by this symptom.
Workaround: There is no workaround.
•
Symptoms: When "cpmISDNCfgBChannelsInUse" is polled from a network access server (NAS), the total number of active analog and digital calls is returned. The value that is returned does not agree with the results from the show caller summary output. It is observed that "cpmISDNCfgBChannelsInUse" returns a value that is one less than the actual value.
For example: If the total number of calls equals 115 (as verified on the NAS from the show caller summary output), polling "cpmISDNCfgBChannelsInUse" returns a value of 114. Similarly, when the total number of calls equals 23, polling "cpmISDNCfgBChannelsInUse" returns a value of 22.
Conditions: This symptom may be observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(11)T2 and may occur when a large number of both analog and digital calls are received.
Workaround: There is no workaround.
•
Symptoms: A Cisco AS5350 that is configured as a voice gateway may reload because of a bus error.
Conditions: This symptom is observed recurringly (weekly) on a Cisco AS5350 that is running Cisco IOS Release 12.2(11)T and Session Initiation Protocol (SIP), and that may have the timer receive-rtcp gateway configuration command enabled.
Workaround: There is no workaround.
•
Symptoms: The H.323 conference ID format on a Cisco 3700 series router and a Cisco 2600XM series router is not compatible with the conference id format from prior releases of Cisco IOS software.
Conference ID format prior to Cisco IOS Release 12.2(11)T: 712E35B1 A3000037 0 2D37E8
Conference ID format for Cisco IOS Release 12.2(11)T: 712E35B1 A3000037 00000000 002D37E8Conditions: This symptom is observed only for the Cisco 3700 series routers and the Cisco 2600XM series routers that are running Cisco IOS Release 12.2(11)T, Release 12.2(11)T2, and Release 12.2(11)T3.
Workaround: There is no workaround.
•
Symptoms: On a Cisco AS5850 gateway, the transmit and receive packet count may be calculated incorrectly. The punted voice packets may be counted twice: once on the feature board and once on the route shelf controller. In addition, packets that are dropped at the feature board because of an incorrect mode may also be counted.
Conditions: This symptom may be observed only on a Cisco AS5850 gateway and affects all voice calls.
Workaround: There is no workaround.
•
Symptoms: A Cisco AS5400 Session Initiation Protocol (SIP) gateway may stop replying to reINVITE requests from the proxy to maintain a call. This behavior may cause the call to be disconnected when the keepalive timer expires.
Conditions: This symptom is observed on a Cisco AS5400 SIP gateway.
Workaround: Ensure that the SIP proxy is configured with a session timer value that is greater than or equal to the minimum session timer value. If this is not possible, configure the session timer to the highest possible value by entering the min-se time SIP configuration command.
•
Symptoms: Call setups with Continuity Test (COT) may fail. When a COT test fails, the CIC is marked as blocked and because COT continues to fail, the CIC is never recovered.
Conditions: This symptom is observed on a Cisco AS5300 gateway and on a Cisco AS5800 that is running the following images of Cisco IOS Release 12.2(11)T3 through Release 12.2(13)T:
–
–
–
–
–
–
–
Workaround: There is no workaround except to turn off COT.
•
Symptoms: When a Cisco integrated access device (IAD) receives a far-end release and when a call agent sends a request notify (RQNT) message for a release complete (RLC) message, the Cisco IAD does not return an acknowledgement for an RLC message and acknowledges only the receipt of the RQNT message. This symptom causes the broadband telephony system (BTS) call agent to perform an automatic recovery on the Cisco IAD.
Conditions: This symptom is observed on a Cisco IAD2420 that is running Cisco IOS Release 12.2(11)T4.
Workaround: To clear the hung connection on the Cisco IAD, enter the mgcp dlcx global configuration command.
•
Symptoms: A Cisco IAD2420 series may reload when it is under stress from voice calls.
Conditions: This symptom is observed when the voice local-bypass global configuration command is configured to bypass the digital signal processor (DSP) for hairpin calls and when there are mixed analog-to-digital voice calls.
Workaround: Deconfigure the voice local-bypass global configuration command.
•
Symptoms: Some dial-in users that connect to a Cisco AS5850 may be unable to reach external destinations. The packets are sent, but the return packets that enter the Gigabit Ethernet egress interfaces are silently dropped. These drops are not reported by the show cef drop EXEC command, nor do any of the interface drop counters increase. The incoming packet counter on the Gigabit Ethernet, and the outgoing packet counter on the vaccess increase as packets arrive, but the packets do not arrive at the user. All Cisco Express Forwarding (CEF), Forwarding Information Base (FIB), and adjacency entries appear normal. This symptom is observed only for some active sessions. Other sessions function normally. Multilink sessions (even with a single channel only) have not been reported as failing.
Conditions: This symptom is observed only on a Cisco AS5850 that is running Cisco IOS Release 12.2(2)XB10. The symptom is not observed on a Cisco AS5800 that is running the same Cisco IOS software release.
Workaround: There is no workaround at this time. The user must disconnect and reconnect to restore connectivity.
•
Symptoms: A universal gateway may reload.
Conditions: This symptom is observed under rare circumstances on a Cisco AS5400 that is used as a terminating gateway.
Workaround: There is no workaround.
•
Symptoms: When a gateway starts up, Media Gateway Control Protocol (MGCP) restart in progress (RSIP) messages may not be sent for all available E1 interfaces, causing the call agent to be unaware of full circuit availability on the gateway and calls to be dropped. For example, of 15 available E1 interfaces, only one RSIP message is sent (generally but necessarily for the first E1 interface). After 20 minutes, another individual E1 RSIP message is sent followed by a wildcard RSIP message for the entire gateway. Every 10 minutes thereafter, two RSIP messages for individual E1s are sent. Up to 80 minutes may be required before stability is reached, causing calls to be dropped each time a delayed RSIP message is sent after the wildcard RSIP message has been sent.
Conditions: This symptom is observed on a Cisco AS5400 that is functioning as a gateway and that is running Cisco IOS Release 12.2(11)T5.
Workaround: There is no workaround.
•
Symptoms: Endpoints on a gateway may no longer be available after the gateway has reloaded.
Conditions: This symptom is observed when restart in progress (RSIP) messages are lost when a Cisco AS5850 uses a secondary Media Gateway Control Protocol (MGCP) link after it has reloaded. This secondary link is the one with a lower priority when redundant MGCP links are configured on the gateway and a Cisco PGW 2200 PSTN gateway.
Workaround: Disable the secondary link by unplugging the IP connectivity on the gateway.
Wide-Area Networking
•
Symptoms: RADIUS attributes may be missing from an access request packet that is sent from a network access server (NAS) to a RADIUS server, causing an authentication failure from the RADIUS server.
Conditions: This symptom is observed intermittently in Cisco IOS Release 12.2 XB but may also occur in other releases such as Release 12.2 T.
Workaround: Remove the following preauthentication attributes:
–
–
–
•
Symptoms: The PPP over ATM (PPPoA) peer starts one session to the Layer 2 Tunneling Protocol (L2TP) network server (LNS). When the LNS ends the session or clears the tunnel, the PPPoA peer is notified and the PPPoA session is restarted, but the L2TP access concentrator (LAC) does not send the Stop or Start record.
Conditions: This symptom is observed on a Cisco 7200 series router that is running Cisco IOS Release 12.2(4)B4.
Workaround: Restart the session from the PPPoA peer by entering the shutdown interface configuration command followed by the no shutdown interface configuration command on the ATM interface.
Resolved Caveats—Cisco IOS Release 12.2(11)T6
Cisco IOS Release 12.2(11)T6 is a rebuild of Cisco IOS Release 12.2(11)T. The caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T6 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
Symptoms—A description of what is observed when the caveat occurs.
Conditions—The conditions under which the caveat has been known to occur.
Workaround—Solutions, if available, to counteract the caveat.
•
Symptoms: Incorrect Low Latency Queueing (LLQ) and Weighted Random Early Detection (WRED) statistics may be observed on a router when the show policy-map interface interface-name EXEC command is entered.
Conditions: This symptom is observed on a Cisco router while there are hundreds of virtual circuits (VCs) on the router.
Workaround: There is no workaround.
Resolved Caveats—Cisco IOS Release 12.2(11)T5
Cisco IOS Release 12.2(11)T5 is a rebuild of Cisco IOS Release 12.2(11)T. The caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T5 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
Symptoms—A description of what is observed when the caveat occurs.
Conditions—The conditions under which the caveat has been known to occur.
Workaround—Solutions, if available, to counteract the caveat.
•
Symptoms: On a router that has static Address Resolution Protocol (ARP) entries configured, the router may fail to use the static ARP entries immediately.
Conditions: This symptom is observed on a Cisco router if CEF is enabled manually or if the router is reloaded with Cisco Express Forwarding (CEF) enabled.
Workaround: Disable CEF on the router by entering the no ip cef global configuration command.
•
Symptoms: Under rare circumstances, a Channelized T3 (CT3) card may reboot because of a bus error and then recover. The router itself does not reboot or reload; just the card by itself.
Conditions: This symptom is observed when the CT3 card is installed on a Cisco AS5850 that is running Cisco IOS Release 12.2(2)XB6 but may also occur on other releases such as Release 12.2 T.
Workaround: There is no workaround.
•
Symptoms: Physical inverse multiplexing over ATM (IMA) ports are not indexed in the IF-MIB.
Conditions: This symptom is observed on a Cisco router that has IMA interfaces. This symptom has been fixed in Cisco IOS Release 12.2(3)T but may appear in Cisco IOS Release 12.2(8)T and Release 12.2(11)T.
The following example of the IF-MIB shows ATM1/IMA0 (index 43), but the interface is not indexed:
ifDescr.40 = ATM1/7-aal5 layer
ifDescr.41 = ATM1/7.0-aal5 layer
ifDescr.42 = Null0
ifDescr.43 = ATM1/ima0 <----
ifDescr.44 = ATM1/ima0-atm layer
ifDescr.45 = ATM1/ima0.0-atm subif
ifDescr.46 = ATM1/ima0-aal5 layer
ifDescr.47 = ATM1/ima0.0-aal5 layer
ifDescr.48 = ATM1/ima0.40-atm subif
ifDescr.49 = ATM1/ima0.40-aal5 layerWorkaround: There is no workaround.
•
Symptoms: A Cisco router may reload because of a bus error when you download per-user access control lists (ACLs) from a RADIUS server and configure these ACLs for each connection.
Conditions: This symptom is observed on but may not be limited to a Cisco AS5850.
Workaround: Configure static ACLs for each connection.
•
Symptoms: Channels may be stuck in the pending state in a Trunk Group Resource Manager (TGRM).
Conditions: This symptom is observed when the TGRM is used for data calls.
Workaround: There is no workaround.
•
Symptoms: Digital calls and stacks beyond 70 do not get registered to a Call Distributor Application Programming Interface (CDAPI), causing the calls to pause indefinitely.
Conditions: This symptom is observed when there are more than 66 T1 ports configured on a Cisco AS5850.
Workaround: Deconfigure some unused controllers.
•
Symptoms: A Cisco AS5850 may reload because of a memory corruption.
Conditions: This symptom is observed on a Cisco AS5850 that is functioning as a voice gateway and that is running Cisco IOS Release 12.2(11)T2.
Workaround: There is no workaround.
•
Symptoms: When a T1 line in channelized T3 interface on a dial feature card (DFC) goes into a loopback, the remote equipment may receive Path Code Violations (PCVs) or Loss of Signal (LoS), or both.
Conditions: This symptom is observed when a channelized DFC is installed in a Cisco AS5400.
Workaround: Cable a hard loop to the T3 channelized interface.
•
Symptom: The following error message may be displayed on the console of a Cisco AS5850:
%RS_TDM-3-TDM_BADARG: conn types different, trunk=1 modem=0The error message is followed by a traceback.
Conditions: This symptom is observed when voice calls and calls that are switched via time-division multiplexing (TDM) are being made in a Media Gateway Control Protocol (MGCP) environment.
Workaround: There is no workaround.
•
Symptoms: A Cisco Catalyst 4000 access gateway module (AGM) may reload when it detects an overtemperature condition.
Conditions: This symptom is observed on a Cisco Catalyst 4000 AGM that is running Cisco IOS Release 12.2(11)T1 or Release 12.2(11)T2.
Workaround: There is no workaround.
•
Symptoms: An incorrect Resource Availability Indicator (RAI) update may occur when a Cisco AS5400 boots up.
Conditions: This symptom is observed on a Cisco AS5400 that is configured with RAI and that has all its B channels in the maintenance state. After the Cisco AS5400 has reloaded, the RAI sends the status of the gateway as "available with full resources" but should send the status as "out of resources" because all the B channels are in the maintenance state.
Workaround: There is no workaround.
•
Symptoms: A Cisco AS5350 may reload because of a bus error that may be related to Session Initiation Protocol (SIP).
Conditions: This symptom is observed on Cisco AS5350 that is running Cisco IOS Release 12.2(11)T and that is configured for Voice over IP (VoIP), fax, and SIP User Agent (SIP-UA).
The symptom may also occur on a Cisco AS5300 or a Cisco AS5400 that is running Cisco IOS Release 12.2(2)XB.
Workaround: There is no workaround.
•
Symptoms: The following symptoms may occur on a Cisco AS5850:
–
–
–
Conditions: These symptoms are observed under high traffic conditions on a Cisco AS5850 that is running Cisco IOS Release 12.2(11)T.
Workaround: There is no workaround.
•
Symptoms: The CPU utilization on a Cisco AS5300 voice gateway may be too high during the handling of voice traffic.
Conditions: This symptom is observed on a Cisco AS5300 voice gateway that is running Cisco IOS Release 12.2(11)T2. The CPU utilization in Release 12.2(11)T2 is about 15 percent higher than the CPU utilization in Release 12.2(12a) under the same traffic conditions.
Workaround: There is no workaround.
•
Symptoms: A Cisco router may reload because of a watchdog timeout condition.
Conditions: This symptom is observed on a Cisco router that is functioning as a voice endpoint with active calls.
Workaround: There is no workaround.
•
Symptoms: A gateway does not provide a ringback tone to a voice call that originates from a remote switch that it is connected to via a T1 connection.
Conditions: This symptom is observed on a Cisco AS5350, Cisco AS5400, or Cisco AS5350.
Workaround: There is no workaround.
•
Symptoms: A Cisco 2600 series may reload with a signal trap (Sigtrap) exception that is caused by a memory leak in the "CCSIP-SPI-CONTROL" process.
Conditions: This symptom is observed on a Cisco 2600 series that is running Cisco IOS Release 12.2(11)T when a subscribe request for unsupported services or nonexistent events occurs.
Workaround: Ensure that no invalid subscribe request is being sent.
•
Symptoms: Error messages may be generated during the bootup of a Cisco AS5850, and Gigabit Ethernet interfaces may not come up.
Conditions: This symptom is observed when there are active calls on a Cisco AS5850 and you reload the Cisco AS5850 with a new image of Cisco IOS Release 12.2(11)T.
Workaround: Reload the Cisco AS5850.
•
Symptoms: The "callactive" and "callhistory" records may display erroneous information.
Conditions: This symptom is observed if the display information element (IE) is greater than 15 characters in size.
Workaround: There is no workaround.
•
Symptoms: A Cisco gateway may return a 200 message (indicating Delete in Progress) to a delete connection (DLCX) message, causing the connection to remain up indefinitely.
Conditions: This symptom is observed on a Cisco AS5850.
Workaround: There is no workaround.
•
Symptoms: A Cisco AS5300 may report an incorrect ISDN service status after it has reloaded.
Conditions: This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(11)T and that is configured with Signaling System 7 (SS7) (using the rlm group global configuration command) and Non-Facility Associated Signaling (NFAS).
When all B channels are set to maintenance state, the output of the show isdn service privileged EXEC command displays correct information. After you reload the Cisco AS5300 with same configuration, all B channels are still displayed in the maintenance state except the 24th B channel in the NFAS group, as is displayed in the following command output:
Router# show isdn service
PRI Channel Statistics:
ISDN Se0:23 SC, Channel [1-24]
Configured Isdn Interface (dsl) 0
Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Service State (0=Inservice 1=Maint 2=Outofservice)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0
Channel blocked? (0=No 1=Yes)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Note
Workaround: Add the isdn service nfas-int 0 b_channel 24 state 1 interface configuration command under the serial interface to place the 24th B channel in the maintenance state, and verify the output of the show isdn service privileged EXEC command.
•
Symptoms: Modem and fax passthrough calls may fail to train up.
Conditions: This symptom is observed when voice activity detection (VAD) is enabled. VAD is not turned off for fax and modem calls after the calls are determined to be fax modem calls.
Workaround: Disable VAD if the gateway is intended to be used for fax and modem calls.
•
Symptoms: Packet statistics may not be updated for some voice calls.
Conditions: This symptom is observed on a Cisco AS5850.
Workaround: There is no workaround.
•
Symptoms: A Cisco 2600 series may incorrectly send a disconnect cause code "0x1B" to a RADIUS server for a normal call.
Conditions: This symptom is observed when you make a call from a Cisco 2600 series using a third-party vendor gateway.
Workaround: There is no workaround.
•
Symptoms: 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.
•
Symptoms: The output of the test dsprm hidden command and the output of the show snmp EXEC command display active digital signal processor (DSP) recovery alarms.
Conditions: This symptom is observed on a Cisco AS5300 that is functioning as a voice gateway.
Workaround: There is no workaround.
•
Symptoms: When digital signal processor (DSP) resource management (DSPRM) attempts to recover a DSP channel without first checking whether its peer channel is still loading, a double loading condition may occur.
Conditions: This symptom is observed on a Cisco AS5300 that is configured for Voice over IP (VoIP).
Workaround: There is no workaround.
•
Symptoms: Media Gateway Control Protocol (MGCP) network access server (NAS) package calls may cause the following RADIUS accounting attributes to contain zero values:
–
–
–
–
–
–
–
–
–
–
Conditions: This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(2)XB8 or Release 12.2 T.
Workaround: There is no workaround.
•
Symptoms: An incorrect cause code may be used for normal call clearing.
Conditions: This symptom is observed when a Cisco gateway receives a disengage reject (DRJ) or timeout message as a response to a disengage request (DRQ) that was sent to a gatekeeper. The gateway attempts to map the DRJ reason into the H.225 termination cause code. However, this termination cause code is incorrect and should not be used.
Workaround: There is no workaround.
•
Symptoms: When you dial an access code to access a Foreign Exchange Office (FXO) port, the call may be dropped immediately after the FXO port is seized.
Conditions: This symptom is observed on a Cisco IAD2421 that is running Cisco IOS Release 12.2(11)T.
Workaround: There is no workaround.
•
Symptoms: Configuring a dialer interface (or any other logical interface) may cause a router to reload.
Conditions: This symptom is observed when the cns config notify diff global configuration command is configured and you use Cisco Networking Services (CNS) to configure a dialer interface (or any other logical interface).
The symptom also occurs when the cns config initial global configuration command or the cns config partial global configuration command is configured.
Workaround: There is no workaround.
•
Symptoms: A gateway that negotiates a G.729 codec with 20 bytes in the call setup may send 40 bytes instead.
Conditions: This symptom is observed on a Cisco AS5300 that is functioning as a gateway.
Workaround: There is no workaround.
•
Symptoms: Voice over Frame Relay (VoFR) calls may fail because of path confirmation failures.
Conditions: This symptom is observed on a Cisco 7200 series.
Workaround: There is no workaround.
•
This caveat consists of four symptoms, four conditions, and four workarounds:
–
Conditions A: This symptom is observed in all images of Cisco IOS Release 12.2(11)T, Release 12.2(13)T, and later releases that support MGCP when a T.38 fax call that is in progress is audited.
Workaround A: There is no workaround.
–
Conditions B: This symptom is observed on a Cisco IOS release later than Release12.2(13)T when a voice call that contains both a voice leg and a Voice over IP (VoIP) leg is audited.
Workaround B: There is no workaround.
–
Conditions C: This symptom is observed on a Cisco IOS release later than Release 12.2(13)T when an active call is audited before a corresponding feature (such as a T.38 fax feature that is driven by a call agent) is invoked.
Workaround C: There is no workaround.
–
Conditions D: This symptom is observed on a Cisco IOS release later than Release 12.2(13)T when an active call is audited before a corresponding feature (such as three-way calling) is invoked.
Workaround D: There is no workaround.
Resolved Caveats—Cisco IOS Release 12.2(11)T4
Cisco IOS Release 12.2(11)T4 is a rebuild of Cisco IOS Release 12.2(11)T. The caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T4 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
Symptoms—A description of what is observed when the caveat occurs.
Conditions—The conditions under which the caveat has been known to occur.
Workaround—Solutions, if available, to counteract the caveat.
•
Symptoms When you bring Media Gateway Control Protocol (MGCP) endpoints out of a hold situation while you simultaneously change their codec, the codec change may not take effect.
Conditions This symptom is observed when a Cisco IAD2420 series is interoperating with a call agent of a third-party vendor.
Workaround There is no workaround.
•
Symptoms No ringback tone is heard when a hairpin call is made from a Foreign Exchange Station (FXS) port to the T1 port of a Cisco IAD2421 integrated access device.
Conditions This symptom is observed on a Cisco IAD2421 that is running Cisco IOS Release 12.2(11)T.
Workaround Configure the no voice local-bypass global configuration command to prevent hairpin calls from being made.
Resolved Caveats—Cisco IOS Release 12.2(11)T3
Cisco IOS Release 12.2(11)T3 is a rebuild of Cisco IOS Release 12.2(11)T. The caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T3 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
Symptoms—A description of what is observed when the caveat occurs.
Conditions—The conditions under which the caveat has been known to occur.
Workaround—Solutions, if available, to counteract the caveat.
•
Symptoms After an integrated access device (IAD) initiates a NTFY message indicating a new call, the call agent sends a notification request (RQNT) with all the dial-plan information to the IAD, but the IAD never sends the notify (NTFY) message with the collected digits to the call agent.
The Voice Port Module (VPM) debug output shows that the IAD starts collecting the digits to be sent to the call agent, but never actually sends the notify (NTFY) message with the collected digits to the call agent. Eventually, after 20 to 30 seconds, an announcement is played to the client on the phone.
Conditions This symptom is observed on a Cisco IAD2420 series router.
Workaround Move the subscriber termination to out of service (OOS) and then back to in service (INS).
•
Symptoms Polling for numbered ATM subinterfaces and unnumbered Frame Relay interfaces does not return any data. When the ifInNUcastPkts, ifOutNUcastPkts, and ifOutQLen variables are among the first of multiple objects that are bundled together in an snmpget command, some or all of these variables return the message "no such variable."
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.0(19)S2.
Workaround Retrieve the variables individually or via an snmpwalk command.
•
Symptoms This symptom is observed in a setup in which three phones (phones A, B, and C) are connected to a gateway that has a Media Gateway Control Protocol (MGCP) call agent. When phone C calls phone A while there is an ongoing call between phone A and phone B, a conference warning departure tone is heard on phone A instead of a call waiting tone.
Conditions This symptom is observed in a setup in which three phones are connected to a gateway that has an MGCP call agent.
Workaround There is no workaround.
•
Symptoms A PRI subscriber cannot hear a ringback tone (RBT) when a call to a call waiting (CW) subscriber is terminated. When the CW line is active with a call and when the PRI terminates to it, the CW line hears a CW tone, but the PRI subscriber does not hear an RBT. The PRI subscriber will hear a RBT tone from all other lines and from the call waiting line if call waiting is not invoked.
Conditions This symptom is observed when calls are made from a PRI to an analog integrated access device (IAD) analog CW line while the CW line is active. This symptom affects all PRI subscribers and is observed in Cisco IOS Release 12.2(11)T2 and earlier releases.
Workaround There is no workaround.
•
Symptoms A provider edge (PE) headend router that is running Multiprotocol Label Switching (MPLS) and that is connected via a Label Distribution Protocol (LDP) link to a neighboring provider (P) router may reload when one or more interfaces on the P router are unconfigured using the following sequence of commands (all commands are entered):
a. no mpls ip global configuration command
b. no mpls ip interface configuration command
c. shutdown interface configuration command
Conditions This symptom is observed on LDP neighbors that are connected via label controlled ATM (LC-ATM) interfaces. The symptom may not occur when Tag Distribution Protocol (TDP) is the label signaling protocol.
Workaround Shut down the LC-ATM interface of the PE headend router before you enter the three above-mentioned configuration commands on the P router.
Alternative Workaround Do not use all three above-mentioned configuration commands to unconfigure the interface on the P router. Instead, use only the two interface configuration commands, that is, the no mpls ip and shutdown interface configuration commands.
•
Symptoms A Cisco router may reload with a software-forced reload error when triggering a dial call.
Conditions This symptom occurs on Cisco platforms that are running Cisco IOS Release 12.2(13)T and that support ISDN using the dialer configuration.
Workaround There is no workaround.
•
Symptoms A gateway may occasionally time out when it is sending side keepalive messages.
Conditions This symptom is observed when a Cisco MC3810 is configured as a connection trunk for Voice over IP (VoIP) over ATM Adaptation Layer 5 (AAL5). This symptom occurs because the Cisco MC3810 generates the keepalive packet without the "initialize rtp ssrc" field. The keepalive packet is then dropped because it failed to pass the Real-Time Protocol (RTP) range checking.
Workaround Enter the signal sequence oos no-action voice-class configuration command to configure the router to ignore the occasional drops of keepalive packets. The trunk will disconnect if the loss of keepalive event lasts longer than the default value of 120 seconds that is in the signal timing oos timeout seconds voice-class configuration command. This workaround prevents the trunk from being blocked, and new calls can be accepted even when the trunk detects dropped keepalives.
•
Symptoms A ringback tone may be played regardless of the true state of the called party.
Conditions This symptom is observed when a loopback-directory number (loopback-dn) is used to place outgoing calls on a Cisco IP telephony gateway that is configured with a loopback-dn between the Voice over IP (VoIP) cloud and the IP phones.
The ringback tone is played for a short duration before the true progress tone is heard. This symptom occurs when a call terminates to open a voice path in the backward direction to play progress tones or messages that can be heard by the caller before the call is disconnected (because the called party is either busy or unavailable). The Cisco gateway in this setup is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms ISUP-to-ISUP calls may fail because the terminating gateway creates an extended facility information element (IE) that is out of order.
Conditions This symptom is observed when a Cisco router that is running Cisco IOS Release 12.2(11)T1 or Release 12.2(11)T2 is configured for a Cisco SS7 Interconnect for Voice Gateways Solution that depends on ISDN User Part (ISUP) transparency.
Workaround There is no workaround.
•
Symptoms When a call goes through a Cisco 2600 series that works as a gateway to be called, the "200 okay reply message to reinvite" has an incorrect Session Definition Protocol (SDP) value.
Conditions This symptom is observed on a Cisco 2600 series that is running Cisco IOS Release 12.2(11)T. This symptom occurs when a mid-call invite message is received to revert from a negotiated dtmf-reply payload type to the inband voice payload type.
Workaround There is no workaround.
•
Symptoms The Simple Network Management Protocol (SNMP) counters of a Cisco AS5800 may begin to deviate and may no longer reflect the actual number of calls when random analog and digital calls are received.
Conditions This symptom is observed on a Cisco AS5800 and occurs only when both analog and digital calls are received at the same time.
Workaround There is no workaround.
•
Symptoms Digital signal processor (DSP) problems may occur during stress. A minilogger output shows that the fax mode message was sent to the DSP before the fax codec overlay request was sent.
Conditions This symptom is observed in a Media Gateway Control Protocol (MGCP) Voice over IP (VoIP) network.
Workaround There is no workaround.
•
Symptoms A Cisco UPC324 dial feature card on a Cisco AS5800 may stop accepting analog calls after running for about two hours. The following message may be displayed in the log when the failure occurs:
DSIP-6-NIP_SEND_BUF: DSIP send data failed, slot 6 nip client id 4 DSIP-6-NIP_SEND_BUF: DSIP send data failed, slot 6 nip client id 4 DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 6 SucceededThe failed board will no longer be accessible by entering the dsip console command, and more than 3 GBs of memory are displayed in the following output of the show dial-shelf EXEC command:
Slot Board CPU DRAM I/O Memory State Elapsed
Type Util Total (free) Total (free) Time
0 CE1 3%/2% 14047744( 48%) 12582912(59%) Up 06:48:47
1 CE1 3%/2% 14047744( 48%) 12582912(59%) Up 06:48:49
6 UP324 3474718759( 0%) 4179101916(0%) Up 06:48:48
7 UP324 0%/0% 60185088( 82%) 67108864(79%) Up 06:48:47
12 DSC 0%/0% 13588640( 53%) 12582912(73%) Up 06:51:21Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(2)XB7. This symptom is observed only when a dial shelf controller (DSC) is installed in slot 12. Cisco universal port cards (UPCs) that are controlled by a DSC in slot 13 are not affected. The symptom may also occur in Release 12.2 T.
Workaround Reload the affected card by entering the hw-module slot shelf-id/slot-number reload privileged EXEC command.
•
Symptoms No dial tone is heard on the Foreign Exchange Station (FXS) ports, and no calls can connect from T1 ports. Dead air exists on the handset.
Conditions This symptom is observed on a Cisco IAD2420 series smart integrated access device that is running Cisco IOS Release 12.2(11)T1.
Workaround Enter the no voice local-bypass global configuration command on the Cisco IAD2420 series.
•
Symptoms ATM permanent virtual circuit (PVC) may remain inactive after a reload occurs. The shutdown interface configuration command followed by the no shutdown interface configuration command has to be entered to bring the interface back up again.
Conditions This symptom is observed on a Cisco 2650XM router that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A bus error may occur on a Cisco AS5400, and the following message may be displayed in the output of the show log EXEC command:
%NP-3-NAKRSP: NAK Response Received - command 0x1501, result code 0x8005, msg id 0x15FF, session id 0x85, msg tag 0x0, slot/port 1/25 %NP_EST-6-CTRL_NAK_RSP: (NP address 1/0/0/255), Msg ID=0x15 01, Result=UNKNOWN_COMMAND_ID, Data format=Binary, Data len=8, Data=80 02 00 85 00 00 15 01Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A router shelf may reload because of a bus error when an illegal access to a low address occurs.
Conditions This symptom occurs on a Cisco 7200 series router shelf that is configured with a PA-MC-8E1/120 port adapter and that is part of a Cisco AS5800 that is running Cisco IOS Release 12.2(11)T after you configure the show running-config privileged EXEC command or the write memory privileged EXEC command
Workaround The Cisco AS5800 does not reload if you do not use the E1 port adapter on the router shelf.
•
Symptoms The loopback-directory number (loopback-dn) is used to place outgoing calls across Voice over IP (VoIP). The ringback tone may play regardless of the true state of the called party (busy for example). The ringback is played for a moment before the true progress tone is heard.
Conditions This symptom occurs when a Cisco IOS Telephony Service (ITS) gateway is configured with loopback-dn between the VoIP cloud and the IP phones. This event is triggered when the loopback-dn falsely predicts itself as the final target and is still in the idle state.
Workaround There is no workaround.
•
Symptoms The Continuity Test (COT) single-tone loopback in a Signaling System 7 (SS7) network may fail because echo cancellation is not being turned off. The digital signal processor (DSP) is not able to detect the same tone that it is sending if echo cancellation is enabled.
Conditions This symptom is observed on a Cisco 3660 router that is running Cisco IOS Release 12.2(11)T2.
Workaround Turn off echo cancellation on the voice port.
Alternate Workaround Change the COT from single-tone loopback to dual-tone test.
•
Symptoms Multiple codecs specified in Voice over IP (VoIP) dial peers, including g723r63 or g726r32, cause several dial peers to rotate with the same destination. The wrong 20-byte payload size is sent to the digital signal processor (DSP) which may cause the DSP to reload intermittently because g723r63 is expecting no less than a 24-byte payload, and g726r32 is expecting no less than a 40-byte payload.
Conditions This symptom is observed in a Cisco H.323 VoIP network and Media Gateway Control Protocol (MGCP) VoIP network.
Workaround There is no workaround.
•
Symptoms A Cisco 2600 series or Cisco 3600 series router that is configured with a Multiflex Trunk (MFT) voice/WAN interface card (VWIC) that is installed in a Fast Ethernet (FE) combo network module (NM) may lose connectivity on port 0 of the MFT VWIC in slot 1 of the FE combo NM. This symptom does not occur on slot 0 of the FE combo NM.
Conditions This symptom is observed on a Cisco 2600 series or Cisco 3600 series router that is running Cisco IOS Release 12.2(12.4)T or a later release.
Workaround There is no workaround.
•
Symptoms Cisco IAD2420 series analog voice ports may overheat. As a result, the Cisco IAD2420 series will try to alleviate the situation by reducing the driving currents. However, there is also a reset operation that might interfere with how the Cisco IAD2420 series current-limit function works. The result may cause the Cisco IAD2420 series to have physical damage (burned parts).
Conditions Under an unknown situation, the Cisco IAD2420 series analog voice ports may overheat, possibly because of poor venting at the installation site.
Workaround Improve the vent condition. To avoid blocking the vent hole, do not remove the rubber feet on the chassis.
•
Symptoms The call-waiting tone may not be played when a call comes into a port where another call is already in progress.
Conditions This symptom is observed when a Cisco IAD2420 series voice port is configured with the cptone hk command (hk stands for Hong Kong).
Workaround There is no workaround.
•
Symptoms The ds0-group channel timeslots range type signal controller configuration command cannot be configured with 15 channels on an E1 controller interface. This limitation allows only 30 channels to be configured on an E1 controller interface.
Conditions This symptom is observed on the E1 controller interface of a Cisco router that is running Cisco IOS Release 12.2(13)T.
Workaround There is no workaround.
•
Symptoms If a T1 or E1 interface is brought back into service either by entering the no shutdown interface configuration command or by flapping the T1 or E1 interface while a default profile is configured, Media Gateway Control Protocol (MGCP) restart in progress (RSIP) messages may use the default retransmit parameters even though MGCP should be using parameters that are defined in the corresponding MGCP profile configuration. As a result of this behavior, the RSIP messages may not reach the correct call agent and the circuit identification code (CIC) on the call agent may enter the BLK= gateway state.
Conditions This symptom is observed on a Cisco gateway router that is running Cisco IOS Release 12.2(11)T2. This behavior does not occur when an RSIP message is sent to the T1 or E1 interface while the interface is shut down. The gateway uses the correct parameters in the corresponding MGCP profile in such a scenario.
Workaround Configure the gateway router so that the IP link is active on the first IP address or reconfigure the static host list so that the current active IP link is the first IP address that is on the list.
•
Symptoms An originating Foreign Exchange Station (FXS) phone hears a ringback tone instead of a busy tone.
Conditions This symptom is observed when a call comes in from an FXS phone on Gateway 1 or Gateway 2. The call comes in to Gateway 2 through a pair of loopback-directory numbers (loopback-dns) and is forwarded on Call Forward No Answer (CFNA)/call forward busy (CFB) to a public switched telephone network (PSTN)/PRI gateway. The PSTN gateway phone is busy; hence a disconnect tone is sent to the originating side in the form of PI value 8. Gateway 2 receives in-band alerting. The loopback-directory number (loopback-dn) pair converts in-band alerting to out-of-band alerting.
Workaround There is no workaround.
•
Symptoms If Create Connection (CRCX) is sent with a string of digits including the symbol "*", the Cisco IOS gateway responds with the 510 protocol error as the acknowledgement (ACK), and the call is not set up.
Conditions This symptom is observed on Cisco 2600 series router when Media Gateway Control Protocol (MGCP) is configured with a Cisco IOS gateway using T1 channel-associated signaling (CAS) and Cisco CallManager.
Workaround Use the H.323 protocol instead of MGCP.
•
Cisco devices which run IOS and contain support for the Secure Shell (SSH) server are vulnerable to a Denial of Service (DoS) if the SSH server is enabled on the device. A malformed SSH packet directed at the affected device can cause a reload of the device. No authentication is necessary for the packet to be received by the affected device. The SSH server in Cisco IOS is disabled by default.
Cisco will be making free software available to correct the problem as soon as possible.
The malformed packets can be generated using the SSHredder test suite from Rapid7, Inc. Workarounds are available. The Cisco PSIRT is not aware of any malicious exploitation of this vulnerability.
This advisory is available at
http://www.cisco.com/warp/public/707/ssh-packet-suite-vuln.shtml
•
Symptoms Internetwork Packet Exchange (IPX) Enhanced Interior Gateway Routing Protocol (EIGRP) neighbors will not form adjacencies if incremental Service Advertising Protocol (SAP) updates are enabled. IPX EIGRP neighbors will not remain established and IPX routing will not work for interfaces that are affected by this symptom.
The following message is displayed if the eigrp log-neighbor-change router configuration command is configured:
%DUAL-5-NBRCHANGE: IPX-EIGRP 1: Neighbor ABC.0001.4266.3381 (Serial0/0)is down: Auth failureIncremental SAP updates are enabled by default on all non-IEEE interfaces (WAN interfaces). Incremental SAP updates are also disabled on all IEEE interfaces (LAN interfaces). Therefore, LAN interfaces are not affected by this symptom unless the interfaces have been configured to perform incremental SAP updates by entering the ipx sap-incremental interface configuration command.
Conditions This symptom is observed on a Cisco 4224 that is running Cisco IOS Release 12.2(8.05)T.
Workaround Configure the no ipx sap-incremental interface configuration command on the interfaces that have incremental SAP updates enabled by default or configuration to prevent the symptom from occurring.
•
Symptoms A router may reload unexpectedly because of a bus error.
Conditions This symptom is observed when IP Security (IPSec) is configured on a Cisco router. The Cisco router rekeys after both the IPSec and Internet Key Exchange (IKE) security associations (SAs) expire while the peer is operating in the Dead Peer Detection (DPD) mode.
Workaround The router is less likely to reload if Internet Security Association and Key Management Protocol (ISAKMP) is not configured.
Resolved Caveats—Cisco IOS Release 12.2(11)T2
Cisco IOS Release 12.2(11)T2 is a rebuild of Cisco IOS Release 12.2(11)T. The caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T2 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
Symptoms—A description of what is observed when the caveat occurs.
Conditions—The conditions under which the caveat has been known to occur.
Workaround—Solutions, if available, to counteract the caveat.
•
Symptoms The virtual-access counters and the RADIUS accounting data exceed the real value.
Conditions This symptom is observed on a Cisco 7200 PA-A3 port adapter and a Cisco 6400 NRP2-SV when a Layer 2 Tunneling Protocol (L2TP) network server (LNS) uses an ATM permanent virtual connection (PVC) as an ingress interface for L2TP tunnels.
Workaround Configure an Ethernet port as the ingress interface.
•
Symptoms A router reloads unexpectedly with I/O memory corruption errors when using RADIUS accounting for Voice over IP (VoIP).
Conditions This symptom is observed on a router that is running Cisco IOS Release 12.2(11)T or Release 12.2(11)T1.
Workaround Configure an accounting template that limits the number attributes so that RADIUS accounting packet sizes do not exceed 1500 bytes.
•
Symptoms The Response Time Reporter (RTR) uses random User Datagram Protocol (UDP) ports to respond to Service Assurance Agent (SAA) probes.
Conditions This symptom is observed on a Cisco router.
Workaround There is no workaround.
•
Symptoms The call-history information that is generated by the Session Initiation Protocol (SIP) call leg does not have a valid duration (nonzero) even though the plain old telephone service (POTS) call history for the same call has a nonzero duration.
Conditions This symptom is observed when the acknowledge (ACK) message fails to reach the terminating gateway (TGW).
Workaround There is no workaround.
•
Symptoms A Cisco IOS MGCP gateway returns a "510 Network type not supported" error message when the Call Agent sends a Request Notify (RQNT) command prior to sending a Create Connection (CRCX) command that specifies "nt:local" to setup a hairpin connection. Any RQNT command will cause this symptom, but it occurs only when the CRCX has "nt:local" to setup a hairpin connection.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2T or Release 12.2XB4.
Workaround There is no workaround.
•
Symptoms A Gigabit Ethernet input queue may become wedged.
Conditions This symptom is observed on a Cisco 7400 router.
Workaround There is no workaround.
•
Symptoms A telephony leg call detail record (CDR) may not have the original called number.
Conditions This symptom is observed when the H.323 call leg receives a new number following signaling with a gatekeeper (GK). The telephony call leg CDR gets updated with the translated number.
Workaround There is no workaround.
•
Symptoms A Cisco IOS terminating gateway that is not configured to use the T.38 fax relay protocol receives and accepts a T.38 fax call after detecting a fax tone when the call should not have been accepted or received.
Conditions This symptom is observed when the remote originating gateway advertises T.38 capabilities, and the terminating gateway is configured for the default Cisco fax protocol. This symptom exists in Cisco IOS Release 12.2T, 12.2(2)XB2, 12.2(2)XA3.
Workaround There is no workaround.
•
Symptoms ISDN Layer 2 traffic processed after the T1/E1 controller is shutdown.
Conditions This symptom has been observed on a Cisco AS5300 access server.
Workaround There is no workaround.
•
Symptoms A Cisco 7507 router that is running 12.2(11)T with an Enhanced Gigabit Ethernet Interface Processor (GEIP+) reloads when Border Gateway Protocol (BGP) is enabled and generates the following error messages:
%SYS-3-CPUHOG: Task ran for 11716 msec (83/3), process = OIR Handler, PC = 604D1A28.
-Traceback= 604D1A30
%VIP4-80 RM7000-3-MSG: slot6 VIP-3-SVIP_RELOAD: SVIP Reload is called.
%IPC_RSP_CBUS-3-NOBUF: No more IPC memd buffers to transmit IPC
%SYS-2-MALLOCFAIL: Memory allocation of 2304 bytes failed from 0x6042BDFC, alignment 0
Pool: Processor Free: 19336 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool
Total Spurious Accesses 171, Recorded 1
Address Count Traceback
D0 171 0x6027E12C 0x602E2678 0x6012EFA0Conditions This symptom is observed on a Cisco 7507 router that is running Cisco IOS Release 12.2(11)T. This symptom does not affect GEIP. This symptom occurs when distributed Cisco Express Forwarding (dCEF) is enabled globally and dCEF is enabled or disabled on the Gigabit Ethernet interface.
Workaround There is no workaround.
•
Symptoms Simple Network Management Protocol (SNMP) queries for the dsx1ConfigTable and dsx1CurrentTable objects do not populate the MIB tables.
Conditions This symptom is observed Cisco 2600 series, Cisco 3600 series, and the Cisco AS5300 when running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A digital signal processor (DSP) of a high density analog voice network module (NM-HDA) may not upspeed.
Conditions This symptom is observed on a Cisco 2600 series and Cisco 3600 series router with fax or modem pass-through calls over an ATM Adaptation Layer 2 (AAL2) connection trunk. The DSP should upspeed to g711 u-law/a-law but does not do so. G711a-law, g711 u-law, and g726r32 codec fax calls go through without upspeed.
Workaround There is no workaround.
•
Symptoms Gatekeepers may fail to exchange Gatekeeper Update Protocol (GUP) registration and may work as a cluster when the number of gateways and zones is high.
Conditions This symptom is observed on a Cisco 2600 series router.
Workaround There is no workaround.
•
Symptoms The output from the show process memory EXEC command indicates that the amount of memory held by the "PPP Events" process continues to increase. This indicates a memory leak.
Conditions This symptom is observed on a Cisco AS5850. User profiles that have a Link Control Protocol (LCP) attribute that is applied to an interface, for example, Timeout or Idle-Timeout, cause a leak of per-user request structures.
Workaround Use virtual profiles.
•
Symptoms On a router, the initial, minimum, and maximum playout values are not set to the same values in the NextPort driver.
Conditions This symptom is observed on a Cisco AS5400. This symptom does not occur on the Cisco AS5300 because the initial value is used.
Workaround Explicitly set the initial, minimum, and maximum delay values as close as possible to the same values in the NextPort driver. Note that there are some range check limitations such as in dial peers and voice ports for H.323 and Session Initiation Protocol (SIP), and in the mgcp playout command for Media Gateway Control Protocol (MGCP).
•
Symptoms A message stating "DSP timeout on event 0x6" may be reported accompanied by a drop in the call success rate.
Conditions This symptom is observed after running several iterations of 40 simultaneous modem and fax pass-through calls.
Workaround There is no workaround.
•
Symptoms When the gateway controller goes down or is disconnected on the network, the gateways still shows that Permanent Virtual Circuits (PVCs) are up.
Conditions This symptom has been observed on a Cisco MC3810 multiservice access concentrator and Cisco IAD 2420 Integrated Access Devices.
Workaround Enter the oam-pvc [manage] configuration command.
•
Symptoms An ISDN BRI interface does not use the T302 timer as an interdigit timer.
Conditions This symptom is observed only with voice calls on an ISDN BRI interface that is configured for overlap receiving on a Cisco router that is running Cisco IOS Release 12.2(6e). This symptom does not affect modem or data calls. The inbound dial peer for the voice call does not have the direct-inward-dial string dial-peer configuration command configured.
Workaround There is no workaround.
•
Symptoms Media Gateway Control Protocol (MGCP) generates parser error (510) in the Session Definition Protocol (SDP) information.
Conditions This symptom is observed when any of the string parameters in the "origin" option (session name and user ID) of the Modify Connection (MDCX) message in the SDP is greater than 80 characters.
Workaround There is no workaround on the Cisco IOS gateway. However, if the call agent is configurable, it can be configured to send a shorter session name and user ID (less than 80 characters).
•
Symptoms A Cisco AS5800 network access server (NAS) reloads at multi_session_add_link after approximately 14 to 16 hours of stress testing.
Conditions This symptom is observed on a NAS that is running almost 700 calls (a mixture of analog, sync PPP, and multilink calls).
Workaround There is no workaround.
•
Symptoms False virtual access interfaces are seen on a Cisco AS5800 under a heavy load.
Conditions This symptom is observed in the output of the show users command on a Cisco AS5800 router. This symptom can be service impacting as the Cisco AS5800 will eventually run out of virtual access interfaces.
Workaround There is no workaround.
•
Symptoms A gateway reloads upon receipt of a STATUS message. The gateway could receive a STATUS message if the sender had received an H.225 message from the gateway that was not understood or that was regarded as an error.
Conditions This symptom is observed when certain IP in IP (IPIP) gateway images send information (INFO) messages with the Signal IE to Cisco IOS 12.1(5) T time-division multiplexing (TDM) gateway images. (Refer to CSCdy23133 for more information on this particular instance of the failure.)
Workaround There is no workaround.
•
Symptoms A Simple Network Management Protocol (SNMP) query for DS0 entities from the cpmDS0UsageTable object in the CISCO-POP-MGMT-MIB fails over an Engine 1 port that is configured with Channel Associated Signalling (CAS). The DS0 entity (specifically, ds0-group) information is not populated in the MIB table.
Conditions This symptom is observed on the Cisco AS5300, AS5350, AS5400, AS5800, and AS5850 platforms when running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A Cisco uBR905 Cable Access Router is unable to go online after a software upgrade to Cisco IOS Release 12.2(8)T5 or later.
Conditions This symptom is observed only on revision 3.c Cisco uBR 905 Cable Access Routers. The following text is seen after entering the show version command:
cisco uBR924 CM (MPC850) processor (revision 3.c)Workaround There is no workaround.
•
Symptoms Calls fail and a "No more SWIDB allowed" error message is displayed.
Conditions This symptom is observed on a Cisco AS5800 series router.
Workaround There is no workaround.
•
Symptoms A voice call fails to connect when both sides negotiate a connection using g711alaw compression.
Conditions This symptom is observed when the Media Gateway Control Protocol (MGCP) starts a call with using g729ar8 compression through an H323 proxy gatekeeper (which prefers g711alaw compression by default). The MGCP changes to g711alaw compression before the call fails.
Workaround There is no workaround.
•
Symptoms A Continuity Test (COT) in Signaling System 7 (SS7) fails when issued from a Terminating Gateway (TGW) toward the Telco side of the network.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(8)T1 or later.
Workaround There is no workaround.
•
Symptoms Attributes 42 and 43 might carry negative values when the aaa accounting exec default none command is configured on the network access server (NAS).
Conditions This symptom occurs in approximately one accounting record out of ten.
Workaround There is no workaround.
•
Symptoms A router that is running cell-mode tag switching or Multiprotocol Label Switching (MPLS) on a label controlled ATM (LC-ATM) interface may reload when it receives a more specific prefix for a label mapping or binding than the one that is already allocated. For example, the router may reload when it receives the prefix 10.1.1.0/24 if a binding was already allocated for 10.1.1.1/32 on the basis of the routing entry 10.1.0.0/16.
Conditions This symptom is observed on an Edge Label Switch Router (ELSR) or Label Switch Controller (LSC).
Workaround There is no workaround for an ELSR. To prevent an LSC from reloading, disable the headend label virtual circuits (LVCs) by entering the tag-switching atm disable-headend-vcs global configuration command.
•
Symptoms Failed Multilink PPP (MLP) calls may cause phantom virtual-access interface conditions.
Conditions This situation has been observed on a Cisco AS5800 access server.
Possible workaround Enter the ppp timeout ncp interface configuration command.
•
Symptoms Configuring a gatekeeper that has Location Request (LRQ) authentication enabled with a file from a TFTP server causes a password authentication error and the "invalid permission" Location Rejection (LRJ) message to be displayed.
Conditions This symptom is observed when the configuration file on the TFTP server contains the security password-group gatekeeper configuration command, and the password string is written to the configuration file in the clear text format.
Workaround Configure an encrypted password on the gatekeeper, and use the encrypted password in the configuration file on the TFTP server.
•
Symptoms All packets that are sent to a line card are shown as queued up when the show cef linecard command is issued.
Conditions This symptom is observed when the Forwarding Information Base (FIB) is disabled on the line card.
Workaround Issue the clear cef linecard slot-number command. If this does not correct the problem, perform an online insertion and removal (OIR) procedure on the affected line card.
•
Symptoms Media Gateway Control Protocol (MGCP) fax passthrough does not function.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A dangling timer causes a digital signal processor (DSP) to crash and time out.
Conditions This symptom is observed when a heavy load of Voice over IP (VoIP) fax or modem calls are received.
Workaround There is no workaround.
•
Symptoms A router reloads with a bus error that has no identifiable trigger.
Conditions This symptom is observed on a Cisco 3660 router that is running Cisco IOS Release 12.2(11)T and is running ATM Service Level Monitoring.
Workaround There is no workaround.
•
Symptoms Digital Signal Processor (DSP) failures to set a codec are not handled correctly.
Conditions This symptom has been observed on a Cisco AS5400 access server or Cisco AS5350 access server Voice over IP (VoIP) topology.
Workaround There is no workaround.
•
Symptoms An input queue wedge error occurs on an ATM interface of a Cisco IAD 2421 Integrated Access Device when the no connect frf575 serial0 75 atm0 0/75 network-internetwork command is configured on a Frame Relay-to-ATM Network Interworking (FRF.5) connection. The input queue (76/75) does not recover if the connect statement is configured again or if the shutdown command is issued and followed by the no shutdown command.
Conditions This symptom is observed when traffic is flowing into the ATM interface where the connect statement is removed.
Workaround Issue the shutdown connect command to disconnect the FRF.5 connection.
•
Symptoms I/O memory fragmentation occurs with various digital signal processor (DSP) timeout errors causing alarms to be triggered.
Conditions This symptom is observed on a Cisco AS5300 with Dual Tone Multifrequency (DTMF) path confirmation enabled.
Workaround There is no workaround.
•
Symptoms Idle channels suppression will not function properly after an AAL2 trunk fails and recovers from PBX failure alarms.
Condition This symptom is observed when an AAL2 trunk is set up with idle channel suppression to save bandwidth on the trunk. After a T1 alarm, the trunk enters out of service (OOS) state. When the T1 alarm is recovered, the trunk recovers. But idle channel suppression is then not seen as active, which does not save bandwidth on the trunk.
Workaround There is no workaround.
•
Symptoms Unexpected long voice delays cause severe voice quality problems.
Conditions This symptom is observed with Voice over IP (VoIP) topologies. This symptom is caused by an incorrect default playout mode.
Workaround There is no workaround.
•
Symptoms A router reloads when sending downstream traffic.
Conditions This symptom has been observed during stress tests with Multilink Point to Point Protocol (MLPPP) call configuration and downstream traffic.
Workaround There is no workaround.
•
Symptoms A device running Cisco IOS software reloads.
Conditions This situation occurs when the cns config initial command is configured with the event keyword option and the initial configuration sends an event message before the event agent starts up.
Workaround There is no workaround.
•
Symptoms Configuring a bind statement multiple times under a serial interface causes the existing ISDN Q.921-User Adaptation (IUA) configurations to be removed.
Conditions This symptom is observed on a Cisco AS5850 that is running the C5850-p9-mz.122-11.T image.
Workaround There is no workaround.
•
Symptoms A voice port does not measure the high idle voltage accurately. The voice port 1/x relays battery-reversal on command and will not send the active low with battery-reversal out if the voice port has idle voltage low configured.
Conditions This symptom is observed on a router that is running Cisco IOS Release 12.2(11)T1.
Workaround There is no workaround.
•
Symptoms A GSM Full Rate (GSMFR) information field size is sent incorrectly as a byte size to the firmware when it should be sent as a 20 ms frame size. The digital signal processor (DSP) will use 40 ms GSMFR frames in voice sessions, which causes a 20ms voice delay in one direction.
Condition This symptom is observed on a router that is running Cisco IOS Release 12.2.
Workaround There is no workaround.
•
Symptoms A gateway that has an ISDN PRI interface does not use T301 as an interdigit timer.
Conditions This symptom is observed on a Cisco gateway that is running Cisco IOS Release 12.2(6g) and that has an ISDN PRI interface that is configured for overlap receiving.
Workaround There is no workaround.
•
Symptoms If a channel-group is removed from an E1 controller using the no channel-group 1 command, then the Signalling Link Terminal (SLT) can restart spontaneously resulting in the loss of connectivity from all ports on the SLT.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(8)T5 or later.
Workaround 1 Copy the running-config from the SLT to an offline location, edit the running-config, copy the running-config back to the SLT as the startup-config, and then reload the SLT.
Workaround 2 Shut down the SLT and remove the E1 or T1 WAN interface card (WIC), start up the SLT and save the running-config, turn off the SLT again, and reinsert the E1 or T1 WIC. When the SLT is started again, the channel groups will have been removed from the running-config.
Resolved Caveats—Cisco IOS Release 12.2(11)T1
Cisco IOS Release 12.2(11)T1 is a rebuild release for Cisco IOS Release 12.2(11)T. The caveats in this section are resolved in Cisco IOS Release 12.2(11)T1 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
Symptoms—A description of what is observed when the caveat occurs.
Conditions—The conditions under which the caveat has been known to occur.
Workaround—Solutions, if available, to counteract the caveat.
•
Symptoms A Cisco AS5300 may reload.
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.1(5)XM.
Workaround Enter the no snmp-server enable traps dial global configuration command.
•
Symptoms The crashinfo file is incomplete, and memory block information is not dumped. Multiple traceback messages may be displayed in the crashinfo file.
Conditions This symptom is observed on a Route Processor Module (RPM) card that has 512 MB of memory when the card dumps the crashinfo file.
Workaround There is no workaround.
•
Symptoms After the aaa accounting send stop-record authentication failure global configuration command is configured, a successful PPP call may generate two stop records.
Conditions This symptom is observed on a Cisco AS5850 that is running Cisco IOS Release 12.2(2)XB if Link Control Protocol (LCP) renegotiates after the authenticating phase has started.
Workaround There is no workaround.
•
Symptoms With continuous traffic and the calls being cleared regularly, over a period of time outgoing calls may fail.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms If a call is terminated after the aaa accounting resource default stop-failure group radius global configuration command is enabled, authentication, authorization, and accounting (AAA) resource accounting may not generate a stop record before a user is authenticated.
Conditions This symptom is observed on a Cisco AS5300.
Workaround There is no workaround.
•
Symptoms A virtual private dial-up network (VPDN) may ignore the configured source IP address and default to the primary IP address of the tunneling interface.
Conditions This symptom is observed on a Cisco AS5400 when VPDN is configured locally on the Cisco AS5400.
Workaround There is no workaround.
•
Symptoms Under load or stress conditions for Voice calls with E1R2 signaling, the following negative acknowledgments (NAKs) are observed on the terminating gateway (TGW).
UTC: %NP-3-NAKRSP: NAK Response Received - command 0x1500, result code 0x8005, msg id 0x15FF, session id 0x1EB, msg tag 0x0, slot/port 4/59
UTC: %NP-3-NAKRSP: NAK Response Received - command 0x1500, result code 0x8005, msg id 0x15FF, session id 0x2C2, msg tag 0x0, slot/port 6/58The overall effect on the call success rate (CSR) is about 1 percent or less.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms The output of the show isdn active EXEC command displays two entries for each Personal Handyphone System (PHS) Internet Access Forum Standard (PIAFS) call.
Conditions This symptom is observed on a Cisco 800 series that is running Cisco IOS Release 12.2(8)T4.
Workaround There is no workaround.
•
Symptoms A router may stop reusing virtual interfaces after the virtual interfaces have been used for a few times.
Conditions This symptom is observed on a Cisco router that is handling a high volume of short-duration calls.
Workaround There is no workaround.
•
Symptoms A router may reload because of an ISDN memory leak.
Conditions This symptom is observed when Signaling System 7 (SS7) calls are made between an originating and a terminating gateway. The symptom is observed when the underlying physical layer is unstable. This may include instances when Layer 2 and Layer 3 bounce at regular intervals. This memory leak does not occur under normal SS7 working conditions when Layers 2 and 3 are stable.
Workaround There is no workaround.
•
Symptoms After a router is rebooted, the "VPDN group" configuration is removed.
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(2)XB6.
Workaround There is no workaround.
•
Symptoms After RADIUS servers are reloaded, the resource manager state is not set to idle and no calls can be received.
Conditions This symptom is observed on a Cisco AS5400.
Workaround Reload the RADIUS servers again.
•
Symptoms A router may drop an event message if the connection to the Tag Information Gate Base (TIB) gate is down when the send attempt is executed.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2 T.
Workaround There is no workaround.
•
Symptoms A Cisco AS5850 sends the same Media Gateway Control Protocol (MGCP) network access server (NAS) error code of 808 when a controller is shut down and a modem line is cleared.
Conditions This symptom is observed on a Cisco AS5850 that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms The network access server (NAS) port name on the TACACS server may be reported incorrectly for a digital call that is terminated on a NextPort; ISDN may be reported as asynchronous. No other types of calls are affected, and the RADIUS server works fine.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms When you configure the no transport tcp SIP user-agent configuration command under the sip-ua global configuration command, save the configuration using the write EXEC command, and reload the router, the no transport tcp SIP user-agent configuration command is no longer in the configuration when the router has come back up.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(2)XB5.
Workaround Reenter the command after the router has reloaded.
•
Symptoms A Media Gateway Control Protocol (MGCP) modem pass-through call may fail with a Cisco Call Manager.
Conditions This symptom is observed on a Cisco 3700 series router when the codec complexity is high. When the codec complexity is medium, the same configuration works fine.
Workaround There is no workaround.
•
Symptoms Authentication, authorization, and accounting (AAA) stop records may report 0 in acct_output_octets and acct_input_octets, even when large amounts of data have been transferred by the session.
Conditions This symptom is observed on a Cisco AS5850.
Workaround Retrieve the information using the spe call-record modem, modem call-record, and calltracker call-record global configuration commands
•
Symptoms An ATM interface may have an incorrect Iftype object (DS1 instead of ATM), which may cause the ATM Service Level Measurement (SLM) feature to be inoperable with third-party software.
Conditions This symptom is observed on a Cisco 2600 series router.
Workaround There is no workaround.
•
Symptoms When an attempt is made to acquire new MIB values, Simple Network Management Protocol (SNMP) responds with a "no such name" message and the MIB variables are not displayed.
Conditions This symptom is observed with Cisco IOS Release 12.2(2)XB5.
Workaround There is no workaround.
•
Symptoms An FTP session may pause indefinitely while compressed files such as zip files are transferred.
Conditions This symptom is observed on a Cisco 3600 series router when a vendor-specific compression protocol is enabled.
Workaround There is no workaround.
•
Symptoms The "PPP Endpoint go" process may leak memory blocks in certain Virtual Private Network (VPN) forwarding configurations.
Conditions This symptom is observed on a Cisco AS5300 when PPP is used.
Workaround There is no workaround.
•
Symptoms A choppy voice signal occurs just after call setup. Consequently, the person on the connected side cannot hear the top of the voice.
Conditions This symptom is observed on a Cisco gateway that is running Cisco IOS Release 12.2 T on the calling side. The symptom does not occur in Cisco IOS 12.2 mainline releases.
Workaround Use a Cisco IOS 12.2 mainline release.
•
Symptoms Terminal Window PPP authentication may fail with the authentication, authorization, and accounting (AAA) "if-needed" method.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms A user may be able to connect to another customer or group via Virtual Private Network (VPN) because Extended Authentication (Xauth) itself is a global procedure.
Conditions This symptom is observed when the service provider has one global authentication, authorization, and accounting (AAA) server where the user is doing both authorization and authentication.
The issue is that XAUTH is independent of the actual VPN client group. Authentication should only be permitted if the user belongs to the group to which he is trying to connect. To tie the user to his correct group, the username entered during Xauth should be in the form of username/group, username\group, username@group, or username%group.
The value of the group must match the group to which the user is trying to connect. In addition, the username must be stored in one of the above formats in RADIUS or in the local router configuration.
If the user enters no groupname and, for example, there is a match in RADIUS, Xauth will succeed. There should be only username/group type names in the AAA database so that the group value can be validated by both AAA and the router.
Workaround There is no workaround.
•
Symptoms Calls may have only one-way audio. There may be calls for which the digital signal processor (DSP) is not responding to Cisco IOS messages and an additional debug points to the fact that a voice path is available only in one direction.
Conditions This symptom is observed on a Cisco AS5300.
Workaround There is no workaround.
•
Symptoms A Cisco 3725 router may report to be in an "Up/Up" status when it is connected to a third-party vendor ATM equipment, but input packets may not be displayed in the output of the show interfaces atm slot/port privileged EXEC command. Far End Block Error (FEBE) errors may also be reported in the output of the show controllers atm slot/port privileged EXEC command:
DS3/E3: G.832 FEBE errors 2434963 DS3/E3: G.832 FEBE errored secs 656Conditions This symptom is observed on a Cisco 3725 router.
Workaround There is no workaround.
•
Symptoms The modemcap AT command string may be in the input buffer of a line when the line comes up. As a result, this string—rather than actual user data received from the client modem—may be used for character mode authentication.
Conditions This symptom is observed on a Cisco AS5800 that has autoconfiguration enabled on the modem lines.
Workaround Enter the no flush-at-activation command.
•
Symptoms A V.110 call fails when it is time-division multiplexing (TDM)-switched from an inbound Signaling System 7 (SS7) trunk to an outbound SS7 trunk, or from an inbound PRI trunk to an outbound PRI trunk.
Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(11).
Workaround There is no workaround.
•
Symptoms A router may reload.
Conditions This symptom is observed on a Cisco 2600 series router and a Cisco 3600 series router that are running a combined H.323 gatekeeper/gateway image (-jsx-) and when the H.323 interface is being disabled using the no h323 interface configuration command while traffic is running.
Workaround Shut down the gateway first by issuing the no gateway global configuration command, or run the gatekeeper on a separate image (-ix-).
•
Symptoms A router may reload before ISDN/User Adaptation (IUA) layer association when Stream Control Transmission Protocol (SCTP) backhauling is used.
Conditions This symptom is observed on a Cisco AS5850.
Workaround If the call agent supports it, use Reliable User Data Protocol (RUDP) backhauling. The call agent must support RUDP backhauling for this workaround to be usable.
•
Symptoms The port information provided on a Cisco AS5350, Cisco AS5400, and Cisco AS5850 on modems within RADIUS attribute 5 using either NAS-port format a or b for asynchronous calls provides the true port information (as in slot/port) and not the TTY line number of the modem that previous-generation dial platforms provided. This causes difficulties for service providers that use a variety of Cisco dial platforms because the platforms are inconsistent in the information that they relay.
Conditions This symptom is observed on a Cisco AS5350, Cisco AS5400, and Cisco AS5850.
Workaround There is no workaround.
•
Symptoms Cisco Fax Relay and modem pass-through cannot be configured at the same time in a Cisco CallManager Media Gateway Control Protocol (MGCP) environment. When MGCP modem pass-through is configured, it overwrites the Cisco Fax Relay for MGCP in the Cisco CallManager.
Conditions This symptom is observed on a Cisco 3600 series router in a Cisco CallManager MGCP environment.
Workaround There is no workaround.
•
Symptoms Policy-based routing (PBR) does not work on a router if Cisco Express Forwarding (CEF) is enabled.
Conditions This symptom is observed on a Cisco 1700 series that is running Cisco IOS software images that have the -sy feature set.
Workaround Disable CEF.
•
Symptoms An ATM Adaptation Layer 2 (AAL2) permanent virtual circuit (PVC) does not come up when managed by Operation, Administration, and Maintenance (OAM) cells. The number of packets received for AAL2 is also incorrect.
Conditions This symptom is observed on a Cisco MC3810 that is running Cisco IOS Release 12.2(10.7)T4.
Workaround There is no workaround.
•
Symptoms Under heavy load conditions, Frame Relay traffic shaping may cause a router to reload with tracebacks.
Conditions This symptom is observed on a Cisco 2600 series router.
Workaround There is no workaround.
•
Symptoms A general call success rate (CSR) degradation may occur on an access router.
Conditions This symptom is observed on a Cisco AS5800 that is running the c5800-p4-mz image of Cisco IOS Release 12.2(10.7)T4. All CSRs observed after running an E1 PRI connection from 5 E1s to 16 E1s are in the low 90-percent range.
Workaround There is no workaround. The earlier Cisco IOS Release 12.2(9.4)PI4 image consistently generates a 99-percent CSR.
•
Symptoms When a router is set up for ATM Adaptation Layer 2 (AAL2) trunking for 24 G.726 voice calls with no voice activity detection (VAD), CPU utilization is up to 90 percent, which is 20 percent higher than for an image of Cisco IOS Release 12.2(2)XB5.
Conditions This symptom is observed on a Cisco MC3810 that is running Cisco IOS Release 12.2(10.7)T4.
Workaround There is no workaround.
•
Symptoms An ATM Adaptation Layer 2 (AAL2) permanent virtual circuit (PVC) does not come up when managed by Operation, Administration, and Maintenance (OAM) cells. The number of packets received for AAL2 is also incorrect.
Conditions This symptom is observed on a Cisco MC3810 that is running Cisco IOS Release 12.2(10.7)T4.
Workaround There is no workaround.
•
Symptoms The Survivable Remote Site Telephony (SRST) feature does not function on the Cisco Catalyst 4000 Access Gateway Module.
Conditions This symptom is observed on all Cisco Catalyst 4000 Access Gateway Module images.
Workaround There is no workaround.
•
Symptoms The received uncompressed bytes counter in the output of the show compression EXEC command is not accumulated correctly. The received uncompressed bytes counter should show the number of the received compressed bytes that cannot be decompressed and the number of bytes that have been decompressed.
Conditions This symptom is observed on a Cisco 3660 router.
Workaround There is no workaround.
•
Symptoms When a "telephone.disconnect.hangup" event is detected by a catch handler in a subdialog, the call control is not returned to the original calling dialog. Thus the event is not returned to the calling dialog.
When a call is disconnected and a catch handler defined in the subdialog, the expected behavior is that the event is caught by the catch handler. If a return is specified in the subdialog, the call control is returned from the subdialog to the calling dialog. The calling dialog is then left to determine how the event that is returned should be handled.
Conditions This symptom is observed when the disconnect event is caught by the catch handler of a subdialog.
Workaround There is no workaround.
•
Symptoms A router may go into a rebooting loop during startup.
Conditions This symptom is observed on an integrated access device (IAD) router that is running Cisco IOS Release 12.2(8)T during startup if the boot host tftp: global configuration command is configured and someone attempts to log on to the console using TACACS.
Workaround There is no workaround.
•
Symptoms When hardware encryption is enabled for IP phone-to-IP phone calls on two different Cisco IOS Telephony Service (ITS) gateways, there is only a one-way voice path.
The data start pointer is not adjusted after the MAC header is added to the packet in the IP phone code (ephone_send_packet). Some Ethernet drivers rely on this pointer. If the pointer is not set, these Ethernet drivers cause malformed frames to be sent out onto the Ethernet, resulting in no voice connectivity.
Conditions This symptom is observed on a Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series router.
Workaround Disable hardware encryption or use process switching.
•
Symptoms High CPU utilization may occur when calls are made using ATM Adaptation Layer 2 (AAL2) trunking. The CPU utilization may be as high as 17 percent per call, which allows for no more than six simultaneous G.711 calls.
Conditions This symptom is observed on a Cisco 3600 series router that is running Cisco IOS Release 12.2(10.7)T5 and that is configured with an Inverse Multiplexing Over ATM (IMA) or High Density Voice network module. The symptom is also observed on a Cisco 3745 router.
Workaround There is no workaround.
•
Symptoms When a Route Processor Module version B (RPM/B) card is switched with a Route Processor Module-PRemium (RPM-PR) card, short flaps may be observed on the provider-edge-to-provider-edge (PE-PE) connections on a network.
Conditions This symptom is observed on the RPM-PR card when a permanent virtual circuit (PVC) is configured by entering the oam-pvc manage 1 VC-class configuration command.
Workaround Stop Operation, Administration, and Maintenance (OAM) loopback cells from being generated by entering the oam-pvc manage 0 VC-class configuration command.
•
Symptoms A router does not send RADIUS connection accounting attribute 46 for TCP clear calls or for any outbound Telnet connections.
Conditions This symptom is observed in Cisco IOS Release 12.2(2)XB and Release 12.2(4)T and in later Cisco IOS releases. This symptom occurs only with regular PPP calls over a Telnet connection. Accounting records do contain this attribute.
Workaround There is no workaround.
•
Symptoms A router may reload when the following sequence of steps is performed on a Cisco IE2100 series configuration registrar:
–
–
–
Conditions This symptom is observed on a Cisco IE2100 series.
Workaround To prevent this symptom from occurring, configure the cns config partial global configuration command on an SSL port on which the Cisco IE2100 series is set up with SSL.
•
Symptoms Extensible markup language (XML) tags that are advertised from a router have a third-party vendor prefix, which makes them specific for this third-party vendor.
Conditions This symptom is observed on a Cisco MC3810, Cisco 2600 series, Cisco IAD2420 series, and Cisco 3660 router.
Workaround There is no workaround.
•
Symptoms The AOC-E facility information element (IE) is not passed across Voice over IP (VoIP) links if the AOC-E facility IE is received as part of an ISDN release message.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(6a).
Workaround There is no workaround.
•
Symptoms Access Gateway Module (AGM) fails to boot. The following output is captured from the console:
%MGCP-3-INTERNAL_ERROR: Not able to create the profile
Unexpected exception to CPU vector 0, PC = 80FB1B90
-Traceback= 80FB1B90 80356DBC
=== Flushing messages ===
*** System received a SegV exception ***
signal= 0xb, code= 0x0, context= 0x81be49f8
PC = 0x80fb1b90, Vector = 0x0, SP = 0x824e7c80Conditions This symptom occurs when the following two conditions are met:
a.
b.
Note that in condition b we are not using the colon (:) between the flash keyword and the filename argument.
Workaround You must have console access. You need to send the control-break sequence to get the AGM in ROM monitor (ROMMON) mode. Once in ROMMON mode, set the configuration to 0x2142. Reset the module. Copy the startup configuration to the running configuration and change the configuration back to 0x2102.
•
Symptoms A Voice over IP (VoIP) connection does not pass the Advice of Charge at the end of the call (AOC-E) facility information element (IE) transparently when the AOC-E facility IE is included with a progress indicator in the DISCONNECT message.
Conditions This symptom is observed when the progress indicator IE and a facility IE are part of a DISCONNECT message.
Workaround There is no workaround.
•
Symptoms On a Cisco Voice Gateway, a number translation that is using the translation-rule rule-tag command-line interface (CLI) global configuration command may not work.
Conditions This symptom is observed on a Cisco Voice Gateway that is using an interactive voice response (IVR) version 2.0 application such as "application session."
Workaround There is no workaround.
•
Symptoms A fax may be transmitted using pass-through even though Cisco Fax Relay has been selected.
Conditions This symptom is observed on a Cisco 3600 series router that is running Cisco IOS Release 12.2(11)T when a modem tone is detected before a fax tone and an upspeed occurs because of the modem tone.
Workaround There is no workaround.
•
Symptoms With Cisco Fax Relay configured as the fax method of choice on the Cisco CallManager, the originating gateway (OGW) ignores the signal to switch to Cisco Fax Relay. The traces imply that Cisco Fax Relay is not supported.
Conditions This symptom is observed on a Cisco CallManager Media Gateway Control Protocol (MGCP) gateway that has Cisco Fax Relay configured as the fax method of choice.
Workaround There is no workaround.
•
Symptoms A Multirate Symmetrical High-Speed Digital Subscriber Line (G.SHDSL) may be reset every three to four days. Although the line comes up normally after the reset occurs, line service may be interrupted.
Conditions This symptom is observed when a Cisco 2600 router is connected to a vendor-specific digital subscriber line access multiplexer (DSLAM) that has a G.SHDSL.
Workaround There is no workaround.
•
Symptoms The keepalive and source command parameters may be switched, rendering the cns event global configuration command unreadable by the parser at the next router reload. This will cause loss of manageability of the router.
Conditions This symptom is observed after a router has reloaded and the cns event ip-address keepalive seconds retry-count source ip-address global configuration command is generated as the cns event ip-address source ip-address keepalive seconds retry-count global configuration command in NVGEN. The cns event global configuration command works correctly until the router is reloaded.
Workaround Reenter the cns event global configuration command each time the router reloads.
•
Symptoms A router may reload and display traceback messages that are related to the mgcpapp_process_ccapi_ev process.
Conditions These symptoms are observed on a Cisco router.
Workaround There is no workaround.
•
Symptoms A router may reload.
Conditions This symptom is observed when you leave an EXEC Secure Shell (SSH) session by entering the exit command-line interface (CLI) command when Connection Accounting is enabled.
Workaround Terminate the line using the clear line-number EXEC CLI command.
•
Symptoms A router may reload if prompts are played while automatic speech recognition (ASR) and text-to-speech (TTS) are not configured on the command-line interface (CLI) and ASR and TTS properties are not set in the voice extensible markup language (VXML) document.
Conditions This symptom is observed on a Cisco AS5300.
Workaround Configure ASR and TTS using the CLI.
•
Symptoms After a TCP connection is terminated, the TCP transmissions that are sent by a router are corrupted. The last 6 bytes of the IP header are duplicated in the packet and appear as the first 6 bytes of the TCP header.
Conditions This symptom is observed on the outgoing interface of a Cisco router that is running Multilink PPP (MLP).
Workaround Disable MLP.
•
Symptoms An error event is "thrown" when a prompt that is used in a field item fails. If another automatic speech recognition (ASR) session is started in the catch handler for the error event, the catch handler will fail because the previous session has not been terminated.
Conditions This symptom is observed on voice platforms that support the ASR/text-to-speech (TTS) feature. This symptom may affect platforms such as the Cisco 3660, Cisco AS5300, Cisco AS5350, and Cisco AS5400 that are running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A Cisco router may reload because of a bus error.
Conditions This symptom is observed when a Service Assurance Agent is configured using the Simple Network Management Protocol (SNMP) through a "Create and Wait" operation. The rttMonEchoAdminOwner or rttMonEchoAdminTag variable is set using this "Create and Wait" operation.
Workaround To configure the Service Assurance Agent, use one of the following three solutions:
–
–
–
For more information about bus errors, refer to the Cisco document at the following location:
http://www.cisco.com/warp/public/122/crashes_buserror_troubleshooting.shtml
•
Symptoms If an established 3-way Media Gateway Control Protocol (MGCP) call is taken out of the conference mode and placed back into the conference mode, the call may disconnect, or the voice path may be dropped.
The call disconnects if the controller party flashes the hook and then goes on-hook. The voice path is dropped if the controlling party flashes the hook and dials the number 3 to put the call back into the conference mode.
Conditions This symptom is observed on a Cisco IAD2420 series.
Workaround There is no workaround.
•
Symptoms An echo may be heard on the Voice over IP (VoIP) side of a call.
Conditions This symptom is observed on a Cisco 3640 router that is running Cisco IOS Release 12.2(11.8)T and that is configured with a VIC-2FXO-M1 card.
Workaround Replace the VIC-2FXO-M1 card with a VIC-2FXO card. The echo does not occur with a VIC-2FXO card.
Alternate Workaround Run Cisco IOS Release 12.2(8)T5 or Release 12.2(9.4)T.
•
Symptoms Built-in and external grammars may not work on a vendor-specific automatic speech recognition (ASR) server.
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms PPP may drop serial interfaces after the PPP session is forwarded.
Conditions This symptom is observed when PPP is used on a Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC).
Workaround There is no workaround.
•
Symptoms A Cisco AS5300 may reload when it is initialized with a stack overflow error for Dynamic Host Configuration Protocol (DHCP) and the port dial-peer configuration command is present in the configuration file that is downloaded from a TFTP server. The following is a sample configuration that may cause the reload to occur:
dial-peer voice 10 pots
destination-pattern .T
direct-inward-dial
port 0:D
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(11)T3.
Workaround Remove the line in the configuration file that contains the port dial-peer configuration command. Configure the port dial-peer configuration command manually after the autoinstall process has completed.
•
Symptoms On a Cisco AS5850, upstream (ingress-to-egress) traffic that is sent through a single-link asynchronous Multilink PPP (MLP) call is process-switched instead of being switched by Cisco Express Forwarding (CEF). This symptom may cause high CPU utilization on the Route Switch Controller (RSC) when MLP data is forwarded. Data integrity is not affected when this symptom occurs.
Conditions This symptom is observed on a Cisco AS5850 that is running Cisco IOS Release 12.2(2)XB6C. Only single-link asynchronous MLP calls are affected by this symptom. All digital calls, non-MLP calls, and all MLP calls that have more than one link are not affected.
Workaround There is no workaround.
•
Symptoms The PRI dial-modifier feature does not work as expected on a Cisco AS5400.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A Cisco AS5850 Media Gateway Control Protocol (MGCP) universal gateway does not send a slot number in the endpoint name when an MGCP NTFY message is sent.
Conditions This symptom is observed with MGCP channel-associated signaling (CAS) calls if a feature board is installed in slot 0.
Workaround Use a slot other than slot 0.
•
Symptoms The RADIUS NAS-Port attribute 5 does not report the TTY number of the asynchronous interface that is used for the modem-based call.
Conditions This symptom is observed when the radius-server attribute nas-port format a global configuration command is configured and authentication, authorization, and accounting (AAA) is tracking the modem-based call.
Workaround There is no workaround.
•
Symptoms Leakage at the I/O memory may cause memory allocation (MALLOC) failures on a Cisco AS5400.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(2)XB6.4 regardless of the load conditions.
Workaround There is no workaround.
•
Symptoms The Media Gateway Control Protocol (MGCP) error code 502 may be observed on MGCP platforms, and calls may not be established successfully.
Conditions This symptom is observed when a gateway that is running Cisco IOS Release 12.2(11)T attempts to negotiate both named telephone events (NTEs) and X-named signal events (NSEs) with a gateway that is running Cisco IOS Release 12.2(8)T.
Workaround Upgrade to Cisco IOS Release 12.2(11)T.
•
Symptoms When a voice port is configured with the Hong Kong (HK) ringing tone (cptone), the off-hook warning tone does not play as expected.
Conditions This symptom is observed on a Cisco IAD2420 series that is running Cisco IOS Release 12.2(10.7)T4.
Workaround There is no workaround.
•
Symptoms Network Address Translation (NAT) may drop H.323 version 3 and version 4 packets because H.323 versions 3 and 4 are not supported.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A router may stop detecting routes when IP version 6 (IPv6) Routing Information Protocol (RIP) is used on a tunnel.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A Cisco AS5800 may reload because of the outb-telnet_aaa_acct_get_dynamic_attrs routine.
Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(2)XB6.
Workaround There is no workaround.
•
Symptoms A Cisco AS5300 may reload when it is accessing an illegal address (0xDEADBEF7).
Conditions This symptom is observed on a Cisco AS5300 when a user attempts to send a TACACS+ accounting packet for a network or PPP connection.
Workaround There is no workaround.
•
Symptoms No ringback tone is heard when a hairpin call is made from a Foreign Exchange Station (FXS) port to the T1 port of a Cisco IAD2421 integrated access device.
Conditions This symptom is observed on a Cisco IAD2421 that is running Cisco IOS Release 12.2(11)T.
Workaround Configure the no voice local-bypass global configuration command to prevent hairpin calls from being made.
•
Symptoms The G.729 codec selection option cannot be configured for Voice over IP (VoIP) dial peer on an Access Gateway Module (AGM) that is operating in the IP telephony mode.
Conditions This symptom is observed on an Access Gateway Module (AGM) for Catalyst 4000 series switch (WS-X4604-GWY).
Workaround There is no workaround.
•
Symptoms The ISDN User Part (ISUP) trunk package cannot be configured on a Media Gateway Control Protocol (MGCP) trunking gateway. This symptom prevents MGCP trunking gateways from being compliant with Trunking Gateway Control Protocol (TGCP) call agents that require the ISUP trunk package as the default trunking package.
When the configure terminal privileged EXEC command is entered, the mgcp package-capability package global configuration command erroneously omits the it-package option. Similarly, the mgcp default-package global configuration command omits the it-package option.
If the ISUP trunk package is not configured, call agents that shorten it-package requests may encounter failures. For example, "R: IT/ft" may be replaced with "R: ft" if the ISUP trunk package is configured as the default. Because the ISUP trunk package cannot be configured as the default package, "R: ft" will fail.
The biggest ramification of this symptom is noncompliance with TGCP call agents. The inability to configure "it-package" as the default package also means that an alternate package must be used as the default trunk package. The trunk package or generic media package are possible substitutes, but neither has the complete set of events that are present in the "it-package." This circumstance means that the call agent may encounter failures with the "it-package" functionality.
Conditions This symptom is observed on a Cisco IAD2421 integrated access device that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms The no boot system global configuration command does not work when it is entered on a redundant primary Route Processor Module (RPM) card.
Conditions This symptom is observed on an RPM card of a Cisco router that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms Public switched telephone network (PSTN) fallback cannot be configured on a Cisco Catalyst 4000.
Conditions This symptom is observed on a Cisco Catalyst 4000 that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A PRI trunk may go out of service. This symptom occurs when an inbound call from a PBX is received on a PRI trunk and when an access code is dialed to access the PBX (the same PBX that originated the call). Subsequent calls that are made on the PRI trunk do not go through.
Conditions This symptom is observed on a PRI trunk when calls are hairpinned on a Catalyst 4000 Access Gateway Module (AGM) that is running the c4gwy-io3sx3-mz.122-10.7.T6 image of Cisco IOS Release 12.2(10.7)T6.
Workaround Restart the controller or reload the router.
•
Symptoms A Cisco AS5400 may not send Restart in Progress (RSIP) messages to the Call Agent.
Conditions This symptom is observed when an E1 cable is unplugged from the Cisco AS5400, causing a Loss of Signal (LOS) on the line.
Workaround There is no workaround.
•
Symptoms The end-to-end delay for an access server may be greater than the delay for a Voice Interworking Service Module (VISM). This end-to-end delay is unacceptable.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms A call is rejected by call admission control (CAC) because of unavailable resources. External Call Service Provider (XCSP) calls may pause in the in-progress state, and no new calls can be made on the given DS0 channel.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms A Media Gateway Control Protocol (MGCP) dial call that is terminated is not deleted from the memory of the Cisco AS5350 after the connection is deleted.
Conditions This symptom is observed on a Cisco AS5350 that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
Resolved Caveats—Cisco IOS Release 12.2(11)T
All the caveats listed in this section are resolved in Cisco IOS Release 12.2(11)T. This section describes only severity 1, severity 2, and select severity 3 caveats.
These caveats are documented in the following format:
•
•
•
Access Server
•
Symptoms A modem configuration may fail.
Conditions This symptom is observed on a Cisco AS5850 when a modem capability (modemcap) is used to modify the NextPort register configuration.
Workaround Apply the same modemcap from a reverse Telnet to the NextPort.
Basic System Services
•
Symptoms You cannot specify a loopback interface to use in relation with Cisco Discovery Protocol (CDP) IP information. Campus Manager, which is a CDP-based discovery tool, cannot use loopback addresses for discovery purposes.
Conditions This symptom is observed on all platforms.
Workaround Upgrade to the latest CiscoWorks 2000 (CD-1 4th Edition, RME 3.3, Campus Manager 3.1) and follow the information at the following location:
http://www.cisco.com/warp/public/cc/pd/wr2k/cpmn/prodlit/wk2ke_wp.htm
•
Symptoms Multichassis Multilink PPP (MMP) Media Gateway Control Protocol (MGCP) calls do not work because of authentication failures.
Conditions This symptom is observed on a Cisco AS5400.
Workaround Use local authentication by enabling the aaa authentication ppp default local global configuration command.
Alternate Workaround If RADIUS authentication is used, omit the "class" attribute from the RADIUS user profile.
•
Symptoms The RADIUS music on hold (MOH) per-user attribute does not function for EXEC and Layer 2 Tunneling Protocol (L2TP) users: the attribute is discarded. The attribute is working fine for PPP users.
Conditions This symptom is observed on a Cisco AS5400.
Workaround Use a modem capability (modemcap) to define a default setting for all EXEC and L2TP users.
•
Symptoms Digital calls should be reported as port type "isdn sync", but some digital calls are reported incorrectly as port type "async". This affects only digital calls that terminate on digital signal processors (DSPs).
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms IP Control Protocol (IPCP) may be rejected when a Virtual Access interface is created for attributes (such as the "route" attribute) that are global per-user attributes. The Virtual Access interface does not contain IP configurations because no Virtual Template has been configured.
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(9.4)T or Release 12.2(6.8)PIa.
Workaround Create a Virtual Template and configure the virtual-profile virtual-template number global configuration command.
•
Symptoms A route switch controller (RSC) reloads upon modem call setup.
Conditions This symptom is observed when an asynchronous interface is configured for interactive mode and a RADIUS server is configured to download an IP address pool to the network access server (NAS).
Workaround Do not configure the RADIUS server to download an IP address pool.
•
Symptoms A router may not make any attempt to authenticate from the authentication, authorization, and accounting (AAA) server, and messages similar to following may be recorded:
AAA/AUTHEN/PPP (00000023): Pick method list 'default'
As61 PPP: Sent MSCHAP LOGIN Request to AAA
TPLUS: Queuing AAA Authentication request 35 for processing
TPLUS: processing authentication start request id 35
As61 PPP: Received LOGIN Response from AAA = FAILConditions This symptom is observed in a router that is running Cisco IOS Release 12.2(4)T3 and that is using MS-CHAP authentication for the TACACS+ server.
Workaround There is no workaround.
•
Symptoms Multichassis Multilink PPP (MPP) sessions do not report RADIUS accounting on the basis of the respective network access server (NAS) that is serving the B channel.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms Two RADIUS accounting stop records are sent to the RADIUS server for a "1-B channel V.120" call.
Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(2)XB5.
Workaround There is no workaround.
•
Symptoms A RADIUS authentication, authorization, and accounting (AAA) accounting stop record may have negative values of presession packets when a V.120 call is disconnected.
Conditions This symptom is observed on a Cisco AS5800 that is running a Cisco IOS release that is earlier than Cisco IOS Release 12.2(2)XB5.
Workaround There is no workaround.
•
Symptoms In a configuration that includes a Large Scale Dial Out (LSDO) with Multilink PPP (MLP), an outbound ping from an enterprise router to a remote client router passes, and multiple links and dialer sessions come up successfully at a Cisco AS5300 that is functioning as a network access server (NAS). However, if you enter the clear dialer session EXEC command on the NAS while dialer sessions are still active, the NAS reloads at aaa_acct_send_req.
Conditions This symptom is observed on a Cisco AS5300 that is running the c5300-js-mz of Cisco IOS Release 12.2(9.4)T.
Workaround Use an LSDO without MLP.
•
Symptoms High CPU utilization may occur on a router, causing the router first to pause and then to reload.
Conditions This symptom is observed on a Cisco uBR7246 router that is running Cisco IOS Release 12.1(9)EC.
Workaround Enter the no snmp-server manager global configuration command to disable the internal Simple Network Management Protocol (SNMP) server.
•
Symptoms A system accounting record is not sent when a hidden command-line interface (CLI) is configured and the RADIUS server is deleted from the configuration.
Conditions This symptom is observed on a Cisco 7200 series router that is running Cisco IOS Release 12.2(6.4)T.
Workaround Configure (add or delete) the RADIUS server from a nonconsole line.
•
Symptoms A network access server (NAS) may reload when a non-multisession call comes in.
Conditions This symptom is observed on a NAS when the ppp multilink interface configuration command is not configured.
Workaround Configure the ppp multilink interface configuration command.
•
Symptoms A class attribute may not be found in the start and stop accounting records on a home gateway when the vpdn aaa attribute class tunnel-class global configuration command is configured.
Conditions This symptom is observed on a Cisco 7200 series router.
Workaround There is no workaround.
•
Symptoms A ppp authorization interface configuration command that is defined under a template does not reference a globally defined nondefault method list of an authentication, authorization, and accounting (AAA) authorization network.
Conditions This symptom is observed on a Cisco AS5400.
Workaround Enter the aaa authorization network default group radius global configuration command in the configuration of the network access server (NAS).
•
Symptoms Authentication, authorization, and accounting (AAA) route download does not work when a router reloads.
Conditions This symptom is observed on a Cisco 6400 Node Route Processor 1 (NRP1) that is running Cisco IOS Release 12.2(4)B3. The symptom has been reproduced in Cisco IOS Release 12.2(4)T3.
Workaround To enable the route download, enter the no aaa route download time global configuration command followed by the aaa route download time global configuration command.
•
Symptoms The "Ascend PW-Lifetime" RADIUS attribute is not supported.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(9.4)P14.
Workaround There is no workaround.
•
Symptoms The "Ascend-Shared-Profile-Enable" RADIUS attribute is not supported.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(9.4)P14.
Workaround There is no workaround.
•
Symptoms A router may reload at radius_build_packet() after a couple of hours of stress tests running analog, ISDN, and Layer 2 Tunneling Protocol (L2TP) calls.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(02)XB05.
Workaround There is no workaround.
•
Symptoms Simple Network Management Protocol (SNMP) traps may stop working after configuration changes are made.
Conditions This symptom is observed on a Route Switch Processor (RSP).
Workaround There is no workaround.
•
Symptoms Users may be assigned IP addresses from a nonspecified pool.
Conditions This symptom is observed when users are assigned an IP address with Ascend-IP-Assign-Pool attribute 218 in the user profile and when all addresses in the specified pool are exhausted.
Workaround There is no workaround.
•
Symptoms An attribute 195 may be sent for users, which is not correct.
Conditions This symptom is observed on a Cisco AS5400 when users are disconnected because of an idle timeout or a session timeout.
Workaround There is no workaround.
•
Symptoms T.38 fax traffic is missing the NAS-Port in the accounting request for the telephony leg.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms Incorrect RADIUS disconnect cause codes may be sent while the PPP idle timeout is tested on the serial interface of a Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC).
Conditions This symptom is observed on a Cisco 7200 series router that is running Cisco IOS Release 12.2(10.3)T2.
Workaround There is no workaround.
•
Symptoms A server may report the absence of an access list after the server has rebooted.
Conditions This symptom is observed on a network access server (NAS) that is running Cisco IOS Release 12.2(02)XB05.
Workaround There is no workaround.
•
Symptoms A Cisco AS5850 may reload.
Conditions This symptom is observed on a Cisco AS5850 Route Switch Controller (RSC) when Multilink PPP (MLP) calls are torn down by clearing a D-channel interface on the caller side. The symptom is seen in Cisco IOS Release 12.2(2)XB5 with authentication, authorization, and accounting (AAA) configured.
Workaround There is no workaround.
•
Symptoms A RADIUS attribute 69 that has special characters defined may fail in decryption.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(02)XB05.
Workaround There is no workaround.
•
Symptoms Digital service zero (DS0) information may not be reported in authentication, authorization, and accounting (AAA).
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms The disconnect cause in attribute 195 may be reported as "no reason."
Conditions This symptom is observed on a Cisco AS5400 when Windows NT clients are disconnected in a normal way.
Workaround There is no workaround.
•
Symptoms A network access server (NAS) may generate an extra stop accounting record for an ISDN Multilink PPP (MLP) call.
Conditions This symptom is observed on a NAS that is running Cisco IOS Release 12.2(02)XB05.
Workaround There is no workaround.
•
Symptoms Copying the configuration of a router from a TFTP server to the running configuration via Simple Network Management Protocol (SNMP) may fail, and the following error message may be displayed:
SNMP error: (genError) A general failure occurred..Copying the configuration of a router via the command-line interface (CLI) works properly.
Conditions This symptom is observed on a router that is running Cisco IOS Release 12.2(10.5)T. The symptom is not seen in Cisco IOS Release 12.2(9.4)T or in earlier releases.
Workaround There is no workaround.
•
Symptoms The internal application programming interface (API) may return wrong values for IfType and IfSubType on an E1 controller.
Conditions This symptom is observed on a Cisco MC3810 that is running Cisco IOS Release 12.2(10.7)T.
Workaround There is no workaround.
•
Symptoms Service Level Measurements feature measurements cannot be made on a Frame Relay Service (FRF.8) encapsulation-type circuit.
Conditions This symptom is observed on a Cisco 3810 router.
Workaround There is no workaround.
•
Symptoms A progress code may be reported as "LCP STOPPED" for a PPP call.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms The RADIUS disconnect code may report value 10, "modem never detected DCD," for a regular PPP.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms PPP Link Control Protocol (LCP) negotiation may not work correctly.
Conditions The conditions under which this symptom occurs are not known at this time. This caveat is related to the fix for CSCdx46822.
Workaround There is no workaround.
•
Symptoms For asynchronous-over-ISDN calls, the network access server (NAS) port type may be incorrectly reported as ISDN when it should be reported as asynchronous.
Conditions The conditions under which this symptom occurs are not known at this time.
Workaround There is no workaround.
•
Symptoms The attribute 6 Service-Type may be missing in an authentication request, and messages similar to the following may be displayed:
RADIUS: Send to unknown id 11 10.52.216.2:1645, Access-Request, len 81
RADIUS: authenticator 65 86 66 A9 AA C9 E5 D5 - DA E6 E6 1D 77 EC 26 37
RADIUS: Framed-Protocol [7] 6 PPP [1]
RADIUS: User-Name [1] 18 "lac-1@tunnel.com"
RADIUS: CHAP-Password [3] 19 *
RADIUS: NAS-Port [5] 6 34
RADIUS: NAS-Port-Type [61] 6 Virtual [5]
RADIUS: NAS-IP-Address [4] 6 10.52.221.120Conditions This symptom is observed on a Cisco 7200 series router that is functioning as a multihop node that is running Cisco IOS Release 12.2(10.7)T1 in a configuration in which the multihop node is located in between a Cisco AS5300 that is functioning as a Layer 2 Tunnel Protocol (L2TP) concentrator (LAC) and a Cisco 7200 series router that is functioning as an L2TP network server (LNS).
The symptom does not occur when the multihop node is running Cisco IOS Release 12.2(6.7)T, in which case messages similar to the following may be displayed:
RADIUS: Send to unknown id 5 10.52.216.2:1645, Access-Request, len 87
RADIUS: authenticator DB C3 2D 4E A8 F6 10 DE - DA E6 E6 1D CB 96 98 DB
RADIUS: Framed-Protocol [7] 6 PPP [1]
RADIUS: User-Name [1] 18 "lac-1@tunnel.com"
RADIUS: CHAP-Password [3] 19 *
RADIUS: NAS-Port [5] 6 12
RADIUS: NAS-Port-Type [61] 6 Virtual [5]
RADIUS: Service-Type [6] 6 Framed [2]
RADIUS: NAS-IP-Address [4] 6 10.52.221.120Workaround To enable the Service-Type to be sent in the authentication request, enter the radius-server attribute 6 on-for-login-auth global configuration command.
•
Symptoms Voice calls may be rejected after running voice calls with preauthorization enabled for an extended period.
Conditions This symptom is observed on a Cisco AS5400.
Workaround Enter the no aaa preauth global configuration command to get voice calls running again.
•
Symptoms A memory leak may be seen in PPP events after a stress test.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(02)XB06 after a stress test.
Workaround There is no workaround.
•
Symptoms Progress Code attribute 196 may report value 10 for Layer 2 Tunneling Protocol (L2TP) call disconnect, but is should pass the value as 65.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms Authentication, authorization, and accounting (AAA) stop records may report 0 in acct_output_octets and acct_input_octets, even when large amounts of data have been transferred by the session.
Conditions This symptom is observed on a Cisco AS5850.
Workaround Retrieve the information using the spe call-record modem, modem call-record, and calltracker call-record global configuration commands.
•
Symptoms Not all extensible markup language (XML) traps are being generated for the Service Level Measurement (SLM) feature.
Conditions This symptom is observed on a Cisco MC3810 router that is using the SLM feature.
Workaround There is no workaround.
•
Symptoms When you enter the no cns event global configuration command, the Service Level Measurement (SLM) notify process may throw tracebacks.
Conditions This symptom is observed on a Cisco 2600 series router.
Workaround Do not remove the CNS event agent.
•
Symptoms A virtual private dial-up network (VPDN) call may not be forwarded.
Conditions This symptom is observed when the vpdn authen-before-forward command is configured and "preauth:auth-required=0"is listed in the preauthorization user profile.
Workaround There is no workaround.
•
Symptoms A Simple Network Management Protocol (SNMP) query may return a wrong value for an entPhysicalVendorType query.
Conditions This symptom is observed when an SNMPWalk entPhysicalVendorType query is performed on a Cisco 7576 router.
Workaround There is no workaround.
•
Symptoms The network access server (NAS) port type for channel-associated signaling (CAS) preauthorization may be reported incorrectly as asynchronous, but should be reported as ISDN for backward compatibility.
Conditions The conditions under which this symptom occurs are not known at this time.
Workaround There is no workaround.
Interfaces and Bridging
•
Symptoms A lot of memory (more than 20 MB) may be used by the Tag Control process.
Conditions This symptom is observed on a Cisco 7200 series router when a very large number of per-Virtual Circuit (VC) queues are allocated under the Tag Control process.
Workaround There is no workaround.
•
Symptoms A Label Distribution Protocol (LDP)/Tag Distribution Protocol (TDP) session may flap, and IP packets that are sent from the Label Switch Controller (LSC) or to the LSC will time-out when IP connectivity is broken on headend tagged virtual circuits (TVCs) and label virtual circuits (LVCs) out of the LSC. Only headend virtual circuits (VCs) from the LSC are affected.
Conditions This symptom is observed on a Cisco 7200 series router and on a Route Processor Module (RPM) that is running Cisco IOS Release 12.2(10.7)T and when TDP or LDP with TVCs and LVCs are using an LSC. Also, for the symptom to occur, the control interface needs to be ATM Deluxe.
At first, Interior Gateway Protocols (IGPs) and TDP and LDP traffic will not be affected, and the IGP and TDP and LDP neighbors will come up because the control-VC is a permanent virtual circuit (PVC). The symptom occurs on TVCs and LVCs only on the LSC. IGPs (Open Shortest Path First [OSPF] and Intermediate System-to-Intermediate System [IS-IS]) will run initially on the control-VC, but then they will move to the TVC or LVC when one of these is created. IGP then fails. Consequently, the TDP/LDP session flaps continuously. In normal conditions, traffic from and to the LSC should be minimal because the edge functionality should be disabled.
Workaround Disable the headend TVCs and LVCs using the mpls atm disable-headend-vcs global configuration command. Traffic terminating and originating in the LSC will run via the control-VC and will be processed switched.
IP Routing Protocols
•
Symptoms The Open Shortest Path First (OSPF) process fails to update the metric in the self-generated external link-state advertisements (LSAs).
Conditions This symptom is observed when interface cost changes because of bandwidth configuration change and there exists an OSPF process to redistribute this interface. OSPF process (OSPF process 1) that is running on this interface updates its router and network LSAs. If another OSPF process (OSPF process 2) is configured to redistribute this interface, it will not update the cost in its external LSAs.
Workaround To update external LSAs with the correct metric, clear redistribution on the OSPF process (OSPF process 2) that is redistributing this interface using the clear ip ospf process-number redistribution EXEC command, or flap the interface on which bandwidth is changed using the shutdown interface configuration command followed by the no shutdown interface configuration command.
•
Symptoms A router may reboot because of a memory allocation (MALLOC) error in the Border Gateway Protocol (BGP) router process.
Conditions This symptom is observed on a Cisco 12000 series router.
Workaround There is no workaround.
•
Symptoms A system may reload.
Conditions This symptom is observed on a Cisco router when a write terminal EXEC command is issued.
Workaround There is no workaround.
•
Symptoms Session Initiation Protocol (SIP) phones (7960) may fail to register.
Conditions This symptom is observed when a third-party server challenges the REGISTER message that is coming across a Cisco IOS Network Address Translation (NAT). The same scenario works fine with a Cisco SIP proxy server (CSPS).
Workaround There is no workaround.
•
Symptoms The Session Initiation Protocol (SIP) Application Layer Gateway (ALG) does not parse the "Expires" header in the REGISTER message.
Conditions This symptom is observed when Cisco IOS Network Address Translation (NAT) is configured on a router in order to use SIP ALG.
Workaround There is no workaround.
•
Symptoms Resource Reservation Protocol (RSVP) ignores the ip rsvp resource-provider none command-line interface (CLI) command.
Conditions This symptom is observed on a Cisco 7500 series router that is configured with a Versatile Interface Processor (VIP) when Distributed Weighted Fair Queuing (DWFQ) is enabled on an interface.
Workaround There is no workaround.
•
Symptoms A call setup may be successful, but data cannot be transferred because the Virtual-Access interface is removed from the routing table after the call is set up.
Conditions This symptom is observed when a user attempts to dial back in to a remote access (RA) Multiprotocol Label Switching (MPLS)/Virtual Private Network (VPN) service for a Layer 2 Tunneling Protocol (L2TP) dial-in virtual home gateway (VHGW)/provider edge (PE) router and a direct dial-in network access server (NAS)/PE router.
Workaround There is no workaround.
•
Symptoms A 99-percent CPU utilization may occur on a router during a stress test.
Conditions This symptom is observed on a Cisco AS5850 with 1100 ISDN synchronous/asynchronous calls, including virtual private dial-up network (VPDN) and non-VPDN calls, and with a traffic rate of 7/28 packets per second (pps) and a teardown rate of 9 calls per second (CPS).
Workaround There is no workaround.
•
Symptoms A system may run out of memory because of a leak in the routing table structures. No explicit triggers (other than routes in the table) are needed to cause this symptom.
Conditions The conditions under which this symptom occurs are not known at this time.
Workaround There is no workaround.
Miscellaneous
•
Symptoms Packets between VLANs on an Enhanced Gigabit Ethernet Interface Processor (GEIP+) are corrupted.
Conditions This symptom is observed on a Cisco 7500 series router that is configured with a GEIP+ if the following conditions are present:
–
–
–
Workaround Disable dCEF on the GEIP+ by entering the no ip route-cache distributed interface configuration command.
•
Symptoms Incoming dual tone multifrequency (DTMF) digits from the public switched telephone network (PSTN) may not be reported by Media Gateway Control Protocol (MGCP) after a call is connected.
Conditions This symptom is observed on a Cisco 3600 series router when a channel-associated signaling (CAS) T1 MGCP trunk is configured for multifrequency (MF) and functions as the terminating endpoint.
Workaround Use DTMF signaling.
•
Symptoms Media Gateway Control Protocol (MGCP) dial preauthentication does not work on a Cisco Resource Policy Management System (RPMS) server.
Conditions The conditions under which this symptom occurs are not known at this time.
Workaround Use an alternate RADIUS server.
•
Symptoms Errors such as "ISA heartbeat failure," "ISA failed to Initialize," or other unusual errors related to the Integrated Services Adapter (ISA) microcode may be reported from an ISA.
Conditions This symptom is observed on a Cisco 7200 series router that is running Cisco IOS Release 12.2, Release 12.2 T, Release 12.2 S, or any release derived from these releases.
Workaround Do not use an ISA.
•
Symptoms Distributed Network-Based Application Recognition (dNBAR) stateful classification and bidirectional traffic classification across Versatile Interface Processors (VIPs) do not work.
Conditions This symptom is observed on a Cisco 7500 series router that is running Cisco IOS Release 12.2(8)T
Workaround There is no workaround.
•
Symptoms Inbound and outbound calls that are going through a gateway may fail with a fastbusy signal because the gateway indicates that all of the channels on the T1 line are the busy.
The debug voip ccapi inout EXEC command indicates that outbound calls are rejected by the gateway based on the following reasons in the debug output:
ssaSetupPeer intf busy. peer(0x824912D8), cid(5543)
ssaSetupPeer - intf busy. calledNum(97526501)
ccCallDisconnect (callID=0x15A7, cause=0x11 tag=0x0)
ssaSetupPeer: setup failed rc(0)An inbound call that originates from either a public switched telephone network (PSTN) or a PBX does not reach the gateway because the channels appear to be busy to the PSTN or the PBX.
Conditions This symptom is observed on a Cisco Catalyst 4224 switch that is configured with T1 data lines and a T1 voice line that is connected to a PSTN. When the T1 controller for one of the T1 lines is shut down administratively or when a T1 line goes down for any reason, the Cisco Catalyst 4224 switch will busyout all of the T1 voice channels. When this situation occurs, the Cisco Catalyst 4224 switch can make no further outbound calls to the PSTN, nor can it receive any inbound call from the PSTN. This symptom can be verified with channel-associated signaling (CAS) using a receive & transmit (E&M) wink.
Workaround There is no workaround.
•
Symptoms An access list may not function properly after Cisco Express Forwarding (CEF) is enabled.
Conditions This symptom is observed if a per-user access list is applied to dialup users that negotiate TCP/IP header compression.
Workaround Disable CEF.
Alternate Workaround Disable TCP/IP header compression.
•
Symptoms Some channels may be aborted on a port adapter.
Conditions This symptom is observed on a multichannel Synchronous Transport Module level 1 (STM-1) port adapter (PA-MC-STM1) that is configured to operate in the framed or unframed mode.
Workaround Perform the following steps:
a.
b.
c.
•
Symptoms When a gateway is operating in gateway-controlled mode with T.38 fax relay for Media Gateway Control Protocol (MGCP) enabled by default, T.38 fax for MGCP does not engage and a fax does not go through. Fax pass-through does not engage either.
Conditions This symptom is observed on a Cisco gateway that is running Cisco IOS Release 12.2(7.6)T.
Workaround There is no workaround.
•
A Cisco MC3810 multiservice access concentrator router may reload when the busyout monitor probe ip-address voice-port configuration command is configured on a voice port interface. The busyout monitor works normally with voice port interfaces. There is no workaround.
•
Symptoms Different speeds cannot be set on a serial interface.
Conditions This symptom is observed when circuit emulation service (CES) is configured on a Cisco MC3810. You cannot set different speeds on the serial 0 and serial 1 interfaces.
Workaround There is no workaround.
•
Symptoms A router may reload after a login is performed using Kerberos.
Conditions This symptom is observed on a Cisco 2500 series router after the username and password are entered during the initial login process using Kerberos.
Workaround There is no workaround.
•
Symptoms A gatekeeper does not send Gatekeeper Transaction Message Protocol (GKTMP) messages to a second server if the first server of the same priority is down or shut down using the command-line interface (CLI).
Conditions This symptom is observed only with Cisco IOS Release 12.2(2)XU2 gatekeeper images when redundant GKTMP servers are used.
Workaround If load balancing between servers is not required, set the servers to different priorities. If load balancing is required, there is no workaround.
•
Symptoms A Cisco AS5850 does not answer more than 256 ISDN calls.
Conditions This symptom is observed when Resource Policy Management System (RPMS) version 1.1 is used in a Signaling System 7 (SS7) environment. This symptom is observed when the number of resources under the resource group are greater than the available High-Level Data Link Control (HDLC) resources on a trunk card. When all the resources on the trunk card are used for the next call (the 257th call), the call fails to terminate as NextPort resources are not used.
Workaround There is no workaround.
•
Symptoms A terminating gateway may print spurious memory access messages and exhibit abnormal signaling behavior.
Conditions This symptom is observed on a Cisco AS5850 that is operating as a terminating gateway in a T1 and channel-associated signaling (CAS) setup in which the originating and the terminating gateways are configured for T1 and CAS.
Workaround There is no workaround.
•
Symptoms A gateway may not report the correct number of trunks that are in use to the gatekeeper via resource availability indicator (RAI) messages. If 24 trunks of a T1 span are in use or are busy remotely, the gateway reports only 20 of the trunks in use via RAI.
Conditions This symptom is observed in a Cisco Signaling System 7 (SS7) Interconnect for Voice Gateways environment on a voice gateway that is configured with a multifrequency (MF) channel-associated signaling (CAS) trunk group.
Workaround There is no workaround.
•
Symptoms Several Cisco attribute-value (AV) pairs are missing from the accounting records that are sent to RADIUS server.
Conditions This symptom is observed on a Cisco AS5300 when authentication, authorization, and accounting (AAA) start and stop records for customer profiles are created on the network access server (NAS) for every call.
Workaround There is no workaround.
•
Symptoms The tag forwarding table does not show entries for recursive static routes.
Conditions This symptom is observed when more than one static route is configured on a router. When the routes are cleared, the Tag Forwarding Information Base (TFIB) entry shows the recursive static route entry briefly, and then the entry disappears.
Workaround There is no workaround.
•
Symptoms Calls are not routed to a gateway.
Conditions This symptom is observed on a Cisco universal access gateway that has trunk groups configured and has the resource threshold gateway configuration command enabled.
Workaround Define dummy operational plain old telephone service (POTS) dial peers to reference the trunk group interfaces.
•
Symptoms A Cisco IAD2420 may not respond to a notification request (RQNT) message that is sent by a call agent.
Conditions This symptom is observed on a Cisco IAD2420. At the end of a call, the call agent will send a delete connection (DLCX) message and a RQNT message one after another without waiting for the Cisco IAD2420 to respond to the first DLCX message. Sometimes the Cisco IAD2420 sends a "250" message in response to the DLCX message and then sends a "200" message for the RQNT message. In some cases, the Cisco IAD2420, though it receives the DLCX message and the RQNT message, responds to the DLCX message with a "250" message, but it never sends a "200" message in response to the RQNT message. Instead, the Cisco IAD2420 will start sending a NTFY message (O:rlc). In this way both the call agent and the Cisco IAD2420 go into a deadlock mode, each one expecting the other to send an acknowledgement.
If the call agent would send a DLCX message and would wait for a "250" message before it would send the RQNT message (S:rel, R:rlc), this condition could be avoided.
Workaround There is no workaround.
•
Symptoms Media Gateway Control Protocol (MGCP) dial calls are unsuccessful and cannot be completed if ISDN is configured.
Conditions This symptom is observed if ISDN is configured on MGCP dial platforms such as the Cisco AS5300, Cisco AS5350, and the Cisco AS5400.
Workaround There is no workaround.
•
Symptoms The dynamic IP pool download feature for digital Multilink PPP (MLP) calls does not work as expected.
Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(10)T.
Workaround There is no workaround.
•
Symptoms The local pool of IP addresses on a router may not be cleaned after a client disconnects.
Conditions This symptom is observed on a Cisco router that is running the Easy VPN Server feature.
Workaround There is no workaround.
•
Symptoms The twist levels for a Foreign Exchange Office (FXO) analog interface are reversed.
Conditions This symptom is observed on an analog interface.
Workaround There is no workaround.
•
Symptoms A Media Gateway Control Protocol (MGCP) call may connect successfully, but the call may not register properly with call tracker and resource accounting.
Conditions This symptom is observed on a Cisco universal access server.
Workaround Do not configure accounting in the configuration file.
•
Symptoms A bus error exception may occur on a router, and the router may reload when a Simple Network Management Protocol (SNMP) walk is performed on a CiscoMgmt MIB.
Conditions This symptom is observed on a Cisco 3660 router.
Workaround There is no workaround.
•
Symptoms A Cisco CVA122 platform incorrectly includes the notified entity parameter in the delete connection (DLCX) message that is sent to the call agent.
Conditions This symptom is observed when the Real-Time Transport Protocol (RTP) stream is disrupted and the Cisco CVA122 platform is configured to disconnect calls if the RTP stream is lost. Sending the notified entity (N:) parameter in the DLCX is a violation of Media Gateway Control Protocol (MGCP) standards.
Workaround There is no workaround.
•
Symptoms An ATM OC-12 interface on a Cisco 7500 series port adapter shows output drops that cannot be accounted for anywhere else in the router. None of the permanent virtual connections (PVCs) show any drops, but the interface still accumulates drops.
Conditions This symptom is observed when the traffic rate is very low compared to line rate of the port adapter.
Workaround There is no workaround.
•
Symptoms Media Gateway Control Protocol (MGCP) dial modem calls do not work because the dispatcher subsystem is not included.
Conditions This symptom is observed on a Cisco AS5350.
Workaround There is no workaround.
•
Symptoms A high CPU utilization condition may occur on a universal access server, and service may be impacted.
Conditions This symptom is observed on a Cisco AS5300 when a Media Gateway Control Protocol (MGCP) network access server (NAS) package is configured.
Workaround There is no workaround.
•
Symptoms A router may have only an 80 percent call success rate (CSR).
Conditions This symptom is observed on two Cisco 3640 routers that are connected back-to-back using a Fast Ethernet connection when fax pass-through is stress tested with 46 calls. The concurrency level is set at 48 for the maximum session numbers and PRI-IP-channel-associated signaling (CAS) is used in the test setup.
Workaround There is no workaround.
•
Symptoms Hung voice calls may exist on a terminating gateway.
Conditions This symptom is observed on a Cisco universal gateway if the IP link between the originating gateway and the terminating gateway goes down.
Workaround There is no workaround.
•
Symptoms The serial background process repeatedly attempts to bring up the serial interface in the middle of a call, the call is brought down, and a carrier transition occurs on the serial interface.
Conditions These symptoms are observed on a serial interface on a Cisco AS5300.
Workaround There is no workaround.
•
Symptoms The virtual IP address on an EtherSwitch network module does not work as the default gateway for clients, and the virtual IP address cannot be pinged across subnets.
Conditions These symptoms are observed on a Cisco 16-port EtherSwitch network module that is installed on a Cisco 2600 series or Cisco 3600 series router that is running Cisco IOS Release 12.2(8)T, Release 12.2(2)XT2, or Release 12.2(2)XT3.
Workaround Enter the standby use-bia interface configuration command on the Cisco 16-port EtherSwitch network module.
•
Symptoms A console port pauses indefinitely when the show call active voice EXEC command is entered.
Conditions This symptom is observed on a Cisco AS5850 that is running Cisco IOS Release 12.2(11)T when the show call active voice EXEC command is entered while there is a call rate of 9 to 10 calls per second.
Workaround To restore the access on the console port, reduce the rate of the calls.
•
Symptoms A serial interface cannot be pinged even though the interface shows that the line protocol is in the "Up/Up" state.
Conditions This symptom is observed on a 1-port serial WAN interface card (WIC-1T) or a 2-port serial WAN interface card (WIC-2T) that is installed in a Cisco 2600 series router that is running Cisco IOS Release 12.2(9.4)T.
Workaround There is no workaround.
•
Symptoms The Cisco IOS Telephony Service (ITS) voice-mail integration command-line interface (CLI) may not function. Customers who are using Cisco IOS Release 12.2(8)T with voice-mail inband integration requirements may not be able to upgrade to Cisco IOS Release 12.2(11)T.
Conditions This symptom is observed on a Cisco 3600 series router.
Workaround There is no workaround.
•
Symptoms The Framed IP Netmask attribute 9 is not installed correctly.
Conditions This symptom is observed when a PPP dialup is performed on a Cisco 7400 series router that is running Cisco IOS Release 12.2 T.
Workaround There is no workaround.
•
Symptoms A router may leak memory.
Conditions This symptom is observed on a Cisco 7200 series router when a "getmany" Simple Network Management Protocol (SNMP) request is made.
Workaround There is no workaround.
•
Symptoms A gateway may report a nonzero duration for failed calls.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms Zone sorting (based on cost and priority) is giving higher precedence to lower priority values, and zone sorting priority has to be reversed.
Conditions This symptom is observed on a Cisco 3600 router that is running Cisco IOS Release 12.2 T.
Workaround There is no workaround.
•
Symptoms The console port of a router pauses indefinitely after an incorrect timeout value is configured.
Conditions This symptom is observed on a Cisco 2600 series router that is running Cisco IOS Release 12.2 T.
Workaround There is no workaround.
•
Symptoms A gateway may lose digital signal processor (DSP) channels after it receives "bursty" traffic.
Conditions This symptom is observed on a Cisco gateway that is running Cisco IOS Release 12.2(2)XU3 in a Signaling System 7 (SS7) Interconnect for Voice Gateway environment when ISDN User Part (ISUP) transparency is configured and a "bursty" traffic load of 24 cells per second (CPS) with a short holding time (2 seconds) occurs.
Workaround There is no workaround.
•
Symptoms A Cisco AS5300 may play a constant tone on a channel-associated signaling (CAS) trunk to a calling party. The constant tone will not terminate until the calling party goes onhook.
Conditions This symptom is observed when an ingress call is made via a CAS trunk to a Cisco AS5300 and the call is not completed either because the Cisco AS5300 receives an admission rejection (ARJ) message from the gatekeeper or because the far end disconnects the call with a cause code of 3, 41, or 38.
Workaround There is no workaround.
•
Symptoms The hairpin connection between ports on different high-density voice network modules (NM-HDVs) may not work; that is when a voice call is switched from a port on one NM-HDV to a port on another NM-HDV.
The same symptom may occur for hairpin connections between ports of an NM-HDV and any other T1 or E1 voice interface card (VIC) that is installed in either an NM-HDV, or in any network module that has two WAN interface card slots, or in slot 0 of the router.
A voice call between two ports on the same NM-HDV works fine.
Conditions This symptom is observed on a Cisco 3660 router that is configured with a multiservice interchange (MIX) module.
Workaround There is no workaround.
•
Symptoms The following error message is logged when a virtual circuit (VC) is activated or deactivated on a Route Processor Module (RPM):
%RPM_VIRTUAL_PORT-3-IPCERR: switch_vport_send_pxm_with_reply: Vport re quest rejected by PXM. Error String = enErr:Input parameters are InCorrect.Error Code = 1869756999The error message above indicates that the virtual port request is rejected by the Processor Switch Module 1 (PXM1) controller card.
Conditions This symptom is observed when a VC is activated or deactivated on an RPM that is installed on a Cisco MGX 8850 advanced ATM multiservice switch that has a PXM1 controller card.
A VC can be activated or deactivated in the following scenarios:
–
–
Workaround There is no workaround. A "CONN_STATE_UPDT" request is not supported on a Cisco MGX 8850 that has a PXM1 controller card; such requests should not be sent.
•
Symptoms A router may reload because of a software condition when a trustpoint label that has more than ten characters is configured.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(10.1)T.
Workaround Configure a trustpoint label that has fewer than ten characters. There is no workaround for labels that have predetermined lengths.
•
Symptoms An interactive voice response (IVR) solution does not work with a T1 or a PRI connection on a WAN router or a LAN router and the following error message may be displayed:
%IVR_MSB-3-INVALID_MAX_PROMPTS: ms_play: This version of IOS does not support prompt playout for IVR applicationsConditions This symptom is observed on a Cisco WAN or LAN router that has a T1 or PRI connection and that is running Cisco IOS Release 12.2 T.
Workaround There is no workaround.
•
Symptoms A subinterface of a Route Processor Module (RPM) can be deleted using a Simple Network Management Protocol (SNMP) command while connections exists on this subinterface. You should not be able to delete a subinterface using an SNMP command while connections exists on this subinterface.
Conditions This symptom is observed on a Cisco MGX RPM that is running Cisco IOS Release 12.2 T. After the subinterface is deleted, the connection is still displayed in the output of the show switch connections EXEC command.
Workaround There is no workaround.
•
Symptoms A Cisco AS5400 may reload during the bootup process.
Conditions This symptom is observed on a Cisco AS5400 that has a failed NextPort module.
Workaround There is no workaround.
•
Symptoms Ping failures may occur between the network access server (NAS) and a caller on ISDN PRI synchronous and asynchronous calls.
Conditions This symptom is observed on a Cisco AS5850 that is running Cisco IOS Release 12.2(2)XB5 when an ISDN call is made while virtual profiles are enabled.
Workaround Disable the virtual profiles on the access server for ISDN calls.
•
Symptoms Spurious memory accesses and tracebacks may occur on a Cisco AS5400. The following error messages may be generated:
%ALIGN-3-SPURIOUS: Spurious memory access made at 0x614D3CBC reading 0x178
%ALIGN-3-TRACE: -Traceback= 614D3CBC 6149D0A0 610528B8 611D43F0 611E2EF0 611F9D38 611FA548 611F35D4
%ALIGN-3-TRACE: -Traceback= 614D33A8 602FF8F4 60303690 6149D0C8 610528B8 611D43F0 611E2EF0 611F9D38Conditions This symptom is observed on a Cisco AS5400 during a performance test with 648 channels using a Voice Extensible Markup Language (VXML) application.
Workaround There is no workaround.
•
Symptoms A gatekeeper may reload when a Cisco Gatekeeper Transaction Message Protocol (GKTMP) server replies with a location confirm (LCF) message to a location reject (LRJ) request.
Conditions This symptom is observed on a Cisco gatekeeper that is configured with an LRJ trigger. When the gatekeeper receives an LRJ trigger from a remote gatekeeper, the originating gatekeeper sends a LRJ request to the server. The server changes this LRJ request to a LCF message. The gatekeeper reloads when the server sends the LCF message.
Workaround Deconfigure the LRJ trigger on the gatekeeper.
•
Symptoms PPP sessions are torn down and brought back up unnecessarily.
Conditions This symptom is observed when you configure PPP sessions on an ATM interface and a virtual circuit (VC) class that is not related to the set of ATM permanent virtual circuits (PVCs).
Workaround There is no workaround.
•
Symptoms Incoming Multiprotocol Label Switching (MPLS) traffic that is destined for Virtual Private Network (VPN) prefixes cannot be forwarded over a VPN routing and forwarding (VRF) generic routing encapsulation (GRE) tunnel. The traffic is dropped at the disposition provider edge (PE) router, which is a Cisco 7500 series router.
Conditions This symptom is observed when distributed switching is enabled on an interface.
Workaround Configure the no ip route-cache distributed interface configuration command on the input interface.
Alternate Workaround Configure the ip cef global configuration command.
•
Symptoms When a Route Processor Module (RPM) subinterface is administratively shut down, "down" traps are generated for the RPM subinterface and for other subinterfaces that are in the "administratively up" state.
Conditions This symptom is observed on a Cisco RPM that is running Cisco IOS Release 12.2 T.
Workaround There is no workaround.
•
Symptoms A router may reload with a bus error when the following EXEC commands are used to change the buffer playout parameters while the router is running and an ISDN interface is explicitly specified as the port:
–
–
When a non-ISDN interface such as an analog or channel-associated signaling (CAS) interface is specified as the port, the router does not reload, but an alignment error is produced in either of the commands stated above.
Conditions These symptoms are observed on a Cisco 3600 series or a Cisco 3700 series router and do not affect the performance of the router significantly.
Workaround There is no workaround.
•
Symptoms Calls may pause indefinitely.
Conditions This symptom is observed on a Cisco AS5400 during a stress test with 230 sessions of audio playback from multiple servers and storage locations (using HTTP, Real-Time Streaming Protocol [RTSP], Flash memory, and TFTP).
Workaround There is no workaround.
•
Symptoms A router may reload because of a memory corruption.
Conditions This symptom is observed during a stress test when you record to RAM and to various servers (using Real-Time Streaming Protocol [RTSP], Simple Mail Transfer Protocol [SMTP], and HTTP).
Workaround There is no workaround.
•
Symptoms A router may reset unexpectedly with a bus error when the command-line interface (CLI) test gssapi init_sec_contxt server name command is issued.
Conditions This symptom is observed on any platform that supports the CLI test gssapi init_sec_contxt server name command.
Workaround Configure the kerberos local-realm kerberos-realm global configuration command.
•
Symptoms A voice port does not come up if the pri-group timeslots 1-24 nfas_d none controller configuration command is configured under the T1 1/0 controller on a Cisco 3600 series or a Cisco 3700 series router.
Conditions This symptom is observed on a Cisco 3600 series or a Cisco 3700 series router that has a network module. The voice port works normally if the T1 1/0 controller is configured as the primary D channel.
Workaround There is no workaround.
•
Symptoms The ignore-dcd interface configuration command does not function on a serial interface.
Conditions This symptom is observed on a Cisco 2600 series router that has a 1-port WAN interface card (WIC-1T), 2-port serial WAN interface card (WIC-2T), or a 2-port asynchronous/synchronous WAN interface card (WIC-2A/S).
The ignore-dcd interface configuration command does function on a 4-port asynchronous/synchronous serial network module (NM-4A/S) and an 8-port asynchronous/synchronous network module (NM-8A/S).
Workaround There is no workaround.
•
Symptoms A bus error may occur, and a gateway may reload.
Conditions This symptom is observed in a Signaling System 7 (SS7) Interconnect for Voice Gateway environment that includes a Cisco AS5300, during the processing of a combination of H.323 Voice over IP (VoIP) calls and SS7 to channel-associated signaling (CAS) hairpin calls.
Workaround There is no workaround.
•
Symptoms Memory leaks may occur in authentication, authorization, and accounting (AAA) when T.37 onramp calls are stress-tested.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms A router may reload when it attempts to access a nonexistent HTTP server.
Conditions This symptom is observed on a Cisco router.
Workaround There is no workaround.
•
Symptoms When a Cisco AS5850 is reloaded, not all D channels can be brought up.
Conditions This symptom is observed on a Cisco AS5850 that is running the c5850-p9-mz image of Cisco IOS Release 12.2(2)XB.
Workaround There is no workaround.
•
Symptoms An end-to-end ping cannot be sent from a customer edge (CE) router to another CE router.
Conditions This symptom is observed in Cisco IOS Release 12.2(10.3)T1 in network in which two CE routers are connected through two provider edge (PE) routers and there are distributed Link Fragmentation and Interleaving (dLFI)-over-Frame Relay or dLFI-over-ATM links between the CE and PE routers. Packets are not switched via distributed Cisco Express Forwarding (dCEF) for the dLFI-over-Frame Relay or dLFI-over-ATM egress interface on the PE router.
Workaround There is no workaround.
•
Symptoms When a fax call arrives from an originating call generator of a T.38-enabled gateway (GW) over a connection trunk, the GW switches to T.38 fax-relay mode. After the fax download is complete, the call switches to voice mode and no obvious error messages are found in the output of the GW debug commands. However, the fax has not been received in the terminating call generator. The terminating call generator produces an error code 0x6F, and the originating call generator produces an error code 0x3F. The same T.38 fax-relay call works fine on a nontrunk H.323 GW.
Conditions This symptom is observed on Cisco 3640 routers that are running Cisco IOS Release 12.2(11)T in the following test topology:
A call originates from a Cisco AS5300 and arrives over a T1 channel-associated signaling (CAS) line at a Cisco 3640 router that functions as an H.323 outgoing gateway (OGW). The OGW forwards the call through a Voice over IP (VoIP) connection to another Cisco 3640 router that functions as an H.323 terminating gateway (TGW). The TGW forwards the call over a T1 channel-associated signaling (CAS) line to a Cisco AS5300 that terminates the call.
Workaround There is no workaround.
•
Symptoms A Cisco AS5400 stops responding during a call run, and the following message is displayed on the console port:
low on memory, try again laterConditions This symptom is observed on a Cisco AS5400 that is running a c5400-js-mz image.
Workaround There is no workaround.
•
Symptoms When reusing the same 8-port number to configure 24 Redundant Link Manager (RLM) groups per Cisco AS5850-route switch controller (RSC) (48 RLM groups per Cisco AS5850), only 8 RLM groups per RSC are active at a time. Because three loopback interfaces per RSC are used to divide each RSC into three virtual network access servers (NASs), the same 8-port number (3000-3016) should be reusable for each virtual NAS and all 24 RLM groups per RSC should be able to be brought up.
Conditions This symptom is observed on a Cisco AS5850 when the customer attempts to configure more than 8 RLM groups. The User Datagram Protocol (UDP) socket handler function selects the socket for RLM on the basis of the incoming UDP ports and source IP address.
Workaround There is no workaround.
•
Symptoms False silence detection does not work for recording.
Conditions This symptom is observed on a Cisco AS5300.
Workaround Use dual tone multifrequency (DTMF) or define a maximum time (maxtime) for the recording duration to terminate the recording.
•
Symptoms Attribute 77 is not supported on NextPort asynchronous calls.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms A low call success rate (CSR) may occur.
Conditions This symptom is observed on a Cisco AS5400 when basic Media Gateway Control Protocol (MGCP) calls are broken up.
Workaround There is no workaround.
•
Symptoms The ISDN Layer 2 is not in the "MULTIPLE-FRAME_ESTABLISHED" state when the ISDN Layer 1 for the D channel is in the "DEACTIVATED" state.
Conditions This symptom is observed when a router is reloaded after you have enabled the pri-group timeslot 1-24 service mgcp controller configuration command.
Workaround Disable the pri-group timeslot 1-24 service mgcp controller configuration command before you reload the router and reenable the pri-group timeslot 1-24 service mgcp controller configuration command after the router has reloaded. Do not enter the shutdown interface configuration command followed by the no shutdown interface configuration command on the controller after the Media Gateway Control Protocol (MGCP) backhaul configuration has occurred.
•
Symptoms Digital signal processors (DSPs) may reload and their corresponding calls are dropped if there are bit errors in the IP cloud. The following console message may be displayed when this symptom occurs:
hda_tx_dsp_pak: Transmit Ring is full. ep = 108 host pointer= 106Conditions This symptom is observed on a Cisco voice gateway that has a high density analog voice network module (NM-HDA). The DSPs stop responding after they have reloaded. If all DSPs enter a nonresponsive state, the NM-HDA has to be removed and reinserted to be restored to normal working condition.
Workaround There is no workaround.
•
Symptoms A stale raw message pointer is used to send disengage requests (DRQs).
Conditions This symptom is observed if multiple DRQs are sent and if the Call Control Application Programming Interface (CCAPI) reuses the cached raw message pointer. When DRQs are either lost or time out, invalid data may be accessed if the cached raw message pointer is reused.
Workaround There is no workaround.
•
Symptoms Intrazone calls are affected when the bandwidth remote gatekeeper configuration command or the bandwidth interzone gatekeeper configuration command is entered.
Conditions This symptom is observed in Cisco IOS Release 12.2(2)T and later T-train releases but does not affect Cisco IOS mainline releases.
Workaround There is no workaround.
•
Symptoms A router may reload when fax calls are made.
Conditions This symptom is observed on a Cisco AS5400 that has Resource Reservation Protocol (RSVP) configured.
Workaround There is no workaround.
•
Symptoms A memory leak may occur with every call on a Cisco AS5400.
Conditions This symptom is observed on a Cisco AS5400 that has preauthentication enabled and either the no gw-accounting aaa global configuration command or the gw-accounting syslog global configuration command configured.
Workaround Enable the gw-accounting aaa global configuration command instead of the gw-accounting syslog global configuration command.
•
Symptoms Memory leaks may occur in the CCH323_CT process.
Conditions This symptom is observed on a Cisco AS5400. This symptom does not appear to have any effect on the system performance.
Workaround There is no workaround.
•
Symptoms Only a one-way Real-Time Transport Protocol (RTP) stream can be established between Session Initiation Protocol (SIP) and Media Gateway Control Protocol (MGCP) phones.
Conditions This symptom is observed on a Cisco IAD 2420 integrated access device that is running Cisco IOS Release 12.2(8)T.
Workaround There is no workaround.
•
Symptoms Memory allocation difficulties may occur and digital signal resources may be overbooked when authentication, authorization, and accounting (AAA) timeouts occur.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(11)T and may be caused by a rejected call that is dangling and that is not properly cleaned.
Workaround There is no workaround.
•
Symptoms A "VXML_ERROR_INVALID" error message is generated for the following prompts and tags:
–
–
–
–
–
Conditions These symptoms are observed on a Cisco AS5300 that is running the c5300-is-mz image of Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms When Resource Pool Management (RPM) is enabled, the authorization of digital virtual private dialup network (VPDN) calls on NextPort modems is skipped.
Conditions This symptom is observed on a NextPort modem on a Cisco AS5400.
Workaround Terminate digital VPDN calls on High-Level Data Link Control (HDLC) resources when the RPM is enabled.
•
Symptoms A router may reload when IP phones are reset.
Conditions This symptom is observed on a Cisco Catalyst 4224 that is running Cisco IOS Release 12.2(9.4)PI4.
Workaround There is no workaround.
•
Symptoms A router may reload when calls are passed through it.
Conditions This symptom is observed on a Cisco 827 router only if the router is running Cisco IOS Release 12.2(10.3)T2.
Workaround There is no workaround.
•
Symptoms The access restrict feature does not function when a client router and Virtual Private Network (VPN) are configured to use certificates instead of preshared keys.
Conditions This symptom is observed on a Cisco 7100 series router. The access restrict feature works fine when preshared keys are used.
Workaround Configure the client router and VPN to use preshared keys instead of certificates.
•
Symptoms The route to a client IP address that was installed into a Virtual Private Network (VPN) routing and forwarding (VRF) instance using Reverse Route Injection (RRI) is removed when the IP Security (IPSec) security associations (SAs) are rekeyed.
Conditions This symptom causes the loss of connectivity between the client and the rest of the VPN.
Workaround Redistribute the summarized subnet.
•
Symptoms A Cisco AS5800 may reload.
Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2 T when multilink multichassis PPP calls are set up and torn down at a random rate of less than 3 calls per second.
Workaround There is no workaround.
•
Symptoms A Cisco 2651 may reload with a segmentation violation (SegV) exception.
Conditions This symptom is observed on the Fast Ethernet interface of a Cisco 2651 that is running Cisco IOS Release 12.2(8)T and that is configured with both priority queueing and quality of service (QoS) preclassification.
Workaround Disable priority queueing on the Fast Ethernet interface.
•
Symptoms A certification authority (CA) trustpoint cannot be authenticated through TFTP.
Conditions This symptom is observed in Cisco IOS Release 12.2(8)T.
Workaround Use a cut-and-paste procedure to configure the CA trustpoint and use HTTP to authenticate the CA trustpoint.
•
Symptoms A router may reload because of a corrupted call detail block (CDB) memory access in vtsp_is_modem_passthrough_active.
Conditions This symptom is observed on a Cisco MC3810 when a voice call is started.
Workaround There is no workaround.
•
Symptoms A user can hear the caller identification (ID) modem burst if the phone is picked up quickly.
Conditions This symptom is observed on a Cisco IAD 2420 integrated access device that is running Cisco IOS Release 12.2(8)T.
Workaround There is no workaround.
•
Symptoms A router may reload if the PPP over Ethernet (PPPoE) virtual private dialup network (VPDN) group is misconfigured and does not contain a virtual template.
Conditions This symptom is observed on a Cisco router that is configured to terminate PPPoE sessions.
Workaround Ensure that the PPPoE VPDN group contains a virtual template.
•
Symptoms If the voice class h323 tag global configuration command is configured without configuring an H.225 timeout connect value that references this voice class in an outbound Voice over IP (VoIP) dial peer, all outbound dial peers will disconnect immediately with a cause code 41 (temporary failure).
Conditions This symptom is observed on a Cisco AS5400 in a Signaling System 7 (SS7) Interconnect for Voice Gateways environment. In the affected setup, the voice class h323 tag global configuration command has to be configured with a valid value (60 to 360 seconds).
Workaround Use the h225 timeout setup value voice class configuration command to set the H.225 timeout connect value to a valid value (60 to 360 seconds).
•
Symptoms A high CPU utilization condition may be observed on a router, and the router may stop responding and display the following traceback message:
Traceback= 61351904 613E46A0 6160FEA4 6161EA04 6144DD18 6144DF20 6144E374 614448A0Conditions This symptom is observed on a router that has a high density analog voice network module (NM-HDA) when Media Gateway Control Protocol (MGCP) Voice over ATM Adaptation Layer 2 (VoAAL2) calls are made.
Workaround There is no workaround.
•
Symptoms Outgoing calls may fail on a router.
Conditions This symptom is observed on a Cisco AS5850 when a network continuity test (COT) in transponder mode is requested by a vendor-specific switch.
Workaround There is no workaround.
•
Symptoms The branch count may become -1 instead of 0 when a Multifrequency (MF) main branch is removed.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms Poor voice quality and dropped calls may occur on a High-Density Analog Voice/Fax Network Module (NM-HDA) with interactive voice response (IVR).
Conditions This symptom is observed on a Cisco 3600 series router that is running Cisco IOS Release 12.2(10.5)T.
Workaround There is no workaround.
•
Symptoms A gateway may reload.
Conditions This symptom is observed when an Open Settlement Protocol (OSP) call is made on a Cisco AS5400 that is running Cisco IOS Release 12.2 T.
Workaround There is no workaround.
•
Symptoms A vendor-specific conferencing device that is registered to a router cannot perform transfer and hold call functions.
Conditions This symptom is observed on a vendor-specific conferencing device.
Workaround Use Cisco IOS Telephony Services (ITS)-supported firmware.
•
Symptoms If more than one certificate authority (CA) trustpoint is pointed to a given CA server, the CA public key will be removed if one of the CA trustpoints is deleted. Subsequent enrollments to the other CA trustpoint will fail.
Conditions This symptom is observed if more than one CA trustpoint is pointed to a given CA server.
Workaround Add another trustpoint that points to the CA server before enrollment.
•
Symptoms A call may pause indefinitely on a terminating gateway and cause resources to hang.
Conditions This symptom is observed when a call is made on a terminating gateway that is running receive and transmit (E&M) wink start signaling and that has failed digital signal processors (DSPs).
Workaround There is no workaround.
•
Symptoms A router may reload if the router is configured with an interface that is inoperative or the interface is shut down.
Conditions This symptom is observed on a Cisco 3640 router.
Workaround There is no workaround.
•
Symptoms A gatekeeper that is processing egress calls may fail to release memory. Over time this situation may result in call failures.
Conditions This symptom is observed in a Cisco Signaling System 7 (SS7) Interconnect for Voice Gateways Solution environment.
Workaround There is no workaround.
•
Symptoms A router may reload at infrequent times with H.323 calls during a stress test.
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(10.5)T.
Workaround There is no workaround.
•
Symptoms If Multifrequency (MF)-Feature Group D (FGD) call termination occurs in a Cisco AS5800, the line signaling for call termination does not behave properly, which results in calls being unanswered, and the circuit may pause indefinitely The egress test equipment receives all digits and answers the call, but the answer signaling is not being propagated to the ingress side.
Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(10.6)T and that is functioning as an egress voice gateway for MF-FDG receive and transmit (E&M) signaling trunks.
Workaround There is no workaround.
•
Symptoms A Node Route Processor 2 (NRP2) may reload when ATM virtual circuits (VCs) are provisioned or deprovisioned.
Conditions This symptom is observed on a Cisco 6400 series platform.
Workaround Shut down the VC to ensure that traffic is not flowing through the VC before you provision or deprovision VCs.
•
Symptoms A Media Gateway Control Protocol (MGCP) gateway does not negotiate the use of payload value 98 from the mgcp tse payload 98 global configuration command.
Conditions This symptom is observed when a dual tone multifrequency (DTMF) relay call is made when the Cisco AS5850 is not configured in the MGCP DTMF relay mode.
Workaround There is no workaround.
•
Symptoms A router may not be able to play any interactive voice response (IVR) prompts from TFTP or Flash. The following errors are generated:
%IPM_C54X-1-TOOBIG: DSP 0, packet(size 260) too big.
%IPM_C54X-1-TOOBIG: DSP 0, packet(size 260) too big.
%IPM_C54X-1-TOOBIG: DSP 0, packet(size 260) too big.
%IPM_C54X-1-TOOBIG: DSP 0, packet(size 260) too big.Conditions This symptom is observed on a Cisco 1751 router that is running Cisco IOS Release 12.2(10.6)T.
Workaround There is no workaround.
•
Symptoms A traceback may occur in xcsp_ppp_event_proc, and the router may reload.
Conditions This symptom is observed on a Cisco AS5400 when a call is made without a hardware interface data block (HWIDB).
Workaround There is no workaround.
•
Symptoms No free event structure may be available from the "vtsp_ev_chunk_pool" for a digital signal processor (DSP).
Conditions This symptom is observed on a Cisco AS5400 that is running the c5400-js-mz image of Cisco IOS Release 12.2 T.
Workaround There is no workaround.
•
Symptoms When a channel that belongs to controllers 7/0 to 7/7 is involved in a call, the RADIUS call detail record (CDR) that is generated by a Cisco AS5400 may display incorrect values in the cisco-vsa-port-string and cisco-avpair fields. The values for these fields in the RADIUS CDR are "6/x:y" instead of "7/x:y."
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(11)T in a Cisco Signaling System 7 (SS7) Interconnect for Voice Gateways Solution. This symptom is observed with calls that have a channel that belongs to controller 7/0 to 7/7.
Workaround There is no workaround.
•
Symptoms A router may reload before it completes the bootup process.
Conditions This symptom is observed on a Cisco 3660 router when it is booted up with the c3660-g4js-mz image or with certain telcoent images of Cisco IOS Release 12.2(8)T1.
Workaround There is no workaround.
•
Symptoms If a negative output attenuation value is configured on a voice port and this value is applied to a NextPort digital signal processor (DSP), the following error is seen:
%NP_VSM-3-OUT_OF_RANGE_VALUE: OUTPUT GAIN value:[#] is out of rangeConditions This symptom is observed on a Cisco AS5850.
Workaround Do not configure a negative output attenuation on a voice port when using NextPort DSPs.
•
Symptoms A router may consistently reload if Internetwork Packet Exchange (IPX) and RADIUS are enabled on the router and a modem dialin user attempts to connect to the router.
Conditions This symptom is observed on a Cisco 5400HPX that is running Cisco IOS Release 12.2(2)XB5.
Workaround Disable either IPX or RADIUS on the router.
•
Symptoms A T1 PRI call cannot be made after a Media Gateway Control Protocol (MGCP) gateway rehomes back to MGCP control following a fallback to H.323 control.
Conditions This symptom is observed on a Cisco Catalyst 4224 and on a Cisco Catalyst 4000 Access Gateway Module.
Workaround There is no workaround.
•
Symptoms If a T1 link in a channel-associated signaling (CAS) trunk group goes down, an incorrect value of 11 may populate the "Pending" field of the "Total calls for trunk group:" section in the output of the show trunk group command. This value is incremented by 11 each time the T1 goes down and comes up. The remaining channels in the span, less these 11, are populated in the "Free" field even though all channels in the span are available and free.
Conditions This symptom is observed on a Cisco AS5850 that is running Cisco IOS Release 12.2(10.7)T1.
Workaround Reload the gateway.
•
Symptoms When an H.323 call to the IP side debit card application on a terminating gateway is made, no prompts are heard.
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(10.6)T, and it affects the interactive voice response (IVR) application that has a codec class configuration.
Workaround Do not use a codec class.
•
Symptoms A router may reload if the long pound is used several times to enter an incorrect destination number.
Conditions This symptom is observed on a Cisco AS5850 that is running the c5850-p9-mz image of Cisco IOS Release 12.2(11)T when a call is made with the debit card application on the incoming plain old telephone service (POTS) side.
Workaround There is no workaround.
•
Symptoms A severe memory leak may occur in an H.323 environment after channel-associated signaling (CAS) Feature Group-B (FGB) voice calls (on 8 T1 lines) are run for a long duration (more than 20 hours).
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
•
Symptoms On a router, when the Media Gateway Control Protocol (MGCP) default codec is set to G.711 with a packetization period of 20 ms, the codec bytes for the Real-Time Transport Protocol (RTP) stream are 160. When the MGCP default codec is G.711 with a packetization period of 10 ms, the codec bytes for the RTP stream are 80.
The network access server (NAS) ignores the create connection (CRCX) Session Definition Protocol (SDP) parameters; that is, the codec bytes appear to use 10 ms when the CRCX states 20 ms and the default is 10 ms. This results in poor voice quality.
Conditions This symptom is observed on a Cisco AS5400.
Workaround Use the G.711 default codec with a packetization period of 20 ms.
•
Symptoms A Cisco platform that functions as a Voice Telephony Service Provider (VTSP) reloads because of a bus error exception.
Conditions This symptom occurs when an interactive voice response (IVR) application terminates unexpectedly immediately after a CONNECT message is received.
Workaround Do not request notification of a CONNECT message or do not terminate the call upon the notification of a CONNECT message.
•
This caveat resolves critical issues related to CSCdx62034 (a digital signal processor [DSP] may reload during a modem relay and Frame Relay test) and CSCdv71641 (a DSP serial port reset is required).
Symptoms A The symptoms for CSCdx62034 are as follows:
A DSP may reload, resulting in a temporary loss of channel connectivity for all channels of this DSP.
Conditions A This symptom is observed under stress conditions, with a combination of modem relay and Frame Relay calls.
Workaround A There is no workaround.
Symptoms B The symptoms for CSCdv71641 are as follows:
Voice ports on a Cisco AS5300 may fail to transport voice, causing a dead-air condition on certain channels.
Conditions B This symptom is observed in rare cases, when serial ports on a DSP stop operating because of irregular conditions existing on the E1 or T1 line connected to voice ports on a Cisco AS5300.
The voice port can be recovered by resetting the Voice Feature Card (VFC), by resetting the DSP, or by reloading the router.
Workaround B There is no workaround.
•
Symptoms Digital signal processor (DSP) resources are not being allocated to channel-associated signaling (CAS) calls by the call switching module (CSM).
Conditions This symptom is observed on a Cisco AS5300.
Workaround There is no workaround.
•
Symptoms The Media Gateway Control Protocol (MGCP) Cisco fax relay functionality may not function.
Conditions This symptom is observed on a Cisco 3600 series router that is running Cisco IOS Release 12.2(10.7)T1.
Workaround There is no workaround.
•
Symptoms Traffic shaping may be affected when a Route Processor Module (RPM) in an adjacent slot boots up.
Conditions This symptom is observed on a Cisco MGX RPM that has traffic shaping configured when another RPM is inserted in the adjacent slot. Traffic shaping is affected until the Processor Switch Module (PXM) recognizes the card and changes the cell-bus clock speed.
Workaround There is no workaround.
•
Symptoms Multiple sessions may not be established between a Secure Socket Layer (SSL) server and a client.
Conditions This symptom is observed on a Cisco router that is running Cisco IOS Release 12.2(10.7)T1.
Workaround There is no workaround.
•
Symptoms A router may reload when the show running-config privileged EXEC command is entered.
Conditions This symptom is observed on a Cisco router when the cns config notify command is configured and the line console line-number global configuration command-line interface (CLI) command is entered.
Workaround Do not use these two CLI commands in the same router configuration.
•
Symptoms A gatekeeper may not route calls to all gateway members of a trunk group.
Conditions This symptom is observed on a Cisco 7200 series router.
Workaround There is no workaround.
•
Symptoms Speech recognition may not function.
Conditions This symptom is observed on a Cisco AS5300. In a Voice Telephony Service Provider (VTSP) platform, Voice Activity Detection (VAD) is always enabled for record and Automatic Speech Recognition (ASR). For ASR to function properly, VAD needs to be disabled. VAD must be enabled only when the final silence parameter is set.
Workaround There is no workaround.
•
Symptoms An event agent may not be able to gain connectivity with a TibGate, and Cisco Networking Services (CNS) event services may not be usable.
Conditions This symptom is observed on a router when the cns event agent global configuration command is first disabled, the cns id global configuration command is enabled, and the cns event agent global configuration command is then reenabled. This situation causes the event ID that is used by the event agent to come up as "Invalid_Event_Id," regardless if the cns id global configuration command is enabled.
Workaround For the correct value to be used, disable the cns id global configuration command when the cns event agent global configuration command is disabled and reenabled, and reenable the cns id global configuration command afterwards.
•
Symptoms DSPALARM, DSP_TIMEOUT, and invalid Finite State Machine (FSM) conditions may occur within two hours of starting a stress bed test.
Conditions This symptom is observed on a Cisco AS5300 when the stress call is started with the dual tone multifrequency (DTMF) path confirmation enabled in the following setup:
A call generator from a third-party vendor connects over a T1 PRI line to a Cisco AS5300 that is functioning as an H.323 Voice over IP (VoIP) gateway. The Cisco AS5300 connects over a T1 channel-associated signaling (CAS) line to a call generator from a third-party vendor.
Workaround There is no workaround.
•
Symptoms A server may not play either the busy or the reorder tone down a channel-associated signaling (CAS) trunk to the calling party.
Conditions This symptom is observed on a Cisco AS5850 when an ingress call is made on a CAS Multifrequency (MF)-Feature Group D (FGD) trunk and either the calling party is busy or the call cannot be completed.
Workaround There is no workaround.
•
Symptoms Packets that are generated by a router to legacy dialer interfaces may not be transmitted properly when Cisco Express Forwarding (CEF) is enabled.
Conditions This symptom is observed on a Cisco AS5850 that has CEF enabled.
Workaround There is no workaround.
•
Symptoms A Media Gateway Control Protocol (MGCP) PRI backhaul call may not be disconnected on fallback.
Conditions This symptom is observed on a Cisco Catalyst 4224 and a Cisco Catalyst 4000 Access Gateway Module following an MGCP fallback. When the symptom occurs, no further H.323 or MGCP PRI calls can be made on the same channel.
Workaround Reload the Cisco Catalyst 4224 or Cisco Catalyst 4000 Access Gateway Module.
•
Symptoms Traceback messages are displayed repeatedly.
Conditions This symptom is observed on a Cisco 7200 series router that has the Cisco Networking Services (CNS) event agent configured in the bootstrap configuration and when the initial CNS configuration process fails.
Workaround There is no workaround.
•
Symptoms In a Media Gateway Control Protocol (MGCP) modem pass-through Voice over IP (VoIP) environment, codec G.726-32 does not function.
Conditions This symptom is observed on a Cisco IAD2400 that is running Cisco IOS Release 12.2(11)T.
Workaround Use a different codec.
•
Symptoms Digital signal processor (DSP) alarm conditions, memory fragmentation, and buffer shortage conditions may occur within five minutes of starting a stress test.
Conditions This symptom is observed on a Cisco AS5300 when a stress call is started with the dual tone multifrequency (DTMF) path confirmation enabled and the debug hpi error and debug vtsp error EXEC commands are enabled in the following setup:
A call generator of a third-party vendor connects over a T1 PRI line to a Cisco AS5300 that is functioning as an H.323 Voice over IP (VoIP) gateway. The Cisco AS5300 connects over a T1 channel-associated signaling (CAS) line to another call generator of a third-party vendor.
Workaround There is no workaround.
•
Symptoms If a T1 link in a channel-associated signaling (CAS) trunk group goes down, an incorrect value of 11 may populate the "Pending" field of the "Total calls for trunk group:" section in the output of the show trunk group command. This value is incremented by 11 each time the T1 goes down and comes up. The remaining channels in the span, less these 11, are populated in the "Free" field even though all channels in the span are available and free.
Conditions This symptom is observed on a Cisco AS5300, Cisco AS5350, Cisco AS5400, Cisco AS5800, or Cisco AS5850 that is running Cisco IOS Release 12.2(10.7)T1.
Workaround Reload the gateway.
•
Symptoms Within one hour of starting a stress test, the following BADSHARE message is displayed:
%SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=61FBDBFC, count=0Conditions This symptom is observed on a Cisco AS5300 when a stress call is started with the dual tone multifrequency (DTMF) path confirmation enabled and the debug hpi error and debug vtsp error EXEC commands are enabled in the following setup:
A call generator of a third-party vendor connects over a T1 PRI line to a Cisco AS5300 that is functioning as an H.323 Voice over IP (VoIP) gateway. The Cisco AS5300 connects over a T1 channel-associated signaling (CAS) line to another call generator of a third-party vendor.
Workaround There is no workaround.
•
Symptoms A Voice Telephony Service Provider (VTSP) voice processor module (VPM) may get stuck in the "wait release" state.
Conditions This symptom is observed on a voice network module (NM-1V or NM-2V) or on a high-density voice network module (NM-HDV) that is installed in a Cisco 3600 series router that is running Cisco IOS Release 12.2(10.7)T2. The symptom occurs when a new call comes in while the previous one has been terminated but the port is not yet on-hook because the port timers (wait-release/call-disconnect) have not yet expired.
Workaround There is no workaround.
To bring the VPM back into service on a voice network module, reload the voice network module.
To bring the VPM back into service on a high-density voice network module, use one of the following solutions:
–
–
After you have applied one of these two solutions, the VPM is back into service, but the output of the show voice call summary command still displays the "wait release" state, which is no longer correct.
•
Symptoms Clock slips may occur on a universal router module (URM) T1/E1 controller interface.
Conditions This symptom is observed when the clocking configuration receives the URM clocking from an attached device. When the URM is set to Internal timing and the attached device to Receive, no slips are observed. If the URM is set to Line Timing and the attached device is set to Internal, slips are seen on the T1/E1 controller interface.
The default clock source configuration on the T1/E1s is line. The show controller [t1 | e1] slot|port EXEC command displays the clock source configuration as follows:
Router#show controllers t1 2/0 brief
T1 2/0 is up.
Applique type is Channelized T1
Cablelength is long gain36 0db
Transmitter is sending remote alarm.
Receiver has loss of signal.
alarm-trigger is not set
Version info Firmware: 20020306, FPGA: 11
Framing is SF, Line Code is AMI, Clock Source is Line.
Data in current interval (20 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsWorkaround There is no workaround.
•
Symptoms On a router, the total amount of free memory may decrease over time, causing memory allocation (MALLOC) failure messages after a long period of time. This symptom may also cause memory fragmentation that will lead to MALLOC failure messages even when memory is available on the router.
Conditions This symptom is observed on a Cisco router when Internet Key Exchange (IKE) connections are used and negotiated with aggressive mode. The memory leak occurs only on the responder of aggressive mode. The memory leak does not occur when the Cisco Unity client is used as the IKE initiator or when the IKE Extended Authentication (Xauth) version 2 is used during IKE negotiation.
Possible Workarounds Use IKE main mode instead of aggressive mode or use Xauth version 2.
•
Symptoms When a Cisco IOS Telephony Service (ITS) router uses loopback-directory number (loopback-dn) configurations and the voice-class codec is set to use a-law as first priority, poor voice quality may occur during three-party conferencing.
Conditions This symptom is observed on a Cisco 3600 series router.
Workaround Select G.711 u-law instead of a-law for the on-net Voice over IP (VoIP) calls.
•
Symptoms A Cisco AS5400 may reload.
Conditions This symptom is observed when a channel group configuration is removed and a PRI group configuration is added.
Workaround After removing the channel group configuration, wait for about two minutes before adding the PRI group configuration.
•
Symptoms A router may reload at "pm7366_fastsend" because of a bus error.
Conditions This symptom is observed on a Cisco AS5400 during a stress test.
Workaround There is no workaround.
•
Symptoms After a Cisco router has reloaded, it may not be able to connect to a Cisco IE2100. The error trace may indicate an authentication error.
Conditions This symptom is observed on a router that has the cns config initial hostname no-persist global configuration command enabled and that has a Cisco Networking Services (CNS) password in the startup configuration through the use of the cns password hidden command-line interface (CLI) command.
Workaround Reconfigure the router so that the CNS password is not configured in the startup configuration. Enter the following sequence of commands:
config terminal
cns password
write memory
copy tftp startup-config
•
Symptoms An ISDN layer 2 may go down after a switchover on a Virtual Switch Controller (VSC).
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(10.7)T2.
Workaround There is no workaround.
•
Symptoms Spurious memory accesses may occur on a per-packet basis on a Versatile Interface Processor (VIP). In addition, interfaces and routing protocols on the affected VIP and other interfaces on the router may flap.
Conditions These symptoms are observed on a Cisco 7500 series router when Multiprotocol Label Switching (MPLS) is enabled on one of the VIP interfaces.
Workaround There is no workaround.
•
Symptoms A router may not boot.
Conditions This symptom is observed on a Cisco 3745 router that is running the Cisco image c3745-ik9o3s-mz.12.2(10.7)T3.
Workaround There is no workaround.
•
Symptoms When you enter the test dsprm command followed by the show pool command, some failed digital signal processors (DSPs) may appear to be located in the disabled queue.
Conditions This symptom is observed on a Cisco AS5300 when a stress call is started with the dual tone multifrequency (DTMF) path confirmation enabled and when all Voice over IP (VoIP) peers are configured with the no vad dial-peer configuration command in the following test topology:
A call generator of a third-party vendor connects over a T1 PRI line to a Cisco AS5300 that is functioning as an H.323 Voice over IP (VoIP) gateway. The Cisco AS5300 connects over a T1 PRI line to another call generator of a third-party vendor.
Workaround There is no workaround.
•
Symptoms When an On Demand Address Pool (ODAP) router requests a subnet from the ODAP server and the ODAP server does not return the subnet mask option in the Dynamic Host Configuration Packet (DHCPACK), ODAP fails to get the subnet allocated and displays the following error message:
DHCP: ack received without mandatory subnet mask. Please contact the DHCP server administrator to upgrade the DHCP server.For ODAP, this subnet mask option is not mandatory.
Conditions This symptom is observed on a Cisco 7200 series router.
Workaround There is no workaround.
•
Symptoms A large memory leak at the rate of 15 MB per hour may occur in the Tool Command Language (TCL) process.
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(10.7)T3 during an Open Settlement Protocol (OSP) stress test.
Workaround There is no workaround.
•
Symptoms A Route Processor Module (RPM) ingress virtual circuit locks up and stops forwarding traffic.
Conditions This symptom is observed when there is a sudden, large increase in the ingress traffic (such as 145 Mbps of traffic or more with packet sizes of 384 bytes).
Workaround Clear the ingress switch subinterface by entering the shutdown interface configuration command followed by the no shutdown interface configuration command.
•
Symptoms An H.323 gateway may reload.
Conditions This symptom is observed when the H.323 gateway accesses an invalid memory location.
Workaround There is no workaround.
•
Symptoms A gateway may not upspeed for fax pass-through over an ATM Adaptation Layer 2 (AAL2) connection trunk.
Conditions This symptom is observed on a Cisco 2600 series router that is running Cisco IOS Release 12.2(10.7)T3.
Workaround There is no workaround.
•
Symptoms After you remove an access list, a packet assembler/disassembler (PAD) call may still go through because the access list appears to be still present.
Conditions This symptom is observed on a Cisco 7200 series router that is running Cisco IOS Release 12.2(8)T5.
Workaround There is no workaround.
•
Symptoms Dynamic IP Security (IPSec) may not be accepted by a router if there are old security associations (SAs) that have the same proxy address but the remote address is different or does not exist.
Conditions This symptom is observed in Cisco IOS Release 12.2(10.7)T and later releases.
Workaround There is no workaround.
•
Symptoms Call waiting does not work properly on an Analog Telephone Adaptor 186 (ATA 186) that is connected to a Cisco IOS Telephony Service (ITS) system.
Conditions This symptom is observed when the telephones are connected via a Cisco 3600 series router that is running Cisco IOS Release 12.2(10.7)T3.
Workaround There is no workaround.
•
Symptoms Service Level Measurement (SLM) ATM packets may be sent and received with an incorrect datagram size.
Conditions This symptom is observed on a Cisco MC3810.
Workaround There is no workaround.
•
Symptoms During interoperability testing of G. Symmetric high-bit-rate DSL (GSHDSL), unexpected retrains over a period of about seven days occur because of both watchdog and cyclic redundancy check (CRC) errors on customer premises equipment (CPE) with a third-party vendor digital subscriber line access multiplexer (DSLAM). This situation causes an interruption to the service.
Conditions This symptom is observed on a Cisco 2600 series router.
Workaround There is no workaround.
•
Symptoms A glare condition may occur on a router, and the router may reload.
Conditions This symptom is observed on a Cisco AS5850 that is running Cisco IOS Release 12.2(10.7)T3. The glare condition is part of the trunk group signaling feature enhancement, which is used for optimization and scaling.
Workaround Do not use trunk group signaling.
•
Symptoms During a stress bed test, the following BADSHARE message is displayed:
%SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=61FBDBFC, count=0Conditions This symptom is observed on a Cisco 3600 series router when a stress call is started with the dual tone multifrequency (DTMF) path confirmation enabled and the debug hpi error and debug vtsp error EXEC commands are enabled in the following topology:
A call generator of a third-party vendor connects over a T1 PRI line to a Cisco AS5300 that is functioning as an H.323 Voice over IP (VoIP) gateway. The Cisco AS5300 connects over a T1 PRI line to another call generator of a third-party vendor.
Workaround There is no workaround.
•
Symptoms A Cisco AS5300 may reload at "voip_authenticate."
Conditions This symptom is observed under stress conditions on a Cisco AS5300 that is running Toolkit Command Language (TCL) 1.0 scripts.
Workaround There is no workaround.
•
Symptoms The mpls ldp router-id interface force global configuration command may not work as expected. The command should use the IP address of the interface that is specified in the interface argument of the command as the Label Distribution Protocol (LDP) router identification (ID) when the interface is up.
However, if a loopback interface is specified in the above-mentioned command and you administratively shut down the loopback interface and bring it back up again by entering the shutdown interface configuration command followed by the no shutdown interface configuration command on the loopback interface, the IP address of the loopback interface is not restored as the LDP router ID, but another interface is selected as the LDP router ID.
Conditions These symptoms are observed on a Cisco 7200 series and a Cisco 7500 series router.
Workaround To recover from this condition, enter the shutdown interface configuration command followed by the no shutdown interface configuration command on the interface that was selected as the LDP router ID.
•
Symptoms A Session Initiation Protocol (SIP) call may not be function properly.
Conditions This symptom is observed when you use TCP as the session transport protocol.
Workaround Use User Datagram Protocol (UDP) as the session transport protocol.
•
Symptoms The Service Selection Gateway (SSG) connection counters may not be updated.
Conditions This symptom is observed on a Cisco 7400 series router that has Parallel Express Forwarding (PXF) configured when there is a Bridge-Group Virtual Interface (BVI) downlink interface on the SSG connection to the Cisco 7400 series router.
Workaround Disable PXF by entering the no ip pxf global configuration command.
First Alternate Workaround Bind the SSG connection to the physical Ethernet interface.
Second Alternate Workaround Enter the no ip route-cache cef interface configuration command on the physical Ethernet interface.
•
Symptoms Calls may fail on some channels on a controller. The create connection (CRCX) request for the affected channels receives a code 400 response (voice call setup failed).
Conditions This symptom is observed on a controller on a multiservice interchange (MIX)-enabled T1/E1 port adapter (PA-MCX) that is configured for PRI backhaul service using Media Gateway Control Protocol (MGCP) version 0.1.
Workaround There is no workaround.
•
Symptoms Modem pass-through or modem relay calls may fail.
Conditions This symptom is observed in a Media Gateway Control Protocol (MGCP) channel-associated signaling (CAS) configuration.
Workaround There is no workaround.
•
Symptoms The amount of memory that is held by a Real-Time Streaming Protocol (RTSP) client may increase steadily.
Conditions This symptom is observed when RTSP recording is stress-tested for six hours.
Workaround There is no workaround.
•
Symptoms For Trunking Gateway Control Protocol (TGCP) 1.0, a gateway may send a response code 500 ("Endpoint unavailable") when you enter any command that includes an endpoint name in the format "DS/S<slot>/DS1-<port>/<timeslot>@<hostname>", even though the endpoint is in service.
If the endpoint name does not include the host name, the gateway sends an appropriate response. If you use the Media Gateway Control Protocol (MGCP) 1.0 endpoint naming convention for TGCP, the gateway acknowledges the command.
Conditions This symptom is observed on any Simple Gateway Control Protocol (SGCP) gateway or MGCP gateway that is running Cisco IOS Release 12.2(10.5)T.
Workaround Do not use a host name with an endpoint, or use the MGCP 1.0 endpoint naming convention for TGCP.
•
Symptoms A redirected number in the Admission Confirm Function (ACF) is not copied to the called number. The called number remains the same as it was before.
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(10.3)T2 or Release 12.2(11)T when the call is forwarded using Registration, Admission, and Status (RAS) and when the server does not copy the redirected number that is present in the ACF to the called number in the H.225 setup message during redirection.
Workaround There is no workaround.
•
Symptoms A Cisco 3745 router may reload during the bootup process with a watchdog timeout.
Conditions This symptom is observed on a Cisco 3745 router while the High-Speed Serial Interface (HSSI) is being configured.
Workaround There is no workaround.
•
Symptoms A Cisco AS5400 may reload at rtsp_process_resp_headers.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(10.7)T3 during an offramp stress test.
Workaround There is no workaround.
•
Symptoms Automatic Speech Recognition (ASR) and Text-to-Speech (TTS) functionality may not work with the G.729 codec.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(10.7)T3.
Workaround There is no workaround.
•
GRE implementation of Cisco IOS is compliant with RFC2784 and RFC2890 and backward compatible with RFC1701.
•
Symptoms A Cisco AS5400 may reload during the first fax call.
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(11)T.
Workaround There is no workaround.
•
Symptoms You may not be able to set up Media Gateway Control Protocol (MGCP) calls with the G.723 codec.
Conditions This symptom is observed on a Cisco AS5400.
Workaround There is no workaround.
TCP/IP Host-Mode Services
•
Symptoms A Packet Data Serving Node (PDSN) may reload when it is in the process of releasing a session.
Conditions This symptom is observed on a PSDN during high traffic conditions when sessions are being set up and released continuously while TCP header compression is enabled.
Workaround Disable TCP header compression.
Wide-Area Networking
•
Symptoms The magic number may fail to negotiate successfully and cause lines to be dropped.
Conditions This symptom is observed when a specific third-party vendor client and a specific third-party vendor access server are used in combination to connect to a Cisco Layer 2 Tunneling Protocol (L2TP) network server (LNS) and keepalives are enabled.
Workaround There is no workaround.
•
Symptoms The B channels on an E1 controller may enter the "out of service" state when microinterruptions occur. When this situation occurs, no calls can be made on the B channels.
Conditions This symptom is observed in an environment in which a network access server (NAS) is connected to a Cisco SC2200 signaling controller.
Workaround Enter the shutdown controller configuration command followed by the no shutdown controller configuration command on the affected E1 controller.
•
Symptoms Instead of selecting an IP address from the local pool, a router may assign the RADIUS framed IP address of 255.255.255.224 to users who dial in using interactive mode.
Conditions This symptom is observed on a router that is running Cisco IOS Release 12.2(7.6)T.
Workaround Configure the dialin to operate in the asynchronous dedicated mode by entering the async mode dedicated interface configuration command.
•
Symptoms A multihop router may fail to transparently send a serial line interface (SLI) message that contains the asynchronous control character map (ACCM) back to a Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC).
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(7). When a vendor-specific device starts to negotiate the Link Control Protocol (LCP), it sends an SLI message to set the transmit and receive ACCM of the LAC back to 0xFFFFFFFF. The message is received by the multihop router, but the message is not sent back to the LAC.
Workaround There is no workaround.
•
Symptoms A channelized T3 (CT3) line card may reload at "vpn_fs_lc."
Conditions This symptom is observed on a Cisco AS5850 that is running Cisco IOS Release 12.2(2)XB5.
Workaround There is no workaround.
•
Symptoms When two routes are installed for the same virtual private dialup network (VPDN) user, the VPDN user receives one IP address from the Layer 2 Tunneling Protocol (L2TP) network server (LNS) and another IP address from the network access server (NAS) even though the VPDN user should receive only one IP address from the LNS server. Only the IP address that is assigned from the LNS is visible on the routing table and can be pinged.
Conditions This symptom is observed on a Cisco AS5300 that is running Cisco IOS Release 12.2(2)XB2.
Workaround There is no workaround.
•
Symptoms A Cisco AS5800 may display a misleading remote IP address for a virtual private dialup network (VPDN) call. The correct IP address should be assigned by the VPDN gateway.
Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(2)XB5. This symptom does not affect service for the remote user. However, IP resources are used, and a misleading IP address may be displayed for the remote VPDN user.
Workaround There is no workaround.
•
Symptoms The following memory access messages may be recorded during a V.120 call setup:
%ALIGN-3-SPURIOUS: Spurious memory access made at 0x6049D1D4 reading 0x8
%ALIGN-3-TRACE: -Traceback= 6049D1D4 6049FD9C 607EE578 607EDA4C 604F2C34 605041D4 605729FC 605729E8
%ALIGN-3-TRACE: -Traceback= 6049D1E8 6049FD9C 607EE578 607EDA4C 604F2C34 605041D4 605729FC 605729E8Conditions This symptom is observed on a Cisco AS5800 and does not impact service.
Workaround There is no workaround.
•
Symptoms A Virtual Private Network (VPN) unity client (version 3.5) may fail to establish an IP Security (IPSec) session to an IPSec gateway if the group profile contains the Tunnel-Type or the Tunnel-Medium-Type Internet Engineering Task Force (IETF) tunnel attributes.
Conditions This symptom is observed on a VPN unity client that is attempting to establish an IPSec session to an IPSec gateway that is running Cisco IOS Release 12.2(8.5)T or a later release.
Workaround Remove the IETF attributes from the group profile or replace IETF attributes with Cisco attribute-value (AV) pairs. Alternatively, you may choose to enable the vpdn enable global configuration command on the gateway.
•
Symptoms LAN Emulation (LANE) clients may not come up when LANE services are running on third-party equipment.
Conditions This symptom is observed with LANE clients that are used on a Cisco router that is running Cisco IOS Release 12.2 T. This symptom is caused by the corruption of the ATM Adaptation Layer (AAL) parameters in the call setup messages.
Workaround Use a Cisco IOS release other than Cisco IOS Release 12.2 T.
•
Symptoms The idle timer may not function properly for Multilink PPP (MLP) calls.
Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(2)XB5.
Workaround There is no workaround.
•
Symptoms The session timeout function works, but the Multilink PPP (MLP) call disconnect cause code (that indicates that a call is disconnected because of a session timeout) is not reflected in the RADIUS stop record. The stop record reflects the disconnect cause code as PPP Link Control Protocol (LCP) close.
Conditions This symptom is observed on a Cisco AS5800 that is running Cisco IOS Release 12.2(2)XB5.
Workaround There is no workaround.
•
Symptoms Excessive debug output may be generated when the debug ppp events privileged EXEC command is enabled.
Conditions This symptom is observed on a Cisco 7400 series router that is running Cisco IOS Release 12.2(8)T or images that are based on Release 12.2 T.
Workaround There is no workaround.
•
Symptoms An ISDN call may be rejected by an access server.
Conditions This symptom is observed on an access server when an ISDN speed of 56 K is configured under the map-class dialer class-name global configuration command.
Workaround There is no workaround.
•
Symptoms A Cisco Express Forwarding (CEF) dialer interface is not able to add an adjacency for a dialer interface. When this symptom occurs, the dialer interface information is missing from the show adjacency detail EXEC command.
Conditions This symptom is observed on a Cisco 7200 series router.
Workaround There is no workaround.
•
Symptoms A router may reload when a Frame Relay-to-ATM Service Internetworking (FRF.8) connection is deleted. This symptom may impact router service.
Conditions This symptom is observed on a Cisco MC3810 that is configured for FRF.8 connections.
Workaround Disable Operation, Administration, and Maintenance (OAM) management on the ATM permanent virtual circuit (PVC).
•
Symptoms V.120 calls fail when virtual private dialup network (VPDN) is enabled for dialed number identification service (DNIS) screening.
Conditions This symptom is observed on a Cisco AS5800 and may impact router service.
Workaround There is no workaround.
•
Symptoms Sessions may be lost on a server during a Large Scale Dialout (LSDO) callback and callback does not occur. The output of debug commands may include messages that state that "callback already exists."
Conditions This symptom is observed in a setup in which an LSDO callback is made from a client to a server.
Workaround There is no workaround.
•
Symptoms Layer 2 Tunnel Protocol (L2TP) may get stuck.
Conditions This symptom is observed on a Cisco 7400 series router that is running Cisco IOS Release 12.2(2)DD3 when L2TP parses an invalid control message with a zero-length attribute-value (AV) pair.
Workaround There is no workaround.
•
Symptoms The following error message may be displayed on the console port:
%ISDN-4-ISDN_UNEXPECTED_EVENT: No NLCB:Occurred at ../isdn/l3.c:7032Conditions This symptom is observed in a Signaling System 7 (SS7) environment when a National ISDN-2 (NI2) switch-type call is made.
Workaround Disable console logging and use syslog or buffer logging instead.
•
Symptoms An outgoing gateway (OGW) may release a call in a "RingNoAnswer" scenario with a cause code of 41 (temporary failure).
Conditions This symptom is observed on a Cisco AS5400 that is running Cisco IOS Release 12.2(2)XU3 when ISDN User Part (ISUP)-PRI calls are made. The ISUP receives an address complete message (ACM) and waits for an unexpected answer message (ANM). The call should be released by the egress side with a cause code of 19 (ring no answer).
Workaround There is no workaround.
•
Symptoms PPP calls are not terminated properly on a Layer 2 Tunneling Protocol (L2TP) network server (LNS).
Conditions This symptom is observed if authentication is performed on the LNS.
Workaround There is no workaround.
•
Symptoms A router may reload when you enter the no shutdown interface configuration command on a PRI interface.
Conditions This symptom is observed when the debug isdn event privileged EXEC command is enabled.
Workaround There is no workaround.
•
Symptoms An authentication failure may occur with ISDN calls even though the RADIUS server may indicate that the authentication was successful.
Conditions This symptom is observed on a Cisco AS5800 but may also occur on other access servers after an asynchronous call is terminated by PPP and a new inbound ISDN call that comes in on the B channel (that was carrying the terminated asynchronous call) receives an authentication failure.
Workaround There is no workaround.
•
Symptoms An asynchronous modem user may not be disconnected after the modem fails to allocate an IP address from a pool that is specified by a user RADIUS profile although the asynchronous group configuration includes the ppp ipcp address required interface configuration command that allows calls to be disconnected if the network access server (NAS) fails to allocate an IP address from the pool that is configured under the asynchronous group configuration.
Conditions This symptom is observed on but may not be limited to a Cisco AS5400 that is running Cisco IOS Release 12.2(2)XB5.
Workaround There is no workaround.
•
Symptoms A network access server (NAS) fails to forward calls to a Virtual Private Dial-up Network (VPDN).
Conditions This symptom is observed on a Cisco AS5400 when authentication, authorization, and accounting (AAA) authorization is configured locally on the NAS and the aaa new-model global configuration command is not configured.
Workaround Add the aaa new-model global configuration command to the configuration.
•
Symptoms The PPP idle timeout timer is reset by incoming keepalive packets. When this symptom occurs, the PPP idle timeout timer does not expire and the PPP session does not get closed.
Conditions This symptom is observed on a Cisco 7200 series router.
Workaround There is no workaround.
•
Symptoms The 25th outgoing modem call may not go through.
Conditions This symptom is observed on a Cisco AS5400 but may also occur on other universal gateways or universal access servers in a Signaling System 7 (SS7) Interconnect dial configuration.
Workaround There is no workaround.
•
Symptoms A a Cisco 7200 series router may reload when a multihop user tries to dial in.
Conditions This symptom is observed on a Cisco 7200 series router that is running Cisco IOS Release 12.2(8)T3 and that is configured for virtual private dial-up network (VPDN) multihop.
Workaround There is no workaround.
•
Symptoms A router that is configured as a PPP over Ethernet (PPPoE) client and that has Cisco Express Forwarding (CEF) enabled may reload unexpectedly.
Conditions This symptom is observed when IP Control Protocol (IPCP) completes negotiation.
Workaround Disable CEF.
•
Symptoms A router may pause indefinitely when you configure the pri-group nec-fusion controller configuration command followed by the no pri-group nec-fusion controller configuration command.
Conditions This symptom is observed on a Cisco AS5300 and Cisco AS5800 but may also occur on other platforms.
Workaround There is no workaround.
•
Symptoms A BRI Q Signaling (QSIG) call may not work on a BRI platform. An outgoing call may get rejected with a cause value of "requested channel not available."
Conditions This symptom is observed a Cisco 2600 series router but may also occur on other BRI platforms.
Workaround There is no workaround.
Guest
