/mcpto clear the route loop and if that fails, reset the affected trunk. Reason Code - Enum Definitions Enum Definitions - DeviceType Value Definition 125 TRUNK Error Message %UC_CALLMANAGER-5-ICTCallThrottlingEnd: %[DeviceName=String][IPAddress=String] [{Optional}DeviceType=Enum][{Optional}Description=String][AppID=String][ClusterID=String] [NodeID=String]: Unified CM starts handling calls again for the indicated H.323 device. Explanation Unified CM has ceased throttling calls on the indicated H.323 device Recommended Action Notification purposes only; no action is required Reason Code - Enum Definitions Enum Definitions - DeviceType Value Definition 125 TRUNK Error Message %UC_CALLMANAGER-2-CodeYellowEntry: %[AverageDelay=UInt][EntryLatency=UInt] [ExitLatency=UInt][SampleSize=UInt][TotalCodeYellowEntry=UInt][HighPriorityQueueDepth=Long] [NormalPriorityQueueDepth=Long][LowPriorityQueueDepth=Long][AppID=String][ClusterID=String] [NodeID=String]: Unified CM has entered Code Yellow state. Explanation Unified CM has initiated call throttling due to unacceptably high delay in handling incoming calls Recommended Action Memory problems or high CPU usage are generally at the root of a Code Yellow condition. A bad disk could also be the cause. Also, trace level settings can consume tremendous amounts of CPU (especially when the Enable SDL TCP Event Trace checkbox is enabled on the SDL Trace Configuration window in Cisco Unified Serviceability). Use RTMT to check for memory leaks, causes of any CPU spikes, and determine whether the server has sufficient memory for the tasks expected of this server. Run server diagnostics to determine if the disk is bad, and examine/reconfigure the SDL trace settings in Unified Serviceability to ensure that trace settings are not contributing to Code Yellow. You can determine the level of fragmentation on the hard disk by issuing the File Fragmentation command from the CLI for the trace directories. After taking one or more of these corrective actions, monitor the situation and collect existing trace files. If the CodeYellowExit alarm is not issued in a reasonable amount of time as deemed by your organization, or if the system is frequently triggering the CodeYellowEntry alarm, contact the Cisco Technical Assistance Center (TAC) and supply the trace information you have collected Error Message %UC_CALLMANAGER-5-CodeYellowExit: %[AverageDelay=UInt][EntryLatency=UInt] [ExitLatency=UInt][SampleSize=UInt][TimeSpentInCodeYellow=UInt] [NumberOfCallsRejectedDueToCallThrottling=UInt][TotalCodeYellowExit=UInt] 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 267/343