McDewey

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

Page 236

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

2 Transcoder 3 Conference bridge 4 Music On Hold 5 Monitor bridge 6 Recorder 7 Annunciator 8 Built-in bridge 9 RSVP agent Error Message %UC_CALLMANAGER-4-RouteListExhausted: %[RouteListName=String][AppID=String] [ClusterID=String][NodeID=String]: An available route could not be found in the indicated route list. Explanation   An available route could not be found in the indicated route list. This alarm is generated when all members' status is unavailable or busy or when the member is down (out of service), not registered, or busy. Recommended Action   Consider adding additional routes in the indicated route list. For shared line when some phones are not ringing, check the busy trigger and maximum call settings of shared line phones; check whether there are some outstanding calls on that DN. When one shared line phone answers an incoming call, the other shared line phone cannot see that remote-in-use call; check the privacy setting of the phone that answers the call. Try to make a call directly to the member, bypassing the route list, to verify that there is not a device or connectivity issue. If you cannot identify the cause through these steps, gather the CCM (SDI) trace and contact the Cisco Technical Assistance Center; TAC may be able to locate a cause code which may provide additional explanation for this alarm. Error Message %UC_CALLMANAGER-4-HuntListExhausted: %[HuntListName=String][AppID=String] [ClusterID=String][NodeID=String]: An available line could not be found in the indicated hunt list. Explanation   An available line could not be found in the indicated hunt list. This alarm is generated when all members' status is unavailable or busy or when the member is down (out of service), not registered, or busy. Recommended Action   Consider adding additional lines in the indicated hunt list. Check whether there are some outstanding calls on the line. Try to make a call directly to the members, bypassing the hunt list, to verify that there is no device or connectivity issue. If you cannot identify the cause through these steps, gather the CCM (SDI) trace and contact the Cisco Technical Assistance Center; TAC may be able to locate a cause code which may provide additional explanation for this alarm. Error Message %UC_CALLMANAGER-3-DeviceTypeMismatch: %[DBDeviceType=Enum][DeviceType=Enum] [DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Device type mismatch between the information contained in the device's TFTP configuration file and what is configured in Unified CM Administration for that device. Explanation   The device type indicated in the device's configuration file does not match the database configuration. This could indicate that a change was made in the database configuration that failed to 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 236/343