IPO-PHONES-MIB
Avaya IP Office Phones MIB The MIB module for representing the phones present on a Avaya IP Office stack.
Main OID:
ipoPhonesMIB.1.3.6.1.4.1.6889.2.2.1.1.1
30
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
30 total| Object Name |
|---|
ipoPhonesMIBAvaya IP Office Phones MIB The MIB module for representing the phones present on a Avaya IP Office stack. MODULE-IDENTITY .1.3.6.1.4.1.6889.2.2.1.1.1 |
ipoPhonesMibNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.2.1.1.1.0 |
ipoPhonesChangeEventThis 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.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.6889.2.2.1.1.1.0.1 |
ipoPhonesChangeSvcEventThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.6889.2.2.1.1.1.0.2 |
ipoPhonesMibObjects OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.2.1.1.1.1 |
ipoPhones OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.2.1.1.1.1.1 |
ipoPhonesNumberThe number of phone interfaces (regardless of their current state) present on this system.ro Integer32 .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.1 |
ipoPhonesTableA list of phone entries. The number of entries is given by the value of ipoPhonesNumber. SEQUENCE OF IpoPhonesEntry .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2 |
ipoPhonesEntryAn entry containing management information applicable to a particular IP Office phone. IpoPhonesEntry .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1 |
ipoPhonesIndexA unique value, greater than zero, for each phone. It is recommended that values are assigned contiguously starting from 1. The value for each phone sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.ro IndexInteger (DIFFSERV-MIB) .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.1 |
ipoPhonesExtIDThe numerical logical extension entity identifier assigned to the phone on the IP Office entity.ro Integer32 .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.2 |
ipoPhonesExtNumberThe number that should be dialed to reach this phone on the IP Office entity.ro Integer32 .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.3 |
ipoPhonesUserShortThe short form of the name of the user of this phone which is used in caller display. This is quite often the forename of the user.ro DisplayString .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.4 |
ipoPhonesUserLongThe long form of the name of the user of this phone. This is normally the full name (forename and surname) of the user.ro DisplayString .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.5 |
ipoPhonesTypeThe type of phone that is connected to this IP Office logical phone extension.ro PhoneType .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.6 |
ipoPhonesPortA reference, by entPhysicalIndex value, to the EntPhysicalEntry representing the physical port entity that this phone entry is associated with in an entity MIB instantiation within the IP Office agent. If no MIB definitions specific to the particular media are available, or the entry is for a IP phone which may not be connected to a physical port on the IP Office, the value should be set to the value 0.ro Unsigned32 .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.7 |
ipoPhonesPortNumberThe port number on the module that the operator uses to identify the port. The port numbers on the expansion modules will follow standard numbering, beginning at 1 and incrementing until the last port. The phone ports on the base units, however, are numbered according to how they are collected into 'banks' on the unit. IP Office IP500 The entire front of the product consists of 4 plug-in modules. Each module has its own numbering from 1..12. So from the left: 101..112, 201..212, etc. IP Office IP412 There is no way to plug phones into the unit, so only expansion modules should be present. IP Office IP406v2 The leftmost bank of ports are Digital (DS/DT) and labeled as 1-8 on the product, and so are labelled ports 101..108 in the mib. The next bank of ports are Analogue and labeled as 1-2 on the product and so are labelled ports 201..202 in the mib. The next bank of phones are LAN and labeled as 1-8 on the product. Not phones, so not in this mib. IP Office Small Office Edition The leftmost bank of 4 ports are Trunk ports, and so are not available in this mib. The next bank of 8 ports are Digital (DS/DT), and so are labelled ports 101..108 in the mib. The next bank of 4 ports are Analogue, and so are labelled ports 201..204 in the mib. The next bank of ports are LAN, and so are not available in this mib.ro Unsigned32 .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.8 |
ipoPhonesModuleNumberThe number that the operator uses to identify the module. The module numbers are assigned according to the expansion port number that it's plugged into on the Control unit. Example: Module number '2' = Expansion unit plugged into expansion port 2 on the Control unit. Module number '0' is reserved for the Control unit itself.ro Unsigned32 .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.9 |
ipoPhonesIPAddressThe IP Address of the phone. In network-byte order. In the usual IP Address format - xxx.xxx.xxx.xxx. The IP address will only be present if the phone is an IP phone. If it is not, it will contain zeros (0.0.0.0).ro IpAddress .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.10 |
ipoPhonesPhysAddressThe Physical Address of the phone, such as the MAC Address. The physical address will only be present if the phone is an IP phone. If it is not, it will contain zeros (00.00.00.00.00.00).ro PhysAddress (SNMPv2-TC) .1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.11 |
ipoPhonesConformance OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.2.1.1.1.2 |
ipoPhonesCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.2.1.1.1.2.1 |
ipoPhonesComplianceThe compliance statement for the IP Office Phones MIBdeprecated Unknown .1.3.6.1.4.1.6889.2.2.1.1.1.2.1.1 |
ipoPhonesv2ComplianceThe compliance statement for the IP Office Phones MIBdeprecated Unknown .1.3.6.1.4.1.6889.2.2.1.1.1.2.1.2 |
ipoPhonesv3ComplianceThe compliance statement for the IP Office Phones MIB Unknown .1.3.6.1.4.1.6889.2.2.1.1.1.2.1.3 |
ipoPhonesGroups OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.2.1.1.1.2.2 |
ipoPhonesGroupThe collection of objects which are used to represent IP Office phones, for which a single agent provides management information. Unknown .1.3.6.1.4.1.6889.2.2.1.1.1.2.2.1 |
ipoPhonesNotificationsGroupThe notifications which indicate specific changes in the state of IP Office phones.deprecated Unknown .1.3.6.1.4.1.6889.2.2.1.1.1.2.2.2 |
ipoPhonesv2NotificationsGroupThe notifications which indicate specific changes in the state of IP Office phones for newer implementations of this MIB. Unknown .1.3.6.1.4.1.6889.2.2.1.1.1.2.2.3 |
ipoPhones2GroupAdditional 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. Unknown .1.3.6.1.4.1.6889.2.2.1.1.1.2.2.4 |
More MIBs from Avaya
Browse all AvayaMIBs →G3-AVAYA-MIB
Standard SNMP MIB module defining data structures for G3-AVAYA-MIB.
4281 objects→
G700-MG-MIB
SNMP MIB module
367 objects→
Avaya-96xxIPTelephone-MIB
The Avaya-96xxIPTelephone-MIB enables SNMP-based monitoring and management of Avaya 96xx series IP telephones running Release S3.1, providing access to device-specific operational metrics such as call session states, network interface statistics, hardware status indicators, and firmware versioning data.
248 objects→
Avaya-46xxIPTelephone-MIB
The Avaya-46xxIPTelephone-MIB facilitates SNMP-based monitoring and management of Avaya 46xx series IP telephones (firmware through Release 2.8) by exposing device status, port statistics, call session states, and power consumption metrics compliant with COMPAS 75441 standards.
225 objects→
Avaya_46xxIPTelephone-MIB
The Avaya_46xxIPTelephone-MIB enables SNMP-based monitoring and management of Avaya 46xx series IP telephones (up to Release 2.8) by exposing device operational status, port statistics, and call session metrics defined in the COMPAS 75441 specification.
225 objects→
IPO-PROD-MIB
The IPO-PROD-MIB module registers specific sysObjectID values to uniquely identify Avaya IP Office telephone switches within an SNMP management station, enabling the differentiation of these hardware devices from other network elements during monitoring and polling operations.
179 objects→