/mcpsecurity settings of the device and Unified CM are correct for your deployment. Resetting the device may help because it forces the device to download its latest settings. If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone and view the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate. If the device is a third-party SIP phone, verify that the configuration on the phone is set to UDP or TCP only; Unified CM does not support TLS on third-party phones. Because each third-party phone model has unique configuration interfaces, please refer to the configuration guide for your phone to learn where the third- party phone defines the UDP/TCP setting. 29 AutoRegisterDBError - Auto- registration of a device failed because auto-registration is not allowed for the device type or because an error occurred while adding the auto-registering device to the database (stored procedure). Note that if Unified CM is in mixed mode (System > Enterprise Parameters > Cluster Security Mode = 1), auto- registration is not allowed and the device must be configured manually. If you are not planning to auto-register phones, either manually configure the phone (Device > Phone > Add New), 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 181/343