SIP-SERVER-MIB
Session Initiation Protocol (SIP) Server MIB module. SIP is an application-layer signaling protocol for creating, modifying, and terminating multimedia sessions with one or more participants. These sessions include Internet multimedia conferences and Internet telephone calls. SIP is defined in RFC 3261 (June 2002). This MIB is defined for the management of SIP Proxy, Redirect, and Registrar Servers. A Proxy Server acts as both a client and a server. It accepts requests from other clients, either responding to them or passing them on to other servers, possibly after modification. A Redirect Server accepts requests from clients and returns zero or more addresses to that client. Unlike a User Agent Server, it does not accept calls. A Registrar is a server that accepts REGISTER requests. A Registrar is typically co-located with a Proxy or Redirect Server. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4780; see the RFC itself for full legal notices.
Main OID:
sipServerMIB.1.3.6.1.2.1.151
59
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
59 total| Object Name |
|---|
sipServerMIBSession Initiation Protocol (SIP) Server MIB module. SIP is an application-layer signaling protocol for creating, modifying, and terminating multimedia sessions with one or more participants. These sessions include Internet multimedia conferences and Internet telephone calls. SIP is defined in RFC 3261 (June 2002). This MIB is defined for the management of SIP Proxy, Redirect, and Registrar Servers. A Proxy Server acts as both a client and a server. It accepts requests from other clients, either responding to them or passing them on to other servers, possibly after modification. A Redirect Server accepts requests from clients and returns zero or more addresses to that client. Unlike a User Agent Server, it does not accept calls. A Registrar is a server that accepts REGISTER requests. A Registrar is typically co-located with a Proxy or Redirect Server. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4780; see the RFC itself for full legal notices. MODULE-IDENTITY .1.3.6.1.2.1.151 |
sipServerMIBObjects OBJECT IDENTIFIER .1.3.6.1.2.1.151.1 |
sipServerCfg OBJECT IDENTIFIER .1.3.6.1.2.1.151.1.1 |
sipServerCfgTableThis table contains configuration objects applicable to SIP Redirect and Proxy Servers. SEQUENCE OF SipServerCfgEntry .1.3.6.1.2.1.151.1.1.1 |
sipServerCfgEntryA row of common configuration. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here. SipServerCfgEntry .1.3.6.1.2.1.151.1.1.1.1 |
sipServerCfgHostAddressTypeThe type of Internet address by which the SIP server is reachable.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.151.1.1.1.1.1 |
sipServerCfgHostAddressThis is the host portion of a SIP URI that is assigned to the SIP server. It MAY contain a fully qualified domain name or an IP address. The length of the value will depend on the type of address specified. The type of address given by this object is controlled by sipServerCfgHostAddressType.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.151.1.1.1.1.2 |
sipServerProxyCfg OBJECT IDENTIFIER .1.3.6.1.2.1.151.1.3 |
sipServerProxyCfgTableThis table contains configuration objects applicable to SIP Proxy Servers. SEQUENCE OF SipServerProxyCfgEntry .1.3.6.1.2.1.151.1.3.1 |
sipServerProxyCfgEntryA row of common proxy configuration. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here. SipServerProxyCfgEntry .1.3.6.1.2.1.151.1.3.1.1 |
sipServerCfgProxyStatefulnessThis object reflects the default mode of operation for the Proxy Server entity. A stateless proxy is a logical entity that does not maintain the client or server transaction state machines when it processes requests. A stateless proxy forwards every request it receives downstream and every response it receives upstream. If the value of this object is stateless(1), the proxy defaults to stateless operations. A transaction stateful proxy, or simply a 'stateful proxy', is a logical entity that maintains the client and server transaction state machines during the processing of a request. A (transaction) stateful proxy is not the same as a call stateful proxy. If the value of this object is transactionStateful(2), the proxy is stateful on a transaction basis. A call stateful proxy is a logical entity if it retains state for a dialog from the initiating INVITE to the terminating BYE request. A call stateful proxy is always transaction stateful, but the converse is not necessarily true. If the value of this object is callStateful(3), the proxy is call stateful.ro Enumeration .1.3.6.1.2.1.151.1.3.1.1.1 |
sipServerCfgProxyRecursionThis object reflects whether or not the Proxy performs a recursive search on the Contacts provided in 3xx redirects. If the value of this object is 'true', a recursive search is performed. If the value is 'false', no search is performed, and the 3xx response is sent upstream towards the source of the request.ro TruthValue (SNMPv2-TC) .1.3.6.1.2.1.151.1.3.1.1.2 |
sipServerCfgProxyRecordRouteThis object reflects whether or not the proxy adds itself to the Record-Route header as a default action. This header is used to list the proxies that insist on being in the signaling path for subsequent requests related to the call leg. If the value of this object is 'true', the proxy adds itself to the end of the Record-Route header, creating the header if required. If the value is 'false', the proxy does not add itself to the Record-Route header.ro TruthValue (SNMPv2-TC) .1.3.6.1.2.1.151.1.3.1.1.3 |
sipServerCfgProxyAuthMethodThis object reflects the authentication methods that MAY be used to authenticate request originators. bit 0 no authentication is performed bit 1 TLS is used bit 2 HTTP Digest is used.ro Bits .1.3.6.1.2.1.151.1.3.1.1.4 |
sipServerCfgProxyAuthDefaultRealmThis object reflects the default realm value used in Proxy-Authenticate headers. Note that this MAY need to be stored per user, in which case, this default value is ignored.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.151.1.3.1.1.5 |
sipServerProxyStats OBJECT IDENTIFIER .1.3.6.1.2.1.151.1.4 |
sipServerProxyStatsTableThis table contains the statistics objects applicable to all SIP Proxy Servers in this system. SEQUENCE OF SipServerProxyStatsEntry .1.3.6.1.2.1.151.1.4.1 |
sipServerProxyStatsEntryA row of summary statistics. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here. SipServerProxyStatsEntry .1.3.6.1.2.1.151.1.4.1.1 |
sipServerProxyStatProxyReqFailuresThis object contains the number of occurrences of unsupported options being specified in received Proxy-Require headers. Such occurrences result in a 420 Bad Extension status code being returned. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipServerProxyStatsDisconTime object in the same row.ro Counter32 .1.3.6.1.2.1.151.1.4.1.1.1 |
sipServerProxyStatsDisconTimeThe value of the sysUpTime object when the counters for the server statistics objects in this row last experienced a discontinuity.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.151.1.4.1.1.2 |
sipServerRegCfg OBJECT IDENTIFIER .1.3.6.1.2.1.151.1.5 |
sipServerRegCfgTableThis table contains configuration objects applicable to SIP Registrars. SEQUENCE OF SipServerRegCfgEntry .1.3.6.1.2.1.151.1.5.1 |
sipServerRegCfgEntryA row of common Registrar configuration. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here. SipServerRegCfgEntry .1.3.6.1.2.1.151.1.5.1.1 |
sipServerRegMaxContactExpiryDurationThis 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.ro Unsigned32 .1.3.6.1.2.1.151.1.5.1.1.1 |
sipServerRegMaxUsersThis object reflects the maximum number of users that the Registrar supports. The current number of users is reflected by sipServerRegCurrentUsers.ro Unsigned32 .1.3.6.1.2.1.151.1.5.1.1.2 |
sipServerRegCurrentUsersThis object reflects the number of users currently registered with the Registrar.ro Gauge32 .1.3.6.1.2.1.151.1.5.1.1.3 |
sipServerRegDfltRegActiveIntervalThis 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.ro Unsigned32 .1.3.6.1.2.1.151.1.5.1.1.4 |
sipServerRegUserTableThis table contains information on all users registered to each Registrar in this system. SEQUENCE OF SipServerRegUserEntry .1.3.6.1.2.1.151.1.5.2 |
sipServerRegUserEntryThis entry contains information for a single user registered to this Registrar. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here. SipServerRegUserEntry .1.3.6.1.2.1.151.1.5.2.1 |
sipServerRegUserIndexThis object uniquely identifies a conceptual row in the table. Unsigned32 .1.3.6.1.2.1.151.1.5.2.1.1 |
sipServerRegUserUriThis object contains the user's address-of-record. It is the main form by which the Registrar knows the user. The format is typically 'user@domain'. It is contained in the To header for all REGISTER requests.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.151.1.5.2.1.2 |
sipServerRegUserAuthenticationFailuresThis object contains a count of the number of times the user has failed authentication. Discontinuities in the value of this counter can occur due to successful user authentications and at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipServerRegUserDisconTime object in the same row.ro Counter32 .1.3.6.1.2.1.151.1.5.2.1.3 |
sipServerRegUserDisconTimeThe value of the sysUpTime object when the counters for the user registration statistics objects in this row last experienced a discontinuity.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.151.1.5.2.1.4 |
sipServerRegContactTableThis table contains information on every location where a registered user (specified by sipServerRegUserIndex) wishes to be found (i.e., the user has provided contact information to each SIP Registrar in this system). SEQUENCE OF SipServerRegContactEntry .1.3.6.1.2.1.151.1.5.3 |
sipServerRegContactEntryThis entry contains information for a single Contact. Multiple contacts may exist for a single user. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here. SipServerRegContactEntry .1.3.6.1.2.1.151.1.5.3.1 |
sipServerRegContactIndexAlong with the sipServerRegUserIndex, this object uniquely identifies a conceptual row in the table. Unsigned32 .1.3.6.1.2.1.151.1.5.3.1.1 |
sipServerRegContactDisplayNameThis object contains the display name for the Contact. For example, 'Santa at Home', or 'Santa on his Sled', corresponding to contact URIs of sip:BigGuy@example.com or sip:sclaus817@example.com, respectively.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.151.1.5.3.1.2 |
sipServerRegContactURIThis object contains either a SIP URI where the user can be contacted. This URI is normally returned to a client from a Redirect Server, or is used as the RequestURI in a SIP request line for requests forwarded by a proxy.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.151.1.5.3.1.3 |
sipServerRegContactLastUpdatedThis object indicates the time when this contact information was accepted. If the contact information is updated via a subsequent REGISTER of the same information, this object is also updated.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.151.1.5.3.1.4 |
sipServerRegContactExpiryThis object contains the date and time when the contact information will no longer be valid. Such times may be specified by the user at registration (i.e., Expires header or expiry parameter in the Contact information), or a system default can be applied.ro DateAndTime (SNMPv2-TC) .1.3.6.1.2.1.151.1.5.3.1.5 |
sipServerRegContactPreferenceThis object indicates a relative preference for the particular Contact header field value compared to other bindings for this address-of-record. A registering user may provide this preference as a 'qvalue' parameter in the Contact header. The format of this item is a decimal number between 0 and 1 (for example 0.9). Higher values indicate locations preferred by the user.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.151.1.5.3.1.6 |
sipServerRegStats OBJECT IDENTIFIER .1.3.6.1.2.1.151.1.6 |
sipServerRegStatsTableThis table contains the summary statistics objects applicable to all SIP Registrars in this system. SEQUENCE OF SipServerRegStatsEntry .1.3.6.1.2.1.151.1.6.1 |
sipServerRegStatsEntryA row of summary statistics. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here. SipServerRegStatsEntry .1.3.6.1.2.1.151.1.6.1.1 |
sipServerRegStatsAcceptedRegsThis object contains a count of the number of REGISTER requests that have been accepted (status code 200) by the Registrar. This includes additions of new contact information, refreshing contact information, as well as requests for deletion of contact information. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipServerRegStatsDisconTime object in the same row.ro Counter32 .1.3.6.1.2.1.151.1.6.1.1.1 |
sipServerRegStatsRejectedRegsThis object contains a count of the number REGISTER requests that have been rejected by the Registrar. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipServerRegStatsDisconTime object in the same row.ro Counter32 .1.3.6.1.2.1.151.1.6.1.1.2 |
sipServerRegStatsDisconTimeThe value of the sysUpTime object when the counters for the registrar statistics objects in this row last experienced a discontinuity.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.151.1.6.1.1.3 |
sipServerMIBConformance OBJECT IDENTIFIER .1.3.6.1.2.1.151.2 |
sipServerMIBCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.151.2.1 |
sipServerProxyServerComplianceThe compliance statement for SIP entities acting as Proxy Servers. Unknown .1.3.6.1.2.1.151.2.1.1 |
sipRedirectServerComplianceThe compliance statement for SIP entities acting as Redirect Servers. Unknown .1.3.6.1.2.1.151.2.1.2 |
sipServerRegistrarServerComplianceThe compliance statement for SIP entities acting as Registrars. Unknown .1.3.6.1.2.1.151.2.1.3 |
sipServerMIBGroups OBJECT IDENTIFIER .1.3.6.1.2.1.151.2.2 |
sipServerConfigGroupA collection of objects providing configuration common to SIP Proxy and Redirect servers. Unknown .1.3.6.1.2.1.151.2.2.1 |
sipServerProxyConfigGroupA collection of objects providing configuration for SIP Proxy servers. Unknown .1.3.6.1.2.1.151.2.2.2 |
sipServerProxyStatsGroupA collection of objects providing statistics for SIP Proxy servers. Unknown .1.3.6.1.2.1.151.2.2.3 |
sipServerRegistrarConfigGroupA collection of objects providing configuration for SIP Registrars. Unknown .1.3.6.1.2.1.151.2.2.4 |
sipServerRegistrarStatsGroupA collection of objects providing statistics for SIP Registrars. Unknown .1.3.6.1.2.1.151.2.2.5 |
sipServerRegistrarUsersGroupA collection of objects related to registered users. Unknown .1.3.6.1.2.1.151.2.2.6 |