All MIBs › ASCEND-CALL-LOGGING-MIB › callLoggingPortNumber
callLoggingPortNumber
Module: ASCEND-CALL-LOGGING-MIB
OID (symbolic): ASCEND-CALL-LOGGING-MIB::callLoggingPortNumber
OID (numeric): 1.3.6.1.4.1.529.25.4
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The UDP server port to use for Call Logging packets.
What is callLoggingPortNumber?
This integer specifies the UDP port on the logging server. Typical values range 1024-65535. Server must be listening on this port for records to be received.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.529.25.4 snmpwalk -v2c -c public <target> ASCEND-CALL-LOGGING-MIB::callLoggingPortNumber
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.529.25.4.1 snmpget -v2c -c public <target> ASCEND-CALL-LOGGING-MIB::callLoggingPortNumber.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.529.25.4.1 i <value>
Start monitoring Ascend Communications (Lucent) MAX/Pipeline/TNT WAN access equipment (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ASCEND-CALL-LOGGING-MIB::callLoggingPortNumber OID value, configure state conditions and alerts, and monitor any Ascend Communications (Lucent) MAX/Pipeline/TNT WAN access equipment (legacy) from a single console.
OID Breakdown
Upper-level ancestors (8 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.529 | ascend | ASCEND-MIB |
| 1.3.6.1.4.1.529.25 | callLoggingGroup | ASCEND-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.529.25.4 | callLoggingPortNumber | ASCEND-CALL-LOGGING-MIB |