CISCO-VISM-DSX0-MIB :: ds0CasOutgoingMgcpPackage

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-VISM-DSX0-MIBds0CasOutgoingMgcpPackage

ds0CasOutgoingMgcpPackage

Module: CISCO-VISM-DSX0-MIB

OID (symbolic): CISCO-VISM-DSX0-MIB::ds0CasOutgoingMgcpPackage

OID (numeric): 1.3.6.1.4.1.351.110.4.7.1.1.32

Node type: OBJECT-TYPE

Type: DisplayString

Access: read-write

Description: This object, in conjunction with the card level persistentXgcpEventsTable, controls how persistent CAS events (like answer, disconnect, etc) related to an outgoing call observed on this DS0 are notified to the Media Gateway Controller (MGC).

At the card level, the persistentXgcpEventsTable allows MGCP package-event combinations to be configured as persistent. For example, when L/hd is added to the persistentXgcpEventsTable, the hook-down event in line package will be notified to the MGC every time it is observed without the MGC requesting for that event.

Since the same CAS event can map to different MGCP events under different packages (eg. the CAS event 'answer' can be 'ans' in 'MS' package and 'hd' in 'BL' package) and different lines could be running different packages at a given time, there needs to be a per-DS0 object indicating what package should be used while notifying CAS events observed on that DS0. This object, ds0CasOutgoingMgcpPackage specifies the package that will be used while notifying CAS events observed on an outgoing call on this DS0.

This object can be set to a package name from xgcpCapabilityPackageTable whose xgcpCapabilityPackageEnable is true or the string 'basic' indicating that one of the basic packages in that table (G, T, L, H, R, D or M) to which the observed event belongs can be used.

This object is used only if the protocol is MGCP. If the notification is in response to an RQNT, VISM uses the package (and event name) that the MGC used to request the event regardless what this object is set to.

In the absence of an RQNT, the observed CAS event is encoded according to the package that this object specifies. An answer observed on the CAS signaling channel on this DS0, for example is encoded as 'ms/ans' if this object is set to 'ms', 'bl/hd' if this object is set to 'bl' or as 'L/hd' if this object is set to 'basic'. If this package/event is present in persistentXgcpEventsTable, a notification is generated, otherwise this event is discarded.

An attempt to set this object to a package name whose xgcpCapabilityPackageEnable is false in xgcpCapabilityPackageTable will fail.

This object is used only if the ds0CasDirectionality is set to 'bidirectional' or 'outgoing'.

What is ds0CasOutgoingMgcpPackage?

This read-write DisplayString works with the card-level persistentXgcpEventsTable to control how persistent CAS events (such as answer or disconnect) related to an outgoing call on this DS0 are reported to the Media Gateway Controller. This gives an admin the same persistent-notification control as ds0CasIncomingMgcpPackage but scoped to the outgoing-call direction on this endpoint. For instance, an admin might configure this so the MGC continues receiving answer-state notifications for outbound calls placed through this DS0 until the call agent acknowledges them.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.4.7.1.1.32
snmpwalk -v2c -c public <target> CISCO-VISM-DSX0-MIB::ds0CasOutgoingMgcpPackage

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.4.7.1.1.32.1
snmpget -v2c -c public <target> CISCO-VISM-DSX0-MIB::ds0CasOutgoingMgcpPackage.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.4.7.1.1.32.1 s <value>

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> ds0CasOutgoingMgcpPackage.1

Start monitoring Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-VISM-DSX0-MIB::ds0CasOutgoingMgcpPackage OID value, configure state conditions and alerts, and monitor any Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) from a single console.

OID Breakdown

Upper-level ancestors (10 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.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.110basisBASIS-MIB
1.3.6.1.4.1.351.110.4basisLinesBASIS-MIB
1.3.6.1.4.1.351.110.4.7dsx0VismBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.4.7.1dsx0VismCnfTableCISCO-VISM-DSX0-MIB
1.3.6.1.4.1.351.110.4.7.1.1dsx0VismCnfEntryCISCO-VISM-DSX0-MIB
1.3.6.1.4.1.351.110.4.7.1.1.32ds0CasOutgoingMgcpPackageCISCO-VISM-DSX0-MIB