CISCO-XGCP-EXT-MIB :: cxeCallCtrlDefaultBearTraffic

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-XGCP-EXT-MIBcxeCallCtrlDefaultBearTraffic

cxeCallCtrlDefaultBearTraffic

Module: CISCO-XGCP-EXT-MIB

OID (symbolic): CISCO-XGCP-EXT-MIB::cxeCallCtrlDefaultBearTraffic

OID (numeric): 1.3.6.1.4.1.9.9.325.1.1.1.1.20

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This object specifies the combination of the network type (IP/ATM), virtual circuit type (PVC/SVC) and ATM adaptation layer type (AAL1/AAL2/AAL5) for the connection used in transporting bearer traffic.

ipPvcAal5 (1) - The bearer traffic is transported in IP network, through Permanent Virtual Circuit(PVC) over AAL5 adaptation layer. atmPvcAal2 (2) - The bearer traffic is transported in ATM network, through Permanent Virtual Circuit(PVC) over AAL2 adaptation layer. atmSvcAal2 (3) - The bearer traffic is transported in ATM network, through Switching Virtual Circuit(SVC) over AAL2 adaptation layer. atmSvcAal1 (4) - The bearer traffic is transported in ATM network, through Switching Virtual Circuit(SVC) over AAL1 adaptation layer.

If the call agent specifies the bear traffic type in the MGCP (Media Gateway Control Protocol) local connection options (CRCX request), then configuration of this object will have no effect, else the value of this object will be used when sending CRCX response.

What is cxeCallCtrlDefaultBearTraffic?

This read-write INTEGER selects the default combination of network type, virtual circuit type, and ATM adaptation layer (such as ipPvcAal5 or atmPvcAal2) used to transport bearer (voice) traffic for the call control profile. It matters because it determines the underlying transport path for actual call audio, and a mismatch with the network's actual provisioning would prevent bearer connections from establishing even if signaling succeeds. For example, an admin migrating a site from an ATM PVC over AAL2 network to an IP network would change this object from atmPvcAal2 to ipPvcAal5 to match the new transport.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.325.1.1.1.1.20
snmpwalk -v2c -c public <target> CISCO-XGCP-EXT-MIB::cxeCallCtrlDefaultBearTraffic

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.325.1.1.1.1.20.1
snmpget -v2c -c public <target> CISCO-XGCP-EXT-MIB::cxeCallCtrlDefaultBearTraffic.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.9.9.325.1.1.1.1.20.1 i <value>

Start monitoring Cisco voice/media gateway / media gateway controller with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-XGCP-EXT-MIB::cxeCallCtrlDefaultBearTraffic OID value, configure state conditions and alerts, and monitor any Cisco voice/media gateway / media gateway controller 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.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.325ciscoXgcpExtMIBCISCO-XGCP-EXT-MIB
1.3.6.1.4.1.9.9.325.1cxgcpExtObjectsCISCO-XGCP-EXT-MIB
1.3.6.1.4.1.9.9.325.1.1cxgcpExtConfigCISCO-XGCP-EXT-MIB
1.3.6.1.4.1.9.9.325.1.1.1cxeCallCtrlConfigTableCISCO-XGCP-EXT-MIB
1.3.6.1.4.1.9.9.325.1.1.1.1cxeCallCtrlConfigEntryCISCO-XGCP-EXT-MIB
1.3.6.1.4.1.9.9.325.1.1.1.1.20cxeCallCtrlDefaultBearTrafficCISCO-XGCP-EXT-MIB