ROHC-RTP-MIB :: rohcRtpContextACKs

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › ROHC-RTP-MIB › rohcRtpContextACKs

rohcRtpContextACKs

Module: ROHC-RTP-MIB

OID (symbolic): ROHC-RTP-MIB::rohcRtpContextACKs

OID (numeric): 1.3.6.1.2.1.114.1.1.1.10

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of all positive feedbacks (ACK) sent or received in this context, respectively.

Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB.

What is rohcRtpContextACKs?

This counter tallies the number of positive acknowledgment (ACK) feedback messages sent or received for this ROHC context. An admin troubleshooting header-compression stability would watch this counter climb steadily as a sign the compressor and decompressor are successfully confirming synchronization, checking ifCounterDiscontinuityTime on the interface if the value unexpectedly resets. For example, rohcRtpContextACKs jumping from 500 to 5000 over a monitoring interval indicates the decompressor is actively confirming context updates rather than the link having gone silent.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.114.1.1.1.10
snmpwalk -v2c -c public <target> ROHC-RTP-MIB::rohcRtpContextACKs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.114.1.1.1.10.1
snmpget -v2c -c public <target> ROHC-RTP-MIB::rohcRtpContextACKs.1

Start monitoring vendor-neutral, standards-based MIB, cellular/mobile access router or gateway performing header compression with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ROHC-RTP-MIB::rohcRtpContextACKs OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, cellular/mobile access router or gateway performing header compression from a single console.

How to Use in IPNetwork Monitor

Select a device implementing ROHC-RTP-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 rohcRtpContextACKs 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. The number of all positive feedbacks (ACK) sent or received in this context, respectively. 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.114rohcRtpMIBROHC-RTP-MIB
1.3.6.1.2.1.114.1rohcRtpObjectsROHC-RTP-MIB
1.3.6.1.2.1.114.1.1rohcRtpContextTableROHC-RTP-MIB
1.3.6.1.2.1.114.1.1.1rohcRtpContextEntryROHC-RTP-MIB
1.3.6.1.2.1.114.1.1.1.10rohcRtpContextACKsROHC-RTP-MIB