SIP-SERVER-MIB :: sipServerRegMaxContactExpiryDuration

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SIP-SERVER-MIB › sipServerRegMaxContactExpiryDuration

sipServerRegMaxContactExpiryDuration

Module: SIP-SERVER-MIB

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

OID (numeric): 1.3.6.1.2.1.151.1.5.1.1.1

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-only

Description: This object reflects 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 sipServerRegMaxContactExpiryDuration?

The maximum expiry time, in seconds, the Registrar will grant for a Contact even if the User Agent requests longer; a requested value above this is capped and the capped value is returned to the client. Lower this to force more frequent re-registration, useful for detecting stale/offline endpoints sooner.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.151.1.5.1.1.1
snmpwalk -v2c -c public <target> SIP-SERVER-MIB::sipServerRegMaxContactExpiryDuration

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.151.1.5.1.1.1.1
snmpget -v2c -c public <target> SIP-SERVER-MIB::sipServerRegMaxContactExpiryDuration.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::sipServerRegMaxContactExpiryDuration 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.1sipServerRegMaxContactExpiryDurationSIP-SERVER-MIB