If you look at the syslog viewer in RTMT, open the alternate syslog that contains that message and use the filter option or just find the message you're interested in. Click on it to view the alert in a window. On the right there will be full definitions of all of the enum values. This same thing can be done for any message with a numeric code. RTMT is always the most up to date place to find what the values mean.
If you can't find it I'll take a screenshot and look on mine when I have a chance to connect to my call manager.
Description: Station device is closing the connection
Explanation: A station device is closing its connection with Unified CM because of the reason that is described in this alarm
Recommended Action: Informational purposes only; no action is required. Also, refer to the reason code definition for additional information.
DeviceName - Device name
ReasonCode - Reason code
Enum Definitions - Reason Code:
0 - deviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action is required; the device will re-register automatically.
1 - sccpDeviceThrottling - (SCCP only) The indicated SCCP device has 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. No action is required; the device will re-register automatically.
2 - keepAliveTimeout - Unified CM did not receive a KeepAlive message from the device. 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 network connectivity between the device and Unified CM, and verify that CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). No action is required; the device will re-register automatically.
3 - dbChangeNotify - An ApplyConfig command was issued from Unified CM Administration resulting in an unregistration. No action is required; the device will re-register automatically.
4 - deviceRegistrationSuperceded - An initial device registration request was received but authentication had not yet completed before a new registration request was received. The first registration request was discarded and re-registration should proceed normally. No action is required; the device will re-register automatically.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...