ochmRemoteAccessMbxLocked
OXO-CALL-HANDLING-MIB ·
.1.3.6.1.4.1.6486.64.4200.1.2.3.0.26
Object
notification
:the remote 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
Context
- MIB
- OXO-CALL-HANDLING-MIB
- OID
.1.3.6.1.4.1.6486.64.4200.1.2.3.0.26- Type
- notification
- Status
- current
- Parent
- ochmNotifications
- Siblings
- 85
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| ochmSystemRestart The call handling has started running.
Correlation:
===========
ochmSystemRestart and ochmSystemRestarted can be
correlated when the variable ProblemId has the same… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.1 |
| ochmFanFailure Fan status anomaly.
Correlation:
===========
ochmFanFailure and ochmFanOperational can be
correlated when the variable ProblemId has the same value
oc… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.10 |
| ochmFanOperational Fan status is operational.
Correlation:
===========
ochmFanFailure and ochmFanOperational can be
correlated when the variable ProblemId has the same value
… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.11 |
| ochmIsdnFailure A T2 access is out of service.
Correlation:
===========
ochmIsdnFailure and ochmIsdnOperational can be
correlated when the variable ProblemId has the same value
… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.12 |
| ochmIsdnOperational A T2 access is back in service.
Correlation:
===========
ochmIsdnFailure and ochmIsdnOperational can be
correlated when the variable ProblemId has the same value
… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.13 |
| ochmVoipLinkDown Ethernet interface of an IP-LAN board is down.
Correlation:
===========
ochmVoipLinkDown and ochmVoipLinkUp can be
correlated when the variable ProblemId has the s… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.14 |
| ochmVoipLinkUp Ethernet interface of an IP-LAN board is up.
Correlation:
===========
ochmVoipLinkDown and ochmVoipLinkUp can be
correlated when the variable ProblemId has the sam… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.15 |
| ochmIbsSynchroDown IBS has lost synchronization on UA link: the link is down.
Correlation:
===========
ochmIbsSynchroDown and ochmIbsSynchroUp can be
correlated when the variable Pro… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.16 |
| ochmIbsSynchroUp IBS has lost synchronization on UA link: the link is up.
Correlation:
===========
ochmIbsSynchroDown and ochmIbsSynchroUp can be
correlated when the variable Probl… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.17 |
| ochmNotifUnknownIncident A trap that notify a PABX incident with UNKNOWN severity | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.18 |
| ochmNotifCriticalIncident A trap that notify a PABX incident with CRITICAL severity | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.19 |
| ochmSystemRestarted The call handling has finished its start.
Correlation:
===========
ochmSystemRestart and ochmSystemRestarted can be
correlated when the variable ProblemId has the … | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.2 |
| ochmNotifMajorIncident A trap that notify a PABX incident with MAJOR severity | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.20 |
| ochmNotifMinorIncident A trap that notify a PABX incident with MINOR severity | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.21 |
| ochmNotifWarningIncident A trap that notify a PABX incident with WARNING severity | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.22 |
| ochmNotifIndeterminateIncident A trap that notify a PABX incident with INDETERMINATE severity | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.23 |
| ochmNotifState A trap that notify a problem state change | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.24 |
| ochmAnoRegisterReject SIP Registration rejected on OXO | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.25 |
| ochmRemoteAccessMbxUnlocked the remote access to voice mail box is currently unlocked
Correlation:
===========
ochmRemoteAccessMbxLocked and ochmRemoteAccessMbxUnlocked can be
correlated when the variab… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.27 |
| ochmRemoteAccessWsapiLocked the remote access to web services API is currently locked
Correlation:
===========
ochmRemoteAccessWsapiLocked and ochmRemoteAccessWsapiUnlocked can be
correlated when the va… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.28 |
| ochmRemoteAccessWsapiUnlocked the remote access to web services API is currently unlocked
Correlation:
===========
ochmRemoteAccessWsapiLocked and ochmRemoteAccessWsapiUnlocked can be
correlated when the … | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.29 |
| ochmCabinetUnplugged A cabinet has been plugged out.
Correlation:
===========
ochmCabinetUnplugged and ochmCabinetOperational can be
correlated when the variable ProblemId has the same… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.3 |
| ochmArpSpoofInfo ARP spoofing detected. Multiple ARP
reply received within lock-time period | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.30 |
| ochmDefaultPasswordFound Default passwords found in Management/ SIP Phone Administrator passwords | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.31 |
| ochmEasyPasswordFound Easy passwords found in Management/ User passwords | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.32 |
| ochmDhcpServerExited Server exited due to bad configuration or option definition
error or IP address not in subnet or restart failed | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.33 |
| ochmDhcpServerStatus Server status changed | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.34 |
| ochmAnoQuarantineAlert An IP address is added in quarantine | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.35 |
| ochmMgtsrvLock Access to system management is locked due to 6 consecutive
authentication failures with in 5 minutes | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.36 |
| ochmMgtsrvUnlock Access to system management is unlocked after 6 consecutive
authentication failures in 5 minutes | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.37 |
| ochmMsdbHealthStatus : eMMC in MSDB is approaching its end of life
due to increase in block erase count / bad blocks | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.39 |
| ochmCabinetOperational A cabinet is now operational.
Correlation:
===========
ochmCabinetUnplugged and ochmCabinetOperational can be
correlated when the variable ProblemId has the same v… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.4 |
| ochmAnoPrinterFault Default TRAPThis 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… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.40 |
| ochmAnoMemoryAvail There is not enough memory to start an application
(mailing, custo, ...). When this problem occurs,
there is less than 15% of free memory | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.41 |
| ochmTermRebootOrResetOfUserData Reboot of IP terminal or reset of user data. | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.42 |
| ochmBoardTempReset A temporary 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… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.43 |
| ochmThresholdHardwareTBL The critical threshold of the hardware anomaly table is reached (80% full). | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.44 |
| ochmThresholdHistoryTBL The critical threshold of the history events table is reached (80% full). | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.45 |
| ochmThresholdMeteringTBL The critical threshold of the metering table is reached (80% full). | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.46 |
| ochmThresholdUrgentTBL The critical threshold of the urgent alarm table is reached (80% full). | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.47 |
| ochmNmcMeteringTblFull The metering table is full (100%) | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.48 |
| ochmAnoNoeDLDFail This event is sent when a NOE TDM terminal downloading fails | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.49 |
| ochmBoardFailure A board has been plugged out.
Correlation:
===========
1/ First correlation
-----------------
ochmBoardFailure and ochmBoardCleared can be
correlated when the… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.5 |
| ochmAnoPraAlarm An alarm has been detected on a primary rate access | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.50 |
| ohcmPasswordAuthenticationLocked User password authentication is locked | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.51 |
| ohcmPasswordAuthenticationUnlocked User password authentication is unlocked | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.52 |
| ochmLocalMgtPwdReset All the management 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 firs… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.53 |
| ochmLocalMgtPwdOperational All the management passwords are now operationals. The sub-event
information given in ochmAlarmEvent field indicates the action
which solves this problem:
2 - they have been re… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.54 |
| ochmAnoCCStatusConnectionSuccess Change in the CC connection state:
CC connection success
-------------
Byte 1: Cause
0x00: No cause
0x01: First OXO startup 0x02: OXO startup
0x03: CC Agent startup 0x0… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.55 |
| ochmAnoCCStatusDisconnectionSuccess Change in the CC connection state:
CC disconnection success
-------------
Byte 1: Cause
00: No cause
0x01: First OXO startup 0x02: OXO startup
0x03: CC Agent startup 0x… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.56 |
| ochmAnoCCStatusFTRDone Change in 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
0x0… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.57 |
| ochmAnoCCFailureConnectionFailed Failure on CC connection
CC connection failed
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error 0x0A: Stream close
0x0B: Proxy auth… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.58 |
| ochmAnoCCFailureIntAgentError Failure on CC connection
Internal CC Agent error
-------------
Byte 1: Cause
0x00: No cause
0x0A: Stream version error 0x09: Stream close
0x0B: Proxy a… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.59 |
| ochmBoardCleared A permanent reset has been performed on a board.
Correlation:
===========
ochmBoardFailure and ochmBoardCleared can be
correlated when the variable ProblemId has t… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.6 |
| ochmAnoCCFailureConnectionLost Failure on CC connection
CC connection lost
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error 0x0A: Stream close
0x0B: Proxy authen… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.60 |
| ochmAnoCCFailureBadCredential Failure on CC connection
Bad credential
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error 0x0A: Stream close
0x0B: Proxy authentica… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.61 |
| ochmAnoCCFailureServUnreachable Failure on CC connection
Service unreachable
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error 0x0A: Stream close
0x0B: Proxy authe… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.62 |
| ochmAnoCCFailureFinalAccountGetting Failure on CC connection
Final account getting
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error 0x0A: Stream close
0x0B: Proxy aut… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.63 |
| ochmAnoCCFailureFinalAccountACK Failure on CC connection
Final account acknowledgement
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error 0x0A: Stream close
0x0B: P… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.64 |
| ochmAnoCCFailureInconsistentRecData Failure on CC connection
Inconsistent received data
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error 0x0A: Stream close
0x0B: Prox… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.65 |
| ochmAnoCCFailureEventNodeError Failure on CC connection
Event node error
-------------
Byte 1: Cause
0x00: No cause
0x09: Stream version error 0x0A: Stream close
0x0B: Proxy authenti… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.66 |
| ochmAnoCCVPNStatus Change in VPN connection state
---------------
Byte 1: Request
0x01: start
0x02: stop
0x03: all stopall
--------------
Byte 2: Cause
0x00: Undefined 0x01: User request
0x02… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.67 |
| ochmAnoCCVPNFailure A remote user 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
0x… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.68 |
| ochmAnoEmergencyConfig No device configured to receive emergency call notification | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.69 |
| ochmBoardOperational A board is now operational.
Correlation:
===========
ochmBoardFailure and ochmBoardOperational can be
correlated when the variable ProblemId has the same value
… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.7 |
| ochmSystemAutoProvision Auto Provisioning is Activated/Deactivated | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.70 |
| ochmAnoRBStatusConnectionSuccess Change in 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 … | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.72 |
| ochmAnoRBStatusDisconnectionSuccess Change in 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… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.73 |
| ochmAnoRBFailureConnectionFailed Failure on RB connection
RB connection failed
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error 0x02: Stream close
0x03: Proxy auth… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.74 |
| ochmAnoRBFailureIntAgentError Failure on RB connection
Internal RB Agent error
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error 0x02: Stream close
0x03: Proxy a… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.75 |
| ochmAnoRBFailureConnectionLost Failure on RB connection
RB connection lost
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error 0x02: Stream close
0x03: Proxy authen… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.76 |
| ochmAnoRBFailureBadCredential Failure on RB connection
Bad credential
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error 0x02: Stream close
0x03: Proxy authentica… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.77 |
| ochmAnoRBFailureServUnreachable Failure on RB connection
Service unreachable
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error 0x02: Stream close
0x03: Proxy authe… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.78 |
| ochmAnoRBFailureFinalAccountGetting Failure on RB connection
Final account getting
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error 0x02: Stream close
0x03: Proxy aut… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.79 |
| ochmPowerSupplyFailure The main power supply went down.
Correlation:
===========
ochmPowerSupplyFailure and ochmPowerSupplyOperational can be
correlated when the variable ProblemId has t… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.8 |
| ochmAnoRBFailureFinalAccountACK Failure on RB connection
Final account acknowledgement
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error 0x02: Stream close
0x03: P… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.80 |
| ochmAnoRBFailureInconsistentRecData Failure on RB connection
Inconsistent received data
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error 0x02: Stream close
0x03: Prox… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.81 |
| ochmAnoRBFailureEventNodeError Failure on RB connection
Event node error
-------------
Byte 1: Cause
0x00: No cause
0x01: Stream version error 0x02: Stream close
0x03: Proxy authenti… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.82 |
| ochmAnoTempMax Max temperature reached.
-------------
Byte 1: temperature | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.83 |
| ochmDectSyncTreeKo Impossible to build the synchronization tree of xBS: the master is ko.
The DECT site is given by the board parameter.
Correlation:
===========
1/ First correlation
----------… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.84 |
| ochmDectSyncTreeOk Impossible to build the synchronization tree of xBS: the master is ok.
The DECT site is given by the board parameter.
Correlation:
===========
ochmDectSyncTreeKo and ochmDectSyn… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.85 |
| ochmDectSyncManual Synchronization mode for xBS: manual.
The DECT site is given by the board parameter. | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.86 |
| ochmDectSyncAutomatic Synchronization mode for xBS: automatic.
The DECT site is given by the board parameter.
Correlation:
===========
ochmDectSyncTreeKo and ochmDectSyncAutomatic can be
correlate… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.87 |
| ochmDectSyncIslandsChanged The number 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.
… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.88 |
| ochmPowerSupplyOperational The main power supply is back in service.
Correlation:
===========
ochmPowerSupplyFailure and ochmPowerSupplyOperational can be
correlated when the variable Proble… | notification | - | .1.3.6.1.4.1.6486.64.4200.1.2.3.0.9 |
Notification Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| ochmSenderType Type of notification sender | scalar | Enumeration | .1.3.6.1.4.1.6486.64.4200.1.2.3.1.7 |
| ochmSeverity Severity of incident | scalar | Enumeration | .1.3.6.1.4.1.6486.64.4200.1.2.3.1.24 |
| ochmAlarmTime Date of Alarm Ticket | scalar | OctetString | .1.3.6.1.4.1.6486.64.4200.1.2.3.1.18 |
| ochmAlarmName Alarm name incident | scalar | Enumeration | .1.3.6.1.4.1.6486.64.4200.1.2.3.1.25 |
| ochmAlarmEvent An integer that acts as an alarm Id NMC
to uniquely identify each alarm.(Different than OXO Id Event) | column | SNMPv2-SMIInteger32 | .1.3.6.1.4.1.6486.64.4200.1.2.2.1.5 |
| ochmEquipementInfo Information about Board, Half-board and Slot | scalar | OctetString | .1.3.6.1.4.1.6486.64.4200.1.2.3.1.20 |
| ochmComplementInfo Complement information of Alarm Ticket | scalar | OctetString | .1.3.6.1.4.1.6486.64.4200.1.2.3.1.21 |
| ochmEventType Type of Event | scalar | Enumeration | .1.3.6.1.4.1.6486.64.4200.1.2.3.1.22 |
| ochmProbableCause Probable cause of incident | scalar | Enumeration | .1.3.6.1.4.1.6486.64.4200.1.2.3.1.23 |