ccmFailCauseCode

• 1.3.6.1.4.1.9.9.156.1.10.2
• Access notifyonly
• Type unknown(1), heartBeatStopped(2), routerThreadDied(3), timerThreadDied(4), criticalThreadDied(5), deviceMgrInitFailed(6), digitAnalysisInitFailed(7), callControlInitFailed(8), linkMgrInitFailed(9), dbMgrInitFailed(10), msgTranslatorInitFailed(11), suppServicesInitFailed(12) ?

  unknown(1), heartBeatStopped(2), routerThreadDied(3), timerThreadDied(4), criticalThreadDied(5), deviceMgrInitFailed(6), digitAnalysisInitFailed(7), callControlInitFailed(8), linkMgrInitFailed(9), dbMgrInitFailed(10), msgTranslatorInitFailed(11), suppServicesInitFailed(12)

  This type is not a standard SMI/SNMP base type and is not defined as a documented TEXTUAL-CONVENTION in this MIB.

  It was extracted as raw syntax from the source MIB file and could not be resolved to a known type definition.

The Cause code of the failure. This cause is derived from a monitoring thread in the CallManager or from a heartbeat monitoring process. unknown: Unknown heartBeatStopped: The CallManager stops generating a heartbeat routerThreadDied: The CallManager detects the death of the router thread timerThreadDied: The CallManager detects the death of the timer thread criticalThreadDied: The CallManager detects the death of one of its critical threads deviceMgrInitFailed: The CallManager fails to start its device manager subsystem digitAnalysisInitFailed: The CallManager fails to start its digit analysis subsystem callControlInitFailed: The CallManager fails to start its call control subsystem linkMgrInitFailed: The CallManager fails to start its link manager subsystem dbMgrInitFailed: The CallManager fails to start its database manager subsystem msgTranslatorInitFailed: The CallManager fails to start its message translation manager subsystem suppServicesInitFailed: The CallManager fails to start its supplementary services subsystem.