Error Message
CCM_CALLMANAGER-CALLMANAGER-2-CallManagerFailure : Indicates an internal failure in Unified CM Additional Text [String] Host Name of Hosting Node [String] Host Node IP Address [String] Reason code [Enum]
Explanation This alarm indicates that an internal failure occurred in the Cisco CallManager service. The service should restart in an attempt to clear the failure.
Recommended Action Monitor for other alarms and restart Cisco CallManager service, if necessary. Collect the core file if available, SDL and CCM/SDI trace files (you can gather these from Trace and Log Central in RTMT using the Collect Files feature) and contact the Cisco Technical Assistance Center (TAC).
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 1 |
Unknown - Unified CM has failed for an unknown reason |
| 2 |
HeartBeatStopped - An internal heart beat has stopped after the preceding heart beat interval |
| 3 |
RouterThreadDied - An internal thread has failed |
| 4 |
TimerThreadDied - An internal thread has failed |
| 5 |
CriticalThreadDied - An internal thread has failed |
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-SDLLinkISV : SDL link to remote application restored Remote Application IP Address [String] Unique Link ID [String] Local Node ID [UInt] Local Application ID [Enum]Remote Node ID [UInt] Remote Application ID [Enum]
Explanation This alarm indicates that the local Unified CM has gained communication with the remote Unified CM. Note that the remote Unified CM should also indicate SDLLinkISV with a different LinkID.
Recommended Action Informational only; no action is required
Reason Code - Enum Definitions
Enum Definitions - LocalApplicationId
| Value |
Definition |
| 100 |
CallManager |
Enum Definitions - RemoteApplicationId
| Value |
Definition |
| 100 |
CallManager |
Error Message
CCM_CALLMANAGER-CALLMANAGER-1-SDLLinkOOS : SDL link to remote application is out of service Remote Application IP Address [String] Unique Link ID [String] Local Node ID [UInt] Local Application ID [Enum]Remote Node ID [UInt] Remote Application ID [Enum]
Explanation This alarm indicates that the local Unified CM has lost communication with the remote Unified CM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).
Recommended Action In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated a CallManager failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.
Reason Code - Enum Definitions
Enum Definitions - LocalApplicationID
| Value |
Definition |
| 100 |
CallManager |
Enum Definitions - RemoteApplicationID
| Value |
Definition |
| 100 |
CallManager |
Error Message
CCM_CALLMANAGER-CALLMANAGER-1-CMVersionMismatch : One or more Unified CM nodes in a cluster are running different Unified CM versions Remote Application Link Protocol Version [String] Local Application Link Protocol Version [String] Remote Node ID [UInt] Remote Application ID [Enum]Remote Application Version [String]
Explanation This alarm indicates that the local Unified CM is unable to establish communication with the remote Unified CM due to a software version mismatch. This is generally a normal occurrence when you are upgrading a Unified CM node.
Recommended Action The alarm details include the versions of the local and remote Unified CM nodes. Compare the versions and upgrade a node if necessary.
Reason Code - Enum Definitions
Enum Definitions - RemoteAppId
| Value |
Definition |
| 100 |
CallManager |
| 200 |
CTIManager |
| 300 |
CMI |
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-BChannelOOS : The B-channel is out of service Unique Channel ID [String] Device Name [String] Reason [Enum]Channel ID [UInt]
Explanation The B-channel indicated by this alarm has gone out of service. Some of the more common reasons for a B-channel to go out of service include: Taking the channel out of service intentionally to perform maintenance on either the near-end or far-end; Losing T1/E1/BRI cable connectivity; When the MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Unified CM; When the MGCP gateway doesn't respond to an MGCP command sent by Unified CM three times; When a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway.
Recommended Action Check the Cisco CallManager advanced service parameter, Change B-channel Maintenance Status to determine if the B-channel has been taken out of service intentionally; Check the Q.931 trace for PRI SERVICE message to determine whether a PSTN provider has taken the B-channel out of service; Check the connection of the T1/E1/BRI cable; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 0 |
None Defined |
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-BChannelISV : B-channel is in service Channel ID [UInt] Unique Channel ID [String] Device Name [String]
Explanation The B-channel indicated by this alarm has gone in service
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-DChannelOOS : The D-channel is out of service Channel ID [UInt] Unique Channel ID [String] Device Name [String] Device IP Address [String] Reason [Enum]
Explanation The D-channel indicated by this alarm has gone out of service. Common reasons for a D-channel to go out of service include losing T1/E1/BRI cable connectivity; losing the gateway data link (Layer 2) due to an internal or external problem; or a gateway reset.
Recommended Action Check the connection of the T1/E1/BRI cable; reset the gateway to restore Layer 2 connectivity; investigate whether the gateway reset was intentional. If the reset was not intentional, take steps to restrict access to the Gateway Configuration window in Cisco Unified CM Administration and the gateway terminal.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 0 |
None Defined |
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-DChannelISV : D-channel is in service Channel ID [UInt] Unique Channel ID [String] Device Name [String] Device IP Address [String]
Explanation The indicated D-channel has gone in service
Recommended Action Notification purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-DeviceTransientConnection : A device attempted to register but did not complete registration Device IP Address [String] Device Name [String] Device MAC Address [String] Protocol [String] Device type [Enum]Reason Code [Enum]Connecting Port [UInt] Registering SIP User [String] IPv6Address [String] IPAddressAttributes [Enum]IPv6AddressAttributes [Enum]
Explanation A connection was established and immediately dropped before completing registration. Incomplete registration may indicate that a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. Network connectivity problems can affect device registration, or the restoration of a primary Unified CM may interrupt registration.
Recommended Action In the Cisco Unified Reporting tool, check the Active Services section of the Unified CM Cluster Overview report to confirm that any failover/fallback scenarios have completed. Confirm that auto-registration is enabled if the phone attempting to connect is set to auto-register, or locate the phone that is attempting to auto-register if auto-registration has been intentionally disabled. Check the device indicated in this alarm and confirm that the device registration details in Cisco Unified CM Administration are accurate. Also, refer to the reason code definitions in the alarm for recommended actions. No action is required if this event was issued as a result of a normal device rehome.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 10 |
CISCO_VGC_PHONE |
| 11 |
CISCO_VGC_VIRTUAL_PHONE |
| 30 |
ANALOG_ACCESS |
| 40 |
DIGITAL_ACCESS |
| 42 |
DIGITAL_ACCESS+ |
| 43 |
DIGITAL_ACCESS_WS-X6608 |
| 47 |
ANALOG_ACCESS_WS-X6624 |
| 48 |
VGC_GATEWAY |
| 50 |
CONFERENCE_BRIDGE |
| 51 |
CONFERENCE_BRIDGE_HARDWARE |
| 52 |
CONFERENCE_BRIDGE_HARDWARE_HDV2 |
| 53 |
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM |
| 62 |
H323_GATEWAY |
| 70 |
MUSIC_ON_HOLD |
| 71 |
DEVICE_PILOT |
| 73 |
CTI_ROUTE_POINT |
| 80 |
VOICE_MAIL_PORT |
| 83 |
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2 |
| 84 |
CISCO_MEDIA_SERVER |
| 85 |
CISCO_VIDEO_CONFERENCE_BRIDGE |
| 90 |
ROUTE_LIST |
| 100 |
LOAD_SIMULATOR |
| 110 |
MEDIA_TERMINATION_POINT |
| 111 |
MEDIA_TERMINATION_POINT_HARDWARE |
| 112 |
MEDIA_TERMINATION_POINT_HDV2 |
| 113 |
MEDIA_TERMINATION_POINT_WS-SVC-CMM |
| 120 |
MGCP_STATION |
| 121 |
MGCP_TRUNK |
| 122 |
GATEKEEPER |
| 124 |
7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 |
TRUNK |
| 126 |
TONE_ANNOUNCEMENT_PLAYER |
| 131 |
SIP_TRUNK |
| 132 |
SIP_GATEWAY |
| 133 |
WSM_TRUNK |
| 134 |
REMOTE_DESTINATION_PROFILE |
| 227 |
7915_12_BUTTON_LINE_EXPANSION_MODULE |
| 228 |
7915_24_BUTTON_LINE_EXPANSION_MODULE |
| 229 |
7916_12_BUTTON_LINE_EXPANSION_MODULE |
| 230 |
7916_24_BUTTON_LINE_EXPANSION_MODULE |
| 232 |
CKEM_36_BUTTON_LINE_EXPANSION_MODULE |
| 254 |
UNKNOWN_MGCP_GATEWAY |
| 255 |
UNKNOWN |
| 30027 |
ANALOG_PHONE |
| 30028 |
ISDN_BRI_PHONE |
| 30032 |
SCCP_GATEWAY_VIRTUAL_PHONE |
Enum Definitions - Reason
| Value |
Definition |
| 1 |
Unknown - (SCCP only) The device failed to register for an unknown reason. If this persists, collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact TAC. |
| 2 |
NoEntryInDatabase - (MGCP only) The device is not configured in the Unified CM Administration database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Unified CM Administration. |
| 3 |
DatabaseConfigurationError - The device is not configured in the Unified CM Administration database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Unified CM Administration. |
| 4 |
DeviceNameUnresolveable - For SIP third-party devices this means that Unified CM could not determine the name of the device from the Authorization header in the REGISTER message. The device did not provide an Authorization header after Unified CM challenged with a 401 Unauthorized message. Verify that the device is configured with digest credentials and is able to respond to 401 challenges with an Authorization header. If this is a Cisco IP phone, the configuration may be out-of-sync. First, go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify "all servers have a good replication status". If DB replications looks good, reset the phone. If that still doesn't fix the problem, restart the TFTP and the Cisco CallManager services. For all other devices, this reason code means that DNS lookup failed. Verify the DNS server configured via the OS Administration CLI is correct and that the DNS name used by the device is configured in the DNS server. |
| 6 |
ConnectivityError - The network connection between the device and Unified CM dropped before the device was fully registered. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). |
| 7 |
InitializationError - An internal error occurred within Unified CM while processing the device registration. Cisco recommends that you restart the Cisco CallManager service. If this issue occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Cisco Technical Assistance Center (TAC). |
| 10 |
AuthenticationError - The device failed either TLS or SIP digest security authentication. If the device is a SIP phone and is enabled for digest authentication (on the System > Security Profile > Phone Security Profile, check if "Enable Digest Authentication" checkbox is checked), verify that the information in the Digest Credentials field on the End User Configuration page is configured. Also, check the Phone Configuration page to determine whether the phone is associated with the specified end user in the Digest User drop box. If the device is a third-party SIP device, verify that the digest credentials configured on the phone match the Digest Credentials configured in the End User Configuration page. |
| 11 |
InvalidX509NameInCertificate - Configured "X.509 Subject Name" doesn't match the information in the certificate from the device. Check the Security profile of the indicated device and verify that the Device Security Mode is set to either Authenticated or Encrypted. Verify that the X.509 Subject Name field has the appropriate content; it should match the Subject Name in the certificate from the peer. |
| 12 |
InvalidTLSCipher - Unsupported cipher algorithm used by the device; Unified CM only supports AES_128_SHA cipher algorithm. Recommended action is for the device to regenerate its certificate with the AES_128_SHA cipher algorithm. |
| 14 |
MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, or an expires value that is too small. Check the REGISTER message for any of these issues and if you find one, correct the issue. |
| 15 |
ProtocolMismatch - The protocol of the device (SIP or SCCP) does not match the configured protocol in Unified CM. Recommended actions: 1) Verify that the device is configured with the appropriate protocol; 2) Verify that the firmware load ID on the Device Defaults page in Cisco Unified CM Administration is correct and actually exists on the TFTP server; 3) If there is a firmware load ID configured on the Device Configuration page, verify that it is correct and that it exists on the TFTP server (on Cisco Unified OS Administration page, access Software Upgrades > TFTP File Management, then look for the file name as specified by load ID); 4) Restart the TFTP and Cisco CallManager services. Use the Cisco Unified OS Administration TFTP File Management page to verify that the configured firmware loads exist. |
| 16 |
DeviceNotActive - The device has not been activated |
| 17 |
AuthenticatedDeviceAlreadyExists - A device with the same name is already registered. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Cisco Technical Assistance Center (TAC). There may be an attempt by unauthorized devices to register. |
| 18 |
ObsoleteProtocolVersion - (SCCP only) A SCCP device registered with an obsolete protocol version. Power-cycle the phone. Verify that the TFTP service is activated. Verify that the TFTP server is reachable from the device. If there is a firmware load ID configured on the Phone Configuration page, verify that the firmware load ID exists on the TFTP server (on Cisco Unified OS Administration page, access Software Upgrades > TFTP File Management, then look for the file name as specified by load ID). |
| 23 |
DatabaseTimeout - Unified CM requested device configuration data from the database but did not receive a response within 10 minutes. |
| 25 |
RegistrationSequenceError - (SCCP only) A device requested configuration information from Unified CM at an unexpected time and Unified CM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC). |
| 26 |
InvalidCapabilities - (SCCP only) Unified CM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC). |
| 27 |
CapabilityResponseTimeout - (SCCP only) Unified CM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that network connectivity exists between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). |
| 28 |
SecurityMismatch - Unified CM detected a mismatch in the security settings of the device and/or Unified CM. This alarm can occur due to any of the following situations: The device established a secure connection yet reported that it does not have the ability to do authenticated signaling; the device did not establish a secure connection but the security mode configured for the device indicates that it should have done so; or the device established a secure connection but the security mode configured for the device indicates that it should not have done so. To correct the error, ensure that the security settings of the device and Unified CM are correct for your deployment. Resetting the device may help because it forces the device to download its latest settings. If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone and view the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate. |
| 29 |
AutoRegisterDBError - Auto-registration of a device failed because auto-registration is not allowed for the device type or because an error occurred while adding the auto-registering device to the database (stored procedure). Note that if Unified CM is in mixed mode (System > Enterprise Parameters > Cluster Security Mode = 1), auto-registration is not allowed and the device must be configured manually. If you are not planning to auto-register phones, either manually configure the phone (Device > Phone > Add New), power the device down, or remove it from the network. If you are attempting to auto-register this phone, verify that the cluster is not in mixed mode (System > Enterprise Parameters > Cluster Security Mode = 1) and verify that auto-registration is enabled on the node to which this device is registering (System > Cisco Unified CM > ensure that the Auto-registration Disabled... checkbox is not checked). |
| 30 |
DBAccessError - Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. View the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate. When database replication is Good on all nodes, restart the Cisco CallManager service on the node to which the device is attempting to register. If the problem persists, collect SDI and SDL traces for the Cisco Database layer Monitor service and contact the Cisco Technical Assistance Center (TAC). |
| 31 |
AutoRegisterDBConfigTimeout - (SCCP only) Unified CM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. Check for high CPU utilization on this Unified CM node because congestion could be a cause of this alarm. If this alarm continues to occur, restart the Cisco CallManager service. If the problem persists, contact the Cisco Technical Assistance Center (TAC). |
| 32 |
DeviceTypeMismatch - The device type reported by the device does not match the device type configured on Unified CM. Verify that the Product Type on the Phone Configuration page in Unified CM Administration matches the model number of the phone. If it does not match, delete the phone and add a new one with the correct Product Type. If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone, and view the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database repliction: utils dbreplication runtimestate. |
| 33 |
AddressingModeMismatch - (SCCP only) Unified CM detected an error related to the addressing mode configured for the device. One of the following errors was detected: 1) The device is configured to use only IPv4 addressing, but did not specify an IPv4 address; or 2) The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. Reset the device to resolve the problem. If the problem persists, restart the Cisco CallManager service. |
Enum Definitions - IPAddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv4 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv4 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling |
Enum Definitions - IPV6AddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv6 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv6 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-EndPointTransientConnection : An endpoint attempted to register but did not complete registration Device IP address [String] Device name [String] Device MAC address [String] Protocol [String] Device type [Enum]Reason Code [Enum]Connecting Port [UInt] Registering SIP User [String] IPv6Address [String] IPAddressAttributes [Enum]IPv6AddressAttributes [Enum]LastSignalReceived [String] StationState [String]
Explanation A connection was established and immediately dropped before completing registration. Incomplete registration may indicate that a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. Network connectivity problems can affect device registration, or the restoration of a primary Unified CM may interrupt registration.
Recommended Action Investigate any network connectivity problems in the system. It's possible that you have reached the maximum number of devices; the Cisco CallManager service parameter, Maximum Number of Registered Devices, controls the number of devices allowed in the system. After taking licensing, system hardware and other related concerns into consideration, you could increase the value of the service parameter. Also, refer to the reason code definitions in the alarm for additional recommended actions. No action is required if this event was issued as a result of a normal device rehome.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 61 |
H323_PHONE |
| 72 |
CTI_PORT |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30035 |
IP_STE |
Enum Definitions - Reason
| Value |
Definition |
| 1 |
Unknown - (SCCP only) The device failed to register for an unknown reason. If this persists, collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact the Cisco Technical Assistance Center (TAC). |
| 2 |
NoEntryInDatabase - (MGCP only) The device is not configured in the Unified CM database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Cisco Unified CM Administration. |
| 3 |
DatabaseConfigurationError - The device is not configured in the Unified CM database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Cisco Unified CM Administration. |
| 4 |
DeviceNameUnresolveable - For SIP third-party devices this means that Unified CM could not determine the name of the device from the Authorization header in the REGISTER message. The device did not provide an Authorization header after Unified CM challenged with a 401 Unauthorized message. Verify that the device is configured with digest credentials and is able to respond to 401 challenges with an Authorization header. If this is a Cisco IP phone, the configuration may be out-of-sync. First go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify that "all servers have a good replication status." If DB replication looks good, reset the phone. If resetting the phone doesn't fix the issue, restart TFTP and Cisco CallManager services. For all other devices, this reason code means that DNS lookup failed. Verify that the DNS server configured via the OS Administration CLI is correct and that the DNS name used by the device is configured in the DNS server. |
| 6 |
ConnectivityError - The network connection between the device and Unified CM dropped before the device was fully registered. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify network connectivity between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). |
| 7 |
InitializationError - An internal error occurred within Unified CM while processing the device registration. Cisco recommends that you restart the Cisco CallManager service. If this issue occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Cisco Technical Assistance Center (TAC). |
| 10 |
AuthenticationError - The device failed either TLS or SIP digest security authentication. If the device is a SIP phone and is enabled for digest authentication (System > Security Profile > Phone Security Profile, check whether the Enable Digest Authentication checkbox is checked), verify that the Digest Credentials field in the End User Configuration page is configured. Also, check the Phone Configuration page to determine whether the phone is associated with the specified end user in the Digest User drop-down list box. If the device is a third-party SIP device, verify that the digest credentials configured on the phone match the Digest Credentials configured in the End User Configuration page in Unified CM Administration. |
| 11 |
InvalidX509NameInCertificate - The configured X.509 Subject Name doesn't match the information in the certificate from the device. Check the Security profile of the indicated device and verify that the Device Security Mode is set to either Authenticated or Encrypted. Verify that the X.509 Subject Name field has the appropriate information. It should match the Subject Name in the certificate from the peer. |
| 12 |
InvalidTLSCipher - An unsupported cipher algorithm was used by the device; Unified CM only supports AES_128_SHA cipher algorithm. Recommended action is for the device to regenerate its certificate with the AES_128_SHA cipher algorithm. |
| 14 |
MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, or an expires value that is too small. Check the REGISTER message for any of these issues and if you find one, correct the issue. |
| 15 |
ProtocolMismatch - The protocol of the device (SIP or SCCP) does not match the configured protocol in Unified CM. Recommended actions: 1) Verify that the device is configured with the desired protocol; 2) Verify that the firmware load ID on the Device Defaults page in Unified CM Administration is correct and actually exists on the TFTP server; 3) If there is a firmware load ID configured on the device page, verify that it is correct and exists on the TFTP server (on the Cisco Unified OS Administration page, access Software Upgrades > TFTP File Management, then look for the file name as specified by load ID); 4) Restart the TFTP and Cisco CallManager services. Use the Cisco Unified OS Administration TFTP File Management page to verify that the configured firmware loads exist. |
| 16 |
DeviceNotActive - The device has not been activated |
| 17 |
AuthenticatedDeviceAlreadyExists - A device with the same name is already registered. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Cisco Technical Assistance Center (TAC). There may be an attempt by unauthorized devices to register. |
| 18 |
ObsoleteProtocolVersion - (SCCP only) A SCCP device registered with an obsolete protocol version. Power-cycle the phone. Verify that the TFTP service is activated. Verify that the TFTP server is reachable from the device. If there is a firmware load ID configured on the Phone Configuration page, verify that the firmware load ID exists on the TFTP server (on the Cisco Unified OS Administration page, access Software Upgrades > TFTP File Management, then look for the file name as specified by load ID). |
| 19 |
DigestAuthChallenge - (SIP only) A SIP device configured for digest authentication attempted to register with invalid credentials. Unified CM has responded with a challenge (401) to request new credentials. |
| 20 |
DigestAuthChallengeForID - (SIP only) A SIP device attempted to register without a device name or MAC address. Unified CM responded with a challenge (401) which requests the device to resend the REGISTER message and include an Authorization header containing a user ID. Unified CM will use this user ID to attempt to find the device in the configuration database. |
| 21 |
DigestChallengeTimeout - (SIP only) A SIP device requiring digest authentication sent a REGISTER message and Unified CM responded with a challenge (401) to request the authorization credentials. The device did not resend the REGISTER within the 30-second timeout interval. |
| 22 |
ExpiresTimeTooSmall - (SIP only) A SIP device attempted to register with an Expires value smaller than the configured SIP Station Keepalive Interval value in the Call Manager Service Parameters. Unified CM responded with 423 Interval Too Brief and the device should re-register with the correct Expires value. |
| 23 |
DatabaseTimeout - Unified CM requested device configuration data from the database but did not receive a response in time (within 15 seconds for SIP devices, or within 10 minutes for SCCP devices). |
| 24 |
UniqueDeviceForUserNotFound - (SIP only) A 3rd-party device attempted to register but there is more than 1 device associated with the same Digest User. Third-party devices must be configured with a unique Digest User. |
| 25 |
RegistrationSequenceError - (SCCP only) A device requested configuration information from Unified CM at an unexpected time and Unified CM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC). |
| 26 |
InvalidCapabilities - (SCCP only) Unified CM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC). |
| 27 |
CapabilityResponseTimeout - (SCCP only) Unified CM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that network connectivity exists between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). |
| 28 |
SecurityMismatch - Unified CM detected a mismatch in the security settings of the device and/or Unified CM. This alarm can occur due to any of the following situations: The device established a secure connection yet reported that it does not have the ability to do authenticated signaling; the device did not establish a secure connection but the security mode configured for the device indicates that it should have done so; or the device established a secure connection but the security mode configured for the device indicates that it should not have done so. To correct the error, ensure that the security settings of the device and Unified CM are correct for your deployment. Resetting the device may help because it forces the device to download its latest settings. If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone and view the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate. If the device is a third-party SIP phone, verify that the configuration on the phone is set to UDP or TCP only; Unified CM does not support TLS on third-party phones. Because each third-party phone model has unique configuration interfaces, please refer to the configuration guide for your phone to learn where the third-party phone defines the UDP/TCP setting. |
| 29 |
AutoRegisterDBError - Auto-registration of a device failed because auto-registration is not allowed for the device type or because an error occurred while adding the auto-registering device to the database (stored procedure). Note that if Unified CM is in mixed mode (System > Enterprise Parameters > Cluster Security Mode = 1), auto-registration is not allowed and the device must be configured manually. If you are not planning to auto-register phones, either manually configure the phone (Device > Phone > Add New), power the device down, or remove it from the network. If you are attempting to auto-register this phone, verify that the cluster is not in mixed mode (System > Enterprise Parameters > Cluster Security Mode = 1) and verify that auto-registration is enabled on the node to which this device is registering (System > Cisco Unified CM > ensure that the Auto-registration Disabled... checkbox is not checked). |
| 30 |
DBAccessError - Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. View the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate. When database replication is Good on all nodes, restart the Cisco CallManager service on the node to which the device is attempting to register. If the problem persists, collect SDI and SDL traces for the Cisco Database layer Monitor service and contact the Cisco Technical Assistance Center (TAC). |
| 31 |
AutoRegisterDBConfigTimeout - (SCCP only) Unified CM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. Check for high CPU utilization on this Unified CM node because congestion could be a cause of this alarm. If this alarm continues to occur, restart the Cisco CallManager service. If the problem persists, contact the Cisco Technical Assistance Center (TAC). |
| 32 |
DeviceTypeMismatch - The device type reported by the device does not match the device type configured on Unified CM. Verify that the Product Type on the Phone Configuration page in Unified CM Administration matches the model number of the phone. If it does not match, delete the phone and add a new one with the correct Product Type. If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone, and view the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database repliction: utils dbreplication runtimestate. |
| 33 |
AddressingModeMismatch - (SCCP only) Unified CM detected an error related to the addressing mode configured for the device. One of the following errors was detected: 1) The device is configured to use only IPv4 addressing, but did not specify an IPv4 address; or 2) The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. Reset the device to resolve the problem. If the problem persists, restart the Cisco CallManager service. |
Enum Definitions - IPAddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv4 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv4 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling |
Enum Definitions - IPV6AddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv6 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv6 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DeviceRegistered : Device registered Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device description [String] User ID [String] Load ID [String] Associated directory numbers [String] Performance monitor object [Enum]Device type [Enum]Configured Gatekeeper Name [String] Technology Prefix Name [String] Zone Information [String] Alternate Gatekeeper List [String] Active Gatekeeper [String] Call Signal Address [String] RAS Address [String] IPV6Address [String] IPAddressAttributes [Enum]IPV6AddressAttributes [Enum]ActiveLoadId [String] InactiveLoadId [String]
Explanation A device successfully registered with Cisco Unified Communications Manager
Recommended Action Informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - PerfMonObjType
| Value |
Definition |
| 1 |
Cisco CallManager |
| 2 |
Cisco Phones |
| 3 |
Cisco Lines |
| 4 |
Cisco H323 |
| 5 |
Cisco MGCP Gateway |
| 6 |
Cisco MOH Device |
| 7 |
Cisco Analog Access |
| 8 |
Cisco MGCP FXS Device |
| 9 |
Cisco MGCP FXO Device |
| 10 |
Cisco MGCP T1CAS Device |
| 11 |
Cisco MGCP PRI Device |
| 12 |
Cisco MGCP BRI Device |
| 13 |
Cisco MTP Device |
| 14 |
Cisco Transcode Device |
| 15 |
Cisco SW Conference Bridge Device |
| 16 |
Cisco HW Conference Bridge Device |
| 17 |
Cisco Locations |
| 18 |
Cisco Gatekeeper |
| 19 |
Cisco CallManager System Performance |
| 20 |
Cisco Video Conference Bridge Device |
| 21 |
Cisco Hunt Lists |
| 22 |
Cisco SIP |
| 23 |
Cisco Annunciator Device |
| 24 |
Cisco QSIG Features |
| 25 |
Cisco SIP Stack |
| 26 |
Cisco Presence Features |
| 27 |
Cisco WSMConnector |
| 28 |
Cisco Dual-Mode Mobility |
| 29 |
Cisco SIP Station |
| 30 |
Cisco Mobility Manager |
| 31 |
Cisco Signaling |
| 32 |
Cisco Call Restriction |
| 33 |
External Call Control |
| 34 |
Cisco SAF Client |
| 35 |
IME Client |
| 36 |
IME Client Instance |
Enum Definitions - DeviceType
| Value |
Definition |
| 10 |
CISCO_VGC_PHONE |
| 11 |
CISCO_VGC_VIRTUAL_PHONE |
| 30 |
ANALOG_ACCESS |
| 40 |
DIGITAL_ACCESS |
| 42 |
DIGITAL_ACCESS+ |
| 43 |
DIGITAL_ACCESS_WS-X6608 |
| 47 |
ANALOG_ACCESS_WS-X6624 |
| 48 |
VGC_GATEWAY |
| 50 |
CONFERENCE_BRIDGE |
| 51 |
CONFERENCE_BRIDGE_HARDWARE |
| 52 |
CONFERENCE_BRIDGE_HARDWARE_HDV2 |
| 53 |
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM |
| 62 |
H323_GATEWAY |
| 70 |
MUSIC_ON_HOLD |
| 71 |
DEVICE_PILOT |
| 73 |
CTI_ROUTE_POINT |
| 80 |
VOICE_MAIL_PORT |
| 83 |
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2 |
| 84 |
CISCO_MEDIA_SERVER |
| 85 |
CISCO_VIDEO_CONFERENCE_BRIDGE |
| 90 |
ROUTE_LIST |
| 100 |
LOAD_SIMULATOR |
| 110 |
MEDIA_TERMINATION_POINT |
| 111 |
MEDIA_TERMINATION_POINT_HARDWARE |
| 112 |
MEDIA_TERMINATION_POINT_HDV2 |
| 113 |
MEDIA_TERMINATION_POINT_WS-SVC-CMM |
| 120 |
MGCP_STATION |
| 121 |
MGCP_TRUNK |
| 122 |
GATEKEEPER |
| 124 |
7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 |
TRUNK |
| 126 |
TONE_ANNOUNCEMENT_PLAYER |
| 131 |
SIP_TRUNK |
| 132 |
SIP_GATEWAY |
| 133 |
WSM_TRUNK |
| 134 |
REMOTE_DESTINATION_PROFILE |
| 227 |
7915_12_BUTTON_LINE_EXPANSION_MODULE |
| 228 |
7915_24_BUTTON_LINE_EXPANSION_MODULE |
| 229 |
7916_12_BUTTON_LINE_EXPANSION_MODULE |
| 230 |
7916_24_BUTTON_LINE_EXPANSION_MODULE |
| 232 |
CKEM_36_BUTTON_LINE_EXPANSION_MODULE |
| 254 |
UNKNOWN_MGCP_GATEWAY |
| 255 |
UNKNOWN |
| 30027 |
ANALOG_PHONE |
| 30028 |
ISDN_BRI_PHONE |
| 30032 |
SCCP_GATEWAY_VIRTUAL_PHONE |
Enum Definitions - IPAddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv4 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv4 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling |
Enum Definitions - IPV6AddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv6 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv6 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-EndPointRegistered : Endpoint registered Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device description [String] User ID [String] Load ID [String] Associated directory numbers [String] Performance monitor object [Enum]Device type [Enum]IPV6Address [String] IPAddressAttributes [Enum]IPV6AddressAttributes [Enum]ActiveLoadId [String] InactiveLoadId [String]
Explanation An endpoint successfully registered with Cisco Unified Communications Manager
Recommended Action Notification purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - PerfMonObjType
| Value |
Definition |
| 2 |
Cisco Phone |
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 61 |
H323_PHONE |
| 72 |
CTI_PORT |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30035 |
IP_STE |
Enum Definitions - IPAddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv4 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv4 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling |
Enum Definitions - IPV6AddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv6 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv6 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-DevicePartiallyRegistered : A device has partially registered Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device description [String] User ID [String] Load ID [String] Associated directory numbers [String] Performance monitor object [Enum]Device type [Enum]ActiveLoadId [String] InactiveLoadId [String]
Explanation A device is partially registered with Cisco Unified Communications Manager. Some, but not all, of the lines configured on the device have successfully registered.
Recommended Action In the Cisco Unified Reporting tool, run the Unified CM Multi-Line Devices report and check the number of lines that are supposed to be configured on the device identified in this alarm. If the device has registered an inconsistent number of lines compared the Multi-Line report for this device, restart the device so that it can reregister all lines. If this alarm persists, verify that the appropriate number of lines has been configured on the device, and that the appropriate directory numbers have been configured. If the device is a third-party SIP phone, verify that the directory numbers configured on the phone match the directory numbers configured on the device in Unified CM Administration.
Reason Code - Enum Definitions
Enum Definitions - PerfMonObjType
| Value |
Definition |
| 1 |
Cisco CallManager |
| 2 |
Cisco Phones |
| 3 |
Cisco Lines |
| 4 |
Cisco H323 |
| 5 |
Cisco MGCP Gateway |
| 6 |
Cisco MOH Device |
| 7 |
Cisco Analog Access |
| 8 |
Cisco MGCP FXS Device |
| 9 |
Cisco MGCP FXO Device |
| 10 |
Cisco MGCP T1CAS Device |
| 11 |
Cisco MGCP PRI Device |
| 12 |
Cisco MGCP BRI Device |
| 13 |
Cisco MTP Device |
| 14 |
Cisco Transcode Device |
| 15 |
Cisco SW Conference Bridge Device |
| 16 |
Cisco HW Conference Bridge Device |
| 17 |
Cisco Locations |
| 18 |
Cisco Gatekeeper |
| 19 |
Cisco CallManager System Performance |
| 20 |
Cisco Video Conference Bridge Device |
| 21 |
Cisco Hunt Lists |
| 22 |
Cisco SIP |
| 23 |
Cisco Annunciator Device |
| 24 |
Cisco QSIG Features |
| 25 |
Cisco SIP Stack |
| 26 |
Cisco Presence Features |
| 27 |
Cisco WSMConnector |
| 28 |
Cisco Dual-Mode Mobility |
| 29 |
Cisco SIP Station |
| 30 |
Cisco Mobility Manager |
| 31 |
Cisco Signaling |
| 32 |
Cisco Call Restriction |
| 33 |
External Call Control |
| 34 |
Cisco SAF Client |
| 35 |
IME Client |
| 36 |
IME Client Instance |
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 10 |
CISCO_VGC_PHONE |
| 11 |
CISCO_VGC_VIRTUAL_PHONE |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 30 |
ANALOG_ACCESS |
| 40 |
DIGITAL_ACCESS |
| 42 |
DIGITAL_ACCESS+ |
| 43 |
DIGITAL_ACCESS_WS-X6608 |
| 47 |
ANALOG_ACCESS_WS-X6624 |
| 48 |
VGC_GATEWAY |
| 50 |
CONFERENCE_BRIDGE |
| 51 |
CONFERENCE_BRIDGE_HARDWARE |
| 52 |
CONFERENCE_BRIDGE_HARDWARE_HDV2 |
| 53 |
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM |
| 61 |
H323_PHONE |
| 62 |
H323_GATEWAY |
| 70 |
MUSIC_ON_HOLD |
| 71 |
DEVICE_PILOT |
| 72 |
CTI_PORT |
| 73 |
CTI_ROUTE_POINT |
| 80 |
VOICE_MAIL_PORT |
| 83 |
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2 |
| 84 |
CISCO_MEDIA_SERVER |
| 85 |
CISCO_VIDEO_CONFERENCE_BRIDGE |
| 90 |
ROUTE_LIST |
| 100 |
LOAD_SIMULATOR |
| 110 |
MEDIA_TERMINATION_POINT |
| 111 |
MEDIA_TERMINATION_POINT_HARDWARE |
| 112 |
MEDIA_TERMINATION_POINT_HDV2 |
| 113 |
MEDIA_TERMINATION_POINT_WS-SVC-CMM |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 120 |
MGCP_STATION |
| 121 |
MGCP_TRUNK |
| 122 |
GATEKEEPER |
| 124 |
7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 |
TRUNK |
| 126 |
TONE_ANNOUNCEMENT_PLAYER |
| 131 |
SIP_TRUNK |
| 132 |
SIP_GATEWAY |
| 133 |
WSM_TRUNK |
| 134 |
REMOTE_DESTINATION_PROFILE |
| 227 |
7915_12_BUTTON_LINE_EXPANSION_MODULE |
| 228 |
7915_24_BUTTON_LINE_EXPANSION_MODULE |
| 229 |
7916_12_BUTTON_LINE_EXPANSION_MODULE |
| 230 |
7916_24_BUTTON_LINE_EXPANSION_MODULE |
| 232 |
CKEM_36_BUTTON_LINE_EXPANSION_MODULE |
| 254 |
UNKNOWN_MGCP_GATEWAY |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30027 |
ANALOG_PHONE |
| 30028 |
ISDN_BRI_PHONE |
| 30032 |
SCCP_GATEWAY_VIRTUAL_PHONE |
| 30035 |
IP_STE |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-DeviceUnregistered : Device unregistered Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device type [Enum]Device description [String] Reason Code [Enum]IPV6Address [String] IPAddressAttributes [Enum]IPV6AddressAttributes [Enum]
Explanation A device that has previously registered with Unified CM has unregistered. In cases of normal unregistration with reason code 'CallManagerReset', 'CallManagerRestart', or 'DeviceInitiatedReset', the severity of this alarm is lowered to INFORMATIONAL. A device can unregister for many reasons, both intentional such as manually resetting the device after a configuration change, and unintentional such as loss of network connectivity. Other causes for this alarm could include a phone being registered to a secondary node and then the primary node coming online, which causes the phone to rehome to the primary Unified CM node. Or, lack of a KeepAlive being returned from the Unified CM node to which this device was registered. Unregistration also occurs if Unified CM receives a duplicate registration request for this same device.
Recommended Action Actions to take vary depending on the reason specified in this alarm for the device unregistration. If the reason is ConfigurationMismatch, go to the Device Configuration page in Cisco Unified CM Administration, make a change to the Description field for this device, click Save, then reset the device. In the case of a network connectivity problem or loss of KeepAlives, use network diagnostic tools and the Cisco Unified CM Reporting tool to fix any reported network or Unified CM system errors. In the case of a device rehoming to the primary Unified CM node, watch for a successful registration of the device on the primary node. In the case of a duplicate registration request, it may be a non-malicious occurrence due to timing of a device registering and unregistering; if duplicate registration requests continue or if the same device has different IP addresses, confirm the IP address on the physical device itself by checking the settings on the device (settings button). If unregistration of this device was expected, no action is required. Also, refer to the reason code descriptions for recommended actions.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 10 |
CISCO_VGC_PHONE |
| 11 |
CISCO_VGC_VIRTUAL_PHONE |
| 30 |
ANALOG_ACCESS |
| 40 |
DIGITAL_ACCESS |
| 42 |
DIGITAL_ACCESS+ |
| 43 |
DIGITAL_ACCESS_WS-X6608 |
| 47 |
ANALOG_ACCESS_WS-X6624 |
| 48 |
VGC_GATEWAY |
| 50 |
CONFERENCE_BRIDGE |
| 51 |
CONFERENCE_BRIDGE_HARDWARE |
| 52 |
CONFERENCE_BRIDGE_HARDWARE_HDV2 |
| 53 |
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM |
| 62 |
H323_GATEWAY |
| 70 |
MUSIC_ON_HOLD |
| 71 |
DEVICE_PILOT |
| 73 |
CTI_ROUTE_POINT |
| 80 |
VOICE_MAIL_PORT |
| 83 |
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2 |
| 84 |
CISCO_MEDIA_SERVER |
| 85 |
CISCO_VIDEO_CONFERENCE_BRIDGE |
| 90 |
ROUTE_LIST |
| 100 |
LOAD_SIMULATOR |
| 110 |
MEDIA_TERMINATION_POINT |
| 111 |
MEDIA_TERMINATION_POINT_HARDWARE |
| 112 |
MEDIA_TERMINATION_POINT_HDV2 |
| 113 |
MEDIA_TERMINATION_POINT_WS-SVC-CMM |
| 120 |
MGCP_STATION |
| 121 |
MGCP_TRUNK |
| 122 |
GATEKEEPER |
| 124 |
7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 |
TRUNK |
| 126 |
TONE_ANNOUNCEMENT_PLAYER |
| 131 |
SIP_TRUNK |
| 132 |
SIP_GATEWAY |
| 133 |
WSM_TRUNK |
| 134 |
REMOTE_DESTINATION_PROFILE |
| 227 |
7915_12_BUTTON_LINE_EXPANSION_MODULE |
| 228 |
7915_24_BUTTON_LINE_EXPANSION_MODULE |
| 229 |
7916_12_BUTTON_LINE_EXPANSION_MODULE |
| 230 |
7916_24_BUTTON_LINE_EXPANSION_MODULE |
| 232 |
CKEM_36_BUTTON_LINE_EXPANSION_MODULE |
| 254 |
UNKNOWN_MGCP_GATEWAY |
| 255 |
UNKNOWN |
| 30027 |
ANALOG_PHONE |
| 30028 |
ISDN_BRI_PHONE |
| 30032 |
SCCP_GATEWAY_VIRTUAL_PHONE |
Enum Definitions - Reason
| Value |
Definition |
| 1 |
Unknown - The device has unregistered for an unknown reason. If the device does not re-register within 5 minutes, verify that it is powered up and verify that there is network connectivity between the device and Unified CM. |
| 6 |
ConnectivityError - Network communication between the device and Unified CM has been interrupted. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). |
| 8 |
DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action required; the device will re-register automatically. |
| 9 |
CallManagerReset - A device reset was initiated from Cisco Unified CM Administration, either due to an explicit command from an administrator, or due to internal errors encountered. No action necessary; the device will re-register automatically. |
| 10 |
DeviceUnregistered - The device has explicitly unregistered. Possible causes include a change in the IP address or port of the device. No action is necessary; the device will re-register automatically. |
| 11 |
MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, or an expires value that is too small. Check the REGISTER message for any of these issues and if you find one, correct the issue. |
| 12 |
SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. |
| 13 |
KeepAliveTimeout - A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). |
| 14 |
ConfigurationMismatch (SIP only) The configuration on the device does not match the configuration in Unified CM. This can be caused by database replication errors or other internal Unified CM communication errors. Go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report and verify "all servers have a good replication status". You can also go to the Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. If this device continues to unregister with this reason code, go to the Device Configuration page in Unified CM Administration for the device indicated in this alarm and click Save. This generates a change notify message to the Cisco CallManager and TFTP services and rebuilds a new configuration file for the device. If the problem still persists, restart the TFTP service and the Cisco CallManager service. |
| 15 |
CallManagerRestart - A device restart was initiated from Unified CM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. No action is necessary; the device will re-register automatically. |
| 16 |
DuplicateRegistration - Unified CM detected that the device attempted to register to two nodes at the same time. Unified CM initiated a restart to the phone to force it to re-home to a single node. No action is necessary; the device will re-register automatically. |
| 17 |
CallManagerApplyConfig - An ApplyConfig action was performed in Unified CM Administration resulting in an unregistration. No action is necessary; the device will re-register automatically. |
| 18 |
DeviceNoResponse - The device did not respond to a reset or restart notification, so it is being forcefully reset. If the device does not re-register within 5 minutes, confirm that it is powered up and confirm that there is network connectivity between the device and Unified CM. |
| 19 |
EMLoginLogout - The device has been unregistered due to an Extension Mobility login or logout |
| 20 |
EMCCLoginLogout - The device has been unregistered due to an Extension Mobility Cross Cluster login or logout |
| 25 |
RegistrationSequenceError - (SCCP only) A device requested configuration information from Unified CM at an unexpected time and Unified CM no longer had the requested information in memory. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC). |
| 26 |
InvalidCapabilities - (SCCP only) Unified CM detected an error in the updated media capabilities reported in one of the StationUpdateCapabilities messages sent by the device. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC). |
| 28 |
FallbackInitiated - The device has initiated a fallback and will automatically re-register to a higher-priority Unified CM. No action is necessary. |
Enum Definitions - IPAddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv4 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv4 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling |
Enum Definitions - IPV6AddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv6 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv6 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-EndPointUnregistered : An endpoint has unregistered Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device type [Enum]Device description [String] Reason Code [Enum]IPV6Address [String] IPAddressAttributes [Enum]IPV6AddressAttributes [Enum]LastSignalReceived [String] CallState [String]
Explanation An endpoint that has previously registered with Cisco Unified Communications Manager has unregistered. In cases of normal unregistration with reason code 'CallManagerReset', 'CallManagerRestart', 'DeviceInitiatedReset', 'EMLoginLogout', or 'EMCCLoginLogout', the severity of this alarm is lowered to INFORMATIONAL. An endpoint can unregister for many reasons, both intentional such as manually resetting the device after a configuration change, or unintentional such as loss of network connectivity. Other causes for this alarm could include a phone being registered to a secondary node and then the primary node coming online, causing the phone to rehome to the primary Unified CM node. Or, lack of a KeepAlive message being returned from the Unified CM node to which this endpoint was registered. Unregistration also occurs if Unified CM receives a duplicate registration request for this same device.
Recommended Action Actions to take vary depending on the reason specified for the endpoint unregistration. If the reason is ConfigurationMismatch, go to the Device Configuration page in Cisco Unified CM Administration, make a change to the Description field for this device, click Save, then reset the device. In the case of a network connectivity problem or loss of KeepAlives, use network diagnostic tools and the Cisco Unified CM Reporting tool to fix any reported network or Unified CM system errors. In the case of an endpoint rehoming to the primary Unified CM node, watch for a successful registration of the device on the primary node. In the case of a duplicate registration request, it may be a non-malicious occurrence due to timing of an endpoint registering and unregistering; if duplicate registration requests continue or if the same endpoint has different IP addresses, confirm the IP address on the physical device itself by checking the settings on the device (settings button). If unregistration of this device was expected, no action is required. Also, refer to the reason code descriptions in this alarm for additional recommended actions.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 61 |
H323_PHONE |
| 72 |
CTI_PORT |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30035 |
IP_STE |
Enum Definitions - Reason
| Value |
Definition |
| 1 |
Unknown - The device has unregistered for an unknown reason. If the device does not re-register within 5 minutes, verify that it is powered up and verify that network connectivity exists between the device and Unified CM. |
| 6 |
ConnectivityError - Network communication between the device and Unified CM has been interrupted. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that network connectivity exists between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). |
| 8 |
DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action is required; the device will re-register automatically. |
| 9 |
CallManagerReset - A device was reset from Cisco Unified CM Administration, either due to an explicit command from an administrator, or due to internal errors encountered. No action is necessary; the device will re-register automatically. |
| 10 |
DeviceUnregistered - The device has explicitly unregistered. Possible causes include a change in the IP address or port of the device. No action is necessary; the device will re-register automatically. |
| 11 |
MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, or an expires value that is too small. Check the REGISTER message for any of these issues and if you find one, correct the issue. |
| 12 |
SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. No action is necessary; the device will re-register automatically. |
| 13 |
KeepAliveTimeout - A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that network connectivity exists between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). No action is necessary; the device will re-register automatically. |
| 14 |
ConfigurationMismatch (SIP only) The configuration on the device does not match the configuration in Unified CM. This can be caused by database replication errors or other internal Unified CM communication errors. First go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify "all servers have a good replication status". You can also go to the Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. If this device continues to unregister with this reason code, go to the Device Configuration page in Unified CM Administration for the device identified in this alarm and click Save. This generates a change notification message to the Cisco CallManager and TFTP services and rebuilds a new configuration file. If the problem still persists, restart the TFTP service and Cisco CallManager service. |
| 15 |
CallManagerRestart - A device restart was initiated from Unified CM, either due to an explicit command from an administrator, or due to a configuration change such as adding, deleting or changing a directory number associated with the device. No action is necessary; the device will re-register automatically. |
| 16 |
DuplicateRegistration - Unified CM detected that the device attempted to register to two nodes at the same time. Unified CM initiated a restart to the phone to force it to re-home to a single node. No action is necessary; the device will re-register automatically. |
| 17 |
CallManagerApplyConfig - An ApplyConfig action was performed in Unified CM Administration resulting in an unregistration. No action is necessary; the device will re-register automatically. |
| 18 |
DeviceNoResponse - The device did not respond to a reset or restart notification, so it is being forcefully reset. If the device does not re-register within 5 minutes, confirm that the device is powered-up and confirm that network connectivity exists between the device and Unified CM. |
| 19 |
EMLoginLogout - The device has been unregistered due to an Extension Mobility login or logout |
| 20 |
EMCCLoginLogout - The device has been unregistered due to an Extension Mobility Cross Cluster login or logout |
| 21 |
PowerSavePlus - The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from Unified CM until the Phone On Time defined in the Product Specific Configuration for this device. |
| 22 |
CallManagerForcedRestart - (SIP Only) The device did not respond to an Apply Config request and as a result, Unified CM sent a restart request to the device. The device may be offline due to a power outage or network problem. Confirm that the device is powered-up and that network connectivity exists between the device and Unified CM. |
| 23 |
SourceIPAddrChanged - (SIP Only) The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. |
| 24 |
SourcePortChanged - (SIP Only) The device has been unregistered because the port number in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. |
| 25 |
RegistrationSequenceError - (SCCP only) A device requested configuration information from Unified CM at an unexpected time and Unified CM no longer had the requested information in memory. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC). |
| 26 |
InvalidCapabilities - (SCCP only) Unified CM detected an error in the updated media capabilities reported in one of the StationUpdateCapabilities messages sent by the device. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC). |
| 28 |
FallbackInitiated - The device has initiated a fallback and will automatically re-register to a higher-priority Unified CM. No action is necessary. |
| 29 |
DeviceSwitch - A second instance of an endpoint with the same device name has registered and assumed control. No action is necessary. |
Enum Definitions - IPAddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv4 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv4 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling |
Enum Definitions - IPV6AddrAttributes
| Value |
Definition |
| 0 |
Unknown - The device has not indicated what this IPv6 address is used for |
| 1 |
Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only |
| 2 |
Signal only - The device has indicated that this IPv6 address is used for control signaling only |
| 3 |
Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-SIPLineRegistrationError : SIP line registration error Device IP address [String] Device Port [UInt] Device name [String] Device MAC address [String] Device type [Enum]Reason Code [Enum]Connecting Port [UInt] Configured DNs [String] Registering SIP User [String]
Explanation A SIP line attempted to register with Cisco Unified Communications Manager (Unified CM) and failed due to the error indicated in the Reason Code parameter. The alarm could indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. This alarm typically occurs with a third-party device.
Recommended Action Verify that the directory number(s) on the device itself match the directory number(s) that are configured for that device in Cisco Unified CM Administration. Also, confirm that database replication is working. To do so, check the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is working. 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. Refer to the reason code definitions for additional recommended actions.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 61 |
H323_PHONE |
| 72 |
CTI_PORT |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30035 |
IP_STE |
Enum Definitions - Reason
| Value |
Definition |
| 2 |
MisconfiguredDirectoryNumber - There is a configuration mismatch between the directory numbers configured on the phone and the directory numbers configured in the Unified CM database. If this is a third-party phone, confirm that the phone configuration is correct and matches the Unified CM configuration. If this is a Cisco IP phone, go to the Cisco Unified Reporting web page and confirm that database replication has a "good status" in the Unified CM Database Status report. 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. If the database replication status is good, reset the device. If the problem still persists, restart the TFTP service and the Cisco CallManager service from the Control Center - Feature Services web page. |
| 3 |
MalformedRegisterMessage - Unified CM cannot process a REGISTER message because of a problem with the format of the message. If the device is a third-party phone, confirm that the endpoint is sending a properly formatted REGISTER message. |
| 4 |
AuthenticationError - The digest User ID or password sent from the phone does not match the User ID or password configured in Cisco Unified CM Administration. Digest User ID is the end user who is associated with the phone, as shown on the Phone Configuration page (in the Digest User drop-down list box). Password is configured on the End User Configuration page in the Digest Credentials field. If this is a third-party phone, ensure that the phone's digest credentials match the digest credentials configured on the End User Configuration page in Unified CM Administration. If this is a Cisco IP phone, go to the Cisco Unified Reporting web page to confirm that database replication has a "good status" in the Unified CM Database Status report. 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. If the database replication status is good, reset the device. If the problem still persists, restart the TFTP service and the Cisco CallManager service from the Control Center - Feature Services web page. |
| 6 |
MaxLinesExceeded - The phone is attempting to register more lines than are allowed. The maximum lines per device is 1024. Reduce the number of lines configured on this device. |
| 7 |
TransportProtocolMismatch - Incorrect transport protocol (UDP, TCP or TCL) on which the REGISTER message was received. If the device is a third-party phone, ensure that the phone is using a transport protocol that matches the Phone Security Profile assigned to the phone on the phone's Device Configuration page in Unified CM Administration. If the device is a Cisco phone, go to the Cisco Unified Reporting web page to confirm that database replication has a "good status" in the Unified CM Database Status report. 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. If the database replication status is good, reset the device. If the problem still persists, restart the TFTP service and the Cisco CallManager service from the Control Center - Feature Services web page. |
| 8 |
BulkRegistrationError - An unexpected bulk registration message was received. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" under Cisco CallManager service turned on and contact the Cisco Technical Assistance Center (TAC). |
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-H323Started : Unified CM is ready to handle calls for the indicated H.323 device Device Name [String] IP Address [String] Device type [Enum]Device description [String] Remote Unified CM Server IP Address/Host Name list as configured in the Trunk Configuration window [String] The Server 1 IP Address/Host Name as configured in the Trunk Configuration window; this parameter provides a partial list of remote Unified CM servers. Refer to the RemoteUnifiedCMServerList for the complete list of Unified CM servers. This parameter will be removed in Unified CM release 10.0(1) [String] Remote Unified CM Server 2 [String] Remote Unified CM Server 3 [String]
Explanation Cisco Unified Communications Manager (Unified CM) is ready to communicate with the indicated H.323 device. Note that this alarm describes the readiness of Unified CM to communicate with the indicated device but does not provide information about the state of the H.323 device (whether it is ready to communicate as well).
Recommended Action Notification purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 61 |
H323_PHONE |
| 62 |
H323_GATEWAY |
| 122 |
GATEKEEPER |
| 125 |
TRUNK |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-H323Stopped : Unified CM is not ready to handle calls for the indicated H.323 device Device Name [String] IP Address [String] Device type [Enum]Device description [String] Remote CallManager Server [String] Remote CallManager Server 2 [String] Remote CallManager Server 3 [String]
Explanation Unified CM is not ready to handle calls for the indicated H.323 device. This could be due to Unified CM being unable to resolve the gateway name to IP address. For trunks, this alarm should only occur when a system administrator has made a configuration change such as resetting the H.323 trunk. For H.323 clients, this alarm occurrence is normal on lower-priority Unified CM nodes when a high-priority Unified CM node starts.
Recommended Action If the service was stopped intentionally, no action is required. Check the domain name system (DNS) configuration for any errors in the gateway name or IP address and correct.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 61 |
H323_PHONE |
| 62 |
H323_GATEWAY |
| 122 |
GATEKEEPER |
| 125 |
TRUNK |
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-SIPStarted : Unified CM is ready to handle calls for the indicated SIP device Device Name [String] IP Address [String] Device type [Enum]Device description [String] Incoming Port Number [UInt] Outgoing Port Number [UInt] Incoming Transport Type [Enum]Outgoing Transport Type [Enum]IPV6Address [String]
Explanation Unified CM is ready to handle calls for the indicated SIP device. This alarm does not indicate the current state of the SIP device, only that Unified CM is prepared to handle calls to/from the SIP device.
Recommended Action Informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 131 |
SIP_TRUNK |
Enum Definitions - InTransportType
| Value |
Definition |
| 1 |
TCP |
| 2 |
UDP |
| 3 |
TLS |
| 4 |
TCP/UDP |
Enum Definitions - OutTransportType
| Value |
Definition |
| 1 |
TCP |
| 2 |
UDP |
| 3 |
TLS |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-SIPStopped : Unified CM is not ready to handle calls for the indicated SIP device Device Name [String] IP Address [String] Device type [Enum]Device description [String] Incoming Port Number [UInt] Outgoing Port Number [UInt] Incoming Transport Type [Enum]Outgoing Transport Type [Enum]IPV6Address [String]
Explanation Unified CM is not ready to handle calls for the indicated SIP device. Possible reasons could be internal database error, the SIP device is not activated on this node, the SIP device failed to register, or the SIP device was deleted from Cisco Unified CM Administration.
Recommended Action This alarm doesn't necessarily mean an error. It could occur as a result of normal administrative changes. If the alarm is unexpected, check whether the StationPortInitError alarm also fired. Check the Device Pool assigned to the SIP device identified in this alarm to ensure that the Cisco Unified Communications Manager Group of the Device Pool includes the Unified CM node that issued the alarm.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 131 |
SIP_TRUNK |
Enum Definitions - InTransportType
| Value |
Definition |
| 1 |
TCP |
| 2 |
UDP |
| 3 |
TLS |
| 4 |
TCP/UDP |
Enum Definitions - OutTransportType
| Value |
Definition |
| 1 |
TCP |
| 2 |
UDP |
| 3 |
TLS |
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-SIPNormalizationScriptOpened : Unified CM has opened the script for this device Device Name [String] Script Name [String] In Use Memory [UInt]
Explanation The normalization script for the indicated SIP device has been successfully loaded, initialized, and is active on Unified CM
Recommended Action Notification purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-SIPNormalizationScriptClosed : Unified CM has closed (disabled) the script for this device Device Name [String] Script Name [String] Reason Code [Enum]Reason Text [String] Additional Information [String]
Explanation Unified CM closed the script either because the indicated device (SIP trunk) was reset manually or automatically, the trunk was deleted, or because of a script error or resource error, or because of an internal error. When the script is closed, Unified CM is not invoking normalization script message handlers for the indicated SIP device.
Recommended Action This alarm serves as notification of the script closure if the alarm occurred due to a SIP trunk maintenance window or some other expected reason for the script to close. If this alarm is unexpected, check for an occurrence of the SIPNormalizationScriptError alarm and refer to the specific action based on the reason code identified in that alarm.
Reason Code - Enum Definitions
Enum Definitions - ReasonCode
| Value |
Definition |
| 1 |
DeviceResetManually - The associated device was manually reset via Cisco Unified CM Administration |
| 2 |
DeviceResetAutomatically - The associated device was reset automatically; the reset was triggered by an execution error in the script |
| 3 |
DeviceDeleted - The associated device was manually deleted in Cisco Unified CM Administration |
| 4 |
ScriptDisassociated - A configuration change occurred in Cisco Unified CM Administration and the script is no longer associated with the device |
| 5 |
ScriptInfoChanged - A change in the script logic occurred or a change to one or more fields on the SIP Normalization Script Configuration window in Cisco Unified CM Administration occurred |
| 6 |
ScriptError - An error occurred in the script; check for a SIPNormalizationScriptError alarm and perform the recommended actions described to correct the script error |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-SIPNormalizationScriptError : A script error occurred Device Name [String] Script Name [String] Script Function [String] Script Type [String] Error Code [Enum]Error Code Text [String] Error Message [String] Configured Action [String] Resulting Action [String] In Use Memory [UInt] Memory Threshold [UInt] In Use Lua Instructions [UInt] Lua Instruction Threshold [UInt]
Explanation Unified CM encountered an error during loading, initializing, or during execution of the SIP normalization script for the indicated SIP device. If the error was due to a resource issue, the SIPNormalizationResourceWarning alarm will also be issued. The Configured Action shown in this alarm may differ from the Resulting Action shown in this alarm because certain errors, such as those occurring during loading or initialization, cannot be configured. If the script closes three times within a 10-minute window due to errors, Unified CM will follow the configured action three times; on the fourth occurrence of the error, Unified CM disables the script and issues the SIPNormalizationAutoResetDisabled alarm.
Recommended Action Examine SDI trace files for details regarding the error such as function calls and the call ID which may help provide details that assist with troubleshooting the error. Examine the script for syntax or logic errors; for scripts provided by Cisco, contact the Cisco Technical Assistance Center (TAC). If the error was due to a resource issue, the SIPNormalizationResourceWarning alarm will also be issued. Check that alarm for additional information and recommended actions.
Reason Code - Enum Definitions
Enum Definitions - ErrorCode
| Value |
Definition |
| 1 |
LoadError - The script failed to load either due to a syntax error in the script or a resource error; check the Recommended Actions for instructions |
| 2 |
InitializationError - The script encountered a failure while initializing either due to a syntax error in the script or a resource error; check the Recommended Actions for instructions |
| 3 |
ExecutionError - The script encountered a failure during execution; check the Recommended Actions for instructions |
| 4 |
InternalError - The system encountered an unexpected condition during execution; check the Recommended Actions for instructions |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-SIPNormalizationResourceWarning : The script has exceeded an internal resource threshold and may be in danger of closing Device Name [String] Script Name [String] Script Function [String] Script Type [String] Reason Code [Enum]Reason Text [String] In Use Memory [UInt] Memory Threshold [UInt] In Use Lua Instructions [UInt] Lua Instruction Threshold [UInt]
Explanation The normalization script for the indicated SIP device has exceeded an internal threshold for resource consumption. This alarm can occur for memory consumption or when the script is close to exceeding the configured allowance of Lua instructions. When the amount of memory (as defined in the Memory Threshold field) or the number of Lua instructions utilized by this script (as defined by the Lua Instruction Threshold) exceeds an internal threshold, this alarm is triggered. For example, if the Memory Threshold is set to 100 kb and the internal threshold is 80%, this alarm will occur when this script has consumed 80 kb of memory. The internal threshold is not configurable and may fluctuate from Unified CM release to release. Another example: if the Lua Instruction Threshold is set to 2000 and the internal threshold is 50%, this alarm occurs when the script has executed 1000 Lua instructions. This alarm serves as a warning that resources (either memory or Lua instructions) have passed an internal mark where investigation into the consumption of those resources may be advisable to ensure the health of the script. Investigate and correct the resource issue before the script closes. When the values that have been configured in the fields, Memory Threshold field and/or Lua Instruction Threshold on the SIP Normalization Script Configuration window are met, the script closes and the SIPNormalizationScriptClosed alarm also occurs. For additional information when troubleshooting, check the SIP Normalization counter, MemoryUsagePercentage to learn the current resource usage.
Recommended Action Examine the thresholds (Memory Threshold and Lua Instruction Threshold) configured in the SIP Normalization Script Configuration window and evaluate if those thresholds can be increased (take into consideration the CPU resources and memory when deciding to increase these values) or examine the script to determine if the message handlers can be written more efficiently to reduce the number of instructions in the script. Examine the script for logic errors. If the script is otherwise functioning normally but contains extensive logic, consider increasing the value in the Lua Instruction Threshold field. Be aware that more computing resources will be consumed as a result. You can also examine SDI trace files for additional details about this resource condition. For scripts provided by Cisco, contact the Cisco Technical Assistance Center (TAC).
Reason Code - Enum Definitions
Enum Definitions - ReasonCode
| Value |
Definition |
| 1 |
InternalLuaInstructionsThreshold - The script exceeded the internal threshold for the number of Lua instructions |
| 2 |
InternalMemoryThreshold - The script exceeded the internal threshold for script memory usage |
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-SIPNormalizationAutoResetDisabled : An error has occurred repeatedly and Unified CM disabled the script Device Name [String] Script Name [String] Script Type [String] Reason Code [Enum]Reason Text [String] Additional Information [String]
Explanation The script failed due to execution errors three times within a 10 minute period. As a result, the normalization script for the indicated SIP device has been disabled. Unified CM is no longer attempting to automatically reset either the script or the device for the purposes of recovering the script.
Recommended Action Notification purposes; examine the information and perform the recommended actions in the SIPNormalizationScriptError alarm, which should have been issued prior to this alarm
Reason Code - Enum Definitions
Enum Definitions - ReasonCode
| Value |
Definition |
| 1 |
ScriptResetDisabled - The system has automatically reset the script three times within a 10 minute period due to script execution errors; on the fourth occurrence of this error, Unified CM disabled the script |
| 2 |
TrunkResetDisabled - The system has automatically reset the trunk three times within a 10 minute period due to script execution errors; on the fourth occurrence of this error, Unified CM disabled the script |
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-SIPTrunkISV : All remote peers are available to handle calls for this SIP trunk SIP Trunk Name [String] Available remote peers for this SIP trunk [String]
Explanation All remote peers are available to handle calls for this SIP trunk. This alarm specifies the available remote peers for this SIP trunk; each peer is identified by resolved IP address and port number, and hostname or SRV if configured on SIP trunk.
Recommended Action Notification purpose only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-SIPTrunkOOS : All remote peers are out of service and unable to handle calls for this SIP trunk SIP Trunk Name [String] Unavailable remote peers with Reason Code [String]
Explanation All remote peers for this SIP trunk are out of service and unable to handle calls. This alarm provides the reason code received by the SIP trunk in response to an Options request sent to the remote peer. The list of unavailable remote peers is provided in this alarm and each peer is separated by semi-colon. For each peer, the alarm provides the hostname or SRV (if configured on SIP trunk), resolved IP address, port number, and reason code in the following format: ReasonCodeType=ReasonCode. ReasonCodeType could be based on a SIP response from the remote peer as defined in SIP RFCs (Remote) or based on a reason code provided by Unified CM (Local). Examples of possible reason codes include Remote=503 ("503 Service Unavailable" a standard SIP RFC error code), Remote=408 ("408 Request Timeout" a standard SIP RFC error code), Local=1 (request timeout), Local=2 (local SIP stack is not able to create a socket connection with the remote peer), Local=3 (DNS query failed). For Local=3, IP address in Alarm will be represented as "0" and when dns srv is configured on SIP trunk then port will be represented as "0".
Recommended Action For Remote=503, possible reasons include 1) route/sip trunk for originating side doesn't exist on remote peer; 2) route/sip trunk for originating side does exist on the remote peer but the port is either used for a SIP phone or a different sip trunk; 3) the remote peer has limited resources and may not be able to handle new calls. For the first cause (item 1), if the remote peer is Unified CM, add a new SIP trunk in Unified CM Administration for the remote peer (Device > Trunk) and make certain that the Destination Address and Destination Port fields are configured to point to the originating host (the originating host is the same node on which this alarm was generated). Also ensure the new SIP trunk has the incoming port in associated SIP Trunk Security Profile configured to be same as originating side SIP Trunk destination port. For the second cause (item 2), if the remote peer is Unified CM, then in Unified CM Administration for the remote peer (Device > Trunk) make certain that incoming port in associated SIP Trunk Security Profile is configured to be same as originating side SIP Trunk destination port. For the third cause (item 3), if the remote peer is administered by a different system administrator, consider communicating the resource issue with the other administrator. For remote=408, possible reason includes remote is running low in resources and unable to process the request. If the remote peer is administered by a different system administrator, consider communicating the resource issue with the other administrator. For Local=1, possible reason could be that no responses has been received for Options request after all retries when transport is configured as UDP in SIP trunk Security Profile assigned to the SIP trunk on originating side. To fix this issue, if the remote peer is Unified CM, then go to remote peer Serviceability web page and then Tools -> Control Center (Feature Services) and make sure Cisco Call Manager service is activated and started. Also, go to remote peer admin web page and then to Device -> Trunk and do a find and make sure that there is a SIP trunk exist with incoming port in associated SIP Trunk security profile configured to be same as what is configured on originating side SIP Trunk destination port. Also, check the network connectivity using the CLI command "utils network ping remote_peer" at originating side. For Local=2, possible reason could be that Unified CM is not be able to create socket connection with remote peer. To fix this issue, if remote peer is Unified CM, then go to remote peer Serviceability web page and then Tools -> Control Center (Feature Services) and make sure Cisco Call Manager service is activated and started. Also, go to remote peer admin web page and then to Device -> Trunk and do a find and make sure that there is a SIP trunk exist with incoming port in associated SIP Trunk security profile configured to be same as what is configured on originating side SIP Trunk destination port. Also, check the network connectivity using "utils network ping remote_peer" at originating side. For Local=3, possible reason could be DNS server is not reachable or DNS is not properly configured to resolve hostname or SRV which is configured on local SIP trunk. To fix this issue, go to OS Administration web page and go to Show -> Network and look into DNS Details and make sure it is correct. If not then configure correct DNS server information using CLI "set network dns primary" command. Also, check the network connectivity with DNS server using "utils network ping "remote_peer" and make sure DNS server is properly configured.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-SIPTrunkPartiallyISV : Some of the remote peers are not available to handle calls for this SIP Trunk SIP Trunk Name [String] Unavailable remote peers with Reason Code [String] Available remote peers for this SIP trunk [String]
Explanation Some of the remote peers are not available to handle calls for this SIP trunk. This alarm provides a list of available remote peers and a list of unavailable remote peers and each peer is separated by semi-colon. Each available peer is identified by resolved IP address and port number, and hostname or SRV (if configured on SIP trunk). In the case of unavailable peers, the alarm provides the hostname or SRV (if configured on SIP trunk), resolved IP address, port number, and reason code in the following format: ReasonCodeType=ReasonCode. ReasonCodeType could be based on a SIP response from the remote peer as defined in SIP RFCs (Remote) or based on a reason code provided by Unified CM (Local). Examples of possible reason codes include Remote=503 ("503 Service Unavailable" a standard SIP RFC error code), Remote=408 ("408 Request Timeout" a standard SIP RFC error code), Local=1 (request timeout), Local=2 (local SIP stack is not able to create a socket connection with the remote peer), Local=3 (DNS query failed). For Local=3, IP address in Alarm will be represented as "0" and when dns srv is configured on SIP trunk then port will be represented as "0".
Recommended Action Available peer list is for notification purpose only; no action is required. For each unavailable peer, complete the following steps depending on the reason code provided in this alarm. For Remote=503, possible reasons include 1) route/sip trunk for originating side doesn't exist on remote peer; 2) route/sip trunk for originating side does exist on the remote peer but the port is either used for a SIP phone or a different sip trunk; 3) the remote peer has limited resources and may not be able to handle new calls. For the first cause (item 1), if the remote peer is Unified CM, add a new SIP trunk in Unified CM Administration for the remote peer (Device > Trunk) and make certain that the Destination Address and Destination Port fields are configured to point to the originating host (the originating host is the same node on which this alarm was generated). Also ensure the new SIP trunk has the incoming port in associated SIP Trunk Security Profile configured to be same as originating side SIP Trunk destination port. For the second cause (item 2), if the remote peer is Unified CM, then in Unified CM Administration for the remote peer (Device > Trunk) make certain that incoming port in associated SIP Trunk Security Profile is configured to be same as originating side SIP Trunk destination port. For the third cause (item 3), if the remote peer is administered by a different system administrator, consider communicating the resource issue with the other administrator. For remote=408, possible reason includes remote is running low in resources and unable to process the request. If the remote peer is administered by a different system administrator, consider communicating the resource issue with the other administrator. For Local=1, possible reason could be that no responses has been received for Options request after all retries when transport is configured as UDP in SIP trunk Security Profile assigned to the SIP trunk on originating side. To fix this issue, if the remote peer is Unified CM, then go to remote peer Serviceability web page and then Tools -> Control Center (Feature Services) and make sure Cisco Call Manager service is activated and started. Also, go to remote peer admin web page and then to Device -> Trunk and do a find and make sure that there is a SIP trunk exist with incoming port in associated SIP Trunk security profile configured to be same as what is configured on originating side SIP Trunk destination port. Also, check the network connectivity using the CLI command "utils network ping remote_peer" at originating side. For Local=2, possible reason could be that Unified CM is not be able to create socket connection with remote peer. To fix this issue, if remote peer is Unified CM, then go to remote peer Serviceability web page and then Tools -> Control Center (Feature Services) and make sure Cisco Call Manager service is activated and started. Also, go to remote peer admin web page and then to Device -> Trunk and do a find and make sure that there is a SIP trunk exist with incoming port in associated SIP Trunk security profile configured to be same as what is configured on originating side SIP Trunk destination port. Also, check the network connectivity using "utils network ping remote_peer" at originating side. For Local=3, possible reason could be DNS server is not reachable or DNS is not properly configured to resolve hostname or SRV which is configured on local SIP trunk. To fix this issue, go to OS Administration web page and go to Show -> Network and look into DNS Details and make sure it is correct. If not then configure correct DNS server information using CLI "set network dns primary" command. Also, check the network connectivity with DNS server using "utils network ping "remote_peer" and make sure DNS server is properly configured.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-ConnectionFailure : Unified CM failed to open a TLS connection for the indicated device Device Name [String] IP Address [String] Device type [Enum]Device description [String] Reason code [Enum]
Explanation Unified CM failed to open a TLS connection for the indicated device because an incorrect Device Security Mode was configured or an incorrect X.509 Subject Name was configured, or due to an unsupported cipher algorithm
Recommended Action Check the Security Profile of the indicated device. Make certain that Device Security Mode is set to either Authenticated or Encrypted. Make sure that the X.509 Subject Name field has the appropriate content; it should match the Subject Name in the certificate from the peer. Also, Unified CM only supports the AES_128_SHA cipher algorithm; let the peer regenerate its certificate with the correct algorithm.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 61 |
H323_PHONE |
| 72 |
CTI_PORT |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 131 |
SIP_TRUNK |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30035 |
IP_STE |
Enum Definitions - Reason
| Value |
Definition |
| 1 |
AuthenticationError - Device Security Mode is not set to either Authenticated or Encrypted |
| 2 |
InvalidX509NameInCertificate - Configured X.509 Subject Name doesn't match the name in the certificate from the peer |
| 3 |
InvalidTLSCipher - Unsupported cipher algorithm used by the peer; Unified CM only supports AES_128_SHA |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-MediaResourceListExhausted : The requested device type is not found in the media resource list or default list or the configured devices are not registered Media Resource Type [Enum]Media Resource List Name [String]
Explanation The requested device is not configured in the Media Resource Group List or Default List, or it's possible that one or more of the devices that are configured in the Media Resource Group List or Default List are not registered to Cisco Unified Communications Manager
Recommended Action First, go to Cisco Unified CM Administration to check the configuration of the devices that are part of the Media Resource Groups in the Media Resource Group List that was specified in the alarm (Media Resource Group List Configuration window and Media Resource Group Configuration window in Unified CM Administration). Check whether the requested type of device is configured in any of the Media Resource Groups in that particular Media Resource Group List; for RSVP Agent, check whether any media termination point or transcoder is configured in any of the Media Resource Groups in that particular Media Resource Group List. Next, go to the Media Resources menu in Cisco Unified CM Administration to see all the devices of the requested type and then check all the Media Resource Groups (irrespective of whether they belong to the Media Resource Group List for which the alarm is generated) to determine whether the devices belong to at least one Media Resource Group. If there exists some media resources of the requested type which do not belong to any Media Resource Groups, then these devices will belong to the Default List. If the requested type of device is not configured in any of the Media Resource Groups of the Media Resource Group List for which the alarm is generated or in the Default List, add the requested type of device to a Media Resource Group in the specified Media Resource Group List or add it to the Default List. To add a media resource to the Default List, remove the Media Device from all the Media Resource Groups. In general, when a new media device is initially added to Unified CM it will automatically be added to the Default List. This Default List can be used by any device or trunk. But when the media device is added to any particular Media Resource Group it will not be available to the Default List. It can only be used by devices and trunks that are configured with the Media Resource Group List that have that particular Media Resource Group. Note that a particular Media Resource Group can be added to multiple Media Resource Group Lists. If the requested device is properly configured in Cisco Unified CM Administration, check whether the device is registered to Unified CM. To do that go to the Media Resources menu of the requested type of device (such as Annunciator or Conference Bridge or Media Termination Point or Music On Hold Server or Transcoder) and click the Find button. All the devices of that type will display along with their status, device pool, and so on. Check the status field to see whether the device is registered with Unified CM. Note that the display on the status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified CM cluster that the Publisher can only write to the Unified CM database and suppose the Publisher goes down. Because the Subscriber may not be able to write to the database the devices may still display as registered in Unified CM Administration after they are actually unregistered. However, if the Publisher is down that should generate another alarm with higher priority than this alarm. If the device is not registered, click on the name of that particular device and check the type of the device. Device types including Cisco Conference Bridge Software, Cisco Media Termination Point Software, or that specify a server name that is the same name as a Unified CM node of the cluster indicate that the requested device is a software device and is part of the Cisco IP Voice Media Streaming application. Check to be sure that the IP Voice Media Streaming App service is enabled on that Unified CM node (Cisco Unified Serviceability > Tools > Service Activation) and if it is not enabled, activate the Cisco IP Voice Media Streaming App service. Devices should try to register. You can also check the status of the service to be sure it is showing as Started (Tools > Control Center > Feature Services). If the device type is a type other than Cisco Conference Bridge Software, Cisco Media Termination Point Software, or a server name that is the same name as a Unified CM node, that indicates that the device is an external media resource to Unified CM. Check the configuration (such as Conference Bridge type, MAC address, and conference bridge name in the case of a conference bridge; Media Termination Point name in the case of a Media Termination Point; Transcoder type, MAC address, and Transcoder name in the case of a Transcoder) of the device in Cisco Unified CM Administration and compare it with the configuration of the actual device. To check the configuration of the actual device you may need to refer to the user manual of the media device. The user manual should provide all the details such as connecting to the media device to check the configuration, commands needed to view and update the configuration, and so on. If configuration in Unified CM and on the actual devices are different, make the necessary changes so that the configurations match. If the configuration matches and the device is still not registered, restart the external media device or the service associated with the external media device. If the external media device continues to fail to register with Unified CM, check the network connectivity between Unified CM and the media device.
Reason Code - Enum Definitions
Enum Definitions - MediaResourceType
| Value |
Definition |
| 1 |
Media termination point |
| 2 |
Transcoder |
| 3 |
Conference bridge |
| 9 |
RSVP agent |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-RouteListExhausted : An available route could not be found in the indicated route list Route List Name [String]
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
CCM_CALLMANAGER-CALLMANAGER-3-DeviceTypeMismatch : 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 Database device type [Enum]Device type [Enum]Name of device [String]
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 get updated at the device itself.
Recommended Action Check the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is working. 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. Restart the phone to download a new configuration file from TFTP.
Reason Code - Enum Definitions
Enum Definitions - DBDeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 61 |
H323_PHONE |
| 72 |
CTI_PORT |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30035 |
IP_STE |
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 61 |
H323_PHONE |
| 72 |
CTI_PORT |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30035 |
IP_STE |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DeviceDnInformation : List of directory numbers (DN) associated with this device Device Name [String] Device type [Enum]Station Desc [String] Station Dn [String]
Explanation Provides a list of directory numbers (DN) associated with the device
Recommended Action Informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 10 |
CISCO_VGC_PHONE |
| 11 |
CISCO_VGC_VIRTUAL_PHONE |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 21 |
STATION_PHONE_APPLICATION |
| 30 |
ANALOG_ACCESS |
| 40 |
DIGITAL_ACCESS |
| 41 |
DIGITAL_ACCESS_T1 |
| 42 |
DIGITAL_ACCESS+ |
| 43 |
DIGITAL_ACCESS_WS-X6608 |
| 47 |
ANALOG_ACCESS_WS-X6624 |
| 48 |
VGC_GATEWAY |
| 50 |
CONFERENCE_BRIDGE |
| 51 |
CONFERENCE_BRIDGE_HARDWARE |
| 52 |
CONFERENCE_BRIDGE_HARDWARE_HDV2 |
| 53 |
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM |
| 61 |
H323_PHONE |
| 62 |
H323_GATEWAY |
| 70 |
MUSIC_ON_HOLD |
| 71 |
DEVICE_PILOT |
| 72 |
CTI_PORT |
| 73 |
CTI_ROUTE_POINT |
| 80 |
VOICE_MAIL_PORT |
| 83 |
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2 |
| 84 |
CISCO_MEDIA_SERVER |
| 85 |
CISCO_VIDEO_CONFERENCE_BRIDGE |
| 90 |
ROUTE_LIST |
| 100 |
LOAD_SIMULATOR |
| 110 |
MEDIA_TERMINATION_POINT |
| 111 |
MEDIA_TERMINATION_POINT_HARDWARE |
| 112 |
MEDIA_TERMINATION_POINT_HDV2 |
| 113 |
MEDIA_TERMINATION_POINT_WS-SVC-CMM |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 120 |
MGCP_STATION |
| 121 |
MGCP_TRUNK |
| 122 |
GATEKEEPER |
| 124 |
7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 |
TRUNK |
| 126 |
TONE_ANNOUNCEMENT_PLAYER |
| 131 |
SIP_TRUNK |
| 132 |
SIP_GATEWAY |
| 133 |
WSM_TRUNK |
| 134 |
REMOTE_DESTINATION_PROFILE |
| 254 |
UNKNOWN_MGCP_GATEWAY |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30027 |
ANALOG_PHONE |
| 30028 |
ISDN_BRI_PHONE |
| 30032 |
SCCP_GATEWAY_VIRTUAL_PHONE |
| 30035 |
IP_STE |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-StationConnectionError : Station device is closing the connection Device Name [String] Reason Code [Enum]
Explanation A station device is closing its connection with Unified CM because of the reason that is described in this alarm
Recommended Action Informational purposes only; no action is required. Also, refer to the reason code definition for additional information.
Reason Code - Enum Definitions
Enum Definitions - ReasonCode
| Value |
Definition |
| 0 |
deviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action is required; the device will re-register automatically. |
| 1 |
sccpDeviceThrottling - (SCCP only) The indicated SCCP device has exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. No action is required; the device will re-register automatically. |
| 2 |
keepAliveTimeout - Unified CM did not receive a KeepAlive message from the device. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify network connectivity between the device and Unified CM, and verify that CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). No action is required; the device will re-register automatically. |
| 3 |
dbChangeNotify - An ApplyConfig command was issued from Unified CM Administration resulting in an unregistration. No action is required; the device will re-register automatically. |
| 4 |
deviceRegistrationSuperceded - An initial device registration request was received but authentication had not yet completed before a new registration request was received. The first registration request was discarded and re-registration should proceed normally. No action is required; the device will re-register automatically. |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-StationAlarm : A station has sent an alarm to Unified CM for pass-through purposes Protocol [String] TCP ProcessID [String] Device Text [String] Param1 [UInt] Param2 [UInt]
Explanation A station device sent an alarm to Unified CM, which acts as a conduit from the device to generate this alarm
Recommended Action To determine the appropriate action, refer to the specific device type and information passed from the device via this alarm
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-StationEventAlert : A station sent an alert to Unified CM for pass-through purposes Protocol [String] TCP ProcessID [String] Device Text [String] Param1 [UInt] Param2 [UInt]
Explanation A station device sent an alert to Unified CM, which acts as a conduit from the device to generate this alarm
Recommended Action To determine the appropriate action, refer to the specific device type and information passed from the device via this alarm
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-MGCPGatewayGainedComm : MGCP communication to the gateway has been established Device Name [String]
Explanation The MGCP gateway has established communication with Unified CM
Recommended Action Notification purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-MGCPGatewayLostComm : MGCP gateway has lost communication with Unified CM Device Name [String]
Explanation The MGCP gateway is no longer in communication with Unified CM. This could occur because Unified CM received an MGCP unregister signal from the gateway such as RSIP graceful/forced; Unified CM didn't receive the MGCP KeepAlive signal from the gateway; the MGCP gateway didn't response to an MGCP command sent by Unified CM three times; a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway; or the gateway has reset.
Recommended Action Reset the MGCP gateway in an attempt to restore communication with Unified CM; check the speed and duplex settings on the Ethernet port. In the case of an unwanted reset of the gateway which caused communication to be lost, take precautions to ensure that no unauthorized personnel resets the gateway from Cisco Unified CM Administration or via the gateway terminal.
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-StationPortInitError : Station TCP initialization error
Explanation An error during initialization was encountered
Recommended Action Verify that the Cisco Unified Communications Manager IP address is configured and is not configured as the loop back address for the IP version. Check the SCCP TCP port configuration to be sure the SCCP TCP port is accurately configured (be certain that there are no port conflicts where another port has the same number). If the IP and port settings are correct, collect SDL and SDI traces and contact the Cisco Technical Assistance Center (TAC).
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DbInfoError : Configuration information may be out of sync for the device and Unified CM database Name of Device [String]
Explanation Configuration information may be out of sync for the device and Unified CM database
Recommended Action Go to Unified CM Administration and confirm that the device specified in this alarm actually exists in the database. If it does not, add the device. If the device is found in Unified CM Administration, examine the device information on the Device Configuration page for this device to make certain that important device information such as MAC address, device name, device pool configuration, and so on are configured accurately. If you find a discrepancy, correct it and reset the device.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DbInfoTimeout : Unified CM did not receive a timely response from the database Name of Device [String]
Explanation Unified CM requested information about the device specified in this alarm but the Unified CM Administration database did not respond before the internally-configured wait timer in Unified CM expired. Delays can occur because of congestion in accessing the database.
Recommended Action Go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report and verify that the report shows that "Local and publisher databases are accessible" and that "all servers have a good replication status". If database status and DB replications look good, the database may be busy with auto-registrations or other intensive tasks. If you know that auto-registration is proceeding for a large number of devices, wait for it to complete (you can also monitor by watching the CPU level on the database server) and allow the phone to attempt to auto-register again.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DbInfoCorrupt : Configuration information may be out of sync for the device and Unified CM database Name of Device [String]
Explanation Configuration information may be out of sync for the device and Unified CM database
Recommended Action Go to Unified CM Administration and confirm that the device specified in this alarm actually exists in the database. If it does not, add the device. If the device is found in Unified CM Administration, examine the device information on the Device Configuration page for this device to make certain that important device information such as MAC address, device name, device pool configuration, and so on are configured accurately. If you find a discrepancy, correct it and reset the device.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-NotEnoughChans : Not enough channels Device Name [String]
Explanation A call attempt was rejected because the requested gateway channel(s) could not be allocated. Some of the more common reasons for the lack of channel to place outgoing calls include: High call traffic volume that has the B-channels in the device fully utilized; B-channels have gone out of service for the following reasons: Taking the channel out of service intentionally to perform maintenance on either the near- or far-end; MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Cisco Unified Communications Manager; MGCP gateway doesn't respond to an MGCP command sent by Unified CM three times; a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway.
Recommended Action Add more gateway resources; Check the Cisco CallManager advanced service parameter, Change B-channel Maintenance Status to determine if the B-channel has been taken out of service intentionally; Check the Q.931 trace for PRI SERVICE message to determine whether a PSTN provider has taken the B-channel out of service; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DeviceResetInitiated : Device reset initiated on the specified device Device name [String] Product type [String] Device type [Enum]
Explanation This alarm occurs when a device is reset via the Reset button in Cisco Unified CM Administration. Reset may cause the device to shut down and come back in service. A device can be reset only when it is registered with Unified CM.
Recommended Action Informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 10 |
CISCO_VGC_PHONE |
| 11 |
CISCO_VGC_VIRTUAL_PHONE |
| 30 |
ANALOG_ACCESS |
| 40 |
DIGITAL_ACCESS |
| 42 |
DIGITAL_ACCESS+ |
| 43 |
DIGITAL_ACCESS_WS-X6608 |
| 47 |
ANALOG_ACCESS_WS-X6624 |
| 48 |
VGC_GATEWAY |
| 50 |
CONFERENCE_BRIDGE |
| 51 |
CONFERENCE_BRIDGE_HARDWARE |
| 52 |
CONFERENCE_BRIDGE_HARDWARE_HDV2 |
| 53 |
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM |
| 62 |
H323_GATEWAY |
| 70 |
MUSIC_ON_HOLD |
| 71 |
DEVICE_PILOT |
| 73 |
CTI_ROUTE_POINT |
| 80 |
VOICE_MAIL_PORT |
| 83 |
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2 |
| 84 |
CISCO_MEDIA_SERVER |
| 85 |
CISCO_VIDEO_CONFERENCE_BRIDGE |
| 90 |
ROUTE_LIST |
| 100 |
LOAD_SIMULATOR |
| 110 |
MEDIA_TERMINATION_POINT |
| 111 |
MEDIA_TERMINATION_POINT_HARDWARE |
| 112 |
MEDIA_TERMINATION_POINT_HDV2 |
| 113 |
MEDIA_TERMINATION_POINT_WS-SVC-CMM |
| 120 |
MGCP_STATION |
| 121 |
MGCP_TRUNK |
| 122 |
GATEKEEPER |
| 124 |
7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 |
TRUNK |
| 126 |
TONE_ANNOUNCEMENT_PLAYER |
| 131 |
SIP_TRUNK |
| 132 |
SIP_GATEWAY |
| 133 |
WSM_TRUNK |
| 134 |
REMOTE_DESTINATION_PROFILE |
| 227 |
7915_12_BUTTON_LINE_EXPANSION_MODULE |
| 228 |
7915_24_BUTTON_LINE_EXPANSION_MODULE |
| 229 |
7916_12_BUTTON_LINE_EXPANSION_MODULE |
| 230 |
7916_24_BUTTON_LINE_EXPANSION_MODULE |
| 232 |
CKEM_36_BUTTON_LINE_EXPANSION_MODULE |
| 254 |
UNKNOWN_MGCP_GATEWAY |
| 255 |
UNKNOWN |
| 30027 |
ANALOG_PHONE |
| 30028 |
ISDN_BRI_PHONE |
| 30032 |
SCCP_GATEWAY_VIRTUAL_PHONE |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-EndPointResetInitiated : Endpoint reset initiated on the specified endpoint Device name [String] Product type [String] Device type [Enum]
Explanation This alarm occurs when a device is reset via the Reset button in Cisco Unified CM Administration. Reset causes the device to shut down and come back in service. A device can be reset only when it is registered with Unified CM.
Recommended Action Informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 61 |
H323_PHONE |
| 72 |
CTI_PORT |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30035 |
IP_STE |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DeviceRestartInitiated : Device restart initiated or Apply Config initiated on the specified device Device name [String] Product type [String] Device type [Enum]
Explanation This alarm occurs when a device is restarted via the Restart button in Cisco Unified CM Administration window or when a system administrator presses the Apply Config button for a device that does not support conditional restart. Restart causes the device to unregister, receive updated configuration, and re-register with Cisco Unified Communications Manager (Unified CM) without shutting down. A device can be restarted only when it is registered with Unified CM.
Recommended Action Informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 10 |
CISCO_VGC_PHONE |
| 11 |
CISCO_VGC_VIRTUAL_PHONE |
| 30 |
ANALOG_ACCESS |
| 40 |
DIGITAL_ACCESS |
| 42 |
DIGITAL_ACCESS+ |
| 43 |
DIGITAL_ACCESS_WS-X6608 |
| 47 |
ANALOG_ACCESS_WS-X6624 |
| 48 |
VGC_GATEWAY |
| 50 |
CONFERENCE_BRIDGE |
| 51 |
CONFERENCE_BRIDGE_HARDWARE |
| 52 |
CONFERENCE_BRIDGE_HARDWARE_HDV2 |
| 53 |
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM |
| 62 |
H323_GATEWAY |
| 70 |
MUSIC_ON_HOLD |
| 71 |
DEVICE_PILOT |
| 73 |
CTI_ROUTE_POINT |
| 80 |
VOICE_MAIL_PORT |
| 83 |
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2 |
| 84 |
CISCO_MEDIA_SERVER |
| 85 |
CISCO_VIDEO_CONFERENCE_BRIDGE |
| 90 |
ROUTE_LIST |
| 100 |
LOAD_SIMULATOR |
| 110 |
MEDIA_TERMINATION_POINT |
| 111 |
MEDIA_TERMINATION_POINT_HARDWARE |
| 112 |
MEDIA_TERMINATION_POINT_HDV2 |
| 113 |
MEDIA_TERMINATION_POINT_WS-SVC-CMM |
| 120 |
MGCP_STATION |
| 121 |
MGCP_TRUNK |
| 122 |
GATEKEEPER |
| 124 |
7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 |
TRUNK |
| 126 |
TONE_ANNOUNCEMENT_PLAYER |
| 131 |
SIP_TRUNK |
| 132 |
SIP_GATEWAY |
| 133 |
WSM_TRUNK |
| 134 |
REMOTE_DESTINATION_PROFILE |
| 227 |
7915_12_BUTTON_LINE_EXPANSION_MODULE |
| 228 |
7915_24_BUTTON_LINE_EXPANSION_MODULE |
| 229 |
7916_12_BUTTON_LINE_EXPANSION_MODULE |
| 230 |
7916_24_BUTTON_LINE_EXPANSION_MODULE |
| 232 |
CKEM_36_BUTTON_LINE_EXPANSION_MODULE |
| 254 |
UNKNOWN_MGCP_GATEWAY |
| 255 |
UNKNOWN |
| 30027 |
ANALOG_PHONE |
| 30028 |
ISDN_BRI_PHONE |
| 30032 |
SCCP_GATEWAY_VIRTUAL_PHONE |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-EndPointRestartInitiated : Endpoint restart initiated or Apply Config initiated on the specified endpoint Device name [String] Product type [String] Device type [Enum]
Explanation This alarm occurs when an endpoint is restarted via the Restart button in Cisco Unified CM Administration window or when a system administrator presses the Apply Config button for an endpoint that does not support conditional restart. Restart causes the endpoint to unregister, receive an updated configuration file, and re-register with Cisco Unified Communications Manager (Unified CM) without shutting down. An endpoint can be restarted only when it is registered with Unified CM.
Recommended Action Informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 1 |
CISCO_30SP+ |
| 2 |
CISCO_12SP+ |
| 3 |
CISCO_12SP |
| 4 |
CISCO_12S |
| 5 |
CISCO_30VIP |
| 6 |
CISCO_7910 |
| 7 |
CISCO_7960 |
| 8 |
CISCO_7940 |
| 9 |
CISCO_7935 |
| 12 |
CISCO_ATA_186 |
| 20 |
SCCP_PHONE |
| 61 |
H323_PHONE |
| 72 |
CTI_PORT |
| 115 |
CISCO_7941 |
| 119 |
CISCO_7971 |
| 255 |
UNKNOWN |
| 302 |
CISCO_7989 |
| 307 |
CISCO_7911 |
| 308 |
CISCO_7941G_GE |
| 309 |
CISCO_7961G_GE |
| 335 |
MOTOROLA_CN622 |
| 336 |
BASIC_3RD_PARTY_SIP_DEVICE |
| 348 |
CISCO_7931 |
| 358 |
CISCO_UNIFIED_COMMUNICATOR |
| 365 |
CISCO_7921 |
| 369 |
CISCO_7906 |
| 374 |
ADVANCED_3RD_PARTY_SIP_DEVICE |
| 375 |
CISCO_TELEPRESENCE |
| 404 |
CISCO_7962 |
| 412 |
CISCO_3951 |
| 431 |
CISCO_7937 |
| 434 |
CISCO_7942 |
| 435 |
CISCO_7945 |
| 436 |
CISCO_7965 |
| 437 |
CISCO_7975 |
| 446 |
CISCO_3911 |
| 468 |
CISCO_UNIFIED_MOBILE_COMMUNICATOR |
| 478 |
CISCO_TELEPRESENCE_1000 |
| 479 |
CISCO_TELEPRESENCE_3000 |
| 480 |
CISCO_TELEPRESENCE_3200 |
| 481 |
CISCO_TELEPRESENCE_500 |
| 484 |
CISCO_7925 |
| 493 |
CISCO_9971 |
| 495 |
CISCO_6921 |
| 496 |
CISCO_6941 |
| 497 |
CISCO_6961 |
| 20000 |
CISCO_7905 |
| 30002 |
CISCO_7920 |
| 30006 |
CISCO_7970 |
| 30007 |
CISCO_7912 |
| 30008 |
CISCO_7902 |
| 30016 |
CISCO_IP_COMMUNICATOR |
| 30018 |
CISCO_7961 |
| 30019 |
CISCO_7936 |
| 30035 |
IP_STE |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DeviceApplyConfigInitiated : An Apply Config action was initiated by a system administrator for the specified device Device name [String] Product type [String] Device type [Enum]
Explanation This alarm occurs when a system administrator presses the Apply Config button in Cisco Unified Communications Manager (Unified CM). The Apply Config button initiates a conditional restart on devices that support conditional restart. This button triggers the system to determine if any relevant configuration has changed for the device. If the configuration changes can be applied dynamically, they are made without service interruption. If a change requires that the device reregister with Unified CM, reregistration occurs automatically. If a change requires a restart, the device will be automatically restarted. If the load ID for a device changes, the device will initiate a background download of the new firmware. The new firmware can then be applied immediately or at a later time. For phones and devices that do not support conditional restart, clicking Apply Config causes these devices to restart.
Recommended Action Informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 493 |
CISCO_9971 |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-DaTimeOut : 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
CCM_CALLMANAGER-CALLMANAGER-5-MaxCallDurationTimeout : Maximum call duration timer has expired Maximum Call Duration (minutes) [UInt] Originating Device name [String] Destination Device name [String] Call start time [UInt] Call stop time [UInt] Calling Party Number [String] Called Party Number [String]
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
CCM_CALLMANAGER-CALLMANAGER-6-MaxHoldDurationTimeout : Maximum Hold Duration Timer expired Maximum Hold Duration (minutes) [Int] Originating Device Name [String] Destination Device Name [String] Hold start time [UInt] Hold stop time [UInt] Calling Party Number [String] Called Party Number [String]
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
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-TimerThreadSlowed : Timer thread has slowed beyond acceptable limits
Explanation Verification of the Unified CM internal timing mechanism has slowed beyond acceptable limits. This generally indicates an increased load on the system or an internal anomaly.
Recommended Action If this alarm occurs at the same general day or time, or if it occurs with increasing frequency, collect all system performance data in Real-Time Monitoring Tool as well as all trace information for the 30 minutes prior to the time that this alarm occurred and contact the Cisco Technical Assistance Center (TAC)
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DatabaseDefaultsRead : Database default information was read successfully
Explanation Database default information was read successfully; this alarm will be removed in Unified CM release 10.0(0).
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DeviceInitTimeout : Device initialization timed out due to internal error Device Name [String] Protocol [String] Side Number [UInt]
Explanation A device initialization timeout occurred because the device did not respond to an initialize request. If this alarm occurs in tandem with a configuration change, this may not indicate a problem unless this alarm recurs.
Recommended Action If you are making a configuration change around the time that this alarm occurred, determine whether the problem still exists by calling the phone or placing a call through the trunk or gateway. If the call fails, reset the device. If the alarm recurs after resetting the device, 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.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-NumDevRegExceeded : The allowed number of registered devices has been exceeded Maximum Devices [Int]
Explanation The allowed number of registered devices, as controlled by the Cisco CallManager service parameter Maximum Number of Registered Devices, has been exceeded
Recommended Action If you did not expect to exceed the number of devices and you have auto-registration enabled, go to Device > Phones in Cisco Unified CM Administration and search for phones starting with "auto". If you see any unexpected devices which may not belong in the system (such as intruder devices) locate that device using it's IP address and remove it from the system. Or, if your licenses and system resources allow, increase the value in the Cisco CallManager service parameter, Maximum Number of Registered Devices.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-CallManagerOnline : Cisco CallManager service is online CCM Version [String]
Explanation The Cisco CallManager service has completed initialization and is online
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-MtpNoMoreResourcesAvailable : MTP or transcoder allocation failed Media Resource List Name [String]
Explanation The alarm occurs when allocation of a media termination point (MTP) or transcoder fails for all the registered MTPs or transcoders belonging to the Media Resource Group List and Default List. Each MTP or transcoder may fail for different reasons. Following are some of the reasons that could cause an MTP or transcoder allocation to fail: a capability mismatch between the device endpoint and MTP/transcoder, codec mismatch between the endpoint and the MTP/transcoder; a lack of available bandwidth between the endpoint and the MTP/transcoder; or because the MTP/transcoders resources are already in use. A capability mismatch may be due to the MTP/transcoder not supporting one or more of the required capabilities for the call such as Transfer Relay Point (which is needed for QoS or firewall traversal), RFC 2833 DTMF (which is necessary when one side of the call does not support RFC 2833 format for transmitting DTMF digits and the other side must receive the DTMF digits in RFC 2833 format, resulting in conversion of the DTMF digits), RFC 2833 DTMF passthrough (in this case, the MTP or transcoder does not need to convert the DTMF digits from one format to another format but it needs to receive DTMF digits from one endpoint and transmit them to the other endpoint without performing any modifications), passthrough (where no codec conversion will occur, meaning the media device will receive media streams in any codec format and transmit them to the other side without performing any codec conversion), IPv4 to IPv6 conversion (when one side of the call supports only IPv4 and the other side of the call supports only IPv6 and so an MTP needs to be inserted to perform the necessary conversion between IPv4 and IPv6 packets), or multimedia capability (if a call involving video and/or data in addition to audio requires insertion of an MTP or transcoder then the MTP/transcoder which supports multimedia will be inserted).
Recommended Action If the MTP or transcoder allocation is failing due to a capability mismatch, it's possible that the media device does not support the capability (such as IPv4 to IPv6 conversion, passthrough) or the capability might not be configured in the device. Please check the user guide and documentation of the media device to make sure that device supports all the necessary capabilities. Also, caution should be taken if all the MTP or transcoders are configured with all the supported capabilities. There are certain capabilities (such as RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough) which could be supported by most of the MTPs or transcoders and there may be certain capabilities (such as IPv4 to IPv6 conversion and vice versa or Transfer Relay Point or multimedia capability) which can be supported by only by a single MTP or transcoder depending on the devices that you have. For example, you may have IP phones that support only IPv4 protocol and there may also be IP phones that support only IPv6 protocol. To make a call between IPv4-only and IPv6-only phones, you need to have an MTP configured to perform the conversion of IPv4 to IPv6 and vice versa. However, suppose all the MTPs or transcoders are configured with all the supported capabilities and only one MTP supports IPv4 to IPv6 conversion; if this MTP is configured with all the supported capabilities (which all the other MTPs or transcoders in the same MRGL or default MRGL also support) it may happen that this MTP can get allocated for Transfer Relay Point or RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough instead. As a result, when the need arises for IPv4 to IPv6 conversion (which other MTPs or transcoders in the same MRGL or default MRGL do not support), all the resources of MTP may be in use and the IPv4 to IPv6 conversion may fail. To avoid this kind of problem, setting the priority of the media resources may be a good idea. This can be done only in the Media Resource Group List and not in the Default List of the media resources. In any Media Resource Group List all the Media Resource Groups have different priorities; during allocation the first Media Resource Group is always checked for availability of the requested type of the media devices. The first Media Resource Group in the Media Resource Group List will have the highest priority, then the second one, and so on. To check all the Media Resource Groups and their priority go the Media Resources and Media Resource Group List of Cisco Unified CM Administration page and click the appropriate Media Resource Group List and check the Selected Media Resource Groups; the priority decreases from top to bottom. So, the MTP or transcoder that you want to be selected for the most basic functionalities should be positioned in the higher priority Media Resource Groups whereas the ones with more rare functionality should be positioned in the Media Resource Groups with lower priority. MTP/transcoder allocation may fail due to codec mismatch between the endpoint and the MTP/transcoder. A solution may be to configure the MTP/transcoder with all the supported codecs (as specified in the user guide of the MTP/transcoder), but be aware that doing so might result in too much bandwidth being allocated for calls. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, approximate bandwidth use per call (not involving MTP/transcoder), and so on, and accordingly calculate the maximum bandwidth that can be allocated per call involving an MTP/transcoder and take that into consideration when configuring the supported codecs in the MTPs and transcoders. It's a good idea to configure the media devices with all the supported codecs and set the region bandwidths to restrict too much bandwidth usage (refer to the Unified CM documentation for details on region and location settings). Also, there may be a codec mismatch between the endpoint and the MTP/transcoders after considering the region bandwidth between the MTP/transcoder and the endpoint. Increasing the region bandwidth may be a solution to the problem, but again, that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions. Another possible cause that an MTP/transcoder did not get allocated is because there was not enough available bandwidth for the call. This can happen if the MTP/transcoder and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, please note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth available. Finally, if MTP or transcoder allocation fails due to capability mismatch or all the resources being in use, consider installing additional MTP or transcoder devices.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-MohNoMoreResourcesAvailable : MOH resource allocation failed Media Resource List Name [String]
Explanation This alarm occurs when allocation of Music On Hold fails for all the registered MOH servers belonging to the Media Resource Group List and Default List. Each MOH server may fail for different reasons. Following are some of the reasons that could cause an MOH server allocation to fail: All the resources of MOH server are already in use; No matching codecs or capability mismatch between the held party and MOH server; Not enough bandwidth between the held party and MOH source; No audio stream available for the MOH server.
Recommended Action If all the resources of the MOH servers are already in use, check to be sure that all the MOH servers that belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are configured and registered in all the applicable Unified CM nodes. To check the registration status go to the Media Resources > Music On Hold Server menu and click the Find button. It will display all the MOH servers with their status, device pool, and so on. Check the status field to discover whether it is registered with Unified CM. Note that the display on the status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified CM cluster that the Publisher can only write to the Unified CM database and the Publisher goes down. Because the Subscriber may not be able to write to the database, the devices may still display as registered in Unified CM Administration after they are actually unregistered. However, if the Publisher is down that should generate another alarm with higher priority than this alarm. The MOH allocation can also fail due to codec mismatch or capability mismatch between the endpoint and the MOH server. If there is a codec mismatch or capability mismatch (such as the endpoint using IPv6 addressing but MOH server supporting only IPv4), an MTP or transcoder should be allocated. If the MTP or transcoder is not allocated, either MediaResourceListExhausted (with Media Resource Type as media termination point or transcoder) or MtpNoMoreResourcesAvailable alarm will be generated for the same Media Resource Group List and you should first concentrate on that alarm. The MOH allocation may even fail after checking the region bandwidth between the regions to which the held party belongs and the region to which the MOH server belongs. Increasing the region bandwidth may be a solution to the problem, but that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, the average number of calls using the MOH servers, approximate bandwidth use per call, and so on, and accordingly calculate the region bandwidth. Another possible cause is that the bandwidth needed for the call may not be available. This can occur if the MOH server and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, please note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth. Another reason for the MOH allocation failure may be due to meeting the maximum number of unicast or multicast streams supported by the MOH server. If all available streams are already in use, none can be allocated. Finally, check the Music On Hold Audio Source Configuration window in Cisco Unified CM Administration to confirm that at least one audio source is configured. If an audio source is not configured, upload an audio file and then configure the audio source in Cisco Unified CM Administration (refer to the Music On Hold configuration documentation for specific details).
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-ConferenceNoMoreResourcesAvailable : Conference resource allocation failed Media Resource List Name [String]
Explanation Conference resource allocation failed for one or more of the following reasons: The required number of conference resources were not available; For an IOS-based conference bridge, the number of participants to be added to the conference bridge exceeded the maximum number of participants allowed per conference; No lower precedence conference was available for preemption although MLPP preemption was enabled; A lower-precedence conference bridge was not preempted
Recommended Action For IOS-based conference bridges, make sure that the maximum number of participants configured in a conference bridge does not exceed the number of participants allowed per conference; please check the IOS-based conference bridge user manual for limitations on the number of participants. Also, be sure to educate end users about the maximum number of participants allowed. For IOS-based and non-IOS-based, consider installing additional conference resources.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-AnnunciatorNoMoreResourcesAvailable : Annunciator resource allocation failed Media Resource List Name [String]
Explanation Annunciator resource allocation failed for one or more of the following reasons: All Annunciator resources are already in use; There was a codec or capability mismatch (such as the endpoint using one type of IP addressing such as IPv6, while the Annunciator supports only IPv4) between the endpoint and the Annunciator resource; Not enough bandwidth existed between the endpoint and the Annunciator.
Recommended Action If all the resources of the Annunciator are already in use, check to be sure that all the Annunciators that belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are configured and registered in all the applicable Unified CM nodes of the cluster. To check the registration status go to Media Resources > Annunciator and click the Find button. It will display all the Annunciators with their status, device pool, and so on. Check the status field to see whether it is registered with Unified CM. Note that the display on the status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified CM cluster that the Publisher can only write to the Unified CM database before the Publisher goes down. Because the Subscriber may not be able to write to the database, the devices may still display registered in Unified CM Administration after they are actually unregistered. However, if the Publisher is down that should generate another alarm with higher priority than this alarm. The Annunciator allocation can fail due to codec mismatch or capability mismatch between the endpoint and the Annunciator. If there is a codec mismatch or capability mismatch (such as the endpoint using IPv6 addressing but Annunciator supporting only IPv4), an MTP or transcoder should be allocated. If the MTP or transcoder is not allocated, either MediaResourceListExhausted (with Media Resource Type as media termination point or transcoder) or MtpNoMoreResourcesAvailable alarm will be generated for the same Media Resource Group List and you should first concentrate on that. The Annunciator allocation may even fail after checking the region bandwidth between the regions to which the held party belongs and the region to which the Annunciator belongs. Increasing the region bandwidth may be a solution to the problem, but that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, the average number of calls using the Annunciator, approximate bandwidth use per call, and so on, and accordingly calculate the region bandwidth. Another possible cause is that the bandwidth needed for the call may not be available. This can happen if the Annunciator and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-RsvpNoMoreResourcesAvailable : RSVP Agent resource allocation failed Media Resource List Name [String]
Explanation This alarm occurs when allocation of an RSVP Agent fails for all the registered RSVP Agents (RSVP Agents are basically MTPs or transcoder devices which provide RSVP functionalities) belonging to the Media Resource Group List and Default List. Each RSVP Agent may fail for different reasons. Following are some of the reasons that could cause an RSVP Agent allocation to fail: Available MTP/transcoders do not support RSVP functionality; A capability mismatch between the device endpoint and MTP/transcoder, Codec mismatch between the endpoint and the MTP/transcoder; A lack of available bandwidth between the endpoint and the MTP/transcoder; Or because the MTP/transcoder resources are already in use. A capability mismatch may be due to the MTP/transcoder not supporting one or more of the required capabilities for the call such as Transfer Relay Point (which is needed for QoS or firewall traversal), RFC 2833 DTMF (which is necessary when one side of the call does not support RFC 2833 format for transmitting DTMF digits and the other side must receive the DTMF digits in RFC 2833 format, resulting in conversion of the DTMF digits), RFC 2833 DTMF passthrough (in this case, the MTP or transcoder does not need to convert the DTMF digits from one format to another format but it needs to receive DTMF digits from one endpoint and transmit them to the other endpoint without performing any modifications), passthrough (where no codec conversion will occur, meaning the media device will receive media streams in any codec format and transmit them to the other side without performing any codec conversion), IPv4 to IPv6 conversion (when one side of the call supports only IPv4 and the other side of the call supports only IPv6 and so MTP needs to be inserted to perform the necessary conversion between IPv4 and IPv6 packets), or multimedia capability (if a call involving video and/or data in addition to audio requires insertion of an MTP or transcoder then the MTP/transcoder which supports multimedia will be inserted).
Recommended Action RSVP Agents are basically Cisco IOS MTPs or transcoder devices which provide RSVP functionalities. Check the user manual of the configured MTPs and transcoders to see whether they support RSVP functionality. If none of them support RSVP functionality either they need to be upgraded (if an upgraded version supports RSVP functionality) or additional MTP or transcoders need to be installed which support RSVP functionality. If the RSVP Agent (MTP or transcoder) allocation is failing due to a capability mismatch, it's possible that the media device does not support the requested capability (such as IPv4 to IPv6 conversion, passthrough) or the capability might not be configured in the device. Please check the user guide and documentation of the media device to make sure that device supports all the necessary capabilities. Also, caution should be taken if all the MTP or transcoders are configured with all the supported capabilities. There are certain capabilities (such as RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough) which could be supported by most of the MTPs or transcoders and there may be certain capabilities (such as IPv4 to IPv6 conversion and vice versa or RSVP Agent functionality or Transfer Relay Point or multimedia capability) which can be supported by only by a single MTP or transcoder depending on the devices that you have. For example, you may have end devices belonging to different locations and may need to reserve the bandwidth only between two locations; calls between other locations may not need to reserve the bandwidth. Now, suppose all the MTPs or transcoders are configured with all the supported capabilities and only one MTP/transcoder supports RSVP functionality; if this MTP/transcoder is configured with all the supported capabilities (which all the other MTPs or transcoders in the same MRGL or default MRGL also support) it may happen that this MTP can get allocated for Transfer Relay Point or RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough instead. As a result, when a need arises to reserve the bandwidth (which other MTPs or transcoders in the same MRGL or default MRGL do not support), all the resources of this MTP/transcoder may be in use and the RSVP Agent allocation may fail. To avoid this situation, set the priority of the media resources appropriately. This can only be done in the Media Resource Group List and not in the Default List of the media resources. In any Media Resource Group List all the Media Resource Groups have different priorities and during allocation the first Media Resource Group is checked for availability of the requested type of the media devices. The first Media Resource Group in the Media Resource Group List will have the highest priority, then the second one and so on. To check all the Media Resource Groups and their priority go the Media Resources and Media Resource Group List in Cisco Unified CM Administration and click the appropriate Media Resource Group List, then check the Selected Media Resource Groups; the priority decreases from top to bottom. Position the MTP or transcoder that you want to be selected for the basic functionalities in the higher priority Media Resource Groups whereas the ones with more rare functionality can be positioned in the Media Resource Groups with lower priority. RSVP Agent allocation may fail due to codec mismatch between the endpoint and the RSVP Agent or MTP/transcoder. A solution may be to configure the MTP/transcoder with all the supported codecs (as specified in the user guide of the MTP/transcoder), but be aware that doing so might result in too much bandwidth being allocated for calls. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, approximate bandwidth use per call (not involving MTP/transcoder), and so on, and accordingly calculate the maximum bandwidth that can be allocated per call involving an MTP/transcoder and take that into consideration when configuring the supported codecs in the MTPs and transcoders. A good idea is to configure the media devices with all the supported codecs and set the region bandwidths to restrict too much bandwidth usage (refer to the Unified CM documentation for details on region and location settings). Also, there may be a codec mismatch between the endpoint and the MTP/transcoders after considering the region bandwidth between the MTP/transcoder and the endpoint. Increasing the region bandwidth may be a solution to the problem, but that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions. Another possible cause that an MTP/transcoder did not get allocated is because there was not enough available bandwidth for the call. This can happen if the MTP/transcoder and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the 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
CCM_CALLMANAGER-CALLMANAGER-2-MaxCallsReached : Maximum calls of simultaneous calls in this node has been reached Description [Int]
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
CCM_CALLMANAGER-CALLMANAGER-1-DBLException : An error occurred while performing database activities ErrorCode [Int] ExceptionString [String]
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
CCM_CALLMANAGER-CALLMANAGER-3-ICTCallThrottlingStart : Unified CM stops handling calls for the indicated H.323 device due to heavy traffic or a route loop over the H.323 trunk Device Name [String] IP Address [String] Device type [Enum]Device description [String]
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 to 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
CCM_CALLMANAGER-CALLMANAGER-5-ICTCallThrottlingEnd : Unified CM starts handling calls again for the indicated H.323 device Device Name [String] IP Address [String] Device type [Enum]Device description [String]
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
CCM_CALLMANAGER-CALLMANAGER-2-CodeYellowEntry : Unified CM has entered Code Yellow state Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Total Code Yellow Entry [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]
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
CCM_CALLMANAGER-CALLMANAGER-5-CodeYellowExit : Unified CM has exited Code Yellow Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Time Spent in Code Yellow [UInt] Number of Calls Rejected Due to Call Throttling [UInt] Total Code Yellow Exit [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]
Explanation Unified CM has ceased throttling calls and has exited the Code Yellow state
Recommended Action Notification purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-CodeRedEntry : Unified CM has entered Code Red condition and will restart Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Code Yellow Duration [UInt] Number of Calls Rejected Due to Call Throttling [UInt] Total Code Yellow Entry [UInt] Total Code Yellow Exit [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]
Explanation Unified CM has been in Code Yellow state for an extended period and is unlikely to recover on its own. The Cisco CallManager service automatically restarts in an attempt to clear the condition that is causing the Code Yellow state. The amount of time that the system will remain in Code Yellow state is configurable in the Code Yellow Duration service parameter. If the duration of this parameter is set to 99999, Code Red condition will never occur.
Recommended Action Make certain that you have attempted the steps in the recommended actions defined in the CodeYellowEntry alarm. If you have not, try those after the system is online. There is no other action for Code Red because the only action is to restart which occurs automatically.
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-SignalCongestionEntry : Unified CM has detected signal congestion in an internal thread and has throttled activities for that thread Thread [String] Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Total Signal Congestion Entry [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]
Explanation Unified CM has initiated throttling for an internal thread due to unacceptably high delay in handling signals
Recommended Action Memory problems or high CPU usage are generally at the root of signal congestion. 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 the signal congestion. 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 SignalCongestionExit alarm is not issued in a reasonable amount of time as deemed by your organization, or if the system is frequently triggering the SignalCongestionEntry alarm, contact the Cisco Technical Assistance Center (TAC) and supply the trace information you have collected.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-SignalCongestionExit : Unified CM has exited throttling caused by a previous signal congestion condition Thread [String] Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Time Spent in Signal Congestion [UInt] Number of Calls Rejected Due to Call Throttling [UInt] Total Signal Congestion Exit [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]
Explanation Unified CM has exited the throttling state caused by signal congestion on a threaded process within Unified CM
Recommended Action Notification purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DeviceCloseMaxEventsExceeded : The TCP socket for the SCCP device has been closed due to excessive events in a 5-second period; under normal conditions, the device will reregister automatically Total Events Received [UInt] IP Address [String] TCP Handle [String] Max Events Allowed [UInt] Number of SCCP Devices Throttled [UInt]
Explanation The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage.
Recommended Action Check the CCM trace data for the indicated SCCP device to determine the reason for the high number of events. Confirm that the value configured in the Cisco CallManager service parameter, Max Events Allowed, is a suitable number for your deployment.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-MaliciousCall : A malicious call has been identified Called Party Number [String] Called Device Name [String] Called Display Name [String] Calling Party Number [String] Calling Device Name [String] Calling Display Name [String]
Explanation A user presses the MCID softkey to alert you that the call indicated in this alarm contained disturbing content. This is not to indicate a voice quality issue on the call but to alert you to a potentially abusive or offensive occurrence involving the calling party device.
Recommended Action After a user presses the MCID softkey, the MCID service flags the call detail record (CDR) with the MCID notice and sends a notification to the PSTN that a malicious call is in progress. Take appropriate action as defined by your company policy regarding disturbing/abusive calls.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-BeginThrottlingCallListBLFSubscriptions : Unified CM has initiated throttling of CallList BLF subscriptions as a preventive measure to avoid overloading the system Active External Presence Subscriptions [UInt] CallList BLF Subscriptions Throttling Threshold [UInt] CallList BLF Subscriptions Resume Threshold [UInt] Total Begin Throttling CallList BLF Subscriptions [UInt]
Explanation Unified CM has initiated throttling of Call List BLF subscriptions as a preventive measure to avoid overloading the system. This alarm occurs when the total number of active BLF subscriptions exceeds the configured limit set by the Presence Subscription Throttling Threshold service parameter.
Recommended Action Determine if CPU and memory resources are available to meet the higher demand for CallList BLF subscriptions. If so, increase the value in the Cisco CallManager service parameter Presence Subscription Throttling Threshold and correspondingly reduce the value in the Presence Subscription Resume Threshold service parameter. If you do not have sufficient CPU and memory resources to increase the throttling threshold value, evaluate a plan to increase system resources to meet the demand.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-EndThrottlingCallListBLFSubscriptions : EndThrottlingCallListBLFSubscriptions Active External Presence Subscriptions [UInt] CallList BLF Subscriptions Throttling Threshold [UInt] CallList BLF Subscriptions Resume Threshold [UInt] Time Duration Of Throttling CallList BLF Subscriptions [UInt] Number of CallList BLF Subscriptions Rejected Due To Throttling [UInt] Total End Throttling CallList BLF Subscriptions [UInt]
Explanation Unified CM has resumed accepting CallList BLF subscriptions subsequent to prior throttling
Recommended Action Notification purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-PktCapServiceStarted : Packet capture service has started
Explanation The packet capture feature has been enabled on the Unified CM server. A Cisco CallManager service parameter, Packet Capture Enable, must be set to True for packet capture to occur.
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-PktCapServiceStopped : Packet capture service has stopped
Explanation The packet capture feature has been disabled in Unified CM
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-PktCapOnDeviceStarted : Packet capture has started on the device Device Name [String] Packet Capture Mode [String] Packet Capture Duration [String]
Explanation Packet capture has been enabled on the device indicated in this alarm
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-PktCapOnDeviceStopped : Packet capture stopped on the device Device Name [String] Packet Capture Mode [String] Packet Capture Duration [String]
Explanation Packet capture has been disabled on the indicated device
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-UserUserPrecedenceAlarm : User-to-User Precedence passing violation Device Name [String] Reason Code [Enum]
Explanation User-to-User IE was not successfully tunneled to destination; please refer to reason code for additional details
Recommended Action Refer to the information (help text) in the reason code in this alarm for detailed actions
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 2 |
HopCountExceeded - The hop count field in passing User-to-User IE exceeded the maximum value of 10. The reason could be the presence of routing loops across the Unified CM trunk interfaces (PRI, intercluster trunk, and so on). The recommended action is to check that no routing loops exist across the Unified CM trunk interfaces (PRI, intercluster trunk, and so on) and gateway (H.323) devices related to the indicated failed call. By examining trace files and CDR data in all Unified CM nodes and route patterns in gateways (H.323) that are involved in routing of the indicated failed call, 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, and then if the looping route pattern was on a Unified CM, reset the affected route list/pattern in an attempt to clear the route loop; if that fails, reset the affected trunk/gateway or if the looping route pattern was on an H.323 gateway, restart the gateway. |
| 3 |
UserUserIEDropped - The passing UserUserIE is dropped. If the indicated device is an H.323 intercluster trunk then the possible reason could be that the Passing Precedence Level Through UUIE checkbox in the Trunk Configuration window in Unified CM is not enabled; the recommended action is to verify that the Passing Precedence Level Through UUIE checkbox has been enabled. If the indicated device is an MGCP gateway with Device Protocol set to Digital Access PRI, the possible reason could be that in the incoming UUIE message, either the IE ID is not set to USER_USER_IE (126) or the User specific protocol ID value is not set to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00); the recommended action is to verify that the far-end side of the configured PRI trunk interface supports PRI 4ESS UUIE-based MLPP and sends the UUIE message with IEID value set to USER_USER_IE (126) and the User specific protocol ID value is set to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00). |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-MultipleSIPTrunksToSamePeerAndLocalPort : A conflict occurred because multiple trunks have been configured to the same destination and local port Peer IP Address [String] Local IP Port [UInt] Old Device name [String] Old Device Instance [String] New Device name [String] New Device Instance [String]
Explanation Multiple trunks have been configured to the same destination and local port, which resulted in a conflict. Only one trunk is allowed for one destination/local port combination. The new trunk invalidated the old trunk.
Recommended Action Check the SIP Trunk Configuration in Cisco Unified CM Administration and ensure that only one SIP trunk is configured to the same destination address and local port
Error Message
CCM_CALLMANAGER-CALLMANAGER-0-NoFeatureLicense : No feature license found
Explanation Unified CM requires a license to function. Also, Unified CM licenses are version-specific so be certain that the license is for the version you are trying to run. You can run a license unit report in Cisco Unified CM Administration (System > Licensing > License Unit Report).
Recommended Action Request license generation for Cisco Unified Communications Manager SW FEATURE for your version of Unified CM and upload the license in Cisco Unified CM Administration (System > Licensing > License File Upload)
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-CMInitializationStateTime : Indicates the amount of time it took for Unified CM to initialize each state in the initialization process Initialization State [String] Initialization Time [String] Initialization Time in Milliseconds [UInt]
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
CCM_CALLMANAGER-CALLMANAGER-6-CMTotalInitializationStateTime : Total amount of time it took for Unified CM to complete initialization Total Initialization Time [String] Total Initialization Time in Milliseconds [UInt]
Explanation Indicates the amount of time required to complete the total system initialization
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-1-CMOverallInitTimeExceeded : 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 Cisco Unified Communications Manager Overall Initialization Time (in minutes) [Int]
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
CCM_CALLMANAGER-CALLMANAGER-4-DigitAnalysisTimeoutAwaitingResponse : Unified CM sent a routing request to the policy decision point but the request timed out without a response Translation Pattern Triggering Point [String] Policy Decision Point [String]
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).
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-InvalidIPNetPattern : An invalid IP address is configured in one or more SIP route patterns in Cisco Unified CM Administration Description [String] IPAddress [String] DeviceName [String]
Explanation An invalid IP address is configured in one or more SIP route patterns in Cisco Unified CM Administration
Recommended Action In Cisco Unified CM Administration, verify that the route pattern associated with the device that is identified in this alarm has an accurate and working IP address. You can learn more how to ensure that the IP address is valid by reviewing RFC 2373.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-FailedToFulfillDirectiveFromPDP : Unified CM cannot fulfill the call routing directive returned by the policy decision point Policy Decision Point [String] Reason, Unified CM failed to fulfill the directive [String] Called Party Number [String] Calling Party Number [String] Calling User ID [String]
Explanation A routing directive from the policy decision point (PDP) cannot be fulfilled. This could occur because the call was cleared by a CTI application before Unified CM was able to route it to the location defined by the PDP; because a call that was allowed by a policy server was redirected by the CTI application to a destination; because the annunciator ID was misconfigured in the PDP; or because Unified CM attempted to invoke a media resource such as Annunciator but no resources were available.
Recommended Action In many cases, a failure to fulfill a routing directive occurs because of intervention by a CTI application which scoops up the call before Unified CM is able to fulfill the routing directive in the PDP. If CTI interaction is having a negative effect, examine the CTI application to ensure that the call is in alerting or connected state before CTI begins to interact with the call. If the failure is caused by a problem with the annunciator ID, check to be sure the ID has been accurately configured in the PDP and that it exists in Unified CM Administration. If the failure was caused by a lack of media resources, try increasing the Annunciator Call Count service parameter in the Cisco IP Voice Media Streaming App service.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-FailureResponseFromPDP : The policy decision point returned a 4xx (client) or 5xx (server) status code in the HTTP response Policy Decision Point URL [String] The status code and reason phrase for the failure [String]
Explanation Unified CM received a 4xx or 5xx response from the policy decision point (PDP). A 4xx response indicates errors in the call routing request from Unified CM, for example: a 400 response indicates the call routing request could not be understood by the PDP; a 404 indicates that the PDP did not find a matching request URI. A 5xx error indicates a PDP server error, for example: a 500 response indicates a PDP internal error; a 501 response indicates that the PDP does not support the functionality to generate a call routing response; a 503 indicates that the PDP is busy and temporarily cannot generate a response; a 505 indicates that the HTTP version number included in the call routing request from Unified CM is not supported. Other such errors may be responsible; please refer to generally available guidelines on HTTP or check RFC 2616 for detailed explanations about HTTP Status Code definitions.
Recommended Action If a 4xx response caused the alarm, verify that the PDP has been accurately configured for the functionality and call routing that you expect it to perform. If a 500 response causes the alarm, check whether the PDP service is active and check the PDP server's log files for any errors. If a 503 causes the alarm, the PDP may be overloaded by requests. Take appropriate action to reduce the load on the PDP by following some or all of these recommendations: 1) consider adding more PDPs and provisioning Unified CM with additional external call control profiles and external call control trigger points in the various configuration pages under the Call Routing menu in Cisco Unified CM Administration; 2) provision a pair of policy servers per external call control profile to enable load balancing; or 3) verify that the PDP server in your deployment meets or exceed the hardware requirements specified in the documentation for Cisco Enterprise Policy Manager (CEPM) or the third-party PDP solution you have deployed. If a 505 response causes the alarm, check to be sure that the PDP supports HTTP version 1.1.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-ConnectionFailureToPDP : A connection request from Unified CM to the policy decision point failed Policy Decision Point [String] The cause of the connection failure [String]
Explanation A connection request to the policy decision point (PDP) failed. Failure may have been due to a network error causing limited or no connectivity between Unified CM and the PDP; because of authentication errors when Unified CM established an HTTPS connection to the PDP; or because the PDP was not in service.
Recommended Action Verify that network connectivity exists between Unified CM and the PDP by pinging the policy server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost. If the connection failure is due to an authentication problem, verify that the valid certificate of the PDP has been imported to Cisco Unified OS Administration and certificates from every node in the Unified CM cluster have been imported to every node in the PDP. Also, make sure that the PDP service is active.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-ConnectionToPDPInService : A connection was successfully established between Unified CM and the policy decision point Policy Decision Point [String]
Explanation A successful connection from Unified CM to the policy decision point (PDP) has been established
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-AwaitingResponseFromPDPTimeout : Unified CM timed out waiting for the routing response from the policy decision point Policy Decision Point [String]
Explanation Unified CM did not receive a call routing response from the policy decision point (PDP) within the time specified by either the Cisco CallManager service parameter, Call Intercept Routing Request Timer, or on the Call Intercept Profile Configuration window in Cisco Unified CM Administration.
Recommended Action Check whether the PDP is in service and working normally. Verify that the PDP is not overloaded; if it is, take appropriate action to reduce the load on the PDP by following some or all of these recommendations: 1) consider adding more PDPs and provisioning Unified CM with additional call intercept profiles and call intercept trigger points in the various configuration pages under the Call Routing menu in Cisco Unified CM Administration; 2) provision a pair of policy servers per call-intercept profile to enable load balancing; or 3) verify that the PDP server in your deployment meets or exceed the hardware requirements specified in the documentation for Cisco Enterprise Policy Manager (CEPM) or the third-party PDP solution you have deployed. If necessary, increase the value in the Cisco CallManager service parameter, Call Intercept Routing Request Timer or the value in the Call Intercept Profile for this PDP.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-ErrorParsingDirectiveFromPDP : Unified CM failed to parse the call routing directive or the diversion destination in the call routing response from the policy decision point Policy Decision Point [String] Called Party Number [String] Calling Party Number [String] Calling User ID [String] Response XML Data [String]
Explanation A routing response was received but Unified CM failed to parse the mandatory elements in the response. This means that a call routing directive or the call diversion destination could not be parsed correctly, or that the call routing directive was not recognized. The error may due to a syntax error or because the call routing directive is missing or the call diversion destination is missing in the call routing response.
Recommended Action Check the external call control documentation, including any applicable API documentation, to determine whether the call routing directive that was included as part of the policy obligations in the call routing response are correctly entered according to the information defined in the external call control documentation.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-ErrorParsingResponseFromPDP : Unified CM failed to parse one or multiple optional elements or attributes in the call routing response from the policy decision point Policy Decision Point [String] Called Party Number [String] Calling Party Number [String] Calling User ID [String] Request XML Data [String]
Explanation A routing response was received from the policy decision point (PDP) but Unified CM failed to parse the optional elements in the response. Optional elements may include modified calling numbers or called numbers, call reject or call diversion reasons, and so on. The cause may be a syntax error or missing attributes in the call routing response.
Recommended Action Confirm that the call routing response from the policy decision point complies with the guidelines specified for external call control in the Cisco Unified Communications Manager documentation. Confirm that any optional elements included as the policy obligations in the call routing response are correctly entered according to the external call control documentation, including any applicable API documentation.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-CallAttemptBlockedByPolicy : A call was attempted but blocked or rejected by the policy decision point Policy Decision Point [String] Reject Reason [String] Called Party Number [String] Calling Party Number [String] Calling User ID [String]
Explanation A call was rejected or blocked because it violated the enterprise policy as defined in a policy decision point (PDP) that was configured in Unified CM. The policy server returns a call reject decision stating that a policy violation was the reason for rejecting the call. Calls may be rejected because an unauthorized user attempted to dial a DN or pattern that is not allowed for him or her or because a call forward directive was invoked and the destination specified in the call forward operation violated the policy. Depending on email configuration in Real-Time Monitoring Tool (RTMT), the system may have generated an email alert when the call was rejected.
Recommended Action Evaluate the information provided in this alarm (caller's user ID, to and from DNs, and so on) to determine if the call attempt was an innocent mistake to dial a number that the user didn't realize was not routable for him or her, or to discover whether the user is intentionally trying to circumvent the policy restrictions. If the rejected call was caused by an innocent mistake, educate the affected user about the numbers that he or she is allowed to dial. Your organization may have a policy or guidelines to follow when investigating call rejects. In addition to or instead of the steps recommended here, please refer to your company's guidelines.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-ServicePortOnline : A Cisco CallManager service port is online Protocol [String] Port Number [UInt]
Explanation Unified CM has successfully opened a socket port to provide service
Recommended Action Notification purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-ServicePortOffline : A Unified CM service port is offline Protocol [String] Port Number [UInt] Error Number [Int]
Explanation A Unified CM socket port that is used to provide service has unexpectedly closed; Unified CM will attempt to reopen this port. Normally, this port should never be closed. An unexpected closing of this port generally indicates an operating system failure or an external attack on Unified CM.
Recommended Action Verify that Unified CM is able to reopen this socket port and provide service. You can watch for an instance of the notice level alarm, ServicePortOnline, when service to the port has been restored. If the port is not reopened and service restored, restart the Cisco CallManager service. If this alarm occurs for an extended duration, collect the existing trace files and contact the Cisco Technical Assistance Center (TAC).
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-SuspiciousIPAddress : Unified CM has identified suspicious connection attempts from an IP address Port Number [UInt] IP Address [String]
Explanation Unified CM has identified suspicious connection attempts from an IP address and has temporarily blocked the address. This alarm is an indication that a Denial-of-Service attack may have been attempted from this IP address.
Recommended Action Examine network activity for repeated attempts to access the port number specified in this alarm. Using the IP address specified in this alarm, attempt to identify the device that has been sending connection attempts to the port. If the IP address belongs to a device that is configured in Unified CM, evaluate the possible reason for such numerous connection attempts. Generally, no device that is functioning properly will trigger this alarm. Reset the device or remove the device from the network.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-LostConnectionToSAFForwarder : Connection to the SAF Forwarder has been lost IP Address [String] SafClientHandle [UInt]
Explanation A TCP connection failure caused the connection between the SAF Forwarder and Unified CM to be lost. When the TCP connection is restored, Unified CM attempts to connect to the SAF Forwarder automatically. If IP connectivity is unreachable for longer than the duration of the Cisco CallManager service parameter CCD Learned Pattern IP Reachable Duration, calls to learned patterns will be routed through the PSTN instead. Calls through the PSTN to learned patterns will be maintained for a certain period of time before the PSTN failover times out.
Recommended Action Investigate possible causes of a TCP connection failure, such as power failure, loose cables, incorrect switch configuration, and so on, and correct any issues that you find. After the connection is restored, CCD will try to register/sync with the SAF Forwarder automatically.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-SAFForwarderError : SAF Forwarder error response sent to Unified CM IP Address [String] SafClientHandle [UInt] Application User Name [String] Reason Code and Description [Enum]SAF Protocol Version Number [String] Service ID [UInt] Sub Service ID [UInt]
Explanation Unified CM received an error from the SAF Forwarder
Recommended Action Refer to the reason code and description (help text) for specific information and actions (where applicable) for this alarm
Reason Code - Enum Definitions
Enum Definitions - ReasonCode
| Value |
Definition |
| 400 |
SAF_BAD_REQUEST - SAF Forwarder was unable to accept the request due to incorrect syntax (malformed), missing required attributes, and other similar reasons. Investigate the configuration between the SAF Forwarder and Unified CM to be certain that all settings are correct for your deployment. In particular, check the Client Label configured on the router to make certain that it matches the Client Label configured in Cisco Unified CM Administration on the SAF Forwarder Configuration window (SAF > SAF Forwarder). |
| 431 |
SAF_INTEGRITY_CHECK_FAILURE - A message failed to pass SAF Forwarder security validation. This can occur because of misconfiguration, a potential attack, or more commonly by incorrect provisioning of the password on the Forwarder and SAF client. Reprovision the password and keep a watch on further SAF INTEGRITY CHECK FAILURE alarms. If you receive a persistent number of SAF INTEGRITY CHECK FAILURE alarms, close the interface between SAF Forwarder and Unified CM and investigate the source of the IP packets. |
| 435 |
**INFO LEVEL** SAF_MISSING_NONCE - A nonce (a random parameter generated when the message is sent) is missing from the message. The system will resend with a new nonce automatically. No action is required. |
| 436 |
SAF_UNKNOWN_USERNAME - Unified CM sent the SAF Forwarder an Application User name that is not configured on the router or that does not match the router's configuration. Check the Application User Name on the router and in the Application User Configuration window in Cisco Unified CM Administration to be sure they match. |
| 438 |
**INFO LEVEL** SAF_STALE_NONCE - A nonce (a random parameter generated when the message is sent) has aged out (gone stale). The system will resend with a new nonce automatically. No action is required. |
| 471 |
**INFO LEVEL** SAF_BAD_CLIENT_HANDLE - SAF_BAD_CLIENT_HANDLE - Unified CM sent the SAF Forwarder a Register message (for KeepAlive purposes) or unregister message with the mandatory CLIENT_HANDLE value, but the SAF Forwarder did not recognize the client handle. Unified CM will attempt to reregister with the SAF Forwarder without a client handle. This alarm is for informational purposes only; no action is required. |
| 472 |
**INFO LEVEL** SAF_VERSION_NUMBER_TOO_LOW - Unified CM published a service (such as Hosted DN) whose version number is now lower than when it was previously published to the SAF Forwarder. The service is out of sync with the SAF Forwarder. Unified CM will republish the service in an attempt to resynch with the SAF Forwarder. This alarm is for informational purposes only; no action is required. |
| 473 |
**INFO LEVEL** SAF_UNKNOWN_SERVICE - Unified CM attempted to unpublish a service from the SAF network but the SAF Forwarder does not have a publish record for that service. This alarm is for informational purposes only; no action is required. |
| 474 |
**INFO LEVEL** SAF_UNREGISTERED - Unified CM attempted to publish or subscribe to the SAF Forwarder, but Unified CM is not registered with SAF Forwarder. Unified CM will automatically reregister with the SAF Forwarder before attempting to publish or subscribe. This alarm is for informational purposes only; no action is required. |
| 475 |
**INFO LEVEL** SAF_BAD_FILTER - Unified CM attempted to subscribe to the SAF Forwarder with a filter that does not match any of the SAF Forwarder's current filters. Unified CM will resend the subscribe message with the appropriate filter value. This alarm is for informational purposes only; no action is required. |
| 476 |
SAF_UNKNOWN_SUBSCRIPTION - Unified CM sent a subscribe or unsubscribe message to the SAF Forwarder but the message contained a Service ID that was not familiar to the SAF Forwarder. Without a recognized Service ID, Unified CM cannot subscribe to the SAF Forwarder. Recommended action is to contact the Cisco Technical Assistance Center (TAC). |
| 477 |
**INFO LEVEL** SAF_ALREADY_REGISTERED - Unified CM attempted to register with the SAF Forwarder but SAF Forwarder indicates that Unified CM is already registered. Unified CM will close and reopen the TCP connection and send a new register request without a client handle to SAF Forwarder. This alarm is for informational purposes only; no action is required. |
| 478 |
SAF_UNSUPPORTED_PROTOCOL_VERSION - Unified CM attempted to register with the SAF Forwarder using a SAF protocol version number that is greater than the protocol version number supported by the SAF Forwarder. Issue a show version command on the SAF Forwarder CLI to determine the SAF Forwarder protocol version; refer to the information in this alarmfor the SAF protocol version number. If the versions do not match, check the Cisco Unified Communications Manager Software Compatibility Matrix (available on Cisco.com) to determine whether the SAF protocol version number that is in use on this Unified CM is compatible with the SAF Forwarder protocol version. If it is not, upgrade the lower-versioned component so that both Unified CM and the SAF Forwarder use the same, compatible version. |
| 479 |
SAF_UNKNOWN_AS - Unified CM attempted to register to the SAF Forwarder but the registration message contained a Client Label that was not familiar to the Autonomous System (AS) on the SAF Forwarder router. Recommended action is to issue the appropriate CLI commands on the SAF Forwarder to associate the Client Label with the autonomous system on the router (refer to the Configuration Guide for the router) and configure the same Client Label in the Client Label field on the SAF Forwarder Configuration window in Cisco Unified CM Administration and click Save. When the Client Label is saved in Cisco Unified CM Administration, Unified CM automatically sends a new registration request to the SAF Forwarder with the updated Client Label information. |
| 500 |
**INFO LEVEL** SAF_RESPONDER_ERROR - Unified CM sent a message (such as register/unregister/publish/unpublish/subscribe) to the SAF Forwarder but the SAF Forwarder responded that it is unable to process the message at this time. This might be due to heavy message queuing, internal resource issues, and so on. Unified CM will wait several seconds and then retry the request. This alarm is for informational purposes only; no action is required. |
| 1000 |
SAF_INVALID_CONNECTION_DETAILS") |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-SAFUnknownService : Unified CM does not recognize the service ID in a Publish Revoke or Withdraw message Client Handle [String] Service ID [UInt] Sub Service ID [UInt] InstanceID1 [UInt] InstancID2 [UInt] InstanceID3 [UInt] InstanceID4 [UInt]
Explanation Unified CM received a Publish Revoke message or Withdraw message from the SAF Forwarder but the service ID in the message is not recognized by Unified CM. Unified CM may not recognize the service ID if the service ID was mistyped in the Publish Revoke CLI command, or if the service was previously withdrawn.
Recommended Action This alarm is for informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-SAFPublishRevoke : A CLI command revoked the publish action for the specified service or subservice ID Client Handle [String] Service ID [UInt] Sub Service ID [UInt] InstanceID1 [UInt] InstancID2 [UInt] InstanceID3 [UInt] InstanceID4 [UInt]
Explanation A system administrator issued a CLI command on the SAF Forwarder router to revoke the publish action for the service or subservice ID specified in this alarm
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-SAFResponderError : SAF Responder Error 500 Client Handle [String] Service Id [UInt] Sub Service ID [UInt] Instance ID1 [UInt] Instance ID2 [UInt] Instance ID3 [UInt] Instance ID4 [UInt]
Explanation This is raised when SAF forwarder doesn't know the transaction ID within SAF response from this Unified CM
Recommended Action No action is required
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DuplicateLearnedPattern : CCD requesting service received a duplicate Hosted DN Client Handle [String] Service ID [UInt] Sub Service ID [UInt] InstanceID1 [UInt] InstancID2 [UInt] InstanceID3 [UInt] InstanceID4 [UInt]
Explanation The Call Control Discovery (CCD) requesting service received the same hosted DN from multiple call control entities such as Unified CM Express or another Unified CM cluster. The Cisco CallManager service parameter, Issue Alarm for Duplicate Learned Patterns, controls whether this alarm gets issued.
Recommended Action In RTMT, check the Pattern Report (CallManager > Report > Learned Pattern) and look for the duplicate pattern identified in this alarm. Learned patterns must be unique. Determine which call control entity (such as Unified CM or Unified CM Express) needs to be changed so that there is no duplicate pattern. Refer to the call control entity's configuration guide (help text) to learn how to update a hosted DN pattern. In Unified CM, to change the Hosted DN Pattern go to Cisco Unified CM Administration to update the Hosted DN Pattern configuration (Call Routing > Call Control Discovery > Hosted DN Patterns).
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-CCDIPReachableTimeOut : CCD Requesting Service IP Reachable Duration Time Out
Explanation The CCD requesting service detected that it can no longer reach the learned patterns through IP. All learned patterns from this forward will be marked as unreachable (via IP) and to allow calls to learned patterns to continue to be routed until IP becomes reachable again, all calls to learned patterns will be routed through the PSTN. Calls can be routed through the PSTN for a certain period of time before PSTN failover times out.
Recommended Action Check IP connectivity and resolve any TCP or IP problems in the network
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-CCDPSTNFailOverDurationTimeOut : The internal limit on PSTN failover has expired
Explanation When learned patterns are not reachable through IP, Unified CM routes calls through the PSTN instead. Calls can be routed through PSTN for an internally-controlled duration. When this alarm occurs, the PSTN failover duration has expired and calls to learned patterns cannot be routed. All learned patterns will be purged from Unified CM.
Recommended Action Troubleshoot your network to get IP connectivity restored. After IP connectivity is restored, Unified CM will automatically relearn Hosted DN patterns and calls to learned patterns will proceed through IP.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-CCDLearnedPatternLimitReached : CCD has reached the maximum number of learned patterns allowed CCD Maximum Numbers of Learned Patterns [UInt] System Limit of CCD Learned Patterns [UInt]
Explanation The CCD requesting service has limited the number of learned patterns to a number defined in the service parameter, CCD Maximum Numbers of Learned Patterns. This alarm inidcates that the CCD requesting service has met the maximum number of learned patterns allowed.
Recommended Action This alarm displays the value that is configured in the Cisco CallManager service parameter, CCD Maximum Numbers of Learned Patterns, as well as the maximum number of learned patterns that are allowed by the system (an internally-controlled maximum). Consider whether the specified maximum number of learned patterns is correct for your deployment. If it is too low, compare it with the number shown in the SystemLimitCCDLearnedPatterns in this alarm. If the Max number is below the System Limit, you can go to the Service Parameters Configuration window and increase the CCD Maximum Numbers of Learned Patterns service parameter. If the Max and System Limit numbers match, the system is already configured to run at capacity of learned patterns; no action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-DbInsertValidatedDIDFailure : The Insertion of an IME-provided E.164 DID has failed E.164 DID [String] Granting Domain [String]
Explanation A failure occurred attempting to insert a Cisco Unified Active Link learned DID
Recommended Action Verify the DID and the granting domain. Check other associated alarms. Verify the database integrity.
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-TCPSetupToIMEFailed : Connection Failure to IME server IP address [String] Port number [UInt]
Explanation This alarm occurs when Unified CM is unable to establish a TCP connection to an IME server. It typically occurs when the IP address and port of the IME server are misconfigured or an Intranet connectivity problem is preventing the connection from being set up.
Recommended Action Check to make sure that the IP address and port of the IME server - which are present in the alarm - are valid. If so, this may be due to a network connectivity problem. Test the connectivity between Unified CM servers and the IME server.
Error Message
CCM_CALLMANAGER-CALLMANAGER-1-TLSConnectionToIMEFailed : TLS Failure to IME service SSL Error Code [UInt] SSL Error Text [String]
Explanation A TLS connection to the IME server could not be established because of a problem with the certificate presented by the IME server. (For example, not in the Unified CM CTL, or is in the CTL but has expired).
Recommended Action Check to see that the certificate of the IME server is configured properly in the UCM.
Error Message
CCM_CALLMANAGER-CALLMANAGER-1-InvalidCredentials : Credential Failure to IME server User name [String] IP address [String] Server name [String]
Explanation The connection to the IME server could not be completed, because the username and/or password configured on Unified CM do not match those configured on the IME server
Recommended Action The alarm will include the username and password which were used to connect to the IME server, along with the IP address of the target IME server and its name. Log into the IME server and check that the username and password configured there match those configured in Unified CM.
Error Message
CCM_CALLMANAGER-CALLMANAGER-1-IMEOverQuota : IME over quota Server name [String] Current quota [UInt] Maximum target quota [UInt]
Explanation Each IME server has a fixed quota on the total number of DIDs it can write into the IME distributed cache. When this alarm is generated, it means that, across all of the Unified CM clusters which are utilizing the same IME server, the quota for the IME distributed cache has been exceeded.
Recommended Action The alarm will include the name of the IME server, and the current and target quota values. The first thing to check is to make sure that you have correctly provisioned the right set of DID prefixes on all of the Unified CM clusters sharing that same IME server. If that is correct, it means you have exceeded the capacity of your IME server, and you require another. Once you have another, you can now split your DID prefixes across two different IME client instances, each on a different IME server. That will alleviate the quota problem.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-PublishFailedOverQuota : Publish Failed - over Quota The DID for which the Publish was attempted [String] Server name [String] Current quota [UInt] Maximum target quota [UInt]
Explanation Each IME server has a fixed quota on the total number of DIDs it can write into the IME distributed cache. When this alarm is generated, it means that, even though you should be under quota, due to an extremely unlikely statistical anomaly, the IME distributed cache rejected your publication, believing you were over quota. You should only see this alarm if you are near, but below, your quota. This error is likely to be persistent, so that the corresponding E.164 number from the alarm will not be published into the IME distributed cache. This means that you will not receive VoIP calls towards that number - they will remain over the PSTN.
Recommended Action The alarm will include the name of the IME server, and the current and target quota values. The first thing to check is to make sure that you have correctly provisioned the right set of DID prefixes on all of the Unified CM clusters sharing that same IME server on the same IME distributed cache. If that is correct, it means you have exceeded the capacity of your IME server, and you require another. Once you have another, you can now split your DID prefixes across two different IME client instances, each on a different IME server. That will alleviate the quota problem.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-PublishFailed : Publish Failed DID [String]
Explanation Unified CM attempted to store a number into the IME distributed cache, but the attempt failed. This is typically due to a transient problem in the IME distributed cache. The problem will self-repair under normal conditions. However, you should be aware that, as a consequence of this failure, the E.164 DID listed as part of the alarm will not be present in the IME distributed cache for a brief interval. Consequently, this may delay the amount of time until which you will receive VoIP calls made to that number - they may continue over the PSTN for some callers. It is useful to be aware of this, in case you are trying to understand why a call is not being made over VoIP.
Recommended Action If you notice single small numbers of this alarm in isolation, no action is required on your part. However, a large number of them indicates a problem in the IME distributed cache, most likely due to problems with Internet connectivity. Check your Internet connectivity.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-IMEDistributedCacheInactive : Inactive IME distributed cache
Explanation This alarm is generated when Unified CM attempts to connect to the IME server, however, the IME distributed cache is not currently active
Recommended Action Check to make sure that the IME certificate is provisioned on the IME server. Check to make sure that the IME distributed cache has been activated via the CLI on the IME server.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-RejectedRoutes : Rejected route due to Untrusted status Domain name [String] Phone number [String]
Explanation This alarm is generated when Unified CM learned a route from the IME server. However, due to the configured Trusted/Untrusted list, the route was rejected.
Recommended Action This condition is not an error. However, it indicates to you that one of your users called a number which was reachable over IME, however, due to your configured Trusted/Untrusted list, a IME call will not be made. You might wish to consider adding the domain or prefix to your Trusted list or removing it from the Untrusted list.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-PublicationRunCompleted : Completion of publication of published DID patterns Start time [String] End time [String] DID count [UInt] Failed DID count [UInt] Failed DIDs [String]
Explanation This alarm is generated when Unified CM completes a publication of the DID patterns into the Cisco Intercompany Media Network
Recommended Action This alarm is provided for historic and informational purposes. It can be used to give you feedback that the system is working and is correctly publishing numbers into the Cisco Intercompany Media Network. It can also be used for troubleshooting. If some of the publishes fail for some reason, the alarm will contain a list of those numbers which were not published. If your users are receiving calls, and they are not over IP but you think they ought to be, you can check the history of these alarms to see if the number failed to be published into the network.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-RouteRemoved : Route removed automatically E.164 number [String] Domain name [String] Route learned time [String] Reason Code [Enum]
Explanation This alarm is generated when Unified CM removes a route from Unified CM Administration because the route is stale and has expired, or because the far end has indicated the number is no longer reachable at that domain
Recommended Action This alarm is provided for historic and informational purposes. It helps you understand why certain numbers are in your routing tables, and why others are not. This historical information is useful to help determine why a call to a particular number is not going over IP, when you expect it to.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 1 |
Expired |
| 2 |
Unreachable |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-InsufficientFallbackIdentifiers : Cannot allocate fallback identifier Fallback profile name [String] Fallback E.164 number [String]
Explanation This alarm is generated when Unified CM is processing a IME call, and is attempting to allocate a PSTN fallback DID and a DTMF digit sequence to associate with this call. However, there are too many IME calls currently in progress which are utilizing this same fallback DID, and as a result, there are no more DTMF digit sequences which could be allocated to this call. As such, this call will proceed, however mid-call fallback will not be possible for this call.
Recommended Action Your first course of action should be to identify the fallback profile associated with this call. Its name will be present in the alarm. Check that profile in Cisco Unified CM Administration and examine the current setting for "Fallback Number of Correlation DTMF Digits". Increase that value by one, and check if that eliminates these alarms. In general, this parameter should be large enough such that the number of simultaneous IME calls made to enrolled numbers associated with that profile is always substantially less than 10 raised to the power of this number. "Substantially" should be at least a factor of ten. For example, if you always have less than 10,000 simultaneous IME calls for the patterns associated with this fallback profile, setting this value to 5 (10 to the power of 5 is 100,000) will give you plenty of headroom and you will not see this alarm. However, increasing this value also results in a small increase in the amount of time it takes to perform the fallback. As such, it should not be set arbitrarily large; it should be set just large enough to keep clear of this alarm. Another alternative to increasing this parameter is to add another fallback profile with a different fallback DID, and associate that fallback profile with a smaller number of enrolled DID patterns. This will allow you to get by with a smaller number of digits.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-IMEQualityAlertEntry : IME call quality problem Active IME call count [UInt] Fallback call count [UInt] Setup attempts count [UInt] Failed attempts [UInt]
Explanation This alarm is generated when Unified CM is seeing a substantial number of IME calls fail back to PSTN, or fail to be set up, due to IP network quality problems. There are two triggers for this alarm. One is when a large fraction of the currently active IME calls have all requested fallback, or have fallen back, to the PSTN. The other is when a large fraction of the recent call attempts have not been made over IP, and instead have gone to the PSTN.
Recommended Action Check your IP connectivity, and make sure it is good. If it looks good in general, you may need to look at CDRs, CMRs, and logs from the firewalls to determine what happened.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-IMEQualityAlertExit : IME call quality problem cleared Active IME call count [UInt] Fallback call count [UInt] Setup attempts count [UInt] Failed attempts [UInt]
Explanation This alarm is generated when the Unified CM sees a significant reduction in the number of failed IME calls following generation of the IMEQualityAlertEntry alarm. This notice alarm indicates that the IP connectivity issues causing the initial generation of the IMEQualityAlertEntry alarm have abated.
Recommended Action Continue to monitor IP connectivity for recurring issues
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-InvalidSubscription : A message has been received from an IME server that contains a subscription identifier that is not handled by this node Subscription Identifier [UInt] IME Server [String]
Explanation Each node that communicates with a IME server saves a subscription identifier associated with each IME client instance. A IME server has sent a message with a subscription identifier that does not match any of the previously sent subscription identifiers.
Recommended Action This may be a race condition if a IME client instance has been recently added or deleted. If this error continues, there may be a synchronization issue between this node and the IME server sending this message.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-FirewallMappingFailure : Firewall unreachable IP address [String] Port number [UInt]
Explanation This alarm indicates that Unified CM was unable to contact the firewall in order to make a IME call. As a consequence, outbound calls are being sent over the PSTN, and inbound calls may be routed over the PSTN by your partner enterprises.
Recommended Action Check to see that your firewall is up. Make sure the mapping service is enabled. Check that the IP address and port on the firewall for that mapping service match the configuration in Unified CM Administration. Check general IP connectivity between Unified CM and the firewall.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-ConflictingDataIE : A call has been rejected because the incoming PRI/BRI Setup message had an invalid IE Device Name [String]
Explanation A call has been rejected because an incoming PRI/BRI Setup message contained an invalid Coding Standard value in the Bearer Capability information element (IE). Unified CM only accepts PRI/BRI Setup messages with Coding Standard values of 0 or 1. When an invalid IE is received, Unified CM rejects the call setup and issues this alarm.
Recommended Action Notify the service provider responsible for sending the Setup message that an IE with Coding Standard values of 0 or 1 must be included in Setup messages
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-SIP IPPortConflict : The local port for this device is already in use Device Name [String] Port Number [String] Device type [Enum]
Explanation The local port specified for this device is already in use, or Cisco Unified CM Communications Manager is unable to bind to the configured port. Either the SIP device is configured incorrectly or the domain name system (DNS) is incorrectly configured.
Recommended Action In Cisco Unified CM Administration, check the port number for the SIP device.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value |
Definition |
| 131 |
SIP_TRUNK |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-ConferenceCreated : An application controlled conference is created. Conference Name [String] Conference ID [UInt] Video Enabled [UInt] Application ID [UInt] Number of Streams [UInt] Status [Int] Reason [Int]
Explanation An application controlled conference is created.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-ConferenceDeleted : An application controlled conference is deleted. Conference Name [String] Conference ID [UInt] Reason [Int]
Explanation An application controlled conference is deleted.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-CtiCallAcceptTimeout : Call Accept Timeout Call Accept Timer [UInt] Device Name [String] Calling Party DN [String] Called Party DN [String]
Explanation The application failed to accept the call within the CallAcceptTimer time period.
Recommended Action Configure the CallAcceptTimer service parameter appropriately based on the expected response time of the application.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-CtiStaleCallHandle : CTI stale call handle. Description [String]
Explanation This alarm is issued by audit when it finds invalid call handles that the CTI application didn't close when calls go to idle state.
Recommended Action No action is required. It is recommended that the CTI applications explicitly close the calls when the call goes to idle state.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DatabaseAuditInfo_074 : Database audit information. Number [Int]
Explanation Database audit information error occurred.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-DatabaseDeviceNoDirNum : No directory number for database device. Text [String]
Explanation No directory number(s) are associated with identified device.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-1-DatabaseInternalDataError_06e : Database internal data error. DeviceName [String]
Explanation Database internal data error occurred.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-DatabaseInternalDataError_06f : Database internal data error. Route Group Name [String]
Explanation Database internal data error occurred.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DatabaseInternalDataError_070 : Database internal data error. Device Name [String]
Explanation Database internal data error occurred.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DatabaseInternalDataError_071 : Database internal data error. Device Name [String]
Explanation Database internal data error occurred.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DatabaseInternalDataError_072 : Database internal data error. Device Name [String]
Explanation Database internal data error occurred.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DatabaseInternalDataError_073 : Database internal data error. Device Type [String]
Explanation Database internal data error occurred.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DatabaseInternalDataError_075 : Database internal data error. Text [String]
Explanation Database internal data error occurred.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DnTimeout : DN Timeout. Port IsoEthPort [UInt] Port DSL [UInt]
Explanation Timeout was encountered while trying to read pattern or directory number configuration.
Recommended Action Investigate configuration for identified device.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-H323AddressResolutionError : H323 address not resolved. Device Name. [String]
Explanation An H323 device address could not be resolved. Cisco CallManager cannot handle calls to/from the indicated H323 device.
Recommended Action Either the H323 device entry is configured incorrectly, or the domain name system (DNS) is incorrectly configured.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-H323CallFailureAlarm : H323 Call failure Peer IP Address [String] Peer IP Port [UInt] Reason Code [Enum]
Explanation H.323 inbound call fails because information required to route the call, including the source E.164 address, call signaling address, or H.323 ID, is missing.
Recommended Action No action needed.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 1 |
Unknown |
| 2 |
SourceE164AddressNotFound |
| 3 |
CallSignallingAddressNotFound |
| 4 |
H323IdNotFound |
| 5 |
SourceE164AddressOrCallSignallingAddressNotFound |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-MWIParamMisMatch : MWI parameter mismatch.
Explanation Message waiting indicator number configuration error occurred.
Recommended Action Investigate message waiting indicator configuration.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-OutOfDnForAutoRegistration : Out of directory numbers for auto-registration.
Explanation Cisco CallManager ran out of directory numbers for auto-registration.
Recommended Action Investigate auto-registration configuration.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-PktCapDownloadOK : Downloaded captured packet or key file. Packet/Key file name [String]
Explanation Indicated the packet or key file has been downloaded.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-PktCapDownloadFailed : Did not get captured packet or key file. Packet/Key file name [String] Failed Reason [String]
Explanation Indicated reasons for the packet or key file could not be downloaded.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-PktCapLoginOK : Login OK for getting captured packet or key file. User ID [String]
Explanation Indicated the user can get the packet or key file.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-PktCapLoginFailed : Login failed for getting captured packet or key file. User ID [String] Login Failed Reson [String]
Explanation Indicated the user cannot get the packet or key file.
Recommended Action It is required that the user is an valid End User under the user group called Standard Packet Sniffer Users.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-ThrottlingSampleActivity : ThrottlingSampleActivity Throttling Sample Activity [Int]
Explanation CallManager has initiated call throttling due to unacceptably high delay in handling incoming calls.
Recommended Action Determine the reason for high CPU usage in the High priority and Normal priority queues (Cisco CallManager System Performance object).
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-GatewayAlarm : Gateway alarm. Device Name [String] TCP Handle [VoidPtr] Device Text [String] Param1 [UInt] Param2 [UInt]
Explanation Gateway device sent an alarm to Cisco CallManager.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-NoConnection : No TCP connection.
Explanation Disconnect or release request attempt occurred on unknown TCP connection.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-TotalCodeYellowEntry : TotalCodeYellowEntry Total Code Yellow Entry [Int]
Explanation CallManager has initiated call throttling due to unacceptably high delay in handling incoming calls.
Recommended Action Determine the reason for high CPU usage in the High priority and Normal priority queues (Cisco CallManager System Performance object).
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-Redirection : Redirection Manager cannot register with the Call Control. Redirection Error Message [String]
Explanation The registration error occurs either when it registers itself or the REDIRECTION_OPERATIONIE_ID with the Call Control.
Recommended Action It is a code bug. No Action is Required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-CorruptedIncomingDMPropagationMessage : Unified CM received a corrupted DMRemoteDeviceRegisterUnRegister message in internode communication Corrupted Register Elements Count [UInt] Corrupted UnRegister Elements Count [UInt] RemoteNodeID [UInt]
Explanation Unified CM examines the incoming DMRemoteDeviceRegisterUnRegister messages to detect values in the message that are outside the normal expected range. Unified CM issues this alarm when the message is determined by Unified CM to contain values outside the normal range. Unified CM has discarded part of the contents of the incoming DMRemoteDeviceRegisterUnRegsister message due to the values that were out of range. This may cause an out-of-synch condition for the registered device's information between the sending node and this node, which in turn can lead to phone calls being routed incorrectly
Recommended Action Make a note of the IP address/name of the remote CM node that generated this message. Around the timestamp of this alarm, save the SDL/SDI logs from this node and the remote node for analysis by Cisco TAC personnel. Next, at the first opportunity, restart the Cisco CallManager service on this node to ensure that the registered devices information throughout the cluster are in synch. Also, in Cisco Unified Serviceability, make sure to set the Unified CM SDI logs setting to Detailed to ensure collecting relevant logs should this alarm recur. If this alarm does occur again, contact Cisco TAC to help determine the source of DMRemoteDeviceRegisterUnRegister message corruption.
Error Message
CCM_SUMI-CMI-6-CMIServiceStatus : Service is running and working properly Service Priority [String]
Explanation CMI service is running and working properly
Recommended Action Informational purpose only; no action is required
Error Message
CCM_SUMI-CMI-1-StopBitConfigurationError : The Cisco Messaging Interface service parameter, Stop Bits, has an invalid configuration Illegal Stop Bit [String]
Explanation An invalid stop bit has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the Stop Bits value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.
Recommended Action Verify that the Cisco Messaging Interface service parameter Stop Bits is set to a valid (allowable) value
Error Message
CCM_SUMI-CMI-1-ParityConfigurationError : The CMI service parameter, Parity, has an invalid configuration Illegal Parity [String]
Explanation An invalid parity has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the parity value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.
Recommended Action Verify that the Cisco Messaging Interface service parameter Parity is set to a valid (allowable) value
Error Message
CCM_SUMI-CMI-5-SMDIMessageError : SMDI message contains invalid DN Invalid DN [String]
Explanation Some voice messaging systems send SMDI messages to Cisco Unified Communications Manager (Unified CM) with an invalid DN specifically for the purpose of verifying that Unified CM is functioning properly. In such cases, if the Validate DNs service parameter is set to True, CMI triggers this alarm because the DN cannot be found in the Unified CM database.
Recommended Action Verify that the Cisco Messaging Interface service parameter Validate DNs is set to false
Error Message
CCM_SUMI-CMI-5-SMDICmdError : CMI receives an invalid incoming SMDI message Invalid SMDI command [String]
Explanation There are two kinds of incoming messages that Cisco Unified Communications Manager can accept from the voice messaging system; they are OP:MWI(SP)nnnnnnn!(D) and RMV:MWI(SP)nnnnnnn!(D) (where:nnnnnnnnnn = station number (can be 7 or 10 digits), (D) = End Of Transmission, (SP) = space). The first message activates the message waiting indicator (MWI). The second deactivates the message waiting indicator. CMI triggers this alarm if the received MWI message doesn't have one of the acceptable formats as described.
Recommended Action Contact the vendor of the third-party voice messaging system and discover why it is sending SMDI message with an invalid format
Error Message
CCM_SUMI-CMI-1-SerialPortOpeningError : When CMI tries to open the serial port, the operating system returns an error Serial Port Opening Error [String]
Explanation For a system running CMI, the serial port through which the voice messaging system is connected is always USB0, and that value is configured in the Cisco Messaging Interface service parameter, Serial Port. It is possible that the Serial Port value has been updated via AXL or a CLI command where validation of the value was not performed. CMI triggers this alarm if the value in the Serial Port service parameter is anything other than USB0.
Recommended Action Ensure that USB0 is configured in the Cisco Messaging Interface service parameter Serial Port. Also, physically confirm that the cable is firmly connected to the USB0 port.
Error Message
CCM_SUMI-CMI-3-SerialPortGetStatusError : When CMI tries to get the status of serial port, the operating system returns an error Serial Port Getting Status Error [String]
Explanation CMI triggers this alarm when it can't get the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.
Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
Error Message
CCM_SUMI-CMI-3-SerialPortSetStatusError : When CMI tries to set the status of serial port, the operating system returns an error Serial Port Setting Status Error [String]
Explanation CMI triggers this alarm when it can't set the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.
Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
Error Message
CCM_SUMI-CMI-3-WritingFileFailure : CMI failed to write SMDI messages to the serial port Error Information [String]
Explanation CMI opened the serial port, however it failed to successfully write data to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.
Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
Error Message
CCM_SUMI-CMI-3-ReadingFileFailure : CMI failed to read SMDI messages from the serial port Error Information [String]
Explanation CMI opened the serial port, however it failed to successfully read data from the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.
Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
Error Message
CCM_SUMI-CMI-3-InvalidPortHandle : The handle for the opened serial port is invalid Error Information [String]
Explanation CMI cannot read/write to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.
Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
Error Message
CCM_SUMI-CMI-1-VMDNConfigurationError : The Voice Mail DN for CMI is invalid Invalid Voice Mail DN [String]
Explanation CMI can't register with Cisco Unified Communications Manager because of an invalid Voice Mail DN. This alarm occurs because the Cisco Messaging Interface service parameter, Voice Mail DN, is empty or has invalid characters other than digits (0-9). It is possible that the Voice Mail DN value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.
Recommended Action Check the CMI service parameter Voice Mail DN to confirm that a valid directory number has been configured.
Error Message
CCM_SUMI-CMI-4-ThreadKillingError : An error occurred when CMI tried to stop the CMI service Error Information [String]
Explanation As a normal part of the process of stopping the CMI service, open threads are closed (killed). This alarm indicates that a timeout occurred which means that the shutdown process is taking longer than expected, causing the operating system to return an error.
Recommended Action Try restarting the CMI service. If the problem persists, collect the system/application event logs and the performance (perfmon) logs and report to Cisco Technical Assistance Center (TAC).
Error Message
CCM_SUMI-CMI-4-MemAllocFailed : CMI tried to allocate memory and failed Memory Allocation Failure [String]
Explanation Cisco Unified Communications Manager tried to read the Cisco Messaging Interface service parameters but not enough memory was allocated for the task and so the information could not be read.
Recommended Action Use the Real-Time Monitoring Tool to check performance counters related to system memory to learn whether any memory leaks or spikes in CPU are occurring. Correct any anomalous memory issues you find. If you do not find any issues with memory, collect the system/application event logs and the performance (perfmon) logs and report this alarm to the Cisco Technical Assistance Center (TAC).
Error Message
CCM_SUMI-CMI-1-DBLException : Unable to connect to the DB DBL Exception [String]
Explanation When CMI service is started, it tries to read CMI Service Parameters from DB. During this, if CMI cannot connect to the database, it triggers this alarm.
Recommended Action Check Database connection, then restart CMI.
Error Message
CCM_SUMI-CMI-1-CMIException : Error while reading the database CMI Exception [String]
Explanation This alarm is always associated with other alarms, which are triggered due to configuring CMI service parameter with invalid values or due to invalid handle value returned by the serial port.
Recommended Action Refer to the associated alarm for further information.
Error Message
CCM_SUMI-CMI-1-UnknownException : Unknown error while connecting to DB
Explanation When CMI service is started, it tries to read CMI service parameters from DB. During this, if there is an unknown error, CMI triggers this alarm.
Recommended Action Report to Customer Service representative.
Error Message
CCM_SUMI-CMI-5-CMIServiceStarted : Service is now running
Explanation CMI service has been started and running
Recommended Action Informational purpose only; no action is required
Error Message
CCM_SUMI-CMI-5-CMIServiceStopped : Service is now stopping.
Explanation CMI Service has been stopped.
Recommended Action Informational purpose only; no action is required.
Error Message
CCM_SUMI-CMI-7-CMIDebugAlarm : This alarm is generated only for the purpose of debugging Debug Message [String]
Explanation CMI has several debug messages which simulate the real-time situations
Recommended Action Report to Customer Service representative
Error Message
CCM_SUMI-CMI-3-CCMConnectionError : CMI can't establish connection with the Cisco Unified Communications Manager CallManager Name [String]
Explanation CMI can't establish connection with the Unified Communications Manager
Recommended Action Check the address/status of the CallManager and the network
Error Message
CCM_SUMI-CMI-3-DisconnectionToCCM : CMI loses the connection with Unified Communications Manager CallManager Name [String]
Explanation CMI loses the connection with the Cisco Unified Communications Manager
Recommended Action Check the status of the Unified Communications Manager and the Network
Error Message
CCM_SUMI-CMI-2-WSAStartupFailed : Windows Socket startup failed Error Information [String]
Explanation WinSock could not be started
Recommended Action Report to Customer Service representative.
Error Message
CCM_SUMI-CMI-5-ConfigParaNotFound : CMI service configuration parameter is not found in Database Parameter Name and Information [String]
Explanation CMI cannot find this process configuration parameter in process configuration table.
Recommended Action Report to Customer Service representative to get the database upgrade
Error Message
CCM_SUMI-CMI-1-COMException : CMI catches an COM exception. COM Exception [String]
Explanation CMI cannot find this process configuration parameter in process configuration table.
Recommended Action Check system setting and resource, then restart system.
Error Message
CCM_CTI-CTI-4-ApplicationConnectionDropped : Application has dropped the connection to CTIManager Last QBE PDU number [Long]
Explanation TCP or TLS connection between CTIManager and Application is disconnected
Recommended Action Possible causes include Application server power outage, network power outage, network configuration error, network delay, packet drops or packet corruption. It is also possible to get this error if the Unified CM node or application server is experiencing high CPU usage. Verify the application is up and running, verify network connectivity between the application server and Unified CM, and verify the CPU utilization is in the safe range for application server and Unified CM (this can be monitored using RTMT via CPU Pegging Alert)
Error Message
CCM_CTI-CTI-4-CtiMaxConnectionReached : Maximum number of application connections is reached; application connection rejected
Explanation Maximum number of CTI connections has been reached, no new connection will be accepted unless an existing connection is closed
Recommended Action Check the CTI Manager service parameter Maximum CTI Connections for the maximum number of connections. Carefully consider increasing the service parameter value or disconnecting CTI applications that are unnecessary. Refer to Unified CM Solution Reference Network Design document in www.cisco.com based on the version you are using for maximum number of applications and devices supported by CTI
Error Message
CCM_CTI-CTI-4-InvalidQBEMessage : An invalid QBE PDU is received CTI Connection type [String] Instance number [Long] QBE PDU number [Long]
Explanation QBE PDU from application is invalid
Recommended Action This alarm indicates that TSP/JTAPI has reported a QBE PDU that cannot be recognized by CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins)
Error Message
CCM_CTI-CTI-3-CtiProviderOpenFailure : CTI application failed to open provider; application startup failed CTIconnectionId [Long] Login User Id [String] Reason code. [Enum]IPaddress [String] IPv6address [String]
Explanation The application is unable to open provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode
Recommended Action Review the reason code and the recommended action within the reason code
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 0 |
Unknown |
| 0x8CCC0075 (2362179701) |
Login request to authenticate user has timed out. Possible causes include LDAP server misconfiguration such as LDAP server referrals misconfiguration or Unified CM node experiencing high CPU usage. Recommended action is to verify the CPU utilization is in the safe range for Unified CM (this can be monitored using RTMT via CPU Pegging Alert) |
| 0x8CCC0060 (2362179680) |
Directory login failed. Verify that credentials are not misconfigured, check the userID and password configured in the application matches with what is configured in Unified CM Admin under (User Management > End User or Application User) |
| 0x8CCC005E (2362179678) |
Directory is unavailable. Verify that the LDAP server is reachable from Unified CM node, make sure that the network connectivity between Unified CM and the LDAP server by pinging the LDAP server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost |
| 0x8CCC00D1 (2362179793) |
Application is connecting to a non secure port but has security priviledges enabled for the user associated with the application. Check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information |
| 0x8CCC005F (2362179679) |
Standard CTI Use permission is not enabled. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information |
| 0x8CCC00D0 (2362179792) |
User is not enabled for a secure connection but the application connecting to secure port. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure... > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information |
Error Message
CCM_CTI-CTI-4-CtiQbeFailureResponse : Requested operation from the application has failed Error code [ULong] Sequence number [Long] Error message [String]
Explanation The requested operation from the application could not be performed because of a normal or abnormal condition
Recommended Action Verify whether the affected application is experiencing a problem. Contact the support organization for the affected application if the problem persists and provide sequence number and error message for further investigation
Error Message
CCM_CTI-CTI-6-CtiProviderClosed : CTI application connection has been closed Login User ID [String] Sequence number [Long] CTI connection Id [Long] IPAddress [String] IPv6Address [String] Reason code [Enum]
Explanation Application closed the provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode
Recommended Action This alarm is for informational purposes only; no action is required.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 0 |
Unknown |
| 1 |
Heart beat from application missed. Possible causes include network connectivity issues or Unified CM node experiencing high CPU usage. Make sure that the network connectivity between Unified CM and the application by pinging the application server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost. Also check for and fix any network issues or high CPU usage on the application server |
| 2 |
Unexpected shutdown; possibly cause is application disconnected the TCP connection. Also check for and fix any network issues or high CPU usage on the application server |
| 3 |
Application requested provider close |
| 4 |
Provider open failure; application could not be initialized |
| 5 |
User deleted. User associated with the application is deleted from the Unified CM Administration |
| 6 |
SuperProvider permission associated with the application is removed. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information |
| 7 |
Duplicate certificate used by application. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information |
| 8 |
CAPF information unavailable. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information |
| 9 |
Certificate compromised. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information |
| 11 |
User is not authorized to connect to CTI using TLS. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure... > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information |
| 12 |
Standard CTI Use permission removed. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information |
Error Message
CCM_CTI-CTI-6-CtiProviderOpened : CTI application connection opened. Login User Id [String] Sequence Number [Long] Version Number [String] CTI Connection Id [Long] IPAddress [String] IPv6Address [String] Unified CM-AssignedAppID [Long]
Explanation Application opened the provider successfully. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode.
Recommended Action This alarm is for informational purposes only; no action is required.
Error Message
CCM_CTI-CTI-3-UnableToRegisterwithCallManagerService : Unable to communicate with the Cisco CallManager service Unified CM Node ID [Long]
Explanation CTI cannot communicate with Cisco CallManager service to register supplementary service features
Recommended Action Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists. If CallManager service is active, verify network connectivity between the Unified CM node that hosts CTIManager service and Unified CM node that hosts CallManager service
Error Message
CCM_CTI-CTI-4-CtiProviderCloseHeartbeatTimeout : CTI heartbeat timed out; application disconnected
Explanation CTI heartbeat timeout occurred causing CTIManager to close the application connection
Recommended Action Heartbeat timeout could occur due to high CPU usage or network connectivity problems. Check for and fix any network issues or high CPU usage on the application server. If the application server is running the Microsoft Windows OS use Task Manager or Perfmon to determine the CPU usage. For applications in Linux use the top command to review CPU usage
Error Message
CCM_CTI-CTI-4-CtiIncompatibleProtocolVersion : Incompatible protocol version Message Version [VoidPtr] Compatible Versions [VoidPtr] Current Version [VoidPtr] Unified CM Version [String] IPAddress [String] IPv6Address [String]
Explanation The JTAPI/TAPI application version is not compatible with this version of CTIManager, so the received message has been rejected. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode
Recommended Action Verify that the correct version of the application is being used. If you're unsure of the correct version, contact the application vendor and upgrade the JTAPI/TSP to the version provided by Cisco Unified Communications Manager. JTAPI/TSP plugins are available in Cisco Unified CM Administration (Application > Plugins)
Error Message
CCM_CTI-CTI-6-CtiDeviceOpened : Device opened Device Name [String] Sequence Number [Long] Device ID [Long] Device Type [Long] CTI connection Id [Long] MediaControlled [Bool] RTP Address [String] CmAssignedAppID [Long]
Explanation Application opened a device
Recommended Action This alarm is for informational purposes only; no action is required
Error Message
CCM_CTI-CTI-6-CtiDeviceClosed : Device closed Device Name [String] Device ID [Long] Device Type [Long] CTI Connection Id [Long] MediaControlled [Bool] RTP Address [String] Reason code. [Enum]
Explanation Application closed a device
Recommended Action This alarm is for informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 0 |
Unknown |
| 1 |
CallManager service is not available to process request; verify that the CallManager service is active. Check the Cisco Unified Serviceability Control Center section in Cisco Unified CM Administration (Tools > Control Center - Feature Services) |
| 2 |
Device has unregistered with Cisco Unified Communications Manager |
| 3 |
Device failed to rehome to Cisco Unified Communications Manager; verify that the device is registered |
| 4 |
Device is removed from the Unified CM database |
| 5 |
Application controlling the device has closed the connection |
| 6 |
Route Point already registered by another application |
| 7 |
CTI Port already registered by another application |
| 8 |
CTI Port/Route Point already registered with dyamic port media termination |
| 9 |
Enabling softkey failed for device; verify that the device is registered |
| 10 |
Multiple applications have registered the device with media capability that do not match |
| 11 |
This device is already controlled by another application |
| 12 |
Protocol used by the device is not supported |
| 13 |
Device is restricted for control by any application |
| 14 |
Unable to communicate with database to retrieve device information |
| 15 |
Device is resetting |
| 16 |
Unable to register the device as specified media type is not supported |
| 17 |
Unsuppported device configuration |
| 18 |
Device is being reset |
| 19 |
IPAddress mode does not match what is configured in Unified CM |
Error Message
CCM_CTI-CTI-4-CtiDeviceOpenFailure : Device Open failed CTI Connection Id [Long] Device Name [String] ReasonCode [Enum]
Explanation Application is unable to open the device
Recommended Action Check the reason code and take appropriate action to resolve the issue
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 0x8CCC0013 (2362179603) |
Device is already opened by another application; identify the application that is controlling this device. You can determine this information from RTMT (CallManager->CTI Manager and CallManager->CTI Search) |
| 0x8CCC00DA (2362179802) |
Unable to communicate with database; verify the CPU utilization is in the safe range for (this can be monitored using RTMT via CPU Pegging Alert) |
| 0x8CCC009A (2362179738) |
Device is unregistering; wait for the device to register. Due to user initiated reset or restart of the device from Unified CM. Device should automatically register wait for few moments for the device to register |
| 0x8CCC0018 (2362179608) |
Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User) |
| 0x8CCC00F3 (2362179827) |
IPAddress mode (IPv4 or IPv6 or both) specified by the application does not match with IP Addressing mode that is configured in Unified CM Administration; check the IP addressing mode of the device in Cisco Unified CM Administration (Device > Device Settings > Common Device Configuration) |
Error Message
CCM_CTI-CTI-6-CtiDeviceOutofService : Device is out of service Device ID [Long] CTI Connection Id [Long] Device Name [String]
Explanation Device is out of service
Recommended Action This alarm is for informational purposes only; no action is required
Error Message
CCM_CTI-CTI-6-CtiDeviceInService : Device in service. Device ID [Long] CTI Connection Id [Long] Device Name [String] Call Manager Id [Long]
Explanation Device is back in service
Recommended Action This alarm is for informational purposes only; no action is required
Error Message
CCM_CTI-CTI-6-CtiLineOpened : Line opened Sequence Number [Long] Directory Number [String] Partition [String] Device Name [String] CTI Connection Id [Long]
Explanation Application opened the line
Recommended Action This alarm is for informational purposes only; no action is required
Error Message
CCM_CTI-CTI-4-CtiLineOpenFailure : Unable to open the line CTI Connection Id [Long] Device Name [String] Directory Number [String] Partition [String] Reason [Enum]
Explanation Application is unable to open the line
Recommended Action Review the reason code and take appropriate action to resolve the issue
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 0 |
Unknown |
| 0x8CCC0018 (2362179608) |
Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User) |
| 0x8CCC0005 (2362179589) |
Line is not found in the device; possible cause could be that the line that previously existed on this device is not available. This could be due to a extension mobility login or logout |
| 0x8CCC00D3 (2362179795) |
Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application |
Error Message
CCM_CTI-CTI-6-CtiLineClosed : Line closed. Directory Number [String] Partition [String] CTI Connection Id [Long] Device Name [String] Reason code [Enum]
Explanation Application closed the line
Recommended Action This alarm is for informational purposes only; no action is required
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value |
Definition |
| 0 |
Unknown |
| 1 |
CallManager failure |
| 2 |
Device has unregistered with Cisco Unified Communications Manager; wait for the device to register |
| 3 |
CTI failed to rehome the line; verify that the device is registered |
| 4 |
Undefined line, possible cause could be that line is no more active on that device due to extension mobility login or logout |
| 5 |
Device removed |
| 6 |
Provider controlling the device is closed |
| 7 |
Protocol used by the device is not supported |
| 8 |
Application cannot control this line as CTI Allow Control is not enabled. Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application |
| 9 |
Unable to register the device; application specified media type is not supported |
| 10 |
Device is being reset; verify that the device is registered before opening the line |
| 11 |
Unsuppported device configuration |
Error Message
CCM_CTI-CTI-6-CtiLineOutOfService : Line is out of service Directory Number [String] Partition [String] CTI Connection Id [Long] Device Name [String]
Explanation Line is going out of service
Recommended Action This alarm is for informational purposes only; no action is required
Error Message
CCM_CTI-CTI-6-CtiLineInService : Line in service Line ID [Long] CTI Connection Id [Long]
Explanation Line is back in service
Recommended Action This alarm is for informational purposes only; no action is required
Error Message
CCM_CTI-CTI-4-UnableToSetorResetMWI : Error in setting message waiting indicator Directory Number [String]
Explanation An error occurred when setting the message waiting indication (MWI) lamp
Recommended Action The line issuing the request to set the MWI lamp on the target line might not have the proper partitions/calling search space settings to allow it to reach the target line. Check the partitions and calling search space of the line that is requesting to set MWI on the target line. The target line should be able to receive a call from the line that is attempting to set MWI
Error Message
CCM_CTI-CTI-6-RedirectCallRequestFailed : Request from application to redirect a call has failed Sequence Number [Long] Directory Number [String] Partition [String]
Explanation CTIManager is unable to redirect a call
Recommended Action This alarm is for informational purposes only; no action is required
Error Message
CCM_CTI-CTI-4-MaxDevicesPerProviderExceeded : Application has opened more devices than allowed
Explanation An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Provider
Recommended Action The application is controlling more devices than the CTI support allows. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the application does not restrict support to the device limit specified by CTI in the CTIManager service parameter, Maximum Devices Per Provider
Error Message
CCM_CTI-CTI-4-MaxDevicesPerNodeExceeded : Application has opened more devices than the limit for each node
Explanation An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Node.
Recommended Action One or more applications are controlling more devices than the CTI support allows on the specified Unified CM node. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the total number of devices controlled by applications is not properly restricted to the device limit specified by the CTIManager service parameter, Maximum Devices Per Node
Error Message
CCM_CTI-CTI-4-ApplicationConnectionError : CTIManager is unable to allow connections from Applications. CTI Connection type [String] Instance number [Long]
Explanation CTIManager is unable to accept connections from applications
Recommended Action CTIManager has encountered problems initializing TCP connections. Restart the CTIManager service to resolve this problem
Error Message
CCM_CTI-CTI-3-kCtiQbeLengthMisMatch : OutputQbeMessage: length mismatch.
Explanation QBE header length mismatch exists.
Recommended Action This alarm indicates that TSP/JTAPI is incompatible with the version of CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins).
Error Message
CCM_CTI-CTI-3-kCtiInvalidQbeSizeAndOffsets : InvalidQBESizeAndOffsets; QBE message decoding encountered illegal size or offset.
Explanation QBE Packet received from the application is not encoded correctly.
Recommended Action A TSP/JTAPI interface error occurred; the QBE message may not be formatted correctly. TSP/JTAPI might be incompatible with the version of CTIManager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.
Error Message
CCM_CTI-CTI-3-kCtiSsRegisterManagerErr : Unable to register CtiLine with SSAPI.
Explanation CTI cannot register CtiLine with SSAPI.
Recommended Action Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists.
Error Message
CCM_CTI-CTI-4-kCtiMytcpErrSocketBroken : Socket connection has been broken.
Explanation The TCP connection has been lost.
Recommended Action Although connection to the application is lost, no action is required if lost connection was intentional. If loss of connectivity was unintentional, investigate what might have caused connectivity to be lost and restore the connection.
Error Message
CCM_CTI-CTI-4-kCtiDirectoryLoginFailure : CTI directory login failure. Sequence number [Long]
Explanation CTI Manager is unable to login to directory. As a result, the application may not be able to access the controlled device list.
Recommended Action In Cisco Unified CM Administration, verify that the correct username and password has been configured and is being used for CTIManager login. If LDAP is used for authentication, check to confirm that the LDAP synchronization is configured and is working.
Error Message
CCM_CTI-CTI-4-kCtiDeviceOpenFailAccessDenied : DeviceOpenRequest failure. User ID [String] Device Name [String] Device Type [Long]
Explanation Application is trying to access a device that is not in its control.
Recommended Action Check the application sending the request or add the device to the user control list.
Error Message
CCM_CTI-CTI-3-kCtiIllegalQbeHeader : Illegal QBE header.
Explanation Because of illegal QBE header, QBE message has been rejected.
Recommended Action QBE header could be fragmented due to TCP fragmentation. Review your network configuration to fix any TCP fragmentation issue.
Error Message
CCM_CTI-CTI-4-kCtiLineOpenFailAccessDenied : Line open failed. Sequence Number [Int] Directory Number [String] Partition [String] Device Name [String] login ID of the user [String]
Explanation Application failed to open a line.
Recommended Action Add the device associated with the line to the user device control list.
Error Message
CCM_CTI-CTI-4-kCtiIllegalEnumHandle : Enumeration handle is not valid. Enumeration handle [Long] Enumeration object type [String]
Explanation The enumeration handle associated with the process of enumerating devices, lines or DNs is invalid.
Recommended Action Check whether all devices, lines or DNs configured for the application are available to the application. If the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User).
Error Message
CCM_CTI-CTI-4-kCtiQbeMessageTooLong : Incoming QBE message exceeds input buffer size CTI Connection type [String] Instance number [Long] Message length [Long]
Explanation An incoming QBE message exceeds the input buffer size and then gets dropped.
Recommended Action The size of the QBE packet could exceed the suggested size when the JTAPI/TSP version is not compatible with the version of CTIManager. Contact the application vendor and verify that the application is compatible with the version of Cisco Unified Communications Manager (Unified CM). If the application vendor requests you to, install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.
Error Message
CCM_CTI-CTI-4-kCtiNullTcpHandle : TranslateCtiQbeInputMessage: NULL TCP HANDLE!!! (QBE packet is dropped) PDU number [Long]
Explanation A null TCP handle is preventing the QBE packets to be reported to applications.
Recommended Action This problem typically happens due to a network connectivity failure. Check for and resolve any connectivity issues in your network.
Error Message
CCM_CTI-CTI-3-kCtiEnvProcDevListRegTimeout : Directory change notification request time out.
Explanation CTIManager registration request to EnvProcDevList timed out; CTIManager will send another registration request.
Recommended Action Check and resolve network connectivity problems between Cisco Unified Communications Manager nodes.
Error Message
CCM_CTI-CTI-3-kCtiMYTCPSendError : MYTCP_Send: send error.
Explanation TCP socket connection has been broken.
Recommended Action This problem occurs when an application is abruptly shut down or has lost network connectivity to CTIManager. Review your application and network connectivity and resolve any issues.
Error Message
CCM_CTI-CTI-2-kCtiSdlErrorvException : Failed to create an internal process that is required to service CTI applications.
Explanation An unexpected internal SDL error caused a failure in creating CTIManager Service SDL Process.
Recommended Action An internal CTIManager error has occurred. Try Restarting the CTIManager service to resolve this problem, if it does resolve the problem restart the Unified CM Server.
Error Message
CCM_CTI-CTI-3-kCtiTcpInitError : CTIManager service is unable to initialize TCP connection Error Code [Int]
Explanation CTIManager service is unable to initialize TCP connection
Recommended Action CTIManager has encountered difficulty initializing TCP connections. Restart the CTIManager service to resolve this problem.
Error Message
CCM_CTI-CTI-3-kCtiIllegalFilterSize : ProviderOpenRequest; illegal filter size.
Explanation ProviderOpenRequest has an illegal filter size.
Recommended Action The application is using an incompatible version of JTAPI/TSP and Cisco Unified Communications Manager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.
Error Message
CCM_CTI-CTI-4-kCtiNewCallNotifyArrayOverflow : Possible internal array overflow condition while generating CTI NewCall event.
Explanation An unexpected internal error occurred.
Recommended Action Restart the CTIManager service if the problem persists.
Error Message
CCM_CTI-CTI-4-kCtiExistingCallNotifyArrayOverflow : Possible internal array overflow condition while generating CTI ExistingCall event.
Explanation An unexpected internal error occurred.
Recommended Action Restart the CTIManager service if the problem persists.
Error Message
CCM_CTI-CTI-4-kCtiLineCallInfoResArrayOverflow : Possible internal array overflow condition while generating response to application request for call information.
Explanation An unexpected internal error occurred.
Recommended Action Restart the CTIManager service if the problem persists.
Error Message
CCM_CTI-CTI-4-kCtiUnknownConnectionHandle : Connection handle is not valid. CTI Connection type [String] Instance number [Long]
Explanation A message has been received from an unknown connection, and then dropped.
Recommended Action This alarm occurs when a QBE packet is received from a connection that is already disconnected. This packet will be ignored by CTIManager and no action is required.
Error Message
CCM_CTI-CTI-3-kCtiProviderOpenInvalidUserNameSize : Invalid userName size in ProviderOpen request. login user Name size [Long]
Explanation User name length is invalid.
Recommended Action Ask user of CTI application to use correct userName and to check the user name in configuration. It should not be more than 31 characters.
Error Message
CCM_DB_LAYER-DB-3-kDbConnectionFailed : Database connection failed. Additional Information [String]
Explanation An attempt to connect to database failed.
Recommended Action Enable trace for the database layer monitor to get specific error information.
Error Message
CCM_DB_LAYER-DB-1-NoDbConnectionAvailable : No database connection available.
Explanation Database layer could not find any working database connection.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Check network connectivity and operation of SQL Server services.
Error Message
CCM_DB_LAYER-DB-2-ErrorChangeNotifyClientBlock : A change notification client is busy (blocked). If the change notification client continues to be blocked for 10 minutes, the system automatically clears the block and change notification should resume successfully.
Explanation Changes made to the database are not being consumed by one of the recipients. This does not always represent an issue. However, if the change notification client continues to be blocked for 10 minutes, the system automatically clears the block for all clients except the blocked one, which means that change notifications should resume successfully for all other clients. To clear the blocked client, you must restart the server.
Recommended Action At the command line interface (CLI) on the database server, execute the following command: show tech notify. The CLI command output will provide information about the block. Use Cisco Unified Serviceability to restart the server that was indicated in the alarm. You may also want to gather traces to examine them for anomalous activity during the time that client was blocked. In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_DB_LAYER-DB-3-ErrorReadingInstalledRPMS : Could not read installed RPMs to populate component version table
Explanation The function that reads the rpm version information and populates database failed
Recommended Action Please report this error to the administrator.
Error Message
CCM_DB_LAYER-DB-3-ErrorChangeNotifyClientTimeout : A change notification client was responding slowly and has been removed.
Explanation A change notification recipient hasn't responded to change notification in several minutes and was thus removed. This may delay call processing features, such as call forwarding and so on.
Recommended Action Rebooting the box will clear this situation. Alternatively, dbnotify trace could be analyzed to find the client that was removed and that service could be restarted in Cisco Unified Serviceability.
Error Message
CCM_DB_LAYER-DB-1-ErrorChangeNotifyReconcile : A change notification shared memory reconciliation has occurred.
Explanation The change notification buffers in shared memory have been rebuilt due to conflicts.
Recommended Action This problem may have been already corrected. If unexpected behavior is observed, restart all Cisco services in the cluster.
Error Message
CCM_DB_LAYER-DB-6-IDSEngineDebug : Indicates debug events from IDS database engine. Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm provides low-level debugging information from IDS database engine. System administrator can disregard this alarm.
Recommended Action This is for debug information purposes only; no action is required.
Error Message
CCM_DB_LAYER-DB-6-IDSEngineInformation : No error has occurred but some routine event completed in IDS database engine. Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm is informational. No error has occurred but some routine event completed in IDS database engine.
Recommended Action This is for information purposes only; no action is required.
Error Message
CCM_DB_LAYER-DB-3-IDSEngineCritical : Pay Attention. This alarm does not compromise data or prevent the use of the system. Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation Pay Attention. This alarm does not compromise data or prevent the use of the system.
Recommended Action This alarm needs monitoring by the db admin
Error Message
CCM_DB_LAYER-DB-3-IDSEngineFailure : Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm indicates combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail
Recommended Action Requires db admin intervention
Error Message
CCM_DB_LAYER-DB-6-IDSReplicationInformation : Information about IDS replication Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm provides information about IDS replication.
Recommended Action Informational purposes only; no action is required
Error Message
CCM_DB_LAYER-DB-3-IDSReplicationFailure : Combined alarm for emergency and error situations. IDS Replication has failed Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm indicates combined alarm for emergency and error situations. It indicates failure in IDS Replication
Recommended Action Requires db admin intervention
Error Message
CCM_CDR_INSERT-CDRINSERT-3-kDbConnectionFailed : Database connection failed. Additional Information [String]
Explanation An attempt to connect to database failed.
Recommended Action Enable trace for the database layer monitor to get specific error information.
Error Message
CCM_CDR_INSERT-CDRINSERT-1-NoDbConnectionAvailable : No database connection available.
Explanation Database layer could not find any working database connection.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Check network connectivity and operation of SQL Server services.
Error Message
CCM_CDR_INSERT-CDRINSERT-2-ErrorChangeNotifyClientBlock : A change notification client is busy (blocked). If the change notification client continues to be blocked for 10 minutes, the system automatically clears the block and change notification should resume successfully.
Explanation Changes made to the database are not being consumed by one of the recipients. This does not always represent an issue. However, if the change notification client continues to be blocked for 10 minutes, the system automatically clears the block for all clients except the blocked one, which means that change notifications should resume successfully for all other clients. To clear the blocked client, you must restart the server.
Recommended Action At the command line interface (CLI) on the database server, execute the following command: show tech notify. The CLI command output will provide information about the block. Use Cisco Unified Serviceability to restart the server that was indicated in the alarm. You may also want to gather traces to examine them for anomalous activity during the time that client was blocked. In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_CDR_INSERT-CDRINSERT-3-ErrorReadingInstalledRPMS : Could not read installed RPMs to populate component version table
Explanation The function that reads the rpm version information and populates database failed
Recommended Action Please report this error to the administrator.
Error Message
CCM_CDR_INSERT-CDRINSERT-3-ErrorChangeNotifyClientTimeout : A change notification client was responding slowly and has been removed.
Explanation A change notification recipient hasn't responded to change notification in several minutes and was thus removed. This may delay call processing features, such as call forwarding and so on.
Recommended Action Rebooting the box will clear this situation. Alternatively, dbnotify trace could be analyzed to find the client that was removed and that service could be restarted in Cisco Unified Serviceability.
Error Message
CCM_CDR_INSERT-CDRINSERT-1-ErrorChangeNotifyReconcile : A change notification shared memory reconciliation has occurred.
Explanation The change notification buffers in shared memory have been rebuilt due to conflicts.
Recommended Action This problem may have been already corrected. If unexpected behavior is observed, restart all Cisco services in the cluster.
Error Message
CCM_CDR_INSERT-CDRINSERT-6-IDSEngineDebug : Indicates debug events from IDS database engine. Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm provides low-level debugging information from IDS database engine. System administrator can disregard this alarm.
Recommended Action This is for debug information purposes only; no action is required.
Error Message
CCM_CDR_INSERT-CDRINSERT-6-IDSEngineInformation : No error has occurred but some routine event completed in IDS database engine. Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm is informational. No error has occurred but some routine event completed in IDS database engine.
Recommended Action This is for information purposes only; no action is required.
Error Message
CCM_CDR_INSERT-CDRINSERT-3-IDSEngineCritical : Pay Attention. This alarm does not compromise data or prevent the use of the system. Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation Pay Attention. This alarm does not compromise data or prevent the use of the system.
Recommended Action This alarm needs monitoring by the db admin
Error Message
CCM_CDR_INSERT-CDRINSERT-3-IDSEngineFailure : Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm indicates combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail
Recommended Action Requires db admin intervention
Error Message
CCM_CDR_INSERT-CDRINSERT-6-IDSReplicationInformation : Information about IDS replication Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm provides information about IDS replication.
Recommended Action Informational purposes only; no action is required
Error Message
CCM_CDR_INSERT-CDRINSERT-3-IDSReplicationFailure : Combined alarm for emergency and error situations. IDS Replication has failed Event Class ID [String] Event class message [String] Event Specific Message [String]
Explanation This alarm indicates combined alarm for emergency and error situations. It indicates failure in IDS Replication
Recommended Action Requires db admin intervention
Error Message
CCM_CALLMANAGER-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CALLMANAGER-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_CALLMANAGER-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CALLMANAGER-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CALLMANAGER-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_CALLMANAGER-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_TFTP-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_TFTP-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_TFTP-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_TFTP-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_TFTP-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_TFTP-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_TFTP-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_SUMI-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_SUMI-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_SUMI-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_SUMI-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_SUMI-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_SUMI-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_SUMI-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_MEDIA_STREAMING_APP-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_MEDIA_STREAMING_APP-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_MEDIA_STREAMING_APP-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_MEDIA_STREAMING_APP-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_MEDIA_STREAMING_APP-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_MEDIA_STREAMING_APP-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_CTI-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_CTI-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CTI-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_CTI-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CTI-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CTI-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_CTI-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_DB_LAYER-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_DB_LAYER-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_DB_LAYER-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_DB_LAYER-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_DB_LAYER-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_DB_LAYER-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_DB_LAYER-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_CDR_INSERT-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_CDR_INSERT-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CDR_INSERT-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_CDR_INSERT-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CDR_INSERT-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CDR_INSERT-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_CDR_INSERT-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_TCD-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_TCD-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_TCD-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_TCD-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_TCD-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_TCD-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_TCD-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_RIS-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_RIS-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_RIS-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_RIS-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_RIS-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_RIS-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_RIS-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_CBB-GENERIC-0-OutOfMemory : Out of memory.
Explanation The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action No action is required.
Error Message
CCM_CBB-GENERIC-6-PermissionDenied : Permission has been denied.
Explanation An operation could not be completed because the process did not have authority to perform it.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CBB-GENERIC-0-ServiceNotInstalled : Service is not installed. Service Name [String]
Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action Reinstall the service.
Error Message
CCM_CBB-GENERIC-6-ServiceStopped : Service stopped. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]
Explanation A service has stopped.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CBB-GENERIC-6-ServiceStarted : Service started. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]
Explanation A service has started.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_CBB-GENERIC-4-ServiceStartupFailed : Service startup failure. Service Name [String]
Explanation An attempt to start the specified service failed.
Recommended Action Restart the service.
Error Message
CCM_CBB-GENERIC-0-FileWriteError : Cannot write into a file. Primary File Path [String]
Explanation Failed to write into the primary file path.
Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgUserLocaleEnterpriseSvcParm : Error reading enterprise default user locale configuration
Explanation A database exception was encountered when reading the default Enterprise User Locale setting. Default of US English will be used.
Recommended Action Verify that the Enterprise parameter setting for User Locale is configured using the CCM Admin web page. Restart the Cisco IP Voice Media Streaming App service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kANNICMPErrorNotification : ANN stream ICMP port unreachable error. Call ID [ULong] Party ID [ULong] Destination IP Address [String] IP Port [ULong]
Explanation An announcement RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point not having the receiving UDP/RTP port open to receive packets.
Recommended Action No action is required. This may occur at times when connections are being stopped or redirected.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNDeviceRecordNotFound : ANN device record not found.
Explanation A device record for the announcer device was not found in the database. The ANN device is normally automatically added when the server is added to the database.
Recommended Action To add the ANN device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kPWavMgrThreadxFailed : WAV playing manager thread creation failed LastError [ULong] OS Error Description [String]
Explanation The process component used for playing WAV files failed to start, possibly due to low system resources.
Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kPWavMgrExitEventCreateFailed : Creation of needed event failed. Error [ULong]
Explanation The needed events could not be created,; the service will exit.
Recommended Action The service needs to be restarted; if the error occurs again, the system needs to be rebooted.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kPWavMgrThreadException : WAV file manager thread exception Exception Code [ULong] EAX Register [ULong] EBX Register [ULong] ECX Register [ULong] EDX Register [ULong] ESI Register [ULong] EDI Register [ULong] EIP Register [ULong] ESP Register [ULong] EBP Register [ULong] Flags Register [ULong] CS Register [ULong] DS Register [ULong] ES Register [ULong] SS Register [ULong] FS Register [ULong] GS Register [ULong]
Explanation An unknown program exception has caused the background WAV file stream processing for announcement files to terminate.
Recommended Action Restart the Cisco IP Media Streaming App service and if the problem continues, report it to Cisco. Include CMS traces and Application Event log.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-ANNDeviceRecoveryCreateFailed : ANN device recovery create failure. OS Error Code [Int] OS Error Description [String]
Explanation The ANN device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The announcement device will not be available.
Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgANNListUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgANNListComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read ANN device Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgANNListDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgANNUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read ANN device configuration information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgANNComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read ANN device configuration information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgANNDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read ANN device configuration information.
Recommended Action Device will not start; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgEnterpriseException : Enterprisewide configuration exception
Explanation An unknown exception occured reading Enterjprisewide configuration settings.
Recommended Action Verify the enterprise configuration settings and restart the IP Media Streaming Service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kCfgListUnknownException : Unknown Configuration Exception
Explanation An exception error was generated reading the service parameter settings.
Recommended Action Restart the server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kCfgListComException : Configuration COM Exception Exception description [String]
Explanation A COM exception error was generated reading the service parameter settings for devices.
Recommended Action Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kCfgListDblException : Configuration DBL Exception Exception description [String] Exception identifier [ULong]
Explanation An exception error was generated reading the service parameter settings for devices.
Recommended Action Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kANNDeviceStartingDefaults : ANN device configuration not found Parameter Name [String] Value Used [String]
Explanation A service parameter for Cisco IP Voice Media Streaming App service related to the ANN device configuration was not found. The system will start with the given default setting.
Recommended Action Review the service parameter settings and configure the ANN device settings properly using the CUCM Administration.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kRequestedANNStreamsFailed : ANN requested streams failure. Requested streams [ULong] Allocated streams [ULong]
Explanation The requested resources for the configured number of annunciator calls (Call Count service parameter) was not available. If the value shown as "Allocated" is non-zero
Recommended Action Verify the ANN Call Count service parameter is correct. A server restart may be needed to recover resources.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kANNAudioCreateDirFailed : ANN create local path error OS Error Code [ULong] OS Error Text [String] Path Name [String]
Explanation Unable to create a subdirectory to contain announcement files. This may be caused by insufficient disk storage. Announcements may not play correctly as a result of this error.
Recommended Action Check for available free space on the common data storage area. If full, take action to remove old trace files to free space. Restart the Cisco IP Voice Media Streaming App service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioThreadWaitFailed : ANN TFTP event wait error LastError [ULong]
Explanation An error was reported while waiting for a list of events. Announcement files will not be automatically updated.
Recommended Action Restart the Cisco IP Voice Media Streaming App service. If the error continues, restart the serverr.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioThreadException : ANN TFTP transfer exception failure Exception Code [ULong] EAX Register [ULong] EBX Register [ULong] ECX Register [ULong] EDX Register [ULong] ESI Register [ULong] EDI Register [ULong] EIP Register [ULong] ESP Register [ULong] EBP Register [ULong] Flags Register [ULong] CS Register [ULong] DS Register [ULong] ES Register [ULong] SS Register [ULong] FS Register [ULong] GS Register [ULong]
Explanation An unknown program exception has caused the background TFTP file transfer processing for announcement files to terminate. Announcement files will not be automatically updated.
Recommended Action Restart the Cisco IP Media Streaming App service and if the problem continues, report it to Cisco. Include CMS traces and Application Event log.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioThreadxFailed : ANN TFTP transfer thread creation failed LastError [ULong]
Explanation The ANN background TFTP file transfer processing thread failed to create possibly due to low system resources.
Recommended Action Reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioComException : ANN TFTP COM exception File name [String] Reason [String]
Explanation A COM exception occured while processing the specified file.
Recommended Action Review the file for possible format errors or missing elements.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioXmlLoadFailed : ANN XML parsing error File name [String] Reason [String]
Explanation There is a syntax error in the specified file.
Recommended Action Correct the syntax error.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioXmlSyntax : ANN XML invalid element File name [String]
Explanation There is an invalid element in the specified file.
Recommended Action Correct the error.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioTftpFileMissing : ANN TFTP file missing File name [String]
Explanation A file was not found on the TFTP server to be downloaded to the announcement server.
Recommended Action Correct the error.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioTftpMgrStartFailed : TFTP start file transfer failed File name [String]
Explanation Unable to start transfering a file from TFTP server.
Recommended Action Verify the file name exists on the TFTP server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioTftpMgrCreate : Unable to create TFTP client TFTP Server [String]
Explanation Unable to create a client TFTP session with the TFTP server.. This may be due to the server not running, or an incorrect server name configuration setting in service paramenters. This operation will be retried periodically.
Recommended Action Verify the TFTP server is operating and configuration settings are correct.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kANNAudioOpenFailed : Open announcement file failed OS Error Code [ULong] OS Error Description [String] File name [String]
Explanation An error was reported when attempting to open an announcement file for reading.
Recommended Action Verify the file exists and the Cisco IP Voice Media Streaming App service has proper access rights to open the file for reading.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kANNAudioUndefinedLocale : Unknown ANN Locale Locale identifier [ULong] Locale Type [String]
Explanation The requested Locale for an announcement is not installed. For network locale you use the platform CLI interface to run (run sql select * from typecountry where enum = #), #=locale. This will tell you what country locale is being requested.
Recommended Action Install the locale package or check device settings for an incorrect locale value.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kANNAudioUndefinedAnnID : Requested announcement not found Locale name [ULong] Announcement identifier [ULong]
Explanation The requested announcement is unknown. This may be caused by using an incorrect announcement identifier for a custom announcement. Use the CUCM Admin to view a list of custom announcement identifiers and verify the correct one is being used.
Recommended Action Correct the announcement identifier chosen from the custom announcement list.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-CFBDeviceRecoveryCreateFailed : CFB device recovery create failure. OS Error Code [Int] OS Error Description [String]
Explanation The CFB device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The conference bridge device will not be available.
Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kAddIpVmsRenderFailed : Add IP VMS render filter-to-filter graph failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to add the IP VMS render filter-to-filter graph failed; audio source will not play possibly due to the lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kCFBDeviceRecordNotFound : CFB device record not found.
Explanation A device record for the software conference bridge device was not found in the database. The CFB device is normally automatically added when the server is added to the database.
Recommended Action To add the CFB device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kCFBDeviceStartingDefualts : CFB device configuration not found. Parameter Name [String] Value Used [String]
Explanation A service parameter for Cisco IP Voice Media Streaming App service related to the CFB device configuration was not found. The system will use the given default setting.
Recommended Action Review the service parameter settings and configure the CFB device settings properly using the CUCM Administration.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kCFBICMPErrorNotification : CFB stream ICMP error. Call ID [ULong] Party ID [ULong] Destination IP Address [String] IP Port [ULong]
Explanation A SW CFB RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point does not have the receiving UDP/RTP port open to receive packets.
Recommended Action No action is required. This may occur at times when connections are being stopped or redirected.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kChangeNotifyServiceCreationFailed : Database change notification subsystem not starting. OS Error Code [Int] OS Error Description [String]
Explanation The background process to activate database changes has failed to start. Database changes affecting the Cisco IP Voice Media Streaming App service will not automatically take effect.
Recommended Action Restart the Cisco IP Voice Media Streaming App service to get the DB notification reenabled.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kChangeNotifyServiceGetEventFailed : Invalid notification event returned by database change notification. OS Error Code [Int] OS Error Description [String]
Explanation The change notification subsystem returned an invalid notification event. The Cisco IP Voice Media Streaming App service will terminate. The SW media devices (ANN, CFB, MOH, MTP) will be temporarily out of service and calls in progress may be dropped.
Recommended Action Check the current status of the Cisco IP Voice Media Streaming App service and monitor for repeated occurances.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kChangeNotifyServiceRestartFailed : Database change notification restart failure. OS Error Code [Int] OS Error Description [String]
Explanation The change notification subsystem failed to restart.
Recommended Action This service has change notification disabled, it may be reenabled at a later time or restart Cisco IP Voice Media Streaming App service to reenable immediately.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kCreateAudioSourcesFailed : Creating audio source class failed. OS Error Code [Int] OS Error Description [String]
Explanation Unable to create audio source subcombonent to provide audio for streaming. This may be due to lack of memory.
Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kCreateControlFailed : Stream Control create failure. Audio Source ID [ULong] Codec Type [String] OS Error Code [Int] OS Error Description [String]
Explanation Create stream control subcomponent. The error may possibly be due to lack of memory.
Recommended Action Reset the MOH device. If continues to fail restart the Cisco IP Voice Media Streaming App service or restart the server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kCreateGraphManagerFailed : Get graph manager failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the graph manager failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kReadCfgIpTosMediaResourceToCmNotFound : IP TOS MediaResource to Cm value not found.
Explanation The IP Type-of-Service Media Resource To Call Manager service parameter value was not found in the database. Defaulting its value to 0x60 for CS3(precedence 3) DSCP (011000).
Recommended Action Set the Ip Type-of-Service Media Resource To Call Manager service parameter for the Cisco IP Voice Media Streaming App service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceDriverError : IP voice media streaming device driver error. Error [String]
Explanation The IP voice media streaming device driver returned an error. This may indicate a significant media error or resource shortage.
Recommended Action Restarting the Cisco IP Voice Media Streaming App service or possibly restarting the server may resolve the error condition.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceMgrCreateFailed : Device connection manager failed to start. Device Name [String] Server Number [ULong] Server Name [String]
Explanation The device controller was unable to start a connection to control device registration with CallManager. This is possibly due to lack of memory.
Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceMgrExitEventCreationFailed : Creation of device manager exit event failed. Device Name [String] Trace Name [String] Error [ULong] OS Error Text [String]
Explanation An error was reported when allocating an exit-control event for a SW media device. The device will not be registered with CallManager or active.
Recommended Action This error may be due to a memory resource shortage. Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kDeviceMgrLockoutWithCallManager : Cisco Unified Communications Manager in lockout. Trace Name [String]
Explanation The specified Cisco Unified Communications Manager has failed to respond to control messages. The TCP control connection to CUCM is being suspended. This will cause a switch to another CUCM if one is available otherwise the device will be unavailable. There may be a shortage of CPU resource or some other error condition on the CUCM server.
Recommended Action Check the status of the Cisco Unified Communications Manager service. You may have to restart the CUCM service or the CUCM server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-5-kDeviceMgrMoreThan50SocketEvents : More than 50 events returned from TCP link. Trace Name [String]
Explanation The specified Cisco Unified Communications Manager TCP link has returned a large number of TCP events. This indicates an unexpected flood of events.
Recommended Action No action is required. Monitor for reoccurance. This could be an indication of a security issue.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceMgrOpenReceiveFailedOutOfStreams : Open receive failure. Trace Name [String] Conference ID [ULong] Party ID [ULong]
Explanation The open receive channel failed. This may indicate a missmatch of media resources between Cisco Unified Call Manager and the Cisco IP Voice Media Streaming App service.
Recommended Action Check the performance monitor counters for resource availability on CUCM and on Cisco IP Voice Media Streaming App. Also, you might run the Platform CLI command "Show Media Streams" to identify possible media connection resource leaks. Possibly reset the media device or restart Cisco IP Voice Media Streaming App or restart the CUCM server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceMgrRegisterKeepAliveResponseError : Cisco Unified Communications Manager not responding. Trace Name [String]
Explanation The specified Cisco Unified Communications Manager is not responding to the keepalive messages. The connection with CUCM is being terminated and the media device will reregister with another Cisco Unified Call Manager if a secondary is configured. Otherwise, the media device will be unavailable until the device is able to reregister with CUCM.
Recommended Action Cisco Unified Communications Manager may have gone down or is unable to respond. Check status of CUCM. The media device should automatically reregister.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kDeviceMgrRegisterWithCallManager : Registered with Cisco Unified Communications Manager. Trace Name [String]
Explanation The software media device registered with the specified Cisco Unified Communications Manager.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceMgrRegisterWithCallManagerError : Connection error with Cisco Unified Communications Manager. Trace Name [String]
Explanation The media device was registered with the specified Cisco Unified Communications Manager and received a socket error or disconnect. This may occur normally when Cisco Unified Communications Manager is stopped.
Recommended Action No action is required. The media device will reregister.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceMgrSocketDrvNotifyEvtCreateFailed : Create driver notification event failure. Device Name [String] Trace Name [String] Error [ULong] OS Error Description [String]
Explanation An error was returned when creating a signaling event for communication with the media streaming kernel driver. This may be due to memory or system resource shortage.
Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceMgrSocketNotifyEventCreateFailed : Creation socket event failure. Device Name [String] Trace Name [String] Error [ULong] OS Error Description [String]
Explanation An error was reported when creating a notification event for a socket interface. This may be due to a resource shortage. The media device will remain unavailable.
Recommended Action Restart the Cisco IP Voice Media Streaming App service and monitor for reoccurance or restart the CUCM server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceMgrStartTransmissionOutOfStreams : Start transmission failure. Trace Name [String] Conference ID [ULong] Party ID [ULong]
Explanation An error was encountered while starting an RTP transmission audio stream. This may indicate a missmatch of resources between Cisco Unified Communications Manager and Cisco IP Voice Media Streaming App service.
Recommended Action Check the performance counters for the media resources on CUCM and Cisco IP Voice Media Streaming App to determine if there is a resource leak. You should also use the platform CLI command "Show Media Streams" to check for orphaned media RTP connections.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kDeviceMgrThreadException : Exception in device manager thread. Trace Name [String] Exception Code [ULong] EAX Register [ULong] EBX Register [ULong] ECX Register [ULong] EDX Register [ULong] ESI Register [ULong] EDI Register [ULong] EIP Register [ULong] ESP Register [ULong] EBP Register [ULong] Flags Register [ULong] CS Register [ULong] DS Register [ULong] ES Register [ULong] SS Register [ULong] FS Register [ULong] GS Register [ULong]
Explanation An exception occurred in the specified device manager thread.
Recommended Action MOH will automatically reset.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kDeviceMgrThreadWaitFailed : Wait call failure in device manager thread. Trace Name [String] OS Error Code [Int] OS Error Description [String]
Explanation An error was reported during a system request to wait on an event, the media device will be restarted.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kDeviceMgrThreadxFailed : Creation of thread failure. Device Name [String] Trace Name [String] OS Error Code [Int] OS Error Description [String]
Explanation An error was reported when starting a process for the specified media device. This may be due to a system resource shortage.
Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server to recover from this error.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kDeviceMgrUnregisterWithCallManager : Unregister with Cisco Unified Communications Manager. Trace Name [String]
Explanation A media device has unregistered with the specified Cisco Unified Communications Manager.
Recommended Action No action is required. The media device will automatically reregister.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kDownloadMOHFileFailed : Download request failure. File Name [String]
Explanation The TFTP download request failed.
Recommended Action Validate the TFTP IP address in the database and that the file exists.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputAddAudioCaptureDeviceFailed : Add fixed audio source to filter graph failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to add the fixed audio source to the filter graph failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputAddG711AlawIpVmsRenderFailed : Add fixed G711 a-law IP VMS render filter-to-filter graph failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to add the fixed G711 a-law IP VMS render filter-to-filter graph failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputAddG711UlawIpVmsRenderFailed : Add fixed G711 ulaw IP VMS render filter to filter graph failed Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to add the fixed G711 mu-law IP VMS render filter-to-filter graph failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputAddG729IpVmsRenderFailed : Add fixed G729 IP VMS render filter-to-filter graph failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to add the fixed G729 IP VMS render filter-to-filter graph failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputAddMOHEncoderFailed : Add fixed MOH encode filter-to-filter graph failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to add the fixed MOH encode filter-to-filter graph failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputAddWideBandIpVmsRenderFailed : Add fixed wideband IP VMS render filter-to-filter graph failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to add the fixed wideband IP VMS render filter-to-filter graph failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputAudioCapMOHEncoderConnFailed : Connect fixed audio capture device to MOH encoder failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to connect the fixed audio source device to the MOH encoder failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputAudioCaptureCreateFailed : Get fixed system device enumerator failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed system device enumerator failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputClassEnumeratorCreateFailed : Create fixed class enumerator failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to create the fixed class enumerator failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kFixedInputCreateControlFailed : Fixed MOH stream control failed to start. Audio Source ID [ULong] Codec Type [String]
Explanation The audio stream control subsystem for the Fixed MOH audio source failed to start. Audio from the MOH Fixed audio source will not be provided for streaming out. This may be due to resource shortage such as memory or availability of the Fixed MOH audio source device.
Recommended Action Reset MOH device, if failure continues restart the server. Monitor for errors in trace files and system log.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kFixedInputCreateSoundCardFailed : Fixed stream sound card interface failed to start. Audio Source ID [ULong] Codec Type [String]
Explanation An error was encountered when starting the interface to access the sound card for providing MOH fixed audio. The audio source will not play possibly due to shortage of memory.
Recommended Action Reset MOH device, or restart the Cisco IP Voice Media Streaming App service, or restart the server. Check the system log and possibly the traces for Cisco IP Voice Media Streaming App service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kFixedInputInitSoundCardFailed : Fixed stream sound card interface initialization failure. Audio Source ID [ULong] System error code [ULong] Error text [String] Device name [String]
Explanation Initialization of sound card failed. Fixed audio source will not play possibly due to missing or unconfigured USB sound device.
Recommended Action Check that the USB sound is installed. Reset MOH device, or restart Cisco IP Voice Media Streaming App service, or restart the server. The system log and traces from Cisco IP Voice Media Streaming App may contain additionsl information.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kFixedInputCodecStreamFailed : Fixed input codec stream initialization failure. Audio Source ID [ULong] System error code [ULong] Error text [String] Codec Type [String]
Explanation Initialization of sound card codec source transcoding process failed. The fixed audio source will not play possibly due to memory or resource shortage.
Recommended Action Reset MOH device, or restart Cisco IO Voice Media Streaming App service, or restart server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kFixedInputTranscoderFailed : Fixed input audio stream transcoder failure. Audio Source ID [ULong] System error code [ULong] Error text [String]
Explanation An error was encountered while transcoding audio from the sound card. The audio source will not play possibly due an error accessing the sound card.
Recommended Action Check that the USB sound device is properly installed. Unplug the USB sound device and replug back into the USB connector. Reset MOH device, restart Cisco IP Voice Media Streaming App service, or restart the server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputCreateGraphManagerFailed : Get fixed graph manager failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed graph manager failed, and audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputFindAudioCaptureDeviceFailed : Unable to find fixed audio source device. Audio Source ID [ULong] Codec Type [String] Fixed audio source device name [String]
Explanation The specified fixed audio source device was not found; audio source will not play.
Recommended Action Make sure the proper device name is specified.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetEventNotificationFailed : Get fixed notification event failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed notification event failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetFileNameFailed : Get fixed audio source device name failure. Audio Source ID [ULong] Codec Type [String]
Explanation The call to get the fixed audio source device name failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetG711AlawIpVmsRenderFailed : Get fixed G711 a-law IP VMS render filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed G711 a-law IP VMS render filter failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetG711AlawIpVmsRendInfFailed : Get fixed G711 a-law IP VMS render filter private interface failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed G711 a-law IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetG711UlawIpVmsRenderFailed : Get fixed G711 mu-law IP VMS render filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed G711 ulaw ipvms render filter failed, audio source will not play, possibly due to lack of memory.
Recommended Action Reset MOH device, if out of resources reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetG711UlawIpVmsRendInfFailed : Get fixed G711 mu-aw IP VMS render filter private interface failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed G711 mu-law IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetG729IpVmsRenderFailed : Get fixed G729 IP VMS render filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed G729 IP VMS render filter failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetG729IpVmsRendInfFailed : Get fixed G729 IP VMS render filter private interface failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed G729 IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetMediaControlFailed : Get fixed media control failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get fixed media control failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetMediaPositionFailed : Get fixed media position failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get fixed media position failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetMOHEncoderFailed : Get fixed MOH encode filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed MOH encode filter failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetWideBandIpVmsRenderFailed : Get fixed wideband IP VMS render filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed wideband IP VMS render filter failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputGetWideBandIpVmsRendInfFailed : Get fixed wideband IP VMS render filter private interface failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the fixed wideband IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputMOHEncG711AlawRenderConnFail : Connect fixed MOH encoder to G711 a-law IP VMS render filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to connect the fixed MOH encoder to G711 a-law IP VMS render filter failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputMOHEncG711UlawRenderConnFail : Connect fixed MOH encoder to G711 u-law IP VMS render filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to connect the fixed MOH encoder to G711 u-law IP VMS render filter failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputMOHEncG729RenderConnFailed : Connect fixed MOH encoder to G729 IP VMS render filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to connect the fixed MOH encoder to G729 IP VMS render filter failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputMOHEncWidebandRenderConnFail : Connect fixed MOH encoder to wideband IP VMS render filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to connect the fixed MOH encoder to wideband IP VMS render filter failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kFixedInputSetNotifyWindowFailed : Set fixed notify window failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to set the fixed notify window failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kGetEventNotificationFailed : Get notification event failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the notification event failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kGetFileNameFailed : Get audio source file name failure. Audio Source ID [ULong] Codec Type [String]
Explanation The Music-on-Hold audio source is not assigned to an audio file.
Recommended Action Assign the audio source to an audio file or change the value of the MOH audio source to a value that has been configured.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kGetIpVmsRenderFailed : Get IP VMS render filter failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the IP VMS render filter failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kGetIpVmsRenderInterfaceFailed : Get IP VMS render filter private interface failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get the IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kGetMediaControlFailed : Get media control failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get media control failed; audio source will not play, possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kGetMediaPositionFailed : Get media position failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to get media position failed; audio source will not play, possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kIPVMSDeviceDriverNotFound : Cisco IP voice media streaming driver not found.
Explanation The Cisco IP voice media streaming driver was not found or is not installed. The Cisco IP Voice Media Streaming App service cannot run until this error is resolved. All software media devices (ANN, CFB, MOH, MTP) for this server will not be available.
Recommended Action Check the system log for an error when the system attempted to load IpVms driver at the last server startup. A server restart is required to cause the driver to be loaded.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kIPVMSMgrEventCreationFailed : Creation of required signaling event failed. OS Error [ULong] OS Error Description [String]
Explanation An error was encountered when creating a signaling event component. This may be due to a resource shortage. The Cisco IP Voice Media Streaming App service will terminate.
Recommended Action Check the trace files for more information. The service should automatically be restarted. If this error continues to reoccur the server may need to be restarted.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kIpVmsMgrThreadWaitFailed : Error while waiting for asynchronous notifications of events.
Explanation An error was reported while the primary control process for Cisco IP Voice Media Streaming App was waiting on asynchronous events to be signaled. The service will terminate and should automatically be restarted. This will cause a temporary loss of availability for the software media devices (ANN, CFB, MOH, MTP).
Recommended Action Monitor the service and status of the software media devices. The service should automatically restart. If the problem continues, review the trace files for additional information. A server restart may be required if this repeats.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kIpVmsMgrNoLocalHostName : Unable to retrieve the local host server name.
Explanation Unable to obtain the local host server name. The Cisco IP Voice Media Streaming App service will terminate. No software media devices (ANN, CFB, MOH, MTP) will be available while the service is stopped.
Recommended Action Check the configuration settings for the server name, DHCP, or DNS. Monitor the status of Cisco IP Voice Media Streaming App service. The service will not operate without a valid server name.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kIpVmsMgrNoLocalNetworkIPAddr : Unable to retrieve the network IP address for host server.
Explanation Unable to obtain the network IP (dotted) address. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while this service is stopped.
Recommended Action Monitor the status of the Cisco IP Voice Media Streaming App service. It should be automatically restarted. If the error occurs again, check the server IP configuration (DHCP, IP address).
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kIPVMSMgrThreadxFailed : Creation of the IPVMSMgr thread failed. OS Error [ULong] OS Error Description [String]
Explanation An error was encountered while starting a process thread. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.
Recommended Action Monitor the status of the Cisco IP Voice Media Streaming App service. It should automatically be restarted. If the error reoccurs, restart the server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kIPVMSMgrWrongDriverVersion : Wrong version of device driver. Version Found Running [ULong] Version Needed [ULong]
Explanation An incompatible device driver was found. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.
Recommended Action Restart the server to ensure the most recent driver is started. If the error continues, then reinstall Cisco Unified Communications Manager to get the proper driver version installed.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kIPVMSStarting : IP voice media streaming application starting. Version [String] IPAddress [String] Hostname [String] ServiceName [String] ProcessID [ULong]
Explanation The Cisco IP Voice Media Streaming App service is starting.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kIPVMSStopping : The IP voice media streaming application shutting down. Version [String] IPAddress [String] Hostname [String] ServiceName [String] ProcessID [ULong]
Explanation The Cisco IP Voice Media Streaming App service is shutting down.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kMOHBadMulticastIP : Invalid multicast IP address. MOH Audio Source ID [ULong] Call/Conference ID [ULong] Codec Type [String] Multicast IP Address [String] Multicast IP Port [ULong]
Explanation An invalid multicast IP address (out of range) was found.
Recommended Action Correct the setting on the Music-on-Hold device configuration for multicast address.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kMOHDeviceRecordNotFound : MOH device record not found.
Explanation A Music-on-Hold device was not found for this server. This device is normally automatically added when a server is added to the configuration.
Recommended Action If Music-on-Hold functionality is required, you will need to remove and readd server to the database. WARNING: This may impact many other configuration settings (CM Groups, Media Resource Groups, etc...).
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kMOHFilterNotifyError : Error on DirectShow returned or user abort. Audio Source ID [ULong] Codec Type [String]
Explanation The DirectShow filter returned an error or user abort. Audio source may quit playing.
Recommended Action No action is required; audio should start back up when requested to play the next time.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kMOHICMPErrorNotification : MOH stream ICMP error. Call ID [ULong] Party ID [ULong] Destination IP Address [String] IP Port [ULong]
Explanation A Music-on-Hold transmission stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This may occur occasionally depending on call termination sequences.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kMOHMgrCreateFailed : Error starting MOH Audio source subcomponent. OS Error [ULong] OS Error Description [String]
Explanation A error was encountered by the Music-on-Hold device while starting the sub-component that provides audio from files or sound card. This may be due to shortage of resources (memory).
Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kMOHMgrExitEventCreationFailed : Creation of MOH manager exit event failed. OS Error [ULong] OS Error Description [String]
Explanation An error was encountered when allocating a signaling event. This may be caused by a resource shortage.
Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kMOHMgrIsAudioSourceInUseThisIsNULL : Synchronization error detected in MOH audio manager.
Explanation A synchronization error was detected. Condition has been resolved automatically.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kMOHMgrThreadCreateWindowExFailed : Creation of MOH manager message window failure. Error [ULong]
Explanation The creation of the MOH manager message window failed. MOH device is being restarted.
Recommended Action No action is required; if this continues, check whether system is out of resources; reboot system if needed.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kMOHMgrThreadWaitFailed : Wait call failure in MOH manager thread. OS Error [ULong] OS Error Description [String]
Explanation An error was encountered in Music-on-Hold audio manager subcomponent while waiting for aynchronous event signaling. The MOH device will be restarted.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kMOHMgrThreadxFailed : Starting of MOH audio manager failed. OS Error [ULong] OS Error Description [String]
Explanation An error was encountered when starting the Music-on-Hold audio manager subcomponent. Music-on-Hold audio services will not be avaliable.
Recommended Action Restart the Cisco IP Voice Media Streaming App service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kMOHPlayStreamControlNull : Stream Control pointer is NULL Audio Source ID [ULong] Codec Type [String]
Explanation The stream control pointer is null, unable to play stream.
Recommended Action Reset MOH device.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kMOHPlayStreamMediaControlObjectNull : Media Position COM interface is NULL Audio Source ID [ULong] Codec Type [String]
Explanation The media position COM interface is null and unable to play stream.
Recommended Action Reset MOH device.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kMOHRewindStreamControlNull : Attempted to rewind an inactive MOH audio source. Audio Source ID [ULong] Codec Type [String]
Explanation An attempt was made to rewind or restart the Music-on-Hold audio source that is inactive. This has been ignored.
Recommended Action No action required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kMOHRewindStreamMediaPositionObjectNull : Error rewinding MOH audio source that is not playing. Audio Source ID [ULong] Codec Type [String]
Explanation An attempt was made to rewind or restart a Music-on-Hold wav file that was not being played. This has been ignored.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kMOHTFTPGoRequestFailed : Transfer of MOH source file to working path failed. Error Description [String] File Name [String] Source Path [String] Destination Path [String] OS Error Code [Int] OS Error Description [String]
Explanation An error was encountered when trying to copy or update a Music-on-Hold audio source file.
Recommended Action Use the Platform CLI to verify the source path and file exist. If the file does not exist then use CUCMAdmin to reupload the missing audio source to this specific server. Reinstall the Cisco Unified Communications Manager to have all required paths created.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kMOHThreadException : Exception in MOH manager thread. Exception Code [ULong] EAX Register [ULong] EBX Register [ULong] ECX Register [ULong] EDX Register [ULong] ESI Register [ULong] EDI Register [ULong] EIP Register [ULong] ESP Register [ULong] EBP Register [ULong] Flags Register [ULong] CS Register [ULong] DS Register [ULong] ES Register [ULong] SS Register [ULong] FS Register [ULong] GS Register [ULong]
Explanation An exception occurred in MOH manager thread.
Recommended Action MOH will automatically reset.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kMTPDeviceRecordNotFound : MTP device record not found.
Explanation A device record for the software media termination point device was not found in the database. This is normally automatically added to the database when a server is added to the database. The software MTP device will be disabled.
Recommended Action If MTP functionality is required, you will need to delete the server and re-add the server back to the database using CCMAdmin. WARNING: This may require many additional configuration settings to be reapplied such as CallManager Groups, Media Resource groups and more.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kMTPDeviceStartingDefualts : MTP device configuration not found, starting with defaults. MTP Call Count [ULong] MTP Run Flag [String]
Explanation One or more Cisco IP Voice Media Streaming App service parameter settings for the MTP device were not found in the database. The default values are included here.
Recommended Action Configure the service parameter settings for the MTP device.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kMTPICMPErrorNotification : MTP stream ICMP error. Call ID [ULong] Party ID [ULong] Destination IP Address [String] IP Port [ULong]
Explanation An MTP stream had an ICMP error; stream has been terminated.
Recommended Action No action is required.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgCFBComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read CFB configuration information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgCFBDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read CFB configuration information.
Recommended Action Device will not start; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgCFBListComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read CFB Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgCFBListDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read CFB Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgCFBListUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read CFB Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgCFBUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read CFB configuration information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kReadCfgDblGetChgNotifyFailed : Get change notification port failure.
Explanation The database layer was unable to find change notification port and is using default.
Recommended Action If default change notification is incorrect or change notification does not work, add value into database and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgDblGetNodeNameFailed : Database layer select my process node failed.
Explanation The database layer was unable to find/determine the current node on which this service is running.
Recommended Action Make sure the database is configured properly.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHAudioSourceComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read MOH audio sources.
Recommended Action Audio sources will be disabled; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHAudioSourceDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read MOH audio sources.
Recommended Action Audio sources will be disabled; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHAudioSourceUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read MOH audio sources.
Recommended Action Audio sources will be disabled; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read MOH configuration information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read MOH configuration information.
Recommended Action Device will not start; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-kReadCfgMOHEnabledCodecsNotFound : MOH enabled codecs not found.
Explanation The Music-on-Hold service parameter for codec selection could not be read from database. Defaulting to G.711 mu-law codec.
Recommended Action Set the Music-on-Hold service parameter for Cisco IP Voice Media Streaming App service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgEnterpriseComException : COM error. COM Description String [String]
Explanation A COM error occurred while trying to read clsterwide service parameters.
Recommended Action MOH or ANN audio sources may be unavailable; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgEnterpriseDblException : Database exception. Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read clusterwide service parameters.
Recommended Action MOH or ANN audio sources may be unavailable; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgEnterpriseUnknownException : Unknown exception.
Explanation An unknown exception occurred while tring to read clusterwide service parameters.
Recommended Action MOH or ANN audio sources may be unavailable; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHListComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read MOH Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHListDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read MOH Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHListUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read MOH Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHServerComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read MOH device information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHServerDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read MOH device information.
Recommended Action Device will not start; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHServerUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read MOH device information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHTFTIPAddressNotFound : MOH TFTP IP address not found.
Explanation The default MOH TFTP IP address was not found in the database.
Recommended Action Audio sources may be unavailable; create proper value in database and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMOHUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read MOH configuration information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMTPComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read MTP configuration information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMTPDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read MTP configuration information.
Recommended Action Device will not start; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMTPListComException : COM error. Device Name [String] COM Description String [String]
Explanation A COM error occurred while trying to read MTP Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMTPListDblException : Database exception. Device Name [String] Exception String [String] Exception ID [ULong]
Explanation A database exception occurred while trying to read MTP Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix database problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMTPListUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read MTP Cisco Unified Communications Manager list information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgMTPUnknownException : Unknown exception. Device Name [String]
Explanation An unknown exception occurred while trying to read MTP configuration information.
Recommended Action Device will not start; fix problem and restart service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kRenderFileFailed : Render file-to-filter graph failure. Audio Source ID [ULong] Filename [String] Codec Type [String] COM Error [ULong]
Explanation The COM call to render the audio source file-to-filter graph failed; audio source will not play, possibly due to missing audio source or lack of memory.
Recommended Action Check to see if the audio source exists. Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kRequestedCFBStreamsFailed : CFB requested streams failure. Requested streams [ULong] Allocated streams [ULong]
Explanation The resources for the number of requested full-duplex streams was not available.
Recommended Action Verify the Cisco IP Voice Media Streaming App service parameter for number of CFB calls. Restart the server to reset the stream resources.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kRequestedMOHStreamsFailed : MOH requested streams failure. Requested streams [ULong] Allocated streams [ULong]
Explanation The resources for the number of requested streams was not available.
Recommended Action Verify the number of calls configuration setting for Music-on-Hold device. Restart the server to reset the resources.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kRequestedMTPStreamsFailed : MTP requested streams failure. Requested streams [ULong] Allocated streams [ULong]
Explanation The resources for the number of requested full-duplex Media Termination Point streams was not available.
Recommended Action Verify the Cisco IP Voice Media Streaming App service parameter setting for number of MTP calls is correct. Restart the server to reset the available resources.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-3-kSetNotifyWindowFailed : Set notify window failure. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]
Explanation The COM call to set the notify window failed; audio source will not play possibly due to lack of memory.
Recommended Action Reset MOH device; if out of resources, reboot server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-MOHDeviceRecoveryCreateFailed : MOH device recovery create failure. OS Error Code [ULong] OS Error Description [String]
Explanation An error was encountered restarting the Music-on-Hold device. This may be caused by a shortage of memory resources.
Recommended Action Check the status of the Music-on-Hold device. If the MOH device is not registered and available, Restart the Cisco IP Voice Media Streaming App service or restart the server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-MTPDeviceRecoveryCreateFailed : MTP device recovery create failure. OS Error Code [ULong] OS Error Description [String]
Explanation An error was encountered trying to restart the Media Termination Point device. This may be due to a shortage of application memory.
Recommended Action Restart the IP Voice Media Streaming App service or restart the server.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-SoftwareLicenseNotValid : Invalid Software License.
Explanation There is no valid software license; the Cisco IP Voice Media Streaming App service requires a valid software license to operate.
Recommended Action Install a valid software license and restart Cisco IP Voice Media Streaming App service.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-6-SoftwareLicenseValid : Valid Software License Found.
Explanation A valid software license has been detected by the IP Voice Media Streaming App service.
Recommended Action No action required. This informational message indicates alarm SoftwareLicenseNotValid is cleared.
Error Message
CCM_MEDIA_STREAMING_APP-IPVMS-4-kANNAudioFileMissing : Announcement file not found. Missing filename [String] Announcement Identifier [ULong] User locale [ULong] Network locale [ULong]
Explanation The annunciator was unable to access an announcement audio file. This may be caused by not uploading a custom announcement to each server in the cluster or a locale has not been installed on the server.
Recommended Action Upload the custom announcement to the server or install the missing locale package.
Error Message
CCM_TFTP-TFTP-1-CreateThreadFailed : Failed to create a new thread. See Reason string for where it failed. Error [Int] Reason [String]
Explanation This usually happens when there are system issues such as running out of memory resources.
Recommended Action Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.
Error Message
CCM_TFTP-TFTP-1-SDIControlLayerFailed : Failed to update trace logging or alarm subsystem for new settings. Error [Int] Reason [String]
Explanation This usually indicates a lack of system resources or a failure in database access by the trace logging or alarm subsystem.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm. Ensure that the database server is running, and that the Cisco Database Layer Monitor service is running without problems. If this alarm persists, contact the Cisco Technical Assistance Center (TAC) with TFTP service and database trace files.
Error Message
CCM_TFTP-TFTP-3-ConfigThreadReadConfigurationFailed : Failed to retrieve enterprise parameter values from database at TFTP service startup.
Explanation This is usually caused by database access failure.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_TFTP-TFTP-3-ConfigThreadBuildFileFailed : Failed to build all device configuration files at TFTP service startup.
Explanation This is usually caused by database access failure.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_TFTP-TFTP-1-ConfigThreadChangeNotifyServerInstanceFailed : Failed to allocate resources to handle configuration change notification from database.
Explanation This usually indicates a lack of memory when there is a system issue such as running out of resources.
Recommended Action Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.
Error Message
CCM_TFTP-TFTP-1-ConfigThreadChangeNotifyServerSingleFailed : Failed to allocate resources to handle configuration change notification from database.
Explanation This usually indicates a lack of memory when there is a system issue such as running out of resources.
Recommended Action Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.
Error Message
CCM_TFTP-TFTP-1-ConfigThreadChangeNotifyServerStartFailed : Failed to start listening to configuration change notification from database.
Explanation This usually indicates a lack of memory when there is a system issue such as running out of resources.
Recommended Action Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.
Error Message
CCM_TFTP-TFTP-3-ConfigThreadCNCMGrpBuildFileFailed : Failed to rebuild configuration files for changes in Cisco Unified Communications Manager Group settings.
Explanation This is usually caused by a failure to access the Cisco Unified Communications Manager database.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_TFTP-TFTP-3-ConfigThreadCNGrpBuildFileFailed : Failed to rebuild configuration files for changes at group level settings such as Device Pool or Common Device Config settings.
Explanation This is usually caused by a failure to access the Cisco Unified Communications Manager database.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_TFTP-TFTP-3-ConfigThreadUnknownExceptionCaught : An exception is caught in the main processing routine.
Explanation This alarm is sent in conjunction with other alarms for failure when building configuration files or when the TFTP service is attempting to retrieve the values in the system's enterprise parameters.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_TFTP-TFTP-3-ReadConfigurationUnknownException : An exception is caught while retrieving enterprise parameters value from database at TFTP service startup.
Explanation This is usually caused by a failure to access the Cisco Unified Communications Manager database.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_TFTP-TFTP-3-ConfigItAllReadConfigurationFailed : Failed to retrieve enterprise parameter values from database when rebuilding all configuration files.
Explanation This is usually caused by a failure to access the Cisco Unified Communications Manager database.
Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_TFTP-TFTP-3-ConfigItAllBuildFilesFailed : A complete rebuild of all device configuration files has failed.
Explanation Probable causes of this alarm could be failure to access the Cisco Unified Communications Manager database, or misconfiguration of some devices.
Recommended Action In Cisco Unified Serviceability, enabled Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.
Error Message
CCM_TFTP-TFTP-1-SocketError : Failed to open network connection for receiving file requests. nError [Int] Reason [String]
Explanation This usually happens when the IP address that the TFTP service uses to open the network connection is invalid.
Recommended Action Verify that the TFTP service parameter, TFTP IP Address, accurately specifies the IP address of the NIC card to use for serving files via TFTP. See the help for the (advanced) TFTP IP Address service parameter for more information. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).
Error Message
CCM_TFTP-TFTP-1-TFTPServerListenSetSockOptFailed : Failed to increase the size of the network buffer for receiving file requests. nError [Int] IPAddress [String] Port [Int]
Explanation This usually indicates a lack of memory when there is a system issue such as running out of resources.
Recommended Action Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.
Error Message
CCM_TFTP-TFTP-1-TFTPServerListenBindFailed : Fail to connect to the network port through which file requests are received. nError [Int] IPAddress [String] Port [Int]
Explanation This usually happens if the network port is being used by other applications on the system or if the port was not closed properly in the last execution of TFTP server.
Recommended Action Verify that the port is not in use by other application. After stopping the TFTP server, at the command line interface (CLI) on the TFTP server, execute the following command: show network status listen. If the port number specified in this alarm is shown in this CLI command output, the port is being used. Restart the Cisco Unified Communications Manager system, which may help to release the port. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).
Error Message
CCM_TFTP-TFTP-4-NoCallManagerFound : No Cisco Unified Communications Manager (Unified CM, formerly known as Cisco Unified CallManager) node has been configured. Error [String]
Explanation A Cisco Unified Communications Manager Group exists but it has no Unified CM node configured as its group member.
Recommended Action In Cisco Unified CM Administration (System > Cisco Unified CM Group), configure at least one Unified CM node for the Unified CM Group referenced in this alarm. The Unified CM Group is part of the device pool to which the specified phone belongs.
Error Message
CCM_TFTP-TFTP-3-CNFFBuffWriteToFilefopenfailed : Failed to create Config File on disk or update existing Config File on disk. FileName [String]
Explanation This may happen if disk is full or the file is in use.
Recommended Action Using RTMT, check the disk utilization and correct any issue discovered. If you do not discover a disk space issue, try restarting the TFTP service from Cisco Unified Serviceability (Tools > Control Center - Feature Services). Stopping and restarting the TFTP service is useful because the Config File that the TFTP service is trying to save might be an existing file that is in use. If you still get this error, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).
Error Message
CCM_TFTP-TFTP-3-CNFFBuffWriteToFilefwritefailed : Failed to save Config File to disk. FileName [String]
Explanation This may happen if disk is full or the file is in use.
Recommended Action Using RTMT, check the disk utilization and correct any issue discovered. If you do not discover a disk space issue, try restarting the TFTP service from Cisco Unified Serviceability (Tools > Control Center - Feature Services). Stopping and restarting the TFTP service is useful because the Config File that the TFTP service is trying to save might be an existing file that is in use. If you still get this error, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).
Error Message
CCM_TFTP-TFTP-4-ServingFileWarning : There was an error during processing of file request. ErrorNumber [Int] FileName [String] IPAddress_Port [String] Mode [String] OpCode [Int] Reason [String]
Explanation This could happen if the requested file is not found by the server, or other error indicated by the "Reason" clause when processing the file request.
Recommended Action You can safely ignore this alarm if the reason shown in this alarm is "File not found" and if that file is the MAC address-based file name for a phone that you are auto-registering; in that case, the phone is not yet registered with the database and so it is normal for the phone's file not be found. In the case that auto-registration is disabled, this alarm shows that the phone or device is not added to Cisco Unified Communications Manager (Unified CM). Either add the phone to Unified CM or remove the phone from the network. If you still get this error after removing the phone(s), go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).
Error Message
CCM_TFTP-TFTP-3-ThreadPoolProxyUnknownException : Unknown exception was caught while processing file request.
Explanation This usually indicates a lack of memory when there is a system issue such as running out of resources.
Recommended Action Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.
Error Message
CCM_TFTP-TFTP-6-BuildStat : Device configuration files are being built. DeviceCount [Int] DeviceTime [Int] UnitCount [Int] UnitTime [Int] SoftkeyCount [Int] SoftkeyTime [Int] FeatureControlPolicyTime [Int] FeatureControlPolicyCount [Int] DialruleCount [Int] DialruleTime [Int] TotalTime [Int] BuildStatus [String]
Explanation This alarm provides information about the BUILD ALL operation to build all types of configuration files.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_TFTP-TFTP-3-IPv6InterfaceNotInstalled : IPv6 network interface is not installed.
Explanation IPv6 option is enabled for TFTP service but the IPv6 network interface/address has not been configured on the system. Until the IPv6 network is functioning, devices that have been configured with IPv6-only will not be able to register. Devices that have been configured to use either IPv6 or IPv4 will register using IPv4. When the IPv6 network is online, IPv6-capable devices that have registered as IPv4 will remain IPv4 until they are reset, at which time they will use IPv6 if available.
Recommended Action Install IPv6 network interface and then restart TFTP service.
Error Message
CCM_CBB-CALLBACK-4-QRTRequest : User submitted problem report using Quality Report Tool. Category [String] Reason Code [String] Report Timestamp [String] Device name. [String] Device IP address. [String] Directory number [String]
Explanation User has experienced a problem with Phone and has submitted problem report.
Recommended Action Investigate the cause for problem report.
Error Message
CCM_RTMT-RTMT-3-RTMT_ALERT : RTMT Alert Name [String] Detail [String]
Explanation A Real-Time Monitoring Tool (RTMT) process in the AMC service uses the alarm mechanism to facilitate delivery of RTMT alerts in RTMT AlertCentral or via email.
Recommended Action Check AlertCentral in RTMT or any alerts that you have received via email to determine what issue has occurred and learn the recommended actions to resolve it. In AlertCentral, right-click the alert to open the alert information.
Error Message
CCM_CDR_REP-CDRREP-3-CDRFileDeliveryFailed : (s)FTP delivery of CDR files to the outside billing server failed. BillingServerAddress [String]
Explanation (s)FTP develiry of CDR files to the Billing Server outside of the cluster failed because of timeout or other reasons. Email alert will be sent to the admin.
Recommended Action 1. Check network link status. 2. Check if billing server is alive. 3. Check if (s)FTP Server on the billing server is running and accepting request. 4. Check if CDRM Configuration is correct - under Serviceability->Tools. 5. check CDR Repository Manager trace.
Error Message
CCM_CDR_REP-CDRREP-3-CDRAgentSendFileFailed : CDR Agent cannot send CDR files from CCM node to CDR Repository node within the CCM cluster CDRRepositoryNodeAddress [String] CDRAgentNodeAddress [String]
Explanation CDR Agent cannot send CDR files from CCM node to CDR Repository node within the cluster because of timeout or other reasons. Email alert will be sent to the admin.
Recommended Action 1. Check network link status. 2. Check if CDR Repository node (first node in the cluster) is alive. 3. Check if CDR Repository Manager is activated on the first node. 4. Check CDRM Configuration under Serviceability->Tools. 5. Check CDR Agent trace on the specific node where error occurred. 6. Check CDR Repository Manager trace. 7. Check if the Publisher is being upgraded. If the CDRAgentSendFileFailureContinues alarm is no longer present, the condition is corrected.
Error Message
CCM_CDR_REP-CDRREP-4-CDRHWMExceeded : High Water Mark for CDR files reached, some successfully delivered CDR files have been deleted DiskUsageInMB [String]
Explanation The CDR files disk usage has exceeded the High Water Mark. CDRM deleted some successfully delivered CDR files that are still within the preservation duration, in order to bring the disk usage down to below HWM. Email alert will be sent to the admin.
Recommended Action 1. The preservation duration may be too long. Reduce it at Serviceability->Tools->CDR Management. 2. Or to raise maximum allocated disk space and/or HWM for CDR files.
Error Message
CCM_CDR_REP-CDRREP-2-CDRMaximumDiskSpaceExceeded : The CDR files disk usage exceeded maximum disk allocation. Some undelivered files may have been deleted to bring disk usage down. DiskUsageInMB [String]
Explanation The CDR files disk usage has exceeded the maximum allocated disk space. CDRM may have deleted some CDR files that have not been sent to the outside billing servers yet, in order to bring the disk usage down to below High Water Mark. The decision whether to delete undelivered files or not depends on how deletionDisable flag is configured at CDRM Configuration page. Email alert will be sent to the admin.
Recommended Action 1. Check if there are too many undelivered CDR files accumulated due to some condition. 2. Check network link status. 3. Check if billing server is alive. 4. Check if (s)FTP Server on the billing server is running and accepting request. 5. Check if CDRM Configuration for billing servers is correct - under Serviceability->Tools. 6. Check if CDR files maximum disk allocation is too low - under Serviceability->Tools. 7. Check CDR Repository Manager trace under /var/log/active/cm/trace/cdrrep/log4j.
Error Message
CCM_CDR_REP-CDRREP-3-CDRFileDeliveryFailureContinues : (s)FTP delivery of CDR files failed on retries. BillingServerAddress [String]
Explanation (s)FTP develiry of CDR files to the Billing Server outside of the cluster failed on retries after the initial failure.
Recommended Action 1. Check network link status. 2. Check if billing server is alive. 3. Check if (s)FTP Server on the billing server is running and accepting request. 4. Check if CDRM Configuration is correct - under Serviceability->Tools. 5. check CDR Repository Manager trace.
Error Message
CCM_CDR_REP-CDRREP-3-CDRAgentSendFileFailureContinues : CDR Agent cannot send CDR files from CCM node to CDR Repository node on retries. CDRRepositoryNodeAddress [String] CDRAgentNodeAddress [String]
Explanation CDR Agent cannot send CDR files on retries after the initial failure from CCM node to CDR Repository node within the cluster.
Recommended Action 1. Check network link status. 2. Check if CDR Repository node (first node in the cluster) is alive. 3. Check if CDR Repository Manager is activated on the first node. 4. Check CDRM Configuration under Serviceability->Tools. 5. Check CDR Agent trace on the specific node where error occurred. 6. Check CDR Repository Manager trace. 7. Check if the Publisher is being upgraded.
Error Message
CCM_TCT-LPMTCT-4-LogPartitionLowWaterMarkExceeded : The percentage of used disk space in the log partition has exceeded the configured low water mark. UsedDiskSpace [String] MessageString [Optional]. [String]
Explanation The percentage of used disk space in the log partition has exceeded the configured low water mark.
Recommended Action Login into RTMT and check the configured threshold value for LogPartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each of the application in trace configuration page under CCM Serviceability. If the number of configured traces / logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old. You can clean up the traces using cli "file delete" or using Remote Browse from RTMT Trace and Log Central function.
Error Message
CCM_TCT-LPMTCT-2-LogPartitionHighWaterMarkExceeded : The percentage of used disk space in the log partition has exceeded the configured high water mark. UsedDiskSpace [String] MessageString [Optional]. [String]
Explanation The percentage of used disk space in the log partition has exceeded the configured high water mark. Some of the core file and / or trace files will be purged until the percentage of used disk space in the log partition gets below the configured low water mark.
Recommended Action Login into RTMT and check the configured threshold value for LogPartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the 1st alert, check for the disk usage for Common partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in LogPartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition.
Error Message
CCM_TCT-LPMTCT-6-LogFileSearchStringFound : The search string has been found in the log file. SearchString [String]
Explanation Trace and Log Central has found the search string that the user has configured
Recommended Action If sysadmin is interested in collecting the traces around the time of generation of alert, use Trace and Log Central to collect the traces for that service.
Error Message
CCM_TCT-LPMTCT-4-LogCollectionJobLimitExceeded : The number of Log Collection Jobs have excceded the allowed limit JobType [String]
Explanation The number of concurrent trace collection from the server has exceeded the allowed limit of trace collection. The allowed limit is defined in the documentation for Trace and Log Central, however this limit can not be changed by sysadmin.
Recommended Action Cancel one or more of the currently running queries and try again to configure the trace collection.
Error Message
CCM_TCT-LPMTCT-3-ScheduledCollectionError : An error occurred while executing scheduled collection. JobID [String] Reason [String]
Explanation Scheduled collection encountered an error during execution.
Recommended Action Review configuration for scheduled collection job under Job Status window.
Error Message
CCM_TCT-LPMTCT-2-CoreDumpFileFound : The new core dump file(s) have been found in the system. TotalCoresFound [String] CoreDetails [String] Core1 [String] Core2 [String] Core3 [String] Core4 [String] Core5 [String] Core6 [String]
Explanation One of the component has crashed and generated a core dump. Use admin cli or RTMT to featch the backtrace.
Recommended Action This serious internal error should be investigated by the Cisco Technical Assistance Center (TAC). Before contacting TAC, Login to cli on CCM serve and run "active analyze core file name" to generate the backtrace of the core dump. The core file name is listed in the alert details. After the analyze command is executed, collect the backtrace using cli command "file get activelog analyze" or "Collect Traces" option from RTMT. Send these backtraces to Cisco TAC for further analysis.
Error Message
CCM_TCT-LPMTCT-3-SparePartitionLowWaterMarkExceeded : The percentage of used disk space in the spare partition has exceeded the configured low water mark. UsedDiskSpace [String] MessageString [Optional]. [String]
Explanation The percentage of used disk space in the spare partition has exceeded the configured low water mark.
Recommended Action Login into RTMT and check the configured threshold value for SparePartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each of the application in trace configuration page under CCM Serviceability. If the number of configured traces / logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old. You can clean up the traces using cli "file delete" or using Remote Browse from RTMT Trace and Log Central function.
Error Message
CCM_TCT-LPMTCT-4-SparePartitionHighWaterMarkExceeded : The percentage of used disk space in the spare partition has exceeded the configured high water mark. UsedDiskSpace [String] MessageString [Optional]. [String]
Explanation The percentage of used disk space in the spare partition has exceeded the configured high water mark. Some of the trace files will be purged until the percentage of used disk space in the spare partition gets below the configured low water mark
Recommended Action Login into RTMT and cheek the configured threshold value for SparePartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the 1st alert, check for the disk usage for Spare partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in SparePartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition.
Error Message
CCM_LPM-LPMTCT-4-LogPartitionLowWaterMarkExceeded : The percentage of used disk space in the log partition has exceeded the configured low water mark. UsedDiskSpace [String] MessageString [Optional]. [String]
Explanation The percentage of used disk space in the log partition has exceeded the configured low water mark.
Recommended Action Login into RTMT and check the configured threshold value for LogPartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each of the application in trace configuration page under CCM Serviceability. If the number of configured traces / logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old. You can clean up the traces using cli "file delete" or using Remote Browse from RTMT Trace and Log Central function.
Error Message
CCM_LPM-LPMTCT-2-LogPartitionHighWaterMarkExceeded : The percentage of used disk space in the log partition has exceeded the configured high water mark. UsedDiskSpace [String] MessageString [Optional]. [String]
Explanation The percentage of used disk space in the log partition has exceeded the configured high water mark. Some of the core file and / or trace files will be purged until the percentage of used disk space in the log partition gets below the configured low water mark.
Recommended Action Login into RTMT and check the configured threshold value for LogPartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the 1st alert, check for the disk usage for Common partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in LogPartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition.
Error Message
CCM_LPM-LPMTCT-6-LogFileSearchStringFound : The search string has been found in the log file. SearchString [String]
Explanation Trace and Log Central has found the search string that the user has configured
Recommended Action If sysadmin is interested in collecting the traces around the time of generation of alert, use Trace and Log Central to collect the traces for that service.
Error Message
CCM_LPM-LPMTCT-4-LogCollectionJobLimitExceeded : The number of Log Collection Jobs have excceded the allowed limit JobType [String]
Explanation The number of concurrent trace collection from the server has exceeded the allowed limit of trace collection. The allowed limit is defined in the documentation for Trace and Log Central, however this limit can not be changed by sysadmin.
Recommended Action Cancel one or more of the currently running queries and try again to configure the trace collection.
Error Message
CCM_LPM-LPMTCT-3-ScheduledCollectionError : An error occurred while executing scheduled collection. JobID [String] Reason [String]
Explanation Scheduled collection encountered an error during execution.
Recommended Action Review configuration for scheduled collection job under Job Status window.
Error Message
CCM_LPM-LPMTCT-2-CoreDumpFileFound : The new core dump file(s) have been found in the system. TotalCoresFound [String] CoreDetails [String] Core1 [String] Core2 [String] Core3 [String] Core4 [String] Core5 [String] Core6 [String]
Explanation One of the component has crashed and generated a core dump. Use admin cli or RTMT to featch the backtrace.
Recommended Action This serious internal error should be investigated by the Cisco Technical Assistance Center (TAC). Before contacting TAC, Login to cli on CCM serve and run "active analyze core file name" to generate the backtrace of the core dump. The core file name is listed in the alert details. After the analyze command is executed, collect the backtrace using cli command "file get activelog analyze" or "Collect Traces" option from RTMT. Send these backtraces to Cisco TAC for further analysis.
Error Message
CCM_LPM-LPMTCT-3-SparePartitionLowWaterMarkExceeded : The percentage of used disk space in the spare partition has exceeded the configured low water mark. UsedDiskSpace [String] MessageString [Optional]. [String]
Explanation The percentage of used disk space in the spare partition has exceeded the configured low water mark.
Recommended Action Login into RTMT and check the configured threshold value for SparePartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each of the application in trace configuration page under CCM Serviceability. If the number of configured traces / logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old. You can clean up the traces using cli "file delete" or using Remote Browse from RTMT Trace and Log Central function.
Error Message
CCM_LPM-LPMTCT-4-SparePartitionHighWaterMarkExceeded : The percentage of used disk space in the spare partition has exceeded the configured high water mark. UsedDiskSpace [String] MessageString [Optional]. [String]
Explanation The percentage of used disk space in the spare partition has exceeded the configured high water mark. Some of the trace files will be purged until the percentage of used disk space in the spare partition gets below the configured low water mark
Recommended Action Login into RTMT and cheek the configured threshold value for SparePartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the 1st alert, check for the disk usage for Spare partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in SparePartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-TestAlarmInformational : Testing INFORMATIONAL_ALARM
Explanation Test Alarm
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-0-TestAlarmEmergency : Testing EMERGENCY_ALARM
Explanation Test Alarm
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-1-TestAlarmAlert : Testing ALERT_ALARM
Explanation Test Alarm
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-TestAlarmCritical : Testing CRITICAL_ALARM
Explanation Test Alarm
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-7-TestAlarmDebug : Testing DEBUG_ALARM
Explanation Test Alarm
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-TestAlarmError : Testing ERROR_ALARM
Explanation Test Alarm
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-TestAlarmNotice : Testing NOTICE_ALARM
Explanation Test Alarm
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-TestAlarmWarning : Testing WARNING_ALARM
Explanation Test Alarm
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-TestAlarmWindows : Testing INFORMATIONAL_ALARM
Explanation Test Alarm for Windows OS based server Only.
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-TestAlarmAppliance : Testing INFORMATIONAL_ALARM
Explanation Test Alarm for Appliance OS based server Only.
Recommended Action No action required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-TotalProcessesAndThreadsExceededThresholdStart : The current total number of processes and threads has exceeded the maximum number of tasks configured for Cisco RIS Data Collector service parameter. This situation could indicate some process is leaking or some process has thread leaking. NumberOfProcesses [String] NumberOfThreads [String] Reason [String] ProcessWithMostInstances [String] ProcessWithMostThreads [String]
Explanation The current total number of processes and threads has exceeded the maximum number of tasks. This situation could indicate some process is leaking or some process has thread leaking.
Recommended Action Check the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads, to see if the parameter has been set to a low value. If it has been, set the value higher or use the default value. Another possible action is that when a new Cisco product is integrated into Cisco Unified Communications Manager (Unified CM), new processes or threads are added to the system. Even in the normal process load situation, it's possible that the total number of processes and threads has exceeded the configured or default value of the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. Set that parameter to the maximum allowed value. You can also review the details of this alarm to check the ProcessWithMostThreads description and the ProcessWithMostInstances description to discover which processes have the most threads and the most instances. Determine whether these values are reasonable for this process; if not, contact the owner of the process for troubleshooting the reasons why the thread count or the number of process instances is so high. It is also possible that Cisco RIS Data Collector sent a false alarm, which would indicate a defect in the Cisco RIS Data Collector service. To determine if this is the cause of the alarm - after you have checked all the other recommended actions described here - use RTMT to check the System object for performance counters Total Threads and Total Processes to confirm that the values in those counters do not exceed the value configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. If the counters do not show a value that is higher than what is configured in the service parameter, restart Cisco RIS Data Collector service. If the alarm persists after restarting the service, go to Cisco Unified Serviceability and collect trace logs (Trace > Configuration) for Cisco Syslog, Cisco RIS Data Collector, Cisco AMC Service, and Cisco RIS Perfmon Logs and contact Cisco Technical Assistance Center (TAC) for detailed assistance.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-TotalProcessesAndThreadsExceededThresholdEnd : The current total number of processes and threads is less than the maximum number of tasks configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. NumberOfProcesses [String] NumberOfThreads [String] Reason [String]
Explanation The current total number of processes and threads is less than the maximum number of tasks that has been configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. This can occur because a product which was integrated into Cisco Unified Communications Manager has been disabled or deactivated, which reduces the total number of processes and threads running on the system. Another cause for the number of processes or thread to decrease is that one or more processes has been stopped, which reduces the total number of processes and threads running on the system.
Recommended Action This alarm is for information purposes only; no action is required.
Error Message
CCM_DRF_MASTER-DRF-3-DRFTruststoreMissing : DRF uses ipsec truststore certificate for securing communication between the MA and LA service. This certificate is missing on the node Reason [String]
Explanation DRF uses ipsec truststore certificate for securing communication between the MA and LA service. This certificate is missing on the node, DRF LA will not be able to connect to MA
Recommended Action Download ipsec.pem file from Publisher and upload it as ipsec-trust only on the missing node then restart Cisco DRF Local service.
Error Message
CCM_DRF_MASTER-DRF-3-DRFUnknownClient : The DRF Master Agent running on the Publisher has received a Client connection request from an unknown server outside the cluster.The request has been rejected Reason [String]
Explanation The DRF Master Agent running on the Publisher has received a Client connection request from an unknown server outside the cluster.The request has been rejected.
Recommended Action Remove the suspect server from the network. Refer to the Reason section for suspect servers: Hostname and IP Address
Error Message
CCM_DRF_MASTER-DRF-3-DRFSecurityViolation : The DRF System has detected a malicious pattern which could result in a security violation Reason [String]
Explanation The DRF Network Message contains a malicious pattern which could result in a security violation like code injection or directory traversal. DRF Network Message has been blocked.
Recommended Action Stop the Cisco DRF Master and Cisco DRF Local Agent Services
Error Message
CCM_DRF_MASTER-DRF-3-DRFMasterAgentStartFailure : DRF Master Agent was unable to start because it was unable to open port 4040. Reason [String]
Explanation DRF Master Agent was unable to start because it was unable to open port 4040.
Recommended Action Check if port 4040 is not already in use.
Error Message
CCM_DRF_MASTER-DRF-3-DRFLocalAgentStartFailure : DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port 4040 Reason [String]
Explanation DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port 4040
Recommended Action Check if the CiscoDRFMaster and CiscoDRFLocal services are running
Error Message
CCM_DRF_MASTER-DRF-3-DRFLA2MAFailure : DRF Local Agent is not able to connect to Master Agent. Reason [String]
Explanation DRF Local Agent is not able to connect to Master Agent.
Recommended Action Check if the Master Agent is up and the port is authorized.
Error Message
CCM_DRF_MASTER-DRF-3-DRFMA2LAFailure : Master Agent was unable to send a backup/restore request to the local agent. Reason [String]
Explanation Master Agent was unable to send a backup/restore request to the local agent.
Recommended Action Restart the corresponding local agents and the master agent.
Error Message
CCM_DRF_MASTER-DRF-3-DRFBackupFailure : Cisco DRF Backup process failed. Reason [String]
Explanation DRF Backup process encountered errors.
Recommended Action Check DRF logs for further details.
Error Message
CCM_DRF_MASTER-DRF-3-DRFRestoreFailure : DRF Restore process failed. Reason [String]
Explanation DRF Restore process encountered errors.
Recommended Action Check DRF logs for further details.
Error Message
CCM_DRF_MASTER-DRF-3-DRFBackupDeviceError : DRF Backup process is failed due to backup device error. Reason [String]
Explanation DRF Backup process is failed due to backup device error.
Recommended Action Check if the proper device has been specified in the DRF configurations.
Error Message
CCM_DRF_MASTER-DRF-3-DRFTapeDeviceError : DRF is unable to access tape device. Reason [String]
Explanation DRF is unable to access tape device.
Recommended Action Check if tape drive is working properly and it contains a valid tape.
Error Message
CCM_DRF_MASTER-DRF-3-DRFLocalDeviceError : DRF is unable to access local device. Reason [String]
Explanation DRF is unable to access local device.
Recommended Action Check if local location exists and is accessible.
Error Message
CCM_DRF_MASTER-DRF-3-DRFInternalProcessFailure : DRF internal process has encountered an error. Reason [String]
Explanation DRF internal process has encountered an error.
Recommended Action Check DRF logs for details.
Error Message
CCM_DRF_MASTER-DRF-3-DRFRestoreInternalError : DRF Restore operation has encountered an error. Restore cancelled internally. Reason [String]
Explanation DRF Restore operation has encountered an error. Restore cancelled internally.
Recommended Action Check DRF logs for details.
Error Message
CCM_DRF_MASTER-DRF-3-DRFMABackupComponentFailure : DRF was unable to backup at least one component. Reason [String]
Explanation DRF requested a component to backup its' data. However, there was an error during the backup process and the component was not backed up.
Recommended Action Please check the component backup logs and contact support if needed.
Error Message
CCM_DRF_MASTER-DRF-3-DRFMARestoreComponentFailure : DRF was unable to restore at least one component. Reason [String]
Explanation DRF requested a component to restore its' data. However, there was an error during the restore process and the component was not restored.
Recommended Action Please check the component restore logs and contact support if needed.
Error Message
CCM_DRF_MASTER-DRF-3-DRFMABackupNodeDisconnect : The node being backed up disconnected from the Master Agent prior to being fully backed up. Reason [String]
Explanation The DRF Master Agent was running a backup operation on a CCM cluster, when one of the nodes disconnected before the backup operation was completed.
Recommended Action Please check the computer that disconnected during backup. If the computer was accidentally shutdown, restart the backup.
Error Message
CCM_DRF_MASTER-DRF-3-DRFNoRegisteredComponent : No registered components available, backup failed. Reason [String]
Explanation DRF backup failed since no registered components are available.
Recommended Action Ensure at least one component is registered before attempting a backup.
Error Message
CCM_DRF_MASTER-DRF-3-DRFNoRegisteredFeature : No feature selected for backup. Reason [String]
Explanation No feature selected for backup
Recommended Action Ensure at least one feature is configured before attempting a backup.
Error Message
CCM_DRF_MASTER-DRF-3-DRFMARestoreNodeDisconnect : The node being restored disconnected from the Master Agent prior to being fully restored. Reason [String]
Explanation The DRF Master Agent was running a restore operation on a CCM cluster, when one of the nodes disconnected before the restore operation was completed.
Recommended Action Please check the computer that disconnected during restore. If the computer was accidentally shutdown, restart the restore.
Error Message
CCM_DRF_MASTER-DRF-3-DRFSftpFailure : DRF sftp operation has failed. Reason [String]
Explanation DRF sftp operation has failed.
Recommended Action Ensure that the destination server is available, has appropriate permissions and sftp daemon is running.
Error Message
CCM_DRF_MASTER-DRF-3-DRFRegistrationFailure : DRF Registration operation failed. Reason [String]
Explanation DRF Registration operation failed.
Recommended Action DRF Registration failed for a component due to some internal error. Check the DRF logs and contact support if needed.
Error Message
CCM_DRF_MASTER-DRF-3-DRFBackupCancelInternalError : DRF Backup operation has encountered an error. Backup cancelled internally. Reason [String]
Explanation DRF Backup operation has encountered an error. Backup cancelled internally.
Recommended Action Check DRF logs for details.
Error Message
CCM_DRF_MASTER-DRF-4-DRFLogDirAccessFailure : DRF couldn't access the log directory. Reason [String]
Explanation DRF couldn't access the log directory.
Recommended Action Ensure that the DRF user has required permission/enough space on DRF Log and Trace directory
Error Message
CCM_DRF_MASTER-DRF-4-DRFComponentDeRegistered : DRF succesfully de-registered the requested component. Reason [String]
Explanation DRF succesfully de-registered the requested component.
Recommended Action Ensure that the component deregistered is not needed for further backup/restore operation.
Error Message
CCM_DRF_MASTER-DRF-4-DRFDeRegistrationFailure : DRF de-registration request for a component failed. Reason [String]
Explanation DRF de-registration request for a component failed.
Recommended Action Please check the DRF logs and contact support if needed.
Error Message
CCM_DRF_MASTER-DRF-4-DRFDeRegisteredServer : DRF automatically de-registered all the components for a server. Reason [String]
Explanation This server might have got disconnected from CCM cluster.
Recommended Action Nothing.
Error Message
CCM_DRF_MASTER-DRF-4-DRFSchedulerDisabled : DRF Scheduler is disabled because no configured features available for backup. Reason [String]
Explanation DRF Scheduler is disabled because no configured features available for backup.
Recommended Action Ensure at least one feature is configured for the scheduled backup to run.
Error Message
CCM_DRF_MASTER-DRF-6-DRFComponentRegistered : DRF Succesfully Registered the requested component. Reason [String]
Explanation DRF Succesfully Registered the requested component.
Recommended Action Ensure that the registered component is needed for backup/restore operation.
Error Message
CCM_DRF_MASTER-DRF-6-DRFSchedulerUpdated : DRF Scheduled backup configurations is updated automatically due to feature DeRegistration. Reason [String]
Explanation DRF Scheduled backup configurations is updated automatically due to feature DeRegistration.
Recommended Action Ensure that the new configurations is appropriate one for the backup/restore operation.
Error Message
CCM_DRF_MASTER-DRF-6-DRFBackupCompleted : DRF backup completed successfully. Reason [String]
Explanation DRF backup completed successfully.
Recommended Action Ensure that the backup operation completed successfully.
Error Message
CCM_DRF_MASTER-DRF-6-DRFRestoreCompleted : DRF restore completed successfully. Reason [String]
Explanation DRF restore completed successfully.
Recommended Action Ensure that the restore operation completed successfully.
Error Message
CCM_DRF_MASTER-DRF-3-DRFFailure : DRF Backup or Restore process has failed. Reason [String]
Explanation DRF Backup or Restore process encountered errors.
Recommended Action Check DRF logs for further details.
Error Message
CCM_DRF_MASTER-DRF-4-DRFNoBackupTaken : A valid backup of the current system was not found. Reason [String]
Explanation A valid backup of the current system was not found after an Upgarde/Migration or Fresh Install.
Recommended Action It is recommended to perform a Backup using the Disaster Recovery System.
Error Message
CCM_TOMCAT_APPS-LOGIN-4-AuthenticationFailed : Login Authentication failed. Login IP Address/Hostname [String] Login Date/Time [String] Login UserID [String] Login Interface [String]
Explanation Authentication failure for login attempt is detected.
Recommended Action If this event happens repeatedly, investigate the source of the failed login attempts.
Error Message
CCM_TOMCAT_APPS-LOGIN-6-AuthenticationSucceeded : Login Authentication succeeded. Login IP Address/Hostname [String] Login Date/Time [String] Login UserID [String] Login Interface [String]
Explanation Authentication success for login attempt is detected.
Recommended Action If this event is expected, no action is required; otherwise, notify the administrator.
Error Message
CCM_TOMCAT_APPS-LOGIN-5-ServiceActivated : Service Activated. Service Name [String]
Explanation This service is now activated.
Recommended Action No action is required.
Error Message
CCM_TOMCAT_APPS-LOGIN-5-ServiceDeactivated : Service Deactivated. Service Name [String]
Explanation This service is now deactivated.
Recommended Action No action is required.
Error Message
CCM_TOMCAT_APPS-LOGIN-1-ServiceActivationFailed : Failed to activate a service. Service Name [String] Reason [String] Error String [String]
Explanation Failed to activate this service.
Recommended Action Activate the service again
Error Message
CCM_TOMCAT_APPS-LOGIN-1-ServiceDeactivationFailed : Failed to deactivate a service. Service Name [String] Reason [String] Error String [String]
Explanation Failed to deactivate this service.
Recommended Action Deactivate the service again
Error Message
CCM_TOMCAT_APPS-LOGIN-2-ServiceFailed : Service terminated. Service Name [String] Process ID [Int] Reason [String]
Explanation The Service has terminated abruptly. Service Manager will try to restart it.
Recommended Action Monitor the state of the service.
Error Message
CCM_TOMCAT_APPS-LOGIN-2-ServiceStartFailed : Failed to start service. Service Name [String] Reason [String]
Explanation Failed to start this service. Service Manager will attempt to start the service again.
Recommended Action Monitor the state of the service.
Error Message
CCM_TOMCAT_APPS-LOGIN-2-ServiceStopFailed : Failed to stop service. Service Name [String] Reason [String]
Explanation Unable to stop the specified service after serveral retries. The service will be marked stopped.
Recommended Action Check the syslog for system error code.
Error Message
CCM_TOMCAT_APPS-LOGIN-2-ServiceRestartFailed : Failed to Restart service. Service Name [String] Reason [String]
Explanation Unable to restart the specified service.
Recommended Action No action is required.
Error Message
CCM_TOMCAT_APPS-LOGIN-1-ServiceExceededMaxRestarts : Service failed to start and exceeded maximum allowed restarts. Service Name [String] Reason [Int]
Explanation Service failed to start, even after the max restarts attempts.
Recommended Action Start the service manually.
Error Message
CCM_TOMCAT_APPS-LOGIN-0-FailedToReadConfig : Service Manager failed to read configuration file. File Name [String] Reason [String]
Explanation Failed to read configuration file. Configuration file might be corrupted.
Recommended Action Re-install CUCM
Error Message
CCM_TOMCAT_APPS-LOGIN-1-MemAllocFailed : Memory allocation failed. Memory Allocation Failure [String]
Explanation Failure to allocate memory.
Recommended Action (1) Check the syslog for the system error number. (2) If the Alert is seen repeatedly, restart Service Manager (3) If the problem still persist, reboot the CUCM node.
Error Message
CCM_TOMCAT_APPS-LOGIN-1-SystemResourceError : A System call failed. System Call [String] Service [String] Reason [String]
Explanation System call failed.
Recommended Action (1) Check the syslog for the system error number.(2) If the Alert is seen repeatedly, restart Service Manager (3) If the problem still persist, reboot the node.
Error Message
CCM_TOMCAT_APPS-LOGIN-6-CLM_IPSecCertUpdated : IPSec self-signed cert updated. Node's Name or IP [String]
Explanation The IPSec self-signed cert from a peer node in the cluster has been imported due to a change.
Recommended Action No action is required.
Error Message
CCM_TOMCAT_APPS-LOGIN-6-CLM_IPAddressChange : IP address change in cluster. Node's Name [String] Node's Old IP [String] Node's New IP [String]
Explanation The IP address of a peer node in the cluster has changed.
Recommended Action No action is required.
Error Message
CCM_TOMCAT_APPS-LOGIN-6-CLM_PeerState : Current ClusterMgr session state. Node's Name or IP [String] Node's State [String]
Explanation The ClusterMgr session state with another node in the cluster has changed to the current state.
Recommended Action No action is required.
Error Message
CCM_TOMCAT_APPS-LOGIN-1-CLM_MsgIntChkError : ClusterMgr message integrity check error. Sender's IP address [String]
Explanation ClusterMgr has received a message which has failed a message integrity check. This can be an indication that another node in the cluster is configured with the wrong security password.
Recommended Action Verify message is coming from an expected IP address. Verify the security password on that node.
Error Message
CCM_TOMCAT_APPS-LOGIN-3-CLM_UnrecognizedHost : ClusterMgr unrecognized host. Node's IP address [String]
Explanation ClusterMgr has received a message from an IP address which is not configured as a node in this cluster.
Recommended Action Verify that this IP address is currently configured as a server in this cluster.
Error Message
CCM_TOMCAT_APPS-LOGIN-4-CLM_ConnectivityTest : CLM Connectivity Test Failed. Node's IP [String] Error description [String]
Explanation Cluster Manager detected a network error.
Recommended Action Verify connectivity between cluster nodes and fix any network issues.