IPO-PHONES-MIB: View SNMP OID List / Download MIB

Avaya IP Office Phones MIB The MIB module for representing the phones present on a Avaya IP Office stack.

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.

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.

The number of phone interfaces (regardless of their current state) present on this system.

A list of phone entries. The number of entries is given by the value of ipoPhonesNumber.

An entry containing management information applicable to a particular IP Office phone.

A 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.

The numerical logical extension entity identifier assigned to the phone on the IP Office entity.

The number that should be dialed to reach this phone on the IP Office entity.

The 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.

The long form of the name of the user of this phone. This is normally the full name (forename and surname) of the user.

The type of phone that is connected to this IP Office logical phone extension.

A 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.

The 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.

The 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.

The 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).

The 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).

The compliance statement for the IP Office Phones MIB

The compliance statement for the IP Office Phones MIB

The compliance statement for the IP Office Phones MIB

The collection of objects which are used to represent IP Office phones, for which a single agent provides management information.

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

The notifications which indicate specific changes in the state of IP Office phones for newer implementations of this MIB.

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.