All MIBs › ASCEND-CALL-LOGGING-MIB
Category: Device Management, Vendor: Ascend/Lucent
Description: Provides call detail record logging and accounting for WAN connections on Ascend access devices.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is ASCEND-CALL-LOGGING-MIB?
ASCEND-CALL-LOGGING-MIB is a vendor-specific MIB for Ascend (later Lucent/Avaya) remote access and WAN dial-up equipment, providing call detail record (CDR) logging and accounting for WAN connections such as dial-up or ISDN sessions. It exposes objects intended to capture per-call accounting data used for billing, usage tracking, and troubleshooting connection setup/teardown. Its monitoring relevance centers on software/service status for call handling: administrators would use it to confirm call sessions are being logged correctly, review call duration and termination cause codes, and detect abnormal call failure rates that point to line or configuration problems. No sample objects or module description text were available in this source excerpt, so specific object or table names cannot be confirmed here. It is typically deployed in enterprise or carrier dial-up/remote-access environments using legacy Ascend access concentrators. Engineers can download the ASCEND-CALL-LOGGING-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in ASCEND-CALL-LOGGING-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Ascend WAN access/remote-access concentrator
Monitoring Examples
No sample_objects or module_desc text was provided in the source data for this MIB, so no specific object or table names, nor a grounded monitoring scenario, can be responsibly constructed here. In general terms, a call-logging MIB of this kind would typically expose a call detail record table with fields for call start/end time, duration, and disconnect cause, polled or trapped to a billing/accounting system. Without confirmed object names this cannot be stated as fact for this specific module.
What Can Be Monitored
- call detail record logging
- call duration
- call disconnect cause
Imported Objects
OIDs
RFC description
Manages call logging server configuration and status on Ascend RAS devices for service management and call tracking.
Start monitoring Ascend Communications (Lucent) MAX/Pipeline/TNT WAN access equipment (legacy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.