/mcpthe higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth. Finally, if RSVP Agent allocation fails due to MTP/transcoder not supporting RSVP functionality or capability mismatch or all the resources being in use, consider installing additional MTP or transcoder devices which support RSVP functionality. Error Message %UC_CALLMANAGER-2-MaxCallsReached: %[Count=Int][AppID=String][ClusterID=String] [NodeID=String]: Maximum calls of simultaneous calls in this node has been reached. Explanation The maximum number of simultaneous connections in a Unified CM node has been reached. This is an internally-set value and when it is exceeded, Unified CM starts throttling calls to keep the number of calls below the internal threshold. Recommended Action In the Real-Time Monitoring Tool, check the CallsActive counter in the Cisco CallManager object for an unusually high number of calls. Internal mechanisms will attempt to correct this condition. If this alarm continues to occur, collect existing SDL and CCM trace files and check to be sure that CM Services trace collection in Cisco Unified CM Serviceability is set to Detailed level. Error Message %UC_CALLMANAGER-1-DBLException: %[ErrorCode=Int][ExceptionString=String][AppID=String] [ClusterID=String][NodeID=String]: An error occurred while performing database activities. Explanation A severe database layer interface error occurred. Possible causes for this include the database being unreachable or down or a DNS error. Recommended Action Review the System Reports provided in the Cisco Unified Reporting tool, specifically the Unified CM Database Status report, for any anomalous activity. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. Check network connectivity to the server that is running the database. If your system uses DNS, check the DNS configuration for any errors. If the cause is still not identified, collect SDL and SDI traces and contact the Cisco Technical Assistance Center (TAC). Error Message %UC_CALLMANAGER-3-ICTCallThrottlingStart: %[DeviceName=String][IPAddress=String] [{Optional}DeviceType=Enum][{Optional}Description=String][AppID=String][ClusterID=String] [NodeID=String]: Unified CM stops handling calls for the indicated H.323 device due to heavy traffic or a route loop over the H.323 trunk. Explanation Unified CM has detected a route loop over the H.323 trunk indicated in this alarm. As a result, Unified CM has temporarily stopped accepting calls for the indicated H.323 trunk. It's also possible that a high volume of calls are occurring over the intercluster trunk, which has triggered throttling. Recommended Action In Real-Time Monitoring Tool, check the CallsActive and CallsInProgress counters for unusual activity on the indicated H.323 trunk. If the CallsActive count is significantly higher than usual, a traffic load issue may be occurring where the demand to send calls over the trunk is greater than the trunk's capacity. Monitor the situation and collect existing trace files. If the ICTCallThrottlingEnd alarm is not issued in a reasonable amount of time as deemed by your organization, contact the Cisco Technical Assistance Center (TAC) and supply the trace information you have collected. For a routing loop condition, the CallsInProgress counter will be significantly higher than usual. By examining trace files and CDR data for calls that occurred over the indicated trunk, you may be able to detect a translation pattern, route list or other routing mechanism that is part of the loop. Update the routing mechanism that resulted in the loop (generally the same number is configured on both near end and far end devices) and then reset the affected route list in an attempt 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 266/343