CISCO-DIAL-CONTROL-MIB :: cCallHistoryReleaseSrc

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-DIAL-CONTROL-MIBcCallHistoryReleaseSrc

cCallHistoryReleaseSrc

Module: CISCO-DIAL-CONTROL-MIB

OID (symbolic): CISCO-DIAL-CONTROL-MIB::cCallHistoryReleaseSrc

OID (numeric): 1.3.6.1.4.1.9.10.25.1.4.3.1.20

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Originator of the call release. Indicates the source of the call release as follows : 1) callingPartyInPstn : Calling party in PSTN. 2) callingPartyInVoip : Calling party in VoIP. 3) calledPartyInPstn : Called party in PSTN. 4) calledPartyInVoip : Called party in VoIP. 5) internalReleaseInPotsLeg : Due to an internal error in Telephony call leg. 6) internalReleaseInVoipLeg : Due to an internal error in VoIP call leg. 7) internalCallControlApp : Due to an internal error in Session Application or Tcl or VXML script originated release. 8) internalReleaseInVoipAAA : Due to an internal error in VoIP AAA module. 9) consoleCommand : Due to CLI or MML. 10) externalRadiusServer : Call failed during authorization , authentication or due to receipt of POD from the RADIUS server. 11) externalNmsApp : Due to SNMP request to clear the call. 12) externalCallControlAgent : External Call Control Agent initiated clear. 13) gatekeeper : Gatekeeper initiated clear due to receipt of Admission Reject, Disengage Request message. 14) externalGKTMPServer : External GKTMP server initiated clear due to receipt of Admission Reject message from the gatekeeper, triggered by RESPONSE.ARJ message from the GKTMP server.

What is cCallHistoryReleaseSrc?

This object records which entity terminated a call, providing diagnostic information for troubleshooting call failures and understanding disconnection causes. Values indicate the call originated from various sources such as PSTN parties, VoIP endpoints, internal errors, RADIUS servers, or management stations. Operators examine this field in call history logs to root-cause connectivity issues or policy violations.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.25.1.4.3.1.20
snmpwalk -v2c -c public <target> CISCO-DIAL-CONTROL-MIB::cCallHistoryReleaseSrc

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.25.1.4.3.1.20.1
snmpget -v2c -c public <target> CISCO-DIAL-CONTROL-MIB::cCallHistoryReleaseSrc.1

Start monitoring Cisco ISR/Catalyst 8000 routers and voice gateways with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-DIAL-CONTROL-MIB::cCallHistoryReleaseSrc OID value, configure state conditions and alerts, and monitor any Cisco ISR/Catalyst 8000 routers and voice gateways 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.25ciscoDialControlMibCISCO-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.10.25.1ciscoDialControlMibObjectsCISCO-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.10.25.1.4cCallHistoryCISCO-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.10.25.1.4.3cCallHistoryTableCISCO-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.10.25.1.4.3.1cCallHistoryEntryCISCO-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.10.25.1.4.3.1.20cCallHistoryReleaseSrcCISCO-DIAL-CONTROL-MIB