SIP-SERVER-MIB :: sipServerRegDfltRegActiveInterval

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SIP-SERVER-MIB › sipServerRegDfltRegActiveInterval

sipServerRegDfltRegActiveInterval

Module: SIP-SERVER-MIB

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

OID (numeric): 1.3.6.1.2.1.151.1.5.1.1.4

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-only

Description: This object reflects the default time interval the Registrar considers registrations to be active. The value is used to compute the Expires header in the REGISTER response. If a user agent requests a time interval shorter than specified by this object, the Registrar SHOULD honor that request. If a Contact entry does not have an 'expires' parameter, the value of the Expires header field is used instead. If a Contact entry has no 'expires' parameter and no Expires header field is present, the value of this object is used as the default value.

What is sipServerRegDfltRegActiveInterval?

The default interval, in seconds, the Registrar considers a registration active when no explicit expiry was requested by the user agent or specified via an Expires header. This is the fallback registration lifetime used per RFC 3261 Section 10.2 when the client doesn't specify one itself.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.151.1.5.1.1.4
snmpwalk -v2c -c public <target> SIP-SERVER-MIB::sipServerRegDfltRegActiveInterval

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.151.1.5.1.1.4.1
snmpget -v2c -c public <target> SIP-SERVER-MIB::sipServerRegDfltRegActiveInterval.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::sipServerRegDfltRegActiveInterval 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.

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.5sipServerRegCfgSIP-SERVER-MIB
1.3.6.1.2.1.151.1.5.1sipServerRegCfgTableSIP-SERVER-MIB
1.3.6.1.2.1.151.1.5.1.1sipServerRegCfgEntrySIP-SERVER-MIB
1.3.6.1.2.1.151.1.5.1.1.4sipServerRegDfltRegActiveIntervalSIP-SERVER-MIB