Cisco Explorer 1540 Specifications Page 398

  • Download
  • Add to my manuals
  • Print
  • Page
    / 924
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 397
6-206
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Enum Definitions for IPAddrAttributes
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).
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.
Page view 397
1 ... 397 398 399 ... 924

Comments to this Manuals

No comments