OXO-CALL-HANDLING-MIB

This is ALE Communication implementation of
enterprise specific MIB for the OmniPCX Office Call Handling.
    

Imported Objects

oxoMIB, EventSeverityOXO-MIB
MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, Integer32, TimeTicksSNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString, DateAndTimeSNMPv2-TC

Type Definitions (3)

Name Base Type Values/Constraints
AlarmEventTypeEnumerationunknown(0), change-Value(1), communication-Alarm(2), environmental-Alarm(3), equipment-Alarm(4), object-Creation(6), object-Deletion(7), processing-Error-Alarm(10), quality-Of-Service-Alarm(11), change-State(14)
AlarmProbableCauseEnumerationunknown(0), adapter-Error(1), application-Subsystem-Failure(2), band-Width-Reduced(3), call-Establishment-Error(4), communications-Protocol-Error(5), communications-Subsystem-Failure(6), configuration-Or-Customization-Error(7), congestion(8), corrupt-Data(9), cpu-Cycles-Limit-Exceeded(10), data-Set-Or-Modem-Error(11), degraded-Signal(12), dte-Dce-Interface-Error(13), enclosure-Door-Open(14), equipment-Mal-Function(15), excessive-Vibration(16), file-Error(17), fire-Detected(18), flood-Detected(19), framing-Error(20), heating-Ventilation-Cooling-System-Problem(21), humidity-Unacceptable(22), input-Output-Device-Error(23), input-Device-Error(24), lAN-Error(25), leak-Detected(26), local-Node-Transmission-Error(27), loss-Of-Frame(28), loss-Of-Signal(29), material-Supply-Exhausted(30), multiplexer-Problem(31), out-Of-Memory(32), output-Device-Error(33), performance-Degraded(34), power-Problem(35), pressure-Unacceptable(36), processor-Problem(37), pump-Failure(38), queue-Size-Exceeded(39), receive-Failure(40), receiver-Failure(41), remote-Node-Transmission-Failure(42), resource-At-Or-Nearing-Capacity(43), response-Time-Excessive(44), retransmission-Rate-Excessive(45), softwar-eError(46), software-Program-Ab-normally-Terminated(47), software-Program-Error(48), storage-Capacity-Problem(49), temperature-Unacceptable(50), threshold-Crossed(51), timing-Problem(52), toxic-Leak-Detected(53), transmit-Failure(54), transmitter-Failure(55), underlying-Resource-Unavailable(56), version-Mismatch(57)
AlarmTypeListEnumerationurgent(1), hardware(2), history(3)

Objects

oxoCallHandlingMIB .1.3.6.1.4.1.6486.64.4200.1.2
ochmObjects .1.3.6.1.4.1.6486.64.4200.1.2.1
ochmStatus
.1.3.6.1.4.1.6486.64.4200.1.2.1.1
ochmAlarmTable .1.3.6.1.4.1.6486.64.4200.1.2.2
ochmAlarmEntry .1.3.6.1.4.1.6486.64.4200.1.2.2.1
ochmAlarmTypeINDEX .1.3.6.1.4.1.6486.64.4200.1.2.2.1.0
ochmAlarmTableType .1.3.6.1.4.1.6486.64.4200.1.2.2.1.1
ochmAlarmInfo1 .1.3.6.1.4.1.6486.64.4200.1.2.2.1.10
ochmAlarmInfo2 .1.3.6.1.4.1.6486.64.4200.1.2.2.1.11
ochmAlarmInfo3 .1.3.6.1.4.1.6486.64.4200.1.2.2.1.12
ochmAlarmInfo4 .1.3.6.1.4.1.6486.64.4200.1.2.2.1.13
ochmAlarmType .1.3.6.1.4.1.6486.64.4200.1.2.2.1.14
ochmAlarmSeverity
.1.3.6.1.4.1.6486.64.4200.1.2.2.1.15
ochmAlarmCause .1.3.6.1.4.1.6486.64.4200.1.2.2.1.16
ochmAlarmIndex .1.3.6.1.4.1.6486.64.4200.1.2.2.1.2
ochmAlarmSystTime
.1.3.6.1.4.1.6486.64.4200.1.2.2.1.3
ochmAlarmDateTime
.1.3.6.1.4.1.6486.64.4200.1.2.2.1.4
ochmAlarmEvent .1.3.6.1.4.1.6486.64.4200.1.2.2.1.5
ochmAlarmSubEvent .1.3.6.1.4.1.6486.64.4200.1.2.2.1.6
ochmAlarmCabinetSlot .1.3.6.1.4.1.6486.64.4200.1.2.2.1.7
ochmAlarmBoardSlot .1.3.6.1.4.1.6486.64.4200.1.2.2.1.8
ochmAlarmHalfBoard .1.3.6.1.4.1.6486.64.4200.1.2.2.1.9
ochmNotificationPrefix .1.3.6.1.4.1.6486.64.4200.1.2.3
ochmNotifications .1.3.6.1.4.1.6486.64.4200.1.2.3.0
ochmNotificationObjects .1.3.6.1.4.1.6486.64.4200.1.2.3.1
ochmProblemId .1.3.6.1.4.1.6486.64.4200.1.2.3.1.1
ochmNotifPbxIncidentNumber .1.3.6.1.4.1.6486.64.4200.1.2.3.1.10
ochmNotifAlarmId .1.3.6.1.4.1.6486.64.4200.1.2.3.1.11
ochmNotifEventType .1.3.6.1.4.1.6486.64.4200.1.2.3.1.12
ochmNotifManagedObject .1.3.6.1.4.1.6486.64.4200.1.2.3.1.13
ochmNotifProbableCause .1.3.6.1.4.1.6486.64.4200.1.2.3.1.14
ochmNotifCorrelation .1.3.6.1.4.1.6486.64.4200.1.2.3.1.15
ochmNotifPbxReceptionTime .1.3.6.1.4.1.6486.64.4200.1.2.3.1.16
ochmNmcTicketNumber .1.3.6.1.4.1.6486.64.4200.1.2.3.1.17
ochmAlarmTime .1.3.6.1.4.1.6486.64.4200.1.2.3.1.18
ochmAlarmNumberEvent .1.3.6.1.4.1.6486.64.4200.1.2.3.1.19
ochmCabinetIndex .1.3.6.1.4.1.6486.64.4200.1.2.3.1.2
ochmEquipementInfo .1.3.6.1.4.1.6486.64.4200.1.2.3.1.20
ochmComplementInfo .1.3.6.1.4.1.6486.64.4200.1.2.3.1.21
ochmEventType .1.3.6.1.4.1.6486.64.4200.1.2.3.1.22
ochmProbableCause .1.3.6.1.4.1.6486.64.4200.1.2.3.1.23
ochmSeverity .1.3.6.1.4.1.6486.64.4200.1.2.3.1.24
ochmAlarmName .1.3.6.1.4.1.6486.64.4200.1.2.3.1.25
ochmBoardIndex .1.3.6.1.4.1.6486.64.4200.1.2.3.1.3
ochmFanId .1.3.6.1.4.1.6486.64.4200.1.2.3.1.4
ochmAccessIndex .1.3.6.1.4.1.6486.64.4200.1.2.3.1.5
ochmInterfaceNumber .1.3.6.1.4.1.6486.64.4200.1.2.3.1.6
ochmSenderType .1.3.6.1.4.1.6486.64.4200.1.2.3.1.7
ochmNotifFaultId .1.3.6.1.4.1.6486.64.4200.1.2.3.1.8
ochmNotifProblemState .1.3.6.1.4.1.6486.64.4200.1.2.3.1.9

Notifications/Traps

NameOIDDescription
ochmSystemRestart









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.1
andling has started running.
          
Correlation:
===========
  ochmSystemRestart and ochmSystemRestarted can be
  correlated when the variable ProblemId has the same value
          
  ochmSystemRestart: opening of the alarm
  ochmSystemRestarted: closing of the alarm
ochmFanFailure









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.10
 anomaly.
          
Correlation:
===========
  ochmFanFailure and ochmFanOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmFanFailure: opening of the alarm
  ochmFanOperational: closing of the alarm
ochmFanOperational









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.11
 is operational.
          
Correlation:
===========
  ochmFanFailure and ochmFanOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmFanFailure: opening of the alarm
  ochmFanOperational: closing of the alarm
ochmIsdnFailure









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.12
s is out of service.
          
Correlation:
===========
  ochmIsdnFailure and ochmIsdnOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmIsdnFailure: opening of the alarm
  ochmIsdnOperational: closing of the alarm
ochmIsdnOperational









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.13
s is back in service.
          
Correlation:
===========
  ochmIsdnFailure and ochmIsdnOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmIsdnFailure: opening of the alarm
  ochmIsdnOperational: closing of the alarm
ochmVoipLinkDown









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.14
nterface of an IP-LAN board is down.
          
Correlation:
===========
  ochmVoipLinkDown and ochmVoipLinkUp can be 
  correlated when the variable ProblemId has the same value
          
  ochmVoipLinkDown: opening of the alarm
  ochmVoipLinkUp: closing of the alarm
ochmVoipLinkUp









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.15
nterface of an IP-LAN board is up.
          
Correlation:
===========
  ochmVoipLinkDown and ochmVoipLinkUp can be 
  correlated when the variable ProblemId has the same value
          
  ochmVoipLinkDown: opening of the alarm
  ochmVoipLinkUp: closing of the alarm
ochmIbsSynchroDown









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.16
st synchronization on UA link: the link is down.
          
Correlation:
===========
  ochmIbsSynchroDown and ochmIbsSynchroUp can be 
  correlated when the variable ProblemId has the same value
          
  ochmIbsSynchroDown: opening of the alarm
  ochmIbsSynchroUp: closing of the alarm
ochmIbsSynchroUp









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.17
st synchronization on UA link: the link is up.
          
Correlation:
===========
  ochmIbsSynchroDown and ochmIbsSynchroUp can be 
  correlated when the variable ProblemId has the same value
          
  ochmIbsSynchroDown: opening of the alarm
  ochmIbsSynchroUp: closing of the alarm
ochmNotifUnknownIncident










.1.3.6.1.4.1.6486.64.4200.1.2.3.0.18
A trap that notify a PABX incident with UNKNOWN severity
ochmNotifCriticalIncident










.1.3.6.1.4.1.6486.64.4200.1.2.3.0.19
A trap that notify a PABX incident with CRITICAL severity
ochmSystemRestarted









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.2
andling has finished its start.
          
Correlation:
===========
  ochmSystemRestart and ochmSystemRestarted can be 
  correlated when the variable ProblemId has the same value
          
  ochmSystemRestart: opening of the alarm
  ochmSystemRestarted: closing of the alarm
ochmNotifMajorIncident










.1.3.6.1.4.1.6486.64.4200.1.2.3.0.20
A trap that notify a PABX incident with MAJOR severity
ochmNotifMinorIncident










.1.3.6.1.4.1.6486.64.4200.1.2.3.0.21
A trap that notify a PABX incident with MINOR severity
ochmNotifWarningIncident










.1.3.6.1.4.1.6486.64.4200.1.2.3.0.22
A trap that notify a PABX incident with WARNING severity
ochmNotifIndeterminateIncident










.1.3.6.1.4.1.6486.64.4200.1.2.3.0.23
A trap that notify a PABX incident with INDETERMINATE severity
ochmNotifState


.1.3.6.1.4.1.6486.64.4200.1.2.3.0.24
A trap that notify a problem state change
ochmAnoRegisterReject









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.25
SIP Registration rejected on OXO
ochmRemoteAccessMbxLocked









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.26
e access to voice mail box is currently locked
Correlation:
===========
   ochmRemoteAccessMbxLocked and ochmRemoteAccessMbxUnlocked can be 
   correlated when the variable ProblemId has the same value
          
   ochmRemoteAccessMbxLocked: opening of the alarm
   ochmRemoteAccessMbxUnlocked: closing of the alarm
ochmRemoteAccessMbxUnlocked









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.27
 access to voice mail box is currently unlocked
Correlation:
===========
  ochmRemoteAccessMbxLocked and ochmRemoteAccessMbxUnlocked can be 
  correlated when the variable ProblemId has the same value
          
  ochmRemoteAccessMbxLocked: opening of the alarm
  ochmRemoteAccessMbxUnlocked: closing of the alarm
ochmRemoteAccessWsapiLocked









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.28
 access to web services API is currently locked
Correlation:
===========
  ochmRemoteAccessWsapiLocked and ochmRemoteAccessWsapiUnlocked can be 
  correlated when the variable ProblemId has the same value
          
  ochmRemoteAccessWsapiLocked: opening of the alarm
  ochmRemoteAccessWsapiUnlocked: closing of the alarm
ochmRemoteAccessWsapiUnlocked









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.29
 access to web services API is currently unlocked
Correlation:
===========
  ochmRemoteAccessWsapiLocked and ochmRemoteAccessWsapiUnlocked can be 
  correlated when the variable ProblemId has the same value
          
  ochmRemoteAccessWsapiLocked: opening of the alarm
  ochmRemoteAccessWsapiUnlocked: closing of the alarm
ochmCabinetUnplugged









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.3
has been plugged out.
          
Correlation:
===========
  ochmCabinetUnplugged and ochmCabinetOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmCabinetUnplugged: opening of the alarm
  ochmCabinetOperational: closing of the alarm
ochmArpSpoofInfo









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.30
ng detected. Multiple ARP 
reply received within lock-time period
ochmDefaultPasswordFound









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.31
Default passwords found in Management/ SIP Phone Administrator passwords
ochmEasyPasswordFound









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.32
Easy passwords found in Management/ User passwords
ochmDhcpServerExited









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.33
ted due to bad configuration or option definition 
error or IP address not in subnet or restart failed
ochmDhcpServerStatus









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.34
Server status changed
ochmAnoQuarantineAlert









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.35
An IP address is added in quarantine
ochmMgtsrvLock









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.36
system management is locked due to 6 consecutive
authentication failures with in 5 minutes
ochmMgtsrvUnlock









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.37
system management is unlocked after 6 consecutive
authentication failures in 5 minutes
ochmMsdbHealthStatus









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.39
MSDB is approaching its end of life
due to increase in block erase count / bad blocks
ochmCabinetOperational









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.4
is now operational.
          
Correlation:
===========
  ochmCabinetUnplugged and ochmCabinetOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmCabinetUnplugged: opening of the alarm
  ochmCabinetOperational: closing of the alarm
ochmAnoPrinterFault









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.40
APThis error is reported by the Formatter 
every N unsuccessful attempts to print.
		Report of anomaly depends on the value attached to the 
		nothworthly address, named «PrintFault»
ochmAnoMemoryAvail









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.41
ot enough memory to start an application 
(mailing, custo, ...). When this problem occurs, 
there is less than 15% of free memory
ochmTermRebootOrResetOfUserData









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.42
Reboot of IP terminal or reset of user data.
ochmBoardTempReset









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.43
y reset has been performed on a board (selective maintenance). 
The reset reason is either a hardware anomaly, or the board 
is not responding anymore. (Not used in wall mounted)
ochmThresholdHardwareTBL









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.44
The critical threshold of the hardware anomaly table is reached (80% full).
ochmThresholdHistoryTBL









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.45
The critical threshold of the history events table is reached (80% full).
ochmThresholdMeteringTBL









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.46
The critical threshold of the metering table is reached (80% full).
ochmThresholdUrgentTBL









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.47
The critical threshold of the urgent alarm table is reached (80% full).
ochmNmcMeteringTblFull









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.48
The metering table is full (100%)
ochmAnoNoeDLDFail









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.49
This event is sent when a NOE TDM terminal downloading fails
ochmBoardFailure









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.5
s been plugged out.
          
Correlation:
===========
 1/ First correlation
    -----------------
  ochmBoardFailure and ochmBoardCleared can be 
  correlated when the variable ProblemId has the same value
          
  ochmBoardFailure: opening of the alarm
  ochmBoardCleared: closing of the alarm
          
 2/ Second correlation
    ------------------
  ochmBoardFailure and ochmBoardOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmBoardFailure: opening of the alarm
  ochmBoardOperational: closing of the alarm
ochmAnoPraAlarm









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.50
An alarm has been detected on a primary rate access
ohcmPasswordAuthenticationLocked









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.51
User password authentication is locked
ohcmPasswordAuthenticationUnlocked









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.52
User password authentication is unlocked
ochmLocalMgtPwdReset









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.53
nagement passwords have been locally reset to
a random value.
These management passwords MUST be modified within the
limited time frame (in minute) indicated in the first byte
of the ochmComplementInfo field.
          
Correlation:
===========
  ochmLocalMgtPwdReset and ochmLocalMgtPwdOperational can be
  correlated when the variable ProblemId has the same value
          
  ochmLocalMgtPwdReset opening of the alarm
  ochmLocalMgtPwdOperational closing of the alarm
ochmLocalMgtPwdOperational









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.54
nagement passwords are now operationals. The sub-event
information given in ochmAlarmEvent field indicates the action
which solves this problem:
   2 - they have been restored to their previous values after
       expiration of the limited time frame
   3 - they have been updated on time
          
Correlation:
===========
  ochmLocalMgtPwdReset and ochmLocalMgtPwdOperational can be
  correlated when the variable ProblemId has the same value
          
  ochmLocalMgtPwdReset opening of the alarm
  ochmLocalMgtPwdOperational closing of the alarm
ochmAnoCCStatusConnectionSuccess









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.55
the CC connection state:
CC connection success
-------------
Byte 1: Cause
0x00: No cause
0x01: First OXO startup      0x02: OXO startup
0x03: CC Agent startup       0x04: FTR done
0x05: CC disabled            0x06: CC enabled
0x07: CC reconnection after a disconnection due to network troubles
0x08: CC reconnection after a disconnection due to a ping timeout
-----------------------
Byte 2: CC account type
00: No param
01: Activation account     02: Final account
ochmAnoCCStatusDisconnectionSuccess









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.56
the CC connection state:
CC disconnection success
-------------
Byte 1: Cause
00: No cause
0x01: First OXO startup      0x02: OXO startup
0x03: CC Agent startup       0x04: FTR done
0x05: CC disabled            0x06: CC enabled
0x07: CC reconnection after a disconnection due to network troubles
0x08: CC reconnection after a disconnection due to a ping timeout
-----------------------
Byte 2: CC account type
00: No param
01: Activation account     02: Final account
ochmAnoCCStatusFTRDone









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.57
the CC connection state:
FTR Done
-------------
Byte 1: Cause
00: No cause
0x01: First OXO startup      0x02: OXO startup
0x03: CC Agent startup       0x04: FTR done
0x05: CC disabled            0x06: CC enabled
0x07: CC reconnection after a disconnection due to network troubles
0x08: CC reconnection after a disconnection due to a ping timeout
-----------------------
Byte 2: CC account type
00: No param
01: Activation account     02: Final account
ochmAnoCCFailureConnectionFailed









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.58
 CC connection
CC connection failed
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error                             0x0A: Stream close
0x0B: Proxy authentication required                    0x0C: Proxy authentication failed
0x0D: Proxy no supported authentication                0x0E: Connection refused
0x0F: DNS error                                        0x10: No supported authentication
0x11: TLS failed                                       0x12: TLS not available
0x13: Connection compression failed                    0x14: Input/Output error
0x15: Parse error                                      0x16: Out of memory
0x17: Authentication failed                            0x18: Service unreachable
0x19: Service non respondind                           0x1A: Invalid input
0x1B: Inconsistent product state                       0x1C: Service internal failure
0x1D: Bad version                                      0x1E: Bad format
0x1F: OXO not subscribed to the Pubsub node            0X20: No persistent item on the Pubsub node
0x21: Item retrieval not supported on the Pubsub node  0X22: OXO is not in the Pubsub node white list
0X23: OXO has a bad affiliation for the Pubsub node    0x24: Pubsub node does not exist
-------------------------------------
Byte 2: CC account type or CC service
0x00: No type
0x01: Activation account        0x02: Final account
0x03: FTR Service               0x04: SA Service
------------------------
Byte 3: Other parameters
0x00: No param                  0x01: SA Pubsub node for service list
ochmAnoCCFailureIntAgentError









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.59
 CC connection
Internal CC Agent error
-------------
Byte 1: Cause
0x00: No cause
0x0A: Stream version error                             0x09: Stream close
0x0B: Proxy authentication required                    0x0C: Proxy authentication failed
0x0D: Proxy no supported authentication                0x0E: Connection refused
0x0F: DNS error                                        0x10: No supported authentication
0x11: TLS failed                                       0x12: TLS not available
0x13: Connection compression failed                    0x14: Input/Output error
0x15: Parse error                                      0x16: Out of memory
0x17: Authentication failed                            0x18: Service unreachable
0x19: Service non respondind                           0x1A: Invalid input
0x1B: Inconsistent product state                       0x1C: Service internal failure
0x1D: Bad version                                      0x1E: Bad format
0x1F: OXO not subscribed to the Pubsub node            0X20: No persistent item on the Pubsub node
0x21: Item retrieval not supported on the Pubsub node  0X22: OXO is not in the Pubsub node white list
0X23: OXO has a bad affiliation for the Pubsub node    0x24: Pubsub node does not exist
-------------------------------------
Byte 2: CC account type or CC service
0x00: No type
0x01: Activation account        0x02: Final account
0x03: FTR Service               0x04: SA Service
------------------------
Byte 3: Other parameters
0x00: No param                  0x01: SA Pubsub node for service list
ochmBoardCleared









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.6
t reset has been performed on a board.
          
Correlation:
===========
  ochmBoardFailure and ochmBoardCleared can be 
  correlated when the variable ProblemId has the same value
          
  ochmBoardFailure: opening of the alarm
  ochmBoardCleared: closing of the alarm
ochmAnoCCFailureConnectionLost









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.60
 CC connection
CC connection lost
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error                             0x0A: Stream close
0x0B: Proxy authentication required                    0x0C: Proxy authentication failed
0x0D: Proxy no supported authentication                0x0E: Connection refused
0x0F: DNS error                                        0x10: No supported authentication
0x11: TLS failed                                       0x12: TLS not available
0x13: Connection compression failed                    0x14: Input/Output error
0x15: Parse error                                      0x16: Out of memory
0x17: Authentication failed                            0x18: Service unreachable
0x19: Service non respondind                           0x1A: Invalid input
0x1B: Inconsistent product state                       0x1C: Service internal failure
0x1D: Bad version                                      0x1E: Bad format
0x1F: OXO not subscribed to the Pubsub node            0X20: No persistent item on the Pubsub node
0x21: Item retrieval not supported on the Pubsub node  0X22: OXO is not in the Pubsub node white list
0X23: OXO has a bad affiliation for the Pubsub node    0x24: Pubsub node does not exist
-------------------------------------
Byte 2: CC account type or CC service
0x00: No type
0x01: Activation account        0x02: Final account
0x03: FTR Service               0x04: SA Service
------------------------
Byte 3: Other parameters
0x00: No param                  0x01: SA Pubsub node for service list
ochmAnoCCFailureBadCredential









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.61
 CC connection
Bad credential
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error                             0x0A: Stream close
0x0B: Proxy authentication required                    0x0C: Proxy authentication failed
0x0D: Proxy no supported authentication                0x0E: Connection refused
0x0F: DNS error                                        0x10: No supported authentication
0x11: TLS failed                                       0x12: TLS not available
0x13: Connection compression failed                    0x14: Input/Output error
0x15: Parse error                                      0x16: Out of memory
0x17: Authentication failed                            0x18: Service unreachable
0x19: Service non respondind                           0x1A: Invalid input
0x1B: Inconsistent product state                       0x1C: Service internal failure
0x1D: Bad version                                      0x1E: Bad format
0x1F: OXO not subscribed to the Pubsub node            0X20: No persistent item on the Pubsub node
0x21: Item retrieval not supported on the Pubsub node  0X22: OXO is not in the Pubsub node white list
0X23: OXO has a bad affiliation for the Pubsub node    0x24: Pubsub node does not exist
-------------------------------------
Byte 2: CC account type or CC service
0x00: No type
0x01: Activation account        0x02: Final account
0x03: FTR Service               0x04: SA Service
------------------------
Byte 3: Other parameters
0x00: No param                  0x01: SA Pubsub node for service list
ochmAnoCCFailureServUnreachable









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.62
 CC connection
Service unreachable
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error                             0x0A: Stream close
0x0B: Proxy authentication required                    0x0C: Proxy authentication failed
0x0D: Proxy no supported authentication                0x0E: Connection refused
0x0F: DNS error                                        0x10: No supported authentication
0x11: TLS failed                                       0x12: TLS not available
0x13: Connection compression failed                    0x14: Input/Output error
0x15: Parse error                                      0x16: Out of memory
0x17: Authentication failed                            0x18: Service unreachable
0x19: Service non respondind                           0x1A: Invalid input
0x1B: Inconsistent product state                       0x1C: Service internal failure
0x1D: Bad version                                      0x1E: Bad format
0x1F: OXO not subscribed to the Pubsub node            0X20: No persistent item on the Pubsub node
0x21: Item retrieval not supported on the Pubsub node  0X22: OXO is not in the Pubsub node white list
0X23: OXO has a bad affiliation for the Pubsub node    0x24: Pubsub node does not exist
-------------------------------------
Byte 2: CC account type or CC service
0x00: No type
0x01: Activation account        0x02: Final account
0x03: FTR Service               0x04: SA Service
------------------------
Byte 3: Other parameters
0x00: No param                  0x01: SA Pubsub node for service list
ochmAnoCCFailureFinalAccountGetting









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.63
 CC connection
Final account getting
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error                             0x0A: Stream close
0x0B: Proxy authentication required                    0x0C: Proxy authentication failed
0x0D: Proxy no supported authentication                0x0E: Connection refused
0x0F: DNS error                                        0x10: No supported authentication
0x11: TLS failed                                       0x12: TLS not available
0x13: Connection compression failed                    0x14: Input/Output error
0x15: Parse error                                      0x16: Out of memory
0x17: Authentication failed                            0x18: Service unreachable
0x19: Service non respondind                           0x1A: Invalid input
0x1B: Inconsistent product state                       0x1C: Service internal failure
0x1D: Bad version                                      0x1E: Bad format
0x1F: OXO not subscribed to the Pubsub node            0X20: No persistent item on the Pubsub node
0x21: Item retrieval not supported on the Pubsub node  0X22: OXO is not in the Pubsub node white list
0X23: OXO has a bad affiliation for the Pubsub node    0x24: Pubsub node does not exist
-------------------------------------
Byte 2: CC account type or CC service
0x00: No type
0x01: Activation account        0x02: Final account
0x03: FTR Service               0x04: SA Service
------------------------
Byte 3: Other parameters
0x00: No param                  0x01: SA Pubsub node for service list
ochmAnoCCFailureFinalAccountACK









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.64
 CC connection
Final account acknowledgement
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error                             0x0A: Stream close
0x0B: Proxy authentication required                    0x0C: Proxy authentication failed
0x0D: Proxy no supported authentication                0x0E: Connection refused
0x0F: DNS error                                        0x10: No supported authentication
0x11: TLS failed                                       0x12: TLS not available
0x13: Connection compression failed                    0x14: Input/Output error
0x15: Parse error                                      0x16: Out of memory
0x17: Authentication failed                            0x18: Service unreachable
0x19: Service non respondind                           0x1A: Invalid input
0x1B: Inconsistent product state                       0x1C: Service internal failure
0x1D: Bad version                                      0x1E: Bad format
0x1F: OXO not subscribed to the Pubsub node            0X20: No persistent item on the Pubsub node
0x21: Item retrieval not supported on the Pubsub node  0X22: OXO is not in the Pubsub node white list
0X23: OXO has a bad affiliation for the Pubsub node    0x24: Pubsub node does not exist
-------------------------------------
Byte 2: CC account type or CC service
0x00: No type
0x01: Activation account        0x02: Final account
0x03: FTR Service               0x04: SA Service
------------------------
Byte 3: Other parameters
0x00: No param                  0x01: SA Pubsub node for service list
ochmAnoCCFailureInconsistentRecData









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.65
 CC connection
Inconsistent received data
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error                             0x0A: Stream close
0x0B: Proxy authentication required                    0x0C: Proxy authentication failed
0x0D: Proxy no supported authentication                0x0E: Connection refused
0x0F: DNS error                                        0x10: No supported authentication
0x11: TLS failed                                       0x12: TLS not available
0x13: Connection compression failed                    0x14: Input/Output error
0x15: Parse error                                      0x16: Out of memory
0x17: Authentication failed                            0x18: Service unreachable
0x19: Service non respondind                           0x1A: Invalid input
0x1B: Inconsistent product state                       0x1C: Service internal failure
0x1D: Bad version                                      0x1E: Bad format
0x1F: OXO not subscribed to the Pubsub node            0X20: No persistent item on the Pubsub node
0x21: Item retrieval not supported on the Pubsub node  0X22: OXO is not in the Pubsub node white list
0X23: OXO has a bad affiliation for the Pubsub node    0x24: Pubsub node does not exist
-------------------------------------
Byte 2: CC account type or CC service
0x00: No type
0x01: Activation account        0x02: Final account
0x03: FTR Service               0x04: SA Service
------------------------
Byte 3: Other parameters
0x00: No param                  0x01: SA Pubsub node for service list
ochmAnoCCFailureEventNodeError









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.66
 CC connection
Event node error
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error                             0x0A: Stream close
0x0B: Proxy authentication required                    0x0C: Proxy authentication failed
0x0D: Proxy no supported authentication                0x0E: Connection refused
0x0F: DNS error                                        0x10: No supported authentication
0x11: TLS failed                                       0x12: TLS not available
0x13: Connection compression failed                    0x14: Input/Output error
0x15: Parse error                                      0x16: Out of memory
0x17: Authentication failed                            0x18: Service unreachable
0x19: Service non respondind                           0x1A: Invalid input
0x1B: Inconsistent product state                       0x1C: Service internal failure
0x1D: Bad version                                      0x1E: Bad format
0x1F: OXO not subscribed to the Pubsub node            0X20: No persistent item on the Pubsub node
0x21: Item retrieval not supported on the Pubsub node  0X22: OXO is not in the Pubsub node white list
0X23: OXO has a bad affiliation for the Pubsub node    0x24: Pubsub node does not exist
-------------------------------------
Byte 2: CC account type or CC service
0x00: No type
0x01: Activation account        0x02: Final account
0x03: FTR Service               0x04: SA Service
------------------------
Byte 3: Other parameters
0x00: No param                  0x01: SA Pubsub node for service list
ochmAnoCCVPNStatus









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.67
VPN connection state
---------------
Byte 1: Request
0x01: start
0x02: stop
0x03: all stopall
--------------
Byte 2:  Cause
0x00: Undefined       0x01: User request
0x02: CC disabled     0x03: CC agent stop
0x04: CC agent start  0x05: Connection supervision
-------
Byte 3: Connection id
-------
Byte 4: Tunnel id
ochmAnoCCVPNFailure









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.68
ser initiated a request to start or stop a VPN. 
The request failed.
---------------
Byte 1: Request
0x01: Start
0x02: Stop
0x03: Stop all
-------------
Byte 2: Cause
0x00: Undefined                0x08: Wrong parameter
0x09: Max connection reached   0x0A: Max tunnel reached
0x0B: Internal error           0x0C: Error during Phase1 establishment
0x0C: Error during Phase2 establishment
----------------------------
Byte 3: Additional parameter
0x00: Undefined              0x01: Query header
0x02: Query version          0x03: Requester
0x04: Organization           0x05: User
0x06: Gateway                0x07: Login
0x08: Password               0x09: Pre Shared Key
0x0A: Connection identifier  0x0B: IKE authentication method
0x0C: IKE port               0xOD: NAT port
0x0E: CA certificate         0x0F: Certificate subject
0x10: Peer id                0x11: Phase1 encryption
0x12: Phase1 hash            0x13: Phase1 DH group
0x14: Phase2 encryption      0x15: Phase2 authentication
0x16: Phase2 PFS group       0x17: Phase2 inativity timer
-----------------
Byte 4: Tunnel id
ochmAnoEmergencyConfig









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.69
No device configured to receive emergency call notification
ochmBoardOperational









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.7
 now operational.
          
Correlation:
===========
  ochmBoardFailure and ochmBoardOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmBoardFailure: opening of the alarm
  ochmBoardOperational: closing of the alarm
ochmSystemAutoProvision









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.70
Auto Provisioning is Activated/Deactivated
ochmAnoRBStatusConnectionSuccess









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.72
the RB connection state:
RB connection success
-------------
Byte 1: Cause
0x00: No cause
0x01: First OXO startup      0x02: OXO startup
0x03: RB Agent startup
0x04: RB disabled            0x05: RB enabled
0x06: RB reconnection after a disconnection due to network troubles
0x07: RB reconnection after a disconnection due to a ping timeout
0x08: RB Agent stop
-----------------------
Byte 2: RB account type
00: No type
01: Activation account     02: Final account
ochmAnoRBStatusDisconnectionSuccess









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.73
the RB connection state:
RB disconnection success
-------------
Byte 1: Cause
00: No cause
0x01: First OXO startup      0x02: OXO startup
0x03: RB Agent startup
0x04: RB disabled            0x05: RB enabled
0x06: RB reconnection after a disconnection due to network troubles
0x07: RB reconnection after a disconnection due to a ping timeout
0x08: RB Agent stop
-----------------------
Byte 2: RB account type
00: No type
01: Activation account     02: Final account
ochmAnoRBFailureConnectionFailed









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.74
 RB connection
RB connection failed
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error                             0x02: Stream close
0x03: Proxy authentication required                    0x04: Proxy authentication failed
0x05: Proxy no supported authentication                0x06: Connection refused
0x07: DNS error                                        0x08: No supported authentication
0x09: TLS failed                                       0x0A: TLS not available
0x0B: Connection compression failed                    0x0C: Input/Output error
0x0D: Parse error                                      0x0E: Out of memory
0x0F: Authentication failed                            0x10: Service unreachable
0x11: Service non respondind                           0x12: Invalid input
0x13: Inconsistent product state                       0x14: Service internal failure
0x15: Bad version                                      0x16: Bad format
-------------------------------------
Byte 2: RB account type
0x00: No type
0x01: Activation account        0x02: Final account
ochmAnoRBFailureIntAgentError









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.75
 RB connection
Internal RB Agent error
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error                             0x02: Stream close
0x03: Proxy authentication required                    0x04: Proxy authentication failed
0x05: Proxy no supported authentication                0x06: Connection refused
0x07: DNS error                                        0x08: No supported authentication
0x09: TLS failed                                       0x0A: TLS not available
0x0B: Connection compression failed                    0x0C: Input/Output error
0x0D: Parse error                                      0x0E: Out of memory
0x0F: Authentication failed                            0x10: Service unreachable
0x11: Service non respondind                           0x12: Invalid input
0x13: Inconsistent product state                       0x14: Service internal failure
0x15: Bad version                                      0x16: Bad format
-------------------------------------
Byte 2: RB account type
0x00: No type
0x01: Activation account        0x02: Final account
ochmAnoRBFailureConnectionLost









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.76
 RB connection
RB connection lost
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error                             0x02: Stream close
0x03: Proxy authentication required                    0x04: Proxy authentication failed
0x05: Proxy no supported authentication                0x06: Connection refused
0x07: DNS error                                        0x08: No supported authentication
0x09: TLS failed                                       0x0A: TLS not available
0x0B: Connection compression failed                    0x0C: Input/Output error
0x0D: Parse error                                      0x0E: Out of memory
0x0F: Authentication failed                            0x10: Service unreachable
0x11: Service non respondind                           0x12: Invalid input
0x13: Inconsistent product state                       0x14: Service internal failure
0x15: Bad version                                      0x16: Bad format
-------------------------------------
Byte 2: RB account type
0x00: No type
0x01: Activation account        0x02: Final account
ochmAnoRBFailureBadCredential









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.77
 RB connection
Bad credential
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error                             0x02: Stream close
0x03: Proxy authentication required                    0x04: Proxy authentication failed
0x05: Proxy no supported authentication                0x06: Connection refused
0x07: DNS error                                        0x08: No supported authentication
0x09: TLS failed                                       0x0A: TLS not available
0x0B: Connection compression failed                    0x0C: Input/Output error
0x0D: Parse error                                      0x0E: Out of memory
0x0F: Authentication failed                            0x10: Service unreachable
0x11: Service non respondind                           0x12: Invalid input
0x13: Inconsistent product state                       0x14: Service internal failure
0x15: Bad version                                      0x16: Bad format
-------------------------------------
Byte 2: RB account type
0x00: No type
0x01: Activation account        0x02: Final account
ochmAnoRBFailureServUnreachable









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.78
 RB connection
Service unreachable
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error                             0x02: Stream close
0x03: Proxy authentication required                    0x04: Proxy authentication failed
0x05: Proxy no supported authentication                0x06: Connection refused
0x07: DNS error                                        0x08: No supported authentication
0x09: TLS failed                                       0x0A: TLS not available
0x0B: Connection compression failed                    0x0C: Input/Output error
0x0D: Parse error                                      0x0E: Out of memory
0x0F: Authentication failed                            0x10: Service unreachable
0x11: Service non respondind                           0x12: Invalid input
0x13: Inconsistent product state                       0x14: Service internal failure
0x15: Bad version                                      0x16: Bad format
-------------------------------------
Byte 2: RB account type
0x00: No type
0x01: Activation account        0x02: Final account
ochmAnoRBFailureFinalAccountGetting









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.79
 RB connection
Final account getting
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error                             0x02: Stream close
0x03: Proxy authentication required                    0x04: Proxy authentication failed
0x05: Proxy no supported authentication                0x06: Connection refused
0x07: DNS error                                        0x08: No supported authentication
0x09: TLS failed                                       0x0A: TLS not available
0x0B: Connection compression failed                    0x0C: Input/Output error
0x0D: Parse error                                      0x0E: Out of memory
0x0F: Authentication failed                            0x10: Service unreachable
0x11: Service non respondind                           0x12: Invalid input
0x13: Inconsistent product state                       0x14: Service internal failure
0x15: Bad version                                      0x16: Bad format
-------------------------------------
Byte 2: RB account type
0x00: No type
0x01: Activation account        0x02: Final account
ochmPowerSupplyFailure


.1.3.6.1.4.1.6486.64.4200.1.2.3.0.8
ower supply went down.
          
Correlation:
===========
  ochmPowerSupplyFailure and ochmPowerSupplyOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmPowerSupplyFailure: opening of the alarm
  ochmPowerSupplyOperational: closing of the alarm
ochmAnoRBFailureFinalAccountACK









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.80
 RB connection
Final account acknowledgement
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error                             0x02: Stream close
0x03: Proxy authentication required                    0x04: Proxy authentication failed
0x05: Proxy no supported authentication                0x06: Connection refused
0x07: DNS error                                        0x08: No supported authentication
0x09: TLS failed                                       0x0A: TLS not available
0x0B: Connection compression failed                    0x0C: Input/Output error
0x0D: Parse error                                      0x0E: Out of memory
0x0F: Authentication failed                            0x10: Service unreachable
0x11: Service non respondind                           0x12: Invalid input
0x13: Inconsistent product state                       0x14: Service internal failure
0x15: Bad version                                      0x16: Bad format
-------------------------------------
Byte 2: RB account type
0x00: No type
0x01: Activation account        0x02: Final account
ochmAnoRBFailureInconsistentRecData









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.81
 RB connection
Inconsistent received data
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error                             0x02: Stream close
0x03: Proxy authentication required                    0x04: Proxy authentication failed
0x05: Proxy no supported authentication                0x06: Connection refused
0x07: DNS error                                        0x08: No supported authentication
0x09: TLS failed                                       0x0A: TLS not available
0x0B: Connection compression failed                    0x0C: Input/Output error
0x0D: Parse error                                      0x0E: Out of memory
0x0F: Authentication failed                            0x10: Service unreachable
0x11: Service non respondind                           0x12: Invalid input
0x13: Inconsistent product state                       0x14: Service internal failure
0x15: Bad version                                      0x16: Bad format
-------------------------------------
Byte 2: RB account type
0x00: No type
0x01: Activation account        0x02: Final account
ochmAnoRBFailureEventNodeError









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.82
 RB connection
Event node error
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error                             0x02: Stream close
0x03: Proxy authentication required                    0x04: Proxy authentication failed
0x05: Proxy no supported authentication                0x06: Connection refused
0x07: DNS error                                        0x08: No supported authentication
0x09: TLS failed                                       0x0A: TLS not available
0x0B: Connection compression failed                    0x0C: Input/Output error
0x0D: Parse error                                      0x0E: Out of memory
0x0F: Authentication failed                            0x10: Service unreachable
0x11: Service non respondind                           0x12: Invalid input
0x13: Inconsistent product state                       0x14: Service internal failure
0x15: Bad version                                      0x16: Bad format
-------------------------------------
Byte 2: RB account type
0x00: No type
0x01: Activation account        0x02: Final account
ochmAnoTempMax









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.83
ature reached.
-------------
Byte 1: temperature
ochmDectSyncTreeKo









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.84
 to build the synchronization tree of xBS: the master is ko.
The DECT site is given by the board parameter.
Correlation:
===========
 1/ First correlation
    -----------------
  ochmDectSyncTreeKo and ochmDectSyncTreeOk can be 
  correlated when the variable ProblemId has the same value
          
  ochmDectSyncTreeKo: opening of the alarm
  ochmDectSyncTreeOk: closing of the alarm
          
 2/ Second correlation
    ------------------
  ochmDectSyncTreeKo and ochmDectSyncAutomatic can be 
  correlated when the variable ProblemId has the same value
          
  ochmDectSyncTreeKo: opening of the alarm
  ochmDectSyncAutomatic: closing of the alarm
ochmDectSyncTreeOk









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.85
 to build the synchronization tree of xBS: the master is ok.
The DECT site is given by the board parameter.
Correlation:
===========
  ochmDectSyncTreeKo and ochmDectSyncTreeOk can be 
  correlated when the variable ProblemId has the same value
          
  ochmDectSyncTreeKo: opening of the alarm
  ochmDectSyncTreeOk: closing of the alarm
ochmDectSyncManual









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.86
ation mode for xBS: manual.
The DECT site is given by the board parameter.
ochmDectSyncAutomatic









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.87
ation mode for xBS: automatic.
The DECT site is given by the board parameter.
Correlation:
===========
  ochmDectSyncTreeKo and ochmDectSyncAutomatic can be 
  correlated when the variable ProblemId has the same value
          
  ochmDectSyncTreeKo: opening of the alarm
  ochmDectSyncAutomatic: closing of the alarm
ochmDectSyncIslandsChanged









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.88
 of islands in the synchronization tree has changed.
The DECT site is given by the board parameter.
The number of islands is given by the byte 1.
The normal value is 0.
When the number gets greater than 0, the DECT synchronization tree in the site has to be analyzed.
Configuration of clusters has to be considered to get in a normal situation.
ochmPowerSupplyOperational









.1.3.6.1.4.1.6486.64.4200.1.2.3.0.9
ower supply is back in service.
          
Correlation:
===========
  ochmPowerSupplyFailure and ochmPowerSupplyOperational can be 
  correlated when the variable ProblemId has the same value
          
  ochmPowerSupplyFailure: opening of the alarm
  ochmPowerSupplyOperational: closing of the alarm