CCM_CALLMANAGER-CALLMANAGER-3-CallManagerFailure : Indicates some failure in the Cisco CallManager system. Additional Text [Optional] [String] Host name of hosting node. [String] IP address of hosting node. [String] Reason code. [Enum]
Explanation This alarm indicates that some failure occurred in the Cisco CallManager system.
Recommended Action Monitor for other alarms and restart Cisco CallManager service, if necessary.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 1 | Unknown |
| 2 | HeartBeatStopped |
| 3 | RouterThreadDied |
| 4 | TimerThreadDied |
| 5 | CriticalThreadDied |
| 6 | DeviceMgrInitFailed |
| 7 | DigitAnalysisInitFailed |
| 8 | CallControlInitFailed |
| 9 | LinkMgrInitFailed |
| 10 | DBMgrInitFailed |
| 11 | MsgTranslatorInitFailed |
| 12 | SuppServiceInitFailed |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-SDLLinkISV : SDL link to remote application restored. Remote IP address of remote application [String] Unique Link ID. [String] Local node ID [UInt] Local Application ID. [Enum]RemoteNodeID [UInt] Remote application ID. [Enum]
Explanation This alarm indicates that the local Cisco CallManager has gained communication with the remote Cisco CallManager. Note that the remote Cisco CallManager should also indicate SDLLinkISV with a different LinkID.
Recommended Action No action is required.
Reason Code - Enum Definitions
Enum Definitions - LocalApplicationId
| Value | Definition |
|---|---|
| 100 | CallManager |
| 200 | CTIManager |
Enum Definitions - RemoteApplicationId
| Value | Definition |
|---|---|
| 100 | Call Manager |
| 200 | CTI Manager |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-SDLLinkOOS : SDL link to remote application out of service. Remote IP address of remote application [String] Unique Link ID. [String] Local node ID [UInt] Local Application ID. [Enum]RemoteNodeID [UInt] Remote application ID. [Enum]
Explanation This alarm indicates that the local Cisco CallManager has lost communication with the remote Cisco CallManager. This alarm usually indicates network errors or a nonrunning remote Cisco CallManager.
Recommended Action Investigate why the remote Cisco CallManager is not running or whether a network problem exists.
Reason Code - Enum Definitions
Enum Definitions - LocalApplicationID
| Value | Definition |
|---|---|
| 100 | CallManager |
| 200 | CTI |
Enum Definitions - RemoteApplicationID
| Value | Definition |
|---|---|
| 100 | Call Manager |
| 200 | CTI Manager |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-SDLLinkAppProtocol : SDL Link Connection Refused. 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 Cisco CallManager is unable to establish communication with the remote Cisco CallManager due to a protocol version mismatch.
Recommended Action Determine the release numbers of the local and remote Cisco CallManager servers. If the releases do not match, it's possible that the local and remote Cisco CallManager servers cannot communicate due to protocol changes. To correct the problem, upgrade the appropriate Cisco CallManager so that the versons of the local and remote Cisco CallManager servers match.
Reason Code - Enum Definitions
Enum Definitions - RemoteAppId
| Value | Definition |
|---|---|
| 100 | Call Manager |
| 200 | CTI Manager |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-BChannelOOS : B channel out of service. Unique channel Id [String] Device Name. [String] Reason [Optional]. [Enum]Channel Id. [UInt]
Explanation Indicated B channel has gone out of service.
Recommended Action Contact TAC for help if this alarm continue to generate.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 0 | None Defined |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-BChannelISV : B channel in service. Channel Id. [UInt] Unique channel Id [String] Device Name. [String]
Explanation Indicated B Channel has gone in service.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DChannelOOS : D channel out of service. Channel Id. [UInt] Unique channel Id [String] Device Name. [String] Device IP address [String] Reason [Optional]. [Enum]
Explanation Indicated D channel has gone out of service.
Recommended Action Contact TAC for help if this alarm continue to generate.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 0 | NoneDefined |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DChannelISV : D channel in service. Channel Id. [UInt] Unique channel Id [String] Device Name. [String] Device IP address [String]
Explanation Indicated D Channel has gone in service.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DeviceTransientConnection : Transient connection attempt. Device IP address. [String] Device name [Optional]. [String] Device MAC address [Optional]. [String] Protocol. [String] Device type. [Optional] [Enum]Reason Code [Optional]. [Enum]Connecting Port [UInt] Registering SIP User. [Optional]. [String]
Explanation A connection was established and immediately dropped before completing registration. Incomplete registration may indicate 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.
Recommended Action 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 |
| 10 | CISCO_VGC_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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 1 | Unknown |
| 2 | NoEntryInDatabase |
| 3 | DatabaseConfigurationError |
| 4 | DeviceNameUnresolveable |
| 5 | MaxDevRegExceeded |
| 6 | ConnectivityError |
| 7 | InitializationError |
| 8 | DeviceInitiatedReset |
| 9 | CallManagerReset |
| 10 | AuthenticationError |
| 11 | InvalidX509NameInCertificate |
| 12 | InvalidTLSCipher |
| 13 | DirectoryNumberMismatch |
| 14 | MalformedRegisterMsg |
| 15 | ProtocolMismatch |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DeviceRegistered : Device registered. Device name. [String] Device MAC address [Optional]. [String] Device IP address. [String] Protocol. [String] Device description [Optional]. [String] User ID [Optional]. [String] Load ID. [Optional] [String] Associated directory numbers. [Optional]. [String] Performance monitor object type [Enum]Device type. [Optional] [Enum]Configured GateKeeper Name [Optional]. [String] Technology Prefix Name [Optional]. [String] Zone Information [Optional]. [String] Alternate Gatekeeper List [Optional]. [String] Active Gatekeeper [Optional]. [String] Call Signal Address [Optional]. [String] RAS Address [Optional]. [String]
Explanation A device successfully registered with Cisco CallManager. Assume that device is in service.
Recommended Action No action is required.
Reason Code - Enum Definitions
Enum Definitions - PerfMonObjType
| Value | Definition |
|---|---|
| 1 | SCM_OBJ |
| 2 | STATION_OBJ |
| 3 | LINE_OBJ |
| 4 | CCM_H323_OBJ |
| 5 | MGCP_GATEWAY_INSTANCE_OBJ |
| 6 | MOH_DEVICE_INSTANCE_OBJ |
| 7 | ANALOG_ACCESS_OBJ |
| 8 | CCM_MGCPFXS_OBJ |
| 9 | CCM_MGCPFXO_OBJ |
| 10 | CCM_MGCPT1CAS_OBJ |
| 11 | CCM_MGCPPRI_OBJ |
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 |
| 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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-DevicePartiallyRegistered : Device partially registered. Device name. [String] Device MAC address [Optional]. [String] Device IP address. [String] Protocol. [String] Device description [Optional]. [String] User ID [Optional]. [String] Load ID. [Optional] [String] Associated directory numbers. [String] Performance monitor object type [Enum]Device type. [Optional] [Enum]
Explanation A device is partially registered with Cisco CallManager. Some, but not all, of the lines configured on the device have successfully registered.
Recommended Action If this alarm persists, verify the number of lines configured on the device are correct, and that the directory numbers are correct. If the device is a third-party SIP phone, verify the directory numbers configured on the phone match the directory numbers configured on the device in CallManager.
Reason Code - Enum Definitions
Enum Definitions - PerfMonObjType
| Value | Definition |
|---|---|
| 1 | SCM_OBJ |
| 2 | STATION_OBJ |
| 3 | LINE_OBJ |
| 4 | CCM_H323_OBJ |
| 5 | MGCP_GATEWAY_INSTANCE_OBJ |
| 6 | MOH_DEVICE_INSTANCE_OBJ |
| 7 | ANALOG_ACCESS_OBJ |
| 8 | CCM_MGCPFXS_OBJ |
| 9 | CCM_MGCPFXO_OBJ |
| 10 | CCM_MGCPT1CAS_OBJ |
| 11 | CCM_MGCPPRI_OBJ |
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 |
| 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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DeviceUnregistered : Device unregistered. Device name. [String] Device MAC address [Optional]. [String] Device IP address. [String] Protocol. [String] Device type. [Optional] [Enum]Device description [Optional]. [String] Reason Code [Optional]. [Enum]
Explanation A device that has previously registered with Cisco CallManager has unregistered. This event may be issued as part of normal unregistration event or due to some other reason such as loss of keepalives.
Recommended Action No action is required if unregistration of this device was expected.
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 |
| 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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 1 | Unknown |
| 2 | NoEntryInDatabase |
| 3 | DatabaseConfigurationError |
| 4 | DeviceNameUnresolveable |
| 5 | MaxDevRegExceeded |
| 6 | ConnectivityError |
| 7 | InitializationError |
| 8 | DeviceInitiatedReset |
| 9 | CallManagerReset |
| 10 | DeviceUnregistered |
| 11 | MalformedRegisterMsg |
| 12 | SCCPDeviceThrottling |
| 13 | KeepAliveTimeout |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-SIPLineRegistrationError : SIP line registration error. Device IP address. [String] Device Port. [UInt] Device name [Optional]. [String] Device MAC address [Optional]. [String] Device type. [Optional] [Enum]Reason Code [Optional]. [Enum]Connecting Port [UInt] Configured DNs. [String] Registering SIP User. [String]
Explanation A SIP line attempted to register with CallManager and failed due to the error inidicated in the Reason Code parameter. The alarm could indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection.
Recommended Action Verify the directory number(s) on the device itself match the directory number(s) configured in the CCM database.
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 |
| 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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 1 | Unknown |
| 2 | MisconfiguredDirectoryNumber |
| 3 | MalformedRegisterMessage |
| 4 | AuthenticationError |
| 5 | InitializationError |
| 6 | MaxLinesExceeded |
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-6-H323Started : Cisco CallManager ready to handle calls for the indicated H323 device. Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description [Optional]. [String] Remote CallManager Server 1[Optional]. [String] Remote CallManager Server 2[Optional]. [String] Remote CallManager Server 3[Optional]. [String]
Explanation Cisco CallManager is ready to handle calls for the indicated H323 device. This alarm does not indicate the current state of the H323 device, only that Cisco CallManager is prepared to handle calls to/from the H323 device.
Recommended Action 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 |
| 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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-H323Stopped : Cisco CallManager not ready to handle calls for the indicated H323 device. Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description [Optional]. [String] Remote CallManager Server 1[Optional]. [String] Remote CallManager Server 2[Optional]. [String] Remote CallManager Server 3[Optional]. [String]
Explanation Cisco CallManager is not ready to handle calls for the indicated H323 device.
Recommended Action 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 |
| 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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-SIP IPPortConflict : Configured local port for indicated Device is already in used. Device Name. [String] Port Number [String] Device type. [Optional] [Enum]
Explanation The configured local port for the indicated device is already in used or CallManager is unable to bind to the configured port.
Recommended Action Either the SIP device entry is configured incorrectly, or the domain name system (DNS) is incorrectly configured.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value | Definition |
|---|---|
| 131 | SIP_TRUNK |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-SIPStarted : Cisco CallManager ready to handle calls for the indicated SIP device. Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description [Optional]. [String] Incoming Port Number. [UInt] Outgoing Port Number. [UInt] Incoming Transport Type [Enum]Outgoing Transport Type [Enum]
Explanation Cisco CallManager is ready to handle calls for the indicated SIP device. This alarm does not indicate the current state of the SIP device, only that Cisco CallManager is prepared to handle calls to/from the SIP device.
Recommended Action 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 | TCP/UDP |
| 4 | TLS |
Enum Definitions - OutTransportType
| Value | Definition |
|---|---|
| 1 | TCP |
| 2 | UDP |
| 4 | TLS |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-SIPStopped : Cisco CallManager not ready to handle calls for the indicated SIP device. Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description [Optional]. [String] Incoming Port Number. [UInt] Outgoing Port Number. [UInt] Incoming Transport Type [Enum]Outgoing Transport Type [Enum]
Explanation Cisco CallManager is not ready to handle calls for the indicated SIP device.
Recommended Action 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 | TCP/UDP |
| 4 | TLS |
Enum Definitions - OutTransportType
| Value | Definition |
|---|---|
| 1 | TCP |
| 2 | UDP |
| 4 | TLS |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-ConnectionFailure : Cisco CallManager failed to open TLS connection for the indicated device. Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description [Optional]. [String] Reason code [Enum]
Explanation Cisco CallManager failed to open TLS connection for the indicated device.
Recommended Action Check the Security profile of the indicated device.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value | Definition |
|---|---|
| 131 | SIP_TRUNK |
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 1 | AuthenticationError |
| 2 | InvalidX509NameInCertificate |
| 4 | InvalidTLSCipher |
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-MediaResourceListExhausted : An available device type not found in the media resource list. Media Resource Type [Enum]Media Resource List Name [String]
Explanation An available resource could not be found as indicated by device type in the indicated media route list.
Recommended Action Add additional resource to the indicated media resource list. This alarm indicates a network failure or device failure.
Reason Code - Enum Definitions
Enum Definitions - MediaResourceType
| Value | Definition |
|---|---|
| 1 | MediaTerminationPoint |
| 2 | Transcoder |
| 3 | ConferenceBridge |
| 4 | MusicOnHold |
| 5 | MonitorBridge |
| 6 | Recorder |
| 7 | Annunciator |
| 8 | BuiltInBridge |
| 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.
Recommended Action Adding additional routes may be needed in the indicated route list.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DeviceTypeMismatch : Device type mismatch. Database device type [UInt] Device type [UInt] Name of device. [String]
Explanation Device type passed on by the indicated device does not match the database configuration.
Recommended Action Verify database configuration for the indicated device.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DeviceDnInformation : Device DN information. Device Name [String] Device type. [Optional] [Enum]Station Desc [String] Station Dn [String]
Explanation List of DNs associated with the device.
Recommended Action 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 |
| 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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-StationConnectionError : Station device closing connection. Device Name [String]
Explanation Station device is closing connection with Cisco CallManager.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-StationAlarm : Station alarm. TCP ProcessID [String] Device Text [String] Param1 [UInt] Param2 [UInt]
Explanation Station device sent an alarm to Cisco CallManager.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-StationEventAlert : Station alert. TCP ProcessID [String] Device Text [String] Param1 [UInt] Param2 [UInt]
Explanation Station device sent an alert to Cisco CallManager.
Recommended Action Ensure that the configuration for identified device is proper.
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-MGCPGatewayGainedComm : MGCP communication to gateway established. Device Name [String]
Explanation MGCP Gateway established communication with Cisco CallManager.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-2-MGCPGatewayLostComm : MGCP communication to gateway lost. Device Name [String]
Explanation MGCP gateway lost communication with Cisco CallManager.
Recommended Action Check see if the identified MGCP gateway has restarted or not in operation. Otherwise, contact TAC for help.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-TCPInitError : TCP initialization error. Error Number [String] ErrorCode [Int]
Explanation TCP library initialization failed.
Recommended Action Contact TAC for help.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-StationTCPInitError : Station TCP initialization error. Error Number [String] ErrorCode [Int]
Explanation Station TCP initialization error was encountered.
Recommended Action Contact TAC for help.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-TspError : Error in TSP. Port IsoEthPort [UInt] Port DSL [UInt] Name of Device [String]
Explanation Database configuration error was encountered.
Recommended Action Investigate configuration for identified device.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-TspTimeout : TSP Timeout. Port IsoEthPort [UInt] Port DSL [UInt] Name of Device [String]
Explanation Timeout was encountered while trying to read database configuration.
Recommended Action Investigate configuration for identified device.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-TspCorrupt : TSP corrupt. Port IsoEthPort [UInt] Port DSL [UInt]
Explanation Database configuration error was encountered.
Recommended Action Investigate configuration for identified device.
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-3-NotEnoughChans : Not enough channels. Port IsoEthPort [UInt] Port DSL [UInt]
Explanation Call attempt was rejected because requested gateway channel(s) could not be allocated.
Recommended Action Add more gateway resources.
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-DeviceResetInitiated : Device reset initiated. Device name [Optional]. [String] Device type. [Optional] [Enum]
Explanation Device reset request was received and initiated on registered device.
Recommended Action 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 |
| 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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-DeviceRestartInitiated : Device restart initiated. Device name [Optional]. [String] Device type. [Optional] [Enum]
Explanation Device restart request was received and initiated on registered device.
Recommended Action 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 |
| 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 |
| 50 | CONFERENCE_BRIDGE |
| 51 | CONFERENCE_BRIDGE_HARDWARE |
| 61 | H323_PHONE |
| 62 | H323_GATEWAY |
| 70 | MUSIC_ON_HOLD |
| 71 | DEVICE_PILOT |
| 72 | CTI_PORT |
| 73 | CTI_ROUTE_POINT |
| 80 | VOICE_MAIL_PORT |
| 90 | ROUTE_LIST |
| 100 | LOAD_SIMULATOR |
| 110 | MEDIA_TERMINATION_POINT |
| 111 | MEDIA_TERMINATION_POINT_HARDWARE |
| 120 | MGCP_STATION |
| 121 | MGCP_TRUNK |
| 122 | GATEKEEPER |
| 124 | 7914_14_BUTTON_LINE_EXPANSION_MODULE |
| 125 | TRUNK |
| 254 | UNKNOWN_MGCP_GATEWAY |
| 255 | UNKNOWN |
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-3-DaTimeOut : Digit analysis timeout.
Explanation Digit analysis timeout occurred.
Recommended Action Check see if the DigitAnalysisTimer is set to the suggested value in the CallManager Service Parameter Configuration page. Otherwise, contact TAC for help.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-MaxCallDurationTimeout : Maximum Call Duration Timer Expired. Maximum Call Duration (minutes) [Int]
Explanation Maximum Call Duration Timer clears an active call after a time duration specified in CallManager Service Parameter page.
Recommended Action No action is required. If the feature need to be disabled, set the value of Maximum Call Duration Timer to zero from Service Parameter page.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-MaxHoldDurationTimeout : Maximum Hold Duration Timer Expired. Maximum Hold Duration (minutes) [Int]
Explanation Maximum Hold Duration Timer clears a held call after a time duration specified in CallManager Service Parameter page.
Recommended Action No action is required. If the feature need to be disabled, set the value of Maximum Hold Duration Timer to zero from Service Parameter page.
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-DatabaseAuditInfo_074 : Database audit information. Number [Int]
Explanation Database audit information 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-4-TimerThreadSlowed : Timer thread slow.
Explanation Verification of the Cisco CallManager timing mechanism slowed beyond acceptable limits.
Recommended Action Investigate the issuance of other alarm or any indication; i.e., trace data that would indicate a heavy processor load or other anomalies for the indicated node.
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-5-DatabaseDefaultsRead : Database defaults read.
Explanation Database default information was read successfully.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-1-DatabaseDefaultsReadFailure : Database defaults reading failure. HostName [String]
Explanation Database default information read failure occurred.
Recommended Action Contact TAC for help.
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-3-DeviceInitTimeout : Device initialization Timeout. Device Name [String] Protocol [String] Side Number [UInt]
Explanation Device initialization timeout was encountered.
Recommended Action Investigate identified device.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-NumDevRegExceeded : Number of registered devices exceeded. Maximum Devices [Int]
Explanation Number of registered devices was exceeded.
Recommended Action Investigate the number of registered devices.
Error Message
CCM_CALLMANAGER-CALLMANAGER-5-CallManagerOnline : Cisco CallManager on line. CCM Version [String]
Explanation Cisco CallManager is on line.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-MtpNoMoreResourcesAvailable : No more MTP resources available.
Explanation MTP resource is not available.
Recommended Action Install additional MTP or transcoder resources.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-MohNoMoreResourcesAvailable : No more MOH resources available.
Explanation MOH resource is not available.
Recommended Action Install additional MOH resources.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-ConferenceNoMoreResourcesAvailable : No more Conference resources available.
Explanation Conference resource is not available.
Recommended Action Install additional Conference resources.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-AnnunciatorNoMoreResourcesAvailable : No more Annunciator resources available.
Explanation Annunciator resource is not available.
Recommended Action Install additional annunciator resources.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-RsvpNoMoreResourcesAvailable : No more RSVP resources available.
Explanation RSVP resource is not available.
Recommended Action Install additional RSVP resources.
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-3-MaxCallsReached : Maximum calls reached. Description [Int]
Explanation Maximum number of simultaneous connections in a Cisco CallManager node has been reached.
Recommended Action Investigate number of active calls in the Cisco CallManger node.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-TcpCommError : TCP communication error. Text [String] Last Error [UInt] Error Text [String] Socket Send [UInt]
Explanation TCP communication error was encountered.
Recommended Action Contact TAC for help with the Alarm Text and ErrorText provided.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-OperatingSystemFailure : Operating system call failed. System Call [String] Error Code. [ULong]
Explanation The operating system call specified has failed; the failure code is also provided.
Recommended Action Contact TAC with the system call and error code provided.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-CdrWriteError : Unable to write CDR records to database. Destination Node Id [UInt] Call Manager Id [UInt] Call Id [UInt] Calling Party [String] Called Party [String]
Explanation Unable to write CDR records to the database; retry count has exceeded.
Recommended Action Contact TAC with the system call and error code provided.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-COMException : COM Exception. ErrorCode [Int] Description [String]
Explanation Severe component object model interface error occurred.
Recommended Action Contact TAC.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DBLException : DBL Exception. ErrorCode [Int] ExceptionString [String]
Explanation Severe database layer interface error occurred.
Recommended Action Contact TAC.
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-3-ICTCallThrottlingStart : Cisco CallManager stops handling calls for the indicated H323 device due to route loop over H323 Trunk Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description [Optional]. [String]
Explanation Cisco CallManager has detected a route loop over H323 Trunk. As a result it has temporarily stops accepting calls for the indicated H323 device.
Recommended Action Administrator needs to remove route loop.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value | Definition |
|---|---|
| 125 | TRUNK |
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-ICTCallThrottlingEnd : Cisco CallManager starts handling calls for the indicated H323 device which was stopped due to route loop created over H323 Trunk Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description [Optional]. [String]
Explanation Cisco CallManager has resumed normal state and starts accepting calls for indicated H323 device.
Recommended Action Administrator needs to remove route loop.
Reason Code - Enum Definitions
Enum Definitions - DeviceType
| Value | Definition |
|---|---|
| 125 | 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-3-CodeYellowEntry : CodeYellowEntry 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 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-3-CodeYellowExit : CodeYellowExit 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 CCM Call throttling terminates when the delay in handling incoming calls falls below the exit latency.
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-3-CodeRedEntry : CodeRedEntry 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 CallManager is not able to recover, even after attempting call throttling. The CallManager service is shut down.
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-3-DeviceCloseMaxEventsExceeded : DeviceCloseMaxEventsExceeded Total Events Received [UInt] IP Address [String] TCP Handle [String] Max Events Allowed [UInt] Number Of Skinny Device Throttled [UInt]
Explanation Due to receiving an unacceptably high number of events from this Skinny device, it is forced to close and reregister.
Recommended Action Check the Skinny device to determine the reason for the high number of events.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-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-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-MaliciousCall : Malicious Call Identification feature is invoked in Cisco CallManager. 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 This indicates that a malicious call is detected in Cisco CallManager and Malicious Call Identification (MCID) feature is invoked.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-Redirection : Redirection Manager cannot regiter 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-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-3-DatabaseInitTimerPop : Database Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Database Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "Database Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-RegionsInitTimerPop : Regions Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Regions Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "Regions Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-LocationsInitTimerPop : Locations Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Locations Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "Locations Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-AARInitTimerPop : Automated Alternate Routing Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Automated Alternate Routing Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "AAR Groups Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DigitAnalysisInitTimerPop : Digit Analysis Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Digit Analysis Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "Digit Analysis Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-RoutePlanInitTimerPop : Route Plan Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Route Plan Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "Route Plan Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-CallControlInitTimerPop : Call Control Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Call Control Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "Call Control Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-SsInitTimerPop : Supplementary Services Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Supplementary Services Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "Supplementary Services Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DirectoryInitTimerPop : Directory Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Directory Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "Directory Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-3-DeviceInitTimerPop : Device Initialization timer has expired. Timer Value in seconds [Int]
Explanation The Device Initialization process has taken longer than expected to initialize. The system configuration is larger and/or more complex than expected, or an error has been encountered.
Recommended Action Try increasing the "Device Initialization Timer" value in the CallManager Service Parameters administration page in 50% multiples of the suggested default value. *Note: This parameter is cluster-wide. Setting this parameter will effect each call processing server within the cluster on the next service restart. If the system does not successfully initialize by increasing this parameter parameter to the maximum value, contact Cisco TAC support immediately.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-BeginThrottlingCallListBLFSubscriptions : BeginThrottlingCallListBLFSubscriptions 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 CallManager has initiated throttling of CallList BLF Subscriptions as a preventive measure to avoid overloading the system.
Recommended Action Determine if CPU and memory resources are available to meet the higher demand for CallList BLF Subscriptions. If so, increase the CallListBLFSubscriptionsThrottlingThreshold and correspondingly the CallListBLFSubscriptionsResumeThreshold. If not, increase system resources to meet the demand.
Error Message
CCM_CALLMANAGER-CALLMANAGER-4-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 CallManager has resumed accepting CallList BLF Subscriptions subsequent to prior throttling.
Recommended Action Determine if CPU and memory resources are available to meet the higher demand for CallList BLF Subscriptions. If so, increase the CallListBLFSubscriptionsThrottlingThreshold and correspondingly the CallListBLFSubscriptionsResumeThreshold. If not, increase system resources to meet the demand.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-PktCapServiceStarted : Packet capture service started.
Explanation Indicated packet capture has been enabled on the CCM server.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-PktCapServiceStopped : Packet capture service stopped.
Explanation Indicated packet capture has been disabled on the CCM server.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-PktCapOnDeviceStarted : Packet capture started on the device. Device Name [String] Packet Capture Mode [String] Packet Capture Duration [String]
Explanation Indicated packet capture has been enabled on the device.
Recommended Action No action is required.
Error Message
CCM_CALLMANAGER-CALLMANAGER-6-PktCapOnDeviceStopped : Packet capture stopped on the device. Device Name [String] Packet Capture Mode [String] Packet Capture Duration [String]
Explanation Indicated packet capture has been disabled on the device.
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-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-4-MultipleSIPTrunksToSamePeerAndLocalPort : Multiple trunks have been configured to the same destination and local port which resulted in a conflict. 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 latest trunk invalidated earlier.
Recommended Action Check the SIP Trunk Configuration in Cisco Unified CallManager Administration and verify that only one SIP trunk has been configured to the same destination address and local port.
Error Message
CCM_SUMI-CMI-6-kCMIServiceStarted : Service now running.
Explanation CMI is now starting and running.
Recommended Action No action is required.
Error Message
CCM_SUMI-CMI-6-kCMIServiceStopped : Service now stopping.
Explanation Service is now stopping.
Recommended Action No action is required.
Error Message
CCM_SUMI-CMI-6-kCMIServiceStatus : Service running and working properly. Service Priority [String]
Explanation Service is running and working properly.
Recommended Action No action is required.
Error Message
CCM_SUMI-CMI-7-kCMIDebugAlarm : Alarm generated only for debugging purposes. Debug Message [String]
Explanation CMI has several debug messages that simulate real-time situations.
Recommended Action Report to Customer Service representative.
Error Message
CCM_SUMI-CMI-3-kCCMConnectionError : No CMI connection with Cisco CallManager. CallManager Name [String]
Explanation CMI cannot establish connection with Cisco CallManager.
Recommended Action Check the address/status of Cisco CallManager and the network.
Error Message
CCM_SUMI-CMI-3-kDisconnectionToCCM : CMI disconnection with Cisco CallManager. CallManager Name [String]
Explanation CMI lost connection to Cisco CallManager.
Recommended Action Check the status of Cisco CallManager and the network.
Error Message
CCM_SUMI-CMI-2-kStopBitConfigurationError : Process configuration parameter StopBit for CMI invalid. Illegal Stop Bit [String]
Explanation CMI cannot work properly because of the invalid StopBit configuration for serial port.
Recommended Action Check the process configuration parameter StopBit for CMI.
Error Message
CCM_SUMI-CMI-2-kParityConfigurationError : Process configuration parameter parity for CMI invalid. Illegal Parity [String]
Explanation CMI cannot work properly because of the invalid parity configuration for serial port.
Recommended Action Check the process configuration parameter parity for CMI.
Error Message
CCM_SUMI-CMI-2-kWSAStartupFailed : Windows socket startup failure. Error Information [String]
Explanation WinSock could not be started.
Recommended Action >Ensure Windows 2000 service pack 1 is installed because it might obstruct Winsock creation. Then try to restart CMI. If this alarm keeps appearing, report to Customer Service representative.
Error Message
CCM_SUMI-CMI-5-kConfigParaNotFound : Configuration parameter 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-5-kSMDIMessageError : Invalid DN in SMDI message. Invalid DN [String]
Explanation CMI cannot find the DN in database.
Recommended Action Check the configuration of voice-mail system. Or disable ValidateDns to avoid this alarm.
Error Message
CCM_SUMI-CMI-5-kSMDICmdError : Bad incoming SMDI message to CMI. Bad SMDI command [String]
Explanation CMI receives a bad incoming SMDI message.
Recommended Action Check the configuration of voice-mail system.
Error Message
CCM_SUMI-CMI-2-kSerialPortOpeningError : Error when CMI tries to open the Windows NT serial port. Serial Port Opening Error [String]
Explanation When CMI tries to open the serial port, Windows NT returns an error.
Recommended Action Make sure the serial port is available.
Error Message
CCM_SUMI-CMI-2-kSerialPortGetStatusError : Error when CMI tries to get the status of Windows NT serial port. Serial Port Getting Status Error [String]
Explanation When CMI tries to get the status of serial port, Windows NT returns an error.
Recommended Action Make sure the serial port available.
Error Message
CCM_SUMI-CMI-2-kSerialPortSetStatusError : Error when CMI tries to set the status of Windows NT serial port. Serial Port Setting Status Error [String]
Explanation When CMI tries to set the status of serial port, Windows NT returns an error.
Recommended Action Make sure the serial port is available.
Error Message
CCM_SUMI-CMI-3-kWritingFileFailure : CMI failure writing SMDI messages to the serial port. Error Information [String]
Explanation CMI opened the serial port; however it failed writing data to the serial port.
Recommended Action Restart CMI. If this alarm keeps appearing, report to Customer Service representative.
Error Message
CCM_SUMI-CMI-2-kReadingFileFailure : CMI failure reading SMDI messages from the serial port. Error Information [String]
Explanation CMI opened the serial port; however it failed reading data from the serial port.
Recommended Action Make sure the serial port is available. If this alarm keeps appearing, report to Customer Service representative.
Error Message
CCM_SUMI-CMI-3-kInvalidPortHandle : Invalid handle for the opened serial port. Error Information [String]
Explanation When CMI tries to write to the serial port, the handle for the opened serial port is invalid.
Recommended Action Make sure the serial port is available.
Error Message
CCM_SUMI-CMI-2-kVMDNConfigurationError : Voice-mail DN for CMI invalid. Invalid VoiceMailDN [String]
Explanation CMI cannot register with Cisco CallManager because of the invalid voice-mail DN.
Recommended Action Check the process configuration parameter VoiceMailDn for CMI.
Error Message
CCM_SUMI-CMI-4-kThreadKillingError : Error when CMI tries to kill the threads. Error Information [String]
Explanation When CMI tries to kill the threads, an error occurs.
Recommended Action Report to Customer Service representative.
Error Message
CCM_SUMI-CMI-4-kMemAllocFailed : Memory allocation not done using NEW function. Memory Allocation Failure [String]
Explanation When CMI uses "new" function to allocate memory, it fails.
Recommended Action Close some applications and check system resources.
Error Message
CCM_SUMI-CMI-1-kDBLException : DBL exception caught. DBL Exception [String]
Explanation When CMI initializes DBL, it catches an exception.
Recommended Action Make sure the Database is running. If this alarm keeps appearing, report to Customer Service representative.
Error Message
CCM_SUMI-CMI-1-kCOMException : COM exception caught. COM Exception [String]
Explanation When CMI initializes COM, it catches an exception.
Recommended Action Report to Customer Service representative.
Error Message
CCM_SUMI-CMI-1-kCMIException : CMI exception thrown. CMI Exception [String]
Explanation When CMI runs, it throws an exception.
Recommended Action The exception may be caused by wrong process configuration parameters or bad serial port status. Refer to the associated alarm for further information.
Error Message
CCM_SUMI-CMI-1-kUnknownException : CMI unknown exception caught.
Explanation When CMI runs, it catches an unknown exception.
Recommended Action Report to Customer Service representative.
Error Message
CCM_CTI-CTI-4-kCtiMytcpErrSocketBroken : Socket connection broken.
Explanation TCP connection is lost.
Recommended Action Although connection to the application is lost, no action is required if lost connection was intentional.
Error Message
CCM_CTI-CTI-4-kCtiNullTcpHandle : TranslateCtiQbeInputMessage: NULL TCP HANDLE!!! (PDU is dropped) PDU number [Long]
Explanation Because a null TCP handle is received, PDU that could not be forwarded gets dropped.
Recommended Action Contact TAC if problem persists.
Error Message
CCM_CTI-CTI-3-kCtiMaxConnectionReached : CTIManager maximum number of CTI providers reached; provider open rejection.
Explanation Maximum number of CTI connections has been reached. No new connection will be accepted unless an existing connection is closed.
Recommended Action Limit number of applications to MaxCTIConnections; Check the CTI Manager service parameter MaxCTIConnections for the maximum number of connections.
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_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 If problem persists, contact TAC.
Error Message
CCM_CTI-CTI-3-kCtiMYTCPSendError : MYTCP_Send: send error.
Explanation TCP socket connection has been broken.
Recommended Action Network error may have occurred. If problem persists, contact TAC.
Error Message
CCM_CTI-CTI-3-kCtiProviderOpenFailure : CTI application failed to open provider CTIconnectionId [Long] Login User Id [String] Reason code. [Enum]IPAddress [String]
Explanation Application is unable to open provider.
Recommended Action Check the reason code and correct the problem. Restart CTIManager if problem persists.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 0 | Unknown |
| 0x8ccc0075 (2362179701) | Directory response timeout |
| 0x8ccc0060 (2362179680) | Login failed |
| 0x8ccc005e (2362179678) | Directory unavailable |
| 4 | Undefined Line for authentication |
| 5 | User is deleted |
| 6 | Unknown |
Error Message
CCM_CTI-CTI-2-kCtiSdlErrorvException : Failure to create internal process required to service CTI applications.
Explanation Unexpected internal SDL error caused failure in creating CTIManager or CTIHandler process.
Recommended Action Capture SDI and SDL trace information for CTIManager service and report problem to TAC.
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 Restart CTIManager. Contact TAC if problem persists.
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 Cisco CallManager. Install the plugin from CTIManager administration page and retry.
Error Message
CCM_CTI-CTI-4-kCtiQbeFailureResponse : Requested operation from application failure. Error code [ULong] Sequence number [Long] Error message [String]
Explanation Requested operation from application could not be performed because of a normal or abnormal condition.
Recommended Action Verify whether affected application is experiencing problem. Contact application support organization if problem persists.
Error Message
CCM_CTI-CTI-3-kCtiInvalidQbeSizeAndOffsets : InvalidQBESizeAndOffsets; QBE message decoding encountered illegal size or offset.
Explanation QBE message has illegal offset; it does not contain correct parameters.
Recommended Action TSP/JTAPI interface error occurred; QBE message is not formatted properly. Install compatible versions of TSP/JATPI.
Error Message
CCM_CTI-CTI-3-kCtiIllegalFilterSize : ProviderOpenRequest; illegal filter size.
Explanation ProviderOpenRequest has illegal filter size.
Recommended Action This alarm indicates the application is using incompatible version of TSP/JTAPI and Cisco CallManager. Install the correct version of TSP/JTAPI and retry.
Error Message
CCM_CTI-CTI-6-kCtiProviderClosed : CTI application connection close. Login User Id [String] Sequence Number [Long] CTI connection Id [Long] IPAddress [String] Reason code. [Enum]
Explanation Application closed the provider.
Recommended Action Informational; no action is required.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 0 | Unknown |
| 1 | Heart beat from application missed |
| 2 | Unexpected shutdown |
| 3 | Applicatoin requested provider close |
| 4 | Provider open failure |
| 5 | user deleted |
| 6 | Unknown |
Error Message
CCM_CTI-CTI-6-kCtiProviderOpened : CTI application connection opened. Login User Id [String] Sequence Number [Long] Version Number [String] CTI Connection Id [Long] IPAddress [String] CmAssignedAppID [Long]
Explanation Application opened the provider successfully.
Recommended Action Informational; no action is required.
Error Message
CCM_CTI-CTI-4-kCtiAdmintSetMsgWaitResErr : Error in setting message waiting indication.
Explanation Error occurred in setting message waiting indication lamp.
Recommended Action This alarm indicates that the device is not reachable. Check the partitions and calling search space of the device.
Error Message
CCM_CTI-CTI-4-kCtiNewCallNotifyArrayOverflow : Possible internal array overflow condition while generating CTI NewCall event.
Explanation Unexpected internal error occurred.
Recommended Action Restart CTIManager if problem persists.
Error Message
CCM_CTI-CTI-4-kCtiExistingCallNotifyArrayOverflow : Possible internal array overflow condition while generating CTI ExistingCall event.
Explanation Unexpected internal error occurred.
Recommended Action Restart CTIManager if problem persists.
Error Message
CCM_CTI-CTI-4-kCtiLineCallInfoResArrayOverflow : Possible internal array overflow condition while generating response to application request for call information.
Explanation Unexpected internal error occurred.
Recommended Action Restart CTIManager if problem persists.
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 Cisco CallManager service. Restart Cisco CallManager service if problem persists.
Error Message
CCM_CTI-CTI-6-kCtiSsRedirectCallErr : mRedirectedCallHandleToDir entry removed.
Explanation CTIHandler mRedirectedCallHandleToDir entry is removed.
Recommended Action Informational; no action is required.
Error Message
CCM_CTI-CTI-2-kCtiProviderCloseHeartbeatTimeout : CTI heartbeat timeout; provider closing.
Explanation CTI heartbeat timeout occurred. This causes CTIManager to close the application connection.
Recommended Action CTI application will need to reconnect; contact TAC if problem persists.
Error Message
CCM_CTI-CTI-4-kCtiDirectoryLoginFailure : CTI directory login failure. Sequence number [Long]
Explanation CTI Manager is unable to login to directory. Hence, application may not be able to see controlled device list.
Recommended Action Use correct username and password; see the username and password configured in Cisco CallManager administration. Also check if DC Directory service is running.
Error Message
CCM_CTI-CTI-3-kCtiIllegalQbeHeader : Illegal QBE header.
Explanation Because of illegal QBE header, QBE message has been rejected.
Recommended Action TSP/JTAPI may not be formatting QBE properly; contact TAC.
Error Message
CCM_CTI-CTI-3-kCtiIncompatibleProtocolVersion : Incompatible protocol version. Message Version [VoidPtr] Compatible Versions [VoidPtr] Current Version [VoidPtr] CallManager Version [String] IPAddress [String]
Explanation The JTAPI/TAPI application version is not compatible with this version of CTIManager, so received message has been rejected.
Recommended Action Verify correct version of application are being used; otherwise, contact TAC.
Error Message
CCM_CTI-CTI-6-kCtiDeviceOpened : 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 Informational; no action is required.
Error Message
CCM_CTI-CTI-6-kCtiDeviceClosed : 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 Informational; no action is required.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 0 | Unknown |
| 1 | CallManager Failure |
| 2 | Device Unregistered with CallManager |
| 3 | Device failed to rehome to CallManager |
| 4 | Device removed |
| 5 | Provider controlling the device is closed |
Error Message
CCM_CTI-CTI-4-kCtiDeviceOpenFailure : 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 correct the problem.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 0x8ccc0052 (2362179666) | Illegal message format |
| 0x8ccc0013 (2362179603) | Device already opened |
Error Message
CCM_CTI-CTI-4-kCtiDeviceOpenFailAccessDenied : DeviceOpenRequest failure. User ID [String] Device Name [String] Device Type [Long]
Explanation Application is trying to access device 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-6-kCtiDeviceOutofService : Device out of service. Device ID [Long] CTI Connection Id [Long] Device Name [String]
Explanation Device is out of service.
Recommended Action Informational; no action is required.
Error Message
CCM_CTI-CTI-6-kCtiDeviceInService : 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 Informational; no action is required.
Error Message
CCM_CTI-CTI-6-kCtiLineOpened : Line opened. Sequence Number [Long] Directory Number [String] Partition [String] Device Name [String] CTI Connection Id [Long]
Explanation Application opened the line.
Recommended Action Informational; no action is required.
Error Message
CCM_CTI-CTI-3-kCtiLineOpenFailure : 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 Check if the device is in the control list.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 0 | NoneDefined |
| 1 | Access denied |
Error Message
CCM_CTI-CTI-6-kCtiLineClosed : Line closed. Directory Number [String] Partition [String] CTI Connection Id [Long] Device Name [String] Reason code. [Enum]
Explanation Application closed the line.
Recommended Action Informational; no action is required.
Reason Code - Enum Definitions
Enum Definitions - Reason
| Value | Definition |
|---|---|
| 0 | Unknown |
| 1 | CallManager Failure |
| 2 | Device Unregistered with CallManager |
| 3 | CTI failed to rehome the line |
| 4 | Undefined Line |
| 5 | Device removed |
| 6 | Provider controlling the device is closed |
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-6-kCtiLineOutOfService : Line out of service. Directory Number [String] CTI Connection Id [Long] Device Name [String]
Explanation Line is going out of service.
Recommended Action Informational; no action is required.
Error Message
CCM_CTI-CTI-6-kCtiLineInService : Line in service. Line ID [Long] CTI Connection Id [Long]
Explanation Line is back in service