Core Issue In some cases, Cisco IP phone users or Plain Old Telephone Service (POTS) users connected to a Cisco IOS® gateway may not hear a busy tone when they call a busy number on the Public Switched Telephone Network (PSTN). This is a problem when the PSTN disconnects the call with a normal call clearing cause code, instead of user busy . Instead of setting the cause code to user busy , the PSTN switch sets the progress indicator information element on the DISCONNECT message to eight, indicating that inband information is available. The disconnect message, however, causes the gateway and Cisco CallManager to release the call. Resolution Issue the voice call convert-discpi-to-prog global configuration command, available in Cisco IOS Software Release 12.2(1). Doing this converts a DISCONNECT message with a progress indicator value of eight to a PROGRESS message with a progress indicator value of eight so that audio is cut through and the Cisco IP phone hears the disconnect tones or announcement from the PSTN. For further information, refer the document Troubleshooting No Busy Tone and No Announcement Messages on ISDN-VoIP (H.323) Calls. For more details on troubleshooting this and various other issues refer to The Cisco Press book Troubleshooting Cisco IP Telephony [ISBN 1-58705-075-7]. Problem Type Call connection (Connection quality: One-way audio, no busy tone, dropped calls, etc.) Call Connection Dead air Disconnect tone Call connection establishment Disconnection failure Announcement Busy tone When Problem Occurs While call is connecting End Where Problem is Heard or Device Type Involved IP phone Call Topology and Direction IP network > PSTN/PBX/gateway Q931 and H225 Call Setup Messages DISCONNECT PROGRESS Common Q931 Information Elements 8 - In-band information or an appropriate pattern is now available sent in alert 80 - Normal Disconnect Progress Indicator Alteration voice call convert-discpi-to-prog ... View more

Core Issue There are several reasons for Cisco CallManager to play Tone on Hold (ToH) to an endpoint that has been configured for Music on Hold (MoH): One reason is a mismatch between the codec configuration used by the MoH server and the region in which the endpoint is registered. For example, the MoH server advertised only a capability of G.711 mu-law. If an endpoint is in another region enforcing the G.729 codec, the Cisco CallManager chooses ToH because a stream cannot be played to this endpoint. If location-based connection admission control is being used and there is no bandwidth available, then Cisco CallManager sends ToH rather than MoH. If there are no available audio streams, it is because the MoH server has a finite number of unicast streams it can generate. Exceeding this limit causes Cisco CallManager to play ToH. Resolution To resolve this issue, ensure that each of these issues are not causing ToH to be played and restart the IPVMS application service. Refer the following document for more information Music On Hold topic of the Cisco CallManager Features and Services Guide CallManager Music on Hold Frequently Asked Questions Chapter 12 of Cisco Press book Troubleshooting Cisco IP Telephony [ISBN: 1-58705-075-7] Problem Type Call connection (Connection quality: One-way audio, no busy tone, dropped calls, etc.) Call control software (CallManager, CallManager Express, ICS7750, SRST, SS7 call agents) When Problem Occurs While on hold Music on Hold Device Counters in RTMT MOHOutOfResources Codec Type Codec mismatch Music on Hold (MoH) Audio streams ... View more

Core Issue A terminal length configuration value of 0 causes output to scroll by without stopping. Resolution If the output of show commands scrolls by without stopping, you can issue the set length command to control the number of lines displayed at a time. This is the syntax: set length number [default] This is a description of the command syntax: Number. The number of lines to display on the screen. Valid values are from 0 to 512. Default (optional). The keyword to set the number of lines in the terminal display screen for the current administration session and all other sessions. The default value is 24 lines upon starting a session. Setting the screen length to 0 turns off the scrolling feature and causes the entire output to display at once. Unless you issue the default keyword, a change to the terminal length value applies only to the current session. When you issue the clear config command, the number of lines in the terminal display screen is reset to the default of 100. The default keyword is available only in privileged mode. This example shows how to set the screen length to 60 lines: Console> (enable) set length 60 Screen length for this session set to 60. Console> (enable) This example shows how to set the default screen length to 40 lines: Console> (enable) set length 40 default Screen length set to 40. For Cisco IOS®-based devices, use the EXEC mode terminal length screen-length command. For example, to set the number of lines displayed to 25 on a Cisco IOS-based device, issue this command: Router# terminal length 25 Once the changes have been made and the output from a single show command overflows, the display screen is followed by the --More-- prompt.  At the --More-- prompt, you have these options: Press Ctrl+C, q, or Q to interrupt the output and return to the command prompt. Press the spacebar to display an additional screen of output. Press Enter to display one more line of output. ... View more

Core Issue By default, all CatOS Layer-2 ports are trunking in the Auto mode.  This means they send out Dynamic Trunking Protocol (DTP) frames periodically. When you connect this type of port to a native Cisco IOS® Layer-3 port, they do not understand any Layer 2 trunking frames, and hence, you receive Input errors, the Input queue drops and you receive WrongEncap errors respectively. Resolution Complete one of these steps in order to resolve this issue: Turn off the default trunking on the CATOS switch with the set trunk mod/port off command. Set the native Cisco IOS switch port to a Layer 2 port with the switchport command and move the Layer 3 information to a Switch Virtual Interface (SVI), for example, a layer 3 VLAN. Note: When Cisco IOS port is made into Layer 2 switchport, the default trunking mode is dynamic desirable mode, which means it sends out the DTP frames and also understands the DTP frames sent by the CATOS switch. Since auto-desriable results in a trunk, the link comes up as trunk and works fine with no errors. For more information on default trunking modes refer, Dynamic Trunking Protocol part of Best Practices for Catalyst 4500/4000, 5500/5000, and 6500/6000 Series Switches Running CatOS Configuration and Management ... View more

What is PAT? Port address translation (PAT) is a function that allows multiple users within a private network to make use of a minimal number of IP addresses. Its basic function is to share a single IP public address between multiple clients who need to use the Internet publicly. It is an extension of network address translation (NAT).Port address translation is also known as overload or port overload. Core issue Static Network Address Translation (NAT) works in PIX Firewall version 6.3(1). However, global Port  Address Translation (PAT) does not work properly. When the PIX configuration is changed to use global PAT, all Telnet and Secure Shell (SSH) connections fail. Note: Even the clear xlate command does not resolve the issue. Resolution For a workaround, upgrade the PIX software to version 6.3(3) or later. Refer to Software Download: Cisco PIX Security Appliance Software. ... View more

Core Issue The %O NLINE-SP-6-DNLDFAIL:Module [dec], Proc [dec],  Runtime image download failed because of [chars] error message indicates that the system is unable to download the runtime image to the indicated module and processor. The first [dec] is the module number, and the second [dec] is the processor number. [chars] is the reason that the system was unable to download to runtime image. Resolution No action is required. The system recovers without user intervention. If the error still happens contact Cisco Technical Assistance Center (TAC) before replacing the module. ... View more

Core Issue The format of the Dynamic Host Configuration Protocol (DHCP) messages is based on the format of Bootstrap Protocol (BOOTP) messages. This ensures: support for BOOTP relay agent functionality when the ip helper-address command is issued interoperability between BOOTP clients and DHCP servers BOOTP relay agents eliminate the need for the deployment of a DHCP server on each physical network segment. If the no ip boot server command is configured, it does not stop the forward of the DHCP packets to the DHCP server. Instead, it continues to forward the DHCP request packet with the giaddr field populated with 0.0.0.0 as it originated from the client and that is forwarded to the DHCP server. If the giaddr field is set to 0.0.0.0 , the DHCP server does not assign an IP address to its client. Therefore, the ip bootp server command becomes mandatory in order for a switch to function properly as a DHCP relay agent and to populate the giaddr field appropriately. In some scenarios, the clients connected to the switch do not obtain the IP address because DHCP requests can be duplicated and sourced from multiple VLANs if a loop exists in the network. For example, if you connect a PC to an HUB, it can cause an Spanning-Tree Protocol (STP) loop in the network. This occurs because when you connect a PC to a HUB, it does not get an IP address from the DHCP address and tries to points its MAC address for two different ports at the same time. Resolution In order to resolve this issue, the ip bootp server command must be enabled in order for routers to use the ip helper-address command in order to forward DHCP User Datagram Protocol (UDP) broadcasts and for the router to properly act as a DHCP relay agent on behalf of the DHCP client. The ip bootp server command listens to BOOTP requests (UDP port 67/68) and acts upon them as a DHCP relay agent. So, the specific funtion of this command is to perform the DHCP relay function, which is to set the giaddr field in the DHCP request packet with the IP address of the interface of the router from which the DHCP request came. Note: In newer Cisco IOS® software releases, the service dhcp command handles the DHCP relay agent function instead of the ip bootp server command. Refer to these documents for more information: Configuring DHCP Understanding and Troubleshooting DHCP in Catalyst Switch or Enterprise Networks ... View more

Core Issue The issue happens when you want to run Netflow and Microflow policing at the same time. It is sometimes observed that Netflow fails to start exporting when a Microflow policer is already active. The Microflow policer continues to work. Alternatively, a Microflow policer does not function when Netflow is already enabled on a Catalyst 6500 and the policer configuration is applied. Netflow continues to function since it was enabled first. The following are the limitations regarding NDE and microflow policers: Full flow microflow policer works only when NDE is configured to Src, Dest, Dest-Src or Full. Src-only / Dest-only Microflow policer will not work, when NDE is configured. For addtional information refer to, Flow Masks. Resolution The only condition that allows the NDE and Microflow policer to work is to use the mls flow ip full command in global configuration mode which configures the flow mask for NDE. The Microflow policers do not match any IPv6 traffic. Note : If you use mls flow ip full command it will consume more memory in MLS because it will have more entries based on layer 4 information. It is recommended to keep the size of the MLS cache below 32K entries. To keep the size of the MLS cache down, enable mls aging fast. For additional information refer to, Configuring NetFlow Data Export (NDE). ... View more

Core issue There are several reasons the ping command could be unsuccessful, ranging from physical layer to network layer problems. Resolution For information on how to resolve this issue, refer to these TAC Case Collection (TAC CC) solutions: Cannot access internal network or host Cannot access the internal host from multiple sources Cannot access devices on a directly connected subnetwork ... View more

Core issue The User Changable Password (UCP) is utility to change user password (local acs database) that can be used only when the user account status is active. As UCP utility is not interactive, you are not prompted to change the password. The UCP is used when you want to change your password and not when you are forced to do it. Note: The UCP does not work if the user account is expired due to password expiry. Resolution Complete these steps in order to change your password with the UCP before password expiry: On a web browser, open the UCP page with the administrator-provided URL. Type your username and password, and then click Submit. The Change Password page opens. The username you entered on the previous page appears in the Username box. Specify this information: Current Password—Type your current password. New Password—Type the new password. Your password possibly needs to fulfill certain special requirements, such as minimum length. Check with your system administrator for details. Confirm New Password—Re-type the new password. Choose Submit. Your password is changed. Choose Logout in order to exit. Refer to User Guide for Cisco Secure ACS User-Changeable Passwords for more information. ... View more

Resolution At present, there is no way to configure IP filters on the WLSE. However, one can authenticate users using a local authentication module or using an external server to do RADIUS or TACACS+ authentication. Once you have selected and configured a module, all authentication transactions are performed by the authentication service associated with that module. Users log in with the user ID and password associated with the current authentication module. Note that you must create all user roles on the local authentication module. Refer to these documents for more information: For more information WLSE and WLSE Express, refer to Getting Started . For more information on security, refer to the Managing Security section of Managing the Appliance . For more information, refer to Configuring the CiscoWorks Wireless LAN Solution Engine TACACS+/RADIUS Authentication Using Cisco Secure ACS . ... View more

Resolution This feature is implemented in Cisco IOS Software Release 12.4(2) onwards. Once Cisco IOS is upgraded to anything later than 12.4(2)T, you can do this configuration: #configure terminal (config)#voice service voip (conf-voip-serv)#sip (conf-serv-sip)#[no | default] localhost dns: Example: (conf-serv-sip)#localhost dns:name1.com In order to disable the usage of DNS name under specific dial-peers, you can configure the dial-peer with: #configure terminal (config) dial-peer voice 100 voip (config-dial-peer)#[no | default] voice-class sip localhost [dns]: In the CLI, there is a provision to exclude a specific dialpeer from the use of the global configuration under voice service voip. In order to do that, use the no version command under dialpeer. This change has been made to allow for the case when the global localhost command is configured and most but not all the dialpeers want to use that config. For the dialpeers that want to fallback to the use of the IP address in the From, Call-ID & RPID headers, this command can be useful.The default version of the command causes the dial-peer to use the globally configured CLI under voice service voip, SIP. Example: dial-peer voice 6 voip no voice-class sip localhost Refer to Cisco IOS SIP Configuration Guide for more information. ... View more

Core Issue: A possible reason for the error message is that the client name is already deleted from the database. The exact message looks similar to this: day month date time year [SECURITY] apf_ms.c 2670: Unable to delete usernamewirelessconnection for mobile 00:00:00:00:00:00 Resolution: When you try to delete the user from the database entry of the WiSM you get this error message. Try one of the steps below As a workaround Change the external identity of the client, but this would make the client to  loose anonymous authentication, gained with EAP-FAST or PEAP methods. Reboot the device Upgrade the version of the Module Refer to these documents for more information WiSM Troubleshooting FAQ Download Software Cisco Wireless LAN Controller Configuration Guide, Release 4.0 ... View more

Core Issue: A possible reason for the error message is that the client name is already deleted from the database. The exact message looks similar to this: day month date time year [SECURITY] apf_ms.c 2670: Unable to delete usernamewirelessconnection for mobile 00:00:00:00:00:00 ... View more

Core Issue Video calls can take longer to complete than voice calls because there is a delay inherent in H.320 bonding. If these calls are set to auto answer, they fail. The calls do work correctly when the IP phone is set to answer manually. Several timers in the Cisco Unified CallManager are tuned, by default, in order to make voice calls process as fast as possible. These timers can cause video calls to fail. Therefore, modify the default values of these timers in order to support H.320 gateway calls: The H.245TCSTimeout The Media Exchange Interface Capability Timer The Media Exchange Timer Resolution Cisco recommends that each of these timers — the H.245TCSTimeout, the Media Exchange Interface Capability Timer, and the Media Exchange Timer — be increased to 25. In order to modify the timers, go to Service Parameters in the Cisco Unified CallManager Administration. Note: These are cluster-wide service parameters, so they affect calls to all types of H.323 devices, including voice calls to existing H.323 Cisco voice gateways. Refer to the Gateways for Video Telephony section of Gateways, as well as Release Notes for Cisco IPVC 3511 MCU, Cisco IPVC 3511 MCU E, and Cisco IPVC 3540 MCU Module Release 3.2.224 for more information on timers and Multipoint Control Units (MCUs). ... View more