Cisco Internal Error Codes
Contents |
call. This section provides procedural and reference information used to troubleshoot gateway-detected errors and resolve problems on the gateway and with other VoIP network entities. Because fields within the cisco 8742hdc error codes IEC identify which network entity and subsystem originated an error, they can be
Cisco 4742hdc Error Codes
used to diagnose and isolate failures that can cause call disconnects. Guide Contents Troubleshooting Cisco IOS Voice OverviewDebug Command
Cisco Vpn Error Codes
Output on Cisco IOS Voice GatewaysFiltering Troubleshooting OutputCisco VoIP Internal Error CodesTroubleshooting Cisco IOS Voice TelephonyTroubleshooting Cisco IOS Voice ProtocolsTroubleshooting Cisco IOS Telephony ApplicationsMonitoring the Cisco IOS Voice NetworkCause Codes and Debug
Cisco 8642 Error Codes
Values Contents 1 Troubleshooting Two-Stage Dialing Failures 1.1 Symptom 1.2 Problem Description 1.3 Troubleshooting Tasks 2 Troubleshooting Socket Failures 2.1 Symptom 2.2 Problem Description 2.3 Troubleshooting Tasks 3 Gatekeeper-Specific IECs 3.1 Verifying IEC Options 3.1.1 Prerequisites 3.1.1.1 SUMMARY STEPS 3.1.1.2 DETAILED STEPS 3.1.2 Displaying IEC Options 3.1.2.1 SUMMARY STEPS 3.1.2.2 DETAILED STEPS Troubleshooting Two-Stage Dialing Failures The following example shows how to troubleshoot a two-stage cisco ucs error codes dialing failure. Symptom The Cisco router or gateway rejects a call placed by a PSTN ISDN user after all the digits have been dialed. Problem Description The PSTN user enters a destination number that is routed through the PSTN ISDN switch, which sends an ISDN SETUP message to the router. The router tags the incoming call leg and sends back an ISDN CONNECT message. The caller receives second dial tone. The router then enters the digit collection stage to use the collected digits to route the call to the next hop, at which point the router rejects the call. Troubleshooting Tasks Perform the following steps to determine the reason for call failure. 1. Use the voice iec syslog command to enable displaying of IECs as they are encountered in real-time. 2. Use the voice iec statistics type iec command to configure the collection of IEC statistics. 3. Use the show running-config command to verify IEC, ISDN, and dial-peer configuration, as shown in the following partial sample output: Router> show running-config Building configuration... ! voice rtp send-recv ! voice service voip The following lines show the IEC configuration: voice iec syslog no
Voice GatewaysFiltering Troubleshooting OutputCisco VoIP Internal Error CodesTroubleshooting Cisco IOS Voice TelephonyTroubleshooting Cisco IOS Voice ProtocolsTroubleshooting Cisco IOS Telephony ApplicationsMonitoring the Cisco IOS Voice NetworkCause Codes and Debug Values Contents 1 Enabling IEC Syslog Reporting and cisco anyconnect error codes Configuring Cause Code Mapping: Example 2 Verifying IEC Configuration: Example 2.1 Sample Output from cisco asa error codes the show running-config Command: Example 2.2 Sample Output from the show voice iec description Command: Example 2.3 Sample Output from cisco cable box error codes the show voice statistics iec Command: Example 2.4 Sample Output from the clear voice statistics Command: Example 2.5 Sample Output from the show voice cause-code category-q850 Command: Example Enabling IEC Syslog Reporting and Configuring http://docwiki.cisco.com/wiki/Cisco_IOS_Voice_Troubleshooting_and_Monitoring_--_VoIP_Network_Troubleshooting_Using_Cisco_VoIP_Internal_Error_Codes Cause Code Mapping: Example In the following example, IEC syslog reporting and cause-code mapping are enabled: enable configure terminal voice iec syslog voice cause-code error-category 128 q850-cause 27 Verifying IEC Configuration: Example In the following examples, the output is displayed for each command used to verify IEC configuration: Sample Output from the show running-config Command: Example Router# show running-config Building configuration... Current configuration:2791 bytes ! version 12.2 http://docwiki.cisco.com/wiki/Cisco_IOS_Voice_Troubleshooting_and_Monitoring_--_Cisco_VoIP_Internal_Error_Codes_Configuration_Examples no parser cache no service pad service timestamps debug uptime service timestamps log uptime no service password-encryption service internal ! hostname GW-1 ! no boot startup-test ! ! resource-pool disable spe default-firmware spe-firmware-1 ! ! aaa new-model ! ! aaa group server radius h323 ! aaa authentication login h323 group radius group h323 aaa authorization config-commands aaa authorization exec h323 group h323 aaa accounting connection h323 start-stop group radius group h323 aaa session-id common ! isdn switch-type primary-5ess ! The following lines show optional IEC configuration information: voice iec syslog voice cause-code error-category 128 q850-cause 27 error-category 129 q850-cause 38 ! ! ! controller T1 3/0 framing esf linecode b8zs pri-group timeslots 1-24 ! controller T1 3/1 shutdown framing sf linecode ami gw-accounting aaa ! ! ! interface FastEthernet0/0 ip address 172.18.195.28 255.255.255.0 no ip route-cache no ip mroute-cache duplex full speed 100 no cdp enable h323-gateway voip interface h323-gateway voip id GK-1 ipaddr 172.18.195.41 1718 h323-gateway voip h323-id GW-1 ! interface FastEthernet0/1 no ip address no ip route-cache no ip mroute-cache shutdown duplex auto speed auto no cdp enable ! interface Serial0/0 no ip address no ip route-cache no ip mroute-cache shutdown clockrate 2000000 no cdp enable ! interface Seria
My Cisco Cisco Unified Communications Manager (CallManager) System Error Messages for Cisco Unified Communications Manager 8.0(1) Hierarchical Navigation HOME SUPPORT PRODUCT SUPPORT UNIFIED COMMUNICATIONS CISCO UNIFIED http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/8_x/ccmalarms801.html COMMUNICATIONS MANAGER (CALLMANAGER) TROUBLESHOOT AND ALERTS ERROR AND SYSTEM MESSAGES System Error Messages for Cisco Unified Communications Manager 8.0(1) Error Message CCM_CALLMANAGER-CALLMANAGER-2-CallManagerFailure : Indicates an internal failure in Unified CM Additional Text[String] Host Name of Hosting Node[String] Host Node IP Address[String] Reason code[Enum] ExplanationThis alarm indicates that an internal failure occurred in the Cisco CallManager service. The service should restart in an attempt to clear error codes the failure. Recommended ActionMonitor for other alarms and restart Cisco CallManager service, if necessary. Collect the core file if available, SDL and CCM/SDI trace files (you can gather these from Trace and Log Central in RTMT using the Collect Files feature) and contact the Cisco Technical Assistance Center (TAC). Reason Code - Enum Definitions Enum Definitions - Reason Value Definition 1 Unknown - Unified CM cisco internal error has failed for an unknown reason 2 HeartBeatStopped - An internal heart beat has stopped after the preceding heart beat interval 3 RouterThreadDied - An internal thread has failed 4 TimerThreadDied - An internal thread has failed 5 CriticalThreadDied - An internal thread has failed Error Message CCM_CALLMANAGER-CALLMANAGER-5-SDLLinkISV : SDL link to remote application restored Remote Application IP Address[String] Unique Link ID[String] Local Node ID[UInt] Local Application ID[Enum]Remote Node ID[UInt] Remote Application ID[Enum] ExplanationThis alarm indicates that the local Unified CM has gained communication with the remote Unified CM. Note that the remote Unified CM should also indicate SDLLinkISV with a different LinkID. Recommended ActionInformational only; no action is required Reason Code - Enum Definitions Enum Definitions - LocalApplicationId Value Definition 100 CallManager Enum Definitions - RemoteApplicationId Value Definition 100 CallManager Error Message CCM_CALLMANAGER-CALLMANAGER-1-SDLLinkOOS : SDL link to remote application is out of service Remote Application IP Address[String] Unique Link ID[String] Local Node ID[UInt] Local Application ID[Enum]Remote Node ID[UInt] Remote Application ID[Enum] ExplanationThis alarm indicates that the local Unified CM has lost communication with the remote Unified CM. This alarm usually indicates that a node has gone out of service (whether intentionally for
be down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 04 Oct 2016 23:51:12 GMT by s_hv1002 (squid/3.5.20)