interopUseDtmfPayloadTypeFoundInAnswer

MX-SIPEP-MIB · .0.1400.1.50000.2200
Commands MIB view Table view

Object

scalar r/w MX-TCMxEnableState 
Enable/Disable Use DTMF Payload Type Found In Answer
          
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 parameter is enabled, the unit rather uses the
payload type found in the answer. The parameter does not
affect the behaviour when receiving an offer.
          
  * Disable: Keep using the initial payload type.
  * Enable: Use the RFC 2833 payload type found in the
    received answer.
          
This parameter only has an effect when the
DefaultDtmfTransportMethod parameter is set to
'OutOfBandUsingRtp'.

Context

MIB
MX-SIPEP-MIB
OID
.0.1400.1.50000.2200
Type
scalar
Access
readwrite
Status
current
Parent
interopGroup

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-SIPEP-MIB' -M '/opt/observium/mibs/media5:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MX-SIPEP-MIB::interopUseDtmfPayloadTypeFoundInAnswer.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'MX-SIPEP-MIB' -M '/opt/observium/mibs/media5:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MX-SIPEP-MIB::interopUseDtmfPayloadTypeFoundInAnswer'

Syntax

MX-TCMxEnableState
Source
MX-TCMxEnableState
Base type
Enumeration

Values & Constraints

Type Values
0disable
1enable