All MIBs › IPO-PHONES-MIB › ipoPhonesPortNumber
ipoPhonesPortNumber
Module: IPO-PHONES-MIB
OID (symbolic): IPO-PHONES-MIB::ipoPhonesPortNumber
OID (numeric): 1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.8
Node type: OBJECT-TYPE
Type: Unsigned32
Access: read-only
Description: 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.
What is ipoPhonesPortNumber?
This object reports the port number, as labeled by the operator, that this phone is connected to, following a numbering scheme specific to the IP Office model and module type, such as 101-112 for the first plug-in module on an IP500, or separate digital and analogue port banks on an IP406v2. Administrators use it to physically locate exactly which labeled port a given phone is plugged into on a specific expansion module or base unit. For example, a phone showing port number 105 on an IP500 system is plugged into port 5 of the first plug-in module.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.8 snmpwalk -v2c -c public <target> IPO-PHONES-MIB::ipoPhonesPortNumber
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.8.1 snmpget -v2c -c public <target> IPO-PHONES-MIB::ipoPhonesPortNumber.1
Start monitoring Avaya IP phone systems with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the IPO-PHONES-MIB::ipoPhonesPortNumber OID value, configure state conditions and alerts, and monitor any Avaya IP phone systems from a single console.
OID Breakdown
Upper-level ancestors (11 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.6889 | avaya | AV-APPLICATION-ENABLEMENT-SERVICES-MIB |
| 1.3.6.1.4.1.6889.2 | mibs | AV-APPLICATION-ENABLEMENT-SERVICES-MIB |
| 1.3.6.1.4.1.6889.2.2 | ipoMIB | IPO-MIB |
| 1.3.6.1.4.1.6889.2.2.1 | ipoGeneric | IPO-MIB |
| 1.3.6.1.4.1.6889.2.2.1.1 | ipoGenMibs | IPO-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.6889.2.2.1.1.1 | ipoPhonesMIB | IPO-PHONES-MIB |
| 1.3.6.1.4.1.6889.2.2.1.1.1.1 | ipoPhonesMibObjects | IPO-PHONES-MIB |
| 1.3.6.1.4.1.6889.2.2.1.1.1.1.1 | ipoPhones | IPO-PHONES-MIB |
| 1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2 | ipoPhonesTable | IPO-PHONES-MIB |
| 1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1 | ipoPhonesEntry | IPO-PHONES-MIB |
| 1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.8 | ipoPhonesPortNumber | IPO-PHONES-MIB |