CISCO-DIAL-CONTROL-MIB
The CISCO-DIAL-CONTROL-MIB enables monitoring of call history and session statistics for Cisco demand access interfaces, specifically tracking dial-in and dial-out events to facilitate troubleshooting of legacy ISDN, analog modem, and dialer-based connections.
Imported Objects
Objects
29 total| Object Name |
|---|
ciscoDialControlMib OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.25 |
IMPORTS Unknown .1.3.6.1.4.1.9.10.25 |
ciscoDialControlMibObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.25.1 |
cCallHistory OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.25.1.4 |
cCallHistoryTable SEQUENCE OF CCallHistoryEntry .1.3.6.1.4.1.9.10.25.1.4.3 |
cCallHistoryEntry CCallHistoryEntry .1.3.6.1.4.1.9.10.25.1.4.3.1 |
cCallHistoryIndex Unsigned32 .1.3.6.1.4.1.9.10.25.1.4.3.1.1 |
cCallHistorySetupTimero TimeStamp -- Rsyntax TimeTicks .1.3.6.1.4.1.9.10.25.1.4.3.1.2 |
cCallHistoryPeerAddressro DisplayString -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.10.25.1.4.3.1.3 |
cCallHistoryPeerSubAddressro DisplayString -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.10.25.1.4.3.1.4 |
cCallHistoryPeerIdro INTEGER .1.3.6.1.4.1.9.10.25.1.4.3.1.5 |
cCallHistoryPeerIfIndexro INTEGER .1.3.6.1.4.1.9.10.25.1.4.3.1.6 |
cCallHistoryLogicalIfIndexro InterfaceIndex -- Rsyntax Integer32 .1.3.6.1.4.1.9.10.25.1.4.3.1.7 |
cCallHistoryDisconnectCausero OCTET STRING .1.3.6.1.4.1.9.10.25.1.4.3.1.8 |
cCallHistoryDisconnectTextro DisplayString -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.10.25.1.4.3.1.9 |
cCallHistoryConnectTimero TimeStamp -- Rsyntax TimeTicks .1.3.6.1.4.1.9.10.25.1.4.3.1.10 |
cCallHistoryDisconnectTimero TimeStamp -- Rsyntax TimeTicks .1.3.6.1.4.1.9.10.25.1.4.3.1.11 |
cCallHistoryCallOriginro Enumeration .1.3.6.1.4.1.9.10.25.1.4.3.1.12 |
cCallHistoryChargedUnitsro AbsoluteCounter32 -- Rsyntax Gauge32 .1.3.6.1.4.1.9.10.25.1.4.3.1.13 |
cCallHistoryInfoTypero Enumeration .1.3.6.1.4.1.9.10.25.1.4.3.1.14 |
cCallHistoryTransmitPacketsro AbsoluteCounter32 -- Rsyntax Gauge32 .1.3.6.1.4.1.9.10.25.1.4.3.1.15 |
cCallHistoryTransmitBytesro AbsoluteCounter32 -- Rsyntax Gauge32 .1.3.6.1.4.1.9.10.25.1.4.3.1.16 |
cCallHistoryReceivePacketsro AbsoluteCounter32 -- Rsyntax Gauge32 .1.3.6.1.4.1.9.10.25.1.4.3.1.17 |
cCallHistoryReceiveBytesro AbsoluteCounter32 -- Rsyntax Gauge32 .1.3.6.1.4.1.9.10.25.1.4.3.1.18 |
ciscoDialControlMibConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.25.3 |
ciscoDialControlMibCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.25.3.1 |
ciscoDialControlMibCompliance OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.25.3.1.1 |
ciscoDialControlMibGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.25.3.2 |
cCallHistoryGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.25.3.2.1 |
CISCO-DIAL-CONTROL-MIB Technical Reference Overview
The CISCO-DIAL-CONTROL-MIB SNMP MIB module published by Cisco defines 29 managed OID objects, including 19 scalar/column metrics, 1 SNMP tables, and 0 trap/notification events. Key tabular structures include cCallHistoryTable.
Key OID Definitions in CISCO-DIAL-CONTROL-MIB
.1.3.6.1.4.1.9.10.25.1.4.3A table containing information about specific calls to a specific destination.
.1.3.6.1.4.1.9.10.25.1.4.3.1The information regarding a single Connection.
.1.3.6.1.4.1.9.10.25.1.4.3.1.1A monotonically increasing integer for the sole purpose of indexing call disconnection events. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1 and may flush existing entries.
.1.3.6.1.4.1.9.10.25.1.4.3.1.2The value of sysUpTime when the call setup was started. This will be useful for an NMS to sort the call history entry with call setup time. Also, this object can be useful in finding large delays between the time the call was started and the time the call was connected. For ISDN media, this will be the time when the setup message was received from or sent to the network. The value of this object is the same as callActiveSetupTime in the callActiveTable
.1.3.6.1.4.1.9.10.25.1.4.3.1.3The number this call was connected to. If the number is not available, then it will have a length of zero.
.1.3.6.1.4.1.9.10.25.1.4.3.1.4The subaddress this call was connected to. If the subaddress is undefined or not available, this will be a zero length string.
.1.3.6.1.4.1.9.10.25.1.4.3.1.5This is the Id value of the peer table entry to which this call was made. If a peer table entry for this call does not exist, the value of this object will be zero.
.1.3.6.1.4.1.9.10.25.1.4.3.1.6This is the ifIndex value of the peer table entry to which this call was made. If a peer table entry for this call does not exist, the value of this object will be zero.
.1.3.6.1.4.1.9.10.25.1.4.3.1.7This is the ifIndex value of the logical interface through which this call was made. For ISDN media, this would be the ifIndex of the B channel which was used for this call.
.1.3.6.1.4.1.9.10.25.1.4.3.1.8The encoded network cause value associated with this call. The value of this object will depend on the interface type as well as on the protocol and protocol version being used on this interface. Some references for possible cause values are given below.
.1.3.6.1.4.1.9.10.25.1.4.3.1.9ASCII text describing the reason for call termination. This object exists because it would be impossible for a management station to store all possible cause values for all types of interfaces. It should be used only if a management station is unable to decode the value of dialCtlPeerStatsLastDisconnectCause.
.1.3.6.1.4.1.9.10.25.1.4.3.1.10The value of sysUpTime when the call was connected.
.1.3.6.1.4.1.9.10.25.1.4.3.1.11The value of sysUpTime when the call was disconnected.
.1.3.6.1.4.1.9.10.25.1.4.3.1.12The call origin.
.1.3.6.1.4.1.9.10.25.1.4.3.1.13The number of charged units for this connection. For incoming calls or if charging information is not supplied by the switch, the value of this object will be zero.
.1.3.6.1.4.1.9.10.25.1.4.3.1.14The information type for this call.
.1.3.6.1.4.1.9.10.25.1.4.3.1.15The number of packets which were transmitted while this call was active.
.1.3.6.1.4.1.9.10.25.1.4.3.1.16The number of bytes which were transmitted while this call was active.
.1.3.6.1.4.1.9.10.25.1.4.3.1.17The number of packets which were received while this call was active.
.1.3.6.1.4.1.9.10.25.1.4.3.1.18The number of bytes which were received while this call was active.
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.
The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.
The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.
SNMP MIB module
The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.
The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.