All MIBs › CISCO-CALL-HISTORY-MIB
Organization: Cisco Systems, Inc.
Last Updated: 1996-11-19
Category: Cisco Devices, Telephony and VoIP
Description: Stores call information for all calls on Cisco routers and access servers for accounting purposes, including connection times and disconnection details.
IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring CISCO-CALL-HISTORY-MIB with a free 30-day trial of IPNetwork Monitor.
What Is CISCO-CALL-HISTORY-MIB?
CISCO-CALL-HISTORY-MIB is a Cisco proprietary MIB that stores historical call records on Cisco routers and access servers for accounting and troubleshooting purposes, capturing details of each call placed or received. Its data is fundamentally a fault/event and usage-accounting log: per-call start time, calling and called numbers, the interface used, destination address/hostname, and disconnect cause, along with global settings for table size and retention timer. As a software-status MIB it is used to review completed call activity and diagnose failure patterns by examining disconnect cause codes, effectively serving the monitoring/fault-analysis role for voice/dial connectivity rather than reporting physical hardware health. It is closely related to, and often deployed alongside, CISCO-DIAL-CONTROL-MIB and the IETF Dial Control MIB framework that it extends for demand-access interfaces. It is typically deployed on Cisco routers and access servers handling dial-up or circuit-switched voice/data calls, where CISCO-CALL-HISTORY-MIB SNMP monitoring supports call accounting and disconnect-cause analysis.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-CALL-HISTORY-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
- Cisco router or access server with dial/voice interfaces
Monitoring Examples
An administrator walks ciscoCallHistoryTable / ciscoCallHistoryEntry ordered by ciscoCallHistoryIndex, examining ciscoCallHistoryStartTime, ciscoCallHistoryCallingNumber, and ciscoCallHistoryCalledNumber to reconstruct recent call activity on a given ciscoCallHistoryInterfaceNumber. Reviewing ciscoCallHistoryCallDisconnectCause across many entries reveals recurring abnormal terminations, such as a specific destination consistently disconnecting with a busy or no-answer cause. Adjusting ciscoCallHistoryTableMaxLength and ciscoCallHistoryRetainTimer controls how much call history is retained locally before older entries are aged out, which matters for post-incident accounting audits.
What Can Be Monitored
- call start time
- calling and called numbers
- call disconnect cause
- destination address/hostname
- call history table retention
Imported Objects
From CISCO-SMI
| ciscoMgmt | OBJECT-IDENTITY |
From IF-MIB
| InterfaceIndex |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString | |
| TimeStamp |
OIDs
RFC description
Call history and accounting information storage for Cisco routers and call management systems.
Start monitoring Cisco routers and access servers 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.