IPO-MIB: View SNMP OID List / Download MIB

Avaya IP Office MIBs OID tree. This MIB module defines the root items for MIBs for use with Avaya IP Office family of telephone switches.

A ipoGenEntityFailureEvent notification is generated whenever a physical entity on the IP Office fails in its operation. It signifies that the SNMP entity, acting in an agent role, has detected that the state of a physical entity of the system has transitioned from the operational to the failed state **NOTE: This notification is deprecated and replaced by ipoGenEntityFailureSvcEvent

A ipoGenEntityOperationalEvent notification is generated whenever a physical entity on the IP Office becomes operational again after having failed. It signifies that the SNMP entity, acting in an agent role, has detected that the state of a physical entity of the system has transitioned from the failed to the operational state **NOTE: This notification is deprecated and replaced by ipoGenEntityOperationalSvcEvent.

A ipoGenEntityErrorEvent notification is generated whenever a physical entity on the IP Office experiences a temporary error. It signifies that the SNMP entity, acting in an agent role, has detected a transitory error on a physical entity of the system. **NOTE: This notification is deprecated and replaced by ipoGenEntityErrorSvcEvent.

A ipoGenEntityChangeEvent notification is generated whenever a physical entity on the IP Office experiences a change itself or with other entities associated with it. It signifies that the SNMP entity, acting in an agent role, has detected a non error/failure change for a physical entity on the system. **NOTE: This notification is deprecated and replaced by ipoGenEntityChangeSvcEvent.

A ipoGenLKSCommsFailureEvent notification is generated whenever communication with a Licence Key Server fails. It signifies that the SNMP entity, acting in an agent role, has detected that the state of the communications between the Licence Key Server has transitioned from the operational to the failed state. **NOTE: This notification is deprecated and replaced by ipoGenLKSCommsFailureSvcEvent.

A ipoGenLKSCommsOperationalEvent notification is generated whenever communication with a Licence Key Server becomes operational again after having failed. It signifies that the SNMP entity, acting in an agent role, has detected that the state of the communications between the Licence Key Server has transitioned from the failed to the operational state. **NOTE: This notification is deprecated and replaced by ipoGenLKSCommsOperationalSvcEvent.

A ipoGenLKSCommsErrorEvent notification is generated whenever a IP Office experiences a temporary error with License Key Server communication. It signifies that the SNMP entity, acting in an agent role, has detected a transitory error with the communication between the License Key Server and Client on the system. **NOTE: This notification is deprecated and replaced by ipoGenLKSCommsErrorSvcEvent.

A ipoGenLKSCommsChangeEvent notification is generated whenever a IP Office experiences a change a non error change License Key Server communication operation. It signifies that the SNMP entity, acting in an agent role, has detected a non error/failure change with the License Key Server and Client operation on the system. **NOTE: This notification is deprecated and replaced by ipoGenLKSCommsChangeSvcEvent.

A ipoGenLoopbackEvent notification is generated whenever a IP Office T1 (DS1) interface operating as a CSU actions a loopback status change. **NOTE: This notification is deprecated and replaced by ipoGenLoopbackSvcEvent.

A ipoGenAppFailureEvent notification is generated whenever communication between a IP Office switch and a IP Office application fails. It signifies that the SNMP entity, acting in an agent role, has detected that the state of the communications between the IP Office switch and a IP Office application has transitioned from the operational to the failed state. The IP Office application between which communication has been lost is identified by the value of ipoGTEventAppEntity. **NOTE: This notification is deprecated and replaced by ipoGenAppFailureSvcEvent.

A ipoGenAppOperationalEvent notification is generated whenever communication between a IP Office switch and a IP Office application becomes operational again after having failed. It signifies that the SNMP entity, acting in an agent role, has detected that the state of the communications between the IP Office switch and a IP Office application has transitioned from the failed to the operational state. The IP Office application between which communication has been lost is identified by the value of ipoGTEventAppEntity. **NOTE: This notification is deprecated and replaced by ipoGenAppOperationalSvcEvent.

A ipoGenAppEvent notification is generated whenever a application entity of the IP Office system experiences an event. It signifies that the SNMP entity, acting as a proxy for the application, has detected an event on the application entity of the overall IP Office system. The event severity varies dependent upon the event condition. **NOTE: This notification is deprecated and replaced by ipoGenAppSvcEvent.

An ipoGenSogFailureEvent notification is generated whenever a previously valid Sub-tending host fails during Small Office Gateway operation. The ipAddress field indicates the address of the failed host. The event severity will always indicate Major. **NOTE: This notification is deprecated and replaced by ipoGenSogHostFailureSvcEvent.

An ipoGenSogModeChangeEvent notification is generated whenever the Small Office Gateway operating mode changes. This also includes entry to the initial mode. The ipoGTEventSOGMode field indicates the new operating mode. The event severity will be major(2) for a ipoGTEventSOGMode value of survivable(1), and minor(3) for a ipoGTEventSOGMode value of subTending(2). **NOTE: This notification is deprecated and replaced by ipoGenSogModeChangeSvcEvent.

Enterprise version of standard coldstart trap featuring device identification information. A coldStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered.

Enterprise version of standard warmstart trap featuring device identification information. A warmStart trap signifies that the sending protocol entity is reinitializing that neither the agent configuration nor the protocol entity implementation is altered.

Enterprise version of standard linkDown trap featuring device identification information. A linkDown trap signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration.

Enterprise version of standard linkUp trap featuring device identification information. A linkUp trap signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come up.

Enterprise version of standard authenticationFailure trap featuring device identification information. An authenticationFailure trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. While implementations of the SNMP must be capable of generating this trap, they must also be capable of suppressing the emission of such traps via an implementation- specific mechanism.

A ipoGenEntityFailureSvcEvent notification is generated whenever a physical entity on the IP Office fails in its operation. It signifies that the SNMP entity, acting in an agent role, has detected that the state of a physical entity of the system has transitioned from the operational to the failed state

A ipoGenEntityOperationalSvcEvent notification is generated whenever a physical entity on the IP Office becomes operational again after having failed. It signifies that the SNMP entity, acting in an agent role, has detected that the state of a physical entity of the system has transitioned from the failed to the operational state

A ipoGenEntityErrorSvcEvent notification is generated whenever a physical entity on the IP Office experiences a temporary error. It signifies that the SNMP entity, acting in an agent role, has detected a transitory error on a physical entity of the system.

A ipoGenEntityChangeSvcEvent notification is generated whenever a physical entity on the IP Office experiences a change itself or with other entities associated with it. It signifies that the SNMP entity, acting in an agent role, has detected a non error/failure change for a physical entity on the system.

A ipoGenLKSCommsFailureSvcEvent notification is generated whenever communication with a Licence Key Server fails. It signifies that the SNMP entity, acting in an agent role, has detected that the state of the communications between the Licence Key Server has transitioned from the operational to the failed state.

A ipoGenLKSCommsOperationalSvcEvent notification is generated whenever communication with a Licence Key Server becomes operational again after having failed. It signifies that the SNMP entity, acting in an agent role, has detected that the state of the communications between the Licence Key Server has transitioned from the failed to the operational state.

A ipoGenLKSCommsErrorSvcEvent notification is generated whenever a IP Office experiences a temporary error with License Key Server communication. It signifies that the SNMP entity, acting in an agent role, has detected a transitory error with the communication between the License Key Server and Client on the system.

A ipoGenLKSCommsChangeSvcEvent notification is generated whenever a IP Office experiences a change a non error change License Key Server communication operation. It signifies that the SNMP entity, acting in an agent role, has detected a non error/failure change with the License Key Server and Client operation on the system.

A ipoGenLoopbackSvcEvent notification is generated whenever a IP Office T1 (DS1) interface operating as a CSU actions a loopback status change.

A ipoGenAppFailureSvcEvent notification is generated whenever communication between a IP Office switch and a IP Office application fails. It signifies that the SNMP entity, acting in an agent role, has detected that the state of the communications between the IP Office switch and a IP Office application has transitioned from the operational to the failed state. The IP Office application between which communication has been lost is identified by the value of ipoGTEventAppEntity.

A ipoGenAppOperationalSvcEvent notification is generated whenever communication between a IP Office switch and a IP Office application becomes operational again after having failed. It signifies that the SNMP entity, acting in an agent role, has detected that the state of the communications between the IP Office switch and a IP Office application has transitioned from the failed to the operational state. The IP Office application between which communication has been lost is identified by the value of ipoGTEventAppEntity.

A ipoGenAppSvcEvent notification is generated whenever a application entity of the IP Office system experiences an event. It signifies that the SNMP entity, acting as a proxy for the application, has detected an event on the application entity of the overall IP Office system. The event severity varies dependent upon the event condition.

An ipoGenSogFailureSvcEvent notification is generated whenever a previously valid Sub-tending host fails during Small Office Gateway operation. The ipAddress field indicates the address of the failed host. The event severity will always indicate major(4).

An ipoGenSogModeChangeSvcEvent notification is generated whenever the Small Office Gateway operating mode changes. This also includes entry to the initial mode. The ipoGTEventSOGMode field indicates the new operating mode. The event severity will be major(4) for a ipoGTEventSOGMode value of survivable(1), and minor(5) for a ipoGTEventSOGMode value of subTending(2).

A ipoGenUPriLicChansReducedSvcEvent notification is generated whenever the number of Universal PRI Licensed channels has been reduced. It signifies that the SNMP entity, acting in an agent role, has detected a reduction in the licensed channels on a Univeral PRI trunk.

A ipoGenUPriLicCallRejectedSvcEvent notification is generated whenever a call on a Universal PRI is rejected due to a licensed channel not being available. It signifies that the SNMP entity, acting in an agent role, has detected a licensed channel not available in order to make a call on a Univeral PRI trunk.

A ipoGenQoSMonSvcEvent notification is generated when one of the monitored QoS parameters (e.g. round trip delay, jitter, packet loss, etc) exceeds its pre-selected threshold during the duration of the call. It signifies that the SNMP entity, acting in an agent role, has detected a state that one of the monitored QoS parameters for the call exceeded its pre-selected threshold. The ipoGTEventQOSMonExtnNo value is only valid when the device monitored is an extension rather than a line.

An ipoGenSystemShutdownSvcEvent notification is generated when a system shutdown is performed. It signifies that the SNMP entity has detected a system shutdown.

An ipoGenSystemRunningBackup notification is generated when a system is running partially or wholly from alternate/backup software and/or configuration data. In the case of an IP500 V2, it indicates that the current boot location is not the System SD card slot, \system\primary.

An ipoGenInvalidMemoryCard notification is generated when a memory card is detected present but cannot be used due to failure in the filesystem or card type checks. The checks are carried out on startup and whenever a memory card is inserted.

A ipoGenNoLicenceKeyDongle notification is generated if a system either does not detect presence, or fails to validate a Licence Feature Key Dongle. In the case of an IP500 V2, it indicates that either the System SD card is not present, or that one of the validation checks has failed. Note that removing the System SD card will cause this event immediately, however the licences will remain valid for approximately 2 hours. ipoGTEventStdSeverity will indicate the events state: Severity is cleared(1): license dongle OK Severity is warning(6): license dongle not OK, in grace period Severity is critical(3): license dongle not OK, grace period expired The first check to fail is contained within ipoGTEventNoKeyReason.

A ipoGenMemoryCardCapacityEvent notification is generated if a memory card passes one of the preset capacity thresholds. In the case of an IP500 V2, the thresholds shall be storageFull(1) - greater than 99% of nominal capacity storageNearlyFull(2) - greater than 90% of nominal capacity storageOkay(3) - less than 90% of nominal capacity.

A ipoGenConfigFailureSvcEvent notification is generated whenever a configuration component fails in its operation. It signifies that the SNMP entity,acting in an agent role,has detected that the state of a configuration component has transitioned from the operational to the failed state. This notification event is associated with a configuration system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenConfigOperationalSvcEvent notification is generated whenever a configuration component becomes operational again after having failed.It signifies that the SNMP entity,acting in an agent role,has detected that the state of a configuration component of thesystem has transitioned from the failed to the operational state. This notification event is associated with a configuration system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenConfigErrorSvcEvent notification is generated whenever a configuration component experiences a temporary error.It signifies that the SNMP entity, acting in an agent role,has detected a transitory error on a configuration component of the system. This notification event is associated with a configuration system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenConfigChangeSvcEvent notification is generated whenever a configuration component experiences a change or a non error change event.It signifies that the SNMP entity, acting in an agent role,has detected a non error/failure change on a configuration component of the system. This notification event is associated with a configuration system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenServiceFailureSvcEvent notification is generated whenever a Service component fails in its operation. It signifies that the SNMP entity,acting in an agent role,has detected that the state of a Service component has transitioned from the operational to the failed state. This notification event is associated with a service system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenServiceOperationalSvcEvent notificationis generated whenever a service component becomes operational again after having failed.It signifiest hat the SNMP entity, acting in an agent role, has detected that the state of a service component of the system has transitioned from the failed to the operational state. This notification event is associated with a service system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenServiceErrorSvcEvent notification is generated whenever a service component experiences a temporary error. It signifiest hat the SNMP entity, acting in an agent role,has detected a transitory error on a service component of the system. This notification event is associated with a service system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenServiceChangeSvcEvent notification is generated whenever a service component experiences a change or a non error change event. It signifies that the SNMP entity, acting in an agent role,has detected a non error/failure change on a service component of the system. This notification event is associated with a service system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenTrunkFailureSvcEvent notification is generated whenever a trunk component fails in its operation. It signifies that the SNMP entity,acting in an agent role,has detected that the state of a Trunk component has transitioned from the operational to the failed state. This notification event is associated with a trunk system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenTrunkOperationalSvcEvent notificationis generated whenever a trunk component becomes operational again after having failed. It signifies that the SNMP entity, acting in an agent role,has detected that the state of a trunk component of the system has transitioned from the failed to the operational state. This notification event is associated with a trunk system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenTrunkErrorSvcEvent notification is generated whenever a trunk component experiences a temporary error. It signifies that the SNMP entity, acting in an agent role, has detected a transitory error on a trunk component of the system. This notification event is associated with a trunk system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenTrunkChangeSvcEvent notification is generated whenever a trunk component experiences a change or a non error change event. It signifies that the SNMP entity, acting in an agent role, has detected a non error/failure change on a trunk component of the system. This notification event is associated with a trunk system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenLinkFailureSvcEvent notification is generated whenever a Link component fails in its operation. It signifies that the SNMP entity,acting in an agent role,has detected that the state of a Link component has transitioned from the operational to the failed state. This notification event is associated with a link system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenLinkOperationalSvcEvent notification is generated whenever a link component becomes operational again after having failed. It signifies that the SNMP entity, acting in an agent role, hasdetected that the state of a link component of the system has transitioned from the failed to the operational state. This notification event is associated with a link system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenLinkErrorSvcEvent notification is generated whenever a link component experiences a temporary error. It signifies that the SNMP entity, acting in an agent role,has detected a transitory error on a link component of thesystem. This notification event is associated with a link system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenLinkChangeSvcEvent notification is generated whenever a link component experiences a change or a non error change event. It signifies that the SNMP entity, acting in an agent role,has detected a non error/failure change on a link component of the system. This notification event is associated with a link system status category alarm. Details about the alarm are provided in the included object variables.

A ipoGenEmergencyCallSvcEvent notification is generated whenever an emergency call is made, regardless whether successfully or not. It signifies that the SNMP entity, acting in an agent role, has detected an emergency call attempt on the system. This notification event is associated with a service system status category alarm. Details about the alarm are provided in the included object variables.

Severity of the event that has occurred. The event severity depends upon the type of entity/notification that the operational state change event relates to: GenEntityEvents: Type of physical Severity entity container critical module major port major Known transient errors for entities have a severity of minor. LKSCommsEvents: Severity is major GenLoopbackEvent: Severity is major GenAppEvents: Severity depends on sub-event Failure/Operational - severity is major Event - severity depends on event condition ipoGenSogEvents: Severity depends on sub-event HostFailure - severity is Major ModeChange: - Mode survivable: severity is Major - Mode subTending: severity is Minor PhoneChangeEvents: Severity is minor **NOTE: This object is deprecated and replaced by ipoGTEventStdSeverity. Enumeration: 'major': 2, 'critical': 1, 'minor': 3.

Date and time of the occurence of the event.

A reference, by entPhysicalIndex value, to the EntPhysicalEntry representing the physical entity that an event is associated with in an entity MIB instantiation within the IP Office agent.

This variable represents the current state of the loopback on the DS1 interface. It contains information about loopbacks established by a manager and remotely from the far end. The ipoGTEventLoopbackStatus is a bit map represented as a sum, therefore is can represent multiple loopbacks simultaneously. The various bit positions are: 1 noLoopback 2 nearEndPayloadLoopback 4 nearEndLineLoopback 8 nearEndOtherLoopback 16 nearEndInwardLoopback 32 farEndPayloadLoopback 64 farEndLineLoopback

The IP Office application to which a notification/trap relates. Enumeration: 'deltaServer': 2, 'voiceMail': 1, 'customerCallReporter': 3, 'oneXPortal': 4.

IP Office application event states. The associated event severity of the notification/trap the object is carried in varies depending upon the event condition. The appropriate severity is detailed against event enumeration. Enumeration: 'imapMessageInvalid': 15, 'storageNearlyFull': 2, 'tooManyClients': 70, 'smtpConnectionTimeout': 42, 'backupFileError': 5, 'loginFailureInvalidMailbox': 32, 'httpSslConnection': 8, 'smgrSettingsError': 40, 'imapNotConfigured': 21, 'onexError': 37, 'imapInvalidMsgNr': 13, 'imapMissingConnection': 18, 'storageFull': 1, 'imapShiftConnection': 22, 'imapMessageNrNotExist': 17, 'testTimeExpired': 64, 'pbxIncompatibility': 39, 'imapNoLicence': 20, 'vmScript': 73, 'mapiMissingSettings': 24, 'socketTimedOutError': 57, 'socketBindError': 48, 'licenceExpired': 29, 'makeLiveMissingFile': 35, 'tftpReadingError': 67, 'tcpAcceptError': 60, 'mapiShiftConnection': 26, 'socketNoresponseError': 51, 'imapInitializationFailed': 12, 'tcpError': 63, 'socketClientDisconnectedError': 49, 'socketRecvFailedError': 54, 'smtpUnsuportedData': 46, 'socketOptionError': 52, 'tcpListenError': 61, 'tftpMonitoringError': 66, 'socketSendFailedError': 55, 'httpSslAcceptFailure': 7, 'makeLiveFileAccess': 34, 'smtpConnectionFailed': 41, 'ignoringRequest': 11, 'httpSslFailure': 9, 'imapMailboxNotExist': 14, 'imapMissingSettings': 19, 'socketAbortingError': 47, 'smtpError': 43, 'storageOkay': 3, 'socketSelectError': 56, 'tftpWrittingError': 69, 'switchedToPrimary': 58, 'smtpUnexpectedData': 45, 'socketConnectionError': 50, 'licence': 27, 'updateEerror': 71, 'pbxConnectionLost': 38, 'switchedToSecondary': 59, 'httpSslPortFailure': 10, 'imapMessageNotExist': 16, 'mapiInitializationFailed': 23, 'socketReceiveError': 53, 'smtpSecureConnectionFailed': 44, 'httpFailure': 6, 'backupCommunicationError': 4, 'updateSuccess': 72, 'tcpSelectError': 62, 'mapiConnectionFailed': 25, 'licenceDistributed': 28, 'licenceSOG': 30, 'loginFailure': 31, 'tftpConnectionError': 65, 'offlineMakeLive': 36, 'mailboxNotFound': 33, 'tftpReceivingError': 68.

Address of an IP Office Small Office Gateway Subtending Host.

IP Office Small Office Gateway operating modes. survivable(1) indicates the control unit has no current host, either through confguration error or communication failure. subTending(2) indicates normal operation to a valid Sub- tending Host. Enumeration: 'subTending': 2, 'survivable': 1.

Severity of the event that has occurred. The event severity depends upon the type of entity/notification that the operational state change event relates to. The severity values that are normally used are detailed below: The enterprise versions of standard SNMP traps all have a severity of major (4). Operational events which notify the transition back to an operational state from a failure state have a severity of cleared (1). GenEntityEvents: Operational - severity is cleared (1) Failure event severity levels Type of physical Severity for failure entity container critical (3) module major (4) port major (4) Error Known transient errors for entities have a severity of warning (6). Change - severity is major (4) LKSCommsSvcEvents: Operational - severity is cleared (1) Failure - severity is major (4) GenLoopbackSvcEvent: Severity is major (4) GenAppSvcEvents: Severity depends on sub-event Operational - severity is cleared (1) Failure - severity is major (4) Event - severity depends on event condition For voicemail storage conditions the severity is as follows: storageOkay - severity is cleared (1) storageNearlyFull - severity is warning (6) (Only warning severity as it could be transitory.) storageFull - severity is critical (3) GenSogSvcEvents: Severity depends on sub-event HostFailure - severity is Major (4) ModeChange: - Mode survivable: severity is Major (4) - Mode subTending: severity is Minor (5) GenUPriLicSvcEvents: Severity depends on sub-event ChansReduced - severity is Major (4) CallRejected - severity is Minor (5) GenQoSMonSvcEvent: QoSWarning - severity is Warning (6) PhoneChangeSvcEvents: Severity is minor (5) ipoGenSystemRunningBackupEvent: Severity is cleared (1) Severity is critical (3) ipoGenInvalidMemoryCardEvent: Severity is cleared (1) Severity is Major (4) ipoGenNoLicenceKeyDongleEvent: Severity is cleared (1) Severity is warning (6) Severity is critical (3) ipoGenMemoryCardCapacityEvent: Severity depends on sub-event storageOkay - severity is cleared (1) storageNearlyFull - severity is warning (6) storageFull - severity is critical (3)

A unique textual identifier of the alarming device.

The textual name of the alarming physical entity. The contents of this object is made of concatenated entPhysicalName values that fully identify the object with the overall IP Office entity. Examples values are: Controller, Trunk Slot B, Trunk Module, T1 PRI 2 = T1 PRI Port 2, on a dual T1 Trunk Module, in Trunk Slot B, on the IP Office Controller Unit Controller, VCM Slot 1, VCM 1 = VCM Card, in VCM Slot 1, on the IP Office Controller Unit Controller, EXP 1, DS EXP 16, DS 12 = DS Phone Port 12, on a DS16 Expansion Module, attached to Expansion Port 1, on the IP Office Controller Unit

This variable represents the current state of the loopback on the DS1 interface. It contains information about loopbacks established by a manager and remotely from the far end. The ipoGTEventLoopbackStatus is a bit map therefore is can represent multiple loopbacks simultaneously. Bits: 'nearEndPayloadLoopback': 1, 'nearEndInwardLoopback': 4, 'noLoopback': 0, 'farEndPayloadLoopback': 5, 'nearEndOtherLoopback': 3, 'nearEndLineLoopback': 2, 'farEndLineLoopback': 6.

IP Office QoS monitoring Received Jitter time in milliseconds.

IP Office QoS monitoring Round Trip Delay time in milliseconds.

IP Office QoS monitoring Received Packet Loss.

IP Office QoS monitoring Call Identifier.

IP Office QoS monitoring Device Type. Enumeration: 'extn': 2, 'line': 1.

IP Office QoS monitoring Device Identifier.

IP Office QoS monitoring Extension Number.

This variable represents the source from where the system shutdown was performed. Possible values are: DTE-Port - if the system shutdown is performed using the DTE, AUX-Button - if the system shutdown is performed using the AUX button (available only for IP500v2), Phone - if the system shutdown is performed from a phone, Manager - if the system shutdown is performed from Manager, SSA - if the system shutdown is performed from SSA.

This variable represents the period of time the system will be in the shutdown state for. Possible values are in the 5 to 1440 minutes range, 0 meaning infinite.

This variable indicates a memory card physical position identifier. System(2) and Optional(3) are valid for the IP500 V2. CF(1) valid for the IP500. Enumeration: 'systemSD': 2, 'optionalSD': 3, 'compactFlash': 1.

This variable indicates the reason no valid licence feature key is assumed. This is also the order of importance and check precedence. noReason(1) - cleared condition notPresent(2) - license feature key no present noRegisterAccess(3) - license feature key present, but no access invalidRegisters(4) - invalid register values invalidWatermark(5) - watermark invalid or not present invalidClusterSize(6) - filesystem not as expected Enumeration: 'noReason': 1, 'invalidClusterSize': 6, 'invalidVolume': 7, 'noRegisterAccess': 3, 'invalidHeaderFiles': 8, 'invalidRegisters': 4, 'invalidWatermark': 5, 'notPresent': 2, 'nonSpecificError': 9.

This variable indicates what event took place within Configuration, Service, Trunk or Link category alarm Enumeration: 'serviceTimeServerAlarm': 30, 'linkResourceDown': 27, 'serviceLicenseServerError': 38, 'configurationAgentNotTargeted': 1, 'serviceGeneralAlarm': 74, 'serviceDuplicateIpAddress': 48, 'serviceMemoryAlarm': 59, 'serviceFeatureLicenseMissing': 5, 'serviceSipRxPacketSizeError': 63, 'serviceAlarm': 12, 'configAppsProcAlarm': 36, 'serviceAllLicensesInUse': 6, 'linkVMProConnFailure': 29, 'scepNoRespError': 35, 'serviceNetworkInterconnectFailure': 13, 'serviceAllResourcesInUse': 11, 'trunkMediaSecuritySettingsIncompatible': 79, 'trunkBlueAlarm': 21, 'serviceAppsProcAlarm': 37, 'serviceLocalBackup': 60, 'linkDeviceChanged': 25, 'serviceNoFreeChannelsAvail': 9, 'serviceEmergencyCall': 55, 'serviceIPDECTSystemError': 72, 'serviceTooManyMissedHeartbeats': 46, 'serviceCpuAlarm': 57, 'serviceLicenseFileInvalid': 31, 'serviceAdditionalHardDriveAlarm': 66, 'trunkNoFreeVoIPChannel': 54, 'serviceSystemInfo': 75, 'serviceLocationCongestion': 56, 'trunkSIPDNSInvalidConfig': 68, 'testAlarm': 39, 'serviceClockSourceChanged': 7, 'trunkDDIIncomplete': 17, 'servicePortRangeExhausted': 52, 'servicePlannedMaintenance': 40, 'trunkOOS': 19, 'trunkLOS': 18, 'trunkSIPDNSTransportError': 69, 'trunkRedAlarm': 20, 'securityError': 33, 'serviceNetworkDisconnection': 41, 'serviceCCRNotSupported': 77, 'configurationNoIncomingCallRoute': 3, 'trunkSMConnectAsSIP': 61, 'serviceInternalError': 45, 'serviceSystemHardDriveAlarm': 65, 'serviceSslVpnServerReportedError': 51, 'linkSMTPServerCommFailure': 28, 'trunkCLINotDelivered': 16, 'serviceHoldMusicFileFailure': 10, 'serviceLicenseError': 32, 'serviceFailedTlsRenegotiation': 43, 'serviceWebservicesUWSError': 53, 'serviceFailedDnsResolution': 47, 'serviceLogonFailed': 8, 'linkDialerConnFailure': 67, 'serviceAuthenticationFailure': 49, 'serviceAMServerNotAvailable': 78, 'trunkSeizeFailure': 14, 'serviceFailedTlsNegotiation': 42, 'serviceIPOCCAlarm': 73, 'trunkSIPConnectAsSM': 62, 'serviceCpuIOAlarm': 58, 'serviceSslVpnStackProtocolError': 50, 'serviceNonSelectAlarm': 76, 'configurationHWTypeFailure': 4, 'linkLDAPServerCommFailure': 26, 'serviceACCSAlarm': 64, 'monitorLogStamped': 70, 'trunkYellowAlarm': 22, 'serviceLackOfResources': 44, 'trunkSCNInvalidConnection': 24, 'configurationSCNDialPlanConflict': 2, 'codecError': 34, 'trunkIncomingCallOutgoingTrunk': 15, 'trunkSCNInvalidSubOperMode': 71, 'trunkIPConnectFail': 23.

This variable contains opaque data that can be used to provide additional information when the ipoGTEventReason value is not sufficient.

This variable describes the alarm

This variable describes the remedial action of the alarm

The compliance statement for IP Office agents which implement up to and including version 1.00.05 of this MIB.

The compliance statement for IP Office agents which implement version 1.00.06 and later versions of this MIB.

The compliance statement for IP Office agents which implement version 1.01.01 and later versions of this MIB.

The compliance statement for IP Office agents which implement version 2.00.01 and later versions of this MIB.

The compliance statement for IP Office agents which implement version 2.00.04 and later versions of this MIB.

The compliance statement for IP Office agents which implement version 2.00.03 and later versions of this MIB.

The compliance statement for IP Office agents which implement version 2.00.07 and later versions of this MIB.

Objects that are contained in IP Office wide notifications. **NOTE: This group is deprecated and replaced by ipoGenv2NotificationObjectsGroup.

The notifications which indicate specific changes in the state of the IP Office system. **NOTE: This group is deprecated and replaced by ipoGenSvcNotificationsGroup.

Objects that are contained in IP Office SOG notifications.

The notifications which indicate specific changes in the state of the IP Office SOG system. **NOTE: This group is deprecated and replaced by ipoGenSvcNotificationsGroup.

Objects that are contained in IP Office wide notifications.

IP Office Enterpise versions of the generic traps as defined RFC1215 that provide more identification of the entity concerned.

The service notifications which indicate specific changes in the state of the IP Office system.

The service notifications which indicate specific changes in the state of the IP Office SOG system.

The service notifications which indicate specific changes related to the state licensing and Universal PRI trunks on the IP Office system.

Additional objects that are contained in IP Office QOS Monitoring notifications.

The service notifications which indicate specific changes related to the value of QoS parameters for a call on a physical entity on the IP Office system.

Additional objects that are contained in the system shutdown notification

The service notifications which indicate specific changes related to the system shutdown performed on the IP Office system.

Additional objects that are contained in IP Office SD card notifications.

The notifications associated with IP Office SD card usage.

Additional objects that are contained in IP Office notifications to provide additional information to end user

The notifications indicating change in status related to four areas: Configuration, Sevice, Trunk and Link