referredByHeader

MX-SIPEP-MIB · .0.1400.1.2200.100

Object

scalar r/w Enumeration
Referred By Header
          
Indicates how the Referred-By header is used when
participating in a transfer.
          
  * None: When acting as the transferor (sending the REFER),
    the REFER does not contain a Referred-By header. When
    acting as the transferee (receiving the REFER and sending
    the INVITE to the target), the Referred-By header is not
    copied from the REFER to the INVITE.
  * HeaderOnly: When acting as the transferor (sending the
    REFER), the Referred-By header contains the SIP URI and
    the parameters of the transferor. When acting as the
    transferee (receiving the REFER and sending the INVITE to
    the target), the Referred-By header is copied from the
    REFER to the INVITE.

Context

MIB
MX-SIPEP-MIB
OID
.0.1400.1.2200.100
Type
scalar
Access
readwrite
Status
current
Parent
transferGroup

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::referredByHeader.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::referredByHeader'

Syntax

Enumeration

Values & Constraints

Enumerated Values
100none
200headerOnly