McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 258

↗ View in doc context
page
258
source
cucm/v15/system-error-messages/system-error-messages.md
chunk_id
cucm::v15::system-error-messages::system-error-messages::219

Error Message %UC_CALLMANAGER-4-DaTimeOut: %[AppID=String][ClusterID=String][NodeID=String]: The digit analysis component in Unified CM has timed out. Explanation   The digit analysis component in Unified CM has timed out. This can occur because Unified CM is busy and the resulting delay in processing request and response messages caused the digit analysis component to time out. Recommended Action   In the Service Parameter Configuration window in Cisco Unified CM Administration, check the Cisco CallManager service parameter, Digit Analysis Timer, to confirm that the default value is in use. Use RTMT to monitor the system resources and correct any system issues that might be contributing to high CPU utilization on Unified CM. Error Message %UC_CALLMANAGER-5-MaxCallDurationTimeout: %[MaxCallDuration=UInt] [OriginatingDevice=String][DestinationDevice=String][CallStartTime=UInt][CallStopTime=UInt] [CallingPartyNumber=String][CalledPartyNumber=String][AppID=String][ClusterID=String] [NodeID=String]: Maximum call duration timer has expired. Explanation   An active call was cleared because the amount of time specified in the Maximum Call Duration Timer service parameter has elapsed. If the allowed call duration is too short, you can increase the value. If you do not want a limit on the duration of an active call, you can disable the limit. If the duration is correct but you did not expect a call to ever exceed that duration, check the trace information around the time that this alarm occurred to try to determine if a gateway port had failed to release a call. Recommended Action   If the duration of the call is too short, increase the value in the Cisco CallManager service parameter or disable the maximum duration by setting the Maximum Call Duration Timer parameter to zero. If you suspect a hung gateway port, check the trace files around the time that this alarm occurred to search for the gateway that was involved in the call, then check the status of that gateway to determine if all ports are functioning normally. Error Message %UC_CALLMANAGER-6-MaxHoldDurationTimeout: %[MaxHoldDuration=Int] [OriginatingDevice=String][DestinationDevice=String][HoldStartTime=UInt][HoldStopTime=UInt] [CallingPartyNumber=String][CalledPartyNumber=String][AppID=String][ClusterID=String] [NodeID=String]: Maximum Hold Duration Timer expired. Explanation   A held call was cleared because the amount of time specified in the Maximum Hold Duration Timer service parameter has elapsed. If the allowed call-on-hold duration is too short, you can increase the value. If you do not want a limit on the duration of a held call, you can disable the limit. Recommended Action   If the duration of the hold time is too short, increase the value in the Cisco CallManager service parameter or disable the maximum duration by setting the Maximum Hold Duration Timer parameter to zero 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 258/343