Cisco Unified Communications Manager (CallManager)

%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.

Enum Definitions -Reason code.

%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.

Enum Definitions -Local Application ID.

%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.

Enum Definitions -Local Application ID.

%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.

Enum Definitions -Reason [Optional].

%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.

Enum Definitions -Reason [Optional].

%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 type. [Optional]  [ Enum ],   Reason Code [Optional].  [ Enum ],   Connecting Port   [UInt]  

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.

Enum Definitions -Device type. [Optional]

%CCM_CALLMANAGER-CALLMANAGER-6-DeviceRegistered: Device registered.  Device name.   [String],  Device IP address.   [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.

Enum Definitions -Performance monitor object type

%CCM_CALLMANAGER-CALLMANAGER-3-DeviceUnregistered: Device unregistered.  Device name.   [String],  Device IP address.   [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.

Enum Definitions -Device type. [Optional]

%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.

Enum Definitions -Device type. [Optional]

%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.

Enum Definitions -Device type. [Optional]

%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.

Enum Definitions -Device type. [Optional]

%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]  

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.

Enum Definitions -Device type. [Optional]

%CCM_CALLMANAGER-CALLMANAGER-4-SIPStopped: Cisco CallManager not ready to handle calls for the indicated SIP device.  Device Name.   [String],  Device type. [Optional]  [ Enum ],   Device description [Optional].   [String]  

Explanation    Cisco CallManager is not ready to handle calls for the indicated SIP device.

Recommended Action    No action is required.

Enum Definitions -Device type. [Optional]

%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.

Enum Definitions -Media Resource Type

%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.

Enum Definitions -Device type. [Optional]

%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]  

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]  

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.

Enum Definitions -Device type. [Optional]

%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.

Enum Definitions -Device type. [Optional]

%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-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-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.

Enum Definitions -Device type. [Optional]

%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.

Enum Definitions -Device type. [Optional]

%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],  Normal Priority Queue Depth   [Long],  High 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],  Normal Priority Queue Depth   [Long],  High 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],  Normal Priority Queue Depth   [Long],  High 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   [UInt],  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-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-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 denied. 

Explanation    An operation could not be completed because the process did not have authority to perform it.

Recommended Action    No action is required.

Error Message

%CCM_CALLMANAGER-GENERIC-0-ServiceNotInstalled: Service 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 or call TAC.

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    No action is required.

Error Message

%CCM_CALLMANAGER-GENERIC-6-ServiceStarted: Service started.  Process ID   [ULong],  IP Address of hosting node.   [String],  Host name of hosting node.   [String],  Service Name   [String],  Version Information.   [String]  

Explanation    A service has started.

Recommended Action    No action is required.

Error Message

%CCM_CALLMANAGER-GENERIC-4-ServiceStartupFailed: Service startup failure.  Service Name   [String]  

Explanation    An attempt to start up the specified service failed.

Recommended Action    Restart the service.

Error Message

%CCM_TFTP-TFTP-3-WindowsSocketError: Windows socket startup failure.  Error   [Int],  Reason   [String]  

Explanation    Winsock could not be started. TFTP will exit.

Recommended Action    Ensure Windows 2000 service pack 1 is installed on your system because it might obstruct Winsock creation. Try restarting TFTP. If it still does not start, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-TftpstatsUpdateError: Error when updating performance monitor statistics. See Reason string for where it failed.  Error   [Int],  Reason   [String]  

Explanation    The performance monitor statistics could not be initialized and updated.

Recommended Action    Contact TAC.

Error Message

%CCM_TFTP-TFTP-3-EventCreationFailed: Event creation failure. See Reason string for where it failed.  Error   [Int],  Reason   [String]  

Explanation    Windows system call CreateEvent() failed. TFTP will exit.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-BeginthreadexFailed: Windows library function beginthreadx. See Reason string for where it failed.  Error   [Int],  Reason   [String]  

Explanation    Windows library function beginthreadx failed;

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-SetEventError: Call to SetEvent() function failure. See Reason string for where it failed.  Error   [Int],  Reason   [String]  

Explanation    Call to SetEvent() function failed.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-TerminateThreadError: Call to TerminateThread() failed. See Reason string for where it failed.  Reason   [String],  Error   [Int]  

Explanation    Call to TerminateThread() function failed.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-CloseHandleError: Call to CloseHandle() failed. See Reason string for where it failed.  Error   [Int],  Reason   [String]  

Explanation    CloseHandle() function failed.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-2-WaitForSingleObjectError: Error on call to WaitForSingleObject() function that waits for timeout or stopping of event. See Reason string for where it failed.  Error   [Int],  Reason   [String]  

Explanation    Call to WaitForSingleObject() function that waits for timeout or stopping of event returned error.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-2-SDIControlLayerFailed: Error value on call of IsError() function of SDI control object.  Error   [Int],  Reason   [String]  

Explanation    Call of IsError() function of SDI control object returned an error value.

Recommended Action    SDI control layer pointer returned an error. Ensure that SQL server is running, and database layer monitor service is running without problems. Ensure that TFTPServer is in database. If this error persists contact TAC with TFTP service trace files.

Error Message

%CCM_TFTP-TFTP-3-CoInitializeFailed: Error on CoInitialize() function inside ConfigThread() function.  hRes   [Long]  

Explanation    The CoInitialize() function returned error inside ConfigThread() function.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kConfigThreadReadConfigurationFailed: ReadConfiguration() false when called by ConfigThread() function. 

Explanation    ReadConfiguration() returned false when called by ConfigThread() function.

Recommended Action    Ensure TFTP Server is configured in the database. If the problem persists, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kConfigThreadBuildFileFailed: BuildFile() function false when called by ConfigThread() function. 

Explanation    BuildFile() function returned false when called by ConfigThread() function.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kConfigThreadChangeNotifyServerSingleFailed: Creation of singleton ChangeNotify pointer using call to ChangeNotifyServerSingle() failure. 

Explanation    Creation of singleton ChangeNotify pointer using call to ChangeNotifyServerSingle() failed.

Recommended Action    Search for CtftpChangeNotify.dll file in program files/Cisco/bin directory. If it is not there, install it. If the problem persists, contact TAC.

Error Message

%CCM_TFTP-TFTP-2-kConfigThreadWaitForMultipleObjectFailed: Error on call to WaitForMultipleObject() from ConfigThread() to wait for timeout or stop event.  Error   [Int]  

Explanation    Call to WaitForMultipleObject() from ConfigThread() to wait for timeout or stop event returned error.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kConfigThreadCNCMGrpBuildFileFailed: Call to BuildFile() function from CM_Group change ConfigThread() false. 

Explanation    The Call to BuildFile() function from CM_Group change ConfigThread() returned false.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kConfigThreadCNGrpBuildFileFailed: Call to BuildFile() function from group change in ConfigThread() false. 

Explanation    The Call to BuildFile() function from group change in ConfigThread() returned false.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kConfigThreadCNDelDeviceFileDeleteFailed: Deletion of file for the deleted device from system failure.  FileName   [String]  

Explanation    File for the deleted device could not be deleted from system.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. Start and stop the TFTP service because the file that it is trying to delete might be in use. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kConfigThreadCNDeviceBuildFileFailed: Call to BuildFile() function from CN_Device change in ConfigThread() false. 

Explanation    Call to BuildFile() function from CN_Device change in ConfigThread() returned false.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kConfigThreadUnknownExceptionCaught: An unknown exception caught at end of ConfigThread(). 

Explanation    An unknown exception was caught at the end of ConfigThread().

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kReadConfigurationNodeGetNameFailed: Call to GetName() function from ReadConfiguration() failure to return a node name. 

Explanation    Call to GetName() function from ReadConfiguration() failed to return a node name.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kReadConfigurationGetVersionInfoFailed: Call to GetVersionInfo() function from ReadConfiguration() failure to return database version. 

Explanation    Call to GetVersionInfo() function from ReadConfiguration() failed to return a database version.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kReadConfigurationUnknownException: An unknown exception caught at the end of ReadConfiguration() in the try-catch construct. 

Explanation    An unknown exception was caught at the end of ReadConfiguration() in the try-catch construct.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kReadConfigurationSDICtrlObjCreationFailed: Unknown exception was caught when calling InitAlarm() function.  hostName   [String],  szDblVersion   [String],  szMyVersion   [String]  

Explanation    Unknown exception was caught when calling InitAlarm() function.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kReadConfigurationSDICtrlObjInformation: Display of node name, database and TFTP version information.  hostName   [String],  szDblVersion   [String],  szMyVersion   [String]  

Explanation    This alarm displays the node name, database, and TFTP version information.

Recommended Action    No action is required.

Error Message

%CCM_TFTP-TFTP-3-kReadConfigurationCDBLException: CDBLException caught in the try-catch construct.  Excpt   [String],  Dump   [String]  

Explanation    CDBLException was caught in the try-catch construct.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kReadConfiguration_com_errorException: Com_error exception caught in the try-catch construct.  Description   [String]  

Explanation    Com_error exception was caught in the try-catch construct.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-4-kBuildFilescnfdeletewarning: Old cnf files to be deleted.  tDeletePattern1   [String]  

Explanation    Old cnf files will be deleted.

Recommended Action    This is normal operation.

Error Message

%CCM_TFTP-TFTP-4-kBuildFilesxmldeletewarning: Old XML files to be deleted.  tDeletePattern2   [String]  

Explanation    Old XML files will be deleted.

Recommended Action    This is normal operation.

Error Message

%CCM_TFTP-TFTP-3-kBuildFilescnfdeleterror: Old cnf files deletion failure.  tDeletePattern1   [String]  

Explanation    Old cnf files could not be deleted.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kBuildFilesxmldeleterror: Old XML files deletion failure.  tDeletePattern2   [String]  

Explanation    Old XML files could not be deleted.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kBuildFilesInfo: Successful creation of FileName and FileLength of XML and cnf files.  Information   [String],  FileName   [String],  FileLength   [Long]  

Explanation    FileName and FileLength of XML and cnf files were successfully created.

Recommended Action    No action is required.

Error Message

%CCM_TFTP-TFTP-6-kConfigItAllReadConfigurationFailed: Call to ReadConfiguration() function from ConfigItAll() false. 

Explanation    Call to ReadConfiguration() function from ConfigItAll() returned false.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kConfigItAllBuildFilesFailed: Call to BuildFile() function from ConfigItAll() false. 

Explanation    Call to BuildFile() function from ConfigItAll() returned false.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-1-SocketError: System socket error. See the reason code to find out more details.  nError   [Int],  Reason   [String]  

Explanation    A socket for receiving requests could not open.

Recommended Action    Run on command prompt NETSTAT -a and redirect its output to a file. This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-1-kTFTPServerListenSetSockOptFailed: Error on SetSockOpt() function call; did not execute.  nError   [Int],  IPAddress   [String],  Port   [Int]  

Explanation    The SetSockOpt() function call returned error and did not execute.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kTFTPServerListenCloseSockFailed: Error on CloseSocket() function; could not succeed.  Error   [Int]  

Explanation    The CloseSocket() function returned error and could not succeed.

Recommended Action    Run on command prompt NETSTAT -a and redirect its output to a file. This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-1-kTFTPServerListenBindFailed: Socket failure to bind to IP address and port.  nError   [Int],  IPAddress   [String],  Port   [Int]  

Explanation    Socket could not bind to IP address and port.

Recommended Action    Run on command prompt NETSTAT -a and redirect its output to a file. This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kTFTPServerStopListenCloseSockFailed: Closure of the Socket used for listening failure.  Error   [Int]  

Explanation    The Socket being used for listening could not be closed.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kCMCacheIsRealChangeCDBLException: Database exception caught.  Pkid   [String],  Excpt   [String],  Dump   [String]  

Explanation    Database exception was caught.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kCMCacheIsRealChangeComError: _com_error caught.  Pkid   [String],  Excpt   [String]  

Explanation    A _com_error was caught.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kCMCacheIsRealChangeUnknownException: Unknown database exception caught.  Pkid   [String]  

Explanation    Unknown database exception was caught.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kCMCacheBuildCMGrInfoCDBLException: Database exception caught in BuldCallManagerGroupInformation function.  Excpt   [String],  Dump   [String]  

Explanation    Database exception was caught in the BuldCallManagerGroupInformation function.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kCMCacheBuildCMGrInfoComError: _com_error caught in BuldCallManagerGroupInformation function.  Description   [String]  

Explanation    A _com_error was caught in the BuldCallManagerGroupInformation function.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kCMCacheBuildCMGrInfoUnknownException: Unknown database exception caught in BuldCallManagerGroupInformation function. 

Explanation    Unknown database exception was caught in the BuldCallManagerGroupInformation function.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kCNFFBuffWriteToFileLength0: Function returned for zero length of file.  FileName   [String]  

Explanation    Function was returned because the length of file was zero.

Recommended Action    No action is required.

Error Message

%CCM_TFTP-TFTP-6-kCNFFBuffWriteToFilefopenfailed: Write to file failure to open the file handle fopen failure inside write to file.  FileName   [String]  

Explanation    Write to file failed to open the file handle fopen failed inside write to file.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. Start and stop the TFTP service because the file it is trying to open might be in use. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kCNFFBuffWriteToFilefwritefailed: Write to file failure to write, fwrite function failure inside write to file.  FileName   [String]  

Explanation    Write to file failed to write, fwrite function failed inside write to file.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. Start and stop the TFTP service because the file it is trying to open might be in use. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kCNFFBuffWriteToFilefclosefailed: Write to file failed to close the file handle, fclose function failed inside write to file.  FileName   [String]  

Explanation    Write to file failed to close the file handle, fclose function failed inside write to file.

Recommended Action    This is a Windows system call that failed, so ensure that you are using recommended Windows configuration. Start and stop the TFTP service because the file it is trying to open might be in use. If you still get this error, collect TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-4-kCTFTPConnectSendFileTimeoutOccurred: Timeout when sending the file.  Size   [Int],  Block   [Int],  Time   [Int]  

Explanation    Timeout occurred when sending the file.

Recommended Action    Ensure your system is connected to the network. Check windows Taskmanager to make sure TFTP is getting sufficient processor time to serve files. Make sure you are following configuration guide recommendations for your system configuration.

Error Message

%CCM_TFTP-TFTP-3-kCTFTPConnectSendFileNonTimeoutError: NonTimeout error during call to recvfrom().  ErrorNumber   [Int],  Block   [Int]  

Explanation    NonTimeout error occurred during call to recvfrom().

Recommended Action    Ensure your system is connected to the network. Check windows Taskmanager to make sure TFTP is getting sufficient processor time to serve files. Make sure you are following configuration guide recommendations for your system configuration.

Error Message

%CCM_TFTP-TFTP-4-kServingFileWarning: Warning about error inside serving part of TFTP.  ErrorNumber   [Int],  FileName   [String],  IPAddress_Port   [String],  Mode   [String],  OpCode   [Int],  Reason   [String]  

Explanation    Error occurred inside serving part of TFTP.

Recommended Action    If this error reports file not found in its Reason parameter and if that file is OS79XX.TXT, then ignore it because it is a file used for SIP phones. If you are auto-registering a phone and you see that phone MAC-address-based filename in file is not found, ignore that error because this phone is not yet registered with the database. If you still get this error, collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-6-kServingFileNoError: No error but general information about health of serving file operation.  FileName   [String],  IPAddress_Port   [String],  Reason   [String]  

Explanation    No error occurred but provides general information about health of serving file operation.

Recommended Action    No action is required.

Error Message

%CCM_TFTP-TFTP-3-kRecvMessageError: Error could not create CtftpConnect Object.  Reason   [String]  

Explanation    Error could not create CtftpConnect Object.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kThreadPoolProxyUnknownException: Unknown exception was caught in ThreadPoolProxy() of CTftpConnect class. 

Explanation    Unknown exception was caught in ThreadPoolProxy() of CTftpConnect class.

Recommended Action    Collect detailed TFTP service traces and contact TAC.

Error Message

%CCM_TFTP-TFTP-3-kCServiceModuleGetName: Alarm from void GetName() function in CServiceModule.  FileName   [String],  UnknownException   [String]  

Explanation    

Recommended Action    

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 denied. 

Explanation    An operation could not be completed because the process did not have authority to perform it.

Recommended Action    No action is required.

Error Message

%CCM_TFTP-GENERIC-0-ServiceNotInstalled: Service 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 or call TAC.

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    No action is required.

Error Message

%CCM_TFTP-GENERIC-6-ServiceStarted: Service started.  Process ID   [ULong],  IP Address of hosting node.   [String],  Host name of hosting node.   [String],  Service Name   [String],  Version Information.   [String]  

Explanation    A service has started.

Recommended Action    No action is required.

Error Message

%CCM_TFTP-GENERIC-4-ServiceStartupFailed: Service startup failure.  Service Name   [String]  

Explanation    An attempt to start up the specified service failed.

Recommended Action    Restart the service.

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-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_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 denied. 

Explanation    An operation could not be completed because the process did not have authority to perform it.

Recommended Action    No action is required.

Error Message

%CCM_SUMI-GENERIC-0-ServiceNotInstalled: Service 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 or call TAC.

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    No action is required.

Error Message

%CCM_SUMI-GENERIC-6-ServiceStarted: Service started.  Process ID   [ULong],  IP Address of hosting node.   [String],  Host name of hosting node.   [String],  Service Name   [String],  Version Information.   [String]  

Explanation    A service has started.

Recommended Action    No action is required.

Error Message

%CCM_SUMI-GENERIC-4-ServiceStartupFailed: Service startup failure.  Service Name   [String]  

Explanation    An attempt to start up the specified service failed.

Recommended Action    Restart the service.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kReadCfgUserLocaleEnterpriseSvcParm: Error reading Enterprise 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 IP Media Streaming App service.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-6-kRECICMPErrorNotification: REC stream ICMP error.  Call ID   [ULong],  Party ID   [ULong],  Destination IP Address   [String],  IP Port   [ULong]  

Explanation    A REC stream had an ICMP error; stream has been terminated.

Recommended Action    No action is required.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-6-kMCBICMPErrorNotification: MCB stream ICMP error.  Call ID   [ULong],  Party ID   [ULong],  Destination IP Address   [String],  IP Port   [ULong]  

Explanation    A MCB stream had an ICMP error; stream has been terminated.

Recommended Action    No action is required.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-6-kANNICMPErrorNotification: ANN stream ICMP error.  Call ID   [ULong],  Party ID   [ULong],  Destination IP Address   [String],  IP Port   [ULong]  

Explanation    A ANN stream had an ICMP error; stream has been terminated.

Recommended Action    No action is required.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-4-kRECDeviceRecordNotFound: REC device record not found. 

Explanation    A device record for the recorder device was not found in the database.

Recommended Action    If Recording functionality is required, add device to database.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-4-kMCBDeviceRecordNotFound: MCB device record not found. 

Explanation    A device record for the monitor conference bridge device was not found in the database.

Recommended Action    If MCB functionality is required, add device to database.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-4-kANNDeviceRecordNotFound: ANN device record not found. 

Explanation    A device record for the announcer device was not found in the database.

Recommended Action    If annunciator functionality is required, add device to database.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECDistMoveAbort: Aborted moving recording file  File name   [String]  

Explanation    Distribution of a recording file was aborted due to unavailable recording storage server or insufficient free space. The recording file will remain on the local drive until a RSS location is available.

Recommended Action    Check for properly configured Recording Storage Server UNC paths and access rights for the IP Voice Media Storage service. Verify sufficient free space is available on either the primary or secondary RSS paths.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-5-kRECDistSecRSSRecResuming: Resuming distribution recording files to secondary storage server  Secondary path   [String]  

Explanation    The secondary recording storage server now has sufficient free space to resume storing of new recording files.

Recommended Action    No action is required. This is a notification that recordings may resume.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-2-kRECDistSecRSSCritRecStopping: Secondary recording storage server is critically low on free space  Secondary path   [String]  

Explanation    The Secondary recording storage server path has reached the configured critical threshhold on available free disk space. New recordings will be disallowed and the recorder device will unregister from Call Manager.

Recommended Action    Disk file maintenance is required to provide more free space. Suggest that: (a) old recording files be archived and/or deleted, or (b) change the primary/secondary RSS location.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-5-kRECDistPrimRSSRevertFromSecRSS: Resuming distribution recording files to primary storage server from secondary server  Primary path   [String]  

Explanation    The primary recording storage server now has sufficient free space to resume storing of new recording files. The recording files that have been stored on the secondary recording storage server will remain. It is left to the administrator to consolidate these if desired.

Recommended Action    No action is required. This is a notification that new recording files will be distributed to the primary location.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-5-kRECDistPrimRSSRecResuming: Resuming distribution recording files to primary storage server  Primary path   [String]  

Explanation    The primary recording storage server now has sufficient free space to resume storing of new recording files.

Recommended Action    No action is required. This is a notification that recordings may resume.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-2-kRECDistPrimRSSCritRecStopping: Primary recording storage server is critically low on free space  Primary path   [String]  

Explanation    The Primary recording storage server path has reached the configured critical threshhold on available free disk space. No secondary recording storage server is available.

Recommended Action    Disk file maintenance is required to provide more free space. Suggest that: (a) old recording files be archived and/or deleted, (b) reconfigure to provide a secondary recording storage server location, or (c) change the primary RSS location. New recordings will be disallowed and the recorder device will unregister from Call Manager.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-1-kRECDistPrimRSSCritSwitchSecRSS: Primary recording storage server is critically low on free space  Primary path   [String]  

Explanation    The Primary recording storage server path has reached the configured critical threshhold on available free disk space. The recording distribution is switching to the secondary recording storage server.

Recommended Action    Suggest that old recording files be archived and/or deleted to provide additional storage on the primary storage server. New recordings will be distributed to the secondary recording storage server. New recordings will automatically revert to the primary after additional disk space is provided. Recordings that are stored on the secondary server will remain on the secondary server.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECDistFindNextChgFailed: Recording distribution find next directory change notification error  LastError   [ULong],  Path Name   [String]  

Explanation    An error was reported when the application attempted to re-enable directory change notifications. This may be caused by security privilages or configuration changes.

Recommended Action    No action is required unless this occurs repeatedly. The service will automatically attempt to reinitialize monitoring of the configured local path.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECDistThreadException: Recording distribution 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 recording distribution processing to terminate. Distribution of recording files will not be performed and may cause recording failures when a shortage of disk storage is reached.

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-kRECDistThreadxFailed: Recorder distribution manager thread creation failed  LastError   [ULong]  

Explanation    The recording file distribution thread failed to create possibly due to low system resources.

Recommended Action    Reboot server.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECDistExitEventCreationFailed: REC Distribution Manager exit event error  LastError   [ULong]  

Explanation    The needed events could not be created,; distribution of recording files will NOT be performed. This error may be caused by a shortage of system resources.

Recommended Action    The service needs to be restarted; if the error occurs again, the server needs to be rebooted.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECSessMoveFileFailed: Local move recording file error  LastError   [ULong],  Source File Name   [String],  Target File Name   [String]  

Explanation    An error was reported when attempting to move a new recording WAV file from the local recording path into the distribution directory. This may be caused by security access rights or available disk storage.

Recommended Action    Correct the problem and restart the IP Media Streaming App service.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECSessCreateWavFailed: Create WAV file error  LastError   [ULong],  File Name   [String]  

Explanation    An error was reported when attempting to create a WAV file for recording. This may be caused by security access rights or available disk storage.

Recommended Action    Correct the problem and restart the IP Media Streaming App service.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECSessLocalPathFull: Local Recording disk storage shortage  Free K-Bytes   [ULong],  Minimum K-Bytes   [ULong],  Local Recording Path   [String]  

Explanation    The current amount of available disk storage for containing local real-time recording files is below the configured minimum. New recording sessions will not be allowed until additional free space is provided.

Recommended Action    Perform neccessary disk file maintenance such as: (a) Remove old temporary or unneeded disk files. (b) Move or archive old recording files. (c) Delete old log files. (d) Reconfigure the local recording path to a different local disk drive with more free space.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECSessCreateEventError: REC session event creation error  LastError   [ULong]  

Explanation    The needed event could not be created,; the recording session will abort. This may be caused by low system resources.

Recommended Action    If the error continues, the service needs to be restarted.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECMgrRecordSessionException: Unknown exception in recording session 

Explanation    An unknown program exception has caused a recorder session to terminate. This affects only one recording session.

Recommended Action    If this problem continues then restart the IP Media Streaming App service and report the problem with CMS trace logs and Application event logs.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECMgrThreadException: Recorder 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 recorder stream processing for recording to disk 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-kRECMgrThreadxFailed: Recorder manager thread creation failed  LastError   [ULong]  

Explanation    The recorder thread failed to create possibly due to low system resources.

Recommended Action    Reboot server.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECMgrExitEventCreationFailed: REC Manager exit event error  LastError   [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-kRECMgrDeleteFileFailed: REC file deletion error  LastError   [ULong],  File Name   [String]  

Explanation    The operating system reported an error when attempting to delete a file. This may be due to incorrect security privilages.

Recommended Action    Correct the error and restart the IP Media Streaming App Service.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kRECMgrCreateDirFailed: REC create directory failed  LastError   [ULong],  Path   [String]  

Explanation    The operating system reported an error when attempting to create a subdirectory. This may be due to incorrect security privilages or incorrect service parameter settings.

Recommended Action    Correct the error and restart the IP Media Streaming App Service.

Error Message

%CCM_MEDIA_STREAMING_APP-IPVMS-3-kPWavMgrThreadxFailed: WAV playing manager thread creation failed  LastError   [ULong]  

Explanation    The WAV file playing thread failed to create possibly due to low system resources.

Recommended Action    Reboot 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.</