SIP-SERVER-MIB :: sipServerProxyStatProxyReqFailures

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SIP-SERVER-MIB › sipServerProxyStatProxyReqFailures

sipServerProxyStatProxyReqFailures

Module: SIP-SERVER-MIB

OID (symbolic): SIP-SERVER-MIB::sipServerProxyStatProxyReqFailures

OID (numeric): 1.3.6.1.2.1.151.1.4.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: This object contains the number of occurrences of unsupported options being specified in received Proxy-Require headers. Such occurrences result in a 420 Bad Extension status code being returned.

Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by

monitoring the sipServerProxyStatsDisconTime object in the same row.

What is sipServerProxyStatProxyReqFailures?

A running counter of REGISTER/request messages rejected with a 420 Bad Extension because they specified an unsupported option in a Proxy-Require header. A rising count suggests clients or peers are using SIP extensions this proxy doesn't support; watch sipServerProxyStatsDisconTime to know if the counter was reset.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.151.1.4.1.1.1
snmpwalk -v2c -c public <target> SIP-SERVER-MIB::sipServerProxyStatProxyReqFailures

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.151.1.4.1.1.1.1
snmpget -v2c -c public <target> SIP-SERVER-MIB::sipServerProxyStatProxyReqFailures.1

Start monitoring vendor-neutral, standards-based MIB, SIP proxy/redirect/registrar servers (service/config status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SIP-SERVER-MIB::sipServerProxyStatProxyReqFailures OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, SIP proxy/redirect/registrar servers (service/config status) from a single console.

How to Use in IPNetwork Monitor

Select a device implementing SIP-SERVER-MIB as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type sipServerProxyStatProxyReqFailures into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This object contains the number of occurrences of unsupported options being specified in received Proxy-Require headers. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (6 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.151sipServerMIBSIP-SERVER-MIB
1.3.6.1.2.1.151.1sipServerMIBObjectsSIP-SERVER-MIB
1.3.6.1.2.1.151.1.4sipServerProxyStatsSIP-SERVER-MIB
1.3.6.1.2.1.151.1.4.1sipServerProxyStatsTableSIP-SERVER-MIB
1.3.6.1.2.1.151.1.4.1.1sipServerProxyStatsEntrySIP-SERVER-MIB
1.3.6.1.2.1.151.1.4.1.1.1sipServerProxyStatProxyReqFailuresSIP-SERVER-MIB