6-229
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Enum Definition
126 TONE_ANNOUNCEMENT_PLAYER
131 SIP_TRUNK
132 SIP_GATEWAY
133 WSM_TRUNK
134 REMOTE_DESTINATION_PROFILE
227 7915_12_BUTTON_LINE_EXPANSION_MODULE
228 7915_24_BUTTON_LINE_EXPANSION_MODULE
229 7916_12_BUTTON_LINE_EXPANSION_MODULE
230 7916_24_BUTTON_LINE_EXPANSION_MODULE
232 CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254 UNKNOWN_MGCP_GATEWAY
255 UNKNOWN
30027 ANALOG_PHONE
30028 ISDN_BRI_PHONE
30032 SCCP_GATEWAY_VIRTUAL_PHONE
Code Reason
1 Unknown - The device has unregistered for an unknown reason. If the device does not
reregister within 5 minutes, verify it is powered-up and verify network connectivity
between the device and Cisco Unified CM.
6 ConnectivityError - Network communication between the device and Cisco Unified CM
has been interrupted. 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).
8 DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or
internal error. No action required; the device will reregister automatically.
9 CallManagerReset - A device reset was initiated from Cisco Unified CM Administration,
either due to an explicit command from an administrator, or due to internal errors
encountered. No action necessary, the device will reregister automatically.
10 DeviceUnregistered - The device has explicitly unregistered. Possible causes include a
change in the IP address or port of the device. No action is necessary, the device will
reregister automatically.
11 MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed
because of an illegal format. Possible causes include a missing Call-ID header, a missing
AoR in the To header, and an expires value too small. Verify the REGISTER message
does not suffer from any of these ills.
To Next Page
Loading...
Need help?
General