Cisco MCS-7825-H3-IPC1 Service Manual page 382

Error-Level Alarms
497
20000
30002
30006
30007
30008
30016
30018
30019
30035
Enum Definitions -Reason Code
Value
1
2
3
4
5
6
Cisco Unified Communications Manager Managed Services Guide
6-148
CISCO_6961
CISCO_7905
CISCO_7920
CISCO_7970
CISCO_7912
CISCO_7902
CISCO_IP_COMMUNICATOR
CISCO_7961
CISCO_7936
IP_STE
Definition
Unknown—(SCCP only) The device failed to register for an unknown reason. If this persists,
collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact TAC.
NoEntryInDatabase—(MGCP only) The device is not configured in the Cisco Unified CM
database and auto-registration is either not supported for the device type or is not enabled. To
correct this problem, configure this device via Cisco Unified CM Administration.
DatabaseConfigurationError—The device is not configured in the Cisco Unified CM database
and auto-registration is either not supported for the device type or is not enabled. To correct
this problem, configure this device via Cisco Unified CM Administration.
DeviceNameUnresolveable—For SIP third-party devices, this reason code means that Cisco
Unified CM could not determine the name of the device from the Authorization header in the
REGISTER message. The device did not provide an Authorization header after Cisco Unified
CM challenged with a 401 Unauthorized message. Verify the device is configured with digest
credentials and is able to respond to 401 challenges with an Authorization header. If this is a
Cisco IP phone, the configuration may be out-of-sync. First go to the Cisco Unified Reporting
web page, generate a Unified CM Database Status report, and verify "all servers have a good
replication status". If DB replications looks good, reset the phone. If that still doesn't fix the
problem, restart the TFTP and the Cisco CallManager services. For all other devices, this
reason code means that DNS lookup failed. Verify the DNS server configured via the OS
Administration CLI is correct and that the DNS name used by the device is configured in the
DNS server.
maxDevRegExceeded—Maximum number of device registrations have been reached.
ConnectivityError - The network connection between the device and Cisco Unified CM
dropped before the device was fully registered. Possible causes include device power outage,
network power outage, network configuration error, network delay, packet drops and packet
corruption. It is also possible to get this error if the Cisco Unified CM node is experiencing
high CPU usage. Verify the device is powered up and operating, verify network connectivity
between the device and Cisco Unified CM, and verify the CPU utilization is in the safe range
(this can be monitored using RTMT via CPU Pegging Alert).
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
OL-22523-01