CcmDevRegFailCauseCode

• Base type Enumeration

This syntax is used as means of identifying the reasons for a device registration failure. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. protocolMismatch: The protocol of the device (SIP or SCCP) does not match the configured protocol in CUCM. deviceNotActive: The device has not been activated. authenticatedDeviceAlreadyExists: A device with the same name is already registered with CUCM. obsoleteProtocolVersion: The SCCP device registered with an obsolete protocol version. databaseTimeout: CUCM requested device configuration data from the database but did not receive a response within 10 minutes. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. This is applicable for SCCP protocol only. invalidCapabilities: The CUCM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. This is applicable for SCCP protocol only. capabilityResponseTimeout: The CUCM timed out while waiting for the device to respond to a request to report its media capabilities. 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 CUCM node is experiencing high CPU usage. Verify that the device is powered up and operating. Verify that network connectivity exists between the device and CUCM, and verify that the CPU utilization is in the safe range. This is applicable for SCCP protocol only. securityMismatch: The CUCM detected a mismatch in the security settings of the device and/or the CUCM. The mismatches that can be detected are: 1) The device established a secure connection, yet reported that it does not have the ability to do authenticated signaling. 2) The device did not establish a secure connection, but the security mode configured for the device indicates that it should have done so. 3) The device established a secure connection, but the security mode configured for the device indicates that it should not have done so autoRegisterDBError: Auto-registration of a device failed for one of the following reasons: 1)Auto-registration is not allowed for the device type. 2)An error occurred while adding the auto-registering device to the database (stored procedure). dbAccessError: Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. autoRegisterDBConfigTimeout: The CUCM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. This is applicable for SCCP protocol only. deviceTypeMismatch: The device type reported by the device does not match the device type configured on the CUCM addressingModeMismatch: The CUCM detected an error related to the addressing mode configured for the device. One of the following errors were detected: 1)The device is configured to use only IPv4 addressing, but did not specify an IPv4 address. 2)The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. This is applicable for SCCP protocol only.