interopRegistrationContactMatching – MX-SIPEP-MIB

Object

scalar r/w Enumeration

Registration Contact Matching
          
Configures the matching behaviour for the contact header
received in positive responses to REGISTER requests sent by
the unit.
          
  * Strict: Validate the complete contact's SIP URI including
    any URI parameters, if any, as per RFC 3261 sections
    '10.2.4 Refreshing Bindings' and '19.1.4 URI Comparison'.
    The contact's SIP URI of a 2XX positive response MUST
    match the contact's SIP URI of the REGISTER request.
  * IgnoreUriParams: Validate the username and the host port
    part of the contact's SIP URI. All URI parameters are
    ignored.
  * IgnoreUriAndPortParams: Validate the username part of the
    contact's SIP URI. All URI and host port parameters are
    ignored.

Context

MIB: MX-SIPEP-MIB
OID: .0.1400.1.50000.5000
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::interopRegistrationContactMatching.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::interopRegistrationContactMatching'

Syntax

Enumeration

Values & Constraints

Enumerated Values

`100`	strict
`200`	ignoreUriParams
`300`	ignoreUriAndPortParams