HI Joseph
The list you are looking for can be found at the link mentioned below :
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/8_x/ccmalarms801.html
Look for the alarm "CCM_CALLMANAGER-CALLMANAGER-4-DeviceUnregistered" .
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-DeviceUnregistered : Device unregistered Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device type [Enum]Device description [String] Reason Code [Enum]IPV6Address [String] IPAddressAttributes [Enum]IPV6AddressAttributes [Enum]
Explanation A device that has previously registered with Unified CM has unregistered. In cases of normal unregistration with reason code 'CallManagerReset', 'CallManagerRestart', or 'DeviceInitiatedReset', the severity of this alarm is lowered to INFORMATIONAL. A device can unregister for many reasons, both intentional such as manually resetting the device after a configuration change, and unintentional such as loss of network connectivity. Other causes for this alarm could include a phone being registered to a secondary node and then the primary node coming online, which causes the phone to rehome to the primary Unified CM node. Or, lack of a KeepAlive being returned from the Unified CM node to which this device was registered. Unregistration also occurs if Unified CM receives a duplicate registration request for this same device
Enum Definitions - Reason
| Value | Definition |
|---|
| 1 | Unknown - The device has unregistered for an unknown reason. If the device does not re-register within 5 minutes, verify that it is powered up and verify that there is network connectivity between the device and Unified CM. |
| 6 | ConnectivityError - Network communication between the device and 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 Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). |
| 8 | DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action required; the device will re-register 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 re-register 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 re-register 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, or an expires value that is too small. Check the REGISTER message for any of these issues and if you find one, correct the issue. |
| 12 | SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. |
| 13 | KeepAliveTimeout - A KeepAlive message was not received. 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 Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). |
| 14 | ConfigurationMismatch (SIP only) The configuration on the device does not match the configuration in Unified CM. This can be caused by database replication errors or other internal Unified CM communication errors. Go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report and verify "all servers have a good replication status". You can also go to the Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. If this device continues to unregister with this reason code, go to the Device Configuration page in Unified CM Administration for the device indicated in this alarm and click Save. This generates a change notify message to the Cisco CallManager and TFTP services and rebuilds a new configuration file for the device. If the problem still persists, restart the TFTP service and the Cisco CallManager service. |
| 15 | CallManagerRestart - A device restart was initiated from Unified CM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. No action is necessary; the device will re-register automatically. |
| 16 | DuplicateRegistration - Unified CM detected that the device attempted to register to two nodes at the same time. Unified CM initiated a restart to the phone to force it to re-home to a single node. No action is necessary; the device will re-register automatically. |
| 17 | CallManagerApplyConfig - An ApplyConfig action was performed in Unified CM Administration resulting in an unregistration. No action is necessary; the device will re-register automatically. |
| 18 | DeviceNoResponse - The device did not respond to a reset or restart notification, so it is being forcefully reset. If the device does not re-register within 5 minutes, confirm that it is powered up and confirm that there is network connectivity between the device and Unified CM. |
| 19 | EMLoginLogout - The device has been unregistered due to an Extension Mobility login or logout |
| 20 | EMCCLoginLogout - The device has been unregistered due to an Extension Mobility Cross Cluster login or logout |
Regards
Aditya Gupta
