New and Changed Document for Cisco Unified Communications Manager 8.0(1)
Cisco Unified Serviceability, RTMT, CAR, and CDRs
Downloads: This chapterpdf (PDF - 1.22MB) The complete bookPDF (PDF - 6.42MB) | Feedback

Cisco Unified Serviceability, RTMT, CAR, and CDRs

Table Of Contents

Cisco Unified Serviceability, RTMT, CAR, and CDRs

Real Time Monitoring Tool

Ability to Monitor Cisco Unified Communications Manager Attendant Console Removed

New Windows in RTMT

Learned Patterns and SAF Forwarder Reports

Analysis Manager

Alerts

LowAttendantConsoleServerHeartbeatRate Alert Removed from RTMT

Email Sender User ID and Domain

Reset Alert to Default Configuration

Custom Alert Migration

New System Cleared Timestamp Column

Alarm Details Concatenation

New Alert Manager Route List Destination

Performance Monitoring Counters

Log Compression

Secure Hash Algorithms

Solution Level Debug

Daylight Savings Time

Cisco Unified Communications Manager CDR Analysis and Reporting

New Cisco CAR DB Alarms

New CAR Object and Counters

Hunt/CTI Integration for CAR Reporting

CAR and CDRM Alarm Interface

System-Wide Call Tracking End-to-End Call Trace

Call Detail Records

End-to-End Call Trace

Remote Destination to Number Mapping and CDRs

New CDR Fields to Support Call Control Discovery

New CDR Fields to Support External Call Control

New CDR Support for iSAC Codec

New CDR Fields for Hunt List Support

Cisco Unified Serviceability

GUI Changes

New or Updated Services

SNMP and MIBS

Event/Alarm Logging Format and Output

Alarms to Prevent Flooding

Authentication Failure Alerts

New Alarms in Audit Log Catalog

AdministrativeEvent

CriticalEvent

SecurityEvent

New Alarms in EM Alarm Catalog

EMAppInitializationFailed

EMAppStarted

EMAppStopped

EMCCFailedInLocalCluster

EMCCFailedInRemoteCluster

EMCCUserLoggedIn

EMCCUserLoggedOut

EMServiceConnectionError

NodeNotTrusted

UserInputFailure

New Alarms in TVS Alarm Catalog

ConfigThreadChangeNotifyServerSingleFailed

ConfigThreadReadConfigurationFailed

DefaultDurationInCacheModified

ITLFileRegenerated

RollBackToPre8.0Disabled

RollBackToPre8.0Enabled

SDIControlLayerFailed

TVSCertificateRegenerated

TVSServerListenBindFailed

TVSServerListenSetSockOptFailed

New Alarms in CallManager Alarm Catalog

CMVersionMismatch

ConflictingDataIE

DbInfoCorrupt

DbInfoError

DbInfoTimeout

DbInsertValidatedDIDFailure

EndPointRegistered

EndPointResetInitiated

EndPointRestartInitiated

EndPointTransientConnection

EndPointUnregistered

FirewallMappingFailure

IMEDistributedCacheInactive

IMEOverQuota

IMEQualityAlertEntry

IMEQualityAlertExit

InsufficientFallbackIdentifiers

InvalidCredentials

InvalidSubscription

PublicationRunCompleted

PublishFailed

PublishFailedOverQuota

RouteRemoved

RejectedRoutes

TCPSetupToIMEFailed

TLSConnectionToIMEFailed

New SAF and CCD Alarms

CCDIPReachableTimeOut

CCDPSTNFailOverDurationTimeOut

CCDLearnedPatternLimitReached

DuplicateLearnedPattern

LostConnectionToSAFForwarder

SAFForwarderError

SAFUnknownService

SAFPublishRevoke

SAFResponderError

New Alarms in External Call Control

AwaitingResponseFromPDPTimeout

CallAttemptBlockedByPolicy

ConnectionFailureToPDP

ConnectionToPDPInService

DigitAnalysisTimeoutAwaitingResponse

ErrorParsingResponseFromPDP

ErrorParsingDirectiveFromPDP

FailureResponseFromPDP

FailedToFulfillDirectiveFromPDP

New Alarms in Certificate Monitor Alarm Catalog

CertValidLessthanADay

CertValidfor7days

CertValidityOver30Days

CertValidLessThanMonth

New Alarms in CMI Alarm Catalog

CMIException

CMIServiceStatus

DBLException

InvalidPortHandle

MemAllocFailed

ParityConfigurationError

ReadingFileFailure

SMDICmdError

SMDIMessageError

SerialPortGetStatusError

SerialPortOpeningError

SerialPortSetStatusError

StopBitConfigurationError

ThreadKillingError

UnknownException

VMDNConfigurationError

WritingFileFailure

New Alarms in CTI Manager Alarm Catalog

ApplicationConnectionDropped

ApplicationConnectionError

CtiDeviceClosed

CtiDeviceInService

CtiDeviceOpenFailure

CtiDeviceOpened

CtiDeviceOutofService

CtiIncompatibleProtocolVersion

CtiLineClosed

CtiLineInService

CtiLineOpenFailure

CtiLineOpened

CtiLineOutOfService

CtiMaxConnectionReached

CtiProviderCloseHeartbeatTimeout

CtiProviderClosed

CtiProviderOpenFailure

CtiProviderOpened

CtiQbeFailureResponse

InvalidQBEMessage

MaxDevicesPerNodeExceeded

MaxDevicesPerProviderExceeded

RedirectCallRequestFailed

UnableToRegisterwithCallManagerService

UnableToSetorResetMWI

New Alarms in DRF Alarm Catalog

DRFBackupCompleted

DRFLocalDeviceError

DRFNoBackupTaken

DRFRestoreCompleted

New Alarm in IpVms Alarm Catalog

kANNAudioFileMissing

New Alarms in JavaApplications Alarm Catalog

CiscoHardwareLicenseInvalid

CiscoLicenseFileInvalid

New Alarm in RTMT Alarm Catalog

RTMT_ALERT

Changed Alarms in CallManager Alarm Catalog

AnnunciatorNoMoreResourcesAvailable

BChannelISV

BChannelOOS

BeginThrottlingCallListBLFSubscriptions

CMInitializationStateTime

CMOverallInitTimeExceeded

CMTotalInitializationStateTime

CallManagerFailure

CallManagerOnline

CodeRedEntry

CodeYellowEntry

CodeYellowExit

ConferenceNoMoreResourcesAvailable

ConnectionFailure

DBLException

DChannelISV

DChannelOOS

DaTimeOut

DatabaseDefaultsRead

DeviceApplyConfigInitiated

DeviceCloseMaxEventsExceeded

DeviceDnInformation

DeviceInitTimeout

DevicePartiallyRegistered

DeviceRegistered

DeviceResetInitiated

DeviceRestartInitiated

DeviceTransientConnection

DeviceTypeMismatch

DeviceUnregistered

EndThrottlingCallListBLFSubscriptions

H323Started

H323Stopped

ICTCallThrottlingEnd

ICTCallThrottlingStart

MGCPGatewayGainedComm

MaliciousCall

MaxCallDurationTimeout

MaxCallsReached

MaxHoldDurationTimeout

MediaResourceListExhausted

MohNoMoreResourcesAvailable

MtpNoMoreResourcesAvailable

MultipleSIPTrunksToSamePeerAndLocalPort

NoFeatureLicense

NotEnoughChans

NumDevRegExceeded

PktCapOnDeviceStarted

PktCapOnDeviceStopped

PktCapServiceStarted

PktCapServiceStopped

RouteListExhausted

RsvpNoMoreResourcesAvailable

SDLLinkISV

SDLLinkOOS

SIPLineRegistrationError

SIPStarted

SIPStopped

StationAlarm

StationConnectionError

StationEventAlert

StationTCPInitError

TimerThreadSlowed

UserUserPrecedenceAlarm

Changed Alarms in CDRRep Alarm Catalog

CDRAgentSendFileFailed

CDRAgentSendFileFailureContinues

CDRFileDeliveryFailed

CDRFileDeliveryFailureContinues

CDRHWMExceeded

CDRMaximumDiskSpaceExceeded

Changed Alarms in DB Alarm Catalog

ErrorChangeNotifyClientBlock

ErrorReadingInstalledRPMS

IDSEngineCritical

IDSEngineDebug

IDSReplicationInformation

Changed Alarms in IMS Alarm Catalog

AdminPassword

authAdminLock

authExpired

authFail

authHackLock

authInactiveLock

authLdapInactive

authMustChange

authSuccess

credFullUpdateFailure

credFullUpdateSuccess

credReadFailure

credReadSuccess

credUpdateFailure

credUpdateSuccess

Changed Alarms in IpVms Alarm Catalog

ANNDeviceRecoveryCreateFailed

CFBDeviceRecoveryCreateFailed

MOHDeviceRecoveryCreateFailed

MTPDeviceRecoveryCreateFailed

SoftwareLicenseNotValid

SoftwareLicenseValid

kANNAudioCreateDirFailed

kANNAudioUndefinedAnnID

kANNAudioUndefinedLocale

kANNDeviceRecordNotFound

kANNDeviceStartingDefaults

kANNICMPErrorNotification

kCFBDeviceRecordNotFound

kCFBDeviceStartingDefaults

kCFBICMPErrorNotification

kChangeNotifyServiceCreationFailed

kChangeNotifyServiceGetEventFailed

kChangeNotifyServiceRestartFailed

kCreateAudioSourcesFailed

kCreateControlFailed

kDeviceDriverError

kDeviceMgrCreateFailed

kDeviceMgrExitEventCreationFailed

kDeviceMgrLockoutWithCallManager

kDeviceMgrMoreThan50SocketEvents

kDeviceMgrOpenReceiveFailedOutOfStreams

kDeviceMgrRegisterKeepAliveResponseError

kDeviceMgrRegisterWithCallManager

kDeviceMgrRegisterWithCallManagerError

kDeviceMgrSocketDrvNotifyEvtCreateFailed

kDeviceMgrSocketDrvNotifyEvtCreateFailed

kDeviceMgrStartTransmissionOutOfStreams

kDeviceMgrThreadWaitFailed

kDeviceMgrThreadxFailed

kDeviceMgrUnregisterWithCallManager

kFixedInputCodecStreamFailed

kFixedInputCreateControlFailed

kFixedInputCreateSoundCardFailed

kFixedInputInitSoundCardFailed

kFixedInputTranscoderFailed

kGetFileNameFailed

kIPVMSDeviceDriverNotFound

kIPVMSMgrEventCreationFailed

kIPVMSMgrThreadxFailed

kIPVMSMgrWrongDriverVersion

kIPVMSStarting

kIPVMSStopping

kIpVmsMgrNoLocalHostName

kIpVmsMgrNoLocalNetworkIPAddr

kIpVmsMgrThreadWaitFailed

kMOHBadMulticastIP

kMOHDeviceRecordNotFound

kMOHICMPErrorNotification

kMOHMgrCreateFailed

kMOHMgrExitEventCreationFailed

kMOHMgrIsAudioSourceInUseThisIsNULL

kMOHMgrThreadWaitFailed

kMOHMgrThreadxFailed

kMOHRewindStreamControlNull

kMOHRewindStreamMediaPositionObjectNull

kMOHTFTPGoRequestFailed

kMTPDeviceRecordNotFound

kMTPDeviceStartingDefaults

kPWavMgrThreadxFailed

kReadCfgIpTosMediaResourceToCmNotFound

kReadCfgMOHEnabledCodecsNotFound

kReadCfgUserLocaleEnterpriseSvcParm

kRequestedANNStreamsFailed

kRequestedCFBStreamsFailed

kRequestedMOHStreamsFailed

kRequestedMTPStreamsFailed

Changed Alarms in JavaApplications Alarm Catalog

IPMAFilteringDown

WDStopped

Changed Alarms in Login Alarm Catalog

AuthenticationFailed

Changed Alarms in LpmTct Alarm Catalog

CoreDumpFileFound

LogCollectionJobLimitExceeded

LogFileSearchStringFound

LogPartitionHighWaterMarkExceeded

LogPartitionLowWaterMarkExceeded

SparePartitionHighWaterMarkExceeded

SparePartitionLowWaterMarkExceeded

Changed Alarms in SystemAccess Alarm Catalog

TotalProcessesAndThreadsExceededThresholdEnd

Changed Alarms in TFTP Alarm Catalog

CNFFBuffWriteToFilefopenfailed

CNFFBuffWriteToFilefwritefailed

ConfigItAllBuildFilesFailed

ConfigItAllReadConfigurationFailed

ConfigThreadBuildFileFailed

ConfigThreadCNCMGrpBuildFileFailed

ConfigThreadCNGrpBuildFileFailed

ConfigThreadChangeNotifyServerInstanceFailed

ConfigThreadChangeNotifyServerSingleFailed

ConfigThreadChangeNotifyServerStartFailed

ConfigThreadReadConfigurationFailed

CreateThreadFailed

NoCallManagerFound

SDIControlLayerFailed

Obsolete Alarms

Obsolete Alarms in CallManager Catalog

Obsolete Alarms in CertMonitor Alarm Catalog

Obsolete Alarms in CMI Alarm Catalog

Obsolete Alarms in CTI Manager Alarm Catalog

Obsolete Alarms in DB Alarm Catalog

Obsolete Alarms in IpVms Alarm Catalog

Obsolete Alarms in Test Alarm Catalog


Cisco Unified Serviceability, RTMT, CAR, and CDRs


This chapter contains information on the following topics:

Real Time Monitoring Tool

Cisco Unified Communications Manager CDR Analysis and Reporting

Call Detail Records

Cisco Unified Serviceability

Real Time Monitoring Tool

This section contains information on the following topics:

Ability to Monitor Cisco Unified Communications Manager Attendant Console Removed

New Windows in RTMT

Alerts

Performance Monitoring Counters

Log Compression

Secure Hash Algorithms

Solution Level Debug

Daylight Savings Time

Ability to Monitor Cisco Unified Communications Manager Attendant Console Removed

In RTMT, you cannot monitor the heartbeat of the Cisco CallManager Attendant Console Server service because the functionality has been removed in 8.0(1).

New Windows in RTMT

This section contains information on the following topics:

Learned Patterns and SAF Forwarder Reports

Analysis Manager

Learned Patterns and SAF Forwarder Reports

The Learned Patterns and SAF Forwarders reports support the call control discovery feature, which you configure in Cisco Unified Communications Manager Administration.

Learned Pattern reports include such information as learned pattern name, time stamp, reachability status for the pattern, remote call-control entity that hosts the pattern, the PSTN failover configuration, and so on. RTMT allows you to search based on different criteria; for example, if you specify a search for the remote call-control entity, all the learned patterns display for the remote call-control entity.

Supported with the call control discovery feature, a SAF forwarder notifies the local Cisco Unified Communications Manager cluster when remote call-control entities advertise their hosted DNs patterns. In addition, the SAF forwarder receives publishing requests from the local Cisco Unified Communications Manager cluster to advertise the hosted DN patterns for the local cluster. SAF Forwarder reports display information such as authentication status, status of SAF forwarders, and so on.

GUI Changes

To access the reports, perform one of the following tasks:

From the RTMT menus, choose CallManager > Report > Learned Pattern (or SAF Forwarders)

Click the CallManager tab; then, click Learned Pattern or SAF Forwarders.

Table 5-1 describes the data from the Learned Pattern report. Table 5-2 describes the data from the SAF Forwarders report.

Table 5-1 Data from Learned Pattern Report 

Column
Description

Pattern

Displays the name of the learned pattern from the remote call-control entity.

TimeStamp

Displays the date and time that the local Cisco Unified Communications Manager marked the pattern as a learned pattern.

Status

Indicates whether the learned pattern was reachable or unreachable

Protocol

Displays the protocol for the SAF-enabled trunk that was used for the outgoing call to the learned pattern; if the remote call-control entity has QSIG tunneling configured for the SAF-enabled trunk, the data indicates that QSIG tunneling was used; for example, EMCA is listed along with H.323 in this column.

AgentID

Displays the cluster name of the remote call-control entity that advertised the learned pattern

IP Address

Displays the IP address for the call control entity that advertised the learned pattern; displays the port number that was used to connect to the SAF network.

ToDID

Displays the PSTN failover configuration for the learned pattern; for example, 0:92781 indicates that you want to strip 0 digits and prepend the value, 92781, to the pattern if PSTN failover occurs.

CUCMNodeId

Displays the ID from the local Cisco Unified Communications Manager node.


Table 5-2 Data from SAF Forwarder Report 

Column
Description

Name

Displays the name of the SAF forwarder that you configured in the SAF Forwarder Configuration window in Cisco Unified Communications Manager Administration.

Description

Displays the description for the SAF forwarder that you configured in the SAF Forwarder Configuration window in Cisco Unified Communications Manager Administration. If None displays, you did not enter a description for the SAF forwarder.

IP Address

Displays the IP address for the SAF forwarder, as configured in the SAF Forwarder Configuration window in Cisco Unified Communications Manager Administration.

Port

Indicates the port number that Cisco Unified Communications Manager uses to connect to the SAF forwarder; by default, Cisco Unified Communications Manager uses 5050.

Type

Indicates whether the SAF forwarder is classified as the primary or backup SAF forwarder.

Connection Status

Indicates whether Cisco Unified Communications Manager can connect to the SAF forwarder.

Authentication Type

Indicates that Cisco Unified Communications Manager used digest authentication to connect to the SAF forwarder.

Registration Status

Indicates whether the Cisco Unified Communications Manager is registered to the SAF forwarder.

Time Last Registered

Displays the date and time when the Cisco Unified Communications Manager last registered with the SAF forwarder.

No of Registered Applications

Displays the total number of CCD advertising and requesting services that are registered to the SAF forwarder

No of Connection Re-Attempts

Displays the number of times that the call-control entity, in this case, the Cisco Unified Communications Manager, has attempted to connect to the SAF forwarder


For More Information

"Monitoring Predefined Cisco Unified Communications Manager Objects" chapter, Cisco Unified Real Time Monitoring Tool Administration Guide

Analysis Manager

The Cisco Unified Analysis Manager is an application included with RTMT that is used to perform troubleshooting operations. When the Cisco Unified Analysis Manager is launched, it collects troubleshooting information from your system and provides an analysis of that information. You can use this information to perform your own troubleshooting operation or send the information to Cisco Technical Assistance for analysis.

The Cisco Unified Analysis Manager application is installed as an option when you install the RTMT software. The Cisco Unified Analysis Manager interface is accessed from a drawer on the RTMT main menu.

Once it is installed, the application can identify the supported UC products and applications that you have in your system and troubleshoot call failures across these UC applications, collecting trace and log files.

The Cisco Unified Analysis Manager will support the following products:

Cisco Unified Communications Manager Release 8.0

Unified CCE Release 8.0(1)

Unified CCX Release 8.0

IOS Voice Gateways (37xx, 28xx, 38xx, 5350XM, 5400XM) IOS Release PI 11.

Unified Expert Advisor Release 7.6(1)

Unity Connection Release 8.0

Unified Presence Release 8.0(2)

The three primary components of the Cisco Unified Analysis Manager interface are:

System—The system component lets you import device and group configuration from an external file and provide a status of jobs run by the Cisco Unified Analysis Manager.

Inventory—The inventory component is used to identify all of the devices in your system that can be accessed and analyzed by the Cisco Unified Analysis Manager.

Tools —The tools component contains all of the functions that Cisco Unified Analysis Manager supports. This includes configuring traces settings, collecting logs and viewing configurations.

For more information, see the Cisco Unified Real Time Monitoring Tool Administration Guide.

Alerts

Cisco Unified Communications Manager Real Time Monitoring Tool has a new alert architecture. The enhancements include the following:

Unique alarms for each alert with one format for all. Each alert has a specific list of parameters and recommended actions viewable on the Cisco Unified Serviceability window instead of logging into Real Time Monitoring Tool.

Cisco default thresholds settings for each alert changeable by a user.

Alert email sender ID and domain name configurable.

Alert Central has a new column to indicate the alert clear time when the trigger condition no longer exists.

The following enhancements get described in this section:

LowAttendantConsoleServerHeartbeatRate Alert Removed from RTMT

Email Sender User ID and Domain

Reset Alert to Default Configuration

Custom Alert Migration

New System Cleared Timestamp Column

Alarm Details Concatenation

New Alert Manager Route List Destination

LowAttendantConsoleServerHeartbeatRate Alert Removed from RTMT

The LowAttendantConsoleServerHeartbeatRate alert, which supports Cisco Unified Communications Manager Attendant Console, has been removed from RTMT.

Email Sender User ID and Domain

Enhanced mail server configuration window enables you to change the sender user ID and domain when sending an alert email. By default, RTMT_Admin@domain gets used and domain is the host server domain.

Reset Alert to Default Configuration

The Reset Alert to Default Config option in Real Time Monitoring Tool enables the use of Cisco default setting for one alert or globally. To set an individual alert in the Quick Launch Channel pane, click System > Alert Central. Then click the System, Unified CM (CallManager), or Custom tab, depending on the type of alert. Right-click the alert name. A drop-down menu displays. Click Reset Alert to Default Config.

To set the global option for all alerts to the Cisco default gets performed from the main menu. Click System > Tools > Alert > Reset All Alerts to Default Config.

Custom Alert Migration

In this release, only one performance counter can be associated with one custom alert. Any multicounter custom alerts from prior releases do not get migrated and get deleted. Information from the deleted custom alerts gets logged.

To configure a custom alert for a counter, click the counter in Performance or drag and drop it in the Monitoring pane. Highlight the counter and right-click to display a menu. Click Set Alert/Properties.

New System Cleared Timestamp Column

Alert Central has a new column in its display called System Cleared Timestamp. The column contains the time when the condition was cleared. The timestamp is not updated when the alert gets manually reset. When an alert clears, the event gets logged in the alert log and an email gets sent.

Alarm Details Concatenation

All alarm details that get collected within the same poll are concatenated in this release.

New Alert Manager Route List Destination

In this release, there is a new configurable route list destination called "Alert Manager." Alert Manager tracks and gathers alert conditions from performance monitoring events, and Scheduler scripts; evaluates the conditions to take action based on frequency settings, or clears the alerts. The actions that the Alert Manager take can be e-mail/e-page, Syslog, Trace Collection, and Alert Log.

Passing events to the Alert Manager gets performed by the alarm interface which writes the alarm information to a Memory Map File (MMF) and transparently passes the information to the Real-Time Information Service Data Collector (RISDC). The RISDC passes the service name, alarm catalog subfacility name, alarm name, key parameter values, AlarmRunTimeSeverity, timestamp when the alarm gets generated, nodeID, and alarm message content to the AMC.

Performance Monitoring Counters

Performance counters for Extension Mobility Cross Cluster feature

The following performance counters are added for the Extension Mobility Cross Cluster feature:

Total Number of EMCC Messages—This represents the total number of messages related to EMCC Requests that came from remote clusters.

Number of Remote Devices—This represents the total number of devices from other clusters that are currently using a EMCC Base Device (EMCC Logged in).

Number of Unknown Remote Users—This represents the total number of users who were not found in any of the remote cluster during inter-cluster extension mobility login.

Active Inter-cluster Sessions—This represents the total number of inter cluster Extension Mobility requests that are currently in progress.

Total Number of Remote Users—This represents the total number of users from other cluster who use a local device of this cluster and have logged into a remote cluster.

EMCC Check User Requests Handled—This represents the total number of EMCC check user requests that came from remote clusters.

New SAF Client Object and Counters

The following SAF counters are added to the Cisco SAF Client object and are specific to each node:

SAFConnectionsSucceeded (range from 0 to 2)—Total number of SAF client connections currently active on this Unified CM node.

SAFFConnectionsFailed (range from 0 to 2)—Total number of SAF client connections that failed on the Unified CM node. A failed connection is a connection that did not register with the SAF Forwarder.


Note A Cisco Unified CM node restart causes a counter reset.


In the Real Time Monitoring Tool window, there is a new SAF option for the CallManager category that displays:

SAFF connectivity status

Each SAFF IP address

Connection status

Uptime since the Cisco Unified CM node started

Downtime since the Cisco Unified CM node started

External Call Control (Call Intercept) Counters and Alarms

The following counters are added to support the External Call Control feature:

Cisco Unified Communication Manager (Cisco CallManager) Object:

ExternalCallControlEnabledCallsAttempted—This counter specifies the total number of calls to devices that have the External Call Control feature enabled. This is a cumulative count of all calls to intercept-enabled patterns or DNs since the last restart of the Cisco CallManager service.

ExternalCallControlEnabledCallsCompleted—This counter specifies the total number of calls that were connected to a device that had the External Call Control feature enabled. This is a cumulative count of all calls to intercept-enabled patterns or DNs since the last restart of the Cisco CallManager service.

ExternalCallControlEnabledFailureTreatmentApplied—This counter specifies the total number of calls that were cleared or routed based on failure treatments (such as Allow or Deny) that are defined in the External Call Control profile.

External Call Control Objects:

PDPServersTotal—This counter defines the total number of PDP servers in all External Call Control Profiles configured in Cisco Unified CM Administration. This counter increments when a new PDP server is added and decrements when a PDP server is removed.

PDPServersInService—This counter defines the total number of in-service (active) PDP servers.

PDPServersOutOfService—This counter defines the total number of times that PDP servers have transitioned from in-service to out-of-service. This is a cumulative count of out-of-service PDP servers since the last restart of the Cisco CallManager service.

ConnectionsActiveToPDPServer—This counter specifies the total number of connections that Cisco Unified Communications Manager has established (currently active) with PDP servers.

ConnectionsLostToPDPServer —This counter specifies the total number of times that active connections between Cisco Unified Communications Manager and the PDP servers were disconnected. This is a cumulative count since the last restart of the Cisco CallManager service.

Feature Control Policy Performance Counters

The Feature Control Policy feature contains the following two new counters for TFTP:

BuildFeaturePolicyCount—Indicates the number of built FCP files

FeaturePolicyChangeNotifications—Indicates the number of sent FCP change notifications

Cisco TFTP sends two new alarm parameters of the BuildStat alarm (System/TFTPAlarmCatalog) that are as follows:

FeatureControlPolicyCount—Indicates the number of FCP files built

FeatureControlPolicyTime—Indicates the time taken to build the files

Cisco TFTP listens for a change notification from the Feature Control Policy table. If it receives a CN, TFTP rebuilds the feature policy file and updates the corresponding one or more of the device configuration files. After installation and if the default feature policy gets changed, or the new policy controlled features gets added, Cisco TFTP builds all of the Feature Control Policy configuration files again and the system is restarted.

Log Compression

In previous releases of Cisco Unified Communications Manager and Cisco Unified Communications Manager Business Edition, there were trace service parameters that enabled and disabled log file compression to the hard disk. The service parameters have been deprecated along with that feature.

There is a new implementation of log compression in 8.0, and is not configurable.

The new log compression feature only compresses the following log files:

cm/trace/cti/sdl

cm/trace/cti/sdi

cm/trace/ccm/sdl

cm/trace/ccm/sdi

The other log files are not compressed and are written directly to the hard disk.

The compressed files have a .gz extension. The file that is being actively written to the disk will have a .gzo extension.

All the CLI commands used to view and tail the files will work on the compressed files and will automatically uncompress them for viewing or tailing. The only difference is in specifying file names with the .gz and .gzo extension.

There is a new option available with the file tail command as follows:

file tail activelog cm/trace/cti/sdl recent

The recent option, when used with a compressed directory, will continually tail the most recent log file. It is not necessary to switch to a newer log file when the currently written-to log file is closed, so it is an infinite and ongoing tail. This option is only available with the compressed log files.

The log files are compressed in the gzip format. For uncompressing the log files, the open source program 7-Zip is available at http://www.7-zip.org, and works on all Windows platforms. You can use 7-Zip on any computer, including a computer in a commercial organization. You don't need to register or pay for 7-Zip. On a linux platform, you can use the gzip or gunzip commands.

Secure Hash Algorithms

The Secure Hash Algorithm (SHA) family is a set of related cryptographic hash functions. The new CP Assist for Cryptographic Function (CPACF) includes the ability to generate SHA-256 hash codes. The hash code produced by SHA-1 is 20 bytes long, whereas the hash code produced by SHA-256 is 32 bytes long.

Cisco Unified Real Time Monitoring Tool uses Sun JRE/JDK version 1.5 and later as the JVM engine. Due to import control restrictions, the version of JCE policy files that get bundled in the JDKTM version 5.0, allow "strong but limited" cryptography. This download bundle (the one that includes a README file) provides unlimited strength policy files which contain no restrictions on cryptographic strengths.


Note The download file does not contain any encryption functionality since such functionality is supported in Sun JDK version 5.0. So, download applies only to Sun JDK version 5.0 and assumes that the JDK version 5.0 is already installed. RTMT supports JCE as separate install from Sun.


Procedure to Download "Unlimited Strength" JCE Policy Files


Step 1 Download the unlimited strength JCE policy files.

Step 2 Uncompress and extract the downloaded file. A subdirectory gets created called "jce." This directory contains the following files:

README.txt

COPYRIGHT.html

local_policy.jar (Unlimited strength local policy file)

US_export_policy.jar (Unlimited strength US export policy file)

Step 3 Install the unlimited strength policy JAR files.

To use the encryption/decryption functionality of the JCE framework without any limitation, first make a copy of the original JCE policy files (US_export_policy.jar and local_policy.jar in the standard place for JCE jurisdiction policy JAR files) in case you later decide to revert to these "strong" versions. Then replace the strong policy files with the unlimited strength versions extracted in the previous step.

CA signed certificate need to be supported by RTMT. RTMT needs GUI enhancement to upload CA/Root certificates just like IE browser.


Solution Level Debug

In prior Cisco Unified Serviceability releases, each component set a trace by using multiple tools. The tools set the tracing for each subcomponent. In this release, Cisco Unified Serviceability supports the following changes:

Tracing Interfaces—All Unified Communications components get displayed and tracing levels get specified for contact center applications. There are two methods to set tracing on multiple devices: One is to manually select the devices from a list and the other is to select a user-defined group that contains one or more devices. There is a GUI that displays the number of components and subcomponents involved so that tracing can be configured.

System-Defined Tracing Levels—The system-level tracing interface sets the level of tracing based on well defined tracing levels. The simple tracing levels get mapped to each relevant application and each component. For example, to turn the debugging on and off, the user specifies debug LEVEL0. This level turns off all tracing. The default specifies call trace and is equivalent to undebug all. The levels are:

Debug LEVEL0—Turns off all tracing (default includes call trace and equivalent to undebug all)

Debug LEVEL1—Turns on interface tracing (can perform during production with little impact to performance)

Debug LEVEL2—Turns on LEVEL 1 and message tracing (can perform during production with little impact to performance but only during light load conditions like off peak hours)

Debug LEVEL3—Turns on LEVEL 2 and detailed debugs (impacts performance and can only be run for a single call and when system is idle or during maintenance window)

Default Tracing Levels—The default trace levels, at the minimum, get displayed or printed as a single line of message. For example, ANI, DNIS, local Call ID and global Call-ID for every component/subsystem as the call traverses through it. This single line of trace from each subsystem does not affect the performance or input/output.

Daylight Savings Time

This section contains Real Time Monitoring Tool changes to support Daylight Savings Time (DST). Cisco Unified uses client-side JDK/JRE. Real Time Monitoring Tool uses Sun TZUpdater utility during installation.

Cisco Unified Communications Manager CDR Analysis and Reporting

The functionality of Call Detail Records (CDR) Analysis and Reporting (CAR) is primarily to generate reports on Unified CM users and system status with respect to call processing records that are loaded to CAR database. CAR also does some CAR database management activities. CAR automatically schedules required tasks to take place or you can manually perform the tasks by using the web interface.

The following topics are described in this section:

New Cisco CAR DB Alarms

New CAR Object and Counters

Hunt/CTI Integration for CAR Reporting

CAR and CDRM Alarm Interface

System-Wide Call Tracking End-to-End Call Trace

New Cisco CAR DB Alarms

New alarms for the CAR DB instance separation get added in this release. A new thread of [CARIDSAlarm] gets created in the existing CAR Scheduler Service to receive the IDS alarms. There are four new categories and alarms with information specific to the IDS based on the class IDs.

The following new alarms support the CAR database instance:

CARIDSEngineDebug

CARIDSEngineInformation

CARIDSEngineCritical

CARIDSEngineFailure


Note For any alarms with severity levels at or higher than Critical, an alert gets automatically generated.


CARIDSEngineDebug

Indicates debug events from CAR IDS database engine. This alarm provides low-level debugging information from CAR IDS database engine. System administrator can disregard this alarm.

Cisco Unified Serviceability Catalog

CallManager/CARAlarmCatalog

Severity

Debug(7)

Routing List

SDI

Event Log

Parameters

Event Specific Message(String)

Event class message(String)

Event Class ID(String)

Recommended Action

None

CARIDSEngineInformation

No error has occurred but some routine event completed in CAR IDS database engine.

Cisco Unified Serviceability Catalog

CallManager/CARAlarmCatalog

Severity

Informational(6)

Routing List

SDI

Event Log

Parameters

Event Specific Message(String)

Event class message(String)

Event Class ID(String)

Recommended Action

None

CARIDSEngineCritical

This alarm does not compromise data or prevent the use of the system but does required attention.

Cisco Unified Serviceability Catalog

CallManager/CARAlarmCatalog

Severity

Critical(2)

Routing List

SDI

Event Log

Sys Log

Alert Manager

Parameters

Event Specific Message(String)

Event class message(String)

Event Class ID(String)

Recommended Action

This alarm needs monitoring by the CAR DB administrator.

CARIDSEngineFailure

Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause CAR IDS to fail.

Cisco Unified Serviceability Catalog

CallManager/CARAlarmCatalog

Severity

Error(3)

Routing List

SDI

Event Log

Sys Log

Alert Manager

Parameters

Event Specific Message(String)

Event class message(String)

Event Class ID(String)

Recommended Action

Requires CAR DB admin intervention.

New CAR Object and Counters

The new CAR counters monitor the CAR database space and shared memory usage. The following CAR counters for the Cisco CAR DB object get supported:

RootDBSpaceUsed—Percentage of Root DB space consumed. The root DB space gets used by the IDS system tables in the CAR IDS instance.

CARDBSpaceUsed—Percentage of CAR DB space consumed. The CAR DB space gets used by the CAR database.

CARTempDBSpaceUsed—Percentage of CAR temporary DB space consumed. The CAR temporary DB space gets used by temporary tables in the CAR IDS instance and used by CAR applications.

FreeSharedMemory—Total free and shared memory expressed in kilobytes (KB). Shared memory gets used by the database system and all database applications in the CAR IDS instance.

UsedSharedMemory—Total used and shared memory expressed in kilobytes (KB). Shared memory gets used by the database system and all database applications in the CAR IDS instance.

There are no performance counters that monitor the CAR IDS processes individually because the counters get automatically added for each new process. The counters get implemented with a new thread/job of the CAR IDS performance in the existing CAR Scheduler service by using Java API (JNI based statsUpdate()).

Hunt/CTI Integration for CAR Reporting

CAR supports hunt groups and contains the following new reports:

Hunt Pilot Summary

Hunt Pilot Detailed Report

Hunt Pilot Summary

Only CAR administrators generate the Hunt Pilot Summary Report.The CDR Hunt Pilot Call Summary report displays the call details for the specified hunt pilot. This report displays an only an overview of the calls for the hunt pilots and hunt member information is not included. The CAR administrator can generate report for a maximum of five hunt pilot DNs.

Hunt Pilot Detailed Report

Only CAR administrators generate the Hunt Pilot Detailed Call Report. This report displays call details for a hunt pilot number or a hunt member DN.

CAR and CDRM Alarm Interface

CAR and CDRM allow the alarm interface to raise alerts. The alarm interface can generate Syslog events, SNMP traps, and e-mail notifications by using RIS/Collector/Alert Manager. CAR allows the performance interface to poll serviceability counters and to be monitored in Cisco Unified Real Time Monitoring Tool.

System-Wide Call Tracking End-to-End Call Trace

The End-to-End Call Trace feature facilitates tracing calls that traverse multiple Cisco voice products, such as Unified CM, Cisco IOS Gateways, and other products.

There are four new CDR fields added: CAR Loader, schema, CDR export, CDR search reports and migration.

For more information about System-Wide Call Tracking (SCT), see End-to-End Call Trace.

Call Detail Records

This feature traces calls that traverse multiple Cisco voice products by using the call records collected from each platform generated for the same call.

This section contains information on the following topics:

End-to-End Call Trace

Remote Destination to Number Mapping and CDRs

New CDR Fields to Support Call Control Discovery

New CDR Fields to Support External Call Control

New CDR Support for iSAC Codec

New CDR Fields for Hunt List Support

End-to-End Call Trace

To support the End-to-End call trace, following new fields have been added in the CDR search reports:

IncomingProtocolID

IncomingProtocolCallRef

OutgoingProtocolID

OutgoingProtocolCallRef

Remote Destination to Number Mapping and CDRs

For an outgoing call to mobile users, the called party information in the CDR gets recorded based on the "Log Mobile Number in CDR" service parameter. The default equals False. If the service parameter is False, the enterprise number of the mobile user gets recorded in the CDR as the called party number. If the service parameter equals True, the mobile number gets recorded in CDR as the called party number.

New CDR Fields to Support Call Control Discovery

New codes display for the call control discovery feature, as described in Table 5-3. (For more information on call control discovery, see the "Call Control Discovery" section on page 2-22.)

Table 5-3 Codes for Call Control Discovery

Value
Type
Description

464

Redirect Reason Code

Indicates that the call is redirected to a PSTN failover number

131

Call Termination Code

Call Control Discovery PSTN Failover (Cisco specific)

29

OnBehalfof Code

CCDRequestingService


New CDR Fields to Support External Call Control

Table 5-4 describes the new CDR fields for the external call control feature. Use Table 5-4 in conjunction with the Table 5-5, which describes the routing reason values that are specific to external call control. (For more information on external call control, see the "External Call Control" section on page 2-123.)

Table 5-4 CDR Fields for External Call Control

Field Name
Range of Values
Description

currentRoutingReason

Positive Integer

This field, which is used with the external call control feature, displays the reason why the call was intercepted for the current call. For a list of reasons, see Table 5-5.

Default value is 0.

origRoutingReason

Positive Integer

This field, which is used with the external call control feature, displays the reason why the call was intercepted for the first time. For a list of reasons, see Table 5-5.

Default value is 0.

lastRedirectingRoutingReason

Positive Integer

This field, which is used with the external call control feature, displays why the call was intercepted for the last time. For a list of reasons, see Table 5-5.

Default - Empty string.


Table 5-5 includes the reasons that can display for the currentRoutingReason, origRoutingReason, or lastRedirectingRoutingReason fields.

Table 5-5 Routing Reason Values for External Call Control

Value that Displays in the Field
Reason
Description

0

PDPDecision_NONE

This value indicates that the route server did not return a routing directive to the Cisco Unified Communications Manager.

1

PDPDecision_Allow_Fulfilled

This value indicates that Cisco Unified Communications Manager allowed a call.

2

PDPDecision_Allow_Unfulfilled

This value indicates that Cisco Unified Communications Manager disallowed a call.

3

PDPDecision_Divert_Fulfilled

This value indicates that Cisco Unified Communications Manager diverted the call.

4

PDPDecision_Divert_Unfulfilled

This value indicates that Cisco Unified Communications Manager was not able to divert the call.

5

PDPDecision_Forward_Fulfilled

This value indicates that Cisco Unified Communications Manager forwarded the call.

6

PDPDecision_Forward_Unfulfilled

This value indicates that Cisco Unified Communications Manager was unable to forward the call.

7

PDPDecision_Reject_Fulfilled

This value indicates that Cisco Unified Communications Manager rejected the call.

8

PDPDecision_Reject_Unfulfilled

This value indicates that Cisco Unified Communications Manager was not able to reject the call.


CAR supports the new fields from the loader, CDR export, and CDR search reports on display and migration.

New CDR Support for iSAC Codec

The codec fields can now support the iSAC (Media_Payload_ISAC) with the value of 89.

New CDR Fields for Hunt List Support

Table 5-6 describes the new CDRs for the hunt list support (see "Hunt List Enhancements" section on page 2-144).

Table 5-6 CDR Fields for Hunt Lists

Field Name
Range of Values
Description

huntPilotDN

Text String

This field indicates the hunt pilot DN through which the call is routed.

Default - Empty string.

huntPilotPartition

Text String

This field indicates the partition for the hunt pilot DN.

Default - Empty string.

huntPilotDN

Text String

This field indicates the hunt pilot DN through which the call is routed.

Default - Empty string.


Cisco Unified Serviceability

This section contains information on the following topics:

GUI Changes

New or Updated Services

SNMP and MIBS

Event/Alarm Logging Format and Output

Alarms to Prevent Flooding

Authentication Failure Alerts

New Alarms in Audit Log Catalog

New Alarms in EM Alarm Catalog

New Alarms in TVS Alarm Catalog

New Alarms in CallManager Alarm Catalog

New Alarms in Certificate Monitor Alarm Catalog

New Alarms in CMI Alarm Catalog

New Alarms in CTI Manager Alarm Catalog

New Alarms in DRF Alarm Catalog

New Alarm in IpVms Alarm Catalog

New Alarms in JavaApplications Alarm Catalog

New Alarm in RTMT Alarm Catalog

Changed Alarms in CallManager Alarm Catalog

Changed Alarms in CDRRep Alarm Catalog

Changed Alarms in DB Alarm Catalog

Changed Alarms in IMS Alarm Catalog

Changed Alarms in IpVms Alarm Catalog

Changed Alarms in JavaApplications Alarm Catalog

Changed Alarms in Login Alarm Catalog

Changed Alarms in LpmTct Alarm Catalog

Changed Alarms in SystemAccess Alarm Catalog

Changed Alarms in TFTP Alarm Catalog

Obsolete Alarms

GUI Changes

A new checkbox displays in the remote syslog field set called "Exclude End Point Alarms" which is displayed only for Cisco Unified Communications Manager services. The checkbox is "unchecked" as the default value.

Table 5-7 lists the alarm configuration options.

Table 5-7 Alarm Configuration Options

Exclude End Point Alarms
Local
Syslog
Alternate Syslog
Remote Syslog
Syslog Severity and StringMatch Alert
Syslog Traps

Checked

No

Yes

No

No

No

Unchecked

No

Yes

Yes

Yes

Yes


New or Updated Services

Cisco Trust Verification Service is a service running on a CallManager server or a dedicated server, that authenticates certificates on behalf of phones and other endpoints. It associates a list of roles for the owner of the certificate. A certificate or the owner can be associated with one or many roles.

The protocol between phones and Trust Verification Service allows phones to request for verification. Trust Verification Service validates the certificate and returns a list of roles associated with it. The protocol allows Trust Verification Service to authenticate a request and conversely, a phone to authenticate the response from Trust Verification Service. The protocol protects the integrity of the request and the response. Confidentiality of the request and the response is not required.

Multiples instances of Cisco Trust Verification Service run on different servers in the cluster to provide scalability. These servers may or may not be the same as the ones hosting the Cisco Unified CallManager. Phones obtain a list of Trust Verification Services in the network and connect to one of them using a selection algorithm (example: Round Robin). If the contacted Trust Verification Service does not respond, the phone switches to the next Trust Verification Service in the list.

SNMP and MIBS

Currently CISCO-CCM-MIB contains the CcmDevFailCauseCode object that provides a Reason Code for device registration status and ccmGatewayFailedReason and ccmGatewayFailed NOTIFICATION-TYPEs. All of these objects get deprecated in this release.

The CcmDevFailCauseCode object gets used in CcmPhoneEntry, CcmPhoneFailedEntry, CcmPhoneStatusUpdateEntry, CcmGatewayEntry, CcmMediaDeviceEntry, CcmCTIDeviceEntry, CcmH323DeviceEntry, CcmVoiceMailDeviceEntry tables. In this release, the CcmDevFailCauseCode gets deprecated and replaced by two new objects called ccmDevUnregCauseCode and ccmDevRegFailCauseCode.

Event/Alarm Logging Format and Output

Currently we follow the old syslog format:

<pri> n: MMM DD hh:mm:ss.mmm TZ : %FACILITY-[SUBFACILITY-]SEVERITY-MNEMONIC: Msg-text

To comply with above PRD item, following syslog format will be used:

<PRI><SEQNUM>: <HOST>: <MONTH> <DAY> <YEAR> <HOUR>:<MINUTES>:<SECONDS>.<MILLISECONDS> 
<TIMEZONE>: %<APPNAME>-<SEVERITY>-<MSGNAME>: [TAGS: ]<MESSAGE>

Example:

Dec 12 11:41:53 my-lab server local7 6 : 14: my-lab server.cisco.com: Dec 12 2008 
19:41:53.289 UTC :  %UC_GENERIC-6-ServiceStarted: %[ServiceName=Cisco 
CallManager][Hostname=server][IPAddress=10.10.10.10][IPV6Address=][ProcessID=5722][Ver
sionInfo=8.0.0.32000-9001][AppID=Cisco 
CallManager][ClusterID=StandAloneCluster][NodeID=server]: Service started.

TLC viewer display will be updated to accommodate new syslog format.

Just like IOS, Product name "UC_<SubFacility>" will be used as APPNAME. New 'SubFacility' tag will be used with application name to compose APPNAME. In above example, 'GENERIC is alarm catalog name while 'ServiceStarted is the alarm name

TLC viewer and Syslog agent will support both new and old format.

Cisco Unified CM will have following exceptions from CiscoLog format:

MsgName may contain lower case letter, in addition to Uppercase and "_" characters

Existing alarm name and parameter may not comply with CiscoLog guidelines

Alarms to Prevent Flooding

To address the flooding issue that affects overall performance of the system, a new configuration option specifies that endpoint phone-related events get logged into a separate file. The alarms that are phone specific and nonphone specific are:

DeviceRegistered

DeviceUnregistered

DeviceTransientConnection

DeviceResetInitiated

DeviceRestartInitiated

EndPointRegistered

EndPointUnregistered

EndPointTransientConnection

EndPointResetInitiated

EndPointRestartInitiated

The following events get generated for phone endpoints only and flood the system, so the new "Exclude End Point Alarms" parameter must be enabled:

DevicePartiallyRegistered

SIPLineRegistrationError

StationConnectionError

StationAlarm

StationEventAlert

StationTCPInitError

DeviceImageDownloadStart

DeviceImageDownloadSuccess

DeviceImageDownloadFailure

DeviceApplyConfigResult

NumDeviceRegExceeded

DeviceDnInformation

To prevent too many alarms flooding the system, you can check the Exclude End Point Alarms checkbox. This ensures that the endpoint phone-related events get logged into a separate file.

Exclude End Point Alarms checkbox is displayed only for the Call Manager services, and is not selected by default. You need to select the Apply to All Nodes also, while selecting this checkbox.

Table 5-8 lists the alarm configuration options.

Table 5-8 Alarm Configuration Options

Exclude End Point Alarms
Local
Syslog
Alternate Syslog
Remote Syslog
Syslog Severity and StringMatch Alert
Syslog Traps

Checked

No

Yes

No

No

No

Unchecked

No

Yes

Yes

Yes

Yes


The Alternate Syslog file gets accessed by using SOAP, TLC, or CLI. Logs get viewed by using Real Time Monitoring Tool Syslog Viewer.

In addition to phone alarms, CTI device alarms get logged into the endpoints file.

Authentication Failure Alerts

Authentication failure alerts and alarms get triggered in Cisco Unified CM. All administrative modifications get logged with the following data:

Product/component

UserID

IP address

Modification Timestamp

Modification Description

Related contextual data

The following features get added to audit logging:

Cisco Unified Real Time Monitoring Tool reports for Cisco Unified CM database updates.

New RESTAPI interface CRUD operations

Remote syslog enhancements CRUD operations

AXL service

New Alarms in Audit Log Catalog

This section explains the new alarms added to the Audit Log catalog.

AdministrativeEvent

Failed to write into the primary file path. Audit Event is generated by this application.

Cisco Unified Serviceability Alarm Catalog

AuditLog

Severity

INFORMATIONAL

Recommended Action

Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

CriticalEvent

Failed to write into the primary file path. Audit Event is generated by this application.

Cisco Unified Serviceability Alarm Catalog

AuditLog

Severity

INFORMATIONAL

Recommended Action

Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

SecurityEvent

Failed to write into the primary file path. Audit Event is generated by this application.

Cisco Unified Serviceability Alarm Catalog

AuditLog

Severity

INFORMATIONAL

Recommended Action

Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

New Alarms in EM Alarm Catalog

The following alarms are new for this release:

EMAppInitializationFailed

EMAppStarted

EMAppStopped

EMCCFailedInLocalCluster

EMCCFailedInRemoteCluster

EMCCUserLoggedIn

EMCCUserLoggedOut

EMServiceConnectionError

NodeNotTrusted

UserInputFailure

EMAppInitializationFailed

EM Application not started. Error occurred while starting application.

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

ERROR

Routing List

Sys Log

Event Log

Data Collector

Parameter(s)

Servlet Name(String)

Recommended Action

Action See application logs for error. Default location for the logs are at /var/log/active/tomcat/logs/em/log4j/

EMAppStarted

EM Application started successfully.

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

INFORMATIONAL

Routing List

Sys Log

Event Log

Parameter(s)

Servlet Name(String)

Recommended Action

No action required.

EMAppStopped

EM Application started.Application is shutting down gracefully because of an unloaded from Tomcat

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

NOTICE

Routing List

Sys Log

Event Log

Parameter(s)

Servlet Name(String)

Recommended Action

No action required.

EMCCFailedInLocalCluster

EMCC login failure occurred due to one of the following conditions:

Devices are incompatible with EMCC.

Unable to retrieve remote cluster information.

EMCC is restricted by the local cluster.

Untrusted certificate received from the remote end while trying to establish a connection

Reason Codes:

31—User is not enabled for EMCC

211/38—EMCC or PSTN is not activated in InterClusterServiceProfile page

23—User does not exist in the end user table 35—No remote cluster entry is present for the home cluster

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

ERROR(3)

Routing List

Sys Log

Event Log

Alert Manager

Parameters

Device Name(String)

Login Date/Time(String)

Login UserID(String)

Reason(String)

Recommended Action

Perform the following steps:


Step 1 Validate if the device model supports EMCC.

Step 2 Ensure that every remote cluster added for EMCC has valid hostname/IP address for EM and PSTN access in the Remote Cluster administration window (From Unified CM Administration window, go to System -> EMCC -> Remote Cluster).

Step 3 Ensure that the entries are enabled.

Step 4 Ensure that a bundle of all Tomcat certificates (PKCS12) has been imported into the local tomcat-trust keystore (From the OS Administration window, go to Security -> Certificate Management and check the certificates in tomcat-trust).


EMCCFailedInRemoteCluster

There was an EMCC login failure at a remote Unified CM. EMCC login could fail due to the following reasons:

User does not exist in any of the configured remote cluster.

User is not enabled for EMCC.

No free EMCC base device.

EMCC access was prevented by remote cluster.

Untrusted certificate received from the remote end while trying to establish a connection.

Reason Codes:

38—EMCC or PSTN is not activated in InterClusterServiceProfile page

31—User is not enabled for EMCC

39—Default and Backup TFTP Service is not configured

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

Warning(4)

Routing List

Sys Log

Event Log

Alert Manager

Parameters

Device Name(String)

Login Date/Time(String)

Login UserID(String)

Reason(String)

Recommended Action

Perform the following steps:


Step 1 Ensure that the user is a valid EMCC user and that user home cluster is added as a EMCC remote cluster (From Unified CM Administration window, go to System > EMCC > Remote Cluster > Add New).

Step 2 Contact remote site administrator to enable user for EMCC (From Unified CM Administration window, go to User Management > End User > Select User > Enable Extension Mobility Cross Cluster checkbox).

Step 3 Contact remote site administrator for adding or freeing EMCC Base Devices (From Unified CM Administration window, go to Bulk Administration > EMCC > Insert/Update EMCC).

Step 4 Contact remote site administrator to validate the remote cluster setting for this cluster.

Step 5 Ensure that a bundle of all Tomcat certificates (PKCS12) got imported into the local tomcat-trust keystore (From the OS Administration window, go to Security > Certificate Management.


EMCCUserLoggedIn

EMCC login was successful.

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

Informational(6)

Routing List

Sys Log

Event Log

Parameters

Device Name(String)

Login Date/Time(String)

Login UserID(String)

Recommended Action

None

EMCCUserLoggedOut

EMCC logout was successful.

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

Informational(6)

Routing List

Sys Log

Event Log

Parameters

Device Name(String)

Login Date/Time(String)

UserID(String)

Recommended Action

None

EMServiceConnectionError

EM Service not reachable. EM Service might be down in one or more nodes in the cluster.

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

ERROR

Routing List

Sys Log

Event Log

Parameter(s)

Servlet Name(String)

Recommended Action

Check if Cisco Extension Mobility service is running on all nodes of the cluster where the service is activated.

NodeNotTrusted

Untrusted Node was contacted. Application could not establish secure connection (SSL handshake failure) with another application. It could be due to certificate for tomcat service where the application is hosted is not trusted (not present in the keystore).

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

ERROR

Routing List

Sys Log

Event Log

Alert Manager

Parameter(s)

Date/Time(String)

Hostname/Ip Address(String)

Recommended Action

1. Ensure that "tomcat-trust" keystore on each CCM node contains the tomcat certificates for every other node within a cluster (Logon to OS Administration Page -> Security -> Certificate Management -> Check the certificates in tomcat-trust). 2. If EMCC is enabled, then ensure that a bundle of all tomcat certificates (PKCS12) has been imported into the local tomcat-trust keystore (Logon to OS Administration Page -> Security -> Certificate Management -> Look for certificates in tomcat-trust).

UserInputFailure

EMCC login failure due to invalid user input due to invalid user credentials or the credentials have expired. Reason Code: 2—Authentication Error.

Cisco Unified Serviceability Alarm Definition Catalog

System/EMAlarmCatalog

Severity

Warning(4)

Routing List

Sys Log

Event Log

Alert Manager

Parameters

Device Name(String)

Login Date/Time(String)

Login UserID(String)

Reason(String)

Recommended Action

Try again with valid credentials or try resetting the credentials.

New Alarms in TVS Alarm Catalog

This section explains the new alarms added to the TVS alarm catalog.

ConfigThreadChangeNotifyServerSingleFailed

Failed to allocate resources to handle configuration change notification from database. This usually indicates a lack of memory when there is a system issue such as running out of resources.

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

ALERT

Routing List

SDI

Event Log

Data Collector

Sys Log

Recommended Action

Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

ConfigThreadReadConfigurationFailed

Failed to retrieve enterprise parameter values from database at TVS service startup. This is usually caused by database access failure.

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

ERROR

Routing List

SDI

Event Log

Data Collector

Sys Log

Recommended Action

In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TVS and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

DefaultDurationInCacheModified

Default value of a Certificate duration in cache is modified in the Service Parameter page. This usually means that the Default Certificate duration in cache value is modified in the Service Parameter page

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

INFORMATIONAL

Routing List

SDI

Event Log

Data Collector

Sys Log

Recommended Action

None.

ITLFileRegenerated

New ITL File has been generated. This usually means that a new certificate related to ITLFile has been modified.

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

INFORMATIONAL

Routing List

SDI

Event Log

Data Collector

Sys Log

Recommended Action

None.

RollBackToPre8.0Disabled

Roll Back to Pre 8.0 has been disabled in the Enterprise Parameter page. This usually means that the RollBack to Pre 8.0 feature is modified in the Enterprise Parameter page.

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

INFORMATIONAL

Routing List

SDI

Event Log

Data Collector

Sys Log

Recommended Action

None.

RollBackToPre8.0Enabled

Roll Back to Pre 8.0 has been enabled in the Enterprise Parameter page.

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

INFORMATIONAL

Routing List

SDI

Event Log

Data Collector

Sys Log

Recommended Action

None.

SDIControlLayerFailed

Failed to update trace logging or alarm subsystem for new settings. This usually indicates a lack of system resources or a failure in database access by the trace logging or alarm subsystem.

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

ALERT

Routing List

SDI

Event Log

Data Collector

Sys Log

Parameter(s)

Error(Int)

Reason(String)

Recommended Action

In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TVS and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm. Ensure that the database server is running, and that the Cisco Database Layer Monitor service is running without problems. If this alarm persists, contact the Cisco Technical Assistance Center (TAC) with TVS service and database trace files.

TVSCertificateRegenerated

TVS Server certificate has been regenerated. This usually means that the TVS certificate has been regenerated. TVS server will automatically be restarted

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

INFORMATIONAL

Routing List

SDI

Event Log

Data Collector

Sys Log

Recommended Action

None.

TVSServerListenBindFailed

Fail to connect to the network port through which file requests are received. This usually happens if the network port is being used by other applications on the system or if the port was not closed properly in the last execution of TVS server.

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

ALERT

Routing List

SDI

Event Log

Data Collector

Sys Log

Parameter(s)

nError(Int)

IPAddress(String)

Port(Int)

Recommended Action

Verify that the port is not in use by other application. After stopping the TVS server, at the command line interface (CLI) on the TVS server, execute the following command: show network status listen. If the port number specified in this alarm is shown in this CLI command output, the port is being used. Restart the Cisco Unified Communications Manager system, which may help to release the port. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TVS service and contact the Cisco Technical Assistance Center (TAC).

TVSServerListenSetSockOptFailed

Failed to increase the size of the network buffer for receiving file requests. This usually indicates a lack of memory when there is a system issue such as running out of resources.

Cisco Unified Serviceability Alarm Catalog

System/TVS

Severity

ALERT

Routing List

SDI

Event Log

Data Collector

Sys Log

Parameter(s)

nError(Int)

IPAddress(String)

Port(Int)

Recommended Action

Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

New Alarms in CallManager Alarm Catalog

This section explains the new alarms added to the CallManager Catalog.

CMVersionMismatch

One or more Unified CM nodes in a cluster are running different Cisco CallManager versions.

This alarm indicates that the local Unified CM is unable to establish communication with the remote Unified CM due to a software version mismatch. This is generally a normal occurrence when you are upgrading a Unified CM node.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ALERT

Recommended Action

The alarm details include the versions of the local and remote Unified CM nodes. Compare the versions and upgrade a node if necessary.

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Remote Application Link Protocol Version(String)

Local Application Link Protocol Version(String)

Remote Node ID(UInt)

Remote Application ID(Enum)

Remote Application Version(String)

Enum Definitions -Remote Application ID

Value
Definition

100

CallManager

200

CTIManager


ConflictingDataIE

A call has been rejected because the incoming PRI/BRI Setup message had an invalid IE.

A call has been rejected because an incoming PRI/BRI Setup message contained an invalid Coding Standard value in the Bearer Capability information element (IE). Unified CM only accepts PRI/BRI Setup messages with Coding Standard values of 0 or 1. When an invalid IE is received, Unified CM rejects the call setup and issues this alarm.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Notify the service provider responsible for sending the Setup message that an IE with Coding Standard values of 0 or 1 must be included in Setup messages.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s

Device Name(String)

DbInfoCorrupt

Database information returned is corrupt. Database configuration error was encountered.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Investigate configuration for the identified device.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Name of Device(String)

DbInfoError

Error in the database information retrieved. Database configuration error was encountered.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Investigate configuration for identified device.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Name of Device(String)

DbInfoTimeout

Database Information request timed out. Timeout was encountered while trying to read database configuration.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Investigate configuration for identified device.

Routing List

SDL

SDI

Event Log

Sys Log

Parameter(s)

Name of Device(String)

DbInsertValidatedDIDFailure

The Insertion of an IME provided E.164 DID has failed. A failure occurred attempting to insert a Cisco Unified Active Link learned DID.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

NOTICE

Recommended Action

Verify the DID and the granting domain. Check other associated alarms. Verify the database integrity.

Routing List

SDL

SDI

Sys Log

Event Log

SNMP Traps

Data Collector

Parameter(s)

e164 DID(String)

Granting Domain(String)

EndPointRegistered

This alarm occurs when a device is successfully registered with Cisco Unified Communications Manager.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

INFORMATIONAL

Recommended Action

No action is required.

Routing List

SDL

SDI

Sys Log

Data Collector

SNMP Traps

Alternate Syslog

Parameter(s)

Device name(String)

Device MAC address(String)

Device IP address(String)

Protocol(String)

Device description(String)

User ID(String)

Load ID(String)

Associated directory numbers(String)

Performance monitor object type(Enum)

Device type(Enum)

Configured Gatekeeper Name(String)

Technology Prefix Name(String)

Zone Information(String)

Alternate Gatekeeper List(String)

Active Gatekeeper(String)

Call Signal Address(String)

RAS Address(String)

IPV6Address(String)

IPAddressAttributes(Enum)

IPV6AddressAttributes(Enum)

ActiveLoadId(String)

InactiveLoadId(String)

Enum Definitions -Performance monitor object type

Value
Definition

2

Cisco Phone


Enum Definitions -Device type

Value
Definition

1

CISCO_30SP+

2

CISCO_12SP+

3

CISCO_12SP

4

CISCO_12S

5

CISCO_30VIP

6

CISCO_7910

7

CISCO_7960

8

CISCO_7940

9

CISCO_7935

12

CISCO_ATA_186

20

SCCP_PHONE

61

H323_PHONE

72

CTI_PORT

115

CISCO_7941

119

CISCO_7971

255

UNKNOWN

302

CISCO_7989

307

CISCO_7911

308

CISCO_7941G_GE

309

CISCO_7961G_GE

335

MOTOROLA_CN622

336

BASIC_3RD_PARTY_SIP_DEVICE

348

CISCO_7931

358

CISCO_UNIFIED_COMMUNICATOR

365

CISCO_7921

369

CISCO_7906

374

ADVANCED_3RD_PARTY_SIP_DEVICE

375

CISCO_TELEPRESENCE

404

CISCO_7962

412

CISCO_3951

431

CISCO_7937

434

CISCO_7942

435

CISCO_7945

436

CISCO_7965

437

CISCO_7975

446

CISCO_3911

468

CISCO_UNIFIED_MOBILE_COMMUNICATOR

478

CISCO_TELEPRESENCE_1000

479

CISCO_TELEPRESENCE_3000

480

CISCO_TELEPRESENCE_3200

481

CISCO_TELEPRESENCE_500

484

CISCO_7925

493

CISCO_9971

495

CISCO_6921

496

CISCO_6941

497

CISCO_6961

20000

CISCO_7905

30002

CISCO_7920

30006

CISCO_7970

30007

CISCO_7912

30008

CISCO_7902

30016

CISCO_IP_COMMUNICATOR

30018

CISCO_7961

30019

CISCO_7936

30035

IP_STE


Enum Definitions -IPAddressAttributes

Value
Definition

0

Unknown - The device has not indicated what this IPv4 address is used for

1

Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only

2

Signal only - The device has indicated that this IPv4 address is used for control signaling only

3

Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling


Enum Definitions -IPV6AddressAttributes

Value
Definition

0

Unknown - The device has not indicated what this IPv6 address is used for

1

Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only

2

Signal only - The device has indicated that this IPv6 address is used for control signaling only

3

Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling


EndPointResetInitiated

This alarm occurs when a device is reset via the Reset button in Cisco Unified CM Administration. Reset causes the device to shut down and come back in service. A device can be reset only when it is registered with Cisco Unified Communications Manager.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

INFORMATIONAL

Recommended Action

Informational purposes only; no action is required.

Routing List

SDL

SDI

Sys Log

Alternate Syslog

Parameter(s)

Device name(String)

Product type(String)

Device type(Enum)

Enum Definitions -Device type

Value
Definition

1

CISCO_30SP+

2

CISCO_12SP+

3

CISCO_12SP

4

CISCO_12S

5

CISCO_30VIP

6

CISCO_7910

7

CISCO_7960

8

CISCO_7940

9

CISCO_7935

12

CISCO_ATA_186

20

SCCP_PHONE

61

H323_PHONE

72

CTI_PORT

115

CISCO_7941

119

CISCO_7971

255

UNKNOWN

302

CISCO_7989

307

CISCO_7911

308

CISCO_7941G_GE

309

CISCO_7961G_GE

335

MOTOROLA_CN622

336

BASIC_3RD_PARTY_SIP_DEVICE

348

CISCO_7931

358

CISCO_UNIFIED_COMMUNICATOR

365

CISCO_7921

369

CISCO_7906

374

ADVANCED_3RD_PARTY_SIP_DEVICE

375

CISCO_TELEPRESENCE

404

CISCO_7962

412

CISCO_3951

431

CISCO_7937

434

CISCO_7942

435

CISCO_7945

436

CISCO_7965

437

CISCO_7975

446

CISCO_3911

468

CISCO_UNIFIED_MOBILE_COMMUNICATOR

478

CISCO_TELEPRESENCE_1000

479

CISCO_TELEPRESENCE_3000

480

CISCO_TELEPRESENCE_3200

481

CISCO_TELEPRESENCE_500

484

CISCO_7925

493

CISCO_9971

495

CISCO_6921

496

CISCO_6941

497

CISCO_6961

20000

CISCO_7905

30002

CISCO_7920

30006

CISCO_7970

30007

CISCO_7912

30008

CISCO_7902

30016

CISCO_IP_COMMUNICATOR

30018

CISCO_7961

30019

CISCO_7936

30035 I

P_STE


EndPointRestartInitiated

Device restart initiated or Apply Config initiated on the specified device.

This alarm occurs when a device is restarted via the Restart button in Cisco Unified CM Administration window or when a system administrator presses the Apply Config button for a device that does not support conditional restart. Restart causes the device to unregister, receive an updated configuration file, and re-register with Cisco Unified Communications Manager (Unified CM) without shutting down. A device can be restarted only when it is registered with Unified CM.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

INFORMATIONAL

Recommended Action

Informational purposes only; no action is required.

Routing List

SDL

SDI

Sys Log

Alternate Syslog

Parameter(s)

Device name(String)

Product type(String)

Device type(Enum)

Enum Definitions -Device type

Value
Definition

1

CISCO_30SP+

2

CISCO_12SP+

3

CISCO_12SP

4

CISCO_12S

5

CISCO_30VIP

6

CISCO_7910

7

CISCO_7960

8

CISCO_7940

9

CISCO_7935

12

CISCO_ATA_186

20

SCCP_PHONE

61

H323_PHONE

72

CTI_PORT

115

CISCO_7941

119

CISCO_7971

255

UNKNOWN

302

CISCO_7989

307

CISCO_7911

308

CISCO_7941G_GE

309

CISCO_7961G_GE

335

MOTOROLA_CN622

336

BASIC_3RD_PARTY_SIP_DEVICE

348

CISCO_7931

358

CISCO_UNIFIED_COMMUNICATOR

365

CISCO_7921

369

CISCO_7906

374

ADVANCED_3RD_PARTY_SIP_DEVICE

375

CISCO_TELEPRESENCE

404

CISCO_7962

412

CISCO_3951

431

CISCO_7937

434

CISCO_7942

435

CISCO_7945

436

CISCO_7965

437

CISCO_7975

446

CISCO_3911

468

CISCO_UNIFIED_MOBILE_COMMUNICATOR

478

CISCO_TELEPRESENCE_1000

479

CISCO_TELEPRESENCE_3000

480

CISCO_TELEPRESENCE_3200

481

CISCO_TELEPRESENCE_500

484

CISCO_7925

493

CISCO_9971

495

CISCO_6921

496

CISCO_6941

497

CISCO_6961

20000

CISCO_7905

30002

CISCO_7920

30006

CISCO_7970

30007

CISCO_7912

30008

CISCO_7902

30016

CISCO_IP_COMMUNICATOR

30018

CISCO_7961

30019

CISCO_7936

30035

IP_STE


EndPointTransientConnection

End point transient connection attempt.

A connection was established and immediately dropped before completing registration. Incomplete registration may indicate that a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. Network connectivity problems can affect device registration, or the restoration of a primary Unified CM may interrupt registration.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Investigate any network connectivity problems in the system. It's possible that you have reached the maximum number of devices; the Cisco Unified Communications Manager service parameter, Maximum Number of Registered Devices, controls the number of devices allowed in the system. Taking licensing, system hardware and other related concerns into consideration, you could increase the value of the service parameter. Also, refer to the reason code definitions for recommended actions. No action is required if this event was issued as a result of a normal device rehome.

Routing List

SDL

SDI

Sys Log

Data Collector

SNMP Traps

Alternate Syslog

Parameter(s)

Device IP address(String)

Device name(String)

Device MAC address(String)

Protocol(String)

Device type(Enum)

Reason Code(Enum)

Connecting Port(UInt)

Registering SIP User(String)

IPv6Address(String)

IPAddressAttributes(Enum)

IPv6AddressAttributes(Enum)

Enum Definitions -Device type

Value
Definition

1

CISCO_30SP+

2

CISCO_12SP+

3

CISCO_12SP

4

CISCO_12S

5

CISCO_30VIP

6

CISCO_7910

7

CISCO_7960

8

CISCO_7940

9

CISCO_7935

12

CISCO_ATA_186

20

SCCP_PHONE

61

H323_PHONE

72

CTI_PORT

115

CISCO_7941

119

CISCO_7971

255

UNKNOWN

302

CISCO_7989

307

CISCO_7911

308

CISCO_7941G_GE

309

CISCO_7961G_GE

335

MOTOROLA_CN622

336

BASIC_3RD_PARTY_SIP_DEVICE

348

CISCO_7931

358

CISCO_UNIFIED_COMMUNICATOR

365

CISCO_7921

369

CISCO_7906

374

ADVANCED_3RD_PARTY_SIP_DEVICE

375

CISCO_TELEPRESENCE

404

CISCO_7962

412

CISCO_3951

431

CISCO_7937

434

CISCO_7942

435

CISCO_7945

436

CISCO_7965

437

CISCO_7975

446

CISCO_3911

468

CISCO_UNIFIED_MOBILE_COMMUNICATOR

478

CISCO_TELEPRESENCE_1000

479

CISCO_TELEPRESENCE_3000

480

CISCO_TELEPRESENCE_3200

481

CISCO_TELEPRESENCE_500

484

CISCO_7925

493

CISCO_9971

495

CISCO_6921

496

CISCO_6941

497

CISCO_6961

20000

CISCO_7905

30002

CISCO_7920

30006

CISCO_7970

30007

CISCO_7912

30008

CISCO_7902

30016

CISCO_IP_COMMUNICATOR

30018

CISCO_7961

30019

CISCO_7936

30035

IP_STE


Enum Definitions -Reason Code

Value
Definition

1

Unknown - (SCCP only) The device failed to register for an unknown reason. If this persists, collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact TAC.

2

NoEntryInDatabase - (MGCP only) The device is not configured in the Cisco Unified CM database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device via Cisco Unified CM Administration.

3

DatabaseConfigurationError - The device is not configured in the Cisco Unified CM database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device via Cisco Unified CM Administration.

4

DeviceNameUnresolveable - For SIP third-party devices this means that Cisco Unified CM could not determine the name of the device from the Authorization header in the REGISTER message. The device did not provide an Authorization header after Cisco Unified CM challenged with a 401 Unauthorized message. Verify the device is configured with digest credentials and is able to respond to 401 challenges with an Authorization header. If this is a Cisco IP phone, the configuration may be out-of-sync. First go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify "all servers have a good replication status". If DB replications looks good, reset the phone. If that still doesn't fix the problem, restart the TFTP and the Cisco CallManager services. For all other devices, this reason code means that DNS lookup failed. Verify the DNS server configured via the OS Administration CLI is correct and that the DNS name used by the device is configured in the DNS server.

6

ConnectivityError - The network connection between the device and Cisco Unified CM dropped before the device was fully registered. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops and packet corruption. It is also possible to get this error if the Cisco Unified CM node is experiencing high CPU usage. Verify the device is powered up and operating, verify network connectivity between the device and Cisco Unified CM, and verify the CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging Alert).

7

InitializationError - An internal error occurred within Cisco Unified CM while processing the device registration. It is recommended to restart the Cisco CallManager service. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact TAC.

10

AuthenticationError - The device failed either TLS or SIP digest security authentication. If the device is a SIP phone and is enabled for digest authentication (on the System > Security Profile > Phone Security Profile, check if "Enable Digest Authentication" checkbox is checked), verify the "Digest Credentials" in the End User config page are configured. Also, check the phone config page to see if the phone is associated with the specified end user in the Digest User drop box. If the device is a third-party SIP device, verify the digest credentials configured on the phone match the "Digest Credentials" configured in the End User page.

11

InvalidX509NameInCertificate - Configured "X.509 Subject Name" doesn't match what's in the certificate from the device. Check the Security profile of the indicated device and verify the "Device Security Mode" is either "Authenticated" or "Encrypted". Verify the "X.509 Subject Name" field has the right content. It should match the Subject Name in the certificate from the peer.

12

InvalidTLSCipher - Unsupported cipher algorithm used by the device; Cisco Unified CM only supports AES_128_SHA cipher algorithm. Recommended action is for the device to regenerate its certificate with the AES_128_SHA cipher algorithm.

14

MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, and an expires value too small. Verify the REGISTER message does not suffer from any of these ills.

15

ProtocolMismatch - The protocol of the device (SIP or SCCP) does not match the configured protocol in Cisco Unified CM. Recommended actions: 1) Verify the device is configured with the desired protocol; 2) Verify the firmware load ID on the Device Defaults page is correct and actually exists on the TFTP server; 3) If there is a firmware load ID configured on the device page, verify it is correct and exists on the TFTP server (On Cisco Unified OS Administration page, Software Upgrades > TFTP File Management, look for the file name as specified by load ID); 4) Restart the TFTP and Cisco CallManager services. Use the Cisco Unified OS Administration TFTP File Management page to verify the configured firmware loads exist.

16

DeviceNotActive - The device has not been activated

17

AuthenticatedDeviceAlreadyExists - A device with the same name is already registered. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact TAC. There may be an attempt by unauthorized devices to register.

18

ObsoleteProtocolVersion - (SCCP only) A SCCP device registered with an obsolete protocol version. Power cycle the phone. Verify that the TFTP service is activated. Verify that the TFTP server is reachable from the device. If there is a firmware load ID configured on the Phone Config page, verify that the firmware load ID exists on the TFTP server (On Cisco Unified OS Administration page, Software Upgrades > TFTP File Management, look for the file name as specified by load ID).


Enum Definitions -IPAddressAttributes

Value
Definition

0

Unknown - The device has not indicated what this IPv4 address is used for

1

Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only

2

Signal only - The device has indicated that this IPv4 address is used for control signaling only

3

Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling


Enum Definitions -IPv6AddressAttributes

Value
Definition

0

Unknown - The device has not indicated what this IPv6 address is used for

1

Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only

2

Signal only - The device has indicated that this IPv6 address is used for control signaling only

3

Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling


EndPointUnregistered

An endpoint that has previously registered with Cisco Unified Communications Manager has unregistered. In cases of normal unregistration with reason code 'CallManagerReset', 'CallManagerRestart', 'DeviceInitiatedReset', 'EMLoginLogout', or 'EMCCLoginLogout', the severity of this alarm is lowered to INFORMATIONAL. An endpoint can unregister for many reasons, both intentional, such as manually resetting the device after a configuration change, or unintentional, such as loss of network connectivity. Other causes for this alarm could include a phone being registered to a secondary node and then the primary node come back online, causing the phone to rehome to the primary Unified CM node or lack of a KeepAlive being returned from the Unified CM node to which this endpoint was registered. Unregistration also occurs if Unified CM receives a duplicate registration request for this same device.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Actions to take vary depending on the reason specified for the endpoint unregistration. If the reason is ConfigurationMismatch, go to the Device Configuration page in Cisco Unified CM Administration, make a change to the Description field for this device, click Save, then reset the device. In the case of a network connectivity or loss of KeepAlives problem, use network diagnostic tools and the Cisco Unified CM Reporting tool to fix any reported network or Unified CM system errors. In the case of an endpoint rehoming to the primary Unified CM node, watch for a successful registration of the device on the primary node. In the case of a duplicate registration request, it may be a non-malicious occurrence due to timing of an endpoint registering and unregistering; if duplicate registration requests continue or if the same endpoint has different IP addresses, confirm the IP address on the physical device itself by checking the settings on the device (settings button). If unregistration of this device was expected, no action is required. Also, refer to the reason code descriptions for recommended actions.

Routing List

SDL

SDI

Sys Log

Data Collector

SNMP Traps

Alternate Syslog

Parameter(s)

Device name(String)

Device MAC address(String)

Device IP address(String)

Protocol(String)

Device type(Enum)

Device description(String)

Reason Code(Enum)

IPV6Address(String)

IPAddressAttributes(Enum)

IPV6AddressAttributes(Enum)

Enum Definitions -Device type

Value
Definition

1

CISCO_30SP+

2

CISCO_12SP+

3

CISCO_12SP

4

CISCO_12S

5

CISCO_30VIP

6

CISCO_7910

7

CISCO_7960

8

CISCO_7940

9

CISCO_7935

12

CISCO_ATA_186

20

SCCP_PHONE

61

H323_PHONE

72

CTI_PORT

115

CISCO_7941

119

CISCO_7971

255

UNKNOWN

302

CISCO_7989

307

CISCO_7911

308

CISCO_7941G_GE

309

CISCO_7961G_GE

335

MOTOROLA_CN622

336

BASIC_3RD_PARTY_SIP_DEVICE

348

CISCO_7931

358

CISCO_UNIFIED_COMMUNICATOR

365

CISCO_7921

369

CISCO_7906

374

ADVANCED_3RD_PARTY_SIP_DEVICE

375

CISCO_TELEPRESENCE

404

CISCO_7962

412

CISCO_3951

431

CISCO_7937

434

CISCO_7942

435

CISCO_7945

436

CISCO_7965

437

CISCO_7975

446

CISCO_3911

468

CISCO_UNIFIED_MOBILE_COMMUNICATOR

478

CISCO_TELEPRESENCE_1000

479

CISCO_TELEPRESENCE_3000

480

CISCO_TELEPRESENCE_3200

481

CISCO_TELEPRESENCE_500

484

CISCO_7925

493

CISCO_9971

495

CISCO_6921

496

CISCO_6941

497

CISCO_6961

20000

CISCO_7905

30002

CISCO_7920

30006

CISCO_7970

30007

CISCO_7912

30008

CISCO_7902

30016

CISCO_IP_COMMUNICATOR

30018

CISCO_7961

30019

CISCO_7936

30035

IP_STE


Enum Definitions -Reason Code

Value
Definition

1

Unknown - The device has unregistered for an unknown reason. If the device does not re-register within 5 minutes, verify it is powered-up and verify network connectivity between the device and Cisco Unified CM.

6

ConnectivityError - Network communication between the device and Cisco Unified CM has been interrupted. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops and packet corruption. It is also possible to get this error if the Cisco Unified CM node is experiencing high CPU usage. Verify the device is powered up and operating, verify network connectivity between the device and Cisco Unified CM, and verify the CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging Alert).

8

DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action required; the device will re-register automatically.

9

CallManagerReset - A device reset was initiated from Cisco Unified CM Administration, either due to an explicit command from an administrator, or due to internal errors encountered. No action necessary, the device will re-register automatically.

10

DeviceUnregistered - The device has explicitly unregistered. Possible causes include a change in the IP address or port of the device. No action is necessary, the device will re-register automatically.

11

MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, and an expires value too small. Verify the REGISTER message does not suffer from any of these ills.

12

SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. No action necessary, the device will re-register automatically.

13

KeepAliveTimeout - A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify the device is powered up and operating, verify network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging Alert). No action necessary, the device will re-register automatically.

14

ConfigurationMismatch (SIP only) The configuration on the device does not match the configuration in Unified CM. This can be caused by database replication errors or other internal Unified CM communication errors. First go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify "all servers have a good replication status". If this device continues to unregister with this reason code, go to the CCMAdmin Device web page for the device and click Save. This allows a change notify to be generated to the Unified CM and TFTP services and rebuild a new config file. If the problem still persists, restart the TFTP service and Unified CM service.

15

CallManagerRestart - A device restart was initiated from Cisco Unified CM, either due to an explicit command from an administrator, or due to a configuration change such as adding, deleting or changing a DN associated with the device. No action necessary, the device will re-register automatically.

16

DuplicateRegistration - Cisco Unified CM detected that the device attempted to register to 2 nodes at the same time. Cisco Unified CM initiated a restart to the phone to force it to re-home to a single node. No action necessary, the device will re-register automatically.

17

CallManagerApplyConfig - An ApplyConfig command was invoked from Unified CM Administration resulting in an unregistration. No action necessary, the device will re-register automatically.

18

DeviceNoResponse - The device did not respond to a reset or restart notification, so it is being forcefully reset. If the device does not re-register within 5 minutes, confirm it is powered-up and confirm network connectivity between the device and Cisco Unified CM.

19

EMLoginLogout

20

EMCCLoginLogout


Enum Definitions -IPAddressAttributes

Value
Definition

0

Unknown - The device has not indicated what this IPv4 address is used for

1

Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only

2

Signal only - The device has indicated that this IPv4 address is used for control signaling only

3

Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling


Enum Definitions -IPV6AddressAttributes

Value
Definition

0

Unknown - The device has not indicated what this IPv6 address is used for

1

Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only

2

Signal only - The device has indicated that this IPv6 address is used for control signaling only

3

Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling


FirewallMappingFailure

Firewall unreachable.

This alarm indicates that Unified CM was unable to contact the firewall in order to make a IME call. As a consequence, outbound calls are being sent over the PSTN, and inbound calls may be routed over the PSTN by your partner enterprises.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Check to see that your firewall is up. Make sure the mapping service is enabled. Check that the IP address and port on the firewall for that mapping service match the configuration in Unified CM Administration. Check general IP connectivity between Unified CM and the firewall.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

IP address(String)

Port number(UInt)

IMEDistributedCacheInactive

Inactive IME distributed cache.

This alarm is generated when Unified CM attempts to connect to the IME server, however, the IME distributed cache is not currently active.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Check to make sure that the IME certificate is provisioned on the IME server. Check to make sure that the IME distributed cache has been activated via the CLI on the IME server.

Routing List

SDL

SDI

Sys Log

Event Log

Alert Manager

IMEOverQuota

IME over quota.

Each IME server has a fixed quota on the total number of DIDs it can write into the IME distributed cache. When this alarm is generated, it means that, across all of the Unified CM clusters which are utilizing the same IME server, the quota for the IME distributed cache has been exceeded.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ALERT

Recommended Action

The alarm will include the name of the IME server, and the current and target quota values. The first thing to check is to make sure that you have correctly provisioned the right set of DID prefixes on all of the Unified CM clusters sharing that same IME server. If that is correct, it means you have exceeded the capacity of your IME server, and you require another. Once you have another, you can now split your DID prefixes across two different IME client instances, each on a different IME server. That will alleviate the quota problem.

Routing List

SDL

SDI

Sys Log

Event Log

Alert Manager

Parameter(s)

Server name(String)

Current quota(UInt)

Maximum target quota(UInt)

IMEQualityAlertEntry

IME call quality problem.

This alarm is generated when Unified CM is seeing a substantial number of IME calls fail back to PSTN, or fail to be set up, due to IP network quality problems. There are two triggers for this alarm. One is when a large fraction of the currently active IME calls have all requested fallback, or have fallen back, to the PSTN. The other is when a large fraction of the recent call attempts have not been made over IP, and instead have gone to the PSTN.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Check your IP connectivity, and make sure it is good. If it looks good in general, you may need to look at CDRs, CMRs, and logs from the firewalls to determine what happened.

Routing List

SDL

SDI

Sys Log

Event Log

Alert Manager

Parameter(s)

Active IME call count(UInt)

Fallback call count(UInt)

Setup attempts count(UInt)

Failed attempts(UInt)

IMEQualityAlertExit

IME call quality problem cleared.

This alarm is generated when the Unified CM sees a significant reduction in the number of failed IME calls following generation of the IMEQualityAlertEntry alarm. This notice alarm indicates that the IP connectivity issues causing the initial generation of the IMEQualityAlertEntry alarm have abated.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

NOTICE

Recommended Action

Continue to monitor IP connectivity for recurring issues.

Routing List

SDL

SDI

Sys Log

Event Log

Alert Manager

Parameter(s)

Active IME call count(UInt)

Fallback call count(UInt)

Setup attempts count(UInt)

Failed attempts(UInt)

InsufficientFallbackIdentifiers

Cannot allocate fallback identifier.

This alarm is generated when Unified CM is processing a IME call, and is attempting to allocate a PSTN fallback DID and a DTMF digit sequence to associate with this call. However, there are too many IME calls currently in progress which are utilizing this same fallback DID, and as a result, there are no more DTMF digit sequences which could be allocated to this call. As such, this call will proceed, however mid-call fallback will not be possible for this call.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Recommended Action

Your first course of action should be to identify the fallback profile associated with this call. Its name will be present in the alarm. Check that profile in Cisco Unified CM Administration and examine the current setting for "Fallback Number of Correlation DTMF Digits". Increase that value by one, and check if that eliminates these alarms. In general, this parameter should be large enough such that the number of simultaneous IME calls made to enrolled numbers associated with that profile is always substantially less than 10 raised to the power of this number. "Substantially" should be at least a factor of ten. For example, if you always have less than 10,000 simultaneous IME calls for the patterns associated with this fallback profile, setting this value to 5 (10 to the power of 5 is 100,000) will give you plenty of headroom and you will not see this alarm.

However, increasing this value also results in a small increase in the amount of time it takes to perform the fallback. As such, it should not be set arbitrarily large; it should be set just large enough to keep clear of this alarm. Another alternative to increasing this parameter is to add another fallback profile with a different fallback DID, and associate that fallback profile with a smaller number of enrolled DID patterns. This will allow you to get by with a smaller number of digits.

Routing List

SDL

SDI

Sys Log

Event Log

Alert Manager

Parameter(s)

Fallback profile name(String)

Fallback E.164 number(String)

InvalidCredentials

Credential Failure to IME server.

The connection to the IME server could not be completed, because the username and/or password configured on Unified CM do not match those configured on the IME server.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ALERT

Recommended Action

The alarm will include the username and password which were used to connect to the IME server, along with the IP address of the target IME server and its name. Log into the IME server and check that the username and password configured there match those configured in Unified CM.

Routing List

SDL

SDI

Sys Log

Event Log

Alert Manager

Parameter(s)

User name(String)

IP address(String)

Server name(String)

InvalidSubscription

A message has been received from an IME server that contains a subscription identifier that is not handled by this node

Each node that communicates with a IME server saves a subscription identifier associated with each IME client instance. A IME server has sent a message with a subscription identifier that does not match any of the previously sent subscription identifiers.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

WARNING

Recommended Action

This may be a race condition if the IME client instance has been recently added or deleted. If this error continues, there may be a synchronization issue between this node and the IME server sending this message.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Subscription Identifier(UInt)

IME Server(String)

PublicationRunCompleted

Completion of publication of published DID patterns.

This alarm is generated when Unified CM completes a publication of the DID patterns into the IME network.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

INFORMATIONAL

Recommended Action

This alarm is provided for historic and informational purposes. It can be used to give you feedback that the system is working and is correctly publishing numbers into the IME network. It can also be used for troubleshooting. If some of the publishes fail for some reason, the alarm will contain a list of those numbers which were not published. If your users are receiving calls, and they are not over IP but you think they ought to be, you can check the history of these alarms to see if the number failed to be published into the network.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Start time(String)

End time(String)

DID count(UInt)

Failed DID count(UInt)

Failed DIDs(String)

PublishFailed

Publish Failed.

Unified CM attempted to store a number into the IME distributed cache, but the attempt failed. This is typically due to a transient problem in the IME distributed cache. The problem will self-repair under normal conditions. However, you should be aware that, as a consequence of this failure, the E.164 DID listed as part of the alarm will not be present in the IME distributed cache for a brief interval. Consequently, this may delay the amount of time until which you will receive VoIP calls made to that number - they may continue over the PSTN for some callers. It is useful to be aware of this, in case you are trying to understand why a call is not being made over VoIP.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

WARNING

Recommended Action

If you notice single small numbers of these alarms in isolation, no action is required on your part. However, a large number of them indicates a problem in the IME distributed cache, most likely due to problems with Internet connectivity. Check your Internet connectivity.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

DID(String)

PublishFailedOverQuota

Each IME server has a fixed quota on the total number of DIDs it can write into the IME distributed cache. When this alarm is generated, it means that, even though you should be under quota, due to an extremely unlikely statistical anomaly, the IME distributed cache rejected your publication, believing you were over quota. You should only see this alarm if you are near, but below, your quota. This error is likely to be persistent, so that the corresponding E.164 number from the alarm will not be published into the IME distributed cache. This means that you will not receive VoIP calls towards that number - they will remain over the PSTN.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR_ALARM

Recommended Action

The alarm will include the name of the IME server, and the current and target quota values. The first thing to check is to make sure that you have correctly provisioned the right set of DID prefixes on all of the Unified CM clusters sharing that same IME server on the same IME distributed cache. If that is correct, it means you have exceeded the capacity of your IME server, and you require another. Once you have another, you can now split your DID prefixes across two different IME client instances, each on a different IME server. That will alleviate the quota problem.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

The DID for which the Publish was attempted(String)

Server name(String)

Current quota(UInt)

Maximum target quota(UInt)

RouteRemoved

Route removed automatically.

This alarm is generated when Unified CM removes a route from Unified CM Administration because the route is stale and has expired, or because the far end has indicated the number is no longer reachable at that domain.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

INFORMATIONAL

Recommended Action

This alarm is provided for historic and informational purposes. It helps you understand why certain numbers are in your routing tables, and why others are not. This historical information is useful to help determine why a call to a particular number is not going over IP, when you expect it to.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

E.164 number(String)

Domain name(String)

Route learned time(String)

Reason Code(Enum)

Enum Definitions -Reason Code

Value
Definition

1

Expired

2

Unreachable


RejectedRoutes

Rejected route due to Untrusted status.

This alarm is generated when Unified CM learned a route from the IME server. However, due to the configured Trusted or Untrusted list, the route was rejected.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

WARNING_ALARM

Recommended Action

This condition is not an error. However, it indicates to you that one of your users called a number which was reachable over IME, however, due to your configured Trusted or Untrusted list, a IME call will not be made. You might wish to consider adding the domain or prefix to your Trusted list or removing it from the Untrusted list.

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Domain name(String)

Phone number(String)

TCPSetupToIMEFailed

Connection Failure to IME server.

This alarm occurs when Unified CM is unable to establish a TCP connection to an IME server. It typically occurs when the IP address and port of the IME server are misconfigured or an Intranet connectivity problem is preventing the connection from being set up.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

CRITICAL_ALARM

Recommended Action

Check to make sure that the IP address and port of the IME server - which are present in the alarm - are valid. If so, this may be due to a network connectivity problem. Test the connectivity between the Unified CM servers and the IME server.

Routing List

SDL

SDI

Sys Log

Event Log

Alert Manager

Parameter(s)

IP address(String)

Port number(UInt)

TLSConnectionToIMEFailed

TLS Failure to IME service.

A TLS connection to the IME server could not be established because of a problem with the certificate presented by the IME server. (For example, not in the Unified CM CTL, or is in the CTL but has expired).

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ALERT

Recommended Action

Check to see that the certificate of the IME server is configured properly in the Unified CM.

Routing List

SDL

SDI

Sys Log

Event Log

Alert Manager

Parameter(s)

SSLErrorCode(UInt)

SSLErrorText(String)

New SAF and CCD Alarms

The following new SAF and CCD alarms are added:

CCDIPReachableTimeOut

CCDPSTNFailOverDurationTimeOut

CCDLearnedPatternLimitReached

DuplicateLearnedPattern

LostConnectionToSAFForwarder

SAFForwarderError

SAFUnknownService

SAFPublishRevoke

SAFResponderError

CCDIPReachableTimeOut

CCD Requesting Service IP Reachable Duration times out.

The CCD requesting service detected that it can no longer reach the learned patterns through IP. All learned patterns from this forward will be marked as unreachable (via IP) and to allow calls to learned patterns to continue to be routed until IP becomes reachable again, all calls to learned patterns will be routed through the PSTN. Calls can be routed through the PSTN for a certain period of time before PSTN failover times out.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Routing List

SDL

SDI

Sys Log

Event Log

Recommended Action

Check IP connectivity and resolve any TCP or IP problems in the network.

CCDPSTNFailOverDurationTimeOut

The internal limit on PSTN failover has expired.

When learned patterns are not reachable through IP, Unified CM routes calls through the PSTN instead. Calls can be routed through PSTN for an internally-controlled duration. When this alarm occurs, the PSTN failover duration has expired and calls to learned patterns cannot be routed. All learned patterns will be purged from Unified CM.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Routing List

SDL

SDI

Sys Log

Event Log

Recommended Action

Troubleshoot your network to get IP connectivity restored. After IP connectivity is restored, Unified CM will automatically relearn Hosted DN patterns and calls to learned patterns will proceed through IP.

CCDLearnedPatternLimitReached

CCD has reached the maximum number of learned patterns allowed.

The CCD requesting service has limited the number of learned patterns to a number defined in the service parameter, CCD Maximum Numbers of Learned Patterns. This alarm indicates that the CCD requesting service has met the maximum number of learned patterns allowed.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

CCD Maximum Numbers of Learned Patterns (UInt)

System Limit of CCD Learned Patterns (UInt)

Recommended Action

This alarm displays the value that is configured in the Cisco CallManager service parameter, CCD Maximum Numbers of Learned Patterns, as well as the maximum number of learned patterns that are allowed by the system (an internally-controlled maximum).

Consider whether the specified maximum number of learned patterns is correct for your deployment. If it is too low, compare it with the number shown in the SystemLimitCCDLearnedPatterns in this alarm. If the Max number is below the System Limit, you can go to the Service Parameters Configuration window and increase the CCD Maximum Numbers of Learned Patterns service parameter. If the Max and System Limit numbers match, the system is already configured to run at capacity of learned patterns; no action is required.

DuplicateLearnedPattern

This alarm occurs when CCD requesting service received a duplicate Hosted DN.

The Call Control Discovery (CCD) requesting service received the same hosted DN from multiple call control entities such as Unified CM Express or another Unified CM cluster. The Cisco CallManager service parameter, Issue Alarm for Duplicate Learned Patterns, controls whether this alarm gets issued.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Client Handle(String)

Service ID(UInt)

Sub Service ID(UInt)

InstanceID1(UInt)

InstancID2(UInt)

InstanceID3(UInt)

InstanceID4(UInt)

Recommended Action

In RTMT, check the Pattern Report (CallManager > Report > Learned Pattern) and look for the duplicate pattern identified in this alarm. Learned patterns must be unique. Determine which call control entity (such as Unified CM or Unified CM Express) needs to be changed so that there is no duplicate pattern. Refer to the call control entity's configuration guide (help text) to learn how to update a hosted DN pattern. In Unified CM, to change the Hosted DN Pattern go to Cisco Unified CM Administration to update the Hosted DN Pattern configuration (Call Routing > Call Control Discovery > Hosted DN Patterns).

LostConnectionToSAFForwarder

Connection to the SAF Forwarder has been lost.

A TCP connection failure caused the connection between the SAF Forwarder and Unified CM to be lost. When the TCP connection is restored, Unified CM attempts to connect to the SAF Forwarder automatically. If IP connectivity is unreachable for longer than the duration of the Cisco CallManager service parameter CCD Learned Pattern IP Reachable Duration, calls to learned patterns will be routed through the PSTN instead. Calls through the PSTN to learned patterns will be maintained for a certain period of time before the PSTN failover times out.

Cisco Unified Serviceability Alarm Catalog

CallManager/CallManager

Severity

Error

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameters

IP Address(String)

SafClientHandle(UInt)

Recommended Action

Investigate possible causes of a TCP connection failure, such as power failure, loose cables, incorrect switch configuration, and so on, and correct any issues that you find. After the connection is restored, CCD will try to register/sync with the SAF Forwarder automatically.

SAFForwarderError

SAF Forwarder error response sent to Unified CM.

Cisco Unified Serviceability Alarm Catalog

CallManager/CallManager

Severity

Error

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameters

IP Address(String)

SafClientHandle(UInt)

Application User Name(String)

Reason Code and Description(Enum)

SAF Protocol Version Number(String)

Service ID(UInt)

Sub Service ID(UInt)

Recommended Action

Refer to the reason code and description (help text) for specific information and actions (where applicable) for this alarm.

Enum Definitions - Reason Code

Value
Definition

400

SAF_BAD_REQUEST - SAF Forwarder was unable to accept the request due to incorrect syntax (malformed), missing required attributes, and other similar reasons. Investigate the configuration between the SAF Forwarder and Unified CM to be certain that all settings are correct for your deployment. In particular, check the Client Label configured on the router to make certain that it matches the Client Label configured in Cisco Unified CM Administration on the SAF Forwarder Configuration window (SAF > SAF Forwarder).

431

SAF_INTEGRITY_CHECK_FAILURE - A message failed to pass SAF Forwarder security validation. This can occur because of misconfiguration, a potential attack, or more commonly by incorrect provisioning of the password on the Forwarder and SAF client. Reprovision the password and keep a watch on further SAF INTEGRITY CHECK FAILURE alarms. If you receive a persistent number of SAF INTEGRITY CHECK FAILURE alarms, close the interface between SAF Forwarder and Unified CM and investigate the source of the IP packets.

435

**INFO LEVEL** SAF_MISSING_NONCE - A nonce (a random parameter generated when the message is sent) is missing from the message. The system will resend with a new nonce automatically. No action is required.

436

SAF_UNKNOWN_USERNAME - Unified CM sent the SAF Forwarder an Application User name that is not configured on the router or that does not match the router's configuration. Check the Application User Name on the router and in the Application User Configuration window in Cisco Unified CM Administration to be sure they match.

438

**INFO LEVEL** SAF_STALE_NONCE - A nonce (a random parameter generated when the message is sent) has aged out (gone stale). The system will resend with a new nonce automatically. No action is required.

471

**INFO LEVEL** SAF_BAD_CLIENT_HANDLE - SAF_BAD_CLIENT_HANDLE - Unified CM sent the SAF Forwarder a Register message (for KeepAlive purposes) or unregister message with the mandatory CLIENT_HANDLE value, but the SAF Forwarder did not recognize the client handle. Unified CM will attempt to reregister with the SAF Forwarder without a client handle. This alarm is for informational purposes only; no action is required.

472

**INFO LEVEL** SAF_VERSION_NUMBER_TOO_LOW - Unified CM published a service (such as Hosted DN) whose version number is now lower than when it was previously published to the SAF Forwarder. The service is out of sync with the SAF Forwarder. Unified CM will republish the service in an attempt to resynch with the SAF Forwarder. This alarm is for informational purposes only; no action is required.

473

**INFO LEVEL** SAF_UNKNOWN_SERVICE - Unified CM attempted to unpublish a service from the SAF network but the SAF Forwarder does not have a publish record for that service. This alarm is for informational purposes only; no action is required.

474

**INFO LEVEL** SAF_UNREGISTERED - Unified CM attempted to publish or subscribe to the SAF Forwarder, but Unified CM is not registered with SAF Forwarder. Unified CM will automatically reregister with the SAF Forwarder before attempting to publish or subscribe. This alarm is for informational purposes only; no action is required.

475

**INFO LEVEL** SAF_BAD_FILTER - Unified CM attempted to subscribe to the SAF Forwarder with a filter that does not match any of the SAF Forwarder's current filters. Unified CM will resend the subscribe message with the appropriate filter value. This alarm is for informational purposes only; no action is required.

476

SAF_UNKNOWN_SUBSCRIPTION - Unified CM sent a subscribe or unsubscribe message to the SAF Forwarder but the message contained a Service ID that was not familiar to the SAF Forwarder. Without a recognized Service ID, Unified CM cannot subscribe to the SAF Forwarder. Recommended action is to contact the Cisco Technical Assistance Center (TAC).

477

**INFO LEVEL** SAF_ALREADY_REGISTERED - Unified CM attempted to register with the SAF Forwarder but SAF Forwarder indicates that Unified CM is already registered. Unified CM will close and reopen the TCP connection and send a new register request without a client handle to SAF Forwarder. This alarm is for informational purposes only; no action is required.

478

SAF_UNSUPPORTED_PROTOCOL_VERSION - Unified CM attempted to register with the SAF Forwarder using a SAF protocol version number that is greater than the protocol version number supported by the SAF Forwarder. Issue a show version command on the SAF Forwarder CLI to determine the SAF Forwarder protocol version; refer to the information in this alarmfor the SAF protocol version number. If the versions do not match, check the Cisco Unified Communications Manager Software Compatibility Matrix (available on Cisco.com) to determine whether the SAF protocol version number that is in use on this Unified CM is compatible with the SAF Forwarder protocol version. If it is not, upgrade the lower-versioned component so that both Unified CM and the SAF Forwarder use the same, compatible version.

479

SAF_UNKNOWN_AS - Unified CM attempted to register to the SAF Forwarder but the registration message contained a Client Label that was not familiar to the Autonomous System (AS) on the SAF Forwarder router. Recommended action is to issue the appropriate CLI commands on the SAF Forwarder to associate the Client Label with the autonomous system on the router (refer to the Configuration Guide for the router) and configure the same Client Label in the Client Label field on the SAF Forwarder Configuration window in Cisco Unified CM Administration and click Save. When the Client Label is saved in Cisco Unified CM Administration, Unified CM automatically sends a new registration request to the SAF Forwarder with the updated Client Label information.

500

**INFO LEVEL** SAF_RESPONDER_ERROR - Unified CM sent a message (such as register/unregister/publish/unpublish/subscribe) to the SAF Forwarder but the SAF Forwarder responded that it is unable to process the message at this time. This might be due to heavy message queuing, internal resource issues, and so on. Unified CM will wait several seconds and then retry the request. This alarm is for informational purposes only; no action is required.

1000

SAF_INVALID_CONNECTION_DETAILS


SAFUnknownService

Unified CM does not recognize the service ID in a publish revoke or withdraw message.

Unified CM received a Publish Revoke message or Withdraw message from the SAF Forwarder but the service ID in the message is not recognized by Unified CM. Unified CM may not recognize the service ID if the service ID was mistyped in the publish revoke CLI command, or if the service was previously withdrawn.

Cisco Unified Serviceability Alarm Catalog

CallManager/CallManager

Severity

Informational(6)

Routing List

SDL

SDI

Sys Log

Event Log

Parameters

Client Handle(String)

Service ID(UInt)

Sub Service ID(UInt)

InstanceID1(UInt)

InstancID2(UInt)

InstanceID3(UInt)

InstanceID4(UInt)

Recommended Action

None

SAFPublishRevoke

A CLI command revoked the publish action for the specified service or subservice ID.

A system administrator issued a CLI command on the SAF Forwarder router to revoke the publish action for the service or subservice ID specified in this alarm.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Client Handle(String)

Service ID(UInt)

Sub Service ID(UInt)

InstanceID1(UInt)

InstancID2(UInt)

InstanceID3(UInt)

InstanceID4(UInt)

Recommended Action

Informational purposes only; no action is required.

SAFResponderError

SAF Responder Error 500.

This is raised when SAF forwarder doesn't know the transaction ID within SAF response from this Cisco Unified CM.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Client Handle(String)

Service Id(UInt)

Sub Service ID(UInt)

Instance ID1(UInt)

Instance ID2(UInt)

Instance ID3(UInt)

Instance ID4(UInt)

Recommended Action

No action is required.

New Alarms in External Call Control

The following new alarms get issued for the External Call Control feature:

AwaitingResponseFromPDPTimeout

CallAttemptBlockedByPolicy

ConnectionFailureToPDP

ConnectionToPDPInService

DigitAnalysisTimeoutAwaitingResponse

ErrorParsingResponseFromPDP

ErrorParsingDirectiveFromPDP

FailureResponseFromPDP

FailedToFulfillDirectiveFromPDP

AwaitingResponseFromPDPTimeout

Cisco Unified Communication Manager timed out waiting for the routing response from the policy decision point. Cisco Unified Communications Manager (Unified CM) did not receive a call routing response from the policy decision point (PDP) within the time specified by the Cisco CallManager service parameter, Call Intercept Routing Request Timer, or on the Call Intercept Profile Configuration window in Cisco Unified CM Administration.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR_ALARM

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Policy Decision Point(String)

Recommended Action

Check whether the PDP is in service and working normally. Verify that the PDP is not overloaded; if it is, take appropriate action to reduce the load on the PDP by following some or all of these recommendations:

Consider adding more PDPs and provisioning Unified CM with additional call intercept profiles and call intercept trigger points in the various configuration pages under the Call Routing menu in Cisco Unified CM Administration.

Provision a pair of policy servers per call-intercept profile to enable load balancing.

OR

Verify that the PDP server in your deployment meets or exceed the hardware requirements specified in the documentation for Cisco Enterprise Policy Manager (CEPM) or the third-party PDP solution you have deployed. If necessary, increase the value in the Cisco CallManager service parameter, Call Intercept Routing Request Timer or the value in the Call Intercept Profile for this PDP.

CallAttemptBlockedByPolicy

A call was attempted but blocked or rejected by the policy decision point (PDP).

A call was rejected or blocked because it violated the enterprise policy as defined in a policy decision point (PDP) that was configured in Cisco Unified Communications Manager (Unified CM). The policy server returns a call reject decision stating that a policy violation was the reason for rejecting the call. Calls may be rejected because an unauthorized user attempted to dial a DN or pattern that is not allowed for him or her or because a call forward directive was invoked and the destination specified in the call forward operation violated the policy. Depending on email configuration in Real-Time Monitoring Tool (RTMT), the system may have generated an email alert when the call was rejected.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Alert Manager

Parameter(s)

Policy Decision Point(String)

Reject Reason(String)

Called Party Number(String)

Calling Party Number(String)

Calling User Id(String)

Recommended Action

Evaluate the information provided in this alarm (caller's user ID, to and from DNs, and so on) to determine if the call attempt was an innocent mistake to dial a number that the user didn't realize was not routable for him or her, or to discover whether the user is intentionally trying to circumvent the policy restrictions. If the rejected call was caused by an innocent mistake, educate the affected user about the numbers that he or she is allowed to dial. Your organization may have a policy or guidelines to follow when investigating call rejects. In addition to or instead of the steps recommended here, please refer to your company's guidelines.

ConnectionFailureToPDP

A connection request from Unified CM to the policy decision point (PDP) failed. The failure may have been a result of the following conditions:

Network error causing limited or no connectivity between Unified CM and the PDP

Authentication errors when Unified CM established an HTTPS connection to the PDP

PDP was not in service.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

Error(3)

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameters

Policy Decision Point(String)

The cause of the connection failure(String)

Recommended Action

Verify the network connectivity between Unified CM and the PDP by pinging the policy server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost. If the connection failure is due to an authentication problem, verify that the valid certificate of the PDP has been imported to Cisco Unified OS Administration and certificates from every node in the Unified CM cluster have been imported to every node in the PDP. Also, check whether the PDP service is active.

ConnectionToPDPInService

A connection was successfully established between Cisco Unified Communications Manager (Unified CM) and the policy decision point (PDP).

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

Informational(6)

Routing List

SDL

SDI

Sys Log

Event Log

Parameters

Policy Decision Point(String)

Recommended Action

None

DigitAnalysisTimeoutAwaitingResponse

Cisco Unified Communications Manager sent a routing request to the policy decision point but the request timed out without a response.

Cisco Unified Communications Manager (Unified CM) was unable to complete the routing request before timing out. This time out could occur due to low system resources, high CPU usage, or a high volume of call activities on this Unified CM node. Unified CM applies the Call Treatment on Failure that is configured for the External Call Control Profile associated with this call.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Translation Pattern Triggering Point(String)

Policy Decision Point(String)

Recommended Action

Check the External Call Control object in Real-Time Monitoring Tool (RTMT) to see whether the ExternalCallControlEnabledCallAttempted counter is spiking. If so, this indicates an unusually high number of calls at this time which could result in reduced system resources.

Check the QueueSignalsPresent2-Normal for persistent long high signal queue. If the long signal queue exists, check whether the Code Yellow alarm has already issued and check the system CPU and memory usage for this Unified CM node.

Follow the recommended actions for Code Yellow alarm if the Code Yellow alarm has fired.

For high CPU usage, use RTMT to determine which areas may be contributing to the high CPU usage. If this alarm persists, collect system performance data (such as the percentage of Memory, Page and VM usage, partition read and write bytes per second, the percentage of CPU usages of all the processes, and the processor IOWait percentage) and contact Cisco Technical Assistance Center (TAC).

ErrorParsingResponseFromPDP

Cisco Unified Communications Manager failed to parse one or multiple optional elements or attributes in the call routing response from the policy decision point.

A routing response was received from the policy decision point (PDP) but Cisco Unified Communications Manager (Unified CM) failed to parse the optional elements in the response. Optional elements may include modified calling numbers or called numbers, call reject or call diversion reasons, and so on. The cause may be a syntax error or missing attributes in the call routing response.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Policy Decision Point(String)

Called Party Number(String)

Calling Party Number(String)

Calling User Id(String)

Request XML Data(String)

Recommended Action

Check if call routing response from the policy decision point complies with the guidelines specified for external call control in the Cisco Unified Communications Manager documentation. Check if any optional elements included as the policy obligations in the call routing response are correctly entered according to the external call control documentation, including any applicable API documentation.

ErrorParsingDirectiveFromPDP

Cisco Unified Communications Manager (Unified CM) failed to parse the call routing directive or the diversion destination in the call routing response from the policy decision point (PDP).

A routing response was received but Cisco Unified Communications Manager (Unified CM) failed to parse the mandatory elements in the response. This means that a call routing directive or the call diversion destination could not be parsed correctly, or that the call routing directive was not recognized. The error may due to a syntax error or because the call routing directive is missing or the call diversion destination is missing in the call routing response.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Policy Decision Point(String)

Called Party Number(String)

Calling Party Number(String)

Calling User Id(String)

Response XML Data(String)

Recommended Action

Check whether the call routing response from the policy decision point (PDP) complies with Cisco Unified Communications Manager's interface specification for external call control. Check the external call control documentation, including any applicable API documentation, to determine whether the call routing directive that was included as part of the policy obligations in the call routing response are correctly entered according to the information defined in the external call control documentation.

FailureResponseFromPDP

The policy decision point (PDP) returned a 4xx (client) or 5xx (server) status code in the HTTP response.

Cisco Unified Communications Manager (Unified CM) received a 4xx or 5xx response from the policy decision point (PDP). A 4xx response indicates errors in the call routing request from Unified CM, for example: a 400 response indicates the call routing request could not be understood by the PDP; a 404 indicates that the PDP did not find a matching request URI. A 5xx error indicates a PDP server error, for example: a 500 response indicates a PDP internal error; A 501 response indicates that the PDP does not support the functionality to generate a call routing response; a 503 indicates that the PDP is busy and temporarily cannot generate a response; a 505 indicates that the HTTP version number included in the call routing request from Unified CM is not supported. Other such errors may be responsible; please refer to generally available guidelines on HTTP or check the RFC 2616 for detailed explanations about HTTP Status Code definitions.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

ERROR

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Policy Decision Point(String)

The status code and reason phrase for the failure(String)

Recommended Action

If a 4xx response caused the alarm, verify that the PDP has been accurately configured for the functionality and call routing that you expect it to perform. If a 500 response causes the alarm, check whether the PDP service is active and check the PDP server's log files for any errors. If a 503 causes the alarm, the PDP may be overloaded by requests. Take appropriate action to reduce the load on the PDP by following some or all of these recommendations: 1) consider adding more PDPs and provisioning Unified CM with additional call intercept profiles and call intercept trigger points in the various configuration pages under the Call Routing menu in Cisco Unified CM Administration; 2) provision a pair of policy servers per call-intercept profile to enable load balancing; or 3) verify that the PDP server in your deployment meets or exceed the hardware requirements specified in the documentation for Cisco Enterprise Policy Manager (CEPM) or the third-party PDP solution you have deployed. If a 505 response causes the alarm, check to be sure that the PDP supports HTTP version 1.1.

FailedToFulfillDirectiveFromPDP

Cisco Unified Communications Manager cannot fulfill the call routing directive returned by the PDP. The failure can occur because of the following conditions:

Call was cleared by a CTI application before Cisco Unified Communications Manager was able to route it to the location defined by the PDP.

Call that was allowed by a policy server was redirected by the CTI application to a destination.

Annunciator ID was misconfigured in the PDP.

Unified CM attempted to invoke a media resource such as Annunciator but no resources were available.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

Warning(4)

Routing List

SDL

SDI

Sys Log

Event Log

Parameters

Policy Decision Point(String)

Reason, Unified CM failed to fulfill the directive(String)

Called Party Number(String)

Calling Party Number(String)

Calling User Id(String)

Recommended Action

In many cases, the cause for a failure occurs because of the intervention by a CTI application which scoops up the call before Unified CM is able to fulfill the routing directive in the PDP. Examine the CTI application to ensure that the call is in alerting or connected state before the CTI begins to interact with it.

If the failure is caused by a problem with the annunciator ID, ensure the ID has been accurately configured in the PDP and that it exists in Unified CM Administration.

If the failure was caused by a lack of media resources, try increasing the Annunciator Call Count service parameter in the Cisco IP Voice Media Streaming App service.

New Alarms in Certificate Monitor Alarm Catalog

Certificate Monitoring service periodically scans the certificates of all applications and generates syslog events and email notifications. The system can be configured such that alerts are sent out "n" number of days in advance as configured by the Administrator. In addition, the severity level of alerts get set appropriately based on the remaining duration for the expiry of certificates.

For secure communication between nodes in a cluster, application such as extension mobility needs relevant certificates to be provisioned on all nodes. Certificate transfer between nodes get performed by using database replication. Provisioning of certificates for services such Tomcat need a service restart for the fresh certificates to come into effect. To alert the administrator for restart of Services, Certificate management sends syslog messages and alarms notifying the need for service restart.

The following alarms get described in this section:

CertValidLessthanADay

CertValidfor7days

CertValidityOver30Days

CertValidLessThanMonth

CertValidLessthanADay

Certificate is about to expire in less than 24 hours or has expired.

Cisco Unified Serviceability Alarm Definition Catalog

System/CertMonitorAlarmCatalog

Severity

Alert(1)

Routing List

Event Log

Sys Log

Parameters

Message(String)

Recommended Action

Regenerate the certificate that is about to expire by accessing the Cisco Unified Operating System and go to Certificate Management. If the certificate is issued by a CA, generate a CSR, submit the CSR to CA, obtain a fresh certificate from CA, and upload it to Cisco Unified CM.

CertValidfor7days

Alarm indicates that the certificate has expired or expires in less than seven days.

Cisco Unified Serviceability Alarm Definition Catalog

System/CertMonitorAlarmCatalog

Severity

Critical(2)

Routing List

Event Log

Sys Log

Parameters

Message(String)

Recommended Action

Regenerate the certificate that is about to expire by accessing the Cisco Unified Operating System and go to Certificate Management. If the certificate is issued by a CA, generate a CSR, submit the CSR to CA, obtain a fresh certificate from CA, and upload it to Cisco Unified CM.

CertValidityOver30Days

Alarm indicates that the certificate expiry is approaching but the expiry date is more than 30 days.

Cisco Unified Serviceability Alarm Definition Catalog

System/CertMonitorAlarmCatalog

Severity

Notice(5)

Routing List

Event Log

Sys Log

Parameters

Message(String)

Recommended Action

Regenerate the certificate that is about to expire by accessing the Cisco Unified Operating System and go to Certificate Management. If the certificate is issued by a CA, generate a CSR, submit the CSR to CA, obtain a fresh certificate from CA, and upload it to Cisco Unified CM.

CertValidLessThanMonth

Alarm indicates that the certificate will expire in 30 days or less.

Cisco Unified Serviceability Alarm Definition Catalog

System/CertMonitorAlarmCatalog

Severity

Warning(4)

Routing List

Event Log

Sys Log

Parameters

Message(String)

Recommended Action

Regenerate the certificate that is about to expire by accessing the Cisco Unified Operating System and go to Certificate Management. If the certificate is issued by a CA, generate a CSR, submit the CSR to CA, obtain a fresh certificate from CA, and upload it to Cisco Unified CM.

New Alarms in CMI Alarm Catalog

This section explains the new alarms added to the CMI Alarm Catalog.

CMIException

Error while reading the database.

This alarm is always associated with other alarms, which are triggered due to configuring CMI service parameter with invalid values or due to invalid handle value returned by the serial port.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ALERT

Routing List

Event Log

SDI

Parameter(s)

CMI Exception(String)

Recommended Action

Refer to the associated alarm for further information.

CMIServiceStatus

CMI service is running and working properly.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

INFORMATIONAL

Routing List

Event Log

SDI

Parameter(s)

Service Priority(String)

Recommended Action

Informational purpose only; no action is required.

DBLException

Unable to connect to the database.

When CMI service is started, it tries to read the CMI Service Parameters from database. During this, if CMI cannot connect to the database, it triggers this alarm.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ALERT

Routing List

Event Log

SDI

Parameter(s)

DBL Exception(String)

Recommended Action

Check Database connection, then restart CMI.

InvalidPortHandle

The handle for the opened serial port is invalid.

CMI cannot read/write to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ERROR

Routing List

Event Log

SDI

Parameter(s)

Error Information(String)

Recommended Action

Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

MemAllocFailed

CMI tried to allocate memory and failed.

Cisco Unified Communications Manager tried to read the Cisco Messaging Interface service parameters but not enough memory was allocated for the task and so the information could not be read.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

WARNING

Routing List

Event Log

SDI

Parameter(s)

Memory Allocation Failure(String)

Recommended Action

Use the Real-Time Monitoring Tool to check the performance counters related to system memory, to learn whether any memory leaks or spikes in CPU are occurring. Correct any anomalous memory issues you find. If you do not find any issues with memory, collect the system/application event logs and the performance (perfmon) logs and report this alarm to the Cisco Technical Assistance Center (TAC).

ParityConfigurationError

The CMI service parameter, Parity, has an invalid configuration.

An invalid parity has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the parity value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration and the value can be validated against the accepted range of values for this field.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ALERT

Routing List

Event Log

SDI

Parameter(s)

Illegal Parity(String)

Recommended Action

Verify that the Cisco Messaging Interface service parameter Parity is set to a valid (allowable) value.

ReadingFileFailure

CMI failed to read SMDI messages from the serial port.

CMI opened the serial port, however it failed to successfully read data from the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ERROR

Routing List

Event Log

SDI

Parameter(s)

Error Information(String)

Recommended Action

Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

SMDICmdError

CMI receives an invalid incoming SMDI message.

There are two kinds of incoming messages that Cisco Unified Communications Manager can accept from the voice messaging system; they are OP:MWI(SP)nnnnnnn!(D) and RMV:MWI(SP)nnnnnnn!(D) (where:nnnnnnnnnn = station number (can be 7 or 10 digits), (D) = End Of Transmission, (SP) = space). The first message activates the message waiting indicator (MWI). The second deactivates the message waiting indicator. CMI triggers this alarm if the received MWI message does not have one of the acceptable formats as described.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

NOTICE

Routing List

Event Log

SDI

Parameter(s)

Invalid SMDI command(String)

Recommended Action

Contact the vendor of the third-party voice messaging system and discover why it is sending SMDI message with an invalid format.

SMDIMessageError

SMDI message contains invalid DN.

Some voice messaging systems send SMDI messages to Cisco Unified Communications Manager (Unified CM) with an invalid DN specifically for the purpose of verifying that Unified CM is functioning properly. In such cases, if the Validate DNs service parameter is set to True, CMI triggers this alarm because the DN cannot be found in the Unified CM database.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

NOTICE

Routing List

Event Log

SDI

Parameter(s)

Invalid SMDI command(String)

Recommended Action

Verify that the Cisco Messaging Interface service parameter Validate DNs is set to false.

SerialPortGetStatusError

When CMI tries to get the status of serial port, the operating system returns an error.

CMI triggers this alarm when it cannot get the status of the serial port. An inability to receive the serial port status information can be caused by a loose or disconnected USB cable.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ERROR

Routing List

Event Log

SDI

Parameter(s)

Serial Port Getting Status Error(String)

Recommended Action

Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

SerialPortOpeningError

When CMI tries to open the serial port, the operating system returns an error.

For a system running CMI, the serial port through which the voice messaging system is connected is always USB0, and that value is configured in the Cisco Messaging Interface service parameter, Serial Port. It is possible that the Serial Port value has been updated via AXL or a CLI command where validation of the value was not performed. CMI triggers this alarm if the value in the Serial Port service parameter is anything other than USB0.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ALERT

Routing List

Event Log

SDI

Parameter(s)

Serial Port Opening Error(String)

Recommended Action

Ensure that USB0 is configured in the Cisco Messaging Interface service parameter Serial Port. Also, physically confirm that the cable is firmly connected to the USB0 port.

SerialPortSetStatusError

When CMI tries to set the status of serial port, the operating system returns an error.

CMI triggers this alarm when it cannot set the status of the serial port. An inability to receive the serial port status information can be caused by a loose or disconnected USB cable.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ERROR

Routing List

Event Log

SDI

Parameter(s)

Serial Port Setting Status Error(String)

Recommended Action

Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

StopBitConfigurationError

The Cisco Messaging Interface service parameter, Stop Bits, has an invalid configuration.

An invalid stop bit has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the Stop Bits value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration and the value can be validated against the accepted range of values for this field.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ALERT

Routing List

Event Log

SDI

Parameter(s)

Illegal Stop Bit(String)

Recommended Action

Verify that the Cisco Messaging Interface service parameter Stop Bits is set to a valid (allowable) value.

ThreadKillingError

An error occurred when CMI tried to stop the CMI service.

As a normal part of the process of stopping the CMI service, open threads are closed (killed). This alarm indicates that a timeout has occurred which means that the shutdown process is taking longer than expected, causing the operating system to return an error.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

WARNING

Routing List

Event Log

SDI

Parameter(s)

Error Information(String)

Recommended Action

Try restarting the CMI service. If the problem persists, collect the system/application event logs and the performance (perfmon) logs and report to Cisco Technical Assistance Center (TAC).

UnknownException

Unknown error while connecting to database.

When CMI service is started, it tries to read CMI service parameters from DB. During this, if there is an unknown error, CMI triggers this alarm.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ALERT

Routing List

Event Log

SDI

Recommended Action

Report to Customer Service representative.

VMDNConfigurationError

The Voice Mail DN for CMI is invalid.

CMI cannot register with Cisco Unified Communications Manager because of an invalid Voice Mail DN. This alarm occurs because the Cisco Messaging Interface service parameter, Voice Mail DN, is empty or has invalid characters other than digits (0-9). It is possible that the Voice Mail DN value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration and the value can be validated against the accepted range of values for this field.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ALERT

Routing List

Event Log

SDI

Parameter(s)

Invalid Voice Mail DN(String)

Recommended Action

Check the CMI service parameter Voice Mail DN to confirm that a valid directory number has been configured.

WritingFileFailure

CMI failed to write SMDI messages to the serial port.

CMI opened the serial port, however it failed to successfully write data to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Cisco Unified Serviceability Alarm Definition Catalog

CMIAlarmCatalog/CMI

Severity

ERROR

Routing List

Event Log

SDI

Parameter(s)

Error Information(String)

Recommended Action

Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

New Alarms in CTI Manager Alarm Catalog

This section explains the new alarms added to the CTI Manager Alarm Catalog.

ApplicationConnectionDropped

Application has dropped the connection to CTIManager.

TCP or TLS connection between CTIManager and Application is disconnected.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Recommended Action

Possible causes include Application server power outage, network power outage, network configuration error, network delay, packet drops or packet corruption. It is also possible to get this error if the Unified CM node or application server is experiencing high CPU usage. Verify the application is up and running, verify network connectivity between the application server and Unified CM, and verify the CPU utilization is in the safe range for application server and Unified CM (this can be monitored using RTMT via CPU Pegging Alert).

ApplicationConnectionError

CTIManager is unable to allow connections from Applications.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

CTI Connection type(String)

Recommended Action

CTIManager has encountered problems initializing TCP connections. Restart the CTIManager service to resolve this problem.

CtiDeviceClosed

Application closed a device.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Device Name(String)

RTP Address(String)

Reason code.(Enum)

Enum Definitions - Reason Code

Value
Definition

0

Unknown

1

CallManager service is not available to process request; verify that the CallManager service is active. Check the Cisco Unified Serviceability Control Center section in Cisco Unified CM Administration (Tools > Control Center - Feature Services)

2

Device has unregistered with Cisco Unified Communications Manager

3

Device failed to rehome to Cisco Unified Communications Manager; verify that the device is registered

4

Device is removed from the Unified CM database

5

Application controlling the device has closed the connection

6

Route Point already registered by another application

7

CTI Port already registered by another application

8

CTI Port/Route Point already registered with dynamic port media termination

9

Enabling softkey failed for device; verify that the device is registered

10

Multiple applications have registered the device with media capability that do not match

11

This device is already controlled by another application

12

Protocol used by the device is not supported

13

Device is restricted for control by any application

14

Unable to communicate with database to retrieve device information

15

Device is resetting

16

Unable to register the device as specified media type is not supported

17

Unsupported device configuration

18

Device is being reset

19

IPAddress mode does not match what is configured in Unified CM


Recommended Action

This alarm is for informational purposes only; no action is required.

CtiDeviceInService

Device is back in service.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Device Name(String)

Recommended Action

This alarm is for informational purposes only; no action is required.

CtiDeviceOpenFailure

Application is unable to open the device.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Device Name(String)

ReasonCode(Enum)

Enum Definitions - Reason Code

Value
Definition

0x8CCC0013 (2362179603)

Device is already opened by another application; identify the application that is controlling this device. You can determine this information from RTMT (CallManager->CTI Manager and CallManager->CTI Search)

0x8CCC00DA (2362179802)

Unable to communicate with database; verify the CPU utilization is in the safe range for (this can be monitored using RTMT via CPU Pegging Alert)

0x8CCC009A (2362179738)

Device is unregistering; wait for the device to register. Due to user initiated reset or restart of the device from Unified CM. Device should automatically register wait for few moments for the device to register

0x8CCC0018 (2362179608)

Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User)

0x8CCC00F3 (2362179827)

IPAddress mode (IPv4 or IPv6 or both) specified by the application does not match with IP Addressing mode that is configured in Unified CM Administration; check the IP addressing mode of the device in Cisco Unified CM Administration (Device > Device Settings > Common Device Configuration)


Recommended Action

Check the reason code and take appropriate action to resolve the issue.

CtiDeviceOpened

Application opened a device.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Device Name(String)

RTP Address(String)

Recommended Action

This alarm is for informational purposes only; no action is required.

CtiDeviceOutofService

Device is out of service.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Device Name(String)

Recommended Action

This alarm is for informational purposes only; no action is required.

CtiIncompatibleProtocolVersion

Incompatible protocol version.

The JTAPI/TAPI application version is not compatible with this version of CTIManager, so the received message has been rejected. The IP address is shown in either IPv4 or IPv6 format depending on the IP addressing mode of the Application.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Unified CM Version(String)

IPAddress(String)

IPv6Address(String)

Recommended Action

Verify that the correct version of the application is being used. If you are not sure of the correct version, contact the application vendor and upgrade the JTAPI/TSP to the version provided by Cisco Unified Communications Manager. JTAPI/TSP plugins are available in Cisco Unified CM Administration (Application > Plugins).

CtiLineClosed

Application closed the line.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Directory Number(String)

Partition(String)

Device Name(String)

Reason code.(Enum)

Enum Definitions - Reason Code

Value
Definition

0

Unknown

1

CallManager failure

2

Device has unregistered with Cisco Unified Communications Manager; wait for the device to register

3

CTI failed to rehome the line; verify that the device is registered

4

Undefined line, possible cause could be that line is no more active on that device due to extension mobility login or logout

5

Device removed

6

Provider controlling the device is closed

7

Protocol used by the device is not supported

8

Application cannot control this line as CTI Allow Control is not enabled. Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application

9

Unable to register the device; application specified media type is not supported

10

Device is being reset; verify that the device is registered before opening the line

11

Unsuppported device configuration


Recommended Action

This alarm is for informational purposes only; no action is required.

CtiLineInService

Line is back in service

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Recommended Action

This alarm is for informational purposes only; no action is required.

CtiLineOpenFailure

Application is unable to open the line.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Device Name(String)

Directory Number(String)

Partition(String)

Reason(Enum)

Enum Definitions - Reason Code

Value
Definition

0

Unknown

0x8CCC0018 (2362179608)

Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User)

0x8CCC0005 (2362179589)

Line is not found in the device; possible cause could be that the line that previously existed on this device is not available. This could be due to a extension mobility login or logout

0x8CCC00D3 (2362179795)

Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application


Recommended Action

Review the reason code and take appropriate action to resolve the issue.

CtiLineOpened

Application opened the line.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Directory Number(String)

Partition(String)

Device Name(String)

Recommended Action

This alarm is for informational purposes only; no action is required.

CtiLineOutOfService

Line is out of service

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Directory Number(String)

Device Name(String)

Recommended Action

This alarm is for informational purposes only; no action is required.

CtiMaxConnectionReached

Maximum number of CTI connections has been reached, no new connection will be accepted unless an existing connection is closed

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Recommended Action

Check the CTI Manager service parameter Maximum CTI Connections for the maximum number of connections. Carefully, consider increasing the service parameter value or disconnecting CTI applications that are unnecessary. Refer to Unified CM Solution Reference Network Design document in www.cisco.com based on the version you are using for maximum number of applications and devices supported by CTI.

CtiProviderCloseHeartbeatTimeout

CTI heartbeat timeout occurred causing CTIManager to close the application connection.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Recommended Action

Heartbeat timeout could occur due to high CPU usage or network connectivity problems. Check for and fix any network issues or high CPU usage on the application server. If the application server is running the Microsoft Windows OS use Task Manager or Perfmon to determine the CPU usage. For applications in Linux use the top command to review CPU usage.

CtiProviderClosed

CTI application closed the provider. The IP address is shown in either IPv4 or IPv6 format depending on the IP addressing mode of the application.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Login User Id(String)

IPAddress(String)

IPV6Address(String)

Reason code(Enum)

Enum Definitions - Reason Code

Value
Definition

0

Unknown

1

Heart beat from application missed. Possible causes include network connectivity issues or Unified CM node experiencing high CPU usage. Make sure that the network connectivity between Unified CM and the application by pinging the application server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost. Also check for and fix any network issues or high CPU usage on the application server

2

Unexpected shutdown; possibly cause is application disconnected the TCP connection. Also check for and fix any network issues or high CPU usage on the application server

3

Application requested provider close

4

Provider open failure; application could not be initialized

5

User deleted. User associated with the application is deleted from the Unified CM Administration

6

SuperProvider permission associated with the application is removed. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information

7

Duplicate certificate used by application. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information

8

CAPF information unavailable. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information

9

Certificate compromised. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information

11

User is not authorized to connect to CTI using TLS. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure... > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information

12

Standard CTI Use permission removed. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information


Recommended Action

This alarm is for informational purposes only; no action is required.

CtiProviderOpenFailure

CTI application is unable to open the provider. The IP address is shown in either IPv4 or IPv6 format depending on the IP addressing mode of the application.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

ERROR

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Login User Id(String)

Reason code.(Enum)

IPAddress(String)

IPV6Address(String)

Enum Definitions - Reason Code

Value
Definition

0

Unknown

0x8CCC0075 (2362179701)

Login request to authenticate user has timed out. Possible causes include LDAP server misconfiguration such as LDAP server referrals misconfiguration or Unified CM node experiencing high CPU usage. Recommended action is to verify the CPU utilization is in the safe range for Unified CM (this can be monitored using RTMT via CPU Pegging Alert)

0x8CCC0060 (2362179680)

Directory login failed. Verify that credentials are not misconfigured, check the userID and password configured in the application matches with what is configured in Unified CM Admin under (User Management > End User or Application User)

0x8CCC005E (2362179678)

Directory is unavailable. Verify that the LDAP server is reachable from Unified CM node, make sure that the network connectivity between Unified CM and the LDAP server by pinging the LDAP server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost

0x8CCC00D1 (2362179793)

Application is connecting to a non secure port but has security privileges enabled for the user associated with the application. Check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information

0x8CCC005F (2362179679)

Standard CTI Use permission is not enabled. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information

0x8CCC00D0 (2362179792)

User is not enabled for a secure connection but the application connecting to secure port. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure... > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information


Recommended Action

Review the reason code and the recommended action within the reason code.

CtiProviderOpened

CTI Application opened the provider successfully. The IP address is shown in either IPv4 or IPv6 format depending on the IP addressing mode of the Application.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Data Collector

Parameter(s)

Login User Id(String)

Version Number(String)

IPAddress(String)

IPV6Address(String)

Recommended Action

This alarm is for informational purposes only; no action is required.

CtiQbeFailureResponse

The requested operation from the application could not be performed because of a normal or abnormal condition.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Error message(String)

Recommended Action

Verify whether the affected application is experiencing a problem. Contact the support organization for the affected application if the problem persists and provide sequence number and error message for further investigation.

InvalidQBEMessage

QBE PDU from application is invalid.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

CTI Connection type(String)

Recommended Action

This alarm indicates that TSP/JTAPI has reported a QBE PDU that cannot be recognized by CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins).

MaxDevicesPerNodeExceeded

An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Node.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Recommended Action

One or more applications are controlling more devices than the CTI support allows on the specified Unified CM node. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the total number of devices controlled by applications is not properly restricted to the device limit specified by the CTIManager service parameter, Maximum Devices Per Node.

MaxDevicesPerProviderExceeded

An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Provider

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Recommended Action

The application is controlling more devices than the CTI support allows. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the application does not restrict support to the device limit specified by CTI in the CTIManager service parameter, Maximum Devices Per Provider.

RedirectCallRequestFailed

CTIManager is unable to redirect a call

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

INFORMATIONAL

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Directory Number(String)

Partition(String)

Recommended Action

This alarm is for informational purposes only; no action is required.

UnableToRegisterwithCallManagerService

CTI cannot communicate with Cisco CallManager service to register supplementary service features.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

ERROR

Routing List

SDL

SDI

Sys Log

Event Log

Recommended Action

Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists. If CallManager service is active, verify network connectivity between the Unified CM node that hosts CTIManager service and Unified CM node that hosts CallManager service.

UnableToSetorResetMWI

An error occurred when setting the message waiting indication (MWI) lamp

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CtiManager

Severity

WARNING

Routing List

SDL

SDI

Sys Log

Event Log

Parameter(s)

Directory Number(String)

Recommended Action

The line issuing the request to set the MWI lamp on the target line might not have the proper partitions/calling search space settings to allow it to reach the target line. Check the partitions and calling search space of the line that is requesting to set MWI on the target line. The target line should be able to receive a call from the line that is attempting to set MWI.

New Alarms in DRF Alarm Catalog

This section explains the new alarms added to the DRF Catalog.

DRFBackupCompleted

DRF backup completed successfully.

Cisco Unified Serviceability Alarm Definition Catalog

System/DRF

Severity

INFORMATIONAL

Routing List

Event Log

Sys Log

Parameter(s)

Reason(String)

Recommended Action

Ensure that the backup operation is completed successfully.

DRFLocalDeviceError

DRF unable to access local device.

Cisco Unified Serviceability Alarm Definition Catalog

System/DRF

Severity

ERROR

Routing List

Event Log

Sys Log

Parameter(s)

Reason(String)

Recommended Action

Check if local location exists and is accessible.

DRFNoBackupTaken

A valid backup of the current system was not found after an Upgrade, Migration, or Fresh Install.

Cisco Unified Serviceability Alarm Definition Catalog

System/DRF

Severity

WARNING

Routing List

Event Log

Sys Log

Parameter(s)

Reason(String)

Recommended Action

It is recommended to perform a Backup using the Disaster Recovery System.

DRFRestoreCompleted

DRF restore completed successfully.

Cisco Unified Serviceability Alarm Definition Catalog

System/DRF

Severity

INFORMATIONAL

Routing List

Event Log

Sys Log

Parameter(s)

Reason(String)

Recommended Action

Ensure that the restore operation is completed successfully.

New Alarm in IpVms Alarm Catalog

This section explains the new alarms added to the IpVms Catalog.

kANNAudioFileMissing

Announcement file not found. The annunciator was unable to access an announcement audio file. This may be caused by not uploading a custom announcement to each server in the cluster or a locale has not been installed on the server.

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/IpVms

Severity

WARNING

Routing List

SDI

Event Log

Sys Log

Parameter(s)

Missing filename(String)

Recommended Action

Upload the custom announcement to the server or install the missing locale package.

New Alarms in JavaApplications Alarm Catalog

This section explains the new alarms added to the JavaApplications Catalog.

CiscoHardwareLicenseInvalid

Installation on invalid or obsolete hardware. Cannot upload license files.

Cisco Unified Serviceability Alarm Definition Catalog

System/Java Applications

Severity

INFORMATIONAL

Routing List

Sys Log

Event Log

SNMP Traps

Parameter(s)

Reason(String)

Recommended Action

Obtain correct hardware and re-install.

CiscoLicenseFileInvalid

License File is invalid.

Cisco Unified Serviceability Alarm Definition Catalog

System/Java Applications

Severity

INFORMATIONAL

Routing List

Sys Log

Event Log

SNMP Traps

Parameter(s)

Reason(String)

Recommended Action

Rehost the License files.

New Alarm in RTMT Alarm Catalog

This section explains the new alarm added to the RTMT catalog.

RTMT_ALERT

A Real-Time Monitoring Tool (RTMT) process in the AMC service uses the alarm mechanism to facilitate delivery of RTMT alerts in the RTMT AlertCentral or through email.

Cisco Unified Serviceability Alarm Definition Catalog

System/RTMT

Severity

ERROR

Routing List

Event Log

Sys Log

Parameter(s)

Name(String)

Detail(String)

Recommended Action

Check AlertCentral in RTMT or any alerts that you have received through email to determine what issue has occurred and learn the recommended actions to resolve it. In AlertCentral, right-click the alert to open the alert information.

Changed Alarms in CallManager Alarm Catalog

This section explains changes done to the existing alarms in CallManager Catalog.


Note The Description and the Recommended Action have been updated for all the alarms listed below. Other changes are indicated in the History table.


AnnunciatorNoMoreResourcesAvailable

No more Annunciator resources available.

Annunciator resource allocation failed for one or more of the following reasons: all Annunciator resources are already in use; there was a codec or capability mismatch (such as the endpoint using one type of IP addressing such as IPv6, while the Annunciator supports only IPv4) between the endpoint and the Annunciator resource; not enough bandwidth existed between the endpoint and the Annunciator.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog— CallManager/CallManager

Severity—Warning

Recommended Action

If all the resources of the Annunciator are already in use, check to be sure that all the Annunciators that belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are configured and registered in all the applicable Unified CM nodes of the cluster. To check the registration status go to the Media Resources > Annunciator menu and click the Find button. It will display all the Annunciators with their status, device pool, and so on.

Check the status field to see whether it is registered with Unified CM. Note that the display on the status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified CM cluster that the Publisher can only write to the Unified CM database before the Publisher goes down. Because the Subscriber may not be able to write to the database, the devices may still display registered in Unified CM Administration after they are actually unregistered. However, if the Publisher is down that should generate another alarm with higher priority than this alarm.

The Annunciator allocation can fail due to codec mismatch or capability mismatch between the endpoint and the Annunciator. If there is a codec mismatch or capability mismatch (such as the endpoint using IPv6 addressing but Annunciator supporting only IPv4), an MTP or transcoder should be allocated. So, if the MTP or transcoder is not allocated then either MediaResourceListExhausted (with Media Resource Type as Media termination point or transcoder) or MtpNoMoreResourcesAvailable alarm will be generated for the same Media Resource Group List and you should first concentrate on that.

The Annunciator allocation may even fail after checking the region bandwidth between the regions to which the held party belongs and the region to which the Annunciator belongs. Increasing the region bandwidth may be a solution to the problem, but that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, the average number of calls using the Annunciator, approximate bandwidth use per call, and so on, and accordingly calculate the region bandwidth.

Another possible cause is that the bandwidth needed for the call may not be available. This can happen if the Annunciator and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased.

However, note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth.

BChannelISV

B-channel is in service.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Notice.


Alarm Catalog— CallManager/CallManager

Severity—Notice

Recommended Action

None

BChannelOOS

The B-channel is out of service. The B-channel indicated by this alarm has gone out of service. Some of the more common reasons for a B-channel to go out of service include are as follows:

Taking the channel out of service intentionally to perform maintenance on either the near- or far-end

MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Cisco Unified Communications Manager (Cisco Unified CM)

MGCP gateway does not respond to an MGCP command sent by Cisco Unified CM three times

Speed and duplex mismatch exists on the Ethernet port between Cisco Unified CM and the MGCP gateway.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Critical.


Alarm Catalog—CallManager/CallManager

Severity—Critical

Recommended Action

Check the Cisco Unified CM advanced service parameter, Change B-channel Maintenance Status to determine if the B-channel has been taken out of service intentionally; Check the Q.931 trace for PRI SERVICE message to determine whether a PSTN provider has taken the B-channel out of service; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.

BeginThrottlingCallListBLFSubscriptions

Cisco Unified Communications Manager has initiated throttling of CallList BLF Subscriptions as a preventive measure to avoid overloading the system. This alarm is raised when the total number of active BLF subscriptions exceeds the configured limit set by the Presence Subscription Throttling Threshold service parameter.

Alarm Catalog—CallManager/CallManager.

Severity—Warning

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.

CMInitializationStateTime

Indicates the amount of time required to complete initialization for the specified state.

Alarm Catalog—CallManager/CallManager.

Severity—Informational

Recommended Action

None

CMOverallInitTimeExceeded

Initialization of the Cisco Unified Communications Manager system has taken longer than allowed by the value specified in the System Initialization Timer service parameter; as a result, the system will automatically restart now to attempt initialization again. The required time to initialize Unified CM has exceeded the time allowed by the Cisco CallManager service parameter, System Initialization Timer; as a result, the system will automatically restart to attempt initialization again. Initialization may have failed due to an increase in system size, due a database error, due to a large amount of new devices added to the system, or any number of other potential causes.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Alert.


Alarm Catalog—CallManager/CallManager

Severity—Alert

Recommended Action

Use RTMT to discover the number of devices and number of users in the system and evaluate whether the numbers seem accurate. Try increasing the value of the Cisco CallManager service parameter, System Initialization Timer, in the Service Parameters Configuration window in Cisco Unified CM Administration. If increasing the time in the System Initialization Timer service parameter does not correct this issue, contact the Cisco Technical Assistance Center (TAC).

CMTotalInitializationStateTime

Indicates the amount of time required to complete the specified total system initialization state.

Alarm Catalog—CallManager/CallManager

Severity—Informational

Recommended Action

None

CallManagerFailure

Indicates an internal failure in the Cisco Unified Communications system. The service should restart in an attempt to clear the failure.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Critical.

Enum Definitions are updated.


Alarm Catalog—CallManager/CallManager

Severity—Critical

Enum Definitions

Code
Reason

1

Unknown—Unified CM has failed for an unknown reason.

2

HeartBeatStopped—An internal heart beat has stopped after the preceding heart beat interval.

3

RouterThreadDied—An internal thread has failed.

4

TimerThreadDied—An internal thread has failed.

5

CriticalThreadDied—An internal thread has failed.


Recommended Action

Monitor for other alarms and restart the Cisco CallManager service, if necessary. Collect the existing trace files in case the alarm persists.

CallManagerOnline

Cisco CallManager service has completed initialization is online.

Alarm Catalog—CallManager/CallManager

Severity—Notice

Recommended Action

None

CodeRedEntry

Unified CM has entered Code Red condition and will restart.

Unified CM has been in Code Yellow state for an extended peiod and is unlikely to recover on its own. The Cisco CallManager service automatically restarts in an attempt to clear the condition that is causing the Code Yellow state. The amount of time that the system will remain in Code Yellow state is configurable in the Code Yellow Duration service parameter. If the duration of this parameter is set to 99999, Code Red condition will never occur.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Critical.


Alarm Catalog—CallManager/CallManager

Severity—Critical

Recommended Action

You should have attempted the steps in the recommended actions defined in the CodeYellowEntry alarm. If you have not, try those after the system is online. There is no other action for Code Red because the only action is to restart which is performed for you automatically.

CodeYellowEntry

CallManager has initiated call throttling due to unacceptably high delay in handling incoming calls.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Critical.


Alarm Catalog—CallManager/CallManager

Severity—Critical

Recommended Action

Memory problems or high CPU usage are generally at the root of a Code Yellow state. A bad disk could also be the cause. Also, trace level settings can consume tremendous amounts of CPU (especially when the Enable SDL TCP Event Trace checkbox is enabled on the SDL Trace Configuration window in Cisco Unified Serviceability). Check these areas to try to correct the Code Yellow condition. You can also determine the level of fragmentation on the hard disk by issuing the File Fragmentation command from the CLI for the trace directories. Monitor the situation and collect existing trace files. If the CodeYellowExit alarm is not issued in a reasonable amount of time as deemed by your organization, or if the system is frequently entering Code Yellow state, contact TAC and supply the trace information you have collected.

CodeYellowExit

CodeYellowExit. Unified CM has ceased throttling calls and has exited the Code Yellow state.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Notice.


Alarm Catalog—CallManager/CallManager

Severity—Notice

Recommended Action

None.

ConferenceNoMoreResourcesAvailable

Conference resource allocation failed for one or more of the following reasons: the required number of conference resources were not available; for an IOS-based conference bridge, the number of participants to be added to the conference bridge exceeded the maximum number of participants allowed per conference; no lower precedence conference was available for preemption although MLPP preemption was enabled; a lower-precedence conference bridge was not preempted.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed severity level from Error to Warning.


Alarm Catalog—CallManager/CallManager

Severity—Warning

Recommended Action

For IOS-based conference bridges, make sure that the maximum number of participants configured in a conference bridge does not exceed the number of participants allowed per conference; please check the IOS-based conference bridge user manual for limitations on the number of participants. Also, be sure to educate end users about the maximum number of participants allowed. For IOS-based and non-IOS-based, consider installing additional conference resources.

ConnectionFailure

Cisco CallManager failed to open TLS connection for the indicated device. Possible reasons could be wrong "Device Security Mode" configured, wrong "X.509 Subject Name" configured or unsupported cipher algorithm.

Alarm Catalog—CallManager/CallManager.

Severity—Error (3)

Recommended Action

Check the Security profile of the indicated device. Make sure "Device Security Mode" is either "Authenticated" or "Encrypted". Make sure "X.509 Subject Name" field has the right content. It should match the Subject Name in the certificate from the peer. Unified CM only supports AES_128_SHA cipher algorithm. Let the peer regenerate its certificate with the right algorithm.

DBLException

An error occurred while performing database activities. A severe database layer interface error occurred. Possible causes for this include the database being unreachable or down or a DNS error.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Alert.


Alarm Catalog—CallManager/CallManager

Severity—Alert

Recommended Action

Review the System Reports provided in the Cisco Unified Reporting tool, specifically the Unified CM Database Status report, for any anomalous activity. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. Check network connectivity to the server that is running the database. If your system uses DNS, check the DNS configuration for any errors. If the cause is still not identified, collect SDL and SDI traces and contact the Cisco Technical Assistance Center (TAC).

DChannelISV

Indicated D-channel has gone in service.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Notice.


Alarm Catalog—CallManager/CallManager

Severity—Notice

Recommended Action

None

DChannelOOS

The D-channel is out of service. D-channel indicated by this alarm has gone out of service. Common reasons for a D-channel going out of service include losing T1/E1/BRI cable connectivity; losing the gateway data link (Layer 2) due to an internal or external problem; or gateway reset.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Critical.


Alarm Catalog—CallManager/CallManager

Severity—Critical

Recommended Action

Check the connection of the T1/E1/BRI cable; reset the gateway to restore Layer 2 connectivity; investigate whether the gateway reset was intentional. If the reset was not intentional, take steps to restrict access to the Gateway Configuration window in Cisco Unified Communications Manager Administration and the gateway terminal.

DaTimeOut

The digit analysis component in Cisco Unified Communications Manager has timed out. This can occur because Cisco Unified Communications Manager is busy and the resulting delay in processing request and response messages caused the digit analysis component to time out.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/CallManager

Severity—Warning

Recommended Action

In the Service Parameter Configuration window in Cisco Unified CM Administration, check the Cisco CallManager service parameter, Digit Analysis Timer, to confirm that the default value is in use. Use RTMT to monitor the system resources and correct any system issues that might be contributing to high CPU utilization on Cisco Unified CM.

DatabaseDefaultsRead

Database default information was read successfully.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Notice to Informational.


Alarm Catalog—CallManager/CallManager.

Severity—Informational

Recommended Action

None

DeviceApplyConfigInitiated

Device Apply Config initiated.

This alarm occurs when a system administrator presses the Apply Config button in Cisco Unified Communications Manager (Unified CM). The Apply Config button initiates a conditional restart on devices that support conditional restart. This button triggers the system to determine if any relevant configuration has changed for the device. If the configuration changes can be applied dynamically, they are made without service interruption. If a change requires that the device reregister with Unified CM, reregistration occurs automatically. If a change requires a restart, the device will be automatically restarted. If the load ID for a device changes, the device will initiate a background download of the new firmware. The new firmware can then be applied immediately or at a later time. For phones and devices that do not support conditional restart, clicking Apply Config causes these devices to restart.

Alarm Catalog—CallManager/CallManager.

Severity—Informational.

Recommended Action

None

DeviceCloseMaxEventsExceeded

The TCP socket for the SCCP device has been closed due to excessive events in a 5-second period. Under normal conditions, the device will reregister automatically.

The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage.

Alarm Catalog—CallManager/CallManager.

Severity—Error (3).

Recommended Action

Check the CCM trace data for the indicated SCCP device to determine the reason for the high number of events. Confirm that the value configured in the Cisco CallManager service parameter, Max Events Allowed, is a suitable number for your deployment.

DeviceDnInformation

List of directory numbers associated with the device.

Alarm Catalog—CallManager/CallManager.

Severity—Informational (6)

Recommended Action

None

DeviceInitTimeout

Device initialization timeout occurred. This alarm does not occur under normal working conditions; it will only occur if a device fails to respond to an initialize request.

Alarm Catalog—CallManager/CallManager.

Severity—Error (3)

Recommended Action

Investigate the identified device.

DevicePartiallyRegistered

Device partially registered. A device is partially registered with Cisco CallManager. Some, but not all, of the lines configured on the device have successfully registered.

History

Cisco Unified Communications
Release
Action

8.0(1)

Following information is updated:

Enum Definitions for performance monitor object type

Enum Definitions for DeviceType


Alarm Catalog—CallManager/CallManager

Severity—Warning

Enum Definitions for Performance Monitor Object type

Code
Reason

1

Cisco CallManager

2

Cisco Phones

3

Cisco Lines

4

Cisco H323

5

Cisco MGCP Gateway

6

Cisco MOH Device

7

Cisco Analog Access

8

Cisco MGCP FXS Device

9

Cisco MGCP FXO Device

10

Cisco MGCP T1CAS Device

11

Cisco MGCP PRI Device


Enum Definitions for DeviceType

Code
Reason

1

CISCO_30SP+

2

CISCO_12SP+

3

CISCO_12SP

4

CISCO_12S

5

CISCO_30VIP

6

CISCO_7910

7

CISCO_7960

8

CISCO_7940

9

CISCO_7935

10

CISCO_VGC_PHONE

11

CISCO_VGC_VIRTUAL_PHONE

12

CISCO_ATA_186

20

SCCP_PHONE

30

ANALOG_ACCESS

40

DIGITAL_ACCESS

42

DIGITAL_ACCESS+

43

DIGITAL_ACCESS_WS-X6608

47

ANALOG_ACCESS_WS-X6624

48

VGC_GATEWAY

50

CONFERENCE_BRIDGE

51

CONFERENCE_BRIDGE_HARDWARE

52

CONFERENCE_BRIDGE_HARDWARE_HDV2

53

CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM

61

H323_PHONE

62

H323_GATEWAY

70

MUSIC_ON_HOLD

71

DEVICE_PILOT

72

CTI_PORT

73

CTI_ROUTE_POINT

80

VOICE_MAIL_PORT

83

SOFTWARE_MEDIA_TERMINATION_POINT_HDV2

84

CISCO_MEDIA_SERVER

85

CISCO_VIDEO_CONFERENCE_BRIDGE

90

ROUTE_LIST

100

LOAD_SIMULATOR

110

MEDIA_TERMINATION_POINT

111

MEDIA_TERMINATION_POINT_HARDWARE

112

MEDIA_TERMINATION_POINT_HDV2

113

MEDIA_TERMINATION_POINT_WS-SVC-CMM

115

CISCO_7941

119

CISCO_7971

120

MGCP_STATION

121

MGCP_TRUNK

122

GATEKEEPER

124

7914_14_BUTTON_LINE_EXPANSION_MODULE

125

TRUNK

126

TONE_ANNOUNCEMENT_PLAYER

131

SIP_TRUNK

132

SIP_GATEWAY

133

WSM_TRUNK

134

REMOTE_DESTINATION_PROFILE

227

7915_12_BUTTON_LINE_EXPANSION_MODULE

228

7915_24_BUTTON_LINE_EXPANSION_MODULE

229

7916_12_BUTTON_LINE_EXPANSION_MODULE

230

7916_24_BUTTON_LINE_EXPANSION_MODULE

232

CKEM_36_BUTTON_LINE_EXPANSION_MODULE

254

UNKNOWN_MGCP_GATEWAY

255

UNKNOWN

302

CISCO_7989

307

CISCO_7911

308

CISCO_7941G_GE

309

CISCO_7961G_GE

335

MOTOROLA_CN622

336

BASIC_3RD_PARTY_SIP_DEVICE

348

CISCO_7931

358

CISCO_UNIFIED_COMMUNICATOR

365

CISCO_7921

369

CISCO_7906

374

ADVANCED_3RD_PARTY_SIP_DEVICE

375

CISCO_TELEPRESENCE

404

CISCO_7962

412

CISCO_3951

431

CISCO_7937

434

CISCO_7942

435

CISCO_7945

436

CISCO_7965

437

CISCO_7975

446

CISCO_3911

468

CISCO_UNIFIED_MOBILE_COMMUNICATOR

478

CISCO_TELEPRESENCE_1000

479

CISCO_TELEPRESENCE_3000

480

CISCO_TELEPRESENCE_3200

481

CISCO_TELEPRESENCE_500

484

CISCO_7925

493

CISCO_9971

495

CISCO_6921

496

CISCO_6941

497

CISCO_6961

20000

CISCO_7905

30002

CISCO_7920

30006

CISCO_7970

30007

CISCO_7912

30008

CISCO_7902

30016

CISCO_IP_COMMUNICATOR

30018

CISCO_7961

30019

CISCO_7936

30027

ANALOG_PHONE

30028

ISDN_BRI_PHONE

30032

SCCP_GATEWAY_VIRTUAL_PHONE

30035

IP_STE


Recommended Action

In the Cisco Unified Reporting tool, run the Unified CM Multi-Line Devices report and check the number of lines that are supposed to be configured on the device identified in this alarm. If the device has registered an inconsistent number of lines compared the Multi-Lines report for this device, restart the device so that it can reregister all lines. If this alarm persists, verify that the appropriate number of lines has been configured on the device, and that the appropriate directory numbers have been configured. If the device is a third-party SIP phone, verify that the directory numbers configured on the phone match the directory numbers configured on the device in Unified CM Administration.

DeviceRegistered

A device successfully registered with Cisco CallManager.

History

Cisco Unified Communications
Release
Action

8.0(1)

Following information is updated:

Enum Definitions for Performance Monitor ObjType

Enum Definitions for Device type

Enum Definitions for IPAddrAttributes

Enum Definitions for IPV6AddrAttributes


Alarm Catalog—CallManager/CallManager

Severity—Informational

Enum Definitions for Performance Monitor ObjType

Code
Reason

1

Cisco CallManager

3

Cisco Lines

4

Cisco H.323

5

Cisco MGCP Gateway

6

Cisco MOH Device

7

Cisco Analog Access

8

Cisco MGCP FXS Device

9

Cisco MGCP FXO Device

10

Cisco MGCP T1CAS Device

11

Cisco MGCP PRI Device

30

Cisco Mobility Manager


Enum Definitions for DeviceType

Code
Reason

10

CISCO_VGC_PHONE

11

CISCO_VGC_VIRTUAL_PHONE

30

ANALOG_ACCESS

40

DIGITAL_ACCESS

42

DIGITAL_ACCESS+

43

DIGITAL_ACCESS_WS-X6608

47

ANALOG_ACCESS_WS-X6624

48

VGC_GATEWAY

50

CONFERENCE_BRIDGE

51

CONFERENCE_BRIDGE_HARDWARE

52

CONFERENCE_BRIDGE_HARDWARE_HDV2

53

CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM

62

H323_GATEWAY

70

MUSIC_ON_HOLD

71

DEVICE_PILOT

73

CTI_ROUTE_POINT

80

VOICE_MAIL_PORT

83

SOFTWARE_MEDIA_TERMINATION_POINT_HDV2

84

CISCO_MEDIA_SERVER

85

CISCO_VIDEO_CONFERENCE_BRIDGE

90

ROUTE_LIST

100

LOAD_SIMULATOR

110

MEDIA_TERMINATION_POINT

111

MEDIA_TERMINATION_POINT_HARDWARE

112

MEDIA_TERMINATION_POINT_HDV2

113

MEDIA_TERMINATION_POINT_WS-SVC-CMM

120

MGCP_STATION

121

MGCP_TRUNK

122

GATEKEEPER

124

7914_14_BUTTON_LINE_EXPANSION_MODULE

125

TRUNK

126

TONE_ANNOUNCEMENT_PLAYER

131

SIP_TRUNK

132

SIP_GATEWAY

133

WSM_TRUNK

134

REMOTE_DESTINATION_PROFILE

227

7915_12_BUTTON_LINE_EXPANSION_MODULE

228

7915_24_BUTTON_LINE_EXPANSION_MODULE

229

7916_12_BUTTON_LINE_EXPANSION_MODULE

230

7916_24_BUTTON_LINE_EXPANSION_MODULE

232

CKEM_36_BUTTON_LINE_EXPANSION_MODULE

254

UNKNOWN_MGCP_GATEWAY

255

UNKNOWN

30027

ANALOG_PHONE

30028

ISDN_BRI_PHONE

30032

SCCP_GATEWAY_VIRTUAL_PHONE


Enum Definitions for IPAddrAttributes

Code
Reason

0

Unknown—The device has not indicated what this IPv4 address is used for.

1

Administrative only—The device has indicated that this IPv4 address is used for administrative communication (web interface) only.

2

Signal only—The device has indicated that this IPv4 address is used for control signaling only.

3

Administrative and signal—The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling.


Enum Definitions for IPV6AddrAttributes

Code
Reason

0

Unknown—The device has not indicated what this IPv6 address is used for.

1

Administrative only—The device has indicated that this IPv6 address is used for administrative communication (web interface) only.

2

Signal only—The device has indicated that this IPv6 address is used for control signaling only.

3

Administrative and signal—The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling.


Recommended Action

None

DeviceResetInitiated

Device reset initiated on the specified device.

This alarm occurs when a device is reset via the Reset button in Cisco Unified CM Administration. Reset may cause the device to shut down and come back in service. A device can be reset only when it is registered with Cisco Unified Communications Manager.

History

Cisco Unified Communications
Release
Action

8.0(1)

Enum Definitions for DeviceType are updated.

Parameters added: Product type [String]


Alarm Catalog—CallManager/CallManager

Severity—Informational

Parameters

Device name [Optional]. [String] Device type. [Optional] [Enum] Product type [String]

Enum Definitions for DeviceType

Code
Device Type

10

CISCO_VGC_PHONE

11

CISCO_VGC_VIRTUAL_PHONE

30

ANALOG_ACCESS

40

DIGITAL_ACCESS

42

DIGITAL_ACCESS+

43

DIGITAL_ACCESS_WS-X6608

47

ANALOG_ACCESS_WS-X6624

48

VGC_GATEWAY

50

CONFERENCE_BRIDGE

51

CONFERENCE_BRIDGE_HARDWARE

52

CONFERENCE_BRIDGE_HARDWARE_HDV2

53

CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM

62

H323_GATEWAY

70

MUSIC_ON_HOLD

71

DEVICE_PILOT

73

CTI_ROUTE_POINT

80

VOICE_MAIL_PORT

83

SOFTWARE_MEDIA_TERMINATION_POINT_HDV2

84

CISCO_MEDIA_SERVER

85

CISCO_VIDEO_CONFERENCE_BRIDGE

90

ROUTE_LIST

100

LOAD_SIMULATOR

110

MEDIA_TERMINATION_POINT

111

MEDIA_TERMINATION_POINT_HARDWARE

112

MEDIA_TERMINATION_POINT_HDV2

113

MEDIA_TERMINATION_POINT_WS-SVC-CMM

120

MGCP_STATION

121

MGCP_TRUNK

122

GATEKEEPER

124

7914_14_BUTTON_LINE_EXPANSION_MODULE

125

TRUNK

126

TONE_ANNOUNCEMENT_PLAYER

131

SIP_TRUNK

132

SIP_GATEWAY

133

WSM_TRUNK

134

REMOTE_DESTINATION_PROFILE

227

7915_12_BUTTON_LINE_EXPANSION_MODULE

228

7915_24_BUTTON_LINE_EXPANSION_MODULE

229

7916_12_BUTTON_LINE_EXPANSION_MODULE

230

7916_24_BUTTON_LINE_EXPANSION_MODULE

232

CKEM_36_BUTTON_LINE_EXPANSION_MODULE

254

UNKNOWN_MGCP_GATEWAY

255

UNKNOWN

30027

ANALOG_PHONE

30028

ISDN_BRI_PHONE

30032

SCCP_GATEWAY_VIRTUAL_PHONE


Recommended Action

None

DeviceRestartInitiated

Device restart initiated or Apply Config initiated on the specified device.

This alarm occurs when a device is restarted via the Restart button in Cisco Unified CM Administration window or when a system administrator presses the Apply Config button for a device that does not support conditional restart. Restart causes the device to unregister, receive updated configuration, and re-register with Cisco Unified Communications Manager (Unified CM) without shutting down. A device can be restarted only when it is registered with Unified CM.

History

Cisco Unified Communications
Release
Action

8.0(1)

Enum Definitions for DeviceType are updated.

Parameters added: Product type [String]


Alarm Catalog—CallManager/CallManager

Severity—Informational

Parameters

Device name [Optional]. [String] Device type. [Optional] [Enum] Product type [String]

Enum Definitions for DeviceType

Code
Device Type

10

CISCO_VGC_PHONE

11

CISCO_VGC_VIRTUAL_PHONE

30

ANALOG_ACCESS

40

DIGITAL_ACCESS

42

DIGITAL_ACCESS+

43

DIGITAL_ACCESS_WS-X6608

47

ANALOG_ACCESS_WS-X6624

48

VGC_GATEWAY

50

CONFERENCE_BRIDGE

51

CONFERENCE_BRIDGE_HARDWARE

52

CONFERENCE_BRIDGE_HARDWARE_HDV2

53

CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM

62

H323_GATEWAY

70

MUSIC_ON_HOLD

71

DEVICE_PILOT

73

CTI_ROUTE_POINT

80

VOICE_MAIL_PORT

83

SOFTWARE_MEDIA_TERMINATION_POINT_HDV2

84

CISCO_MEDIA_SERVER

85

CISCO_VIDEO_CONFERENCE_BRIDGE

90

ROUTE_LIST

100

LOAD_SIMULATOR

110

MEDIA_TERMINATION_POINT

111

MEDIA_TERMINATION_POINT_HARDWARE

112

MEDIA_TERMINATION_POINT_HDV2

113

MEDIA_TERMINATION_POINT_WS-SVC-CMM

120

MGCP_STATION

121

MGCP_TRUNK

122

GATEKEEPER

124

7914_14_BUTTON_LINE_EXPANSION_MODULE

125

TRUNK

126

TONE_ANNOUNCEMENT_PLAYER

131

SIP_TRUNK

132

SIP_GATEWAY

133

WSM_TRUNK

134

REMOTE_DESTINATION_PROFILE

227

7915_12_BUTTON_LINE_EXPANSION_MODULE

228

7915_24_BUTTON_LINE_EXPANSION_MODULE

229

7916_12_BUTTON_LINE_EXPANSION_MODULE

230

7916_24_BUTTON_LINE_EXPANSION_MODULE

232

CKEM_36_BUTTON_LINE_EXPANSION_MODULE

254

UNKNOWN_MGCP_GATEWAY

255

UNKNOWN

30027

ANALOG_PHONE

30028

ISDN_BRI_PHONE

30032

SCCP_GATEWAY_VIRTUAL_PHONE


Recommended Action

None

DeviceTransientConnection

A connection was established and immediately dropped before completing registration. Incomplete registration may indicate that a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. Network connectivity problems can affect device registration, or the restoration of a primary Unified CM may interrupt registration.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Following information is updated:

Enum Definitions for DeviceType

Enum Definitions

Enum Definitions for IPAddrAttributes

Enum Definitions for IPV6AddrAttributes


Alarm Catalog—CallManager/CallManager

Severity—Warning.

Enum Definitions for DeviceType

Code
Reason

10

CISCO_VGC_PHONE

11

CISCO_VGC_VIRTUAL_PHONE

30

ANALOG_ACCESS

40

DIGITAL_ACCESS

42

DIGITAL_ACCESS+

43

DIGITAL_ACCESS_WS-X6608

47

ANALOG_ACCESS_WS-X6624

48

VGC_GATEWAY

50

CONFERENCE_BRIDGE

51

CONFERENCE_BRIDGE_HARDWARE

52

CONFERENCE_BRIDGE_HARDWARE_HDV2

53

CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM

62

H323_GATEWAY

70

MUSIC_ON_HOLD

71

DEVICE_PILOT

73

CTI_ROUTE_POINT

80

VOICE_MAIL_PORT

83

SOFTWARE_MEDIA_TERMINATION_POINT_HDV2

84

CISCO_MEDIA_SERVER

85

CISCO_VIDEO_CONFERENCE_BRIDGE

90

ROUTE_LIST

100

LOAD_SIMULATOR

110

MEDIA_TERMINATION_POINT

111

MEDIA_TERMINATION_POINT_HARDWARE

112

MEDIA_TERMINATION_POINT_HDV2

113

MEDIA_TERMINATION_POINT_WS-SVC-CMM

120

MGCP_STATION

121

MGCP_TRUNK

122

GATEKEEPER

124

7914_14_BUTTON_LINE_EXPANSION_MODULE

125

TRUNK

126

TONE_ANNOUNCEMENT_PLAYER

131

SIP_TRUNK

132

SIP_GATEWAY

133

WSM_TRUNK

134

REMOTE_DESTINATION_PROFILE

227

7915_12_BUTTON_LINE_EXPANSION_MODULE

228

7915_24_BUTTON_LINE_EXPANSION_MODULE

229

7916_12_BUTTON_LINE_EXPANSION_MODULE

230

7916_24_BUTTON_LINE_EXPANSION_MODULE

232

CKEM_36_BUTTON_LINE_EXPANSION_MODULE

254

UNKNOWN_MGCP_GATEWAY

255

UNKNOWN

30027

ANALOG_PHONE

30028

ISDN_BRI_PHONE

30032

SCCP_GATEWAY_VIRTUAL_PHONE


Enum Definitions

Code
Reason

1

Unknown—(SCCP only) The device failed to register for an unknown reason. If this persists, collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact TAC.

2

NoEntryInDatabase—(MGCP only) The device is not configured in the Unified CM Administration database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Unified CM Administration.

3

DatabaseConfigurationError—The device is not configured in the Unified CM Administration database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Unified CM Administration.

4

DeviceNameUnresolveable—For SIP third-party devices this means that Unified CM could not determine the name of the device from the Authorization header in the REGISTER message. The device did not provide an Authorization header after Unified CM challenged with a 401 Unauthorized message. Verify that the device is configured with digest credentials and is able to respond to 401challenges with an Authorization header. If this is a Cisco IP phone, the configuration may be out-of-sync. First, go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify "all servers have a good replication status". If DB replications looks good, reset the phone. If that still doesn't fix the problem, restart the TFTP and the Cisco CallManager services. For all other devices, this reason code means that DNS lookup failed. Verify the DNS server configured via the OS Administration CLI is correct and that the DNS name used by the device is configured in the DNS server.

6

ConnectivityError—The network connection between the device and Cisco Unified CM dropped before the device was fully registered. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops and packet corruption. It is also possible to get this error if the Cisco Unified CM node is experiencing high CPU usage. Verify the device is powered up and operating, verify network connectivity between the device and Cisco Unified CM, and verify the CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging Alert).

7

InitializationError—An internal error occurred within Cisco Unified CM while processing the device registration. It is recommended to restart the Cisco CallManager service. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact TAC.

10

AuthenticationError—The device failed either TLS or SIP digest security authentication. If the device is a SIP phone and is enabled for digest authentication (on the System > Security Profile > Phone Security Profile, check if "Enable Digest Authentication" checkbox is checked), verify the "Digest Credentials" in the End User config page are configured. Also, check the phone config page to see if the phone is associated with the specified end user in the Digest User drop box. If the device is a third-party SIP device, verify the digest credentials configured on the phone match the "Digest Credentials" configured in the End User page.

11

InvalidX509NameInCertificate—Configured "X.509 Subject Name" doesn't match what's in the certificate from the device. Check the Security profile of the indicated device and verify the "Device Security Mode" is either "Authenticated" or "Encrypted". Verify the "X.509 Subject Name" field has the right content. It should match the Subject Name in the certificate from the peer.

12

InvalidTLSCipher—Unsupported cipher algorithm used by the device; Cisco Unified CM only supports AES_128_SHA cipher algorithm. Recommended action is for the device to regenerate its certificate with the AES_128_SHA cipher algorithm.

14

MalformedRegisterMsg—(SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, and an expires value too small. Verify the REGISTER message does not suffer from any of these ills.

15

ProtocolMismatch—The protocol of the device (SIP or SCCP) does not match the configured protocol in Cisco Unified CM. Recommended actions: 1) Verify the device is configured with the desired protocol; 2) Verify the firmware load ID on the Device Defaults page is correct and actually exists on the TFTP server; 3) If there is a firmware load ID configured on the device page, verify it is correct and exists on the TFTP server (On Cisco Unified OS Administration page, Software Upgrades > TFTP File Management, look for the file name as specified by load ID); 4) Restart the TFTP and Cisco CallManager services. Use the Cisco Unified OS Administration TFTP File Management page to verify the configured firmware loads exist.

16

DeviceNotActive—The device has not been activated

17

AuthenticatedDeviceAlreadyExists—A device with the same name is already registered. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact TAC. There may be an attempt by unauthorized devices to register.

18

ObsoleteProtocolVersion—(SCCP only) A SCCP device registered with an obsolete protocol version. Power cycle the phone. Verify that the TFTP service is activated. Verify that the TFTP server is reachable from the device. If there is a firmware load ID configured on the Phone Config page, verify that the firmware load ID exists on the TFTP server (On Cisco Unified OS Administration page, Software Upgrades > TFTP File Management, look for the file name as specified by load ID).


Enum Definitions for IPAddrAttributes

Code
Reason

0

Unknown—The device has not indicated what this IPv4 address is used for.

1

Administrative only—The device has indicated that this IPv4 address is used for administrative communication (web interface) only.

2

Signal only—The device has indicated that this IPv4 address is used for control signaling only.

3

Administrative and signal—The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling.


Enum Definitions for IPV6AddrAttributes

Code
Reason

0

Unknown—The device has not indicated what this IPv6 address is used for.

1

Administrative only—The device has indicated that this IPv6 address is used for administrative communication (web interface) only.

2

Signal only—The device has indicated that this IPv6 address is used for control signaling only.

3

Administrative and signal—The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling.


Recommended Action

In the Cisco Unified Reporting tool, check the Active Services section of the Unified CM Cluster Overview report to confirm that any failover/fallback scenarios have completed. Confirm that auto-registration is enabled if the phone attempting to connect is set to auto-register, or locate the phone that is attempting to auto-register if auto-registration has been intentionally disabled. Check the device indicated in this alarm and confirm that the device registration details in Cisco Unified CM Administration are accurate. Also, refer to the reason code definitions for recommended actions. No action is required if this event was issued as a result of a normal device rehome.

DeviceTypeMismatch

Device type mismatch between the information contained in the device's TFTP config file and what is configured in the database for that device.

The device type indicated in the device's configuration file does not match the database configuration. This could indicate that a change was made in the database configuration that failed to get updated at the device itself.

History

Cisco Unified Communications
Release
Action

8.0(1)

Following information is updated:

Enum Definitions for DBDeviceType

Enum Definitions for DeviceType


Alarm Catalog—CallManager/CallManager

Severity—Error

Enum Definitions for DBDeviceType

Code
Device Type

1

CISCO_30SP+

2

CISCO_12SP+

3

CISCO_12SP

4

CISCO_12S

5

CISCO_30VIP

6

CISCO_7910

7

CISCO_7960

8

CISCO_7940

9

CISCO_7935

12

CISCO_ATA_186

20

SCCP_PHONE

61

H323_PHONE

72

CTI_PORT

115

CISCO_7941

119

CISCO_7971

255

UNKNOWN

302

CISCO_7989

307

CISCO_7911

308

CISCO_7941G_GE

309

CISCO_7961G_GE

335

MOTOROLA_CN622

336

BASIC_3RD_PARTY_SIP_DEVICE

348

CISCO_7931

358

CISCO_UNIFIED_COMMUNICATOR

365

CISCO_7921

369

CISCO_7906

374

ADVANCED_3RD_PARTY_SIP_DEVICE

375

CISCO_TELEPRESENCE

404

CISCO_7962

412

CISCO_3951

431

CISCO_7937

434

CISCO_7942

435

CISCO_7945

436

CISCO_7965

437

CISCO_7975

446

CISCO_3911

468

CISCO_UNIFIED_MOBILE_COMMUNICATOR

478

CISCO_TELEPRESENCE_1000

479

CISCO_TELEPRESENCE_3000

480

CISCO_TELEPRESENCE_3200

481

CISCO_TELEPRESENCE_500

484

CISCO_7925

493

CISCO_9971

495

CISCO_6921

496

CISCO_6941

497

CISCO_6961

20000

CISCO_7905

30002

CISCO_7920

30006

CISCO_7970

30007

CISCO_7912

30008

CISCO_7902

30016

CISCO_IP_COMMUNICATOR

30018

CISCO_7961

30019

CISCO_7936

30035

IP_STE


Enum Definitions for DeviceType

Code
Device Type

1

CISCO_30SP+

2

CISCO_12SP+

3

CISCO_12SP

4

CISCO_12S

5

CISCO_30VIP

6

CISCO_7910

7

CISCO_7960

8

CISCO_7940

9

CISCO_7935

12

CISCO_ATA_186

20

SCCP_PHONE

61

H323_PHONE

72

CTI_PORT

115

CISCO_7941

119

CISCO_7971

255

UNKNOWN

302

CISCO_7989

307

CISCO_7911

308

CISCO_7941G_GE

309

CISCO_7961G_GE

335

MOTOROLA_CN622

336

BASIC_3RD_PARTY_SIP_DEVICE

348

CISCO_7931

358

CISCO_UNIFIED_COMMUNICATOR

365

CISCO_7921

369

CISCO_7906

374

ADVANCED_3RD_PARTY_SIP_DEVICE

375

CISCO_TELEPRESENCE

404

CISCO_7962

412

CISCO_3951

431

CISCO_7937

434

CISCO_7942

435

CISCO_7945

436

CISCO_7965

437

CISCO_7975

446

CISCO_3911

468

CISCO_UNIFIED_MOBILE_COMMUNICATOR

478

CISCO_TELEPRESENCE_1000

479

CISCO_TELEPRESENCE_3000

480

CISCO_TELEPRESENCE_3200

481

CISCO_TELEPRESENCE_500

484

CISCO_7925

493

CISCO_9971

495

CISCO_6921

496

CISCO_6941

497

CISCO_6961

20000

CISCO_7905

30002

CISCO_7920

30006

CISCO_7970

30007

CISCO_7912

30008

CISCO_7902

30016

CISCO_IP_COMMUNICATOR

30018

CISCO_7961

30019

CISCO_7936

30035

IP_STE


Recommended Action

Check the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is working. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. Restart the phone to download a new configuration file from TFTP. Also, refer to the reason code definitions for additional recommended actions.

DeviceUnregistered

A device that has previously registered with Cisco CallManager has unregistered. In cases of normal unregistration with reason code 'CallManagerReset', 'CallManagerRestart', or 'DeviceInitiatedReset', the severity of this alarm is lowered to INFORMATIONAL. A device can unregister for many reasons, both intentional, such as manually resetting the device after a configuration change, or unintentional, such as loss of network connectivity. Other causes for this alarm could include a phone being registered to a secondary node and then the primary node come back online, causing the phone to rehome to the primary Unified CM node or lack of a KeepAlive being returned from the Unified CM node to which this device was registered. Unregistration also occurs if Unified CM receives a duplicate registration request for this same device.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Following information is updated:

Enum Definitions for DeviceType

Enum Definition

Enum Definitions for IPAddrAttributes

Enum Definitions for IPV6AddrAttributes


Alarm Catalog—CallManager/CallManager

Severity—Severity changed from Error to Warning.

Enum Definitions for DeviceType

Code
Device Type

10

CISCO_VGC_PHONE

11

CISCO_VGC_VIRTUAL_PHONE

30

ANALOG_ACCESS

40

DIGITAL_ACCESS

42

DIGITAL_ACCESS+

43

DIGITAL_ACCESS_WS-X6608

47

ANALOG_ACCESS_WS-X6624

48

VGC_GATEWAY

50

CONFERENCE_BRIDGE

51

CONFERENCE_BRIDGE_HARDWARE

52

CONFERENCE_BRIDGE_HARDWARE_HDV2

53

CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM

62

H323_GATEWAY

70

MUSIC_ON_HOLD

71

DEVICE_PILOT

73

CTI_ROUTE_POINT

80

VOICE_MAIL_PORT

83

SOFTWARE_MEDIA_TERMINATION_POINT_HDV2

84

CISCO_MEDIA_SERVER

85

CISCO_VIDEO_CONFERENCE_BRIDGE

90

ROUTE_LIST

100

LOAD_SIMULATOR

110

MEDIA_TERMINATION_POINT

111

MEDIA_TERMINATION_POINT_HARDWARE

112

MEDIA_TERMINATION_POINT_HDV2

113

MEDIA_TERMINATION_POINT_WS-SVC-CMM

120

MGCP_STATION

121

MGCP_TRUNK

122

GATEKEEPER

124

7914_14_BUTTON_LINE_EXPANSION_MODULE

125

TRUNK

126

TONE_ANNOUNCEMENT_PLAYER

131

SIP_TRUNK

132

SIP_GATEWAY

133

WSM_TRUNK

134

REMOTE_DESTINATION_PROFILE

227

7915_12_BUTTON_LINE_EXPANSION_MODULE

228

7915_24_BUTTON_LINE_EXPANSION_MODULE

229

7916_12_BUTTON_LINE_EXPANSION_MODULE

230

7916_24_BUTTON_LINE_EXPANSION_MODULE

232

CKEM_36_BUTTON_LINE_EXPANSION_MODULE

254

UNKNOWN_MGCP_GATEWAY

255

UNKNOWN

30027

ANALOG_PHONE

30028

ISDN_BRI_PHONE

30032

SCCP_GATEWAY_VIRTUAL_PHONE


Enum Definition

Code
Reason

1

Unknown - The device has unregistered for an unknown reason. If the device does not re-register within 5 minutes, verify it is powered-up and verify network connectivity between the device and Cisco Unified CM.

6

ConnectivityError - Network communication between the device and Cisco Unified CM has been interrupted. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops and packet corruption. It is also possible to get this error if the Cisco Unified CM node is experiencing high CPU usage. Verify the device is powered up and operating, verify network connectivity between the device and Cisco Unified CM, and verify the CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging Alert).

8

DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action required; the device will re-register automatically.

9

CallManagerReset - A device reset was initiated from Cisco Unified CM Administration, either due to an explicit command from an administrator, or due to internal errors encountered. No action necessary, the device will re-register automatically.

10

DeviceUnregistered - The device has explicitly unregistered. Possible causes include a change in the IP address or port of the device. No action is necessary, the device will re-register automatically.

11

MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, and an expires value too small. Verify the REGISTER message does not suffer from any of these ills.

12

SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage.

13

KeepAliveTimeout - A keepalive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops and packet corruption. It is also possible to get this error if the Cisco Unified CM node is experiencing high CPU usage. Verify the device is powered up and operating, verify network connectivity between the device and Cisco Unified CM, and verify the CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging Alert).

14

ConfigurationMismatch (SIP only) The configuration on the device does not match the configuration in Cisco Unified CM. This can be caused by database replication errors or other internal Cisco Unified CM communication errors. First go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify "all servers have a good replication status". If this device continues to unregister with this reason code, go to the CCMAdmin Device web page for the device and click Save. This allows a change notify to be generated to the Unified CM and TFTP services and rebuild a new config file. If the problem still persists, restart the TFTP service and Cisco Unified CM service.

15

CallManagerRestart - A device restart was initiated from Cisco Unified CM, either due to an explicit command from an administrator, or due to a configuration change such as adding, deleting or changing a DN associated with the device. No action necessary, the device will re-register automatically.

16

DuplicateRegistration - Cisco Unified CM detected that the device attempted to register to 2 nodes at the same time. Cisco Unified CM initiated a restart to the phone to force it to re-home to a single node. No action necessary, the device will re-register automatically.

17

CallManagerApplyConfig - An ApplyConfig command was invoked from Unified CM Administration resulting in an unregistration. No action necessary, the device will re-register automatically.

18

DeviceNoResponse - The device did not respond to a reset or restart notification, so it is being forcefully reset. If the device does not re-register within 5 minutes, confirm it is powered-up and confirm network connectivity between the device and Cisco Unified CM.


Enum Definitions for IPAddrAttributes

Code
Reason

0

Unknown—The device has not indicated what this IPv4 address is used for.

1

Administrative only—The device has indicated that this IPv4 address is used for administrative communication (web interface) only.

2

Signal only—The device has indicated that this IPv4 address is used for control signaling only.

3

Administrative and signal—The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling.


Enum Definitions for IPV6AddrAttributes

Code
Reason

0

Unknown - The device has not indicated what this IPv6 address is used for

1

Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only.

2

Signal only - The device has indicated that this IPv6 address is used for control signaling only.

3

Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling.


Recommended Action

Actions to take vary depending on the reason specified for the device unregistration. If the reason is ConfigurationMismatch, go to the Device Configuration page in Cisco Unified CM Administration, make a change to the Description field for this device, click Save, then reset the device. In the case of a network connectivity or loss of KeepAlives problem, use network diagnostic tools and the Cisco Unified CM Reporting tool to fix any reported network or Unified CM system errors. In the case of a device rehoming to the primary Unified CM node, watch for a successful registration of the device on the primary node. In the case of a duplicate registration request, it may be a non-malicious occurrence due to timing of a device registering and unregistering; if duplicate registration requests continue or if the same device has different IP addresses, confirm the IP address on the physical device itself by checking the settings on the device (settings button). If unregistration of this device was expected, no action is required. Also, refer to the reason code descriptions for recommended actions.

EndThrottlingCallListBLFSubscriptions

CallManager has resumed accepting CallList BLF Subscriptions subsequent to prior throttling.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Warning to Informational.


Alarm Catalog—CallManager/CallManager

Severity—Informational

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.

H323Started

Cisco CallManager is ready to handle calls for the indicated H323 device. Cisco Unified Communications Manager is ready to communicate with the indicated H.323 device. Note that this alarm describes the readiness of Unified CM to communicate with the indicated device, but does not provide information about the state of the H.323 device (whether it is ready to communicate as well).

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Notice.

Following information updated:

Parameters

Enum Definitions for DeviceType


Alarm Catalog—CallManager/CallManager

Severity—Notice

Parameters

Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description [Optional]. [String] The Server 1 IP Address/Host Name as configured in the Trunk Configuration window [String] Remote CallManager Server 2[Optional]. [String] Remote CallManager Server 3[Optional]. [String]

Enum Definitions for DeviceType

Code
Device Type

61

H323_PHONE

62

H323_GATEWAY

122

GATEKEEPER

125

TRUNK


Recommended Action

None

H323Stopped

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

Cisco Unified Communications Manager (Unified CM) is not ready to handle calls for the indicated H.323 device. This could be due to Unified CM being unable to resolve the gateway name to IP address. For trunks, this alarm should only occur when a system administrator has made a configuration change such as resetting the H.323 trunk. For H.323 clients, this alarm occurrence is normal on lower-priority Unified CM nodes when a high-priority Unified CM node starts.

History

Cisco Unified Communications
Release
Action

8.0(1)

Following information updated:

Parameters

Enum Definitions for DeviceType


Alarm Catalog—CallManager/CallManager

Severity—Warning

Parameters

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]

Enum Definitions for DeviceType

Code
Device Type

61

H323_PHONE

62

H323_GATEWAY

122

GATEKEEPER

125

TRUNK


Recommended Action

If the service was stopped intentionally, no action is required. Check the domain name system (DNS) configuration for any errors in the gateway name or IP address and correct.

ICTCallThrottlingEnd

Cisco CallManager starts handling calls for the indicated H323 device. Cisco CallManager has ceased throttling calls on the indicated H.323 device.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Notice.


Alarm Catalog—CallManager/CallManager

Severity—Notice

Recommended Action

None.

ICTCallThrottlingStart

Cisco CallManager stops handling calls for the indicated H.323 device due to heavy traffic or a route loop over the H.323 trunk.

Cisco Unified Communications Manager has detected a route loop over the H.323 trunk indicated in this alarm. As a result, Unified CM has temporarily stopped accepting calls for the indicated H.323 trunk. It's also possible that a high volume of calls are occurring over the intercluster trunk, which has triggered throttling.

Alarm Catalog—CallManager/CallManager

Severity—Error (3)

Recommended Action

In Real-Time Monitoring Tool, check the CallsActive and CallsInProgress counters for unusual activity on the indicated H.323 trunk. If the CallsActive count is significantly higher than usual, a traffic load issue may be occurring where the demand to send calls over the trunk is greater than the trunk's capacity. Monitor the situation and collect existing trace files. If the ICTCallThrottlingEnd alarm is not issued in a reasonable amount of time as deemed by your organization, contact TAC and supply the trace information you have collected. For a routing loop condition, the CallsInProgress counter will be significantly higher than usual. By examining trace files and CDR data for calls that occurred over the indicated trunk, you may be able to detect a translation pattern, route list or other routing mechanism that is part of the loop. Update the routing mechanism that resulted in the loop (generally the same number is configured on both near end and far end devices) and then reset the affected route list in an attempt to clear the route loop and if that fails, reset the affected trunk.

MGCPGatewayGainedComm

The MGCP gateway has established communication with Cisco Unified Communications Manager.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Notice.


Alarm Catalog—CallManager/CallManager

Severity—Notice

Recommended Action

Informational purposes only; no action is required.

MaliciousCall

Malicious Call Identification feature is invoked in Cisco CallManager.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Warning.


Alarm Catalog—CallManager/CallManager

Severity—Warning

Recommended Action

Informational purposes only; no action is required.

MaxCallDurationTimeout

An active call was cleared because the amount of time specified in the Maximum Call Duration Timer service parameter had elapsed. If the allowed call duration is too short, you can increase the value. If you do not want a limit on the duration of an active call, you can disable the limit. If the duration is correct but you did not expect a call to ever exceed that duration, check the trace information around the time that this alarm occurred to try to determine if a gateway port had failed to release a call.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Notice.

Following parameters added:

Originating Device name(String)

Destination Device name(String)

Call start time(UInt)

Call stop time(UInt)

Calling Party Number(String)

Called Party Number(String)


Alarm Catalog—CallManager/CallManager

Severity—Notice

Recommended Action

If the duration of the call is too short, increase the value in the Cisco CallManager service parameter or disable the maximum duration by setting the Maximum Call Duration Timer parameter to zero. If you suspect a hung gateway port, check the trace files around the time that this alarm occurred to search for the gateway that was involved in the call, then check the status of that gateway to determine if all ports are functioning normally.

MaxCallsReached

The maximum number of simultaneous connections in a Cisco Unified Communications Manager (Unified CM) node has been reached. This is an internally-set value and when it is exceeded, Unified CM starts throttling calls to keep the number of calls below the internal threshold.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Critical.


Alarm Catalog—CallManager/CallManager

Severity—Critical

Recommended Action

In the Real-Time Monitoring Tool, check the CallsActive counter in the Cisco CallManager object for an unusually high number of calls. Internal mechanisms will attempt to correct this condition. If this alarm continues to occur, collect existing SDL and CCM trace files and check to be sure that CM Services trace collection in Cisco Unified CM Serviceability is set to Detailed level.

MaxHoldDurationTimeout

A held call was cleared because the amount of time specified in the Maximum Hold Duration Timer service parameter had elapsed. If the allowed call-on-hold duration is too short, you can increase the value. If you do not want a limit on the duration of a held call, you can disable the limit.

History

Cisco Unified Communications
Release
Action

8.0(1)

Following parameters added:

Originating Device Name(String)

Destination Device Name(String)

Hold start time(UInt)

Hold stop time(UInt)

Calling Party Number(String)

Called Party Number(String)


Alarm Catalog—CallManager/CallManager

Severity—Informational

Recommended Action

If the duration of the hold time is too short, increase the value in the Cisco CallManager service parameter or disable the maximum duration by setting the Maximum Hold Duration Timer parameter to zero.

MediaResourceListExhausted

The requested device type is not found in the media resource list or default list or the configured devices are not registered.

The requested device is not configured in the Media Resource Group List or Default List, or it's possible that one or more of the devices that are configured in the Media Resource Group List or Default List are not registered to Cisco Unified Communications Manager.

Cisco Unified Communications
Release
Action

8.0(1)

Enum Definitions for MediaResourceType is updated.


Alarm Catalog—CallManager/CallManager

Severity—Warning

Enum Definitions for MediaResourceType

Code
Definition

1

MediaTerminationPoint

2

Transcoder

3

ConferenceBridge

9

RSVP Agent


Recommended Action

First, go to Cisco Unified CM Administration to check the configuration of the devices that are part of the Media Resource Groups in the Media Resource Group List that was specified in the alarm (Media Resource Group List Configuration window and Media Resource Group Configuration window in Unified CM Administration).

Check whether the requested type of device is configured in any of the Media Resource Groups in that particular Media Resource Group List in Cisco Unified CM Administration; for RSVP Agent, check whether any media termination point or transcoder is configured in any of the Media Resource Groups in that particular Media Resource Group List. Next, go to the Media Resources menu in Cisco Unified CM Administration to see all the devices of the requested type and then check all the Media Resource Groups (irrespective of whether they belong to the Media Resource Group List for which the alarm is generated) to see whether the devices belong to at least one Media Resource Group.

MohNoMoreResourcesAvailable

No more MOH resources available.

This alarm occurs when allocation of Music On Hold fails for all the registered MOH servers belonging to the Media Resource Group List and Default List. Each MOH server may fail for different reasons. Following are some of the reasons that could cause an MOH server allocation to fail: All the resources of MOH server are already in use; No matching codecs or capability mismatch between the held party and MOH server; Not enough bandwidth between the held party and MOH source; No audio stream available for the MOH server.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/CallManager

Severity—Warning

Recommended Action

If all the resources of the MOH servers are already in use, check to be sure that all the MOH servers that belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are configured and registered in all the applicable Unified CM nodes. To check the registration status go to the Media Resources > Music On Hold Server menu and click the Find button. It will display all the MOH servers with their status, device pool, and so on.

Check the status field to discover whether it is registered with Unified CM. Note that the display on the status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified CM cluster that the Publisher can only write to the Unified CM database and the Publisher goes down. Because the Subscriber may not be able to write to the database, the devices may still display as registered in Unified CM Administration after they are actually unregistered. However, if the Publisher is down that should generate another alarm with higher priority than this alarm.

The MOH allocation can also fail due to codec mismatch or capability mismatch between the endpoint and the MOH server. If there is a codec mismatch or capability mismatch (such as the endpoint using IPv6 addressing but MOH server supporting only IPv4), an MTP or transcoder should be allocated. If the MTP or transcoder is not allocated then either MediaResourceListExhausted (with Media Resource Type as Media termination point or transcoder) or MtpNoMoreResourcesAvailable alarm will be generated for the same Media Resource Group List and you should first concentrate on that alarm.

The MOH allocation may even fail after checking the region bandwidth between the regions to which the held party belongs and the region to which the MOH server belongs. Increasing the region bandwidth may be a solution to the problem, but that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions.

You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, the average number of calls using the MOH servers, approximate bandwidth use per call, and so on, and accordingly calculate the region bandwidth. Another possible cause is that the bandwidth needed for the call may not be available. This can occur if the MOH server and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls.

Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, please note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations.

Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth. Another reason for the MOH allocation failure may be due to meeting the maximum number of unicast or multicast streams supported by the MOH server.

If all available streams are already in use, none can be allocated. Finally, check the Music On Hold Audio Source Configuration window in Cisco Unified CM Administration to confirm that at least one audio source is configured. If an audio source is not configured, upload an audio file and then configure the audio source in Cisco Unified CM Administration (refer to the Music On Hold configuration documentation for specific details).

MtpNoMoreResourcesAvailable

Media termination point or transcoder allocation failed.

The alarm occurs when allocation of a media termination point (MTP) or transcoder fails for all the registered MTPs or transcoders belonging to the Media Resource Group List and Default List. Each MTP or transcoder may fail for different reasons. Following are some of the reasons that could cause an MTP or transcoder allocation to fail: a capability mismatch between the device endpoint and MTP/transcoder, codec mismatch between the endpoint and the MTP/transcoder; a lack of available bandwidth between the endpoint and the MTP/transcoder; or because the MTP/transcoders resources are already in use.

A capability mismatch may be due to the MTP/transcoder not supporting one or more of the required capabilities for the call such as Transfer Relay Point (which is needed for QoS or firewall traversal), RFC 2833 DTMF (which is necessary when one side of the call does not support RFC 2833 format for transmitting DTMF digits and the other side must receive the DTMF digits in RFC2833 format, resulting in conversion of the DTMF digits), RFC 2833 DTMF passthrough (in this case, the MTP or transcoder does not need to convert the DTMF digits from one format to another format but it needs to receive DTMF digits from one endpoint and transmit them to the other endpoint without performing any modifications), passthrough (where no codec conversion will occur, meaning the media device will receive media streams in any codec format and transmit them to the other side without performing any codec conversion), IPv4 to IPv6 conversion (when one side of the call supports only IPv4 and the other side of the call supports only IPv6 and so an MTP needs to be inserted to perform the necessary conversion between IPv4 and IPv6 packets), or multimedia capability (if a call involving video and/or data in addition to audio requires insertion of an MTP or transcoder then the MTP/transcoder which supports multimedia will be inserted).

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Media Resource List Name parameter added.


Alarm Catalog—CallManager/CallManager

Severity—Warning.

Recommended Action

If the MTP or transcoder allocation is failing due to a capability mismatch, it's possible that the media device does not support the capability (such as IPv4 to IPv6 conversion, passthrough) or the capability might not be configured in the device. Please check the user guide and documentation of the media device to make sure that device supports all the necessary capabilities. Also, caution should be taken care if all the MTP or transcoders are configured with all the supported capabilities.

There are certain capabilities (such as RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough) which could be supported by most of the MTPs or transcoders and there may be certain capabilities (such as IPv4 to IPv6 conversion and vice versa or Transfer Relay Point or multimedia capability) which can be supported by only by a single MTP or transcoder depending on the devices that you have. For example, you may have IP phones that support only IPv4 protocol and there may also be IP phones that support only IPv6 protocol.

MultipleSIPTrunksToSamePeerAndLocalPort

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.

Alarm Catalog—CallManager/CallManager

Severity—Error.

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.

NoFeatureLicense

No feature license found. Cisco Unified Communications Manager (Unified CM) requires a license to function. Also, Unified CM licenses are version-specific so be certain that the license is for the version you are trying to run. You can run a license unit report in Cisco Unified CM Administration (System > Licensing > License Unit Report).

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Emergency.


Alarm Catalog—CallManager/CallManager

Severity—Emergency

Recommended Action

Request license generation for Cisco Unified Communications Manager SW FEATURE for your version of Unified CM and upload the license in Cisco Unified CM Administration (System > Licensing > License File Upload).

NotEnoughChans

Call attempt was rejected because requested gateway channel(s) could not be allocated. Some of the more common reasons for the lack of channel to place outgoing calls include: High call traffic volume that has the B-channels in the device fully utilized; B-channels have gone out of service for the following reasons: Taking the channel out of service intentionally to perform maintenance on either the near- or far-end; MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Cisco Unified Communications Manager; MGCP gateway doesn't respond to an MGCP command sent by Unified CM three times; a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Device Name(String) is the only parameter


Alarm Catalog—CallManager/CallManager

Severity—Warning

Parameters

Device Name(String)

Recommended Action

Add more gateway resources; Check the Unified CM advanced service parameter, Change B-channel Maintenance Status to determine if the B-channel has been taken out of service intentionally; Check the Q.931 trace for PRI SERVICE message to determine whether a PSTN provider has taken the B-channel out of service; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.

NumDevRegExceeded

The allowed number of registered devices was exceeded.

Alarm Catalog—CallManager/CallManager

Severity—Error (3)

Recommended Action

If you did not expect to exceed the number of devices and you have auto-registration enabled, go to Device > Phones in Cisco Unified CM Administration and search for phones starting with "auto". If you see any unexpected devices which may not belong in the system (such as intruder devices) locate that device using it's IP address and remove it from the system. Or, if your licenses and system resources allow, increase the value in the Cisco CallManager service parameter, Maximum Number of Registered Devices.

PktCapOnDeviceStarted

Packet capture started on the device. Indicated packet capture has been enabled on the device.

Alarm Catalog—CallManager/CallManager

Severity—Informational (6)

Recommended Action

None

PktCapOnDeviceStopped

Packet capture stopped on the device. Indicated packet capture has been disabled on the device.

Alarm Catalog—CallManager/CallManager

Severity—Informational (6)

Recommended Action

None

PktCapServiceStarted

Packet capture service started. Packet capture feature has been enabled on the Cisco Unified Communications Manager server. A Cisco CallManager service parameter, Packet Capture Enable, must be set to True for packet capture to occur.

Alarm Catalog—CallManager/CallManager

Severity—Informational (6)

Recommended Action

None

PktCapServiceStopped

Packet capture service stopped. The packet capture feature has been disabled on the Cisco Unified Communications Manager server.

Alarm Catalog—CallManager/CallManager

Severity—Informational (6)

Recommended Action

None

RouteListExhausted

An available route could not be found in the indicated route list.

1. This alarm is generated when all member are not available or not idle; this condition existed when the member is down (out of service), not registered, or busy.

2. For share line when some phones are not ringing, check the busy trigger and maximal call settings of share line phones; check whether there are some outstanding calls on that DN.

3. When one share line phones answers an incoming call, the other share line phone cannot see that remote-in-use call; check the privacy setting of the phone which answers the call.

4. To verify user can try to make call directly to the member by passing the route list, and see if the call can goes through.

5. Check SDI trace for cause code which may provide reason for this alarm.

Alarm Catalog—CallManager/CallManager

Severity—Warning.

Recommended Action

Consider adding additional routes in the indicated route list. For shared line when some phones are not ringing, check the busy trigger and maximum call settings of shared line phones; check whether there are some outstanding calls on that DN.

When one shared line phone answers an incoming call, the other shared line phone cannot see that remote-in-use call; check the privacy setting of the phone that answers the call.

Try to make a call directly to the member, bypassing the route list, to verify that there is not a device or connectivity issue. If you cannot identify the cause through these steps, gather the CCM (SDI) trace and contact the Cisco Technical Assistance Center; TAC may be able to locate a cause code which may provide additional explanation for this alarm.

RsvpNoMoreResourcesAvailable

RSVP Agent resource allocation failed.

The alarm occurs when allocation of an RSVP Agent fails for all the registered RSVP Agents (RSVP Agents are basically MTPs or transcoder devices which provide RSVP functionality) belonging to the Media Resource Group List and Default List. Each RSVP Agent may fail for different reasons. Following are some of the reasons that could cause an RSVP Agent allocation to fail: available MTP/transcoders do not support RSVP functionality; a capability mismatch between the device endpoint and MTP/transcoder, codec mismatch between the endpoint and the MTP/transcoder; a lack of available bandwidth between the endpoint and the MTP/transcoder; or because the MTP/transcoder resources are already in use.

A capability mismatch may be due to the MTP/transcoder not supporting one or more of the required capabilities for the call such as Transfer Relay Point (which is needed for QoS or firewall traversal), RFC 2833 DTMF (which is necessary when one side of the call does not support RFC 2833 format for transmitting DTMF digits and the other side must receive the DTMF digits in RFC2833 format, resulting in conversion of the DTMF digits), RFC 2833 DTMF passthrough (in this case, the MTP or transcoder does not need to convert the DTMF digits from one format to another format but it needs to receive DTMF digits from one endpoint and transmit them to the other endpoint without performing any modifications), passthrough (where no codec conversion will occur, meaning the media device will receive media streams in any codec format and transmit them to the other side without performing any codec conversion), IPv4 to IPv6 conversion (when one side of the call supports only IPv4 and the other side of the call supports only IPv6 and so MTP needs to be inserted to perform the necessary conversion between IPv4 and IPv6 packets), or multimedia capability (if a call involving video and/or data in addition to audio requires insertion of an MTP or transcoder then the MTP/transcoder which supports multimedia will be inserted).

Cisco Unified Communications
Release
Action

8.0(1)

Media Resource List Name(String) parameter is added.


Alarm Catalog—CallManager/CallManager

Severity—Error

Parameter(s)

Media Resource List Name(String)

Recommended Action

RSVP Agents are basically Cisco IOS MTPs or transcoder devices which provide RSVP functionality. Check the user manual of the configured MTPs and transcoders to see whether they support RSVP functionality. If none of them support RSVP functionality either they need to be upgraded (if upgraded version support RSVP functionality) or additional MTP or transcoders need to be installed which support RSVP functionality. If the RSVP Agent (MTP or transcoder) allocation is failing due to a capability mismatch, it's possible that the media device does not support the requested capability (such as IPv4 to IPv6 conversion, passthrough) or the capability might not be configured in the device. Please check the user guide and documentation of the media device to make sure that device supports all the necessary capabilities.

Also, caution should be taken care if all the MTP or transcoders are configured with all the supported capabilities. There are certain capabilities (such as RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough) which could be supported by most of the MTPs or transcoders and there may be certain capabilities (such as IPv4 to IPv6 conversion and vice versa or RSVP Agent functionality or Transfer Relay Point or multimedia capability) which can be supported by only by a single MTP or transcoder depending on the devices that you have.

For example, you may have end devices belonging to different locations and may need to reserve the bandwidth only between two locations; calls between other locations may not need to reserve the bandwidth. Now, suppose all the MTPs or transcoders are configured with all the supported capabilities and only one MTP/transcoder supports RSVP functionality; if this MTP/transcoder is configured with all the supported capabilities (which all the other MTPs or transcoders in the same MRGL or default MRGL also support) it may happen that this MTP can get allocated for Transfer Relay Point or RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough instead. As a result, when a need arises to reserve the bandwidth (which other MTPs or transcoders in the same MRGL or default MRGL do not support), all the resources of this MTP/transcoder may be in use and the RSVP Agent allocation may fail.

To avoid this situation, set the priority of the media resources appropriately. This can be done only in the Media Resource Group List and not in the Default List of the media resources. In any Media Resource Group List all the Media Resource Groups have different priorities and during allocation the first Media Resource Group is checked for availability of the requested type of the media devices. The first Media Resource Group in the Media Resource Group List will have the highest priority, then the second one and so on. To check all the Media Resource Groups and their priority go the Media Resources and Media Resource Group List of Cisco Unified CM Administration page and click the appropriate Media Resource Group List and check the Selected Media Resource Groups; the priority decreases from top to bottom. Position the MTP or transcoder that you want to be selected for the basic functionalities in the higher priority Media Resource Groups whereas the ones with more rare functionality can be positioned in the Media Resource Groups with lower priority. RSVP Agent allocation may fail due to codec mismatch between the end point and the RSVP Agent or MTP/transcoder.

A solution may be to configure the MTP/transcoder with all the supported codecs (as specified in the user guide of the MTP/transcoder), but be aware that doing so might result in too much bandwidth being allocated for calls. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, approximate bandwidth use per call (not involving MTP/transcoder), and so on, and accordingly calculate the maximum bandwidth that can be allocated per call involving an MTP/transcoder and take that into consideration when configuring the supported codecs in the MTPs and transcoders. A good idea is to configure the media devices with all the supported codecs and set the region bandwidths to restrict too much bandwidth usage (refer to the Unified CM documentation for details on region and location settings).

Also, there may be codec mismatch between the endpoint and the MTP/transcoders after considering the region bandwidth between the MTP/transcoder and the endpoint. Increasing the region bandwidth may be a solution to the problem, but that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions.

Another possible cause that an MTP/transcoder did not get allocated is because there was not enough available bandwidth for the call. This can happen if the MTP/transcoder and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations.

Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth. Finally, if RSVP Agent allocation fails due to MTP/transcoder not supporting RSVP functionality or capability mismatch or all the resources being in use, consider installing additional MTP or transcoder devices which support RSVP functionality.

SDLLinkISV

SDL link to remote application is restored. This alarm indicates that the local Cisco CallManager has gained communication with the remote Cisco CallManager.


Note The remote Cisco CallManager should also indicate SDLLinkISV with a different LinkID.


History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Notice.


Alarm Catalog—CallManager/CallManager

Severity—Notice

Recommended Action

None

SDLLinkOOS

SDL link to remote application out of service.This alarm indicates that the local Unified CM has lost communication with the remote Unified CM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Alert.


Alarm Catalog—CallManager/CallManager

Severity—Alert

Recommended Action

In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can talk to the Publisher. Also check for any alarms that might have indicated a CallManager failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

SIPLineRegistrationError

A SIP line attempted to register with CallManager and failed due to the error indicated in the Reason Code parameter. The alarm could indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Enum Definitions for DeviceType are updated.

Enum Reasons table is updated.


Alarm Catalog—CallManager/CallManager

Severity—Warning

Enum Definitions for DeviceType

Code
Device Type

1

CISCO_30SP+

2

CISCO_12SP+

3

CISCO_12SP

4

CISCO_12S

5

CISCO_30VIP

6

CISCO_7910

7

CISCO_7960

8

CISCO_7940

9

CISCO_7935

12

CISCO_ATA_186

20

SCCP_PHONE

61

H323_PHONE

72

CTI_PORT

115

CISCO_7941

119

CISCO_7971

255

UNKNOWN

302

CISCO_7989

307

CISCO_7911

308

CISCO_7941G_GE

309

CISCO_7961G_GE

335

MOTOROLA_CN622

336

BASIC_3RD_PARTY_SIP_DEVICE

348

CISCO_7931

358

CISCO_UNIFIED_COMMUNICATOR

365

CISCO_7921

369

CISCO_7906

374

ADVANCED_3RD_PARTY_SIP_DEVICE

375

CISCO_TELEPRESENCE

404

CISCO_7962

412

CISCO_3951

431

CISCO_7937

434

CISCO_7942

435

CISCO_7945

436

CISCO_7965

437

CISCO_7975

446

CISCO_3911

468

CISCO_UNIFIED_MOBILE_COMMUNICATOR

478

CISCO_TELEPRESENCE_1000

479

CISCO_TELEPRESENCE_3000

480

CISCO_TELEPRESENCE_3200

481

CISCO_TELEPRESENCE_500

484

CISCO_7925

493

CISCO_9971

495

CISCO_6921

496

CISCO_6941

497

CISCO_6961

20000

CISCO_7905

30002

CISCO_7920

30006

CISCO_7970

30007

CISCO_7912

30008

CISCO_7902

30016

CISCO_IP_COMMUNICATOR

30018

CISCO_7961

30019

CISCO_7936

30035

IP_STE


Enum Reason

Code
Reason

2

MisconfiguredDirectoryNumber - There is a configuration mismatch between the directory numbers configured on the phone and the directory numbers configured in the Cisco Unified CM database. If this is a third-party phone, confirm that the phone configuration is correct and matches the Cisco Unified CM configuration. If this is a Cisco IP phone, confirm database replication has a "good status" in the Unified CM Database Status report. This can be found on the Cisco Unified Reporting web page. If the database replication status is good, reset the device. If the problem still persists, restart the TFTP service and the Cisco Unified CM service from the Control Center - Feature Services web page.

3

MalformedRegisterMessage - Cisco Unified CM cannot process a REGISTER message because of a problem with the format of the message. If the device is a third-party phone, confirm that the endpoint is sending a properly formatted REGISTER message.

4

AuthenticationError - The digest userid or password sent from the phone does not match the userid or password configured in Cisco Unified CM. Digest userid is the end-user associated with the phone on the Phone Config page, Digest User drop down box. Password is configured on the end user page, digest credentials box. If this is a third-party phone, ensure the phone digest credentials match the digest credentials configured on the End User web page. If this is a Cisco IP phone, confirm database replication has a "good status" in the Unified CM Database Status report. This can be found on the Cisco Unified Reporting web page. If the database replication status is good, reset the device. If the problem still persists, restart the TFTP service and the Cisco Unified CM service from the Control Center - Feature Services web page.

6

MaxLinesExceeded - The phone is attempting to register more lines than are allowed. The maximum lines per device is 1024. Reduce the number of lines configured on this device.

7

TransportProtocolMismatch - Incorrect transport protocol (UDP, TCP or TCL) on which the REGISTER message was received. If the device is a third-party phone, ensure that the phone is using a transport protocol that matches the Phone Security Profile assigned to the phone in the CCMAdmin device page. If the device is a Cisco phone, confirm database replication has a "good status" in the Unified CM Database Status report. This can be found on the Cisco Unified Reporting web page. If the database replication status is good, reset the device. If the problem still persists, restart the TFTP service and the Cisco Unified CM service from the Control Center - Feature Services web page.

8

BulkRegistrationError - A unexpected bulk registration message was received. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" under Cisco CallManager services turned on and contact TAC.


Recommended Action

Verify that the directory number(s) on the device itself match the directory number(s) that are configured for that device in Cisco Unified CM Administration. Also, confirm that database replication is working. Refer to the reason code definitions for additional recommended actions.

SIPStarted

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.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Notice.

Enum Definitions for InTransportType and OutTransportType are updated.


Alarm Catalog—CallManager/CallManager

Severity—Notice

Enum Definitions for DeviceType

131—SIP_TRUNK

Enum Definitions for InTransportType

Code
Definition

1

TCP

2

UDP

3

TLS

4

TCP/UDP


Recommended Action

None

SIPStopped

Cisco CallManager is not ready to handle calls for the indicated SIP device. Possible reasons could be internal database error, the SIP device is not activated on this node, the SIP device failed to register or the SIP device was deleted from admin page.

History

Cisco Unified Communications
Release
Action

8.0(1)

Enum Definitions for InTransportType and OutTransportType are updated.


Alarm Catalog—CallManager/CallManager

Severity—Warning

Enum Definitions for InTransportType

Code
Definition

1

TCP

2

UDP

3

TLS

4

TCP/UDP


Enum Definitions for OutTransportType

Code
Definition

1

TCP

2

UDP

3

TLS


Recommended Action

This alarm doesn't necessarily mean an error. It could occur as a result of normal administrative changes. If the alarm is unexpected, check whether the StationPortInitError alarm also fired. Check the Device Pool assigned to the SIP device identified in this alarm to ensure that the Cisco Unified Communications Manager Group of the Device Pool includes the Unified CM node that issued the alarm.

StationAlarm

A station device sent an alarm to Cisco Unified Communications Manager, which acts as a conduit from the device to generate this alarm.

Alarm Catalog—CallManager/CallManager

Severity—Informational (6)

Recommended Action

Refer to the specific device type and information passed via this alarm to determine the appropriate action.

StationConnectionError

Station device is closing its connection with Cisco Unified Communications Manager because of the reason that is stated in this alarm.

History

Cisco Unified Communications
Release
Action

8.0(1)

Reason Code[Enum] parameter added.

Enum Definitions for Reason Code table added.


Alarm Catalog—CallManager/CallManager

Severity—Informational

Enum Definitions -Reason Code

Code
Reason

0

deviceInitiatedReset—The device has initiated a reset, possibly due to a power cycle or internal error. No action required; the device will re-register automatically.

1

sccpDeviceThrottling—(SCCP only) The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. No action necessary, the device will re-register automatically.

2

keepAliveTimeout—Unified CM did not receive a KeepAlive message from the device. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify the device is powered up and operating, verify network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging Alert). No action necessary, the device will re-register automatically.

3

dbChangeNotify—An ApplyConfig command was invoked from Unified CM Administration resulting in an unregistration. No action necessary, the device will re-register automatically.

4

deviceRegistrationSuperceded—An initial device registration request was received but authentication had not yet completed before a new registration request was received. The first registration request was discarded and re-registration should proceed normally. No action is required, the device will re-register automatically.


Recommended Action

None

StationEventAlert

A station device sent an alert to Cisco Unified Communications Manager, which acts as a conduit from the device to generate this alarm.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/CallManager

Severity—Warning

Recommended Action

Refer to the specific device type and information passed via this alarm to determine the appropriate action.

StationTCPInitError

An error during initialization was encountered.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Critical.

Following parameters are removed:

Error Number [String]

ErrorCode [Int]


Alarm Catalog—CallManager/CallManager

Severity—Severity changed from Error to Critical.

Recommended Action

Verify the Cisco Unified Communications Manager IP address is configured and is not configured as the loop back address for the IP version. If the IP settings are correct, collect SDL and SDI traces and contact TAC.

TimerThreadSlowed

Verification of the Cisco Unified Communications Manager (Unified CM) internal timing mechanism has slowed beyond acceptable limits. This generally indicates an increased load on the system or an internal anomaly.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Warning to Critical.


Alarm Catalog—CallManager/CallManager

Severity—Critical

Recommended Action

If this alarm occurs at the same general day or time, or if it occurs with increasing frequency, collect all system performance data in Real-Time Monitoring Tool as well as all trace information for the 30 minutes prior to the time that this alarm occurred and contact TAC.

UserUserPrecedenceAlarm

User-to-user IE was not successfully tunneled to destination; please refer to reason code for additional details.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Enum definitions updated.


Alarm Catalog—CallManager/CallManager

Severity—Warning

Enum Definitions

Code
Definition

2

HopCountExceeded—The hop count field in passing User-to-User IE exceeded the maximum value of 10. The reason could be the presence of routing loops across the Unified CM trunk interfaces (PRI, intercluster trunk, and so on). The recommended action is to check that no routing loops exist across the Unified CM trunk interfaces (PRI, intercluster trunk, and so on) and gateway (H.323) devices related to the indicated failed call. By examining trace files and CDR data in all Unified CM nodes and route patterns in gateways (H.323) that are involved in routing of the indicated failed call, you may be able to detect a translation pattern, route list or other routing mechanism that is part of the loop. Update the routing mechanism that resulted in the loop, and then if the looping route pattern was on a Unified CM, reset the affected route list/pattern in an attempt to clear the route loop; if that fails, reset the affected trunk/gateway or if the looping route pattern was on an H.323 gateway, restart the gateway.

3

UserUserIEDropped—The passing UserUserIE is dropped. If the indicated device is an H.323 intercluster trunk then the possible reason could be that the Passing Precedence Level Through UUIE checkbox in the Trunk Configuration window in Unified CM is not enabled; the recommended action is to verify that the Passing Precedence Level Through UUIE checkbox has been enabled. If the indicated device is an MGCP gateway with Device Protocol set to Digital Access PRI, the possible reason could be that in the incoming UUIE message, either the IEID is not set to USER_USER_IE (126) or the User specific protocol ID value is not set to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00); the recommended action is to verify that the far-end side of the configured PRI trunk interface supports PRI 4ESS UUIE-based MLPP and sends the UUIE message with IEID value set to USER_USER_IE (126) and the User specific protocol ID value is set to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00).


Recommended Action

For HopCountExceeded alarm, the recommended action is to check that no routing loops exist across the Unified CM trunk interfaces (PRI, intercluster trunk, and so on) and gateway (H.323) devices related to the indicated failed call. By examining trace files and CDR data in all Unified CM nodes and route patterns in gateways (H.323) that are involved in routing of the indicated failed call, you may be able to detect a translation pattern, route list or other routing mechanism that is part of the loop.

Update the routing mechanism that resulted in the loop, and then if the looping route pattern was on a Unified CM, reset the affected route list/pattern in an attempt to clear the route loop; if that fails, reset the affected trunk/gateway or if the looping route pattern was on a H.323 gateway, restart the gateway. For call failure reason UserUserIEDropped, if the indicated device is an H.323 intercluster trunk then the recommended action is to verify that the Passing Precedence Level Through UUIE checkbox has been enabled on the Trunk Configuration window. If the indicated device is an MGCP gateway with Device Protocol set to Digital Access PRI and Passing Precedence Level Through UUIE is enabled on the gateway, then verify that the far-end side of the configured PRI trunk interface supports PRI 4ESS UUIE-based MLPP and sends the UUIE message with IEID value set to USER_USER_IE (126) and the User specific protocol ID value set to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00).

Changed Alarms in CDRRep Alarm Catalog

This section explains changes done to the existing alarms in CDRRep Catalog.


Note The Description and the Recommended Action have been updated for all the alarms listed below. Other changes are indicated in the History table.


CDRAgentSendFileFailed

CDR Agent cannot send CDR files from CCM node to CDR Repository node within the CCM cluster because of timeout or other reasons. E-mail alert will be sent to the admin.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed Data Collector Routing List element to Alert Manager.


Alarm Catalog—CallManager/CDR Rep

Severity—Error (3)

Routing List

Event Log

Sys Log

Alert Manager

Recommended Action

1. Check network link status.

2. Check if CDR Repository node (first node in the cluster) is alive.

3. Check if CDR Repository Manager is activated on the first node.

4. Check CDRM Configuration under serviceability->tools.

5. Check CDR Agent trace on the specific node where error occurred.

6. Check CDR Repository Manager trace.

7. Check if the Publisher is being upgraded. If the CDRAgentSendFileFailureContinues alarm is no longer present, the condition is corrected.

CDRAgentSendFileFailureContinues

CDR Agent cannot send CDR files from CCM node to CDR Repository node on retries. CDR Agent cannot send CDR files on retries after the initial failure from CCM node to CDR Repository node within the cluster.

Alarm Catalog—CallManager/CDR Rep

Severity—Error (3)

Recommended Action

1. Check network link status.

2. Check if CDR Repository node (first node in the cluster) is alive.

3. Check if CDR Repository Manager is activated on the first node.

4. Check CDRM Configuration under serviceability->tools.

5. Check CDR Agent trace on the specific node where error occurred.

6. Check CDR Repository Manager trace.

7. Check if the Publisher is being upgraded.

CDRFileDeliveryFailed

FTP delivery of CDR files to the Billing Server outside of the cluster failed because of timeout or other reasons. E-mail alert will be sent to the admin.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed Data Collector Routing List element to Alert Manager.


Alarm Catalog—CallManager/CDR Rep

Severity—Error (3)

Routing List

Event Log

Sys Log

Alert Manager

Recommended Action

1. Check network link status.

2. Check if billing server is alive.

3. Check if (s)FTP Server on the billing server is running and accepting request.

4. Check if CDRM Configuration is correct under Serviceability > Tools.

5. Check CDR Repository Manager trace.

CDRFileDeliveryFailureContinues

(s)FTP delivery of CDR files failed on retries to the Billing Server outside of the cluster failed on retries after the initial failure.

Alarm Catalog—CallManager/CDR Rep

Severity—Error (3)

Recommended Action

1. Check network link status.

2. Check if billing server is alive.

3. Check if (s)FTP Server on the billing server is running and accepting request.

4. Check if CDRM Configuration is correct - under Serviceability>tools.

5. Check CDR Repository Manager trace.

CDRHWMExceeded

The CDR files disk usage has exceeded the High Water Mark. CDRM deleted some successfully delivered CDR files that are still within the preservation duration, in order to bring the disk usage down to below HWM. E-mail alert will be sent to the admin.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed Data Collector Routing List element to Alert Manager.


Alarm Catalog—CallManager/CDR Rep

Severity—Error (3)

Routing List

Event Log

Sys Log

Alert Manager

Recommended Action

The preservation duration may be too long. Reduce it at serviceability->tools->CDRM Configuration.

Or raise maximum allocated disk space and/or HWM for CDR files.

CDRMaximumDiskSpaceExceeded

The CDR files disk usage exceeded maximum disk allocation. Some undeliverable files may have been deleted to bring disk usage down. The CDR files disk usage has exceeded the maximum allocated disk space. CDRM may have deleted some CDR files that have not been sent to the outside billing servers yet, in order to bring the disk usage down to below High Water Mark. The decision whether to delete undeliverable files or not depends on how deletionDisable flag is configured at CDRM Configuration page. E-mail alert will be sent to the admin.

History

Cisco Unified Communications
Release
Action

8.0(1)

Facility and sub-facility changed. Added Routing List and changed Data Collector to Alert Manager.


Facility/Sub-Facility

CDRREP

Alarm Catalog—CallManager/CDR Rep

Severity—Critical (2)

Routing List

Event Log

Sys Log

Alert Manager

Recommended Action

1. Check if there are too many undeliverable CDR files accumulated due to some condition.

2. Check network link status.

3. Check if billing server is alive.

4. Check if (s)FTP Server on the billing server is running and accepting request.

5. Check if CDRM Configuration for billing servers is correct - under serviceability->tools.

6. Check if CDR files maximum disk allocation is too low - under serviceability->tools.

7. Check CDR Repository Manager trace under /var/log/active/cm/trace/cdrrep/log4j.

Changed Alarms in DB Alarm Catalog

This section explains changes done to the existing alarms in DB Catalog.


Note The Description and the Recommended Action have been updated for all the alarms listed below. Other changes are indicated in the History table.


ErrorChangeNotifyClientBlock

A change notification client is busy (blocked). If the change notification client continues to be blocked for 10 minutes, the system automatically clears the block and change notification should resume successfully. Changes made to the database are not being consumed by one of the recipients. This does not always represent an issue. However, if the change notification client continues to be blocked for 10 minutes, the system automatically clears the block for all clients except the blocked one, which means that change notifications should resume successfully for all other clients. To clear the blocked client, you must restart the server.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed severity level to Critical from Error.


Alarm Catalog—System/DB

Severity—Critical (2)

Recommended Action

At the command line interface (CLI) on the database server, execute the following command:

show tech notify

The CLI command output will provide information about the block. Use Cisco Unified Serviceability to restart the server that was indicated in the alarm. You may also want to gather traces to examine them for anomalous activity during the time that client was blocked. In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Also, use RTMT to look for a change that may have occurred around the time of the alarm.

ErrorReadingInstalledRPMS

Could not read installed RPMs to populate component version table. The function that reads the rpm version information and populates database failed.

Alarm Catalog—System/DB

Severity—Error (3)

Recommended Action

Report this error to the administrator.

IDSEngineCritical

This alarm does not compromise data or prevent the use of the system but need to be monitored by the Administrator.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed severity level to Error from Critical.


Alarm Catalog—System/DB

Severity—Error (3)

Recommended Action

This alarm needs monitoring by the db admin.

IDSEngineDebug

Indicates debug events from IDS database engine. This alarm provides low-level debugging information from IDS database engine. System administrator can disregard this alarm.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed severity level to Informational from Debug.


Alarm Catalog—System/DB

Severity—Informational

Recommended Action

None

IDSReplicationInformation

Information about IDS replication.

Alarm Catalog—System/DB

Severity—Informational

Recommended Action

Information only. No action is required.

Changed Alarms in IMS Alarm Catalog

This section explains changes done to the existing alarms in IMS Catalog.


Note The Description and the Recommended Action have been updated for all the alarms listed below. Other changes are indicated in the History table.


AdminPassword

Administrative password got changed. If the change was unsuccessful or successful, a message gets displayed.

Alarm Catalog—System/IMS

Severity—Informational

Recommended Action

None

authAdminLock

User is locked out by administrator.

Alarm Catalog—System/IMS

Severity—Warning (4)

Recommended Action

Administrator can unlock this user.

authExpired

Authentication failure due to expired soft lock. User credentials have expired.

History

Cisco Unified Communications
Release
Action

8.0(1)

Added Routing List element and updated the parameter list.


Alarm Catalog—System/IMS

Severity—Notice (5)

Routing List

Event Log

Parameters

Authentication failure due to expired soft lock.(String)

Recommended Action

Administrator may reset the credential.

authFail

Failed to authenticate this user.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed severity level from Notice to Warning.


Alarm Catalog—System/IMS

Severity—Warning (4)

Recommended Action

Determine correct credentials and retry.

authHackLock

User attempted too many incorrect authentications. The maximum number of attempts gets set by the administrator.

History

Cisco Unified Communications
Release
Action

8.0(1)

Updated the parameter list.


Alarm Catalog—System/IMS

Severity—Warning (4)

Parameters

UserID(String)

Recommended Action

Wait for administrator specified time to retry, or have administrator unlock the credential.

authInactiveLock

The user has been inactive for a specified time and the credential is locked.

History

Cisco Unified Communications
Release
Action

8.0(1)

Updated the parameter list.


Alarm Catalog—System/IMS

Severity—Warning (4)

Parameters

UserID(String)

Recommended Action

Reset credential.

authLdapInactive

Authentication failed because the user exists in the database and the system specifies LDAP authentication. A directory sync got performed in the immediate past (1 day).

Alarm Catalog—System/IMS

Severity—Warning (4)

Recommended Action

This user has yet to be removed from the database or the alarm will clear itself within 24 hours.

authMustChange

Authentication failed because it is marked that it must be changed by the user."User must change" is set on this credential. The user must change the credential.

History

Cisco Unified Communications
Release
Action

8.0(1)

Parameter list is updated.

Routing List element is added.


Alarm Catalog—System/IMS

Severity—Notice

Routing List

Event Log

Parameters

UserID[String]

Recommended Action

User or Administrator may reset credential.

authSuccess

Successfully authenticated this user.

Alarm Catalog—System/IMS

Severity—Informational (6)

Recommended Action

None

credFullUpdateFailure

An error was encountered during update of credential fields.

Alarm Catalog—System/IMS

Severity—Informational (6)

Recommended Action

Determine the issue and retry.

credFullUpdateSuccess

Credential was successfully updated.

Alarm Catalog—System/IMS

Severity—Informational (6)

Recommended Action

None

credReadFailure

Error occurred attempting to read a credential in the database. This could be a network or database issue.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed severity level to Notice from Informational. Updated parameter list and added Routing List element.


Alarm Catalog—System/IMS

Severity—Notice (5)

Routing List

Event

Parameters

Credential read failure for(String)

Recommended Action

Ensure credential (user name) exists. Could be a database problem.

credReadSuccess

Successfully read a credential.

Alarm Catalog—System/IMS

Severity—Informational (6)

Recommended Action

None

credUpdateFailure

The credential update failed most likely because the credential did not pass the security requirements (too short or credential used before, for example).

Alarm Catalog—System/IMS

Severity—Informational (6)

Recommended Action

Determine issue (check length requirements, etc.) for this credential and retry.

credUpdateSuccess

Credential was successfully updated.

Alarm Catalog—System/IMS

Severity—Informational (6)

Recommended Action

None

Changed Alarms in IpVms Alarm Catalog

This section explains changes done to the existing alarms in IpVms Catalog.


Note The Description and the Recommended Action have been updated for all the alarms listed below. Other changes are indicated in the History table.


ANNDeviceRecoveryCreateFailed

ANN device recovery create failure. The ANN device recovery class create failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The announcement device will not be available.

History

Cisco Unified Communications
Release
Action

8.0(1)

Added Routing List elements and Parameters.


Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Routing List

SDI

Event Log

Sys Log

Parameters

OS Error Code(Int)

OS Error Description(String)

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart server.

CFBDeviceRecoveryCreateFailed

The CFB device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The conference bridge device will not be available.

History

Cisco Unified Communications
Release
Action

8.0(1)

Added Routing List elements and Parameters.


Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Routing List

SDI

Event Log

Sys Log

Parameter(s)

OS Error Code(Int)

OS Error Description(String)

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart server.

MOHDeviceRecoveryCreateFailed

An error got triggered restarting the Music On Hold (MOH) device. It may have been caused by a shortage of memory resources.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning (4)

Recommended Action

Check the status of the MOH device. If it is not registered and available, restart the Cisco IP voice Media Streaming App service or restart the server.

MTPDeviceRecoveryCreateFailed

MTP device recovery create failure. An error was encountered trying to restart the Media Termination Point device. This may be due to a shortage of application memory.

History

Cisco Unified Communications
Release
Action

8.0(1)

Changed severity level from Error to Warning and added existing Routing List elements and Parameters.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Restart the IP Voice Media Streaming App service or restart the server.

SoftwareLicenseNotValid

There is no valid software license; the Cisco IP Voice Media Streaming App service requires a valid software license to operate.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Install a valid software license and restart Cisco IP Voice Media Streaming App service.

SoftwareLicenseValid

A valid software license has been detected by the IP Voice Media Streaming App service.

Alarm Catalog—CallManager/IpVms

Severity—Informational

Recommended Action

No action required. This informational message indicates alarm SoftwareLicenseNotValid is cleared.

kANNAudioCreateDirFailed

Unable to create a subdirectory to contain announcement files. This may be caused by insufficient disk storage. Announcements may not play correctly as a result of this error.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Parameter list updated.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameters

OS Error Text(String)

Path Name(String)

Recommended Action

Check for available free space on the common data storage area. If full, take action to remove old trace files to free space. Restart the Cisco IP Voice Media Streaming App service.

kANNAudioUndefinedAnnID

Requested announcement not found. This may be caused by using an incorrect announcement identifier for a custom announcement. Use the Cisco Unified CM Admin to view a list of custom announcement identifiers and verify the correct one is being used.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Parameter list removed.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Correct the announcement identifier chosen from the custom announcement list.

kANNAudioUndefinedLocale

Unknown ANN locale. The requested Locale for an announcement is not installed. For network locale you use the platform CLI interface to run (run sql select * from typecountry where enum = #), #=locale. This will tell you what country locale is being requested.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Parameter list is updated.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Install the locale package or check device settings for an incorrect locale value.

kANNDeviceRecordNotFound

ANN device record not found. A device record for the announcer device was not found in the database. The ANN device is normally automatically added when the server is added to the database.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Warning to Error.


Alarm Catalog—CallManager/IpVms

Severity—Error

Recommended Action

To add the ANN device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

kANNDeviceStartingDefaults

The ANN device configuration was not found. A service parameter for Cisco IP Voice Media Streaming App service related to the ANN device configuration was not found. The system will start with the given default setting.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Warning.

Parameter list added.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameter(s)

Parameter Name [String]

Value Used [String]

Recommended Action

Review the service parameter settings and configure the ANN device settings properly using the Cisco Unified CM Administration.

kANNICMPErrorNotification

ANN stream ICMP port unreachable error. An announcement RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point not having the receiving UDP/RTP port open to receive packets.

History
Cisco Unified Communications
Release
Action

8.0.1

Parameter list updated.


Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Parameters

Destination IP Address [String]

Recommended Action

No action is required. This may occur at times when connections are being stopped or redirected.

kCFBDeviceRecordNotFound

CFB device record not found. A device record for the conference bridge device was not found in the database. The CFB device is normally automatically added when the server is added to the database.

History
Cisco Unified Communications
Release
Action

8.0(1)

The severity changed from Informational to Error.


Alarm Catalog—CallManager/IpVms

Severity—Error

Recommended Action

To add the CFB device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

kCFBDeviceStartingDefaults

CFB device configuration not found. A service parameter for Cisco IP Voice Media Streaming App service related to the CFB device configuration was not found. The system will use the given default setting.

History
Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Warning.

New parameters added:

Parameter Name(String)

Value Used(String)


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameter(s)

Parameter Name(String)

Value Used(String)

Recommended Action

Review the service parameter settings and configure the CFB device settings properly using the Cisco Unified CM Administration.

kCFBICMPErrorNotification

CFB stream ICMP error. A SW CFB RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point does not have the receiving UDP/RTP port open to receive packets.

Cisco Unified Communications
Release
Action

8.0(1)

Following parameters are removed:

Call ID [ULong] Party ID [ULong] IP Port [ULong]


Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Parameters

Destination IP Address [String]

Recommended Action

No action is required. This may occur at times when connections are being stopped or redirected.

kChangeNotifyServiceCreationFailed

Database change notification subsystem not starting. The background process to activate database changes has failed to start. Database changes affecting the Cisco IP Voice Media Streaming App service will not automatically take effect.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Following parameters added:

OS Error Code(Int)

OS Error Description(String)


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameter(s)

OS Error Code(Int)

OS Error Description(String)

Recommended Action

Restart the Cisco IP Voice Media Streaming App service to get the DB notification reenabled.

kChangeNotifyServiceGetEventFailed

Invalid notification event returned by database change notification. The change notification subsystem returned an invalid notification event. The Cisco IP Voice Media Streaming App service will terminate. The SW media devices (ANN, CFB, MOH, MTP) will be temporarily out of service and calls in progress may be dropped.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Following parameters added:

OS Error Code(Int)

OS Error Description(String)


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameter(s)

OS Error Code(Int)

OS Error Description(String)

Recommended Action

Check the current status of the Cisco IP Voice Media Streaming App service and monitor for repeated occurrences.

kChangeNotifyServiceRestartFailed

Database change notification restart failure. The change notification subsystem failed to restart.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Following parameters added:

OS Error Code(Int)

OS Error Description(String)


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameter(s)

OS Error Code(Int)

OS Error Description(String)

Recommended Action

This service has change notification disabled, so it may be enabled at a later time. You can restart the Cisco IP Voice Media Streaming App service to enable immediately.

kCreateAudioSourcesFailed

Creating audio source class failed. Unable to create audio source subcomponent to provide audio for streaming. This may be due to lack of memory.

Cisco Unified Communications
Release
Action

8.0(1)

Following parameters added:

OS Error Code(Int)

OS Error Description(String)


Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Parameters

OS Error Code(Int)

OS Error Description(String)

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart the server.

kCreateControlFailed

Stream Control create failure. Create stream control subcomponent. The error may be due to lack of memory.

Cisco Unified Communications
Release
Action

8.0(1)

Following parameters added:

OS Error Code(Int)

OS Error Description(String)


Alarm Catalog—CallManager/IpVms

Severity—Error

Parameters

Codec Type [String]

OS Error Code [Int]

OS Error Description [String]

Recommended Action

Reset the MOH device. If continues to fail restart the Cisco IP Voice Media Streaming App service or restart the server.

kDeviceDriverError

IP voice media streaming device driver error. The IP voice media streaming device driver returned an error. This may indicate a significant media error or resource shortage.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Restarting the Cisco IP Voice Media Streaming App service or possibly restarting the server may resolve the error condition.

kDeviceMgrCreateFailed

Device connection manager failed to start. The device controller was unable to start a connection to control device registration with CallManager. This is possibly due to lack of memory.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart the Cisco Unified CM server.

kDeviceMgrExitEventCreationFailed

Creation of device manager exit event failure. An error was reported when allocating an exit-control event for a SW media device. The device will not be registered with CallManager or active.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning (4)

Recommended Action

This error may be due to a memory resource shortage. Restart the Cisco IP Voice Media Streaming App service or restart the Cisco Unified CM server.

kDeviceMgrLockoutWithCallManager

Cisco Unified Communications Manager in lockout.The specified Cisco Unified Communications Manager has failed to respond to control messages. The TCP control connection to Cisco Unified CM is being suspended. This will cause a switch to another Cisco Unified CM if one is available otherwise the device will be unavailable. There may be a shortage of CPU resource or some other error condition on the Cisco Unified CM server.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Informational.


Alarm Catalog—CallManager/IpVms

Severity—Informational

Recommended Action

Check the status of the Cisco Unified Communications Manager service. You may have to restart the Cisco Unified CM service or the Cisco Unified CM server.

kDeviceMgrMoreThan50SocketEvents

More than 50 events returned from TCP link. The specified Cisco Unified Communications Manager TCP link has returned a large number of TCP events. This indicates an unexpected flood of events.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Notice.


Alarm Catalog—CallManager/IpVms

Severity—Notice

Recommended Action

No action is required. Monitor for reoccurrence. This could be an indication of a security issue.

kDeviceMgrOpenReceiveFailedOutOfStreams

Open receive failure. The open receive channel failed. This may indicate a mismatch of media resources between Cisco Unified Call Manager and the Cisco IP Voice Media Streaming App service.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Check the performance monitor counters for resource availability on Cisco Unified CM and on Cisco IP Voice Media Streaming App. Also, you might run the Platform CLI command "Show Media Streams" to identify possible media connection resource leaks. Possibly reset the media device or restart Cisco IP Voice Media Streaming App or restart the Cisco Unified CM server.

kDeviceMgrRegisterKeepAliveResponseError

Cisco Unified Communications Manager not responding. The specified Cisco Unified Communications Manager is not responding to the keepalive messages. The connection with Cisco Unified CM is being terminated and the media device will reregister with another Cisco Unified Call Manager if a secondary is configured. Otherwise, the media device will be unavailable until the device is able to reregister with Cisco Unified CM.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Cisco Unified Communications Manager may have gone down or is unable to respond. Check status of Cisco Unified CM. The media device should automatically reregister.

kDeviceMgrRegisterWithCallManager

Register with Cisco Unified Communications Manager. The software media device registered with the specified Cisco Unified Communications Manager.

Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Recommended Action

None

kDeviceMgrRegisterWithCallManagerError

Connection error with Cisco Unified Communications Manager. The media device was registered with the specified Cisco Unified Communications Manager and received a socket error or disconnect. This may occur normally when Cisco Unified Communications Manager is stopped.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

No action is required; The media device will reregister.

kDeviceMgrSocketDrvNotifyEvtCreateFailed

This alarm get generated when creating a signaling event for communication with the media streaming kernel driver. It can be caused by memory or system resource shortages/

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning (4)

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart the Cisco Unified Communications Manager server.

kDeviceMgrSocketDrvNotifyEvtCreateFailed

This alarm get generated when creating a signaling event for communication with the media streaming kernel driver. It can be caused by memory or system resource shortages/

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed to Warning from Error.


Alarm Catalog—CallManager/IpVms

Severity—Warning (4)

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart the Cisco Unified Communications Manager server.

kDeviceMgrStartTransmissionOutOfStreams

Start transmission failure. An error was encountered while starting an RTP transmission audio stream. This may indicate a mismatch of resources between Cisco Unified Communications Manager and Cisco IP Voice Media Streaming App service.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Check the performance counters for the media resources on Cisco Unified CM and Cisco IP Voice Media Streaming App to determine if there is a resource leak. You should also use the platform CLI command "Show Media Streams" to check for orphaned media RTP connections.

kDeviceMgrThreadWaitFailed

Wait call failure in device manager thread. An error was reported during a system request to wait on an event, the media device will be restarted.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Informational.

Following parameters added:

OS Error Code [Int]

OS Error Description [String]


Alarm Catalog—CallManager/IpVms

Severity—Informational

Parameters

Trace Name [String]

OS Error Code [Int]

OS Error Description [String]

Recommended Action

None

kDeviceMgrThreadxFailed

Creation of thread failure. An error was reported when starting a process for the specified media device. This may be due to a system resource shortage.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Following parameters added:

OS Error Code[Int]

OS Error Description [String]


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameters

Device Name [String] Trace Name [String] OS Error Code [Int] OS Error Description [String]

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart the Cisco Unified CM server to recover from this error.

kDeviceMgrUnregisterWithCallManager

Unregister with Cisco Unified Communications Manager. A media device has unregistered with the specified Cisco Unified Communications Manager.

Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Recommended Action

No action is required. The media device will automatically reregister.

kFixedInputCodecStreamFailed

Fixed input codec stream initialization failure. Initialization of sound card codec source transcoding process failed. The fixed audio source will not play possibly due to memory or resource shortage.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Following parameters removed:

Audio Source ID [ULong]

System error code [ULong]


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameters

Error text [String] Codec Type [String]

Recommended Action

Reset MOH device, or restart Cisco IO Voice Media Streaming App service, or restart server.

kFixedInputCreateControlFailed

Fixed stream control create failure. The audio stream control subsystem for the Fixed MOH audio source failed to start. Audio from the MOH Fixed audio source will not be provided for streaming out. This may be due to resource shortage such as memory or availability of the Fixed MOH audio source device.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Audio Source ID [ULong] parameter is removed.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameters

Codec Type [String]

Recommended Action

Reset MOH device, if failure continues restart the server. Monitor for errors in trace files and system log.

kFixedInputCreateSoundCardFailed

Fixed stream sound card interface create failure. An error was encountered when starting the interface to access the sound card for providing MOH fixed audio. The audio source will not play possibly due to shortage of memory.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Audio Source ID [ULong] parameter is removed.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameters

Codec Type [String]

Recommended Action

Reset MOH device, or restart the Cisco IP Voice Media Streaming App service, or restart the server. Check the system log and possibly the traces for Cisco IP Voice Media Streaming App service.

kFixedInputInitSoundCardFailed

Fixed stream sound card interface initialization failure. Initialization of sound card failed. Fixed audio source will not play possibly due to missing or unconfigured USB sound device.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Following parameters are removed:

Audio Source ID [ULong]

System error code [ULong]


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameters

Error text [String] Device name [String]

Recommended Action

Check that the USB sound is installed. Reset MOH device, or restart Cisco IP Voice Media Streaming App service, or restart the server. The system log and traces from Cisco IP Voice Media Streaming App may contain additional information.

kFixedInputTranscoderFailed

Fixed input audio stream transcoder failure. An error was encountered while transcoding audio from the sound card. The audio source will not play possibly due an error accessing the sound card.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Following parameters are removed:

Audio Source ID [ULong]

System error code [ULong]


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameters

Error text [String]

Recommended Action

Check that the USB sound device is properly installed. Unplug the USB sound device and replug back into the USB connector. Reset MOH device, restart Cisco IP Voice Media Streaming App service, or restart the server.

kGetFileNameFailed

Get audio source file name failure. The Music-on-Hold audio source is not assigned to an audio file.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

Audio Source ID [ULong] parameter is removed.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameters

Codec Type [String]

Recommended Action

Assign the audio source to an audio file or change the value of the MOH audio source to a value that has been configured.

kIPVMSDeviceDriverNotFound

Cisco IP voice media streaming driver not found. The Cisco IP voice media streaming driver was not found or is not installed. The Cisco IP Voice Media Streaming App service cannot run until this error is resolved. All software media devices (ANN, CFB, MOH, MTP) for this server will not be available.

Cisco Unified Communications
Release
Action

8.0(1)

This alarm is available in 8.0(1).


Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Recommended Action

Check the system log for an error when the system attempted to load IpVms driver at the last server startup. A server restart is required to cause the driver to be loaded.

kIPVMSMgrEventCreationFailed

Creation of required signaling event failed. An error was encountered when creating a signaling event component. This may be due to a resource shortage. The Cisco IP Voice Media Streaming App service will terminate.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Check the trace files for more information. The service should automatically be restarted. If this error continues to reoccur the server may need to be restarted.

kIPVMSMgrThreadxFailed

Creation of the IPVMSMgr thread failed. An error was encountered while starting a process thread. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Monitor the status of the Cisco IP Voice Media Streaming App service. It should automatically be restarted. If the error reoccurs, restart the server.

kIPVMSMgrWrongDriverVersion

Wrong version of device driver. An incompatible device driver was found. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

History

Cisco Unified Communications
Release
Action

8.0(1)

Following parameters are removed:

Found [ULong]

Need [ULong]


Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Recommended Action

Restart the server to ensure the most recent driver is started. If the error continues, then reinstall Cisco Unified Communications Manager to get the proper driver version installed.

kIPVMSStarting

The Cisco IP Voice Media Streaming App service is starting.

Cisco Unified Communications
Release
Action

8.0(1)

ProcessID [ULong] parameter is removed.


Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Parameters

Version [String] IPAddress [String] Hostname [String] ServiceName [String]

Recommended Action

No action is required.

kIPVMSStopping

The Cisco IP voice media streaming application is shutting down.

History

Cisco Unified Communications
Release
Action

8.0(1)

ProcessID [ULong] parameter is removed.


Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Parameters

Version [String] IPAddress [String] Hostname [String] ServiceName [String]

Recommended Action

No action is required.

kIpVmsMgrNoLocalHostName

Unable to retrieve the local host server name. The Cisco IP Voice Media Streaming App service will terminate. No software media devices (ANN, CFB, MOH, MTP) will be available while the service is stopped.

Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Recommended Action

Check the configuration settings for the server name, DHCP, or DNS. Monitor the status of Cisco IP Voice Media Streaming App service. The service will not operate without a valid server name.

kIpVmsMgrNoLocalNetworkIPAddr

Unable to retrieve the network IP address for host server. Unable to obtain the network IP (dotted) address. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while this service is stopped.

Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Recommended Action

Monitor the status of the Cisco IP Voice Media Streaming App service. It should be automatically restarted. If the error occurs again, check the server IP configuration (DHCP, IP address).

kIpVmsMgrThreadWaitFailed

Error while waiting for asynchronous notifications of events. An error was reported while the primary control process for Cisco IP Voice Media Streaming App was waiting on asynchronous events to be signaled. The service will terminate and should automatically be restarted. This will cause a temporary loss of availability for the software media devices (ANN, CFB, MOH, MTP).

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Monitor the service and status of the software media devices. The service should automatically restart. If the problem continues, review the trace files for additional information. A server restart may be required if this repeats.

kMOHBadMulticastIP

An invalid multicast IP address (out of range) was found.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed to Warning from Error.

Following parameters are removed:

Audio Source ID [ULong]

Call/Conference ID [ULong]

Multicast IP Port [ULong]


Alarm Catalog—CallManager/IpVms

Severity—Warning (4)

Parameters

Codec Type [String]

Multicast IP Address [String]

Recommended Action

Correct the setting on the Music-on-Hold device configuration for multicast address.

kMOHDeviceRecordNotFound

MOH device was not found for the server. This device gets added automatically when a server gets added to the configuration.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning (4)

Recommended Action

If MOH functionality is required, you will have to remove and re-add the device to database.


Caution Adding and removing the device may impact other configuration settings, for example, Cisco Unified Communications Manager groups and media resource groups.

kMOHICMPErrorNotification

MOH stream ICMP error. A Music-on-Hold transmission stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This may occur occasionally depending on call termination sequences.

History

Cisco Unified Communications
Release
Action

8.0(1)

Following parameters are removed:

Call ID [ULong] Party ID [ULong] IP Port [ULong]


Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Parameters

Destination IP Address [String]

Recommended Action

No action is required.

kMOHMgrCreateFailed

Error starting MOH Audio source subcomponent. A error was encountered by the Music-on-Hold device while starting the sub-component that provides audio from files or sound card. This may be due to shortage of resources (memory).

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

OS Error Description(String) parameter is added.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameter(s)

OS Error Description(String)

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart the server.

kMOHMgrExitEventCreationFailed

Creation of MOH manager exit event failure. An error was encountered when allocating a signaling event. This may be caused by a resource shortage.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart the server.

kMOHMgrIsAudioSourceInUseThisIsNULL

Synchronization error detected in MOH audio manager. A synchronization error was detected. Condition has been resolved automatically.

Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Recommended Action

No action is required.

kMOHMgrThreadWaitFailed

Wait call failure in MOH manager thread. An error was encountered in Music-on-Hold audio manager subcomponent while waiting for asynchronous event signaling. The MOH device will be restarted.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Informational.

OS Error Description(String) parameter is added.


Alarm Catalog—CallManager/IpVms

Severity—Informational

Parameter(s)

OS Error Description(String)

Recommended Action

No action is required.

kMOHMgrThreadxFailed

Starting of MOH audio manager failed. An error was encountered when starting the Music-on-Hold audio manager subcomponent. Music-on-Hold audio services will not be avaliable.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.

OS Error Description(String) parameter is added.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Parameters

OS Error Description(String)

Recommended Action

Restart the Cisco IP Voice Media Streaming App service.

kMOHRewindStreamControlNull

Attempted to rewind an inactive MOH audio source. An attempt was made to rewind or restart the Music-on-Hold audio source that is inactive. This has been ignored.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Informational.

Audio Source ID [ULong] parameter is removed.


Alarm Catalog—CallManager/IpVms

Severity—Informational

Parameters

Codec Type [String]

Recommended Action

None

kMOHRewindStreamMediaPositionObjectNull

Error rewinding MOH audio source that is not playing. An attempt was made to rewind or restart a Music-on-Hold wav file that was not being played. This has been ignored.

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Informational.

Audio Source ID [ULong] parameter is removed.


Alarm Catalog—CallManager/IpVms

Severity—Informational

Parameters

Codec Type [String]

Recommended Action

None

kMOHTFTPGoRequestFailed

Transfer of MOH source file to working path failed. An error was encountered when trying to copy or update a Music-on-Hold audio source file.

Cisco Unified Communications
Release
Action

8.0(1)

Following parameters added:

Error Description [String] Source Path [String]
Destination Path [String] OS Error Code [Int]
OS Error Description [String]


Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Parameters

Error Description [String] File Name [String] Source Path [String] Destination Path [String]
OS Error Code [Int] OS Error Description [String]

Recommended Action

Use the Platform CLI to verify that the the source path and file exist. If the file does not exist, open Cisco Unified Communications Manager Administration and upload the missing audio source to this specific server. Reinstall the Cisco Unified Communications Manager to have all required paths created.

kMTPDeviceRecordNotFound

MTP device record not found. A device record for the software media termination point device was not found in the database. This is normally automatically added to the database when a server is added to the database. The software MTP device will be disabled.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Informational to Warning.


Alarm Catalog—CallManager/IpVms

Severity—Warning

Recommended Action


Tip If MTP functionality is required, you will need to delete the server and re-add the server back to the database using by Cisco Unified Communications Manager Administration.This may require many additional configuration settings to be reapplied such as Cisco Unified Communications Manager groups, media resource groups, and more.


kMTPDeviceStartingDefaults

One or more Cisco IP Voice Media Streaming App service parameter settings for the MTP device were not found in the database. The default values are included here.

History

Cisco Unified Communications
Release
Action

8.0(1)

MTP Run Flag(String) parameter is added.


Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Parameter(s)

MTP Run Flag(String)

Recommended Action

Configure the service parameter settings for the MTP device.

kPWavMgrThreadxFailed

WAV playing manager thread creation failed. The process component used for playing WAV files failed to start, possibly due to low system resources.

Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Recommended Action

Restart the Cisco IP Voice Media Streaming App service or restart server.

kReadCfgIpTosMediaResourceToCmNotFound

IP TOS MediaResource to Cm value not found. The IP Type-of-Service Media Resource To Call Manager service parameter value was not found in the database. Defaulting its value to 0x60 for CS3(precedence 3) DSCP (011000).

Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Recommended Action

Set the Ip Type-of-Service Media Resource To Call Manager service parameter for the Cisco IP Voice Media Streaming App service.

kReadCfgMOHEnabledCodecsNotFound

MOH enabled codecs not found. The Music-on-Hold service parameter for codec selection could not be read from database. Defaulting to G.711 mu-law codec.

Alarm Catalog—CallManager/IpVms

Severity—Informational (6)

Recommended Action

Set the Music-on-Hold service parameter for Cisco IP Voice Media Streaming App service.

kReadCfgUserLocaleEnterpriseSvcParm

Error reading Enterprise User Locale configuration. A database exception was encountered when reading the default Enterprise User Locale setting. Default of US English will be used.

Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Recommended Action

Verify that the Enterprise parameter setting for User Locale is configured using the CCM Admin web page. Restart the Cisco IP Voice Media Streaming App service.

kRequestedANNStreamsFailed

The requested resources for the configured number of annunciator calls (Call Count service parameter) was not available. If the value gets shown as "Allocated," it is non-zero.

History

Cisco Unified Communications
Release
Action

8.0(1)

Following parameters are removed:

Requested streams [ULong] Allocated streams [ULong]


Alarm Catalog—CallManager/IpVms

Severity—Error (3)

Recommended Action

Verify that the ANN Call Count service parameter is correct. A server restart may be needed to recover resources.

kRequestedCFBStreamsFailed

CFB requested streams failure. The resources for the number of requested full-duplex streams was not available.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—WARNING

Recommended Action

Verify the Cisco IP Voice Media Streaming App service parameter for number of CFB calls. Restart the server to reset the stream resources.

kRequestedMOHStreamsFailed

MOH requested streams failure. The resources for the number of requested streams was not available.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—WARNING

Recommended Action

Verify the number of calls configuration setting for Music-on-Hold device. Restart the server to reset the resources.

kRequestedMTPStreamsFailed

MTP requested streams failure. The resources for the number of requested full-duplex Media Termination Point streams was not available.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Error to Warning.


Alarm Catalog—CallManager/IpVms

Severity—WARNING

Recommended Action

Verify the Cisco IP Voice Media Streaming App service parameter setting for number of MTP calls is correct. Restart the server to reset the available resources.

Changed Alarms in JavaApplications Alarm Catalog

This section explains changes done to the existing alarms in JavaApplications Catalog.


Note The Description and the Recommended Action have been updated for all the alarms listed below. Other changes are indicated in the History table.


IPMAFilteringDown

IPMA application filtering is down.

Alarm Catalog—System/Java Applications

Severity—Error (3)

Recommended Action

Restart Cisco IP Manager Assistant Service.

WDStopped

WebDialer application stopped and was unloaded from Tomcat.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity changed from Alert to Warning.


Alarm Catalog—System/Java Applications

Severity—Warning

Recommended Action

Check if Tomcat service is up.

Changed Alarms in Login Alarm Catalog

This section explains changes done to the existing alarms in Login Catalog.


Note The Description and the Recommended Action have been updated for all the alarms listed below. Other changes are indicated in the History table.


AuthenticationFailed

Login Authentication failed.

History

Cisco Unified Communications
Release
Action

8.0(1)

Severity Changed from Error to Warning.


Alarm Catalog—System/Login

Severity—Warning

Recommended Action

If this event happens repeatedly, investigate the source of the failed login attempts.

Changed Alarms in LpmTct Alarm Catalog

This section explains changes done to the existing alarms in LpmTct Catalog.


Note