sipInteropUseDtmfPayloadTypeFoundInAnswer

MX-SIP-INTEROP-MIB · .1.3.6.1.4.1.4935.99.20.1.447

Object

scalar r/w MX-TCMxEnableState

The default behaviour when sending an initial offer
that contains an RFC 2833 payload type is to keep using
that payload type even if the response comes back with a
different one.  When this variable is enabled,
the unit rather uses the payload type found in the answer.
The variable does not affect the behaviour when receiving an
offer. The payload type is used symmetrically meaning that
it's used to send and receive the DTMF. Use the variable
sipInteropAllowAsymmetricDtmfPayloadType to allow
asymmetric payload type.
          
disable :
   Keep using the initial payload type.
          
enable :
   Use the RFC 2833 payload type found in the received
   answer.
          
This variable only has an effect when voiceIfDtmfTransport
is set to outOfBandUsingRtp.

Context

MIB: MX-SIP-INTEROP-MIB
OID: .1.3.6.1.4.1.4935.99.20.1.447
Type: scalar
Access: readwrite
Status: current
Parent: sipInteropMIBObjects
Groups: 1

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'MX-SIP-INTEROP-MIB' -M '/opt/observium/mibs/media5:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MX-SIP-INTEROP-MIB::sipInteropUseDtmfPayloadTypeFoundInAnswer.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'MX-SIP-INTEROP-MIB' -M '/opt/observium/mibs/media5:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MX-SIP-INTEROP-MIB::sipInteropUseDtmfPayloadTypeFoundInAnswer'

Syntax

MX-TCMxEnableState

Source: MX-TCMxEnableState
Base type: Enumeration

Values & Constraints

Type Values

`0`	disable
`1`	enable