IPO-PHONES-MIB

        Avaya IP Office Phones MIB
        
The MIB module for representing the phones present on a Avaya
IP Office stack.
    
Source file
IPO-PHONES-MIB
Last revised
Identity
ipoPhonesMIB
Base OID
1.3.6.1.4.1.6889.2.2.1.1.1
Imported Objects
DIFFSERV-MIB IndexInteger
IPO-MIB ipoGenMibs ipoGTEventDateTime ipoGTEventDevID ipoGTEventEntityName ipoGTEventSeverity ipoGTEventStdSeverity
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-MIB sysDescr
SNMPv2-SMI Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString PhysAddress TEXTUAL-CONVENTION (no object page)
Net-SNMP examples using the avaya MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'IPO-PHONES-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IPO-PHONES-MIB::ipoPhonesMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'IPO-PHONES-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'IPO-PHONES-MIB::ipoPhonesMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (21)
.1.3.6.1.4.1.6889.2.2.1.1.1
.1.3.6.1.4.1.6889.2.2.1.1.1.0
.1.3.6.1.4.1.6889.2.2.1.1.1.1
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.1
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.1
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.10
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.11
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.2
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.3
OctetString
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.4
OctetString
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.5
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.6
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.7
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.8
.1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.9
.1.3.6.1.4.1.6889.2.2.1.1.1.2
.1.3.6.1.4.1.6889.2.2.1.1.1.2.1
.1.3.6.1.4.1.6889.2.2.1.1.1.2.2
Dependencies (14) 6 direct · 8 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (1)
Enumeration
noPhone(1)
genericPhone(2)
potPhone(3)
dtPhone(4)
a4406Dplus(5)
a4412Dplus(6)
a4424Dplus(7)
a4424LDplus(8)
a9040TransTalk(9)
a6408Dplus(10)
a6416Dplus(11)
a6424Dplus(12)
a4606ip(13)
a4612ip(14)
a4624ip(15)
a4620ip(16)
a4602ip(17)
a2420(18)
a2010dt(19)
a2020dt(20)
a2030dt(21)
a2050dt(22)
act5(23)
att3(24)
att5(25)
a5420(26)
a5410(27)
a4601ip(28)
a4610ip(29)
ablf(30)
a2402(31)
a2410(32)
a5610ip(33)
a5620ip(34)
softIPPhone(35)
a5601ip(36)
a5602ip(37)
a4621ip(38)
a5621ip(39)
a4625ip(40)
a5402(41)
h323Phone(42)
sipPhone(43)
t3Compact(44)
t3Classic(45)
t3Comfort(46)
t3Phone(47)
t3compactIP(48)
t3classicIP(49)
t3comfortIP(50)
avayaSip(51)
admmPhone(52)
a9620ip(53)
a9630ip(54)
telecommuter(55)
mobiletwin(56)
a9640ip(57)
a9650ip(58)
a9610ip(59)
a1603ip(60)
a1608ip(61)
a1616ip(62)
a1703ip(63)
a1708ip(64)
a1716ip(65)
s60Sip(66)
sp320Sip(67)
sp601Sip(68)
a10ataSip(69)
pmataSip(70)
ip22Sip(71)
ip24Sip(72)
gxp2000Sip(73)
gxp2020Sip(74)
eyebeamSip(75)
a1403(76)
a1408(77)
a1416(78)
a1450(79)
ip28Sip(80)
phoneManagerIP(81)
a1503(82)
a1508(83)
a1516(84)
a1550(85)
a1603Lip(86)
a1608Lip(87)
a1616Lip(88)
softPhoneSip(89)
etr34d(90)
etr18d(91)
etr6d(92)
etr34(93)
etr18(94)
etr6(95)
etrpots(96)
doorphone1(97)
doorphone2(98)
bstT7316e(99)
a9620Sip(100)
a9630Sip(101)
a9640Sip(102)
a9650Sip(103)
a96xxSip(104)
a1603Sip(105)
a9404(106)
a9408(107)
a9504(108)
a9508(109)
a9608ip(110)
a9611ip(111)
a9621ip(112)
a9641ip(113)
a3720Admm(114)
a3725Admm(115)
a1010Sip(116)
a1040Sip(117)
a1120ESip(118)
a1140ESip(119)
a1220Sip(120)
a1230Sip(121)
a1692Sip(122)
pvvxSip(123)
gxv3140Sip(124)
a3740Admm(125)
a3749Admm(126)
bstT7316(127)
bstT7208(128)
bstM7208(129)
bstM7310(130)
bstM7310blf(131)
bstM7324(132)
bstM7100(133)
bstT7100(134)
bstT7000(135)
bstDectA(136)
bstDectB(137)
bstDectC(138)
bstDoorphone(139)
bstT7406(140)
bstT7406E(141)
bstM7310N(142)
bstAcu(143)
bstM7100N(144)
bstM7324N(145)
bstM7208N(146)
aB179Sip(147)
bstAta(148)
aA175Sip(149)
aOneXSip(150)
aFlareSip(151)
aD100(152)
aRadvisionXT1000(153)
aRadvisionXT1200(154)
aRadvisionXT4000(155)
aRadvisionXT4200(156)
aRadvisionXT5000(157)
aRadvisionXTPiccolo(158)
aRadvisionScopiaMCU(159)
aRadvisionScopiaVC240(160)
aOneXSipMobile(161)
aACCSServer(162)
aCIEServer(163)
aE129SIP(164)
aE159SIP(165)
aE169SIP(166)
aOneXMsiSIP(167)
aRadvisionXT240(168)
aWebRTCSIP(169)
softPhoneSipMac(170)
Conformance Groups (4)
The collection of objects which are used to represent IP
Office phones, for which a single agent provides management
information.
.1.3.6.1.4.1.6889.2.2.1.1.1.2.2.1
The notifications which indicate specific changes in the
state of IP Office phones.
.1.3.6.1.4.1.6889.2.2.1.1.1.2.2.2
The notifications which indicate specific changes in the
state of IP Office phones for newer implementations of this
MIB.
.1.3.6.1.4.1.6889.2.2.1.1.1.2.2.3
Additional collection of objects which are used to represent
physical information about IP Office phones, for which a
single agent provides management information. These objects
provide more information on where phones are directly
connected to an IP Office and further details on IP Phones for
their identification.
.1.3.6.1.4.1.6889.2.2.1.1.1.2.2.4
Compliance Statements (3)

OID .1.3.6.1.4.1.6889.2.2.1.1.1.2.1.1
The compliance statement for the IP Office Phones MIB
Required groups

OID .1.3.6.1.4.1.6889.2.2.1.1.1.2.1.2
The compliance statement for the IP Office Phones MIB
Required groups

OID .1.3.6.1.4.1.6889.2.2.1.1.1.2.1.3
The compliance statement for the IP Office Phones MIB
Required groups
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.6889.2.2.1.1.1.0.1
This notification is generated whenever the type of phone
connected to a logical extension entity is detected as having
changed after completion of normal start up of the Agent
entity.

Its purpose is to allow a management application to identify
the removal or switching of phone types on the IP Office
entity.

**NOTE: This notification is deprecated and replaced by
ipoPhonesChangeSvcEvent.
.1.3.6.1.4.1.6889.2.2.1.1.1.0.2
This notification is generated whenever the type of phone
connected to a logical extension entity is detected as having
changed after completion of normal start up of the Agent
entity.

Its purpose is to allow a management application to identify
the removal or switching of phone types on the IP Office
entity.

Newer implementations of this MIB should put in place this
event in favour of ipoPhonesChangeEvent.