Internet Engineering Task Force
SIP Working Group                                            K. Lingle,
Internet Draft                                     Cisco Systems, Inc.,
draft-ietf-sip-mib-01.txt                                     J. Maeng,
July 2000                                                   VTEL Corp.,
Expires: January 2001                                        D. Walker Walker,
                                                     SS8 Networks, Inc.
Internet Draft
Document: draft-ietf-sip-mib-00.txt                       March 6, 2000
Expires: September, 2000

                        Management Information Base
                      for Session Invitation Initiation Protocol

                       draft-ietf-sip-mib-00.txt

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC 2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that
   other groups may also distribute working documents as Internet-Drafts. Internet-
   Drafts. Internet-Drafts are draft documents valid for a maximum of
   six months and may be updated, replaced, or obsoleted by other
   documents at any time. It is inappropriate to use Internet- Drafts Internet-Drafts as
   reference material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Internet-
   Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This particular draft is being developed in the Session Initiation
   Protocol Working Group. Discussion of it therefore belongs on that
   list. The charter for Session Initiation Protocol may be found at
   http://www.ietf.org/html.charters/sip-charter.html

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes a set of managed objects that are used
   to manage Session Initiation Protocol(SIP) [17] devices, which
   include User Agent, Agents, Proxy server, servers, Redirect server servers and Registrar.

Table of Contents

1.Introduction .......................................................2

2.The SNMP Management Framework ......................................2
3.Overview ...........................................................3
4.Structure of SIP MIB ...............................................3
4.1 Textual Conventions ..............................................3
4.2 Relationship to Other MIB ........................................4
5.Definitions ........................................................4
6.Security Considerations ...........................................67

7.Intellectual Property .............................................67
8.Full Copyright Statement ..........................................68
9.References ........................................................68

10. Authors' Addresses ..............................................69 Registrars.

1. Introduction

   This memo defines a portion of the Management Information Base
   (MIB)for use with network management protocols in the Internet
   community. In particular, it describes a set of managed objects that
   are used to schedule management operations periodically or at
   specified dates and times.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [16].

Lingle/Maeng/Walker                                                  1

2. The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

      o

   - An overall architecture, described in RFC 2271 [1].

      o

   - Mechanisms for describing and naming objects and events for the
     purpose of management. The first version of this Structure of
     Management Information (SMI) is called SMIv1 and described in
     STD16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
     second version, called SMIv2, is described in STD 58, RFC 2578
     [5], RFC 2579 [6] and RFC 2580 [7].

      o

   - Message protocols for transferring management information.  The
     first version of the SNMP message protocol is called SNMPv1 and
     described in RFC 1157 [8]. A second version of the SNMP message
     protocol, which is not an Internet standards track protocol, is
     called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
     The third version of the message protocol is called SNMPv3 and
     described in RFC 2272 [11] and RFC 2274 [12].

      o

   - Protocol operations for accessing management information. The
     first set of protocol operations and associated PDU formats is
     described in STD 15, RFC 1157 [8]. A second set of protocol
     operations and associated PDU formats is described in RFC 1905
     13].

      o

   - A set of fundamental applications described in RFC 2273 [14] and
     the view-based access control mechanism described in RFC 2275
     [15].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2. A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations. The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64). Some machine readable
   information in SMIv2 will be converted into textual descriptions in

   SMIv1 during the translation process. However, this loss of
   machinereadable information is not considered to change the
   semantics of the MIB.

3. Overview

   The Session Initiation Protocol (SIP) [17] is an application-layer
   control protocol that can establish, modify and terminate multimedia
   sessions or calls. This mib MIB provides some managed objects for SIP
   devices defined in RFC 2543 - User Agent, Proxy server, Redirect

Lingle/Maeng/Walker                                                  2
   server and Registrar. It is provided as a base for the work within
   the working group to define a mib. MIB.

   This MIB is intended to provide management of the basic devices in
   SIP. It provides for monitoring of status and protocol statistics,
   as well as for configuration of basic SIP devices.

4. Structure of SIP MIB

   Objects in this

   This memo specifies six MIB modules.  They are arranged into groups.  Each group is
   organized as a set SIP-MIB-SMI, SIP-
   COMMON-MIB, SIP-REGISTRAR-MIB, SIP-SERVER-MIB, SIP-UA-MIB and SIP-
   TC. SIP-MIB-SMI indicates the root OID of related objects. SIP MIB modules.  SIP-
   COMMON-MIB contains common objects used in all the SIP entities such
   as Registrars, Proxy Servers, Redirect Servers and User Agents. SIP-
   SIP-REGISTRAR-MIB, SIP-SERVER-MIB and SIP-UA-MIB includes objects
   defined for Registrars, Proxy and Redirect servers, and User Agents,
   respectively.  SIP-TC defines the textual conventions used through
   out MIB modules.

   The overall structure is
   described below. MIB modules contain the following groups of objects:

   -- SIP-COMMON-MIB: Common to all the SIP devices
      sipCommonConfigGroup
      sipCommonStatsGroup
      sipCommonNotifGroup

   -- SIP-REGISTRAR-MIB: Groups of objects for User Agent
        sipUAConfigGroup
        sipUAStatsGroup

        -- Groups of objects for Proxy/Redirect server configuration
        sipNetServerConfigGroup

        -- Groups of objects for Proxy server
        sipProxyConfigGroup
        sipProxyStatsGroup

        -- Groups of objects for Registrar Registrars
      sipRegistrarConfigGroup
      sipRegistrarStatsGroup

   -- SIP-SERVER-MIB: Groups of objects for proxy and Redirect server (A place holder - not
        defined at this time)
        -- sipRedirectConfigGroup
        -- sipRedirectStatsGroup Servers
      sipServerConfigGroup
      sipServerStatsGroup
      sipProxyConfigGroup
      sipProxyStatsGroup

   -- Notification SIP-UA-MIB: Groups of objects for UA, Proxy, User Agents
      sipUAConfigGroup
      sipUAStatsGroup

   It is required to implement SIP-COMMON-MIB together with its own MIB
   module in Registrars, Proxy Servers, Redirect Servers and User
   Agents.  For instance, a SIP Registrar (A place holder - not defined at this time)
        -- sipUANotificationGroup
        -- sipProxyNotificationGroup
        -- sipRedirectNotificationGroup
        -- sipRegistrarNotificationGroup will need four MIB modules,
   SIP-MIB-SMI, SIP-COMMON-MIB, SIP-REGISTRAR-MIB, and SIP-TC in order
   to provide a complete set of objects . If a device has more than one
   sip entity or multiple instances of the same entity, it may
   implement multiple SIP modules.  Section 4.2 describes handling of
   multiple instances in detail.

4.1 Textual Conventions

   The datatypes data type SipServerActions is used as textual conventions in
   this document.  These textual conventions have NO effect on either
   the syntax nor the semantics of any managed object.  Objects defined

Lingle/Maeng/Walker                                                  3
   using these conventions are always encoded by means of the rules
   that define their primitive type.  Hence, no changes to the SMI or
   the SNMP are necessary to accommodate these textual conventions
   which are adopted merely for the convenience of readers.

4.2 Relationship to Other MIB

   If there

   There is a need for using a single agent which supports requirement to be able to support multiple instances of sipMIB, one may use the Entity
   SIP MIB [19].  It in no way
   alters the information required modules in the sipMib.

   The Entity MIB introduces a standardized way of presenting the
   components context of complex systems that a single system having a single
   SNMP agent.   For example, a device acting as a SIP Proxy Server may
   also contain multiple racks,
   shelves,line cards, and/or ports. The Entity MIB's main goal a Registrar function.   It is also possible to
   present these system components, their containment relationship, and
   mapping information with other MIBs.

5.
  Definitions

   SIP-MIB DEFINITIONS ::= BEGIN

   IMPORTS
        MODULE-IDENTITY,
        OBJECT-TYPE,
        Counter32,
        Integer32,
        Gauge32,
        mib-2,
        TimeTicks,
        Unsigned32
             FROM SNMPv2-SMI

        TEXTUAL-CONVENTION,
        DateAndTime,
        RowStatus,
        TimeStamp,
        TruthValue
             FROM SNMPv2-TC

        MODULE-COMPLIANCE,
        OBJECT-GROUP,
        NOTIFICATION-GROUP
             FROM SNMPv2-CONF

        SnmpAdminString
             FROM SNMP-FRAMEWORK-MIB;

   sipMIB MODULE-IDENTITY
        LAST-UPDATED   "200003020000Z"
        ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
        CONTACT-INFO
                "SIP MIB Team email: sip-mib@egroups.com

                 Co-editor  Kevin Lingle
                            Cisco Systems, Inc.
                 postal:    7025 Kit Creek Road
                            P.O. Box 14987
                            Research Triangle Park, NC 27709
                            USA
                 email:     klingle@cisco.com
                 phone:     +1-919-392-2029
                 Co-editor  Joon Maeng
                            VTEL Corporation
                 postal:    108 Wild Basin Rd.
                            Austin, TX 78746
                            USA
                 email:     joon_maeng@vtel.com
                 phone:     +1-512-437-4567

                 Co-editor  Dave Walker
                            SS8 Networks, Inc.
                 postal:    135 Michael Cowpland Drive, Suite 200
                            Kanata, ON  K2M 2E9
                            Canada
                 email:     drwalker@ss8networks.com
                 phone:     +1 613 592 2459"
        DESCRIPTION
                "Initial version have
   multiple instances of a particular type of Session Initiation Protocol (SIP)
                 MIB module. SIP is an application-layer signalling
                 protocol entity running on the
   same system.  For example, there may be Registrars for creating, modifying and terminating
                 multimedia sessions different
   domains with one or more participants.
                 These sessions include Internet multimedia conferences
                 and Internet telephone calls.  SIP is defined in
                 RFC 2543 (March 1999).

                 This completely different behaviors.

   While there are separate MIB is modules defined for the management of SIP User
                 Agents (UAs), Proxy and Redirect &
   Proxy Servers, for Registrars, and
                 registrars.

                 A for User Agent Agents, there is an application that contains both a
                 User Agent Client (UAC) and a User Agent Server (UAS).
                 A UAC is an application that initiates also a
   "common" MIB module expected to be supported by every SIP request.
                 A UAS is an application that contacts the user when entity.
   So a SIP request is received Proxy Server must support the SIP-SERVER-MIB and that returns a response on
                 behalf of SIP-
   COMMON-MIB modules.  Likewise, the user.  The response accepts, rejects, or
                 redirects Registrar must support the request.

                 A Proxy Server acts as both a client SIP-
   REGISTRAR and SIP-COMMON-MIB modules.   Here we have the requirement
   for supporting multiple instances of 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 particular MIB module in one
   system.

   This problem is solved by using the framework provided by RFC 2788
   [19].   The Network Services Monitoring MIB applTable will be
   populated with entries corresponding to each SIP entity in the
   system.  Each entity will then have an applIndex associated with it.
   That applIndex is used throughout the SIP MIB modules' tables so
   that client. Unlike
                 a Proxy server each SIP entity can have its own set (instances) of managed
   objects defined in those MIBs.

   A quick example will illustrate how it does not initiate requests.  Unlike would conceptually appear in
   a User Agent Server it does not accept calls.

                 A Registrar is running system.  Take the example above of a server that accepts REGISTER
                 requests.  A Registrar is typically co-located Proxy Server co-
   located with a
                 Proxy or Redirect Server.

                 A Registrar.

   NETWORK-SERVICES-MIB applTable would be populated something like the
   following:

   applIndex | applName        | applDescription
   ----------+-----------------+------------------------------
       1     | "sip_proxy"     | "ACME Inc. SIP transaction occurs between a client and Proxy Ver 1.0"
   ----------+-----------------+------------------------------
       2     | "registrar"     | "ACME Inc. Registrar Ver 1.3"
   ----------+-----------------+------------------------------

   Note: There are a server
                 and comprises all messages from number of other objects in the first request sent
                 from applTable.  They
   are not included for the client to sake of brevity and for the server up to a final (non-1xx)
                 response sent from fact that they
   do not enhance the server to concept being presented.

   The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for
   the client."
        ::= { mib-2 9998 } -- to proxy (applIndex=1) and one for the registrar (applIndex=2).
   The SIP-SERVER-MIB and SIP-REGISTRAR-MIB  tables would, however,

Lingle/Maeng/Walker                                                  4
   only be assigned populated with one row  indexed by IANA

   --
   -- High Level Structure of MIB Object Definitions
   --
   sipMIBObjects             OBJECT IDENTIFIER ::= { sipMIB applIndex=1 and
   applIndex=2 respectively.

   SIP-COMMON-MIB sipCommonCfgTable might be populated as:

   applIndex | sipProtocolVersion | sipServiceOperStatus | ...
   ----------+--------------------+----------------------+----
       1     |     "SIP/2.0"      |      up(1)           |
   ----------+--------------------+----------------------+----
       2     |     "SIP/2.0"      |      restarting(6)   |
   ----------+--------------------+----------------------+----

   while the SIP-SERVER-MIB sipProxyCfgTable is populated as:

   applIndex | sipRequestMaxExpires | sipProxyStateful | ...
   ----------+----------------------+------------------+----
       1 }
   sipCommon                 OBJECT IDENTIFIER ::= { sipMIBObjects     |        3600          |      false       |
   ----------+----------------------+------------------+----

   and the SIP-REGISTRAR-MIB sipRegUserTable is populated as:

   applIndex | sipUserIndex |   sipUserUri             | ...
   ----------+--------------+--------------------------+----
       2     |       1 }
   sipUA                     OBJECT IDENTIFIER ::= { sipMIBObjects      | drwalker@ss8networks.com |
   ----------+--------------+--------------------------+----
       2 }
   sipServer                 OBJECT IDENTIFIER ::= { sipMIBObjects     |       2      | joon_maeng@vtel.com      |
   ----------+--------------+--------------------------+----
       2     |       3 }
   sipProxy                  OBJECT IDENTIFIER ::= { sipMIBObjects 4 }
   sipRedir                  OBJECT IDENTIFIER      | klingle@cisco.com        |
   ----------+--------------+--------------------------+----

   The NETWORK-SERVICES-MIB assocTable is not considered a requirement
   for SIP systems.  It is not a mandatory group for NETWORK-SERVICES-
   MIB compliance.

5. Definitions

5.1. SIP Structure Management Information

   SIP-MIB-SMI DEFINITIONS ::= { sipMIBObjects BEGIN

   IMPORTS
        MODULE-IDENTITY,
        mib-2
             FROM SNMPv2-SMI;

   sipMIB MODULE-IDENTITY
        LAST-UPDATED   "200007080000Z"
        ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
        CONTACT-INFO
                "SIP MIB Team email: sip-mib@egroups.com

                 Co-editor  Kevin Lingle
                            Cisco Systems, Inc.
                 postal:    7025 Kit Creek Road

Lingle/Maeng/Walker                                                  5 }
   sipReg                    OBJECT IDENTIFIER
                            P.O. Box 14987
                            Research Triangle Park, NC 27709
                            USA
                 email:     klingle@cisco.com
                 phone:     +1-919-392-2029

                 Co-editor  Joon Maeng
                            VTEL Corporation
                 postal:    108 Wild Basin Rd.
                            Austin, TX 78746
                            USA
                 email:     joon_maeng@vtel.com
                 phone:     +1-512-437-4567

                 Co-editor  Dave Walker
                            SS8 Networks, Inc.
                 postal:    80 Hines Road
                            Kanata, ON  K2K 2T8
                            Canada
                 email:     drwalker@ss8networks.com
                 phone:     +1 613 592 2100"
        DESCRIPTION
                "Initial version of Session Initiation Protocol (SIP)
                 MIB module that defines base OID for all other
                 SIP-related MIB Modules."
        ::= { sipMIBObjects 6 mib-2 9998 } --
   -- to be assigned by IANA

   END

5.2. SIP Textual Conventions
   --
   SipServerActions

   SIP-TC DEFINITIONS ::= BEGIN

   IMPORTS
        MODULE-IDENTITY
             FROM SNMPv2-SMI

        TEXTUAL-CONVENTION
           STATUS current
           DESCRIPTION
                "Lists the possible actions of a
             FROM SNMPv2-TC

        sipMIB
             FROM SIP-MIB-SMI;

   sipTC MODULE-IDENTITY
        LAST-UPDATED   "200007080000Z"
        ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
        CONTACT-INFO
                "SIP MIB Team email: sip-mib@egroups.com

                 Co-editor  Kevin Lingle
                            Cisco Systems, Inc.
                 postal:    7025 Kit Creek Road
                            P.O. Box 14987
                            Research Triangle Park, NC 27709

Lingle/Maeng/Walker                                                  6
                            USA
                 email:     klingle@cisco.com
                 phone:     +1-919-392-2029

                 Co-editor  Joon Maeng
                            VTEL Corporation
                 postal:    108 Wild Basin Rd.
                            Austin, TX 78746
                            USA
                 email:     joon_maeng@vtel.com
                 phone:     +1-512-437-4567

                 Co-editor  Dave Walker
                            SS8 Networks, Inc.
                 postal:    80 Hines Road
                            Kanata, ON  K2K 2T8
                            Canada
                 email:     drwalker@ss8networks.com
                 phone:     +1 613 592 2100"
        DESCRIPTION
                "Initial version of Session Initiation Protocol (SIP)
                 MIB Textual Conventions module used by other
                 SIP-related MIB Modules."
        ::= { sipMIB 1 }

   --
   -- Textual Conventions
   --
   SipServerActions ::= TEXTUAL-CONVENTION
           STATUS current
           DESCRIPTION
                "Lists the possible actions of a SIP network server.
                 A specific action may be requested by a user agent
                 as a Contact parameter in a REGISTER."
           SYNTAX INTEGER {
                          redirect(1),
                          proxy(2)
           }

   --
   -- sipCommon Group
   -- This group contains

   END

5.3. SIP Common

   SIP-COMMON-MIB DEFINITIONS ::= BEGIN

   IMPORTS
        MODULE-IDENTITY,
        OBJECT-TYPE,
        NOTIFICATION-TYPE,
        Counter32,
        Integer32,
        Gauge32,
        TimeTicks,
        Unsigned32

Lingle/Maeng/Walker                                                  7
             FROM SNMPv2-SMI

        DateAndTime,
        RowStatus,
        TruthValue
             FROM SNMPv2-TC

        MODULE-COMPLIANCE,
        OBJECT-GROUP,
        NOTIFICATION-GROUP
             FROM SNMPv2-CONF

        SnmpAdminString
             FROM SNMP-FRAMEWORK-MIB

        sipMIB
             FROM SIP-MIB-SMI

        applIndex
             FROM NETWORK-SERVICES-MIB;

   sipCommonMIB MODULE-IDENTITY
        LAST-UPDATED   "200004120000Z"
        ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
        CONTACT-INFO
                "SIP MIB Team email: sip-mib@egroups.com

                 Co-editor  Kevin Lingle
                            Cisco Systems, Inc.
                 postal:    7025 Kit Creek Road
                            P.O. Box 14987
                            Research Triangle Park, NC 27709
                            USA
                 email:     klingle@cisco.com
                 phone:     +1-919-392-2029

                 Co-editor  Joon Maeng
                            VTEL Corporation
                 postal:    108 Wild Basin Rd.
                            Austin, TX 78746
                            USA
                 email:     joon_maeng@vtel.com
                 phone:     +1-512-437-4567

                 Co-editor  Dave Walker
                            SS8 Networks, Inc.
                 postal:    80 Hines Road
                            Kanata, ON  K2K 2T8
                            Canada
                 email:     drwalker@ss8networks.com
                 phone:     +1 613 592 2100"
        DESCRIPTION
                "Initial version of Session Initiation Protocol (SIP)

Lingle/Maeng/Walker                                                  8
                 Common MIB module.  This module defines objects that are which
                 may be common to all SIP
   -- entities.
   --
   sipCommonCfg              OBJECT IDENTIFIER

                 SIP is an application-layer signalling 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 2543 (March
                 1999).

                 This MIB is defined for the managing objects which are
                 common to SIP User Agents (UAs), Proxy and Redirect
                 Servers, and Registrars.  Objects specific to each of
                 these entities may be managed using entity specific
                 MIBs defined in other modules.

                 A User Agent is an application that contains both a
                 User Agent Client (UAC) and a User Agent Server (UAS).
                 A UAC is an application that initiates a SIP request.
                 A UAS is an application that contacts the user when a
                 SIP request is received and that returns a response on
                 behalf of the user.  The response accepts, rejects, or
                 redirects the request.

                 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 Proxy server it does not initiate requests.  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."
        ::= { sipMIB 2 }

   --
   -- sipCommon Group
   -- This group contains MIB objects that are common to all SIP
   -- entities.
   --
   sipCommonCfg              OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
   sipCommonStats            OBJECT IDENTIFIER ::= { sipCommon sipCommonMIB 2 }
   sipCommonStatsSummary     OBJECT IDENTIFIER ::= { sipCommonStats 1 }
   sipCommonStatsMethod      OBJECT IDENTIFIER ::= { sipCommonStats 2 }
   sipCommonStatsInfo
   sipCommonStatusCode       OBJECT IDENTIFIER ::= { sipCommonStats 3 }
   sipCommonStatsSuccess
   sipCommonStatsTrans       OBJECT IDENTIFIER ::= { sipCommonStats 4 }
   sipCommonStatsRedirect    OBJECT IDENTIFIER ::= { sipCommonStats 5 }
   sipCommonStatsErrClient   OBJECT IDENTIFIER

Lingle/Maeng/Walker                                                  9
   --
   -- Common Configuration Objects
   --
   sipCommonCfgTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipCommonCfgEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains the common configuration objects
             applicable to all SIP entities.  Each row represents
             those objects for a particular SIP entity present in
             this system. The instances of SIP entities are
             uniquely identified by applIndex."
       ::= { sipCommonStats 6 sipCommonCfg 1 }
   sipCommonStatsErrServer   OBJECT IDENTIFIER ::=

   sipCommonCfgEntry OBJECT-TYPE
       SYNTAX     SipCommonCfgEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A row of common configuration."
       INDEX { sipCommonStats 7 applIndex }
   sipCommonStatsGlobalFail  OBJECT IDENTIFIER
       ::= { sipCommonStats 8 sipCommonCfgTable 1 }
   sipCommonStatsTrans       OBJECT IDENTIFIER

   SipCommonCfgEntry ::=
       SEQUENCE { sipCommonStats 9
                sipProtocolVersion        SnmpAdminString,
                sipServiceOperStatus      INTEGER,
                sipServiceAdminStatus     INTEGER,
                sipServiceStartTime       TimeTicks,
                sipServiceLastChange      TimeTicks,
                sipOrganization           SnmpAdminString,
                sipMaxTransactions        Unsigned32,
                sipInviteTimeout          Unsigned32,
                sipHideOperation          INTEGER,
                sipUserLocationServerAddr SnmpAdminString,
                sipCanUseCompact          TruthValue,
                sipRequestUriHostMatching TruthValue
       }

   --
   -- Common Configuration Objects
   --

   sipProtocolVersion OBJECT-TYPE
       SYNTAX      SnmpAdminString
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object will reflect the version of SIP supported by
             this user agent. SIP entity.  It will follow the same format as SIP
             version information contained in the SIP messages
             generated by this SIP entity.  For example, entities
             supporting SIP version 2 will return 'SIP/2.0' as dictated
             by RFC 2543."
       ::= { sipCommonCfg sipCommonCfgEntry 1 }

Lingle/Maeng/Walker                                                 10
   sipServiceOperStatus OBJECT-TYPE
       SYNTAX     INTEGER {
                          up(1),
                          down(2),
                          testing(3),
                          unknown(4),
                          halted(5),
                          restarting(6)
                  }
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the current operational state of the
             SIP application.

             up(1)         : The application is operating normally, and
                             is processing (receiving and possibly
                             issuing) SIP requests and responses.
             down(2)       : The application is currently unable to
                             process SIP messages.
             testing(3)    : The application is currently in test mode
                             and unable may not be able to process SIP
   messages.
             unknown(4)    : The operational status of the application
                             cannot be determined for some reason.
             halted(5)     : The application has been manually
                             prevented from processing SIP messages.
             restarting(6) : The application is booting and will soon
                             be able to process SIP messages."
       ::= { sipCommonCfg sipCommonCfgEntry 2 }

   sipServiceAdminStatus OBJECT-TYPE
       SYNTAX     INTEGER {
                          shutdown(1),
                          reset(2),
                          restart(3),
                          stop(4),
                          rts(5)
                  }
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object is used to affect the overall operational
             state of the SIP server application.

             shutdown(1) : Immediately kill the application, don't
                           restart.
             reset(2)    : Restart application, reinitialize data,
                           requires rts.
             restart(3)  : Restart application, no data loss, requires
                           rts.
             stop(4)     : Stop processing new requests, requires rts.
             rts(5)      : Return to service."

Lingle/Maeng/Walker                                                 11
       ::= { sipCommonCfg sipCommonCfgEntry 3 }

   sipServiceStartTime OBJECT-TYPE
       SYNTAX     TimeTicks
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "The value of sysUpTime at the time the SIP entity was last
             started. If the current state was entered prior to the
             last re-initialization of the local network management
             subsystem, then this object contains a zero value."
       ::= { sipCommonCfg sipCommonCfgEntry 4 }

   sipServiceLastChange OBJECT-TYPE
       SYNTAX     TimeTicks
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "The value of sysUpTime at the time the SIP entity entered
             its current operational state.  If the current state was
             entered prior to the last re-initialization of the local
             network management subsystem, then this object contains a
             zero value."
       ::= { sipCommonCfg sipCommonCfgEntry 5 }

   --
   -- Support for multiple ports
   --
   sipPortTable

   sipOrganization OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipPortEntry     SnmpAdminString
       MAX-ACCESS not-accessible read-write
       STATUS     current
       DESCRIPTION
            "This table object contains the list name of ports that this SIP entity
             is allowed to use.  These ports can be advertised using the Contact header in a REGISTER organization issuing
             the request or response.
             Port 5060 (the default SIP port registered with IANA) must
             always  It may also be present in this table." inserted by a
             proxy at a boundary of an organization.  If the object
             exists, it is inserted into requests and responses."
       REFERENCE
             "RFC 2543, Section 6.24"
       ::= { sipCommonCfg sipCommonCfgEntry 6 }

   sipPortEntry

   sipMaxTransactions OBJECT-TYPE
       SYNTAX     SipPortEntry     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible read-only
       STATUS     current
       DESCRIPTION
            "Specification
            "This object indicates the maximum number of a particular port."
       INDEX { sipPort }
       ::= { sipPortTable 1 }

   SipPortEntry simultaneous
             transactions that the SIP entity can manage."
       ::=
       SEQUENCE {
                sipPort                 INTEGER,
                sipTransport            INTEGER,
                sipPortStatus           RowStatus sipCommonCfgEntry 7 }

   sipPort

   sipInviteTimeout OBJECT-TYPE
       SYNTAX     INTEGER (0..65535)     Unsigned32 (0..4294967295)
       UNITS      "seconds"
       MAX-ACCESS not-accessible read-write
       STATUS     current
       DESCRIPTION

Lingle/Maeng/Walker                                                 12
            "This object reflects a particular port that can be used by specifies the default duration that a SIP application."
             client will wait for a response to an INVITE request.

             For proxy servers, if a received request contained an
             Expires header, then the value in the header takes
             precedence.  The server returns a 408 Request Timeout if
             no response is received before
             expiration of the request timer.

             For user agent clients, this value is inserted into the
             Expires header."
       ::= { sipPortEntry 1 sipCommonCfgEntry 8 }

   sipTransport

   sipHideOperation OBJECT-TYPE
       SYNTAX     INTEGER {
                          udp(1),
                          tcp(2),
                          udpAndTcp(3)
                          none(1),
                          hop(2),
                          route(3)
                  }
       MAX-ACCESS read-create read-write
       STATUS     current
       DESCRIPTION
            "This object will specify the transport protocol specifies which type of Hide header the SIP
             application will use server
             adds to receive SIP messages.

             udp(1)       : Use requests.  These headers are normally added by a
             User Datagram Protocol.
             tcp(2) Agent, but may be added by a proxy.  The value of
             this object does not affect processing of Hide headers in
             received requests.

             The value of this object only applies to requests that do
             not contain a Hide:route header.

             none(1)  : Use Transmission Control Protocol.
             udpAndTcp(3) The server doesn't insert a Hide header.
             hop(2)   : Use both UDP and TCP." The server inserts a Hide:hop header.
             route(3) : The server inserts a Hide:route header."
       REFERENCE
             "RFC 2543, Section 6.22"
       DEFVAL { none }
       ::= { sipPortEntry 2 sipCommonCfgEntry 9 }

   sipPortStatus

   sipUserLocationServerAddr OBJECT-TYPE
       SYNTAX     RowStatus      SnmpAdminString
       MAX-ACCESS read-create  read-write
       STATUS      current
       DESCRIPTION
            "The row status
            "This object will specify the address of the entry. This object is required User Location
             Server (ULS) being used to
             create or delete rows remotely by resolve the location of end
             points.

             This could be a manager.  The row
             associated with port 5060 need not be created and cannot
             be deleted.  It is always present in the table."
       ::= { sipPortEntry 3 }

   --
   -- Support for multiple non-SIP URIs
   --
   sipUriSupportedTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipUriSupportedEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains Domain Name Server (DNS) or a list of URIs supported by the SIP
             entity. These are
             proxy/redirect server in addition to the SIP URL which must
             necessarily case where this entity is a
             user agent. This could be supported.  Normally the list some sort of URIs
             supported by an database server if
             this entity is static (i.e. will not change
             over time).

             A URI a proxy/redirect server.

             The format of the address follows the IETF service

Lingle/Maeng/Walker                                                 13
             location protocol. The syntax is as follows:

                mapping-type:type-specific-syntax

             The mapping-type specifies a Uniform Resource Identifier (as defined in RFC
             2396).

             URIs could, scheme for mapping the
             matching dial  string to a target server. The type-
             specific-syntax is exactly that, something that the
             particular mapping scheme can understand.
             For example, contain URLs
                Session target           Meaning
                ipv4:171.68.13.55:1006   The session target is the IP
                                         version 4 address of
                                         171.68.13.55 and port 1006.
                dns:pots.cisco.com       The session target is the IP
                                         host with dns name
                                         pots.cisco.com.

             The valid Mapping type definitions for phones, fax, or
             irc if they were defined) the peer are as
             follows:
                ipv4  - Syntax: ipv4:w.x.y.z:port or a mailto: (RFC 2368) URL."
       REFERENCE
             "RFC 2543, Section 6.13"  ipv4:w.x.y.z
                dns   - Syntax: dns:host.domain."
       ::= { sipCommonCfg 7 sipCommonCfgEntry 10 }

   sipUriSupportedEntry

   sipCanUseCompact OBJECT-TYPE
       SYNTAX     SipUriSupportedEntry     TruthValue
       MAX-ACCESS not-accessible read-only
       STATUS     current
       DESCRIPTION

            "A particular non-SIP URI supported by
            "This object specifies whether or not the SIP entity."
       INDEX { sipUriSupportedIndex }
       ::= { sipUriSupportedTable 1 }

   SipUriSupportedEntry ::=
       SEQUENCE {
                sipUriSupportedIndex           Unsigned32,
                sipUriSupported                SnmpAdminString
       }

   sipUriSupportedIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This object uniquely identifies a conceptual row client is able
             to use the compact encoding form in the table." requests it sends.

             If the value of this object is TRUE, the client is able to
             encode outgoing messages using the compact encoding form.
             If the value is FALSE, the client is unable to encode
             outgoing messages using the compact form."
        REFERENCE
             "RFC 2543, Section 9"
        ::= { sipUriSupportedEntry 1 sipCommonCfgEntry 11 }

   sipUriSupported

   sipRequestUriHostMatching OBJECT-TYPE
       SYNTAX SnmpAdminString     TruthValue
       MAX-ACCESS read-only read-write
       STATUS     current
       DESCRIPTION
            "This object indicates a particular non-SIP URI supported
             by the SIP entity.  Only specifies whether or not the scheme itself (as described host in RFC 2396)
             RequestURI must match server's host name.

             If the value of this object is indicated.  For example, TRUE, then the server
             requires a match, and if the mailto:
             URLs are supported,then RequestURI doesn't match the table entry contains 'mailto'
             without
             server's host name, a 404 Not Found status code is
             returned by the colon." server.
             If the value is FALSE, then no match is required."
       REFERENCE
            "RFC 2396 section 3" 2543, Section 4.3"

Lingle/Maeng/Walker                                                 14
       ::= { sipUriSupportedEntry 2 sipCommonCfgEntry 12 }

   --
   -- Support for features which may be requested in Proxy-Require
   -- and Require headers multiple ports
   --
   sipFtrSupportedTable
   sipPortTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipFtrSupportedEntry SipPortEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains a the list of the non-standard features
             supported by the ports that each SIP entity, and which may be required by
             a peer. Definition of such features entity
             in this system is outside allowed to use.  These ports can be
             advertised using the scope Contact header in a REGISTER request
             or response. The instances of SIP, which only provides mechanisms whereby support for
             specific features may be signalled or requested.

             For example, a user agent client may require that a server
             support the 'com.example.billing' feature, which it would
             indicate in a Require header.  Such a client would have
             a row in its sipFtrSupportedTable containing the string
             'com.example.billing'.  Similarly, a server which is
             capable of handling requests for such features would list
             the string in its sipFtrSupportedTable.

             If a server does not support the required feature
             (indicated in a Require header to a UAS, or in a Proxy-
             Require to a proxy server), the server returns a 420 Bad
             Extension listing the feature in an Unsupported header.

             Normally the list of such features supported SIP entities are uniquely
             identified by an entity
             is static (i.e. will not change over time)."
       REFERENCE
            "RFC 2543, Sections 6.28, 6.30, and 6.38" applIndex."
       ::= { sipCommonCfg 8 2 }

   sipFtrSupportedEntry

   sipPortEntry OBJECT-TYPE
       SYNTAX SipFtrSupportedEntry     SipPortEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A particular non-standard feature supported by the SIP
             entity, and which may be required by
            "Specification of a peer." particular port."
       INDEX { sipFtrSupportedIndex applIndex, sipPort }
       ::= { sipFtrSupportedTable sipPortTable 1 }

   SipFtrSupportedEntry

   SipPortEntry ::=
       SEQUENCE {
                sipFtrSupportedIndex           Unsigned32,
                sipFtrSupported                SnmpAdminString
                sipPort                 INTEGER,
                sipTransport            INTEGER,
                sipPortStatus           RowStatus
       }

   sipFtrSupportedIndex

   sipPort OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)     INTEGER (1..65535)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This object uniquely identifies reflects a conceptual row in particular port that can be used by
             the
             table." SIP application."
       ::= { sipFtrSupportedEntry sipPortEntry 1 }

   sipFtrSupported

   sipTransport OBJECT-TYPE
       SYNTAX     SnmpAdminString     INTEGER {
                          udp(1),
                          tcp(2),
                          udpAndTcp(3)
                  }
       MAX-ACCESS read-only read-create
       STATUS     current
       DESCRIPTION
            "This object indicates a particular non-standard feature
             which is supported by will specify the transport protocol the SIP entity."
             application will use to receive SIP messages.

Lingle/Maeng/Walker                                                 15
             udp(1)       : Use User Datagram Protocol.
             tcp(2)       : Use Transmission Control Protocol.
             udpAndTcp(3) : Use both UDP and TCP."
       ::= { sipFtrSupportedEntry sipPortEntry 2 }

   sipPortStatus OBJECT-TYPE
       SYNTAX     RowStatus
       MAX-ACCESS read-create
       STATUS     current
       DESCRIPTION
            "The row status of the entry. This object is required to
             create or delete rows remotely by a manager.  The row
             associated with port 5060 need not be created and cannot
             be deleted.  It is always present in the table."
       ::= { sipPortEntry 3 }

   --
   -- Additional Common Configuration Objects
   --
   sipOrganization
   -- Support for multiple non-SIP URIs
   --
   sipUriSupportedTable OBJECT-TYPE
       SYNTAX     SnmpAdminString     SEQUENCE OF SipUriSupportedEntry
       MAX-ACCESS read-write not-accessible
       STATUS     current
       DESCRIPTION
            "This object table contains the name a list of URIs supported by each SIP
             entity in this system. These are in addition to the organization issuing
             the request or response.  It may also SIP
             URL which must necessarily be inserted supported.  Normally the
             list of URIs supported by an entity is static (i.e. will
             not change over time).

             A URI is a
             proxy at Uniform Resource Identifier (as defined in RFC
             2396).

             URIs could, for example, contain URLs for phones, fax, or
             irc if they were defined) or a boundary mailto: (RFC 2368) URL.

             The instances of an organization.  If the object
             exists, it is inserted into requests and responses." SIP entities are uniquely identified
             by applIndex."
       REFERENCE
             "RFC 2543, Section 6.24" 6.13"
       ::= { sipCommonCfg 9 3 }

   sipMaxTransactions

   sipUriSupportedEntry OBJECT-TYPE
       SYNTAX     SipUriSupportedEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A particular non-SIP URI supported by the SIP entity."
       INDEX { applIndex, sipUriSupportedIndex }
       ::= { sipUriSupportedTable 1 }

   SipUriSupportedEntry ::=
       SEQUENCE {

Lingle/Maeng/Walker                                                 16
                sipUriSupportedIndex           Unsigned32,
                sipUriSupported                SnmpAdminString
       }

   sipUriSupportedIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object indicates the maximum number of simultaneous
             transactions that uniquely identifies a conceptual row
             in the SIP entity can manage." table."
       ::= { sipCommonCfg 10 sipUriSupportedEntry 1 }

   sipRequestDfltExpires

   sipUriSupported OBJECT-TYPE
       SYNTAX     Unsigned32 (0..4294967295)
       UNITS      "seconds" SnmpAdminString
       MAX-ACCESS read-write read-only
       STATUS current
       DESCRIPTION
            "This object specifies the default duration that indicates a particular non-SIP URI supported
             by the SIP
             client will wait for a response to an INVITE request.

             For proxy servers, if a received request contained an
             Expires header, then entity.  Only the value scheme itself (as described
             in the header takes
             precedence.  The server returns a 408 Request Timeout if
             no response RFC 2396) is received before
             expiration of the request timer. indicated.  For user agent clients, this value is inserted into example, if the
             Expires header." mailto:
             URLs are supported,then the table entry contains 'mailto'
             without the colon."
       REFERENCE
             "RFC 2396 section 3"
       ::= { sipCommonCfg 11 sipUriSupportedEntry 2 }

   sipHideOperation

   --
   -- Support for features which may be requested in Proxy-Require
   -- and Require headers
   --
   sipFtrSupportedTable OBJECT-TYPE
       SYNTAX     INTEGER {
                          none(1),
                          hop(2),
                          route(3)
                  }     SEQUENCE OF SipFtrSupportedEntry
       MAX-ACCESS read-write not-accessible
       STATUS     current
       DESCRIPTION
            "This object specifies which type table contains a list of Hide header the server
             adds to requests.  These headers are normally added non-standard features
             supported by a
             User Agent, but each SIP entity in this system, and which
             may be added required by a proxy.  The value of
             this object does not affect processing peer. Definition of Hide headers in
             received requests.

             The value such features is
             outside the scope of this object SIP, which only applies to requests provides mechanisms
             whereby support for specific features may be signalled or
             requested.

             For example, a user agent client may require that do
             not contain a Hide:route header.

             none(1)  : The server doesn't insert
             support the 'com.example.billing' feature, which it would
             indicate in a Hide Require header.
             hop(2)   : The server inserts  Such a Hide:hop header.
             route(3) : The server inserts client would have
             a Hide:route header."
       REFERENCE
             "RFC 2543, Section 6.22"
       DEFVAL { none }
       ::= { sipCommonCfg 12 }

   sipUserLocationServerAddr OBJECT-TYPE
       SYNTAX      SnmpAdminString
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object will specify the address of the User Location
             Server (ULS) being used to resolve the location of end
             points.

             This could be a Domain Name Server (DNS) or a SIP
             proxy/redirect server row in its sipFtrSupportedTable containing the case where this entity is string
             'com.example.billing'.  Similarly, a
             user agent. This could be some sort of database server if
             this entity which is a proxy/redirect server.

             The format
             capable of the address follows the IETF service
             location protocol. The syntax is as follows:

                mapping-type:type-specific-syntax

             The mapping-type specifies a scheme handling requests for mapping such features would list
             the
             matching dial string in its sipFtrSupportedTable.

             If a server does not support the required feature
             (indicated in a Require header to a target server. The type-
             specific-syntax is exactly that, something that UAS, or in a Proxy-
             Require to a proxy server), the
             particular mapping scheme can understand.
             For example,
                Session target           Meaning
                ipv4:171.68.13.55:1006   The session target is server returns a 420 Bad

Lingle/Maeng/Walker                                                 17
             Extension listing the IP
                                         version 4 address feature in an Unsupported header.

             Normally the list of
                                         171.68.13.55 and port 1006.
                dns:pots.cisco.com       The session target such features supported by an entity
             is the IP
                                         host with dns name
                                         pots.cisco.com. static (i.e. will not change over time).

             The valid Mapping type definitions for the peer instances of SIP entities are as
             follows:
                ipv4  - Syntax: ipv4:w.x.y.z:port or  ipv4:w.x.y.z
                dns   - Syntax: dns:host.domain." uniquely identified
             by applIndex."
       REFERENCE
            "RFC 2543, Sections 6.28, 6.30, and 6.38"
       ::= { sipCommonCfg 13 4 }

   sipFtrSupportedEntry OBJECT-TYPE
       SYNTAX SipFtrSupportedEntry
       MAX-ACCESS not-accessible
       STATUS current
       DESCRIPTION
            "A particular non-standard feature supported by the SIP
             entity, and which may be required by a peer."
       INDEX { applIndex, sipFtrSupportedIndex }
       ::= { sipFtrSupportedTable 1 }

   SipFtrSupportedEntry ::=
       SEQUENCE {
                sipFtrSupportedIndex           Unsigned32,
                sipFtrSupported                SnmpAdminString
       }

   sipFtrSupportedIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This object uniquely identifies a conceptual row in the
             table."
       ::= { sipFtrSupportedEntry 1 }

   sipFtrSupported OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object indicates a particular non-standard feature
             which is supported by the SIP entity."
       ::= { sipFtrSupportedEntry 2 }

   --
   -- Common Statistics Objects
   --

   --
   --
   -- Common Statistics Objects
   --

   --
   -- Summary Statistics
   -- Summary Statistics
   --

Lingle/Maeng/Walker                                                 18
   sipSummaryStatsTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipSummaryStatsEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains the summary statistics objects
             applicable to all SIP entities.  Each row represents
             those objects for a particular SIP entity present in
             this system.  The instances of SIP entities are uniquely
             identified by applIndex."
       ::= { sipCommonStatsSummary 1 }

   sipSummaryStatsEntry OBJECT-TYPE
       SYNTAX     SipSummaryStatsEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A row of summary statistics."
       INDEX { applIndex }
       ::= { sipSummaryStatsTable 1 }

   SipSummaryStatsEntry ::=
       SEQUENCE {
                sipSummaryInRequests         Counter32,
                sipSummaryOutRequests        Counter32,
                sipSummaryInResponses        Counter32,
                sipSummaryOutResponses       Counter32,
                sipSummaryTotalTransactions  Counter32
       }

   sipSummaryInRequests OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object indicates the total number of SIP request
             messages received by the SIP entity." entity including
             retransmissions."
       ::= { sipCommonStatsSummary sipSummaryStatsEntry 1 }

   sipSummaryOutRequests OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the total number of SIP request
             messages sent out (originated and relayed) by the SIP
             entity.  Where a particular message is sent more than
             once, for example as a retransmission, or as a result of
             forking, each transmission is counted separately."
       ::= { sipCommonStatsSummary sipSummaryStatsEntry 2 }

   sipSummaryInResponses OBJECT-TYPE

Lingle/Maeng/Walker                                                 19
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the total number of SIP response
             messages received by the SIP entity." entity including
             retransmissions."
       ::= { sipCommonStatsSummary sipSummaryStatsEntry 3 }

   sipSummaryOutResponses OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the total number of SIP response
             messages sent (originated and relayed) by the SIP entity." entity
             including retransmissions."
       ::= { sipCommonStatsSummary sipSummaryStatsEntry 4 }

   sipSummaryTotalTransactions OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
            "This object contains a count of the number of transactions
             completed or in progress.

             A SIP transaction occurs between a client and a server and
             comprises all messages from the first request sent from
             the client to the server up to a final (non-1xx) response
             sent from the server to the client.

             A transaction is identified by the CSeq sequence number
             within a single call leg.  The ACK request has the same
             CSeq number as the corresponding INVITE request, but
             comprises a transaction of its own.

             In the case of a forked request, all branches count as a
             single transaction."
       ::= { sipCommonStatsSummary sipSummaryStatsEntry 5 }

   --
   -- SIP Method Statistics
   -- Total counts for each SIP method.
   --
   sipStatsInviteIns
   sipMethodStatsTable OBJECT-TYPE
       SYNTAX      Counter32     SEQUENCE OF SipMethodStatsEntry
       MAX-ACCESS  read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object reflects table contains the total number per method statistics objects
             applicable to all SIP entities.  Each row represents
             those objects for a particular SIP entity present in

Lingle/Maeng/Walker                                                 20
             this system.  The instances of INVITE requests
             received by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.1" entities are uniquely
             identified by applIndex."
       ::= { sipCommonStatsMethod 1 }

   sipStatsInviteOuts

   sipMethodStatsEntry OBJECT-TYPE
       SYNTAX      Counter32     SipMethodStatsEntry
       MAX-ACCESS  read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object
            "A row of per method statistics."
       INDEX { applIndex }
       ::= { sipMethodStatsTable 1 }

   SipMethodStatsEntry ::=
       SEQUENCE {
                sipStatsInviteIns          Counter32,
                sipStatsInviteOuts         Counter32,
                sipStatsAckIns             Counter32,
                sipStatsAckOuts            Counter32,
                sipStatsByeIns             Counter32,
                sipStatsByeOuts            Counter32,
                sipStatsCancelIns          Counter32,
                sipStatsCancelOuts         Counter32,
                sipStatsOptionsIns         Counter32,
                sipStatsOptionsOuts        Counter32,
                sipStatsRegisterIns        Counter32,
                sipStatsRegisterOuts       Counter32
       }

   sipStatsInviteIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of INVITE requests
             received by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.1"
       ::= { sipMethodStatsEntry 1 }

   sipStatsInviteOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of INVITE requests
             sent by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.1"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 2 }

   sipStatsAckIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only

Lingle/Maeng/Walker                                                 21
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of ACK requests
             received by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.2"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 3 }

   sipStatsAckOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of ACK requests sent
             by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.2"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 4 }

   sipStatsByeIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of BYE requests
             received by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.4"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 5 }

   sipStatsByeOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of BYE requests sent
             by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.4"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 6 }

   sipStatsCancelIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of CANCEL requests
             received by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.5"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 7 }

   sipStatsCancelOuts OBJECT-TYPE
       SYNTAX      Counter32

Lingle/Maeng/Walker                                                 22
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of CANCEL requests
             sent by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.5"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 8 }

   sipStatsOptionsIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of OPTIONS requests
             received by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.3"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 9 }

   sipStatsOptionsOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of OPTIONS requests
             sent by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.3"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 10 }

   sipStatsRegisterIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of REGISTER requests
             received by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.6"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 11 }

   sipStatsRegisterOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of REGISTER requests
             sent by the SIP entity."
       REFERENCE
            "RFC 2543, Section 4.2.6"
       ::= { sipCommonStatsMethod sipMethodStatsEntry 12 }

   sipStatsInfoIns

   --

Lingle/Maeng/Walker                                                 23
   -- support for extension methods
   --

   sipStatsExtMethodTable OBJECT-TYPE
       SYNTAX      Counter32      SEQUENCE OF SipStatsExtMethodEntry
       MAX-ACCESS  read-only  not-accessible
       STATUS      current
       DESCRIPTION
            "This object reflects table contains the total number list of INFO requests
             received by the extension methods which
             each SIP entity."
       REFERENCE
            "draft-ietf-sip-info-method-02.txt" entity in this system has been requested to
             monitor. The instances of SIP entities are uniquely
             identified by applIndex."
       ::= { sipCommonStatsMethod 13 2 }

   sipStatsInfoOuts

   sipStatsExtMethodEntry OBJECT-TYPE
       SYNTAX      Counter32      SipStatsExtMethodEntry
       MAX-ACCESS  read-only  not-accessible
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of INFO requests
             sent by row contains information on a particular extension
             method that the SIP entity."
       REFERENCE
            "draft-ietf-sip-info-method-02.txt" entity has been requested to monitor."
       INDEX { applIndex, sipStatsExtMethodIndex }
       ::= { sipCommonStatsMethod 14 sipStatsExtMethodTable 1 }

   --
   -- SIP Informational Response Statistics
   --
   -- These counters reflect the number of SIP messages sent and
   -- received by this system that relate to providing some
   -- informational response to the progress of processing

   SipStatsExtMethodEntry ::=
       SEQUENCE {
                sipStatsExtMethodIndex      Unsigned32,
          sipStatsExtMethodName       SnmpAdminString,
          sipStatsExtMethodIns        Counter32,
          sipStatsExtMethodOuts       Counter32,
          sipStatsExtMethodStatus     RowStatus
       }

   sipStatsExtMethodIndex OBJECT-TYPE
       SYNTAX      Unsigned32 (1..4294967295)
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
            "This object uniquely identifies a SIP
   -- request.
   --
   sipStatsInfoTryingIns conceptual row in the
             table."
       ::= { sipStatsExtMethodEntry 1 }

   sipStatsExtMethodName OBJECT-TYPE
       SYNTAX      Counter32      SnmpAdminString
       MAX-ACCESS  read-only  read-create
       STATUS      current
       DESCRIPTION
            "This object reflects contains the total number name of Trying
             (100) responses received by the SIP entity.
             Trying responses indicate particular extension
             method that some unspecified
             action is being taken on behalf of this call, but the user SIP entity has not yet been located.  Inbound Trying
             responses indicate requested to monitor.
             For example, it may contain the string 'INFO' if the
             network management station has requested that outbound INVITE requests
             sent out by this system have been received and
             are processed."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.1.1"
       ::= { sipCommonStatsInfo 1 }

   sipStatsInfoTryingOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total SIP
             entity count the number of Trying
             (100) responses messages sent by the SIP entity.
             Trying responses indicate that some unspecified
             action is being taken on behalf of this call, but
             the user has not yet been located.  Outbound Trying
             responses indicate that this system an received
             which containing an INFO method.  It is successfully
             receiving INVITE requests and processing them on
             behalf an error for any
             of the system initiating the INVITE."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.1.1" methods contained in RFC 2543 to be requested."

Lingle/Maeng/Walker                                                 24
       ::= { sipCommonStatsInfo sipStatsExtMethodEntry 2 }

   sipStatsInfoRingingIns

   sipStatsExtMethodIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Ringing
             (180) responses requests received
             by the SIP entity.
             A inbound Ringing response indicates that the UAS that is
             processing an INVITE initiated by this system has
             found a possible location where entity which requested the desired end user
             has registered recently and is trying to alert method contained in
             the user."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.1.2" sipStatsExtMethodName column."
       ::= { sipCommonStatsInfo sipStatsExtMethodEntry 3 }

   sipStatsInfoRingingOuts

   sipStatsExtMethodOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Ringing
             (180) responses requests sent
             by the SIP entity.
             A outbound Ringing response indicates that this
             system has processed an INVITE for a particular
             end user and found a possible location where that
             user has registered recently.  The system is trying
             to alert the end user and is conveying that status
             to entity which requested the system that originated method contained in
             the INVITE."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.1.2" sipStatsExtMethodName column."
       ::= { sipCommonStatsInfo sipStatsExtMethodEntry 4 }

   sipStatsInfoForwardedIns

   sipStatsExtMethodStatus OBJECT-TYPE
       SYNTAX      Counter32      RowStatus
       MAX-ACCESS  read-create
       STATUS      current
       DESCRIPTION
            "The row status of the entry. This object is required
             to create or delete rows remotely by a manager."
       ::= { sipStatsExtMethodEntry 5 }

   --
   -- SIP Response Status Codes
   --
   sipStatusCodesTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF SipStatusCodesEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
            "This table contains statistics on response status code
             classes for each SIP entity in this system. The instances
             of SIP entities are uniquely identified by applIndex."
       ::= { sipCommonStatusCode 1 }

   sipStatusCodesEntry OBJECT-TYPE
       SYNTAX      SipStatusCodesEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
            "This row contains statistics on response status codes."
       INDEX { applIndex }
       ::= { sipStatusCodesTable 1 }

Lingle/Maeng/Walker                                                 25
   SipStatusCodesEntry ::=
       SEQUENCE {
                sipStatsInfoClassIns          Counter32,
                sipStatsInfoClassOuts         Counter32,
                sipStatsSuccessClassIns       Counter32,
                sipStatsSuccessClassOuts      Counter32,
                sipStatsRedirClassIns         Counter32,
                sipStatsRedirClassOuts        Counter32,
                sipStatsReqFailClassIns       Counter32,
                sipStatsReqFailClassOuts      Counter32,
                sipStatsServerFailClassIns    Counter32,
                sipStatsServerFailClassOuts   Counter32,
                sipStatsGlobalFailClassIns    Counter32,
                sipStatsGlobalFailClassOuts   Counter32
       }

   sipStatsInfoClassIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Call Is Being
             Forwarded (181) 1xx class
             SIP responses received by the SIP entity.
             A proxy server might use a Forwarded status code to
             indicate that the call is being forwarded to a different
             set
             This class of destinations.  Inbound Forwarded responses indicate
             to this system that forwarding actions are taking place
             with regard relates to calls initiated by this system." providing some
             information concerning the progress of processing
             a SIP request."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.1.3" 7.1"
       ::= { sipCommonStatsInfo 5 sipStatusCodesEntry 1 }

   sipStatsInfoForwardedOuts

   sipStatsInfoClassOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Call Is Being
             Forwarded (181) 1xx class
             SIP responses sent by the SIP entity.
             A proxy server might use a Forwarded status code to
             indicate that the call is being forwarded to a different
             set
             This class of destinations.  Outbound Forwarded responses
             indicate this system is taking some forwarding action
             for calls and conveying that status relates to providing some
             information concerning the system that
             initiated the calls." progress of processing
             a SIP request."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.1.3" 7.1"
       ::= { sipCommonStatsInfo 6 sipStatusCodesEntry 2 }

   sipStatsInfoQueuedIns

   sipStatsSuccessClassIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Queued
             (182) 2xx class SIP
             responses received by the SIP entity.
             Inbound Queued This class of
             responses indicate that the users that
             this system is attempting relate to call are temporarily
             unavailable but successful completion of a SIP
             request."
       REFERENCE

Lingle/Maeng/Walker                                                 26
            "RFC 2543, Sections 5.1.1 & 7.2"
       ::= { sipStatusCodesEntry 3 }

   sipStatsSuccessClassOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the number of 2xx class SIP agents operating on behalf
             of those users wish to queue the calls rather than
             reject them.  When the called parties become available,
             this system can expect to receive the appropriate
             final status response.  The Reason-Phrase from the
             Queued response messages Status-Line can give further
             details about
             responses sent by the status SIP entity. This class of the call.  Multiple
             Queued
             responses relate to update this system about the status successful completion of the queued call might be received." a SIP
             request."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.1.4" 7.2"
       ::= { sipCommonStatsInfo 7 sipStatusCodesEntry 4 }

   sipStatsInfoQueuedOuts

   sipStatsRedirClassIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Queued
             (182) 3xx class SIP
             responses sent received by the SIP entity.
             Outbound Queued responses indicate that this system
             has determined that the called party is temporarily
             unavailable but the call is not rejected.  Instead,
             the call is queued until the called party becomes
             available.  Queued This class of
             responses messages are sent relate to
             the system originating the call request to convey
             the current status of redirection actions taken
             by a queued call." Redirect Server."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.1.4" 7.3"
       ::= { sipCommonStatsInfo 8 sipStatusCodesEntry 5 }

   sipStatsInfoSessionProgIns

   sipStatsRedirClassOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Session
             Progress (183) 3xx class SIP
             responses received sent by the SIP entity." entity. This class of
             responses relate to call redirection actions taken
             by a Redirect Server."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.3"
       ::= { sipCommonStatsInfo 9 sipStatusCodesEntry 6 }

   sipStatsInfoSessionProgOuts

   sipStatsReqFailClassIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Session
             Progress (183) 4xx class SIP
             responses sent received by the SIP entity." entity. This class of
             responses reflect request failure by a SIP entity
             providing a client function."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4"
       ::= { sipCommonStatsInfo 10 sipStatusCodesEntry 7 }

   --
   -- SIP Success Response Statistics
   --
   -- These counters reflect

Lingle/Maeng/Walker                                                 27
   sipStatsReqFailClassOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the number of 4xx class SIP messages
             responses sent and
   -- received by this system that relate to successful completion the SIP entity. This class of
             responses reflect request failure by a
   -- SIP request.
   --
   sipStatsSuccessOkIns entity
             providing a server function."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4"
       ::= { sipStatusCodesEntry 8 }

   sipStatsServerFailClassIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Ok
             (200) 5xx class SIP
             responses received by the SIP entity.

             The meaning This class of inbound Ok
             responses depends
             on the method used in the associated request.

             BYE      : The Ok response means the call has
                        been terminated.

             CANCEL   : The Ok response means the search for
                        the end user has been cancelled.

             INVITE   : The Ok response means the called party
                        has agreed to participate in the call.

             OPTIONS  : The Ok response means the called party
                        has agreed to share its capabilities.

             REGISTER : The Ok response means the registration
                        has succeeded.

             INFO     : The Ok response means the INFO request
                        was reflect failure responses received by a
             SIP entity providing a client function.  These
             responses are not definite failures and processed correctly." must not
             terminate a search if other possible locations remain
             untried."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.2.1" 7.5"
       ::= { sipCommonStatsSuccess 1 sipStatusCodesEntry 9 }

   sipStatsSuccessOkOuts

   sipStatsServerFailClassOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Ok
             (200) 5xx class SIP
             responses sent by the SIP entity.
             The meaning This class of outbound Ok
             responses depends
             on the method used in the associated request.

             BYE      : The Ok response means the call has
                        been terminated.

             CANCEL   : The Ok response means the search for
                        the end user has been cancelled.

             INVITE   : The Ok response means the called party
                        has agreed to participate in the call.

             OPTIONS  : The Ok response means the called party
                        has agreed to share its capabilities.

             REGISTER : The Ok response means the registration
                        has succeeded.

             INFO     : The Ok response means the INFO request
                        was received reflect failure responses sent by a SIP
             entity providing a server function.  These
             responses are not definite failures and processed correctly." must not
             terminate a search if other possible locations remain
             untried."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.2.1" 7.5"
       ::= { sipCommonStatsSuccess 2 sipStatusCodesEntry 10 }

   --
   -- SIP Redirection Response Statistics
   --
   -- These counters reflect the number of SIP messages sent and
   -- received by this system that relate to call redirection actions
   -- taken by a Redirect Server.
   --
   sipStatsRedirMultipleChoiceIns

   sipStatsGlobalFailClassIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Multiple
             Choices (300) 6xx class SIP
             responses received by the SIP entity.
             Multiple Choices This class of
             responses reflect failure responses received by a

Lingle/Maeng/Walker                                                 28
             SIP entity providing a client function.

             The responses generally indicate that the called
             party can be reached at several different locations
             and the a server cannot or prefers has
             definitive information about a particular called party,
             not to proxy just the
             request." particular instance indicated in the
             Request-URI.  All further searches for this user are
             doomed to failure and pending searches should be
             terminated."
       REFERENCE
            "RFC 2543, Section Sections 5.1.1 & 7.3.1" 7.6"
       ::= { sipCommonStatsRedirect 1 sipStatusCodesEntry 11 }

   sipStatsRedirMultipleChoiceOuts

   sipStatsGlobalFailClassOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Multiple
             Choices (300) 6xx class SIP
             responses sent by the SIP entity.
             Multiple Choices This class of
             responses reflect failure responses sent by a SIP
             entity providing a server function.

             The responses generally indicate that the called
             party can be reached at several different locations
             and the a server cannot or prefers has
             definitive information about a particular called party,
             not to proxy just the
             request." particular instance indicated in the
             Request-URI.  All further searches for this user are
             doomed to failure and pending searches should be
             terminated."
       REFERENCE
            "RFC 2543, Section Sections 5.1.1 & 7.3.1" 7.6"
       ::= { sipCommonStatsRedirect 2 sipStatusCodesEntry 12 }

   sipStatsRedirMovedPermIns

   --
   -- support for specific status codes
   --

   sipCommonStatusCodeTable OBJECT-TYPE
       SYNTAX      Counter32      SEQUENCE OF SipCommonStatusCodeEntry
       MAX-ACCESS  read-only  not-accessible
       STATUS      current
       DESCRIPTION
            "This object reflects table contains the total number list of Moved
             Permanently (301) responses received SIP status codes which
             each SIP entity in this system has been requested to
             monitor. The instances of SIP entities are uniquely
             identified by applIndex."
       ::= { sipCommonStatusCode 2 }

   sipCommonStatusCodeEntry OBJECT-TYPE
       SYNTAX      SipCommonStatusCodeEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
            "This row contains information on a particular SIP status
             code that the SIP entity.
             Moved Permanently responses indicate entity has been requested to monitor."

Lingle/Maeng/Walker                                                 29
       INDEX { applIndex, sipCommonStatusCodeValue }
       ::= { sipCommonStatusCodeTable 1 }

   SipCommonStatusCodeEntry ::=
       SEQUENCE {
          sipCommonStatusCodeValue      INTEGER,
          sipCommonStatusCodeIns        Counter32,
          sipCommonStatusCodeOuts       Counter32,
          sipCommonStatusCodeSendNotif  TruthValue,
          sipCommonStatusCodeStatus     RowStatus
       }

   sipCommonStatusCodeValue OBJECT-TYPE
       SYNTAX      INTEGER (100..999)
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
            "This object contains a SIP status code value that the called party
             can no longer be found at SIP
             entity has been requested to monitor.  All of the address offered other
             information in the
             request and the requesting UAC should retry at the new
             address given by the Contact header field of the
             response."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.3.2" row is related to this value."
       ::= { sipCommonStatsRedirect 3 sipCommonStatusCodeEntry 1 }

   sipStatsRedirMovedPermOuts

   sipCommonStatusCodeIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Moved
             Permanently (301) responses sent by response messages
             received by the SIP entity.
             Moved Permanently responses indicate that the called party
             can no longer be found at entity with the address offered status code value
             contained in the
             request and the requesting UAC should retry at the new
             address given by the Contact header field of the
             response."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.3.2" sipCommonStatusCodeValue column."
       ::= { sipCommonStatsRedirect 4 sipCommonStatusCodeEntry 2 }

   sipStatsRedirMovedTempIns

   sipCommonStatusCodeOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Moved
             Temporarily (302) responses received response messages
             sent by the SIP entity.
             Moved Temporarily responses indicate the UAC should
             retry the request directed at the new address(es)
             given by the Contact header field of the response.
             The duration of this redirection can be indicated
             through entity with the Expires header.  If no explicit expiration
             time is given, status code value
             contained in the new address(es) are only valid
             for this call."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.3.3" sipCommonStatusCodeValue column."
       ::= { sipCommonStatsRedirect 5 sipCommonStatusCodeEntry 3 }

   sipStatsRedirMovedTempOuts

   sipCommonStatusCodeSendNotif OBJECT-TYPE
       SYNTAX      Counter32      TruthValue
       MAX-ACCESS  read-only  read-create
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Moved
             Temporarily (302) responses controls whether a notification is sent by the SIP entity.
             Moved Temporarily responses indicate the UAC should
             retry the request directed at when
             the new address(es)
             given by status code value specified in the Contact header field of
             sipCommonStatusCodeValue column is sent or received.
             If the response.
             The duration value of this redirection can be indicated
             through the Expires header. object is TRUE, then a notification
             is sent.  If it is FALSE, no explicit expiration
             time notification is given, the new address(es) are only valid
             for this call."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.3.3" sent."
       DEFVAL { false }
       ::= { sipCommonStatsRedirect 6 sipCommonStatusCodeEntry 4 }

   sipStatsRedirSeeOtherIns

Lingle/Maeng/Walker                                                 30
   sipCommonStatusCodeStatus OBJECT-TYPE
       SYNTAX      Counter32      RowStatus
       MAX-ACCESS  read-only  read-create
       STATUS      current
       DESCRIPTION
            "This object reflects the total number
            "The row status of See Other
             (303) responses received by the SIP entity."
       REFERENCE
            "RFC 2543, Sections 5.1.1" entry. This object is required
             to create or delete rows remotely by a manager."
       ::= { sipCommonStatsRedirect 7 sipCommonStatusCodeEntry 5 }

   sipStatsRedirSeeOtherOuts

   --
   -- Transaction Statistics
   --
   sipCurrentTransTable OBJECT-TYPE
       SYNTAX      Counter32     SEQUENCE OF SipCurrentTransEntry
       MAX-ACCESS  read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object reflects table contains information on the total number of See Other
             (303) transactions
             currently awaiting definitive responses sent by the each SIP entity."
       REFERENCE
            "RFC 2543, Sections 5.1.1"
             entity in this system.  The instances of SIP entities
             are uniquely identified by applIndex."
       ::= { sipCommonStatsRedirect 8 sipCommonStatsTrans 1 }
   sipStatsRedirUseProxyIns

   sipCurrentTransEntry OBJECT-TYPE
       SYNTAX      Counter32     SipCurrentTransEntry
       MAX-ACCESS  read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object reflects the total number of Use Proxy
             (305) responses received by the
            "Information on a particular SIP entity.
             Use Proxy responses indicate that requested resources
             must be accessed through the proxy given by the
             Contact header field of the response.  The recipient
             of this response is expected to repeat this single
             request via the proxy."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.3.4" entities' current
             transactions."
       INDEX { applIndex }
       ::= { sipCommonStatsRedirect 9 sipCurrentTransTable 1 }

   SipCurrentTransEntry ::=
       SEQUENCE {
                sipCurrentTransactions  Gauge32
       }

   sipStatsRedirUseProxyOuts

   sipCurrentTransactions OBJECT-TYPE
       SYNTAX      Counter32     Gauge32 (0..4294967295)
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number of Use Proxy
             (305) responses sent by the SIP entity.
             See Other responses indicate that requested resources
             must be accessed through the proxy given by transactions awaiting
             definitive (non-1xx) response.  In the
             Contact header field case of the response. a forked
             request, all branches count as a single transaction.  The recipient
             value of this response is expected to repeat this single
             request via object will reflect the proxy."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.3.4" number of rows in
             sipTransactionTable."
   ::= { sipCommonStatsRedirect 10 sipCurrentTransEntry 1 }

   sipStatsRedirAltServiceIns

   sipTransactionTable OBJECT-TYPE

Lingle/Maeng/Walker                                                 31
       SYNTAX      Counter32     SEQUENCE OF SipTransactionEntry
       MAX-ACCESS  read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object reflects table contains information on all of the total number transactions
             currently being processed (the count of Alternative
             Service (380) responses received by such transactions
             is maintained in the sipCurrentTransactions object) by a
             particular SIP entity.
             Alternative Service responses indicate that the call
             was not successful, but alternative services are
             possible.  Those alternative services are described entity in the message body this system. The instances of the response."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.3.5" SIP
             entities are uniquely identified by applIndex."
       ::= { sipCommonStatsRedirect 11 sipCommonStatsTrans 2 }

   sipStatsRedirAltServiceOuts

   sipTransactionEntry OBJECT-TYPE
       SYNTAX      Counter32     SipTransactionEntry
       MAX-ACCESS  read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object reflects the total number of Alternative
             Service (380) responses sent by the SIP entity.
             Alternative Service responses indicate that the call
             was not successful, but alternative services are
             possible.  Those alternative services are described
             in the message body of the response."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.3.5"
            "Information on a particular current transaction."
       INDEX { applIndex, sipTransIndex }
       ::= { sipCommonStatsRedirect 12 sipTransactionTable 1 }
   --
   -- SIP Client Error Responses Statistics
   --
   -- The following Inbound counters reflect failure responses received
   -- by a SIP entity providing a client function.
   --
   -- The following Outbound counters reflect failure responses sent by
   -- a SIP entity providing a server function.
   --
   -- Servers generally send these responses to Clients.
   --
   sipStatsClientBadRequestIns

   SipTransactionEntry ::=
       SEQUENCE {
                sipTransIndex                         Unsigned32,
                sipTransTo                            SnmpAdminString,
                sipTransFrom                          SnmpAdminString,
                sipTransCallId                        SnmpAdminString,
                sipTransCSeq                          Unsigned32,
                sipTransState                         INTEGER,
                sipTransNumOutstandingBranches        Integer32,
                sipTransExpiry                        DateAndTime,
                sipTransCallingPartyContentType       SnmpAdminString,
                sipTransCalledPartyContentType        SnmpAdminString
       }

   sipTransIndex OBJECT-TYPE
       SYNTAX      Counter32     Unsigned32 (0..4294967295)
       MAX-ACCESS  read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object reflects the total number of Bad Request (400)
             responses received by uniquely identifies a conceptual row in the SIP entity. Inbound Bad Request
             responses indicate that requests issued by this system
             could not be understood due to malformed syntax."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.1"
             table."
       ::= { sipCommonStatsErrClient sipTransactionEntry 1 }

   sipStatsClientBadRequestOuts

   sipTransTo OBJECT-TYPE
       SYNTAX      Counter32     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number value of Bad Request (400)
             responses sent by the SIP entity.  Outbound Bad Request
             responses indicate that requests received by this system
             could not be understood due to malformed syntax."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.1" To header in request
             message."
       ::= { sipCommonStatsErrClient sipTransactionEntry 2 }

   sipStatsClientUnauthorizedIns

   sipTransFrom OBJECT-TYPE
       SYNTAX      Counter32     SnmpAdminString

Lingle/Maeng/Walker                                                 32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number value of Unauthorized
             (401) responses received by the SIP entity. Inbound
             Unauthorized responses indicate that requests issued by
             this system require user authentication."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.2" From header in the
             request message."
       ::= { sipCommonStatsErrClient sipTransactionEntry 3 }

   sipStatsClientUnauthorizedOuts

   sipTransCallId OBJECT-TYPE
       SYNTAX      Counter32     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number value of Unathorized (401)
             responses sent by the SIP entity.
             Outbound Unauthorized responses indicate that requests
             received by this system require user authentication."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.2" CallId value in the
             request message."
       ::= { sipCommonStatsErrClient sipTransactionEntry 4 }

   sipStatsClientPaymentReqdIns

   sipTransCSeq OBJECT-TYPE
       SYNTAX      Counter32     Unsigned32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number of Payment Required
             (402) responses received by CSeq value for the SIP entity."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.3" current
             transaction."
       ::= { sipCommonStatsErrClient sipTransactionEntry 5 }

   sipStatsClientPaymentReqdOuts

   sipTransState OBJECT-TYPE
       SYNTAX      Counter32     INTEGER {
                          null(1),
                          initial(2),
                          calling(3),
                          ringing(4),
                          completed(5),
                          callProceeding(6),
                          failure(7),
                          success(8),
                          confirmed(9)
                  }
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number current state of Payment Required
             (402) responses sent by the SIP entity."
             transaction.

             null(1)           : The SIP entity is not active.
             initial(2)        : Prior to sending or receiving any
                                 request.
             calling(3)        : After sending the request and prior to
                                 receiving any response.
             ringing(4)        : After receiving one or more
                                 informational (1xx) responses.
             completed(5)      : After ACK has been sent following
                                 reception of definitive response.
             callProceeding(6) : Entered on reception of an INVITE.
             failure(7)        : Entered when call fails(send status

Lingle/Maeng/Walker                                                 33
                                 code>=300).
             success(8)        : Entered when user answers(send status
                                 code=200).
             confirmed(9)      : Entered on reception of an ACK in
                                 failure or success states."
       REFERENCE
           "RFC 2543, Sections 5.1.1 & 7.4.3" Figures 12 and 13"
   ::= { sipCommonStatsErrClient sipTransactionEntry 6 }

   sipStatsClientForbiddenIns

   sipTransNumOutstandingBranches OBJECT-TYPE
       SYNTAX      Counter32     Integer32 (0..255)
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects contains a count of the total number of Forbidden (403)
             responses received by the SIP entity.  Inbound Forbidden
             responses indicate that requests issued by this system are
             understood by the server but the server refuses to fulfill
             the request.  Authorization branches
             awaiting a final response.  Only a forking proxy will not help and the requests
             should not be repeated."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.4" have
             a value greater than one."
       ::= { sipCommonStatsErrClient sipTransactionEntry 7 }

   sipStatsClientForbiddenOuts

   sipTransExpiry OBJECT-TYPE
       SYNTAX      Counter32     DateAndTime
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects the total number contains an indication of Forbidden (403)
             responses sent by when the SIP entity. Outbound Forbidden
             responses indicate that requests received by this system
             are understood but this system is refusing transaction
             will be considered to
             fulfill have timed out.  This value is based
             on the requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.4" value in the Expires header, or the value of the
             sipInviteTimeout object if no Expires value was
             specified in the original request."
       ::= { sipCommonStatsErrClient sipTransactionEntry 8 }

   sipStatsClientNotFoundIns

   sipTransCallingPartyContentType OBJECT-TYPE
       SYNTAX      Counter32     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number content type of Not Found (404)
             responses received by the SIP entity.
             Inbound Not Found responses indicate that the called party
             does not exist at transaction,
             including parameters, as indicated by the domain specified session
             initiator. All optional white space is removed from
             subfields in the Request-URI
             or media-type specification.  It may
             indicate mime multipart, in which case the domain is not handled multiple
             entries are separated by the recipient of the
             request." spaces."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.5" Section 6.16 and RFC 2068 section 3.7"
       ::= { sipCommonStatsErrClient sipTransactionEntry 9 }

   sipStatsClientNotFoundOuts

   sipTransCalledPartyContentType OBJECT-TYPE
       SYNTAX      Counter32     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number content type of Not Found (404)
             responses sent by the SIP entity.
             Outbound Not Found responses indicate that this system
             knows that the called party does not exist at transaction,
             including parameters, as indicated by the domain
             specified session
             respondant.  All optional white space is removed from

Lingle/Maeng/Walker                                                 34
             subfields in the Request-URI or media-type specification.  It may
             indicate mime multipart, in which case the domain is not handled multiple
             entries are separated by this system." spaces."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.5" Section 6.16 and RFC 2068, Section 3.7"
       ::= { sipCommonStatsErrClient sipTransactionEntry 10 }

   sipStatsClientMethNotAllowedIns

   --
   -- Other Common Statistics
   --
   sipOtherStatsTable OBJECT-TYPE
       SYNTAX      Counter32     SEQUENCE OF SipOtherStatsEntry
       MAX-ACCESS  read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object reflects the total number of Method Not
             Allowed (405) responses received table contains other common statistics supported by the
             each SIP entity.
             Inbound Method Not Allowed responses indicate that
             requests issued by entity in this system have specified a system. The instances of SIP method
             in the Request-Line that is not allowed for the address
             entities are uniquely identified by the Request-URI."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.6" applIndex."
       ::= { sipCommonStatsErrClient 11 sipCommonStats 5 }

   sipOtherStatsEntry OBJECT-TYPE
       SYNTAX     SipOtherStatsEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "Information on a particular SIP entities' other common
             statistics."
       INDEX { applIndex }
       ::= { sipOtherStatsTable 1 }

   SipOtherStatsEntry ::=
       SEQUENCE {
                sipNumUnsupportedUris  Counter32
       }

   sipStatsClientMethNotAllowedOuts

   sipNumUnsupportedUris OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object reflects the total number
            "Number of Method Not
             Allowed (405) responses sent by the SIP entity.
             Outbound Method Not Allowed responses indicate that
             requests RequestURIs received by this system have SIP methods
             specified in the Request-Line with unsupported scheme.
             A server normally responds to such requests with a 400 Bad
             Request status code."
       ::= { sipOtherStatsEntry 5 }

   --
   -- Notifications
   --
   sipCommonMIBNotifPrefix    OBJECT IDENTIFIER ::= { sipCommonMIB 7 }
   sipCommonMIBNotif          OBJECT IDENTIFIER ::= {
   sipCommonMIBNotifPrefix 0 }

Lingle/Maeng/Walker                                                 35
   sipStatusCodeNotif         NOTIFICATION-TYPE
       OBJECTS {
               sipStatusCodeNotifValue,
               sipStatusCodeNotifTo,
               sipStatusCodeNotifFrom,
               sipStatusCodeNotifCallId,
               sipStatusCodeNotifCSeq
       }
       STATUS  current
       DESCRIPTION
            "Signifies that are not allowed for the
             address identified by the Request-URI."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.6" a specific status code has been used."
       ::= { sipCommonStatsErrClient 12 sipCommonMIBNotif 1 }

   sipStatsClientNotAcceptableIns

   sipStatusCodeNotifValue    OBJECT-TYPE
       SYNTAX      Counter32     INTEGER (100..999)
       MAX-ACCESS  read-only accessible-for-notify
       STATUS     current
       DESCRIPTION
            "This object reflects the total number of Not Acceptable
             (406) responses received by contains the SIP entity.

             Inbound Not Acceptable responses indicate status code that caused the
             resources identified by requests issued by this system
             cannot generate responses with content characteristics
             acceptable to this system according to the accept headers
             sent in the requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.7"
             notification."
       ::= { sipCommonStatsErrClient 13 sipCommonMIBNotif 2 }

   sipStatsClientNotAcceptableOuts

   sipStatusCodeNotifTo       OBJECT-TYPE
       SYNTAX      Counter32     SnmpAdminString
       MAX-ACCESS  read-only accessible-for-notify
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number value of Not Acceptable
             (406) responses sent by the SIP entity.
             Outbound Not Acceptable responses indicate that To header in the
             resources identified by requests received by this system
             cannot generate responses with content characteristics
             acceptable to
             message containing the system sending status code that caused the requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.7"
             notification."
       ::= { sipCommonStatsErrClient 14 sipCommonMIBNotif 3 }

   sipStatsClientProxyAuthReqdIns

   sipStatusCodeNotifFrom     OBJECT-TYPE
       SYNTAX      Counter32     SnmpAdminString
       MAX-ACCESS  read-only accessible-for-notify
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number value of Proxy
             Authentication Required (407) responses received by the
             SIP entity.
             Inbound Proxy Authentication Required responses indicate
             that this system must authenticate itself with From header in the proxy
             before gaining access to
             message containing the requested resource."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.8" status code that caused the
             notification."
       ::= { sipCommonStatsErrClient 15 sipCommonMIBNotif 4 }

   sipStatsClientProxyAuthReqdOuts

   sipStatusCodeNotifCallId   OBJECT-TYPE
       SYNTAX      Counter32     SnmpAdminString
       MAX-ACCESS  read-only accessible-for-notify
       STATUS     current
       DESCRIPTION
            "This object reflects contains the total number value of Proxy
             Authenticaion Required (407) responses sent by the SIP
             entity.
             Outbound Proxy Authentication Required responses indicate CallId in the
             message containing the status code that caused the systems issuing requests being processed by this
             system must authenticate themselves with this system
             before gaining access to requested resources."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.8"
             notification."
       ::= { sipCommonStatsErrClient 16 sipCommonMIBNotif 5 }

   sipStatsClientReqTimeoutIns

   sipStatusCodeNotifCSeq     OBJECT-TYPE
       SYNTAX      Counter32     Unsigned32

Lingle/Maeng/Walker                                                 36
       MAX-ACCESS  read-only accessible-for-notify
       STATUS     current
       DESCRIPTION
            "This object reflects the total number of Request Timeout
             (408) responses received by the SIP entity.
             Inbound Request Timeout responses indicate that requests
             issued by this system are not being processed by the
             server within contains the time indicated CSeq value in the Expires header of message
             containing the request."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.9" status code that caused the notification."
       ::= { sipCommonStatsErrClient 17 sipCommonMIBNotif 6 }

   sipStatsClientReqTimeoutOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only

   --
   -- Conformance
   --
   sipCommonMIBConformance
     OBJECT IDENTIFIER ::= { sipCommonMIB 6 }
   sipCommonMIBCompliances
     OBJECT IDENTIFIER ::= { sipCommonMIBConformance 1 }
   sipCommonMIBGroups
     OBJECT IDENTIFIER ::= { sipCommonMIBConformance 2 }

   --
   -- Compliance Statements
   --
   sipCommonCompliance MODULE-COMPLIANCE
       STATUS     current
       DESCRIPTION
            "This object reflects the total number of Request Timeout
             (408) responses sent by the
            "The compliance statement for SIP entity.
             Outbound Request Timeout responses indicate that entities."

       MODULE -- this
             system is not able to produce an appropriate response
             within the time indicated in the Expires header of the
             request."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.9" module
            MANDATORY-GROUPS { sipCommonConfigGroup,
                               sipCommonStatsGroup,
                               sipCommonNotifGroup }

       ::= { sipCommonStatsErrClient 18 sipCommonMIBCompliances 1 }

   sipStatsClientConflictIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number

   --
   -- Units of Conflict (409)
             responses received by the SIP entity.
             Inbound Conflict responses indicate that requests issued
             by this system could not be completed due to a conflict
             with the current state of a requested resource."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.10"
       ::= Conformance
   --
   sipCommonConfigGroup OBJECT-GROUP
       OBJECTS { sipCommonStatsErrClient 19
               sipProtocolVersion,
               sipServiceOperStatus,
               sipServiceAdminStatus,
               sipServiceStartTime,
               sipServiceLastChange,
               sipTransport,
               sipPortStatus,
               sipUriSupported,
               sipFtrSupported,
               sipOrganization,
               sipMaxTransactions,
               sipInviteTimeout,
               sipHideOperation,
               sipUserLocationServerAddr,

Lingle/Maeng/Walker                                                 37
               sipCanUseCompact,
               sipRequestUriHostMatching,
               sipStatusCodeNotifValue,
               sipStatusCodeNotifTo,
               sipStatusCodeNotifFrom,
               sipStatusCodeNotifCallId,
               sipStatusCodeNotifCSeq
       }

   sipStatsClientConflictOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
            "This object reflects the total number
            "A collection of Conflict (409)
             responses sent by the SIP entity.
             Outbound Conflict responses indicate that requests
             received by this system could not be completed due objects providing configuration common
             to a
             conflict with the current state of a requested resource."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.10" all SIP enities."
       ::= { sipCommonStatsErrClient 20 sipCommonMIBGroups 1 }

   sipCommonStatsGroup OBJECT-GROUP
       OBJECTS {
               sipSummaryInRequests,
               sipSummaryOutRequests,
               sipSummaryInResponses,
               sipSummaryOutResponses,
               sipSummaryTotalTransactions,
               sipStatsInviteIns,
               sipStatsInviteOuts,
               sipStatsAckIns,
               sipStatsAckOuts,
               sipStatsByeIns,
               sipStatsByeOuts,
               sipStatsCancelIns,
               sipStatsCancelOuts,
               sipStatsOptionsIns,
               sipStatsOptionsOuts,
               sipStatsRegisterIns,
               sipStatsRegisterOuts,
               sipStatsExtMethodName,
               sipStatsExtMethodIns,
               sipStatsExtMethodOuts,
               sipStatsExtMethodStatus,
               sipStatsInfoClassIns,
               sipStatsInfoClassOuts,
               sipStatsSuccessClassIns,
               sipStatsSuccessClassOuts,
               sipStatsRedirClassIns,
               sipStatsRedirClassOuts,
               sipStatsReqFailClassIns,
               sipStatsReqFailClassOuts,
               sipStatsServerFailClassIns,
               sipStatsServerFailClassOuts,
               sipStatsGlobalFailClassIns,
               sipStatsGlobalFailClassOuts,
               sipCommonStatusCodeIns,
               sipCommonStatusCodeOuts,
               sipCommonStatusCodeSendNotif,
               sipCommonStatusCodeStatus,
               sipCurrentTransactions,

Lingle/Maeng/Walker                                                 38
               sipTransTo,
               sipTransFrom,
               sipTransCallId,
               sipTransCSeq,
               sipTransState,
               sipTransNumOutstandingBranches,
               sipTransExpiry,
               sipTransCallingPartyContentType,
               sipTransCalledPartyContentType,
               sipNumUnsupportedUris
       }

   sipStatsClientGoneIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
            "This object reflects the total number
            "A collection of Gone (410)
             responses received by the objects providing statistics common
             toall SIP entity.
             Inbound Gone responses indicate that resources requested
             by this system are no longer available at the recipient
             server and no forwarding address is known."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.11" entities."
       ::= { sipCommonStatsErrClient 21 sipCommonMIBGroups 2 }

   sipCommonNotifGroup NOTIFICATION-GROUP
       NOTIFICATIONS {
               sipStatusCodeNotif
       }

   sipStatsClientGoneOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
            "This object reflects the total number
            "A collection of Gone (410)
             responses sent by the notifications common to all SIP entity.
             Outbound Gone responses indicate that the requested
             resources are no longer available at this system and
             no forwarding address is known."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.11" entities."
       ::= { sipCommonStatsErrClient 22 sipCommonMIBGroups 3 }

   sipStatsClientLengthRequiredIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Length Required
             (411) responses received by the

   END

5.4. SIP entity.
             Inbound Length Required responses indicate that requests
             issued by this system are being refused by servers because
             of no defined Content-Length header field."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.12" User Agent

   SIP-UA-MIB DEFINITIONS ::= { sipCommonStatsErrClient 23 }

   sipStatsClientLengthRequiredOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Length Required
             (411) responses sent by the BEGIN

   IMPORTS
        MODULE-IDENTITY,
        OBJECT-TYPE,
        Counter32,
        Integer32
             FROM SNMPv2-SMI

        MODULE-COMPLIANCE,
        OBJECT-GROUP,
        NOTIFICATION-GROUP
             FROM SNMPv2-CONF

        sipMIB
             FROM SIP-MIB-SMI

        applIndex
             FROM NETWORK-SERVICES-MIB;

   sipUAMIB MODULE-IDENTITY
        LAST-UPDATED   "200007080000Z"

Lingle/Maeng/Walker                                                 39
        ORGANIZATION   "IETF SIP entity.
             Outbound Length Required responses indicate that requests
             received by this system are being refused because of no
             defined Content-Length header field."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.12"
       ::= { sipCommonStatsErrClient 24 }

   sipStatsClientReqEntTooLargeIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Request Entity
             Too Large 413) responses received by the Working Group, SIP entity.
             Inbound Request Entity Too Large responses indicate that
             requests issued by this system are being refused because
             the request is larger than the server is willing or able
             to process."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.13"
       ::= { sipCommonStatsErrClient 25 }

   sipStatsClientReqEntTooLargeOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current MIB Team"
        CONTACT-INFO
                "SIP MIB Team email: sip-mib@egroups.com

                 Co-editor  Kevin Lingle
                            Cisco Systems, Inc.
                 postal:    7025 Kit Creek Road
                            P.O. Box 14987
                            Research Triangle Park, NC 27709
                            USA
                 email:     klingle@cisco.com
                 phone:     +1-919-392-2029

                 Co-editor  Joon Maeng
                            VTEL Corporation
                 postal:    108 Wild Basin Rd.
                            Austin, TX 78746
                            USA
                 email:     joon_maeng@vtel.com
                 phone:     +1-512-437-4567

                 Co-editor  Dave Walker
                            SS8 Networks, Inc.
                 postal:    80 Hines Road
                            Kanata, ON  K2K 2T8
                            Canada
                 email:     drwalker@ss8networks.com
                 phone:     +1 613 592 2100"
        DESCRIPTION
            "This object reflects the total number
                "Initial version of Request Entity
             Too Large (413) responses sent by the Session Initiation Protocol (SIP)
                 User Agent (UA) MIB module.

                 SIP entity.
             Outbound Request Entity Too Large responses indicate that
             requests received by this system are larger than this
             system is willing or able to process."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.13"
       ::= { sipCommonStatsErrClient 26 }

   sipStatsClientReqURITooLargeIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Request-URI Too
             Large (414) responses received by the SIP entity.
             Inbound Request-URI Too Large responses indicate that
             requests issued by this system are being refused because
             the Request-URI is longer than the server is willing or
             able to interpret."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.14"
       ::= { sipCommonStatsErrClient 27 }

   sipStatsClientReqURITooLargeOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Request-URI Too
             Large (414) responses sent by the SIP entity.
             Outbound Request-URI Too Large responses indicate that
             Request-URIs received by this system are longer than this
             system is willing or able to interpret."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.14"
       ::= { sipCommonStatsErrClient 28 }

   sipStatsClientNoSupMediaTypeIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Unsupported Media
             Type (415) responses received by the SIP entity.
             Inbound Unsupported Media Type responses indicate that
             requests issued by this system are being refused because
             the message body of the request is in a format not
             supported by the requested resource for the requested
             method."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.15"
       ::= { sipCommonStatsErrClient 29 }
   sipStatsClientNoSupMediaTypeOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Unsupported Media
             Type (415) responses sent by the SIP entity.
             Outbound Unsupported Media Type responses indicate that
             the body of requests received by this system are in a
             format not supported by the requested resource for the
             requested method."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.15"
       ::= { sipCommonStatsErrClient 30 }

   sipStatsClientBadExtensionIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Bad Extension
             (420) responses received by the SIP entity.
             Inbound Bad Extension responses indicate that the
             recipient did not understand the protocol extension
             specified in a Require header field."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.16"
       ::= { sipCommonStatsErrClient 31 }

   sipStatsClientBadExtensionOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Bad Extension
             (420) responses sent by the SIP entity.
             Outbound Bad Extension responses indicate that this system
             did not understand the protocol extension specified in a
             Require header field of requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.16"
       ::= { sipCommonStatsErrClient 32 }

   sipStatsClientTempNotAvailIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Temporarily Not
             Available 480) responses received by the SIP entity.
             Inbound Temporarily Not Available responses indicate that
             the called party is currently unavailable."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.17"
       ::= { sipCommonStatsErrClient 33 }

   sipStatsClientTempNotAvailOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Temporarily Not
             Available (480) responses sent by the SIP entity.
             Outbound Temporarily Not Available responses indicate that
             the called party's end system was contacted successfully
             but the called party is currently unavailable."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.17"
       ::= { sipCommonStatsErrClient 34 }

   sipStatsClientCallLegNoExistIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Call
             Leg/Transaction Does Not Exist (481) responses received by
             the SIP entity.
             Inbound Call Leg/Transaction Does Not Exist responses
             indicate that either BYE or CANCEL requests issued by this
             system were received by a server and no matching call leg
             or transaction existed."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.18"
       ::= { sipCommonStatsErrClient 35 }

   sipStatsClientCallLegNoExistOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Call
             Leg/Transaction Does Not Exist (481) responses sent by the
             SIP entity.
             Outbound Call Leg/Transaction Does Not Exist responses
             indicate that BYE or CANCEL requests have been received by
             this system and no call leg or transaction matching that
             request exists."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.18"
       ::= { sipCommonStatsErrClient 36 }

   sipStatsClientLoopDetectedIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Loop Detected
             (482) responses received by the SIP entity.
             Inbound Loop Detected responses indicate that requests
             issued by this system were received at servers and the
             server found itself in the Via path more than once."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.19"
       ::= { sipCommonStatsErrClient 37 }

   sipStatsClientLoopDetectedOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Loop Detected
             (482) responses sent by the SIP entity.
             Outbound Loop Detected responses indicate that requests
             received by this system contain a Via path with this
             system appearing more than once."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.19"
       ::= { sipCommonStatsErrClient 38 }

   sipStatsClientTooManyHopsIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Too Many Hops
             (483) responses received by the SIP entity.
             Inbound Too Many Hops responses indicate that requests
             issued by this system contain more Via entries (hops) than
             allowed by the Max-Forwards header field of the requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.20"
       ::= { sipCommonStatsErrClient 39 }

   sipStatsClientTooManyHopsOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Too Many Hops
             (483) responses sent by the SIP entity.
             Outbound Too Many Hops responses indicate that requests
             received by this system contain more Via entries (hops)
             than are allowed by the Max-Forwards header field of the
             requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.20"
       ::= { sipCommonStatsErrClient 40 }

   sipStatsClientAddrIncompleteIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Address
             Incomplete (484) responses received by the SIP entity.
             Inbound Address Incomplete responses indicate that
             requests issued by this system had To addresses or
             Request-URIs that were incomplete."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.21"
       ::= { sipCommonStatsErrClient 41 }

   sipStatsClientAddrIncompleteOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Address
             Incomplete (484) responses sent by the SIP entity.

             Outbound Address Incomplete responses indicate that
             requests received by this system had To addresses or
             Request-URIs that were incomplete."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.21"
       ::= { sipCommonStatsErrClient 42 }

   sipStatsClientAmbiguousIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Ambiguous (485)
             responses received by the SIP entity.
             Inbound Ambiguous responses indicate that requests issued
             by this system provided ambiguous address information."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.22"
       ::= { sipCommonStatsErrClient 43 }

   sipStatsClientAmbiguousOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Ambiguous (485)
             responses sent by the SIP entity.
             Outbound Ambiguous responses indicate that requests
             received by this system contained ambiguous address
             information."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.22"
       ::= { sipCommonStatsErrClient 44 }

   sipStatsClientBusyHereIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Busy Here (486)
             responses received by the SIP entity.
             Inbound Busy Here responses indicate that the
             called party is currently not willing or not able to
             take additional calls."
       REFERENCE
            "RFC 2543, Section 5.1.1 & 7.4.23"
       ::= { sipCommonStatsErrClient 45 }

   sipStatsClientBusyHereOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Busy Here (486)
             responses sent by the SIP entity.
             Outbound Busy Here responses indicate that the
             called party's end system was contacted successfully but
             the called party is currently not willing or able to take
             additional calls."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.4.23"
       ::= { sipCommonStatsErrClient 46 }

   --
   -- SIP Server Error Responses Statistics
   --
   -- The following Inbound counters reflect failure responses received
   -- by a SIP entity providing a client function.
   --
   -- The following Outbound counters reflect failure responses sent by
   -- a SIP entity providing a server function.
   --
   -- Servers generally send these responses to Clients.  They are not
   -- definite failures and must not terminate a search if other
   -- possible locations remain untried.
   --
   sipStatsServerIntErrorIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Internal Server
             Error (500) responses received by the SIP entity.
             Inbound Internal Server Error responses indicate that
             servers to which this system is sending requests have
             encountered unexpected conditions that prevent them from
             fulfilling the requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.1"
       ::= { sipCommonStatsErrServer 1 }

   sipStatsServerIntErrorOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Internal Server
             Error (500) responses sent by the SIP entity.
             Outbound Internal Server Error responses indicate that
             this system has encountered unexpected conditions that
             prevent it from fulfilling received requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.1"
       ::= { sipCommonStatsErrServer 2 }

   sipStatsServerNotImplementedIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Not Implemented
             (501) responses received by the SIP entity.
             Inbound Not Implemented responses indicate that servers to
             which this system is sending requests do not support the
             functionality required to fulfill the requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.2"
       ::= { sipCommonStatsErrServer 3 }

   sipStatsServerNotImplementedOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Not Implemented
             (501) responses sent by the SIP entity.
             Outbound Not Implemented responses indicate that this
             system does not support the functionality required to
             fulfill the requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.2"
       ::= { sipCommonStatsErrServer 4 }

   sipStatsServerBadGatewayIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Bad Gateway (502)
             responses received by the SIP entity."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.3"
       ::= { sipCommonStatsErrServer 5 }

   sipStatsServerBadGatewayOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Bad Gateway (502)
             responses sent by the SIP entity."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.3"
       ::= { sipCommonStatsErrServer 6 }

   sipStatsServerServiceUnavailIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Service
             Unavailable (503) responses received by the SIP entity.
             Inbound Service Unavailable responses indicate that the
             server servicing this system's request is temporarily
             unavailable to handle the request."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.4"
       ::= { sipCommonStatsErrServer 7 }

   sipStatsServerServiceUnavailOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Service
             Unavailable (503) responses sent by the SIP entity.
             Outbound Service Unavailable responses indicate that this
             system is temporarily unable to handle received requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.4"
       ::= { sipCommonStatsErrServer 8 }
   sipStatsServerGatewayTimeoutIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Gateway Time-out
             (504) responses received by the SIP entity.
             Inbound Gateway Time-out responses indicate that the
             server attempting to complete this system's request did
             not receive a timely response from yet another system it
             was accessing to complete the request."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.5"
       ::= { sipCommonStatsErrServer 9 }

   sipStatsServerGatewayTimeoutOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Gateway Time-out
             (504) responses sent by the SIP entity.
             Outbound Gateway Time-out responses indicate that this
             system did not receive a timely response from the system
             it had accessed to assist in completing a received
             request."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.5"
       ::= { sipCommonStatsErrServer 10 }

   sipStatsServerBadSipVersionIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of SIP Version Not
             Supported (505) responses received by the SIP entity.
             Inbound SIP Version Not Supported responses indicate that
             the server does not support, or refuses to support, the
             SIP protocol version that was used in the request
             message."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.6"
       ::= { sipCommonStatsErrServer 11 }

   sipStatsServerBadSipVersionOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of SIP Version Not
             Supported (505) responses sent by the SIP entity.
             Outbound SIP Version Not Supported responses indicate that
             this system does not support, or refuses to support, the
             SIP protocol version used in received requests."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.5.6"
       ::= { sipCommonStatsErrServer 12 }

   --
   -- SIP Global Failure Response Statistics
   --
   -- The following Inbound counters reflect failure responses received
   _- by a SIP entity providing a client function.
   --
   -- The following Outbound counters reflect failure responses sent by
   -- a SIP entity providing a server function.
   --
   -- Servers generally send these responses to Clients.  The responses
   -- generally indicate that a server has definitive information about
   -- a particular called party, not just the particular instance
   -- indicated in the Request-URI.  All further searches for this user
   -- are doomed to failure and pending searches should be terminated.
   --
   sipStatsGlobalBusyEverywhereIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Busy
             Everywhere (600) responses received by the SIP entity.
             Inbound Busy Everywhere responses indicate that the
             called party's end system was contacted successfully
             but the called party is busy and does not want to take
             the call at this time."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.6.1"
       ::= { sipCommonStatsGlobalFail 1 }

   sipStatsGlobalBusyEverywhereOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Busy
             Everywhere (600) responses sent by the SIP entity.
             Outbound Busy Everywhere responses indicate that
             this system has successfully contacted a called party's
             end system and the called party does not want to take
             the call at this time."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.6.1"
       ::= { sipCommonStatsGlobalFail 2 }

   sipStatsGlobalDeclineIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Decline
             (603) responses received by the SIP entity.
             Decline responses indicate that the called party's end
             system was contacted successfully but the called party
             explicitly does not want to, or cannot, participate."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.6.2"
       ::= { sipCommonStatsGlobalFail 3 }

   sipStatsGlobalDeclineOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Decline
             (603) responses sent by the SIP entity.
             Outbound Decline responses indicate that this system
             has successfully contacted a called party's end system
             and the called party explicitly does not want to, or
             cannot, participate."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.6.2"
       ::= { sipCommonStatsGlobalFail 4 }

   sipStatsGlobalNotAnywhereIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Does Not
             Exist Anywhere (604) responses received by the SIP entity.
             Inbound Does Not Exist Anywhere responses indicate that
             the server handling this system's request has
             authoritative information that the called party indicated
             in the To request field does not exist anywhere."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.6.3"
       ::= { sipCommonStatsGlobalFail 5 }

   sipStatsGlobalNotAnywhereOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Does Not
             Exist Anywhere (604) responses sent by the SIP entity.
             Outbound Does Not Exist Anywhere responses indicate that
             this system has authoritative information that the called
             party in the To field of received requests does not exist
             anywhere."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.6.3"
       ::= { sipCommonStatsGlobalFail 6 }

   sipStatsGlobalNotAcceptableIns OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Not Acceptable
             (606) responses received by the SIP entity.
             Inbound Not Acceptable responses indicate that the called
             party's end system was contacted successfully but some
             aspect of the session description is not acceptable."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.6.4"
       ::= { sipCommonStatsGlobalFail 7 }

   sipStatsGlobalNotAcceptableOuts OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of Not Acceptable
             (606) responses sent by the SIP entity.
             Outbound Not Acceptable responses indicate that the called
             party wishes to communicate, but cannot adequately support
             the session described in the request."
       REFERENCE
            "RFC 2543, Sections 5.1.1 & 7.6.4"
       ::= { sipCommonStatsGlobalFail 8 }

   --
   -- Transaction Statistics
   --
   sipCurrentTransactions OBJECT-TYPE
       SYNTAX     Gauge32 (0..4294967295)
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the number of transactions awaiting
             definitive (non-1xx) response.  In the case of a forked
             request, all branches count as a single transaction.  The
             value of this object will reflect the number of rows in
             sipTransactionTable."
   ::= { sipCommonStatsTrans 1 }

   sipTransactionTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipTransactionEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains information on all of the transactions
             currently being processed (the count of such transactions
             is maintained in the sipCurrentTransactions object)."
       ::= { sipCommonStatsTrans 2 }

   sipTransactionEntry OBJECT-TYPE
       SYNTAX     SipTransactionEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "Information on a particular current transaction."
       INDEX { sipTransIndex }
       ::= { sipTransactionTable 1 }

   SipTransactionEntry ::=
       SEQUENCE {
                sipTransIndex                         Unsigned32,
                sipTransTo                            SnmpAdminString,
                sipTransFrom                          SnmpAdminString,
                sipTransCallId                        SnmpAdminString,
                sipTransCSeq                          Unsigned32,
                sipTransState                         INTEGER,
                sipTransOutstandingBranches           Integer32,
                sipTransExpiry                        DateAndTime,
                sipTransCallingPartyContentType       SnmpAdminString,
                sipTransCalledPartyContentType        SnmpAdminString
       }

   sipTransIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (0..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This object uniquely identifies a conceptual row in the
             table."
       ::= { sipTransactionEntry 1 }

   sipTransTo OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the value of the To header in request
             message."
       ::= { sipTransactionEntry 2 }

   sipTransFrom OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the value of the From header in the
             request message."
       ::= { sipTransactionEntry 3 }

   sipTransCallId OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the value of the CallId value in the
             request message."
       ::= { sipTransactionEntry 4 }

   sipTransCSeq OBJECT-TYPE
       SYNTAX     Unsigned32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the CSeq value for the current
             transaction."
       ::= { sipTransactionEntry 5 }

   sipTransState OBJECT-TYPE
       SYNTAX     INTEGER {
                          null(1),
                          initial(2),
                          calling(3),
                          ringing(4),
                          completed(5),
                          callProceeding(6),
                          failure(7),
                          success(8),
                          confirmed(9)
                  }
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the current state of the SIP
             transaction.

             null(1)           : The SIP entity is not active.

             initial(2)        : Prior to sending or receiving any
                                 request.
             calling(3)        : After sending the request and prior to
                                 receiving any response.
             ringing(4)        : After receiving one or more
                                 informational (1xx) responses.
             completed(5)      : After ACK has been sent following
                                 reception of definitive response.
             callProceeding(6) : Entered on reception of an INVITE.
             failure(7)        : Entered when call fails(send status
                                 code>=300).
             success(8)        : Entered when user answers(send status
                                 code=200).
             confirmed(9)      : Entered on reception of is an ACK in
                                 failure or success states."
       REFERENCE
           "RFC 2543, Figures 12 application-layer signalling protocol for
                 creating, modifying and 13"
   ::= { sipTransactionEntry 6 }

   sipTransOutstandingBranches OBJECT-TYPE
       SYNTAX     Integer32 (0..255)
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains a count of the number of branches
             awaiting a final response.  Only a forking proxy will have
             a value greater than one."
       ::= { sipTransactionEntry 7 }

   sipTransExpiry OBJECT-TYPE
       SYNTAX     DateAndTime
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains an indication of when the transaction
             will be considered to have timed out.  This value is based
             on the value in the Expires header, or the value of the
             sipRequestDfltExpires object if no Expires value was
             specified in the original request."
       ::= { sipTransactionEntry 8 }

   sipTransCallingPartyContentType OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the content type of the transaction,
             including parameters, as indicated by the session
             initiator. All optional white space is removed from
             subfields in the media-type specification.  It may
             indicate mime multipart, in which case the multiple
             entries are separated by spaces."
       REFERENCE
            "RFC 2543, Section 6.16 terminating multimedia
                 sessions with one or more participants. These sessions
                 include Internet multimedia conferences and Internet
                 telephone calls.  SIP is defined in RFC 2068 section 3.7"
       ::= { sipTransactionEntry 9 }

   sipTransCalledPartyContentType OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object 2543 (March
                 1999).

                 A User Agent is an application that contains the content type of the transaction,
             including parameters, as indicated by the session
             respondant.  All optional white space both a
                 User Agent Client (UAC) and a User Agent Server (UAS).
                 A UAC is removed from
             subfields in the media-type specification.  It may
             indicate mime multipart, in which case an application that initiates a SIP request.
                 A UAS is an application that contacts the multiple
             entries are separated by spaces."
       REFERENCE
            "RFC 2543, Section 6.16 and RFC 2068, Section 3.7"
       ::= { sipTransactionEntry 10 }

   --
   -- Other Common Statistics
   --
   sipNumUnsupportedUris OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "Number of RequestURIs user when a
                 SIP request is received with unsupported scheme.
             A server normally responds to such requests with and that returns a 400 Bad
             Request status code." response on
                 behalf of the user.  The response accepts, rejects, or
                 redirects the request."
        ::= { sipCommonStats 10 sipMIB 3 }

   --
   -- sipUA group
   -- This group contains MIB objects related to SIP User Agents.
   --
   sipUACfg                    OBJECT IDENTIFIER ::= { sipUA sipUAMIB 1 }

Lingle/Maeng/Walker                                                 40
   sipUACfgTimer               OBJECT IDENTIFIER ::= { sipUACfg 1 }
   sipUACfgRetry               OBJECT IDENTIFIER ::= { sipUACfg 2 }
   sipUAStats                  OBJECT IDENTIFIER ::= { sipUA sipUAMIB 2 }
   sipUAStatsRetry             OBJECT IDENTIFIER ::= { sipUAStats sipUAStats 1 }

   --
   -- User Agent Configuration
   --

   --
   -- SIP Timer Configuration
   --
   sipUACfgTimerTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF SipUACfgTimerEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains timer configuration objects applicable
             to each SIP user agent in this system.  The instances of
             SIP entities are uniquely identified by applIndex."
       ::= { sipUACfgTimer 1 }

   sipUACfgTimerEntry OBJECT-TYPE
       SYNTAX     SipUACfgTimerEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A row of timer configuration."
       INDEX { applIndex }
       ::= { sipUACfgTimerTable 1 }

   --
   -- User Agent Configuration
   --

   --
   -- SIP Timer Configuration
   --

   SipUACfgTimerEntry ::=
       SEQUENCE {
                sipUACfgTimerTrying        Integer32,
                sipUACfgTimerProv          Integer32,
                sipUACfgTimerAck           Integer32,
                sipUACfgTimerDisconnect    Integer32,
                sipUACfgTimerReRegister    Integer32
       }

   sipUACfgTimerTrying OBJECT-TYPE
       SYNTAX      Integer32 (100..1000)
       UNITS       "milliseconds"
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object specifies the time a user agent will wait to
             receive a provisional response to an INVITE before
             resending the INVITE."
       ::= { sipUACfgTimer sipUACfgTimerEntry 1 }

   sipUACfgTimerExpires

   sipUACfgTimerProv OBJECT-TYPE
       SYNTAX      Integer32 (60000..300000)

Lingle/Maeng/Walker                                                 41
       UNITS       "milliseconds"
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object specifies the time a user agent will wait to
             receive a final response to an INVITE before canceling the
             transaction."
       ::= { sipUACfgTimer sipUACfgTimerEntry 2 }

   sipUACfgTimerAck OBJECT-TYPE
       SYNTAX      Integer32 (100..1000)
       UNITS       "milliseconds"
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object specifies the time a user agent will wait to
             receive an ACK confirmation indicating that a session is
             established."
       ::= { sipUACfgTimerEntry 3 }

   sipUACfgTimerDisconnect OBJECT-TYPE
       SYNTAX      Integer32 (100..1000)
       UNITS       "milliseconds"
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object specifies the time a user agent will wait to
             receive a BYE confirmation indicating that a session is
             disconnected."
       ::= { sipUACfgTimerEntry 4 }

   sipUACfgTimerReRegister OBJECT-TYPE
       SYNTAX      Integer32 (1..2147483647)
       UNITS       "seconds"
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object specifies how long the user agent wishes its
             registrations to be valid."
       ::= { sipUACfgTimerEntry 5 }

   --
   -- SIP Retry Configuration
   --
   sipUACfgRetryTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF SipUACfgRetryEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains retry configuration objects applicable
             to each SIP user agent in this system.  The instances of
             SIP entities are uniquely identified by applIndex."
       ::= { sipUACfgRetry 1 }

Lingle/Maeng/Walker                                                 42
   sipUACfgRetryEntry OBJECT-TYPE
       SYNTAX     SipUACfgRetryEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A row of retry configuration."
       INDEX { applIndex }
       ::= { sipUACfgRetryTable 1 }

   SipUACfgRetryEntry ::=
       SEQUENCE {
                sipUACfgRetryInvite       Integer32,
                sipUACfgRetryBye          Integer32,
                sipUACfgRetryCancel       Integer32,
                sipUACfgRetryRegister     Integer32,
                sipUACfgRetryResponse     Integer32
       }

   sipUACfgRetryInvite OBJECT-TYPE
       SYNTAX      Integer32 (1..10)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object will specify the number of times a user agent
             will retry sending an INVITE request."
       ::= { sipUACfgRetryEntry 1 }

   sipUACfgRetryBye OBJECT-TYPE
       SYNTAX      Integer32 (1..10)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object will specify the number of times a user agent
             will retry sending a BYE request."
       ::= { sipUACfgRetryEntry 2 }

   sipUACfgTimerConnect

   sipUACfgRetryCancel OBJECT-TYPE
       SYNTAX      Integer32 (100..1000)
       UNITS       "milliseconds" (1..10)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object specifies will specify the time number of times a user agent
             will wait to
             receive an ACK confirmation indicating that retry sending a session is
             established." CANCEL request."
       ::= { sipUACfgTimer sipUACfgRetryEntry 3 }

   sipUACfgTimerDisconnect

   sipUACfgRetryRegister OBJECT-TYPE
       SYNTAX      Integer32 (100..1000)
       UNITS       "milliseconds" (1..10)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object specifies will specify the time number of times a user agent
             will wait to
             receive a BYE confirmation indicating that retry sending a session is
             disconnected." REGISTER request."
       ::= { sipUACfgTimer sipUACfgRetryEntry 4 }

   --
   -- SIP Retry Configuration
   --
   sipUACfgRetryInvite

Lingle/Maeng/Walker                                                 43
   sipUACfgRetryResponse OBJECT-TYPE
       SYNTAX      Integer32 (1..10)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
            "This object will specify the number of times a user agent
             will retry sending a Response and expecting an INVITE request." ACK."
       ::= { sipUACfgRetry sipUACfgRetryEntry 5 }

   --
   -- User Agent Statistics
   --

   --
   -- SIP Retry Statistics
   --
   -- The counter objects in this group correspond directly to the
   -- retry timers supported in sipCfgRetry group.  applIndex can
   -- be used to correlate the two groups.
   --
   --
   sipUAStatsRetryTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipUAStatsRetryEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains retry statistics objects applicable
             to each SIP user agent in this system.  The instances of
             SIP entities are uniquely identified by applIndex."
       ::= { sipUAStatsRetry 1 }

   sipUACfgRetryBye

   sipUAStatsRetryEntry OBJECT-TYPE
       SYNTAX      Integer32 (1..10)     SipUAStatsRetryEntry
       MAX-ACCESS  read-write not-accessible
       STATUS     current
       DESCRIPTION
            "A row of retry statistics."
       INDEX { applIndex }
       ::= { sipUAStatsRetryTable 1 }

   SipUAStatsRetryEntry ::=
       SEQUENCE {
                sipStatsRetryInvites        Counter32,
                sipStatsRetryByes           Counter32,
                sipStatsRetryCancels        Counter32,
                sipStatsRetryRegisters      Counter32,
                sipStatsRetryResponses      Counter32
       }

   sipStatsRetryInvites OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only

Lingle/Maeng/Walker                                                 44
       STATUS      current
       DESCRIPTION
            "This object will specify reflects the total number of times a INVITE retries
             that have been sent by the user agent
             will retry sending a agent.   If the number of
             'first attempt' INVITES is of interest, subtract the value
             of this object from sipStatsTrafficInviteOut."
       ::= { sipUAStatsRetryEntry 1 }

   sipStatsRetryByes OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of BYE request." retries that
             have been sent by the user agent."
       ::= { sipUACfgRetry sipUAStatsRetryEntry 2 }

   sipUACfgRetryCancel

   sipStatsRetryCancels OBJECT-TYPE
       SYNTAX      Integer32 (1..10)      Counter32
       MAX-ACCESS  read-write  read-only
       STATUS      current
       DESCRIPTION
            "This object will specify reflects the total number of times a user agent
             will retry sending a CANCEL request." retries
             that have been sent by the user agent."
       ::= { sipUACfgRetry sipUAStatsRetryEntry 3 }

   sipUACfgRetryRegister

   sipStatsRetryRegisters OBJECT-TYPE
       SYNTAX      Integer32 (1..10)      Counter32
       MAX-ACCESS  read-write  read-only
       STATUS      current
       DESCRIPTION
            "This object will specify reflects the total number of times a user agent
             will retry sending a REGISTER request." retries
             that have been sent by the user agent."
       ::= { sipUACfgRetry sipUAStatsRetryEntry 4 }

   sipUACfgRetryResponse

   sipStatsRetryResponses OBJECT-TYPE
       SYNTAX      Integer32 (1..10)      Counter32
       MAX-ACCESS  read-write  read-only
       STATUS      current
       DESCRIPTION
            "This object will specify reflects the total number of times a user agent
             will retry sending a Response and (while
             expecting an ACK." ACK) retries that have been sent by the user
             agent."
       ::= { sipUACfgRetry sipUAStatsRetryEntry 5 }

   --
   -- User Agent Statistics Notifications
   --
   sipUAMIBNotif            OBJECT IDENTIFIER ::= { sipUAMIB 3 }

   -- none at this time

Lingle/Maeng/Walker                                                 45
   -- SIP Retry Statistics
   -- Conformance
   -- The counter objects in this group correspond directly to the
   sipUAMIBConformance
     OBJECT IDENTIFIER ::= { sipUAMIB 4 }
   sipUAMIBCompliances
     OBJECT IDENTIFIER ::= { sipUAMIBConformance 1 }
   sipUAMIBGroups
     OBJECT IDENTIFIER ::= { sipUAMIBConformance 2 }

   -- retry timers supported in sipCfgRetry group.
   --
   sipStatsRetryInvites OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only Compliance Statements
   --
   sipUACompliance MODULE-COMPLIANCE
       STATUS     current
       DESCRIPTION
            "This object reflects the total number of INVITE retries
             that have been sent by the user agent.   If the number of
             'first attempt' INVITES is
            "The compliance statement for SIP entities."

       MODULE -- this module
            MANDATORY-GROUPS { sipUAConfigGroup,
                               sipUAStatsGroup }
   --                            sipUANotifGroup }
       ::= { sipUAMIBCompliances 1 }

   --
   -- Units of interest, subtract the value Conformance
   --

   sipUAConfigGroup OBJECT-GROUP
       OBJECTS {
               sipUACfgTimerTrying,
               sipUACfgTimerProv,
               sipUACfgTimerAck,
               sipUACfgTimerDisconnect,
               sipUACfgTimerReRegister,
               sipUACfgRetryInvite,
               sipUACfgRetryBye,
               sipUACfgRetryCancel,
               sipUACfgRetryRegister,
               sipUACfgRetryResponse
       }
       STATUS  current
       DESCRIPTION
            "A collection of this object from sipStatsTrafficInviteOut." objects providing configuration for
             SIP User Agents."
       ::= { sipUAStatsRetry sipUAMIBGroups 1 }

   sipStatsRetryByes OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only

   sipUAStatsGroup OBJECT-GROUP
       OBJECTS {
               sipStatsRetryInvites,
               sipStatsRetryByes,
               sipStatsRetryCancels,

Lingle/Maeng/Walker                                                 46
               sipStatsRetryRegisters,
               sipStatsRetryResponses
       }
       STATUS  current
       DESCRIPTION
            "This object reflects the total number
            "A collection of BYE retries that
             have been sent by the user agent." objects providing statistics for
             SIP User Agents."
       ::= { sipUAStatsRetry sipUAMIBGroups 2 }

   sipStatsRetryCancels OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "This object reflects the total number of CANCEL retries
             that have been sent by the user agent."
       ::=

   --sipUANotifGroup NOTIFICATION-GROUP
   --    OBJECTS { sipUAStatsRetry 3
   -- none at this time
   --    }

   sipStatsRetryRegisters OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
   --    STATUS  current
   --    DESCRIPTION
            "This object reflects the total number
   --         "A collection of REGISTER retries
             that have been sent by the user agent." notifications defined for SIP User
   --          Agents."
   --    ::= { sipUAStatsRetry 4 sipMIBGroups 3 }

   sipStatsRetryResponses OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current

   END

5.5. SIP Redirect & Proxy Server

   SIP-SERVER-MIB DEFINITIONS ::= BEGIN

   IMPORTS
        MODULE-IDENTITY,
        OBJECT-TYPE,
        Counter32,
        Integer32,
        Unsigned32
             FROM SNMPv2-SMI

        RowStatus,
        TruthValue
             FROM SNMPv2-TC

        MODULE-COMPLIANCE,
        OBJECT-GROUP
             FROM SNMPv2-CONF

        SnmpAdminString
             FROM SNMP-FRAMEWORK-MIB

        SipServerActions
             FROM SIP-TC

        sipMIB
             FROM SIP-MIB-SMI

        applIndex
             FROM NETWORK-SERVICES-MIB;

Lingle/Maeng/Walker                                                 47
   sipServerMIB MODULE-IDENTITY
        LAST-UPDATED   "200007080000Z"
        ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
        CONTACT-INFO
                "SIP MIB Team email: sip-mib@egroups.com

                 Co-editor  Kevin Lingle
                            Cisco Systems, Inc.
                 postal:    7025 Kit Creek Road
                            P.O. Box 14987
                            Research Triangle Park, NC 27709
                            USA
                 email:     klingle@cisco.com
                 phone:     +1-919-392-2029

                 Co-editor  Joon Maeng
                            VTEL Corporation
                 postal:    108 Wild Basin Rd.
                            Austin, TX 78746
                            USA
                 email:     joon_maeng@vtel.com
                 phone:     +1-512-437-4567

                 Co-editor  Dave Walker
                            SS8 Networks, Inc.
                 postal:    80 Hines Road
                            Kanata, ON  K2K 2T8
                            Canada
                 email:     drwalker@ss8networks.com
                 phone:     +1 613 592 2100"
        DESCRIPTION
            "This object reflects
                "Initial version of Session Initiation Protocol (SIP)
                 Server MIB module.

                 SIP is an application-layer signalling 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 2543 (March
                 1999).

                 This MIB is defined for the total number management of Response (while
             expecting an ACK) retries SIP Proxy
                 and Redirect 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 have been sent by the user
             agent." client. Unlike
                 a Proxy server it does not initiate requests.  Unlike
                 a User Agent Server it does not accept calls."

Lingle/Maeng/Walker                                                 48
        ::= { sipUAStatsRetry 5 sipMIB 4 }

   --
   -- sipServer group
   -- This group contains MIB objects common to Proxy and Redirect
   -- Servers.
   --
   sipServerCfg                OBJECT IDENTIFIER ::= { sipServer sipServerMIB 1 }
   sipServerStats              OBJECT IDENTIFIER ::= { sipServer sipServerMIB 2 }

   --
   -- Common Server Configuration Objects
   --
   sipServerCfgTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipServerCfgEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains configuration objects applicable
             to SIP redirect and proxy servers.  Each row represents
             those objects for a particular SIP server present in
             this system. The instances of SIP servers are uniquely
             identified by applIndex."
       ::= { sipServerCfg 1 }

   sipServerCfgEntry OBJECT-TYPE
       SYNTAX     SipServerCfgEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A row of common configuration."
       INDEX { applIndex }
       ::= { sipServerCfgTable 1 }

   SipServerCfgEntry ::=
       SEQUENCE {
                sipServerHost                   SnmpAdminString,
                sipInformationAlwaysSendTrying  TruthValue,
                sipInformationTryingInterval    Integer32,
                sipPgpVersion                   SnmpAdminString,
                sipServerDfltAction             SipServerActions,
                sipServerRespectUAAction        TruthValue
       }

   sipServerHost OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This is the host portion of a SIP URL that is assigned
             to the SIP server.  It may contain a fully qualified
             domain name, or an IP address (v4 only for now)."
       REFERENCE

Lingle/Maeng/Walker                                                 49
             "RFC 2543, Section 2"
       ::= { sipServerCfg sipServerCfgEntry 1 }

   --
   -- Support for 1xx Status Codes
   --
   sipInformationTryingInitial
   sipInformationAlwaysSendTrying OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "If this object is true, the server sends 100 Trying when a
             request is processed."
       ::= { sipServerCfg sipServerCfgEntry 2 }

   sipInformationTryingInterval OBJECT-TYPE
       SYNTAX     Integer32 (0..60000)
       UNITS      "milliseconds"
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "Server sends a 100 Trying at intervals of this duration
             as counted from when the request was processed.  If the
             value is zero, no such retransmission is performed."
       ::= { sipServerCfg sipServerCfgEntry 3 }

   --
   -- Security
   --
   sipPgpVersion OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object indicates the version of PGP (Pretty Good
             Privacy) supported by this server.  Common values are
             2.6.2 and 5.0."
       ::= { sipServerCfg sipServerCfgEntry 4 }

   --
   -- Additional Server Configuration
   --
   sipServerDfltAction OBJECT-TYPE
       SYNTAX     SipServerActions
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether the default action of the
             server is to be a proxy server or a redirect server.  A
             User Agent may indicate a preference upon registration of
             Contact information. The value of this object is used in
             the absence of such an indication."
       REFERENCE
             "RFC 2543,  Section 6.13"

Lingle/Maeng/Walker                                                 50
       ::= { sipServerCfg sipServerCfgEntry 5 }

   sipServerRespectUAAction OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether the server should respect
             the wishes of a User Agent when the UA specifies a server
             action (proxy or redirect) for certain Contact
             information.  If the value of this object is false, then
             the value contained in the sipServerDfltAction is used."
       REFERENCE
             "RFC 2543, Section 6.13"
       ::= { sipServerCfg 6 }

   sipRequestUriHostMatching OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether or not the host in
             RequestURI must match server's host name. redirect) for certain Contact
             information.  If the value of this object is TRUE, false, then
             the server
             requires a match, and if the RequestURI doesn't match the
             server's host name, a 404 Not Found status code is
             returned by the server.
             If the value contained in the sipServerDfltAction is FALSE, then no match is required." used."
       REFERENCE
             "RFC 2543, Section 4.3" 6.13"
       ::= { sipServerCfg 7 sipServerCfgEntry 6 }

   --
   -- Common Server Statistics
   --

   -- none at this time

   -- sipProxy group
   -- This group contains MIB objects related to SIP Proxy Servers.
   --
   sipProxy                    OBJECT IDENTIFIER ::= { sipServerMIB 3 }
   sipProxyCfg                 OBJECT IDENTIFIER ::= { sipProxy 1 }
   sipProxyStats               OBJECT IDENTIFIER ::= { sipProxy 2 }

   --
   -- Proxy Server Configration Configuration
   --
   sipProxyCfgTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipProxyCfgEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains configuration objects applicable
             to SIP proxy servers.  Each row represents those objects
             for a particular SIP proxy server present in this system.
             The instances of SIP proxy servers are uniquely identified
             by applIndex."
       ::= { sipProxyCfg 1 }

   sipProxyCfgEntry OBJECT-TYPE
       SYNTAX     SipProxyCfgEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A row of common configuration."
       INDEX { applIndex }

Lingle/Maeng/Walker                                                 51
       ::= { sipProxyCfgTable 1 }

   SipProxyCfgEntry ::=
       SEQUENCE {
                sipRequestMaxExpires         Unsigned32,
                sipProxyStateful             TruthValue,
                sipProxySendsCancel          TruthValue,
                sipProxyForwardAll1xx        TruthValue,
                sipProxyRecursion            TruthValue,
                sipProxyProvideAlternatives  TruthValue,
                sipProxyRecordRoute          TruthValue,
                sipProxyStateTimeout         Integer32,
                sipProxyAuthMethod           INTEGER,
                sipProxyAuthPgpAlgorithm     INTEGER,
                sipProxyAuthRealm            SnmpAdminString,
                sipProxyNonceLifeTime        Integer32,
                sipPgpPrivateKey             OCTET
   STRING(SIZE(0..255)),
                sipHideRespect               TruthValue
       }

   sipRequestMaxExpires OBJECT-TYPE
       SYNTAX     Unsigned32 (0..4294967295)
       UNITS      "seconds"
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies the maximum duration that a SIP
             proxy server will accept from a client in the Expires
             header.

             If a longer duration is contained in the request, the
             server returns a 400 Bad Request response."
       ::= { sipProxyCfg sipProxyCfgEntry 1 }

   sipProxyStateful OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether or not the default for
             the the proxy server
             operates is to operate in stateful mode.

             When stateful, a proxy remembers the incoming request
             which generated outgoing requests, and the outgoing
             requests. A stateless proxy forgets all information
             once an outgoing request is generated.

             If the value of this object is TRUE, the proxy is defaults
             to stateful.  If FALSE, the proxy is defaults to stateless."
       REFERENCE
             "RFC 2543, Section 12.3"
       ::= { sipProxyCfg sipProxyCfgEntry 2 }

Lingle/Maeng/Walker                                                 52
   sipProxySendsCancel OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether or not a forking proxy sends
             CANCEL on outstanding branch requests after receiving a
             2xx or 6xx, or after the request times-out.

             If the value of this object is TRUE, the server sends a
             CANCELs on branches where no definitive response has been
             received.  If FALSE, the proxy does not send CANCELs."
       REFERENCE
             "RFC 2543, Section 12.4"
       ::= { sipProxyCfg sipProxyCfgEntry 3 }

   sipProxyForwardAll1xx OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether or not the proxy forwards
             all 1xx responses responses, except the 100 Trying response,
             upstream towards the source of the request.

             If the value of this object is TRUE, all the 1xx response responses are
             sent.  If the value is FALSE, duplicate 1xx responses are
             not sent upstream."
       ::= { sipProxyCfg sipProxyCfgEntry 4 }

   sipProxyRecursion OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether or not the Proxy performs
             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,
             the 3xx response is sent upstream towards the source of
             the request."
       ::= { sipProxyCfg sipProxyCfgEntry 5 }

   sipProxyProvideAlternatives OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "The object specifies whether or not the Server provides
             alternative Contacts in 3xx and 485 responses.

             If the value of this object is TRUE, the server inserts a

Lingle/Maeng/Walker                                                 53
             list of alternative URLs into a Contact header where the
             request Originator may possibly find the desired called
             party.  If the value is FALSE, the server doesn't add
             Contact information to 3xx and 485 responses.

             Note that the policies of a server may limit the
             particular alternatives that are returned when this object
             is TRUE."
       REFERENCE
             "RFC 2543, Section 6.13"
       DEFVAL { false }
       ::= { sipProxyCfg sipProxyCfgEntry 6 }

   sipProxyRecordRoute OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether or not the proxy adds itself
             to the Record-Route header. header as a default action.  This
             header is used to list the proxies that insist on being in
             the signalling 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 doesn't add
             itself to the Record-Route header."
       REFERENCE
             "RFC 2543, Section 6.29"
       ::= { sipProxyCfg sipProxyCfgEntry 7 }

   sipProxyUseCompact OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether or not the proxy should use
             the compact encoding form in the requests it sends.

             If the value of this object is TRUE, the proxy encodes all
             outgoing messages using the compact encoding form.  If the
             value is FALSE, the encoding form used on the
             corresponding incoming message is used, and if no incoming
             message existed, full encoding is used."
        REFERENCE
             "RFC 2543, Section 9"
        ::= { sipProxyCfg 8 }

   sipProxyRetransmissionBuffer

   sipProxyStateTimeout OBJECT-TYPE
       SYNTAX     Integer32 (0..255)
       UNITS      "seconds"
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies the duration after reception of the
             first definitive non-200 response that a stateful proxy
             retains state in order to handle possible retransmissions
             of the response."
       REFERENCE
             "RFC 2543, Section 12.3.6"
       ::= { sipProxyCfg 9 sipProxyCfgEntry 8 }

   --
   -- Security
   --
   sipProxyAuthMethod OBJECT-TYPE
       SYNTAX     INTEGER {
                          none(1),
                          basic(2),
                          digest(3),

Lingle/Maeng/Walker                                                 54
                          pgp(4)
                  }
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies the authentication method that is
             used to authenticate request originators.  If the value is
             none(1), no authentication is performed."
       ::= { sipProxyCfg 10 sipProxyCfgEntry 9 }

   sipProxyAuthPgpAlgorithm OBJECT-TYPE
       SYNTAX     INTEGER {
                          other(1),
                          md5(2),
                          sha1(3)

                  }
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies the PGP algorithm the proxy uses."
       ::= { sipProxyCfg 11 sipProxyCfgEntry 10 }

   sipProxyAuthRealm OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies the realm used in Proxy-Authenticate
             headers.  Note that this may need to be stored per user."
       ::= { sipProxyCfg 12 }

   sipProxyNonceLifeTime OBJECT-TYPE
       SYNTAX Integer32 (0..65535)
       UNITS "milliseconds"
       MAX-ACCESS read-write
       STATUS current
       DESCRIPTION
            "This object specifies the life-time of a given nonce.  A
             nonce is a server specified value whose contents are
             opaque to the entity being authenticated and which is used
             in calculating authentication data.  If this object has a
             value of zero, then
             nonces are not reused."
       ::= { sipProxyCfg 13 }

   --
   -- Proxy-Authenticate received by this server
   -- (i.e. this server is being authenticated by a peer)
   --
   sipPgpPrivateKey OBJECT-TYPE
       SYNTAX     OCTET STRING(SIZE(0..255))
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "The value of this object is the server's private PGP key,
             used for both PGP authentication of this server and for
             PGP-based
             encryption."
       ::= { sipProxyCfg 14 }

   sipRxProxyAuthTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipRxProxyAuthEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains authentication data for peers of the
             server."
       ::= { sipProxyCfg 15 }

   sipRxProxyAuthEntry OBJECT-TYPE
       SYNTAX     SipRxProxyAuthEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This object contains authentication data for a single
             peer."
       INDEX { sipRxProxyAuthIndex }
       ::= { sipRxProxyAuthTable 1 }

   SipRxProxyAuthEntry ::=
       SEQUENCE {
                sipRxProxyAuthIndex              Unsigned32,
                sipRxProxyAuthRealm              SnmpAdminString,
                sipRxProxyAuthPassword           OCTET STRING,
                sipRxProxyAuthStatus             RowStatus
       }

   sipRxProxyAuthIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This object uniquely identifies a conceptual row in the
             table."
       ::= { sipRxProxyAuthEntry 1 }

   sipRxProxyAuthRealm OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-create
       STATUS     current
       DESCRIPTION
            "This object contains the realm that is specified by
             another server when it is authenticating this server." to be stored per user."
       ::= { sipRxProxyAuthEntry 2 sipProxyCfgEntry 11 }

   sipRxProxyAuthPassword

   sipProxyNonceLifeTime OBJECT-TYPE
       SYNTAX     OCTET STRING(SIZE(1..4095)) Integer32 (0..65535)
       UNITS "milliseconds"
       MAX-ACCESS read-create read-write
       STATUS current
       DESCRIPTION
            "This object contains specifies the password that this server uses
             when it life-time of a given nonce.  A
             nonce is being authenticated by another a server using the
             realm specified by value whose contents are
             opaque to the sipRxProxyAuthRealm object entity being authenticated and which is used
             in calculating authentication data.  If this
             table row." object has a
             value of zero, then
             nonces are not reused."
       ::= { sipRxProxyAuthEntry 3 sipProxyCfgEntry 12 }

   sipRxProxyAuthStatus

   --
   -- Proxy-Authenticate received by this server
   -- (i.e. this server is being authenticated by a peer)
   --
   sipPgpPrivateKey OBJECT-TYPE
       SYNTAX     RowStatus     OCTET STRING(SIZE(0..255))
       MAX-ACCESS read-create read-write
       STATUS     current

Lingle/Maeng/Walker                                                 55
       DESCRIPTION
            "The row status value of the entry. This this object is required
             to create or delete rows remotely by a manager." the server's private PGP key,
             used for both PGP authentication of this server and for
             PGP-based
             encryption."
       ::= { sipRxProxyAuthEntry 4 sipProxyCfgEntry 13 }

   sipHideRespect OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
       STATUS     current
       DESCRIPTION
            "This object specifies whether the server encrypts Via
             headers as requested by received Hide headers."
       ::= { sipProxyCfg 16 sipProxyCfgEntry 14 }

   --
   -- Proxy Server Statistics
   --
   sipNumProxyRequireFailures

   sipRxProxyAuthTable OBJECT-TYPE
       SYNTAX     Counter32     SEQUENCE OF SipRxProxyAuthEntry
       MAX-ACCESS read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This 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."
       ::= { sipProxyStats 1 }

   --
   -- sipRedir group
   -- This group contains MIB objects related to SIP Redirect Servers.
   --
   sipRedirCfg                 OBJECT IDENTIFIER ::= { sipRedir 1 }
   sipRedirStats               OBJECT IDENTIFIER ::= { sipRedir 2 }

   -- none at this time

   --
   -- sipReg group
   -- This group table contains MIB objects related to SIP Registrars.
   --
   sipRegCfg                   OBJECT IDENTIFIER ::= { sipReg 1 }
   sipRegStats                 OBJECT IDENTIFIER authentication data for peers of each
             proxy server in this system.  The instances of proxy
             server are uniquely identified by the applIndex."
       ::= { sipReg sipProxyCfg 2 }

   --
   -- Registrar Configuration
   --
   sipRegAllowThirdParty

   sipRxProxyAuthEntry OBJECT-TYPE
       SYNTAX     TruthValue     SipRxProxyAuthEntry
       MAX-ACCESS read-write not-accessible
       STATUS     current
       DESCRIPTION
            "This object specifies whether or not the Registrar should
             allows third party registrations. In third-party
             registration, the entity issuing the request (in the From
             header) is different from the entity being registered (in
             the To header) to whom the
             provided Contact information applies.

             If the value of this object is TRUE, the Registrar allows
             third party registrations.  If the value is FALSE, third
             party registrations are rejected: contains authentication data for a 403 Forbidden status
             code is returned to the requestor."
       REFERENCE
            "RFC 2543, Section 4.2.6" single
             peer."
       INDEX { applIndex, sipRxProxyAuthIndex }
       ::= { sipRegCfg sipRxProxyAuthTable 1 }

   sipRegContactDfltExpiryDuration

   SipRxProxyAuthEntry ::=
       SEQUENCE {
                sipRxProxyAuthIndex              Unsigned32,
                sipRxProxyAuthRealm              SnmpAdminString,
                sipRxProxyAuthPassword           OCTET STRING,
                sipRxProxyAuthStatus             RowStatus
       }

   sipRxProxyAuthIndex OBJECT-TYPE
       SYNTAX     Unsigned32
       UNITS      "seconds" (1..4294967295)
       MAX-ACCESS read-write not-accessible
       STATUS     current
       DESCRIPTION
            "This object specifies the default expiration (time-to-
             live) of Contact information that is provided by User
             Agents when registering with this Registrar.  This value
             is only used when no expiration has been specified by the
             user in the REGISTER
             request.

             If the value is applied to uniquely identifies a registration and is different
             from the default (one hour), the server must return the
             value to the registered User Agent.

             The value contained in this object only applies if the
             value of the sipContactDfltExpiryDate object is NULL.  If
             the value of this object applies, and is zero, then no
             default expiry is applied to registered contact
             information."
       REFERENCE
             "RFC 2543, Section 4.2.6"
       DEFVAL { 3600 } conceptual row in the
             table."
       ::= { sipRegCfg 2 sipRxProxyAuthEntry 1 }

   sipRegContactDfltExpiryDate

Lingle/Maeng/Walker                                                 56
   sipRxProxyAuthRealm OBJECT-TYPE
       SYNTAX     DateAndTime     SnmpAdminString
       MAX-ACCESS read-write read-create
       STATUS     current
       DESCRIPTION
            "This object specifies contains the default expiration date (time-
             to-live) of Contact information realm that is provided specified by User
             Agents
             another server when registering with this Registrar.  This value it is only used when no expiration has been specified by the
             user in authenticating this server."
       ::= { sipRxProxyAuthEntry 2 }

   sipRxProxyAuthPassword OBJECT-TYPE
       SYNTAX     OCTET STRING(SIZE(1..4095))
       MAX-ACCESS read-create
       STATUS     current
       DESCRIPTION
            "This object contains the REGISTER request.

             If password that this value server uses
             when it is applied to a registration, the being authenticated by another server
             must return using the value to
             realm specified by the registered User Agent.

             The value contained sipRxProxyAuthRealm object in this object only applies if the
             value
             table row."
       ::= { sipRxProxyAuthEntry 3 }

   sipRxProxyAuthStatus OBJECT-TYPE
       SYNTAX     RowStatus
       MAX-ACCESS read-create
       STATUS     current
       DESCRIPTION
            "The row status of the sipContactDfltExpiryDuration object is zero.
             If the value of this entry. This object applies, and is NULL, then no
             default expiry is applied required
             to
             registered contact information."
       REFERENCE
            "RFC 2543, Section 4.2.6" create or delete rows remotely by a manager."
       ::= { sipRegCfg 3 sipRxProxyAuthEntry 4 }

   sipRegMaxContactExpiryDate

   --
   -- Proxy Server Statistics
   --
   sipProxyStatsTable OBJECT-TYPE
       SYNTAX     Unsigned32 (0..4294967295)
       UNITS      "seconds"     SEQUENCE OF SipProxyStatsEntry
       MAX-ACCESS read-write not-accessible
       STATUS     current
       DESCRIPTION
            "This object specifies table contains the maximum expiry that may be
             requested by a User Agent statistics objects applicable
             to all SIP Proxy Servers in this system.

             Each row represents those objects 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
             SIP Proxy Server.  The instances of SIP Proxy Server
             are uniquely identified by the User Agent is greater than the value applIndex."
       ::= { sipProxyStats 1 }

   sipProxyStatsEntry OBJECT-TYPE
       SYNTAX     SipProxyStatsEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A row of
             this object, then the contact information is given summary statistics."
       INDEX { applIndex }
       ::= { sipProxyStatsTable 1 }

Lingle/Maeng/Walker                                                 57
   SipProxyStatsEntry ::=
       SEQUENCE {
                sipNumProxyRequireFailures Counter32
       }

   sipNumProxyRequireFailures OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains the
             duration number of occurrences of
             unsupported options being specified by this object, and that duration
             is indicated to the User Agent in the response."
       DEFVAL received Proxy-
             Require headers.  Such occurrences result in a 420 Bad
             Extension status code being
             returned."
       ::= { 4294967295 sipProxyStatsEntry 1 }

   --
   -- sipRedir group
   -- This group contains MIB objects related to SIP Redirect Servers.
   --
   sipRedir               OBJECT IDENTIFIER ::= { sipRegCfg sipServerMIB 4 }

   sipRegRespHasContacts OBJECT-TYPE
       SYNTAX     TruthValue
       MAX-ACCESS read-write
   sipRedirCfg            OBJECT IDENTIFIER ::= { sipRedir 1 }
   sipRedirStats          OBJECT IDENTIFIER ::= { sipRedir 2 }

   -- none at this time

   --
   -- Notifications
   --
   sipServerMIBNotif      OBJECT IDENTIFIER ::= { sipServerMIB 5 }
   sipProxyNotif          OBJECT IDENTIFIER ::= { sipServerMIBNotif 1 }
   sipRedirNotif          OBJECT IDENTIFIER ::= { sipServerMIBNotif 2 }

   -- none at this time

   --
   -- Conformance
   --
   sipServerMIBConformance
     OBJECT IDENTIFIER ::= { sipServerMIB 6 }
   sipServerMIBCompliances
     OBJECT IDENTIFIER ::= { sipServerMIBConformance 1 }
   sipServerMIBGroups
     OBJECT IDENTIFIER ::= { sipServerMIBConformance 2 }

   --
   -- Compliance Statements
   --

Lingle/Maeng/Walker                                                 58
   sipCompliance MODULE-COMPLIANCE
       STATUS     current
       DESCRIPTION
            "The compliance statement for SIP entities."

       MODULE -- this module
            MANDATORY-GROUPS { sipServerConfigGroup }
   --                            sipServerStatsGroup,
   --                            sipServerNotifGroup }

            GROUP sipProxyConfigGroup
            DESCRIPTION
                  "This group is mandatory for SIP Proxy servers."

            GROUP sipProxyStatsGroup
            DESCRIPTION
                  "This group is mandatory for SIP Proxy servers."

   --         GROUP sipProxyNotifGroup
   --         DESCRIPTION
   --               "This group is mandatory for SIP Proxy servers."

   --         GROUP sipRedirectConfigGroup
   --         DESCRIPTION
   --               "This object specifies whether or not the Registrar should
             return all currently reachable locations for a
             successfully registering party in the REGISTER response
             message.

             If the value of this object group is TRUE, the Registrar returns
             the locations in the REGISTER response.  If the value mandatory for SIP Redirect servers."

   --         GROUP sipRedirectStatsGroup
   --         DESCRIPTION
   --               "This group is
             FALSE, no location information mandatory for SIP Redirect servers."

   --         GROUP sipRedirectNotifGroup
   --         DESCRIPTION
   --               "This group is provided." mandatory for SIP Redirect servers."

       ::= { sipRegCfg 5 sipServerMIBCompliances 1 }

   sipRegMaxUsers OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object specifies the maximum number of users that the
             registrar supports.  The current number

   --
   -- Units of users is
             reflected by sipRegCurrentUsers."
       ::= Conformance
   --

   sipServerConfigGroup OBJECT-GROUP
       OBJECTS { sipRegCfg 6
               sipServerHost,
               sipInformationAlwaysSendTrying,
               sipInformationTryingInterval,
               sipPgpVersion,
               sipServerDfltAction,
               sipServerRespectUAAction
       }

   sipRegCurrentUsers OBJECT-TYPE
       SYNTAX     Gauge32 (0..4294967295)
       MAX-ACCESS read-only
       STATUS  current
       DESCRIPTION
            "This object specifies the number
            "A collection of users currently
             configured on the registrar." objects providing configuration common
             to SIP Proxy and Redirect servers."

Lingle/Maeng/Walker                                                 59
       ::= { sipRegCfg 7 sipServerMIBGroups 1 }

   --sipServerStatsGroup OBJECT-GROUP
   --    OBJECTS {
   -- Per User Information none at this time
   --    }
   --
   sipRegUserTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipRegUserEntry
       MAX-ACCESS not-accessible    STATUS  current
   --    DESCRIPTION
            "This table contains information on all users registered to
             this Registrar."
   --         "A collection of objects providing common statistics for
   --          SIP Proxy and Redirect servers."
   --    ::= { sipRegCfg 8 sipServerMIBGroups 2 }
   sipRegUserEntry OBJECT-TYPE
       SYNTAX     SipRegUserEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This entry contains information for a single user
             registered to this Registrar."
       INDEX

   sipProxyConfigGroup OBJECT-GROUP
       OBJECTS { sipUserIndex
               sipRequestMaxExpires,
               sipProxyStateful,
               sipProxySendsCancel,
               sipProxyForwardAll1xx,
               sipProxyRecursion,
               sipProxyProvideAlternatives,
               sipProxyRecordRoute,
               sipProxyStateTimeout,
               sipProxyAuthMethod,
               sipProxyAuthPgpAlgorithm,
               sipProxyAuthRealm,
               sipProxyNonceLifeTime,
               sipPgpPrivateKey,
               sipRxProxyAuthRealm,
               sipRxProxyAuthPassword,
               sipRxProxyAuthStatus,
               sipHideRespect
       }
       STATUS  current
       DESCRIPTION
            "A collection of objects providing configuration for
             SIP Proxy servers."
       ::= { sipRegUserTable 1 sipServerMIBGroups 3 }

   SipRegUserEntry ::=
       SEQUENCE

   sipProxyStatsGroup OBJECT-GROUP
       OBJECTS {
                sipUserIndex                            Unsigned32,
                sipUserUri
   SnmpAdminString,
                sipUserPassword                         OCTET STRING,
                sipUserAuthenticationFailures           Counter32,
                sipUserTableRowStatus                   RowStatus
               sipNumProxyRequireFailures
       }

   sipUserIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS  current
       DESCRIPTION
            "This object uniquely identifies a conceptual row in the
             table."
            "A collection of objects providing statistics for
             SIP Proxy servers."
       ::= { sipRegUserEntry 1 sipServerMIBGroups 4 }

   sipUserUri OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-create

   --sipProxyNotifGroup NOTIFICATION-GROUP
   --    OBJECTS {
   -- none at this time
   --    }
   --    STATUS  current
   --    DESCRIPTION
            "This 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

Lingle/Maeng/Walker                                                 60
   --         "A collection of notifications defined for all REGISTER requests." SIP
   --          Proxy servers."
   --    ::= { sipRegUserEntry 2 sipServerMIBGroups 5 }

   sipUserPassword OBJECT-TYPE
       SYNTAX     OCTET STRING (SIZE(0..255))
       MAX-ACCESS read-create
       STATUS     current
       DESCRIPTION
            "This object specifies the password that the user must
             enter when being authenticated."
       ::=

   --sipRedirectConfigGroup OBJECT-GROUP
   --    OBJECTS { sipRegUserEntry 3
   -- none at this time
   --    }

   sipUserAuthenticationFailures OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
   --    STATUS  current
   --    DESCRIPTION
            "This object contains a count of the number
   --         "A collection of times the
             user has failed authentication." objects providing configuration for
   --          SIP Redirect servers."
   --    ::= { sipRegUserEntry 4 sipServerMIBGroups 6 }

   sipUserTableRowStatus OBJECT-TYPE
       SYNTAX     RowStatus
       MAX-ACCESS read-create

   --sipRedirectStatsGroup OBJECT-GROUP
   --    OBJECTS {
   -- none at this time
   --    }
   --    STATUS  current
   --    DESCRIPTION
            "The row status
   --         "A collection of the entry. This object is required
             to create or delete rows remotely by a manager." objects providing statistics for
   --          SIP Redirect servers."
   --    ::= { sipRegUserEntry 5 sipServerMIBGroups 7 }

   --sipRedirectNotifGroup NOTIFICATION-GROUP
   --    OBJECTS {
   -- Per Contact Information none at this time
   --    }
   --
   sipContactTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipContactEntry
       MAX-ACCESS not-accessible    STATUS  current
   --    DESCRIPTION
            "This table contains information on every location where
             every registered user wishes to be found (i.e. has
   provided
             Contact information)."
   --         "A collection of notifications defined for SIP
   --          Redirect servers."
   --    ::= { sipRegCfg 9 sipServerMIBGroups 8 }

   sipContactEntry OBJECT-TYPE
       SYNTAX     SipContactEntry
       MAX-ACCESS not-accessible
       STATUS     current

   END

5.6. SIP Registrar

   SIP-REGISTRAR-MIB DEFINITIONS ::= BEGIN

   IMPORTS
        MODULE-IDENTITY,
        OBJECT-TYPE,
        Counter32,
        Gauge32,
        Unsigned32
             FROM SNMPv2-SMI

        DateAndTime,
        RowStatus,
        TimeStamp,
        TruthValue
             FROM SNMPv2-TC

Lingle/Maeng/Walker                                                 61
        MODULE-COMPLIANCE,
        OBJECT-GROUP
             FROM SNMPv2-CONF

        SnmpAdminString
             FROM SNMP-FRAMEWORK-MIB

        SipServerActions
             FROM SIP-TC

        sipMIB
             FROM SIP-MIB-SMI

        applIndex
             FROM NETWORK-SERVICES-MIB;

   sipRegistrarMIB MODULE-IDENTITY
        LAST-UPDATED   "200007080000Z"
        ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
        CONTACT-INFO
                "SIP MIB Team email: sip-mib@egroups.com

                 Co-editor  Kevin Lingle
                            Cisco Systems, Inc.
                 postal:    7025 Kit Creek Road
                            P.O. Box 14987
                            Research Triangle Park, NC 27709
                            USA
                 email:     klingle@cisco.com
                 phone:     +1-919-392-2029

                 Co-editor  Joon Maeng
                            VTEL Corporation
                 postal:    108 Wild Basin Rd.
                            Austin, TX 78746
                            USA
                 email:     joon_maeng@vtel.com
                 phone:     +1-512-437-4567

                 Co-editor  Dave Walker
                            SS8 Networks, Inc.
                 postal:    80 Hines Road
                            Kanata, ON  K2K 2T8
                            Canada
                 email:     drwalker@ss8networks.com
                 phone:     +1 613 592 2100"
        DESCRIPTION
            "This entry contains information
                "Initial version of Session Initiation Protocol (SIP)
                 Registrar MIB module.

                 SIP is an application-layer signalling protocol for
                 creating, modifying and terminating multimedia
                 sessions with one or more participants. These sessions

Lingle/Maeng/Walker                                                 62
                 include Internet multimedia conferences and Internet
                 telephone calls.  SIP is defined in RFC 2543 (March
                 1999).

                 A Registrar is a single Contact.
             Multiple contacts may exist for server that accepts REGISTER
                 requests.  A Registrar is typically co-located with a single user."
       INDEX
                 Proxy or Redirect Server."
        ::= { sipUserIndex, sipContactIndex sipMIB 5 }

   --
   -- sipReg group
   -- This group contains MIB objects related to SIP Registrars.
   --
   sipRegCfg       OBJECT IDENTIFIER ::= { sipContactTable sipRegistrarMIB 1 }

   SipContactEntry
   sipRegStats     OBJECT IDENTIFIER ::=
       SEQUENCE {
                sipContactIndex                Unsigned32,
                sipContactDisplayName          SnmpAdminString,
                sipContactURI                  SnmpAdminString,
                sipContactLastUpdated          TimeStamp,
                sipContactExpiry               DateAndTime,
                sipContactAction               SipServerActions,
                sipContactPreference           OCTET STRING,
                sipContactRetryAfter           DateAndTime sipRegistrarMIB 2 }

   sipContactIndex

   --
   -- Registrar Configuration
   --
   sipRegCfgTable OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)     SEQUENCE OF SipRegCfgEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "Along with the sipUserIndex, this object uniquely
             identifies a conceptual
            "This table contains configuration objects applicable
             SIP registrars.  Each row represents those objects
             for a particular SIP registrar present in the table." this system.
             The instances of SIP registrars are uniquely identified
             by applIndex."
       ::= { sipContactEntry sipRegCfg 1 }

   sipContactDisplayName

   sipRegCfgEntry OBJECT-TYPE
       SYNTAX     SnmpAdminString     SipRegCfgEntry
       MAX-ACCESS read-only not-accessible
       STATUS     current
       DESCRIPTION
            "This object contains the display name for the Contact.
             For example, 'Santa at Home', or 'Santa on his Sled',
             corresponding to contact URLs
            "A row of
             sip:BigGuy@sip.northpole.ca or
             sip:sclaus817@sip.mobile.com, respectively." common configuration."
       INDEX { applIndex }
       ::= { sipContactEntry 2 sipRegCfgTable 1 }

   sipContactURI

   SipRegCfgEntry ::=
       SEQUENCE {
                sipRegAllowThirdParty           TruthValue,
                sipRegContactDfltExpiryDuration Unsigned32,
                sipRegContactDfltExpiryDate     DateAndTime,
                sipRegMaxContactExpiryDate      Unsigned32,
                sipRegRespHasContacts           TruthValue,
                sipRegMaxUsers                  Unsigned32,
                sipRegCurrentUsers              Gauge32
       }

   sipRegAllowThirdParty OBJECT-TYPE

Lingle/Maeng/Walker                                                 63
       SYNTAX     SnmpAdminString     TruthValue
       MAX-ACCESS read-only read-write
       STATUS     current
       DESCRIPTION
            "This object contains either a SIP URL specifies whether or a URI where not the
             user can be contacted.  This URI Registrar should
             allows third party registrations. In third-party
             registration, the entity issuing the request (in the From
             header) is normally returned to a
             client different from a redirect server, or the entity being registered (in
             the To header) to whom the
             provided Contact information applies.

             If the value of this object is used as TRUE, the
             RequestURI in a SIP request line for requests forwarded by Registrar allows
             third party registrations.  If the value is FALSE, third
             party registrations are rejected: a proxy." 403 Forbidden status
             code is returned to the requestor."
       REFERENCE
            "RFC 2543, Section 4.2.6"
       ::= { sipContactEntry 3 sipRegCfgEntry 1 }

   sipContactLastUpdated

   sipRegContactDfltExpiryDuration OBJECT-TYPE
       SYNTAX     TimeStamp     Unsigned32
       UNITS      "seconds"
       MAX-ACCESS read-only read-write
       STATUS     current
   DESCRIPTION
            "This object indicates specifies the time default expiration (time-to-
             live) of Contact information that is provided by User
             Agents when registering with this contact
             information was accepted. Registrar.  This value
             is only used when no expiration has been specified by the
             user in the REGISTER
             request.

             If the contact information value is
             updated via applied to a subsequent REGISTER registration and is different
             from the default (one hour), the server must return the
             value to the registered User Agent.

             The value contained in this object only applies if the
             value of the same information, sipContactDfltExpiryDate object is NULL.  If
             the value of this object applies, and is also updated." zero, then no
             default expiry is applied to registered contact
             information."
       REFERENCE
             "RFC 2543, Section 4.2.6"
       DEFVAL { 3600 }
       ::= { sipContactEntry 4 sipRegCfgEntry 2 }

   sipContactExpiry

   sipRegContactDfltExpiryDate OBJECT-TYPE
       SYNTAX     DateAndTime
       MAX-ACCESS read-only read-write
       STATUS     current
       DESCRIPTION
            "This object contains specifies the default expiration date and time when the contact (time-
             to-live) of Contact information will that is provided by User
             Agents when registering with this Registrar.  This value

Lingle/Maeng/Walker                                                 64
             is only used when no longer be valid.  Such times may be expiration has been specified by the
             user at registration (Expires header or
             expiry parameter in the Contact information), or a system
             default can be applied."
       ::= { sipContactEntry 5 }

   sipContactPreference OBJECT-TYPE
       SYNTAX     OCTET STRING (SIZE(0..255))
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object specifies the preference for REGISTER request.

             If this contact
             relative value is applied to all other active contacts for same user.  A
             registering user may provide this preference as a 'qvalue'
             parameter registration, the server
             must return the value to the registered User Agent.

             The value contained in this object only applies if the Contact header.

             The format
             value of this item the sipContactDfltExpiryDuration object is a decimal number between 0
             and 1 (for example 0.9).  Higher values indicate locations
             preferred by zero.
             If the user." value of this object applies, and is NULL, then no
             default expiry is applied to
             registered contact information."
       REFERENCE
            "RFC 2543, Section 6.13" 4.2.6"
       ::= { sipContactEntry 6 sipRegCfgEntry 3 }

   sipContactAction

   sipRegMaxContactExpiryDate OBJECT-TYPE
       SYNTAX     SipServerActions     Unsigned32 (0..4294967295)
       UNITS      "seconds"
       MAX-ACCESS read-only read-write
       STATUS     current
       DESCRIPTION
            "This object indicates whether the user wanted specifies the server
             to act as maximum expiry that may be
             requested by a redirect server User Agent for a particular Contact.  User
             Agents can specify expiry using either an Expiry header in
             a REGISTER request, or as using an Expires parameter in a proxy server.  It
             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 optional 'action' parameter User Agent in the
             Contact header." response."
       DEFVAL { 4294967295 }
       ::= { sipContactEntry 7 sipRegCfgEntry 4 }

   sipContactRetryAfter

   sipRegRespHasContacts OBJECT-TYPE
       SYNTAX     DateAndTime     TruthValue
       MAX-ACCESS read-only read-write
       STATUS     current
       DESCRIPTION
            "This object indicates that specifies whether or not the contact information is
             currently inactive, and that it Registrar should only be activated
             after
             return all currently reachable locations for a
             successfully registering party in the date and time specified by REGISTER response
             message.

             If the object.  This value of this object is provided by a user when deleting contact
             information using a TRUE, the Registrar returns
             the locations in the REGISTER request containing a Retry-
             After header."
       REFERENCE
            "RFC 2543, Section 6.32" response.  If the value is
             FALSE, no location information is provided."
       ::= { sipContactEntry 8 sipRegCfgEntry 5 }

   --
   -- Registrar Statistics
   --
   sipRegAcceptedRegistrations

   sipRegMaxUsers OBJECT-TYPE
       SYNTAX     Counter32     Unsigned32 (1..4294967295)
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains a count of specifies the maximum number of REGISTER
             requests users 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

Lingle/Maeng/Walker                                                 65
             registrar supports.  The current number of contact information." users is
             reflected by sipRegCurrentUsers."
       ::= { sipRegStats 1 sipRegCfgEntry 6 }

   sipRegRejectedRegistrations

   sipRegCurrentUsers OBJECT-TYPE
       SYNTAX     Counter32     Gauge32 (0..4294967295)
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains a count of specifies the number REGISTER
             requests that have been rejected by of users currently
             configured on the Registrar." registrar."
       ::= { sipRegStats 2 sipRegCfgEntry 7 }

   --
   -- Notifications Per User Information
   --
   sipMIBNotifPrefix      OBJECT IDENTIFIER
   sipRegUserTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipRegUserEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This table contains information on all users registered to
             each Registrar in this system.  The instances of SIP
             Registrar are uniquely identified by applIndex."
       ::= { sipMIB sipRegCfg 2 }
   sipMIBNotif            OBJECT IDENTIFIER ::=

   sipRegUserEntry OBJECT-TYPE
       SYNTAX     SipRegUserEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This entry contains information for a single user
             registered to this Registrar."
       INDEX { sipMIBNotifPrefix 0 applIndex, sipUserIndex }
   sipNotif               OBJECT IDENTIFIER
       ::= { sipMIBNotif sipRegUserTable 1 }
   sipUANotif             OBJECT IDENTIFIER ::= { sipMIBNotif 2 }
   sipProxyNotif          OBJECT IDENTIFIER

   SipRegUserEntry ::=
       SEQUENCE { sipMIBNotif 3
                sipUserIndex                         Unsigned32,
                sipUserUri                           SnmpAdminString,
                sipUserPassword                      OCTET STRING,
                sipUserAuthenticationFailures        Counter32,
                sipUserTableRowStatus                RowStatus
       }
   sipRedirNotif          OBJECT IDENTIFIER

   sipUserIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This object uniquely identifies a conceptual row in the
             table."
       ::= { sipMIBNotif 4 sipRegUserEntry 1 }
   sipRegNotif            OBJECT IDENTIFIER

Lingle/Maeng/Walker                                                 66
   sipUserUri OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-create
       STATUS     current
       DESCRIPTION
            "This 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."
       ::= { sipMIBNotif 5 sipRegUserEntry 2 }
   -- none at this time

   --
   -- Conformance
   --
   sipMIBConformance      OBJECT IDENTIFIER

   sipUserPassword OBJECT-TYPE
       SYNTAX     OCTET STRING (SIZE(0..255))
       MAX-ACCESS read-create
       STATUS     current
       DESCRIPTION
            "This object specifies the password that the user must
             enter when being authenticated."
       ::= { sipMIB sipRegUserEntry 3 }
   sipMIBCompliances      OBJECT IDENTIFIER ::= { sipMIBConformance 1 }
   sipMIBGroups           OBJECT IDENTIFIER

   sipUserAuthenticationFailures OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "This object contains a count of the number of times the
             user has failed authentication."
       ::= { sipMIBConformance 2 sipRegUserEntry 4 }

   --
   -- Compliance Statements
   --
   sipCompliance MODULE-COMPLIANCE

   sipUserTableRowStatus OBJECT-TYPE
       SYNTAX     RowStatus
       MAX-ACCESS read-create
       STATUS     current
       DESCRIPTION
            "The compliance statement for SIP entities."

       MODULE -- this module
            MANDATORY-GROUPS row status of the entry. This object is required
             to create or delete rows remotely by a manager."
       ::= { sipCommonConfigGroup,
                               sipCommonStatsGroup }
   --                            sipCommonNotifGroup sipRegUserEntry 5 }

            GROUP sipUAConfigGroup
            DESCRIPTION
                  "This group is mandatory for SIP User Agents."

            GROUP sipUAStatsGroup
            DESCRIPTION
                  "This group is mandatory for SIP User Agents."

   --         GROUP sipUANotifGroup
   --         DESCRIPTION
   --               "This group is mandatory for SIP User Agents."

            GROUP sipServerConfigGroup
            DESCRIPTION
                  "This group is mandatory for SIP Proxy/Redirect
                  servers."

   --         GROUP sipServerStatsGroup
   --         DESCRIPTION
   --               "This group is mandatory for SIP Proxy/Redirect
   --                servers."

            GROUP sipProxyConfigGroup
            DESCRIPTION
                  "This group is mandatory for SIP Proxy servers."

            GROUP sipProxyStatsGroup
            DESCRIPTION
                  "This group is mandatory for SIP Proxy servers."

   --         GROUP sipProxyNotifGroup
   --         DESCRIPTION
   --               "This group is mandatory for SIP Proxy servers."

   --         GROUP sipRedirectConfigGroup
   --         DESCRIPTION
   --               "This group is mandatory for SIP Redirect servers."

   --         GROUP sipRedirectStatsGroup
   --         DESCRIPTION

   --               "This group is mandatory for SIP Redirect servers."
   --         GROUP sipRedirectNotifGroup Per Contact Information
   --
   sipContactTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipContactEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
   --
            "This group is mandatory for table contains information on every location where a
             registered user (specified by sipUserIndex) wishes to be
             found (i.e. has provided Contact information) to each SIP Redirect servers."

            GROUP sipRegistrarConfigGroup
            DESCRIPTION
                  "This group is mandatory for
             Registrar in this system.

             The instances of SIP Registrars."

            GROUP sipRegistrarStatsGroup Registrar are uniquely identified by
             applIndex."
       ::= { sipRegCfg 3 }

Lingle/Maeng/Walker                                                 67
   sipContactEntry OBJECT-TYPE
       SYNTAX     SipContactEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "This group is mandatory entry contains information for SIP Registrars."

   --         GROUP sipRegistrarNotifGroup
   --         DESCRIPTION
   --               "This group is mandatory a single Contact.
             Multiple contacts may exist for SIP Registrars." a single user."
       INDEX { applIndex, sipUserIndex, sipContactIndex }
       ::= { sipMIBCompliances sipContactTable 1 }

   --
   -- Units of Conformance
   --
   sipCommonConfigGroup OBJECT-GROUP
       OBJECTS

   SipContactEntry ::=
       SEQUENCE {
               sipProtocolVersion,
               sipServiceOperStatus,
               sipServiceAdminStatus,
               sipServiceStartTime,
               sipServiceLastChange,
               sipTransport,
               sipPortStatus,
               sipUriSupported,
               sipFtrSupported,
               sipOrganization,
               sipMaxTransactions,
               sipRequestDfltExpires,
               sipHideOperation,
               sipUserLocationServerAddr
                sipContactIndex                Unsigned32,
                sipContactDisplayName          SnmpAdminString,
                sipContactURI                  SnmpAdminString,
                sipContactLastUpdated          TimeStamp,
                sipContactExpiry               DateAndTime,
                sipContactAction               SipServerActions,
                sipContactPreference           OCTET STRING,
                sipContactRetryAfter           DateAndTime
       }

   sipContactIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A collection of objects providing configuration common
             to all SIP enities."
            "Along with the sipUserIndex, this object uniquely
             identifies a conceptual row in the table."
       ::= { sipMIBGroups sipContactEntry 1 }

   sipCommonStatsGroup OBJECT-GROUP
       OBJECTS {
               sipSummaryInRequests,
               sipSummaryOutRequests,
               sipSummaryInResponses,
               sipSummaryOutResponses,
               sipSummaryTotalTransactions,
               sipStatsInviteIns,
               sipStatsInviteOuts,
               sipStatsAckIns,
               sipStatsAckOuts,
               sipStatsByeIns,
               sipStatsByeOuts,
               sipStatsCancelIns,
               sipStatsCancelOuts,
               sipStatsOptionsIns,
               sipStatsOptionsOuts,
               sipStatsRegisterIns,
               sipStatsRegisterOuts,
               sipStatsInfoIns,
               sipStatsInfoOuts,
               sipStatsInfoTryingIns,
               sipStatsInfoTryingOuts,
               sipStatsInfoRingingIns,
               sipStatsInfoRingingOuts,
               sipStatsInfoForwardedIns,
               sipStatsInfoForwardedOuts,
               sipStatsInfoQueuedIns,
               sipStatsInfoQueuedOuts,
               sipStatsInfoSessionProgIns,
               sipStatsInfoSessionProgOuts,
               sipStatsSuccessOkIns,
               sipStatsSuccessOkOuts,
               sipStatsRedirMultipleChoiceIns,
               sipStatsRedirMultipleChoiceOuts,
               sipStatsRedirMovedPermIns,
               sipStatsRedirMovedPermOuts,
               sipStatsRedirMovedTempIns,
               sipStatsRedirMovedTempOuts,
               sipStatsRedirSeeOtherIns,
               sipStatsRedirSeeOtherOuts,
               sipStatsRedirUseProxyIns,
               sipStatsRedirUseProxyOuts,
               sipStatsRedirAltServiceIns,
               sipStatsRedirAltServiceOuts,
               sipStatsClientBadRequestIns,
               sipStatsClientBadRequestOuts,
               sipStatsClientUnauthorizedIns,
               sipStatsClientUnauthorizedOuts,
               sipStatsClientPaymentReqdIns,
               sipStatsClientPaymentReqdOuts,
               sipStatsClientForbiddenIns,
               sipStatsClientForbiddenOuts,
               sipStatsClientNotFoundIns ,
               sipStatsClientNotFoundOuts,
               sipStatsClientMethNotAllowedIns,
               sipStatsClientMethNotAllowedOuts,
               sipStatsClientNotAcceptableIns,
               sipStatsClientNotAcceptableOuts,
               sipStatsClientProxyAuthReqdIns,
               sipStatsClientProxyAuthReqdOuts,
               sipStatsClientReqTimeoutIns,
               sipStatsClientReqTimeoutOuts,
               sipStatsClientConflictIns,
               sipStatsClientConflictOuts,
               sipStatsClientGoneIns,
               sipStatsClientGoneOuts,
               sipStatsClientLengthRequiredIns,
               sipStatsClientLengthRequiredOuts,
               sipStatsClientReqEntTooLargeIns,
               sipStatsClientReqEntTooLargeOuts,
               sipStatsClientReqURITooLargeIns,
               sipStatsClientReqURITooLargeOuts,
               sipStatsClientNoSupMediaTypeIns,
               sipStatsClientNoSupMediaTypeOuts,
               sipStatsClientBadExtensionIns,
               sipStatsClientBadExtensionOuts,
               sipStatsClientTempNotAvailIns,
               sipStatsClientTempNotAvailOuts,
               sipStatsClientCallLegNoExistIns,
               sipStatsClientCallLegNoExistOuts,
               sipStatsClientLoopDetectedIns,
               sipStatsClientLoopDetectedOuts,
               sipStatsClientTooManyHopsIns,
               sipStatsClientTooManyHopsOuts,
               sipStatsClientAddrIncompleteIns,
               sipStatsClientAddrIncompleteOuts,
               sipStatsClientAmbiguousIns,
               sipStatsClientAmbiguousOuts,
               sipStatsClientBusyHereIns,
               sipStatsClientBusyHereOuts,
               sipStatsServerIntErrorIns,
               sipStatsServerIntErrorOuts,
               sipStatsServerNotImplementedIns,
               sipStatsServerNotImplementedOuts,
               sipStatsServerBadGatewayIns,
               sipStatsServerBadGatewayOuts,
               sipStatsServerServiceUnavailIns,
               sipStatsServerServiceUnavailOuts,
               sipStatsServerGatewayTimeoutIns,
               sipStatsServerGatewayTimeoutOuts,
               sipStatsServerBadSipVersionIns,
               sipStatsServerBadSipVersionOuts ,
               sipStatsGlobalBusyEverywhereIns,
               sipStatsGlobalBusyEverywhereOuts,
               sipStatsGlobalDeclineIns,
               sipStatsGlobalDeclineOuts,
               sipStatsGlobalNotAnywhereIns,
               sipStatsGlobalNotAnywhereOuts,
               sipStatsGlobalNotAcceptableIns,
               sipStatsGlobalNotAcceptableOuts,
               sipCurrentTransactions,
               sipTransTo,
               sipTransFrom,
               sipTransCallId,
               sipTransCSeq,
               sipTransState,
               sipTransOutstandingBranches,
               sipTransExpiry,
               sipTransCallingPartyContentType,
               sipTransCalledPartyContentType,
               sipNumUnsupportedUris
       }

   sipContactDisplayName OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "A collection
            "This object contains the display name for the Contact.
             For example, 'Santa at Home', or 'Santa on his Sled',
             corresponding to contact URLs of objects providing statistics common
             toall SIP entities."
             sip:BigGuy@sip.northpole.ca or
             sip:sclaus817@sip.mobile.com, respectively."
       ::= { sipMIBGroups sipContactEntry 2 }

   --sipCommonNotifGroup NOTIFICATION-GROUP
   --    OBJECTS {
   -- not at this time
   --    }
   --

   sipContactURI OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
   --
       DESCRIPTION
   --         "A collection of notifications common
            "This object contains either a SIP URL or a URI where the
             user can be contacted.  This URI is normally returned to all a
             client from a redirect server, or is used as the
             RequestURI in a SIP
   --          entities."
   -- request line for requests forwarded by
             a proxy."

Lingle/Maeng/Walker                                                 68
       ::= { sipMIBGroups sipContactEntry 3 }

   sipUAConfigGroup OBJECT-GROUP
       OBJECTS {
               sipUACfgTimerTrying,
               sipUACfgTimerExpires,
               sipUACfgTimerConnect,
               sipUACfgTimerDisconnect,
               sipUACfgRetryInvite,
               sipUACfgRetryBye,
               sipUACfgRetryCancel,
               sipUACfgRetryRegister,
               sipUACfgRetryResponse
       }

   sipContactLastUpdated OBJECT-TYPE
       SYNTAX     TimeStamp
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "A collection
            "This object indicates the time when this contact
             information was accepted.  If the contact information is
             updated via a subsequent REGISTER of objects providing configuration for
             SIP User Agents." the same information,
             this object is also updated."
       ::= { sipMIBGroups sipContactEntry 4 }

   sipUAStatsGroup OBJECT-GROUP
       OBJECTS {
               sipStatsRetryInvites,
               sipStatsRetryByes,
               sipStatsRetryCancels,
               sipStatsRetryRegisters,
               sipStatsRetryResponses
       }

   sipContactExpiry OBJECT-TYPE
       SYNTAX     DateAndTime
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "A collection of objects providing statistics for
             SIP User Agents."
            "This 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 (Expires header or
             expiry parameter in the Contact information), or a system
             default can be applied."
       ::= { sipMIBGroups sipContactEntry 5 }

   --sipUANotifGroup NOTIFICATION-GROUP
   --    OBJECTS {
   -- none at this time
   --    }
   --

   sipContactPreference OBJECT-TYPE
       SYNTAX     OCTET STRING (SIZE(0..255))
       MAX-ACCESS read-only
       STATUS     current
   --
       DESCRIPTION
   --         "A collection
            "This object specifies the preference for this contact
             relative to all other active contacts for same user.  A
             registering user may provide this preference as a 'qvalue'
             parameter in the Contact header.

             The format of notifications defined for SIP User
   --          Agents."
   -- this item is a decimal number between 0
             and 1 (for example 0.9).  Higher values indicate locations
             preferred by the user."
       REFERENCE
            "RFC 2543, Section 6.13"
       ::= { sipMIBGroups sipContactEntry 6 }

   sipServerConfigGroup OBJECT-GROUP
       OBJECTS {
               sipServerHost,
               sipInformationTryingInitial,
               sipInformationTryingInterval,
               sipPgpVersion,
               sipServerDfltAction,
               sipServerRespectUAAction,
               sipRequestUriHostMatching
       }

   sipContactAction OBJECT-TYPE
       SYNTAX     SipServerActions
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
            "A collection of objects providing configuration common
            "This object indicates whether the user wanted the server
             to SIP Proxy and Redirect servers." act as a redirect server or as a proxy server.  It is
             specified by the optional 'action' parameter in the
             Contact header."
       ::= { sipMIBGroups sipContactEntry 7 }

   --sipServerStatsGroup OBJECT-GROUP
   --    OBJECTS {
   -- none at this time
   --    }
   --

   sipContactRetryAfter OBJECT-TYPE

Lingle/Maeng/Walker                                                 69
       SYNTAX     DateAndTime
       MAX-ACCESS read-only
       STATUS     current
   --
       DESCRIPTION
   --         "A collection of objects providing common statistics for
   --          SIP Proxy
            "This object indicates that the contact information is
             currently inactive, and Redirect servers."
   -- that it should only be activated
             after the date and time specified by the object.  This
             value is provided by a user when deleting contact
             information using a REGISTER request containing a Retry-
             After header."
       REFERENCE
            "RFC 2543, Section 6.32"
       ::= { sipMIBGroups sipContactEntry 8 }

   sipProxyConfigGroup OBJECT-GROUP
       OBJECTS {
               sipRequestMaxExpires,
               sipProxyStateful,
               sipProxySendsCancel,
               sipProxyForwardAll1xx,
               sipProxyRecursion,
               sipProxyProvideAlternatives,
               sipProxyRecordRoute,
               sipProxyUseCompact,
               sipProxyRetransmissionBuffer,
               sipProxyAuthMethod,
               sipProxyAuthPgpAlgorithm,
               sipProxyAuthRealm,
               sipProxyNonceLifeTime,
               sipPgpPrivateKey,
               sipRxProxyAuthRealm,
               sipRxProxyAuthPassword,
               sipRxProxyAuthStatus,
               sipHideRespect
       }

   --
   -- Registrar Statistics
   --
   sipRegStatsTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF SipRegStatsEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A collection of
            "This table contains the summary statistics objects
             applicable to all SIP Registrars in this system.
             Each row represents those objects providing configuration for a particular
             SIP Proxy servers." Registrar.  The instances of SIP Registrars are
             uniquely identified by applIndex."
       ::= { sipMIBGroups 9 }

   sipProxyStatsGroup OBJECT-GROUP
       OBJECTS {
               sipNumProxyRequireFailures sipRegStats 1 }

   sipRegStatsEntry OBJECT-TYPE
       SYNTAX     SipRegStatsEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
            "A collection row of objects providing statistics for
             SIP Proxy servers." summary statistics."
       INDEX { applIndex }
       ::= { sipMIBGroups 10 sipRegStatsTable 1 }

   --sipProxyNotifGroup NOTIFICATION-GROUP
   --    OBJECTS

   SipRegStatsEntry ::=
       SEQUENCE {
   -- none at this time
   --
                sipRegAcceptedRegistrations Counter32,
                sipRegRejectedRegistrations Counter32
       }
   --

   sipRegAcceptedRegistrations OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
   --
       DESCRIPTION
   --         "A collection
            "This object contains a count of notifications defined the number of REGISTER
             requests that have been accepted (status code 200) by the

Lingle/Maeng/Walker                                                 70
             Registrar.  This includes additions of new contact
             information, refreshing contact information, as well as
             requests for SIP
   --          Proxy servers."
   -- deletion of contact information."
       ::= { sipMIBGroups 11 }
   --sipRedirectConfigGroup OBJECT-GROUP
   --    OBJECTS {
   -- none at this time
   -- sipRegStatsEntry 1 }
   --

   sipRegRejectedRegistrations OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
   --
       DESCRIPTION
   --         "A collection
            "This object contains a count of objects providing configuration for
   --          SIP Redirect servers."
   -- the number REGISTER
             requests that have been rejected by the Registrar."
       ::= { sipMIBGroups 12 sipRegStatsEntry 2 }

   --sipRedirectStatsGroup OBJECT-GROUP

   --    OBJECTS
   -- Notifications
   --
   sipRegMIBNotif         OBJECT IDENTIFIER ::= { sipRegistrarMIB 3 }

   -- none at this time

   --    }
   --    STATUS  current
   --    DESCRIPTION
   --         "A collection of objects providing statistics for
   --          SIP Redirect servers." Conformance
   --
   sipRegMIBConformance
     OBJECT IDENTIFIER ::= { sipMIBGroups 13 sipRegistrarMIB 4 }

   --sipRedirectNotifGroup NOTIFICATION-GROUP
   --    OBJECTS
   sipRegMIBCompliances
     OBJECT IDENTIFIER ::= { sipRegMIBConformance 1 }
   sipRegMIBGroups
     OBJECT IDENTIFIER ::= { sipRegMIBConformance 2 }

   -- none at this time
   --    } Compliance Statements
   --
   sipRegCompliance MODULE-COMPLIANCE
       STATUS     current
   --
       DESCRIPTION
   --         "A collection of notifications defined
            "The compliance statement for SIP entities."

       MODULE --          Redirect servers." this module
            MANDATORY-GROUPS { sipRegistrarConfigGroup,
                               sipRegistrarStatsGroup }
   --                            sipRegistrarNotifGroup }

       ::= { sipMIBGroups 14 sipRegMIBCompliances 1 }

   sipRegistrarConfigGroup OBJECT-GROUP
       OBJECTS {
               sipRegAllowThirdParty,

Lingle/Maeng/Walker                                                 71
               sipRegContactDfltExpiryDuration,
               sipRegContactDfltExpiryDate,
               sipRegMaxContactExpiryDate,
               sipRegRespHasContacts,
               sipRegMaxUsers,
               sipRegCurrentUsers,
               sipUserUri,
               sipUserPassword,
               sipUserAuthenticationFailures,
               sipUserTableRowStatus,
               sipContactDisplayName,
               sipContactURI,
               sipContactLastUpdated,
               sipContactExpiry,
               sipContactPreference,
               sipContactAction,
               sipContactRetryAfter
       }
       STATUS  current
       DESCRIPTION
            "A collection of objects providing configuration for
             SIP Registrars."
       ::= { sipMIBGroups 15 sipRegMIBGroups 1 }

   sipRegistrarStatsGroup OBJECT-GROUP
       OBJECTS {
               sipRegAcceptedRegistrations,
               sipRegRejectedRegistrations
       }
       STATUS  current
       DESCRIPTION
            "A collection of objects providing statistics for
             SIP Registrars."
       ::= { sipMIBGroups 16 sipRegMIBGroups 2 }

   --sipRegistrarNotifGroup NOTIFICATION-GROUP
   --    OBJECTS {
   -- none at this time
   --    }
   --    STATUS  current
   --    DESCRIPTION
   --         "A collection of notifications defined for SIP
   --          Registrars."
   --    ::= { sipMIBGroups 17 sipRegMIBGroups 3 }

   END

6. Security Considerations

   There are a number of management objects defined in this MIB that
   have a MAX-ACCESS clause of read-write and/or read-create.  Such
   objects may be considered sensitive or vulnerable in some network
   environments. The support for SET operations in a non-secure

Lingle/Maeng/Walker                                                 72
   environment without proper protection can have a negative effect on
   network operations.

   The managed objects in this MIB contain sensitive information since,
   collectively, they allow tracing and influencing of connections in
   SIP devices and provide information of their connection
   characteristics.

   It is thus important to control even GET access to these objects and
   possibly to even encrypt the values of these object when sending
   them over the network via SNMP. Not all versions of SNMP provide
   features for such a secure environment.

   SNMPv1 by itself is not a secure environment. Even if the network
   itself is secure (for example by using IPSec), even then, there is
   no control as to who on the secure network is allowed to access and
   GET/SET (read/change/create/delete) the objects in this MIB.

   It is recommended that the implementers consider the security
   features as provided by the SNMPv3 framework. Specifically, the use
   of the User-based Security Model RFC 2574 [18] and the View-based
   Access Control Model RFC 2575 [19] is recommended.

   It is then a customer/user responsibility to ensure that the SNMP
   entity giving access to an instance of this MIB, is properly
   configured to give access to the objects only to those principals
   users) that have legitimate rights to indeed GET or SET
   (change/create/delete) them.

7. Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11.  Copies of
   claims of rights made available for publication and any assurances
   of licenses to be made available, or the result of an attempt made
   to obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification
   can be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.

8. Full Copyright Statement

   Copyright (C)

Lingle/Maeng/Walker                                                 73
   Copyright(C) The Internet Society (2000).  All Rights Reserved. This
   document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph
   are included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

9. References

   [1]  Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
        Describing SNMP Management Frameworks", RFC 2271, January 1998.

   [2]  Rose, M. and K. McCloghrie, "Structure and Identification of
        Management Information for TCP/IP-based Internets", STD 16, RFC
        1155, May 1990.

   [3]  Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
        RFC 1212, March 1991.

   [4]  Rose, M., "A Convention for Defining Traps for use with the
        SNMP", RFC 1215, March 1991.

   [5]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
        M. and S. Waldbusser, "Structure of Management Information
        Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

   [6]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
        M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
        RFC 2579, April 1999.

   [7]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
        M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
        58, RFC 2580, April 1999.

   [8]  Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
        Network Management Protocol", STD 15, RFC 1157, May 1990.

Lingle/Maeng/Walker                                                 74
   [9]  Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
        "Introduction to Community-based SNMPv2", RFC 1901, January
           1996.

   [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
        "Transport Mappings for Version 2 of the Simple Network
        Management Protocol (SNMPv2)", RFC 1906, January 1996.

   [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
        Processing and Dispatching for the Simple Network Management
        Protocol (SNMP)", RFC 2272, January 1998.

   [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
        for version 3 of the Simple Network Management Protocol
        (SNMPv3)", RFC 2274, January 1998.

   [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
        Operations for Version 2 of the Simple Network Management
        Protocol (SNMPv2)", January 1996.

   [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
        2273, January 1998

   [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
        Control Model (VACM) for the Simple Network Management Protocol
        (SNMP)", RFC 2275, January 1998.

   [16] Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [17] M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg,
        "SIP: Session Initiation Protocol", RFC 2543, March 1999.

   [18] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
        for version 3 of the Simple Network Management Protocol
        (SNMPv3)", RFC 2574, April 1999.

   [19] McCloghrie, K. N. Freed, and A. Bierman, "Entity S, Kille, "Network Services Monitoring MIB", RFC 2037, October
        1996.
        2788, March 2000.

   [20] Steve Donavan, "The SIP INFO Method", Internet Draft, draft-
        ietf-sip-info-method-02.txt, February 2000 ietf-sip-
        info-method-04.txt, work in progress.

10. Authors' Addresses

   Kevin Lingle
   Cisco Systems, Inc.
   7025 Kit Creek Road
   P.O. Box 14987
   Research Triangle Park, NC 27709 USA
   Email: klingle@cisco.com
   phone: +1-919-392-2029

Lingle/Maeng/Walker                                                 75
   Joon Maeng
   VTEL Corporation
   108 Wild Basin Rd.
   Austin, TX 78746 USA
   email: joon_maeng@vtel.com
   phone: +1-512-437-4567

   Dave Walker
   SS8 Networks, Inc.
   135 Michael Cowpland Drive, Suite 200
   80 Hines Road
   Kanata, ON  K2M 2E9  K2K 2T8 Canada
   email: drwalker@ss8networks.com
   phone: +1 613 592 2459" 2100

Lingle/Maeng/Walker                                                 76