CISCO-VOICE-DIAL-CONTROL-MIB :: cvVoIPPeerCfgDigitRelay

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-VOICE-DIAL-CONTROL-MIBcvVoIPPeerCfgDigitRelay

cvVoIPPeerCfgDigitRelay

Module: CISCO-VOICE-DIAL-CONTROL-MIB

OID (symbolic): CISCO-VOICE-DIAL-CONTROL-MIB::cvVoIPPeerCfgDigitRelay

OID (numeric): 1.3.6.1.4.1.9.9.63.1.2.3.1.14

Node type: OBJECT-TYPE

Type: Bits

Access: read-write

Description: This object specifies the methods to transmit dial digits (DTMF or MF digits) via IP network. rtpCisco - Enable capability to transmit dial digits with Cisco proprietary RTP payload type. h245Signal - Enable capability to transmit dtmf digits across the H.245 channel, via the signal field of the UserInputIndication message h245Alphanumeric - Enable capability to transmit dtmf digit across the H.245 channel, via the string or alphanumeric fields of the UserInputIndication message rtpNte - Enable capability to transmit dial digits using Named Telephony Event per RFC 2833 section 3. sipNotify - Enable capability to transmit dtmf digits using unsolicited SIP NOTIFY messages. This mechanism is only available for SIP dialpeers. sipKpml - Enable capability to transmit dtmf digits using KPML over SIP SUBSCRIBE and NOTIFY messages. This mechanism is only available for SIP dialpeers.

Modifying the value of cvVoIPPeerCfgSessionProtocol can reset the digit-relay method associated bits value in this object if the modified session protocol does not support these digit-relay methods.

What is cvVoIPPeerCfgDigitRelay?

This is a read-write bit-mask setting that enables one or more specific methods, such as Cisco's proprietary RTP payload, H.245 signal or alphanumeric channels, RFC2833/RTP-NTE, or SIP NOTIFY, for transmitting DTMF or MF dial digits across the IP network on this peer. An admin selects the digit-relay method or methods that match what the far-end device or call-control platform supports, since mismatched digit-relay methods cause touch-tone input to be lost. For example, when interconnecting with a third-party SIP system that only understands RFC2833, an admin would enable the rtpNte bit on this peer rather than relying on Cisco's proprietary method.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.63.1.2.3.1.14
snmpwalk -v2c -c public <target> CISCO-VOICE-DIAL-CONTROL-MIB::cvVoIPPeerCfgDigitRelay

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.63.1.2.3.1.14.1
snmpget -v2c -c public <target> CISCO-VOICE-DIAL-CONTROL-MIB::cvVoIPPeerCfgDigitRelay.1

Set instance 1 (SNMPv2c):

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

Start monitoring Cisco voice gateways (POTS/VoIP dial peers) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-VOICE-DIAL-CONTROL-MIB::cvVoIPPeerCfgDigitRelay OID value, configure state conditions and alerts, and monitor any Cisco voice gateways (POTS/VoIP dial peers) 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.63ciscoVoiceDialControlMIBCISCO-VOICE-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.9.63.1cvdcMIBObjectsCISCO-VOICE-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.9.63.1.2cvPeerCISCO-VOICE-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.9.63.1.2.3cvVoIPPeerCfgTableCISCO-VOICE-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.9.63.1.2.3.1cvVoIPPeerCfgEntryCISCO-VOICE-DIAL-CONTROL-MIB
1.3.6.1.4.1.9.9.63.1.2.3.1.14cvVoIPPeerCfgDigitRelayCISCO-VOICE-DIAL-CONTROL-MIB