/mcpmonitor 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 5/24/26, 3:34 AM System Error Messages for Cisco Unified Communications Manager 15 - Cisco https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/15_x/ccmalarms15.html 203/343