/mcp[NodeID=String]: Indicates the amount of time it took for Unified CM to initialize each state in the initialization process. Explanation Indicates the amount of time required to complete initialization for the specified state Recommended Action Informational purposes only; no action is required Error Message %UC_CALLMANAGER-6-CMTotalInitializationStateTime: %[TotalInitializationTime=String] [TotalInitializationTimeMs=UInt][AppID=String][ClusterID=String][NodeID=String]: Total amount of time it took for Unified CM to complete initialization. Explanation Indicates the amount of time required to complete the total system initialization Recommended Action Informational purposes only; no action is required Error Message %UC_CALLMANAGER-1-CMOverallInitTimeExceeded: %[CMOverallInitializationTime=Int] [AppID=String][ClusterID=String][NodeID=String]: Initialization of the Unified CM system has taken longer than allowed by the System Initialization Timer service parameter; the system automatically restarts to attempt initialization again. Explanation The required time to initialize Unified CM has exceeded the time allowed by the Cisco CallManager service parameter, System Initialization Timer; as a result, the system will automatically restart to attempt initialization again. Initialization may have failed due to an increase in system size, due a database error, due to a large amount of new devices added to the system, or any number of other potential causes. Recommended Action Use RTMT to discover the number of devices and number of users in the system and evaluate whether the numbers seem accurate. Try increasing the value of the Cisco CallManager service parameter, System Initialization Timer, in the Service Parameters Configuration window in Cisco Unified CM Administration. If increasing the time in the System Initialization Timer service parameter does not correct this issue, contact the Cisco Technical Assistance Center (TAC). Error Message %UC_CALLMANAGER-4-DigitAnalysisTimeoutAwaitingResponse: % [TranslationPatternTriggeringPoint=String][PolicyDecisionPoint=String][AppID=String] [ClusterID=String][NodeID=String]: Unified CM sent a routing request to the policy decision point but the request timed out without a response. Explanation Unified CM was unable to complete the routing request before timing out. This timeout could occur due to low system resources, high CPU usage, or a high volume of call activities on this Unified CM node. Unified CM applies the Call Treatment on Failure that is configured for the External Call Control Profile associated with this call. Recommended Action Check the External Call Control object in Real-Time Monitoring Tool (RTMT) to see whether the ExternalCallControlEnabledCallAttempted counter is spiking. A dramatic increase in that counter indicates an unusually high number of calls at this time which could result in reduced system resources. Check the QueueSignalsPresent2-Normal counter for persistent (long) high signal queue. If the long signal queue exists, check whether the Code Yellow alarm has already issued and check the system CPU and memory usage for this Unified CM node. Follow the recommended actions for Code Yellow alarm if the Code Yellow alarm has fired. For high CPU usage, use RTMT to determine which areas may be contributing to the high CPU usage. If this alarm persists, collect system performance data (such as the percentage of Memory, Page and VM usage, partition read and write bytes per second, the percentage of CPU usages of all the processes, and the processor IOWait percentage) and contact Cisco Technical Assistance Center (TAC). 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 274/343