SIP-REGISTRAR-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SIP-REGISTRAR-MIB

Organization: IETF SIP Working Group, SIP MIB Team

Last Updated: 2000-07-08

Category: IETF Standards MIBs, SIP and VoIP Protocol, VoIP and Media Gateway

Description: Manages IETF SIP registrar server contact bindings, registration expiry, and authentication state.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is SIP-REGISTRAR-MIB?

SIP-REGISTRAR-MIB is a vendor-neutral IETF standards-based MIB defining managed objects for a SIP (Session Initiation Protocol) Registrar, the server component that accepts REGISTER requests from SIP user agents. It exposes data about contact bindings (the mapping of a SIP address-of-record to the device/location currently reachable at), registration expiry timers, and authentication state associated with those registrations. Its monitoring relevance is software/service status oriented: it lets an administrator confirm active registration counts and binding expiry to detect endpoints that failed to re-register, and check authentication state to spot credential or authentication failures affecting call routing. It is explicitly built on top of the SIP protocol as defined in RFC 2543 (and superseded by RFC 3261), so it is tightly coupled to that IETF signaling standard rather than to any vendor extension. It is typically deployed on SIP registrar/proxy servers in VoIP or unified-communications infrastructure to monitor registration health across a population of SIP endpoints. Engineers implementing or auditing this functionality typically reference the SIP-REGISTRAR-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in SIP-REGISTRAR-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • SIP registrar server

Monitoring Examples

No concrete object or table names were captured in the sample for this MIB, so a specific polling example can't be grounded in real identifiers, but per the module description it would define a contact-binding table keyed by address-of-record with expiry and authentication-state columns. A realistic scenario would be an NMS polling the registration table to count currently bound endpoints and flag any binding nearing its expiry time without a renewal, indicating a device that may be about to drop off the network.

What Can Be Monitored

  • registered contact bindings
  • registration expiry time
  • authentication state of registrations
  • active registration count
Imported Objects

From NETWORK-SERVICES-MIB

applIndexOBJECT-TYPE

From SIP-MIB-SMI

sipMIBMODULE-IDENTITY

From SIP-TC

SipServerActions

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
RowStatus
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using sipUserAuthenticationFailures OID:

Select a device implementing SIP-REGISTRAR-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 sipUserAuthenticationFailures 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 a count of the number of times the user has failed authentication. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

An SNMP MIB defined in RFC 4780 for managing Session Initiation Protocol (SIP) registrar servers, providing statistics and control objects for SIP registration services.

Start monitoring vendor-neutral, standards-based MIB, SIP registrar server (registration binding/expiry/auth status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SIP-REGISTRAR-MIB