SIP-REGISTRAR-MIB :: sipRegMaxContactExpiryDate

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SIP-REGISTRAR-MIB › sipRegMaxContactExpiryDate

sipRegMaxContactExpiryDate

Module: SIP-REGISTRAR-MIB

OID (symbolic): SIP-REGISTRAR-MIB::sipRegMaxContactExpiryDate

OID (numeric): 1.3.6.1.2.1.9998.5.1.1.1.4

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-write

Description: This object specifies the maximum expiry that may be requested by a User Agent for a particular Contact. User Agents can specify expiry using either an Expiry header in a REGISTER request, or using an Expires parameter in a Contact header in a REGISTER request. If the value requested by the User Agent is greater than the value of this object, then the contact information is given the duration specified by this object, and that duration is indicated to the User Agent in the response.

What is sipRegMaxContactExpiryDate?

A read-write ceiling in seconds (default 4294967295, effectively unlimited) on the expiry a User Agent may request for a Contact; if a client asks for longer, the registrar caps it at this value and reports the shorter duration back to the client.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.9998.5.1.1.1.4
snmpwalk -v2c -c public <target> SIP-REGISTRAR-MIB::sipRegMaxContactExpiryDate

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.9998.5.1.1.1.4.1
snmpget -v2c -c public <target> SIP-REGISTRAR-MIB::sipRegMaxContactExpiryDate.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.2.1.9998.5.1.1.1.4.1 i <value>

Start monitoring vendor-neutral, standards-based MIB, SIP registrar server (registration binding/expiry/auth status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SIP-REGISTRAR-MIB::sipRegMaxContactExpiryDate OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, SIP registrar server (registration binding/expiry/auth status) from a single console.

OID Breakdown

Upper-level ancestors (7 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
1.3.6.1.2.1.9998sipMIBSIP-MIB-SMI
Numeric OIDNameModule
1.3.6.1.2.1.9998.5sipRegistrarMIBSIP-REGISTRAR-MIB
1.3.6.1.2.1.9998.5.1sipRegCfgSIP-REGISTRAR-MIB
1.3.6.1.2.1.9998.5.1.1sipRegCfgTableSIP-REGISTRAR-MIB
1.3.6.1.2.1.9998.5.1.1.1sipRegCfgEntrySIP-REGISTRAR-MIB
1.3.6.1.2.1.9998.5.1.1.1.4sipRegMaxContactExpiryDateSIP-REGISTRAR-MIB