CISCO-VISM-CODEC-MIB :: vismCodecPktPeriod

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-VISM-CODEC-MIBvismCodecPktPeriod

vismCodecPktPeriod

Module: CISCO-VISM-CODEC-MIB

OID (symbolic): CISCO-VISM-CODEC-MIB::vismCodecPktPeriod

OID (numeric): 1.3.6.1.4.1.351.110.5.5.18.1.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This object gives the packetization period for a particular codec. for G.711u allowed values are 10 & 20 for G.711a allowed values are 10 & 20 for G.726 at 32 kbps allowed values are 10, 20, 30 & 40 for G.729a allowed values are 10, 20, 30 & 40 for G.729ab allowed values are 10, 20, 30 & 40 for clear channel allowed values are 10 and 20 for G.726 at 16 kbps allowed values are 10, 20, 30 & 40 for G.726 at 14 kbps allowed values are 10, 20, 30 & 40 for G.726 at 40 kbps allowed values are 10, 20, 30 & 40 for G.723 allowed values are 30 & 60 for Lossless allowed values are 10 and 20 Default value for G.723 is 30, for other codecs it is 10.

What is vismCodecPktPeriod?

This read-write INTEGER object, in milliseconds (values ten through sixty), sets the packetization period for a particular codec, with the specific allowed values varying per codec (e.g., G.711u/G.711a allow only 10 and 20, while G.726/G.729/G.729ab allow 10 through 40). Since packetization period trades latency against per-call bandwidth overhead, and each codec has different valid ranges, this setting must respect the codec-specific constraints to be accepted. An engineer trying to squeeze more calls onto a bandwidth-limited G.729a trunk would raise this period toward the codec's allowed maximum rather than assume all codecs share the same range.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.18.1.1.3
snmpwalk -v2c -c public <target> CISCO-VISM-CODEC-MIB::vismCodecPktPeriod

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.18.1.1.3.1
snmpget -v2c -c public <target> CISCO-VISM-CODEC-MIB::vismCodecPktPeriod.1

Set instance 1 (SNMPv2c):

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

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> vismCodecPktPeriod.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-CODEC-MIB::vismCodecPktPeriod 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.5basisServicesBASIS-MIB
1.3.6.1.4.1.351.110.5.5voiceBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.5.5.18vismCodecCnfGrpCISCO-VISM-CODEC-MIB
1.3.6.1.4.1.351.110.5.5.18.1vismCodecCnfTableCISCO-VISM-CODEC-MIB
1.3.6.1.4.1.351.110.5.5.18.1.1vismCodecCnfEntryCISCO-VISM-CODEC-MIB
1.3.6.1.4.1.351.110.5.5.18.1.1.3vismCodecPktPeriodCISCO-VISM-CODEC-MIB