ASCEND-CALL-LOGGING-MIB :: callLoggingIdBase

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ASCEND-CALL-LOGGING-MIB › callLoggingIdBase

callLoggingIdBase

Module: ASCEND-CALL-LOGGING-MIB

OID (symbolic): ASCEND-CALL-LOGGING-MIB::callLoggingIdBase

OID (numeric): 1.3.6.1.4.1.529.25.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The Base to use in reporting Call Logging ID.

What is callLoggingIdBase?

This field specifies the number base for call logging IDs: base10 (10) or base16 (16). Affects how IDs appear in reports. Choice is mainly for readability.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.529.25.7
snmpwalk -v2c -c public <target> ASCEND-CALL-LOGGING-MIB::callLoggingIdBase

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.529.25.7.1
snmpget -v2c -c public <target> ASCEND-CALL-LOGGING-MIB::callLoggingIdBase.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.529.25.7.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::callLoggingIdBase 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 OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.529ascendASCEND-MIB
1.3.6.1.4.1.529.25callLoggingGroupASCEND-MIB
Numeric OIDNameModule
1.3.6.1.4.1.529.25.7callLoggingIdBaseASCEND-CALL-LOGGING-MIB