Specifications

6-106
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
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.