Internet Draft Charles Schell draft-ietf-ipcdn-pktc-signaling-00.txt Motorola Satish Kumar Texas Instruments Sumanth Channabasappa Alopa Networks Inc Expires: April 25, 2003 October 25, 2002 Network Control Signaling (NCS) Signaling MIB for PacketCable/IPCablecom MTAs Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of RFC 2026 [18]. 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 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 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 Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright Notice Copyright (C) The Internet Society (2002). All Rights Reserved. Abstract This memo defines the Signaling Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it provides a common data and format representation for PacketCable/IPCablecom compliant Multimedia Terminal Adapter devices. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. Schell/Kumar/Channabasappa Page 1 10/25/2002 [Page 1] Internet Draft PacketCable Signaling MIB October 2002 Table of Contents 1 The SNMP Management Framework ................................... 2 2 Glossary ........................................................ 3 2.1 MTA .......................................................... 3 3 Overview ........................................................ 3 3.1 Structure of the MIB .......................................... 3 3.1.1 pktcSigMibObjects ........................................... 3 3.1.1.1 pktcSigDevConfigObjects ................................... 4 3.1.1.2 pktcNcsEndPntConfigObjects ................................ 5 3.1.1.3 pktcSigEndPntConfigObjects ................................ 5 3.1.1.4 PktcDcsEndPntConfigObjects ................................ 5 3.1.2 pktcSigNotification ......................................... 5 3.1.3 pktcSigConformance .......................................... 6 4 Definitions ..................................................... 6 5 Acknowledgments ................................................ 28 6 References ..................................................... 28 7 Security Considerations ........................................ 30 8 Intellectual Property .......................................... 30 9 Authors Addresses .............................................. 31 10 Full Copyright Statement ...................................... 31 1. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [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 STD 16, 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], STD 58, RFC 2579 [6] and STD 58, 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 1906 [10], RFC 2572 [11] and RFC 2574 [12]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is Schell/Kumar/Channabasappa Expires April 2003 [Page 2] Internet Draft PacketCable Signaling MIB October 2002 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 2573 [14] and the view-based access control mechanism described in RFC 2575 [15]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [16]. Managed objects are accessed via a virtual information store, termed as 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 machine readable information is not considered to change the semantics of the MIB. 2. Glossary The terms in this document are derived either from normal cable system usage, or from the documents associated with the IPcablecom/PacketCable Specification process. 2.1. MTA Multimedia Terminal Adapter, a device that contains the interface(s) to a physical voice device, a network interface, CODECs, and all signaling and encapsulation functions required for VoIP transport, class feature signaling and QoS signaling. 3. Overview This MIB provides a set of objects required for Signaling PacketCable/IPCablecom compliant MultiMedia Terminal Adapter (MTA) devices. The significance of each MIB object is defined along with applicable default values. Since telephone systems are typically very complex and often have a wide distribution, it is important for management systems to support MTAs from multiple vendors at the same time, including those from multiple countries. As a result, this MIB module provides objects suitable for operating in the widest variety of marketplaces as is possible. Schell/Kumar/Channabasappa Expires April 2003 [Page 3] Internet Draft PacketCable Signaling MIB October 2002 3.1. Structure of the MIB This MIB is identified by pktcSigMib and is structured in three groups: o Signaling information that control device and endpoint configuration objects(pktcSigMibObjects). o Signaling Notification object, that notifies the status(pktcSigNotification) o Signaling Conformance has mandatory signaling objects(pktcSigConformance) Each group of objects is explained in detail. 3.1.1. pktcSigMibObjects The objects in pktcSigMibObjects group is divided into four sub groups: o Device configuration MIB explain MTA configuration (pktcSigDevConfigObjects). o NCS Endpoint configuration MIB is explained in pktcNcsEndPntConfigObjects o Endpoint signaling configuration MIB is in pktcSigEndPntConfigObjects o DCS Endpoint configuration is explained in pktcDcsEndPntConfigObjects Each group of objects are explained in detail. 3.1.1.1 pktcSigDevConfigObjects pktcSigDevCodecTable - this table describes MTA supported codec types. pktcSigDevEchoCancellation - This object identifies the capability of echo cancellation on the device. pktcSigDevSilenceSuppression - This object specifies if the device is capable of silence suppression (Voice Activity Detection). pktcSigDevConnectionMode - This object specifies the connection modes that The MTA device can support. pktcSigDevR0Cadence - this object specifies ring cadence 0. pktcSigDevR6Cadence - this object specifies ring cadence 6. pktcSigDevR7Cadence - this object specifies ring cadence 7. pktcSigDefCallSigTos - this object specifies the default value used in the IP header for setting the Type of Service (TOS) value for call signaling. pktcSigDefMediaStreamTos - this object specifies the default value used in the IP header for setting the Type of Service (TOS) value for media stream packets. Schell/Kumar/Channabasappa Expires April 2003 [Page 4] Internet Draft PacketCable Signaling MIB October 2002 pktcSigTosFormatSelector - this object specifies the format of the default signaling and media Type of Service (TOS) values. pktcSigCapabilityTable - this table specifies list of supported signaling types, versions and vendor extensions for MTA. pktcSigDefNcsReceiveUdpPort - this object contains the MTA User Datagram Protocol (UDP) receive port that is being used for NCS call signaling. pktcSigServiceClassNameUS - this object contains a string indicating the Service Class Name to create an Upstream Service Flow for NCS. pktcSigServiceClassNameDS - this object contains a string indicating the Service Class Name to create an Downstream Service Flow for NCS. pktcSigServiceClassNameMask - this object contains a value for the Call Signaling Network Mask. pktcSigNcsServiceFlowState - this object contains a status value of the Call Signaling Service Flow. pktcSigDevR1Cadence - this object specifies ring cadence 1. pktcSigDevR2Cadence - this object specifies ring cadence 2. pktcSigDevR3Cadence - this object specifies ring cadence 3. pktcSigDevR4Cadence - this object specifies ring cadence 4. pktcSigDevR5Cadence - this object specifies ring cadence 5. pktcSigDevRgCadence - this object specifies ring cadence rg. pktcSigDevRsCadence - this object specifies ring cadence rs. pktcSigDevRtCadence - this object specifies ring cadence rt. pktcSigDevCIDMode - this international object selects various modes of caller id in common use throughout the world. pktcSigDevCIDFskAfterRing - this international object sets the delay between the end of first ringing and the transmission of caller id information. pktcSigDevCIDFskAfterDTAS - this international object sets the delay between the dual-tone alert signal and the transmission of caller id information. pktcSigDevCIDRingAfterFSK - this international object sets the delay between the transmission of caller id information and the Schell/Kumar/Channabasappa Expires April 2003 [Page 5] Internet Draft PacketCable Signaling MIB October 2002 first ringing pattern. pktcSigDevCIDDTASAfterLR - this international object sets the delay between the end of a line reversal and the dual-tone alert signal. pktcSigDevRingCadenceTable - this international object provides a flexible structure within which to specify a variety of ring cadences. pktcSigDevStandardRingCadence - this international object specifies the standard ring assumed by the MTA. pktcSigDevRingSplashCadence - this international object specifies the standard splash ring assumed by the MTA. pktcSigDevToneTable - this international object specifies a flexible structure within which to specify all of the tones used in the MTA. 3.1.1.2 pktcNcsEndPntConfigObjects pktcNcsEndPntConfigTable - this table describes the PacketCable(tm) NCS EndPoint configuration. The number of entries in this table represents the number of provisioned end points. 3.1.1.3 pktcSigEndPntConfigObjects pktcSigEndPntConfigTable - this table describes the packet cable EndPoint slected signaling type. The number of entries in this table represents the number of provisioned end points. 3.1.1.4 pktcDcsEndPntConfigObjects This object is reserved for future use in Distributed Call Signaling (DCS). 3.1.2. pktcSigNotification This object is used for signaling notification and reserved for future use. 3.1.3. pktcSigConformance pktcSigCompliances - this tables has one object that has compliance statement for devices that implement Signaling on the MTA. pktcSigGroups - this table contains group of objects for the common portion of the PacketCable NCS and Signaling MIB. pktcInternationalGroup - this table extends this MIB Module by establishing Schell/Kumar/Channabasappa Expires April 2003 [Page 6] Internet Draft PacketCable Signaling MIB October 2002 a set of objects designed to support operations over the widest range of marketplaces as is possible. 4. Definitions PKTC-SIG-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, mib-2 FROM SNMPv2-SMI InetAddressType, InetAddress, InetPortNumber FROM INET-ADDRESS-MIB TEXTUAL-CONVENTION, RowStatus, TruthValue FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF SnmpAdminString FROM SNMP-FRAMEWORK-MIB ifIndex FROM IF-MIB; pktcSigMib MODULE-IDENTITY LAST-UPDATED "200210250000Z" -- October 25, 2002 ORGANIZATION "CableLabs - PacketCable OSS Group" CONTACT-INFO "Satish Kumar Mudugere Eswaraiah Texas Instruments India (P) Ltd., Golf view, Wind Tunnel Road Murugesh Palya Bangalore - 560 017, INDIA Phone: +91 80 5269451 Email: satish.kumar@ti.com Sumanth Channabasappa Alopa Networks Inc 248, McCaslin Bvld #101, Louisville, Colorado - 80027 U.S.A. Phone: +1 303 604 6595 Email: Sumanth@alopa.com Charles Schell Motorola BCS/IPNS Schell/Kumar/Channabasappa Expires April 2003 [Page 7] Internet Draft PacketCable Signaling MIB October 2002 101 Tournament Drive, Bldg. 3 Horsham, PA 19044, USA Phone: +1 215-323-1145 E-Mail: cschell@motorola.com IETF IPCDN Working Group General Discussion: ipcdn@ietf.org Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn Chair: Richard Woundy, rwoundy@broadband.att.com" DESCRIPTION "This MIB module supplies the basic management object for the PacketCable Signaling protocols. This version of the MIB includes common signaling and Network Call Signaling (NCS) related signaling objects." REVISION "200210210000Z" DESCRIPTION "Initial Introduction of the draft of the document." ::= { mib-2 99992 } -- to be assigned by IANA. -- Textual Conventions PktcCodecType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION " These are the various types of codecs that may be supported." SYNTAX INTEGER { other (1), unknown (2), g729 (3), g729a (4), g729e (5), g711mu (6), g726K32 (7), -- G.726 32 Khz g728 (8), g711a (9), g726K16 (10), -- G.726 16 Khz g726K24 (11), -- G.726 24 Khz g726K40 (12) -- G.726 40 Khz } PktcRingCadence ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION " This object represents a ring cadence in bit string format. The ring cadence representation starts with the first 1 in the pattern (the leading 0s in the MSB are padding and are to be ignored). Each bit represents 100ms of tone; 1 is tone, 0 is no tone. Initial 60 bits are used for cadence representation. Bit 61 is Schell/Kumar/Channabasappa Expires April 2003 [Page 8] Internet Draft PacketCable Signaling MIB October 2002 used to represent repeatable(when set to ZERO) and non repeatable (when set to ONE) characteristic of cadence. Other three bits are reserved for future use, and currently set to 000. Repeatable characteristic of cadence is currently coded as 0000, and 1000 means non repeatable As an example, the hex representation of a ring cadence of 0.5 secs on; 4 secs off; repeatable would be: 0x1F0000000000." SYNTAX BITS { interval1 (0), interval2 (1), interval3 (2), interval4 (3), interval5 (4), interval6 (5), interval7 (6), interval8 (7), interval9 (8), interval10 (9), interval11 (10), interval12 (11), interval13 (12), interval14 (13), interval15 (14), interval16 (15), interval17 (16), interval18 (17), interval19 (18), interval20 (19), interval21 (20), interval22 (21), interval23 (22), interval24 (23), interval25 (24), interval26 (25), interval27 (26), interval28 (27), interval29 (28), interval30 (29), interval31 (30), interval32 (31), interval33 (32), interval34 (33), interval35 (34), interval36 (35), interval37 (36), interval38 (37), interval39 (38), interval40 (39), interval41 (40), interval42 (41), interval43 (42), interval44 (43), Schell/Kumar/Channabasappa Expires April 2003 [Page 9] Internet Draft PacketCable Signaling MIB October 2002 interval45 (44), interval46 (45), interval47 (46), interval48 (47), interval49 (48), interval50 (49), interval51 (50), interval52 (51), interval53 (52), interval54 (53), interval55 (54), interval56 (55), interval57 (56), interval58 (57), interval59 (58), interval60 (59), interval61 (60), interval62 (61), interval63 (62), interval64 (63) } PktcSigType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION " These are the various types of signaling that may be supported. ncs - network call signaling a derivation of MGCP (Media Gateway Control Protocol) version 1.0 dcs - distributed call signaling a derivation of SIP (Session Initiation Protocol)RFC 2543" SYNTAX INTEGER { other(1), unknown(2), ncs(3), dcs(4) } pktcSigMibObjects OBJECT IDENTIFIER ::= { pktcSigMib 1 } pktcSigDevConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 1 } pktcNcsEndPntConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 2 } pktcSigEndPntConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 3 } pktcDcsEndPntConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 4 } -- -- The pktcSigDevCodecTable defines the codecs supported by the -- Media Terminal Adapter (MTA). There is one entry for each -- codecs supported. -- Schell/Kumar/Channabasappa Expires April 2003 [Page 10] Internet Draft PacketCable Signaling MIB October 2002 pktcSigDevCodecTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigDevCodecEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This table describes the MTA supported codec types." ::= { pktcSigDevConfigObjects 1 } pktcSigDevCodecEntry OBJECT-TYPE SYNTAX PktcSigDevCodecEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " List of supported codecs types for the MTA." INDEX { pktcSigDevCodecIndex } ::= { pktcSigDevCodecTable 1 } PktcSigDevCodecEntry ::= SEQUENCE { pktcSigDevCodecIndex Integer32, pktcSigDevCodecType PktcCodecType, pktcSigDevCodecMax Integer32 } pktcSigDevCodecIndex OBJECT-TYPE SYNTAX Integer32 (1..16383) MAX-ACCESS not-accessible STATUS current DESCRIPTION " The index value which uniquely identifies an entry in the pktcSigDevCodecTable." ::= { pktcSigDevCodecEntry 1 } pktcSigDevCodecType OBJECT-TYPE SYNTAX PktcCodecType MAX-ACCESS read-only STATUS current DESCRIPTION " A codec type supported by this MTA." ::= { pktcSigDevCodecEntry 2 } pktcSigDevCodecMax OBJECT-TYPE SYNTAX Integer32(1..16383) MAX-ACCESS read-only STATUS current DESCRIPTION " The maximum number of simultaneous sessions of the specific codec that the MTA can support" ::= { pktcSigDevCodecEntry 3 } -- Schell/Kumar/Channabasappa Expires April 2003 [Page 11] Internet Draft PacketCable Signaling MIB October 2002 -- These are the common signaling related definitions that affect the -- entire MTA device. -- pktcSigDevEchoCancellation OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION " This object specifies if the device is capable of echo cancellation." ::= { pktcSigDevConfigObjects 2 } pktcSigDevSilenceSuppression OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION " This object specifies if the device is capable of silence suppression (Voice Activity Detection)." ::= { pktcSigDevConfigObjects 3 } pktcSigDevConnectionMode OBJECT-TYPE SYNTAX BITS { voice(0), fax(1), modem(2) } MAX-ACCESS read-only STATUS current DESCRIPTION " This object specifies the connection modes that the MTA device can support." ::= { pktcSigDevConfigObjects 4 } -- -- In the United States Ring Cadences 0, 6, and 7 are custom -- ring cadences definable by the user. The following three -- objects are used for these definitions. -- pktcSigDevR0Cadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence 0 (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." Schell/Kumar/Channabasappa Expires April 2003 [Page 12] Internet Draft PacketCable Signaling MIB October 2002 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, interval7, interval8, interval9, interval10, interval11, interval12, interval13, interval14, interval15, interval16, interval17, interval18, interval19, interval20 } } ::= { pktcSigDevConfigObjects 5 } pktcSigDevR6Cadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence 6 (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, interval7, interval8, interval9, interval10, interval11, interval12, interval13, interval14, interval15, interval16, interval17, interval18, interval19, interval20 } } ::= { pktcSigDevConfigObjects 6 } pktcSigDevR7Cadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence 6 (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, interval7, interval8, interval9, interval10, interval11, interval12, interval13, interval14, interval15, interval16, interval17, interval18, interval19, interval20 } } ::= { pktcSigDevConfigObjects 7 } pktcSigDefCallSigTos OBJECT-TYPE SYNTAX Integer32 (0..63) MAX-ACCESS read-write STATUS current DESCRIPTION " The default value used in the IP header for setting the Type of Service (TOS) value for call signaling. " REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 0 } ::= { pktcSigDevConfigObjects 8 } pktcSigDefMediaStreamTos OBJECT-TYPE SYNTAX Integer32 (0..63) MAX-ACCESS read-write STATUS current DESCRIPTION " The default value used in the IP header for setting the Type of Service (TOS) value for media stream packets. " REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 0 } Schell/Kumar/Channabasappa Expires April 2003 [Page 13] Internet Draft PacketCable Signaling MIB October 2002 ::= { pktcSigDevConfigObjects 9 } pktcSigTosFormatSelector OBJECT-TYPE SYNTAX INTEGER { ipv4TOSOctet(1), dscpCodepoint(2) } MAX-ACCESS read-write STATUS current DESCRIPTION " The format of the default signaling and media Type of Service (TOS) values. " DEFVAL { ipv4TOSOctet } ::= { pktcSigDevConfigObjects 10 } -- -- pktcSigCapabilityTable - This table defines the valid signaling -- types supported by this MTA. -- pktcSigCapabilityTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigCapabilityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This table describes the signaling types by this MTA." ::= { pktcSigDevConfigObjects 11 } pktcSigCapabilityEntry OBJECT-TYPE SYNTAX PktcSigCapabilityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " Entries in pktcMtaDevSigCapabilityTable - List of supported signaling types, versions and vendor extensions for this MTA. Each entry in the list provides for one signaling type and version combination. If the device supports multiple versions of the same signaling type - it will require mutiple entries." INDEX { pktcSignalingIndex } ::= { pktcSigCapabilityTable 1 } PktcSigCapabilityEntry ::= SEQUENCE { pktcSignalingIndex Integer32, pktcSignalingType PktcSigType, pktcSignalingVersion SnmpAdminString, pktcSignalingVendorExtension SnmpAdminString } pktcSignalingIndex OBJECT-TYPE SYNTAX Integer32 (1..16383) MAX-ACCESS not-accessible STATUS current DESCRIPTION " The index value which uniquely identifies an entry in the pktcSigCapabilityTable." Schell/Kumar/Channabasappa Expires April 2003 [Page 14] Internet Draft PacketCable Signaling MIB October 2002 ::= { pktcSigCapabilityEntry 1 } pktcSignalingType OBJECT-TYPE SYNTAX PktcSigType MAX-ACCESS read-only STATUS current DESCRIPTION " The Type indentifies the type of signaling used, this can be NCS, DCS, etc. This value has to be associated with a single signaling version." ::= { pktcSigCapabilityEntry 2 } pktcSignalingVersion OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION " Provides the version of the signaling type - reference pktcSignalingType. Examples would be 1.0 or 2.33 etc." ::= { pktcSigCapabilityEntry 3 } pktcSignalingVendorExtension OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION " The vendor extension allows vendors to provide a list of additional capabilities, vendors can decide how to encode these Extensions, although space separated text is suggested." ::= { pktcSigCapabilityEntry 4 } pktcSigDefNcsReceiveUdpPort OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-only STATUS current DESCRIPTION " This object contains the MTA User Datagram Protocol (UDP) receive port that is being used for NCS call signaling. This object should only be changed by the configuration file." REFERENCE "Refer to Packetcable NCS specification [17]" DEFVAL { 2427 } ::= { pktcSigDevConfigObjects 12 } pktcSigServiceClassNameUS OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION " This object contains a string indicating the Service Class Schell/Kumar/Channabasappa Expires April 2003 [Page 15] Internet Draft PacketCable Signaling MIB October 2002 Name to create an Upstream Service Flow for NCS. If the object has an empty string value then the NCS SF is not created and the best effort primary SF is used for NCS data. Setting this object to a different value does not cause the US SF to be re-created." DEFVAL { "" } ::= { pktcSigDevConfigObjects 13 } pktcSigServiceClassNameDS OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION " This object contains a string indicating the Service Class Name to create a Downstream Service Flow for NCS. If the object has an empty string value then the NCS SF is not created and the best effort primary SF is used for NCS data. Setting this object to a different value does not cause the DS SF to be re-created." DEFVAL { "" } ::= { pktcSigDevConfigObjects 14 } pktcSigServiceClassNameMask OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION " This object contains a value for the Call Signaling Network Mask. The value is used as the NCS Call Signaling classifier mask. The object is used to delete the NCS SF when set to zero. When the object is set to a non-zero value by the SNMP Manager, the NCS SF are to be created" DEFVAL { 0 } ::= { pktcSigDevConfigObjects 15 } pktcSigNcsServiceFlowState OBJECT-TYPE SYNTAX INTEGER { notactive (1), active (2), error (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains a status value of the Call Signaling Service Flow. - 'not-active' indicates that the NCS SF is not being used, and has not tried to be created, - 'active' indicates that the NCS SF is in use, - 'error' indicates that the NCS SF creation resulted in an error and the best effort channel is used for NCS Signaling" Schell/Kumar/Channabasappa Expires April 2003 [Page 16] Internet Draft PacketCable Signaling MIB October 2002 ::= { pktcSigDevConfigObjects 16 } pktcSigDevR1Cadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence 1 (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, interval7, interval8, interval9, interval10, interval11, interval12, interval13, interval14, interval15, interval16, interval17, interval18, interval19, interval20 } } ::= { pktcSigDevConfigObjects 17 } pktcSigDevR2Cadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence 2 (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, interval7, interval8, interval13, interval14, interval15, interval16, interval17, interval18, interval19, interval20 } } ::= { pktcSigDevConfigObjects 18 } pktcSigDevR3Cadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence 3 (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval4, interval7, interval8, interval9, interval10, interval13, interval14, interval15, interval16, interval17, interval18, interval19, interval20 } } ::= { pktcSigDevConfigObjects 19 } pktcSigDevR4Cadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence 4 (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval6, interval7, interval8, interval9, interval10, interval11, interval12, interval13, interval14, interval15, interval18, interval19, interval20 } } ::= { pktcSigDevConfigObjects 20 } Schell/Kumar/Channabasappa Expires April 2003 [Page 17] Internet Draft PacketCable Signaling MIB October 2002 pktcSigDevR5Cadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence 5 (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval61 } } ::= { pktcSigDevConfigObjects 21 } pktcSigDevRgCadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence rg (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, interval7, interval8, interval9, interval10, interval11, interval12, interval13, interval14, interval15, interval16, interval17, interval18, interval19, interval20 } } ::= { pktcSigDevConfigObjects 22 } pktcSigDevRsCadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence rs (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval61 } } ::= { pktcSigDevConfigObjects 23 } pktcSigDevRtCadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence rt (a user defined field) where each bit (least significant bit) represents a duration of 100 milliseconds (6 seconds total)." DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, interval7, interval8, interval9, interval10, interval11, interval12, interval13, interval14, interval15, interval16, interval17, interval18, interval19, interval20 } } ::= { pktcSigDevConfigObjects 24 } pktcSigPowerRingFrequency OBJECT-TYPE SYNTAX INTEGER { twenty(1), twentyFive(2), thirtyThreePointThreeThree(3), Schell/Kumar/Channabasappa Expires April 2003 [Page 18] Internet Draft PacketCable Signaling MIB October 2002 fifty(4) } UNITS "Hertz" MAX-ACCESS read-write STATUS current DESCRIPTION " The power ring frequency is the frequency at which the sinusoidal voltage must travel down the twisted pair to make terminal equipment ring. Different countries define different electrical characteristics to make this happen. ETS 300 001 (1998) [21] lists the frequency ranges that are defined for each country." DEFVAL {twenty} ::= { pktcSigDevConfigObjects 25 } pktcSigPCMCoding OBJECT-TYPE SYNTAX INTEGER { aLaw(1), uLaw(2) } MAX-ACCESS read-write STATUS current DESCRIPTION " This is the Pulse Code Modulation (PCM) format used by an EMTA when coding and decoding analog telephone signals. The default will be aLaw(1)." ::= { pktcSigDevConfigObjects 26 } pktcSigPulseSignalTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigPulseSignalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " The Pulse signal table defines the pulse signal operation. There are four types of international pulse signals, initial ring, meter pulse, reverse polarity and no battery. The Pulse duration type is specific and it is specified with a 1 to 32 value." ::= { pktcSigDevConfigObjects 27 } pktcSigPulseSignalEntry OBJECT-TYPE SYNTAX PktcSigPulseSignalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " Unique value ranging from 1 to 32 that will correspond to the value specified by the operator." INDEX { pktcSigPulseSignalIndex } ::= { pktcSigPulseSignalTable 1 } PktcSigPulseSignalEntry ::= SEQUENCE { pktcSigPulseSignalIndex Integer32, pktcSigPulseSignalDuration Integer32, pktcSigPulseSignalType INTEGER, pktcSigPulseSignalDbLevel Integer32, Schell/Kumar/Channabasappa Expires April 2003 [Page 19] Internet Draft PacketCable Signaling MIB October 2002 pktcSigPulseSignalFrequency INTEGER, pktcSigPulseSignalRepeatCount Integer32, pktcSigPulseSignalPauseDuration Integer32} pktcSigPulseSignalIndex OBJECT-TYPE SYNTAX Integer32 (1..32) MAX-ACCESS not-accessible STATUS current DESCRIPTION " The table index equivalent to the operator specific pulse type and duration." ::= { pktcSigPulseSignalEntry 1 } pktcSigPulseSignalDuration OBJECT-TYPE SYNTAX Integer32 (1..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " The pulse duration varies according to the operator and country." DEFVAL { 1000 } ::= {pktcSigPulseSignalEntry 2 } pktcSigPulseSignalType OBJECT-TYPE SYNTAX INTEGER { initialRing(1), meterPulse(2), reversePolarity(3), noBattery(4) } MAX-ACCESS read-write STATUS current DESCRIPTION " There are four types of international pulse signals." DEFVAL { initialRing } ::= { pktcSigPulseSignalEntry 3 } pktcSigPulseSignalDbLevel OBJECT-TYPE SYNTAX Integer32 (-25..15) UNITS "dbm" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the decibel level at which the meter pulse could be generated." ::={pktcSigPulseSignalEntry 4 } pktcSigPulseSignalFrequency OBJECT-TYPE SYNTAX INTEGER { fifty(1), Schell/Kumar/Channabasappa Expires April 2003 [Page 20] Internet Draft PacketCable Signaling MIB October 2002 twelvethousand(2), sixteenthousand(3) } UNITS "Hertz" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the frequency at which the meter pulse could be generated." ::= { pktcSigPulseSignalEntry 5} pktcSigPulseSignalRepeatCount OBJECT-TYPE SYNTAX Integer32 (0..5000) MAX-ACCESS read-write STATUS current DESCRIPTION " This is the repeat count, which signifies how many times to repeat the pulse." ::={ pktcSigPulseSignalEntry 6 } pktcSigPulseSignalPauseDuration OBJECT-TYPE SYNTAX Integer32 (1..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " The pause duration between pulses varies according to the operator and country." ::= {pktcSigPulseSignalEntry 7 } pktcSigDevCIDMode OBJECT-TYPE SYNTAX INTEGER { northAmerican(1), duringRingingETS(2), dtAsETS(3), rpAsETS(4), lrAsETS(5) } MAX-ACCESS read-write STATUS current DESCRIPTION " For both on-hook and off-hook Caller ID, pktcSigDevCIDMode selects between North American modulation (BellCore 202) and ETS modulation (V.23). For on-hook Caller ID, it also selects between sending the FSK between the first and second ring pattern (northAmerican and duringRingingETS), Dual Tone Alert Signal (DtAsETS), after a Ring Pulse (rsAsETS) or, after a Line Reversal followed by a Dual Tone Alert Signal (lrAsETS)." DEFVAL { northAmerican } ::= {pktcSigDevConfigObjects 28 } pktcSigDevCIDFskAfterRing OBJECT-TYPE SYNTAX Integer32 (500..2000) Schell/Kumar/Channabasappa Expires April 2003 [Page 21] Internet Draft PacketCable Signaling MIB October 2002 UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " Determines the delay between the end of first ringing pattern and the transmission of the FSK containing the CallerID information. It is only used when pktcSigDevCIDMode is northAmerican or duringRingingETS." DEFVAL { 550 } ::= {pktcSigDevConfigObjects 29 } pktcSigDevCIDFskAfterDTAS OBJECT-TYPE SYNTAX Integer32 (45..500) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " Determines the delay between the Dual Tone Alert Signal (DT-AS) and the transmission of the FSK containing the Caller ID information. It is only used when pktcSigDevCIDMode is dtAsETS or lrAsETS." ::= {pktcSigDevConfigObjects 30 } pktcSigDevCIDRingAfterFSK OBJECT-TYPE SYNTAX Integer32 (200..500) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " Determines the delay between the complete transmission of the FSK containing the Caller ID information and the first ring pattern. It is only used when pktcSigDevCIDMode is dtAsETS, rpAsETS or lrAsETS." ::= {pktcSigDevConfigObjects 31 } pktcSigDevCIDDTASAfterLR OBJECT-TYPE SYNTAX Integer32 (100..655) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " Determines the delay between the end of the Line Reversal and Dual Tone Alert Signal (DT-AS). It is only used when pktcSigDevCIDMode is lrAsETS." ::= {pktcSigDevConfigObjects 32 } pktcSigDevRingCadenceTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigDevRingCadenceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " In V5.2, Cadence rings are defined by the telco governing body for each Schell/Kumar/Channabasappa Expires April 2003 [Page 22] Internet Draft PacketCable Signaling MIB October 2002 country. The MTA must be able to support various ranges of cadence patterns and cadence periods. The MTA will be able to support country specific provisioning of the cadence and idle period. There will be at most 3 on/off transitions per cadence period. Each cadence pattern will be assigned a unique value ranging 1-128 corresponding to the value sent by the LE SIGNAL message plus one. MTA will derive the cadence periods from the ring Cadence table entry as provisioned by the customer." ::= { pktcSigDevConfigObjects 33 } pktcSigDevRingCadenceEntry OBJECT-TYPE SYNTAX PktcSigDevRingCadenceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " Unique value ranging from 1 to 128 that corresponds to the value sent by the LE (plus one) based on country specific cadences, one row per cadence cycle. In any given system implementation for a particular country, it is anticipated that a small number of ring cadences will be in use. Thus, this table most likely will not be populated to its full 128-row size." INDEX { pktcSigDevRingCadenceIndex } ::= { pktcSigDevRingCadenceTable 1 } PktcSigDevRingCadenceEntry ::= SEQUENCE { pktcSigDevRingCadenceIndex Integer32, pktcSigDevRingCadence OCTET STRING } pktcSigDevRingCadenceIndex OBJECT-TYPE SYNTAX Integer32 (1..128) MAX-ACCESS not-accessible STATUS current DESCRIPTION " The table index equivalent to the country specific cadence (1 - 128)." ::= { pktcSigDevRingCadenceEntry 1 } pktcSigDevRingCadence OBJECT-TYPE SYNTAX OCTET STRING (SIZE(2..28)) MAX-ACCESS read-write STATUS current DESCRIPTION " This is the Ring Cadence Octet String. The first octet of the bit string represents the length in bits of the duration of the cadence. Each Bit after the first octet represents 50 ms and 1 represents ring and 0 represent silent. The first bit of the second octet is the first bit of the ring cadence. Only 216 Bits can be set total to represent 10800 ms of total cadence cycle." ::= { pktcSigDevRingCadenceEntry 2 } pktcSigDevStandardRingCadence OBJECT-TYPE SYNTAX OCTET STRING (SIZE(2..28)) MAX-ACCESS read-write STATUS current DESCRIPTION Schell/Kumar/Channabasappa Expires April 2003 [Page 23] Internet Draft PacketCable Signaling MIB October 2002 " This is the Ring Cadence Octet String for the standard ring. The first octet of the bit string represents the length in bits of the duration of the cadence Each Bit after the first octet represents 50 ms and 1 represents ring and 0 represent silent. The first bit of the second octet is the first bit of the ring cadence. Only 216 Bits can be set total to represent 10800 ms of total cadence cycle." ::= { pktcSigDevConfigObjects 34 } pktcSigDevRingSplashCadence OBJECT-TYPE SYNTAX OCTET STRING (SIZE(2..28)) MAX-ACCESS read-write STATUS current DESCRIPTION " This is the Ring Cadence Octet String for splash ring. The first octet of te bit string represents the length in bits of the duration of the cadence. Each Bit after the first octet represents 50 ms and 1 represents ring and 0 represent silent. The first bit of the second octet is the first bit of the ring cadence. Only 216 Bits can be set total to represent 10800 ms of total cadence cycle." ::= { pktcSigDevConfigObjects 35 } pktcSigDevToneTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigDevToneEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " The Tone Table defines the various tone operations." ::= { pktcSigDevConfigObjects 36 } pktcSigDevToneEntry OBJECT-TYPE SYNTAX PktcSigDevToneEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " Unique value ranging from 1 to 49 that will correspond to the different tone types that are being supported by the device. These tones can be provisioned based on country specific needs." INDEX { pktcSigDevToneType } ::= { pktcSigDevToneTable 1 } PktcSigDevToneEntry ::= SEQUENCE { pktcSigDevToneType INTEGER, pktcSigDevToneDbLevel Integer32, pktcSigDevToneFreqType INTEGER, pktcSigDevToneNumFrequencies Integer32, pktcSigDevToneFirstFrequency Integer32, pktcSigDevToneSecondFrequency Integer32, pktcSigDevToneThirdFrequency Integer32, pktcSigDevToneFourthFrequency Integer32, pktcSigDevToneNumOnOffTimes Integer32, pktcSigDevToneFirstToneOn Integer32, pktcSigDevToneFirstToneOff Integer32, pktcSigDevToneSecondToneOn Integer32, pktcSigDevToneSecondToneOff Integer32, Schell/Kumar/Channabasappa Expires April 2003 [Page 24] Internet Draft PacketCable Signaling MIB October 2002 pktcSigDevToneThirdToneOn Integer32, pktcSigDevToneThirdToneOff Integer32, pktcSigDevToneFourthToneOn Integer32, pktcSigDevToneFourthToneOff Integer32, pktcSigDevToneWholeToneRepeatCount Integer32, pktcSigDevToneSteady TruthValue } pktcSigDevToneType OBJECT-TYPE SYNTAX INTEGER { dtmf0(0), dtmf1(1), dtmf2(2), dtmf3(3), dtmf4(4), dtmf5(5), dtmf6(6), dtmf7(7), dtmf8(8), dtmf9(9), dtmfToneStar(10), dtmfTonePound(11), dtmfA(12), dtmfB(13), dtmfC(14), dtmfD(15), busy(16), confirmation(17), dial(18), messageWaiting(19), offHookWarning(20), ringBack(21), reOrder(22), stutterdial(23), loopback(24), callWaiting1(25), callWaiting2(26), callWaiting3(27), callWaiting4(28), alertingSignal(29), testTone(30), specialDial(31), specialInfo(32), release(33), congestion(34), userDefinedOne(35) } MAX-ACCESS read-only STATUS current DESCRIPTION " This defines the type of tone being accessed." ::={pktcSigDevToneEntry 1 } Schell/Kumar/Channabasappa Expires April 2003 [Page 25] Internet Draft PacketCable Signaling MIB October 2002 pktcSigDevToneDbLevel OBJECT-TYPE SYNTAX Integer32 (-60..4) UNITS "dbm" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the decibel level at which tones could be generated." DEFVAL { -4 } ::={pktcSigDevToneEntry 2 } pktcSigDevToneFreqType OBJECT-TYPE SYNTAX INTEGER { allFrequencies (1), singleFrequecySequence (2), dualFrequencySequence (3), allFrequenciesModulated (4) } MAX-ACCESS read-write STATUS current DESCRIPTION " This object describes how the frequencies are applied. allFrequencies indicates all frequences specifed by btiToneNumFrequencies are mixed to form a single tone. The tone is then applied in sequence using the number of on/off times specified in btiToneNumOnOffTimes. singleFrequecySequence indicates all frequencies specified by btiToneNumFrequencies are applied in sequence using the corresponding frequency number on/off time (eg. btiToneFirstFrequency uses btiToneFirstToneOn and btiToneFirstToneOff, btiToneSecondFrequency uses btiToneSecondToneOn and btiToneSecondToneOff, ... ). For this tone type btiToneNumFrequencies MUST equal btiToneNumOnOffTimes. dualFrequencySequence indicates two pairs of frequencies are mixed to form two sequenced tones. The first and second frequency are mixed to form tone one and are applied using btiToneFirstToneOn and btiToneFirstToneOff. The third and forth frequency are mixed to form tone two and are applied using btiToneSecondToneOn and btiToneSecondToneOff. For this tone type btiToneNumFrequencies MUST equal 4 and btiToneNumOnOffTimes MUST equal 2 allFrequenciesModulated indicates all frequences specifed by btiToneNumFrequencies are modulated to form a single tone. The tone is then applied in sequence using the number of on/off times specified in btiToneNumOnOffTimes." DEFVAL { allFrequencies } ::={ pktcSigDevToneEntry 3 } pktcSigDevToneNumFrequencies OBJECT-TYPE SYNTAX Integer32 (1..4) Schell/Kumar/Channabasappa Expires April 2003 [Page 26] Internet Draft PacketCable Signaling MIB October 2002 MAX-ACCESS read-write STATUS current DESCRIPTION " Specifies the number of frequencies specified in the table entry." DEFVAL { 1 } ::={pktcSigDevToneEntry 4} pktcSigDevToneFirstFrequency OBJECT-TYPE SYNTAX Integer32 (0..4000) UNITS "Hertz" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the first frequency at which the tones could be generated in a multiple frequency tone." ::={pktcSigDevToneEntry 5} pktcSigDevToneSecondFrequency OBJECT-TYPE SYNTAX Integer32 (0..4000) UNITS "Hertz" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the second frequency at which the tones could be generated in a ultiple frequency tone." ::={pktcSigDevToneEntry 6} pktcSigDevToneThirdFrequency OBJECT-TYPE SYNTAX Integer32 (0..4000) UNITS "Hertz" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the third frequency at which the tones could be generated." ::={pktcSigDevToneEntry 7} pktcSigDevToneFourthFrequency OBJECT-TYPE SYNTAX Integer32 (0..4000) UNITS "Hertz" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the fourth frequency at which the tones could be generated." ::={pktcSigDevToneEntry 8} pktcSigDevToneNumOnOffTimes OBJECT-TYPE SYNTAX Integer32 (1..4) MAX-ACCESS read-write STATUS current DESCRIPTION Schell/Kumar/Channabasappa Expires April 2003 [Page 27] Internet Draft PacketCable Signaling MIB October 2002 " Specifies the number of on/off times specified in the table entry." DEFVAL { 1 } ::={pktcSigDevToneEntry 9} pktcSigDevToneFirstToneOn OBJECT-TYPE SYNTAX Integer32 (0..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the first tone interval." ::={ pktcSigDevToneEntry 10} pktcSigDevToneFirstToneOff OBJECT-TYPE SYNTAX Integer32 (0..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the first idle interval." ::={ pktcSigDevToneEntry 11 } pktcSigDevToneSecondToneOn OBJECT-TYPE SYNTAX Integer32 (0..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the second tone interval." ::={ pktcSigDevToneEntry 12 } pktcSigDevToneSecondToneOff OBJECT-TYPE SYNTAX Integer32 (0..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the second idle interval." ::={ pktcSigDevToneEntry 13 } pktcSigDevToneThirdToneOn OBJECT-TYPE SYNTAX Integer32 (0..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the third tone interval." ::={ pktcSigDevToneEntry 14 } pktcSigDevToneThirdToneOff OBJECT-TYPE SYNTAX Integer32 (0..5000) Schell/Kumar/Channabasappa Expires April 2003 [Page 28] Internet Draft PacketCable Signaling MIB October 2002 UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the third idle interval." ::={ pktcSigDevToneEntry 15 } pktcSigDevToneFourthToneOn OBJECT-TYPE SYNTAX Integer32 (0..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the fourth tone interval." ::={ pktcSigDevToneEntry 16 } pktcSigDevToneFourthToneOff OBJECT-TYPE SYNTAX Integer32 (0..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This is the Fourth idle interval." ::={ pktcSigDevToneEntry 17 } pktcSigDevToneWholeToneRepeatCount OBJECT-TYPE SYNTAX Integer32 (0..5000) MAX-ACCESS read-write STATUS current DESCRIPTION " This is the repeat count, which signifies how many times to repeat the entire on-off sequence." ::={ pktcSigDevToneEntry 18 } pktcSigDevToneSteady OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION " This is the steady tone. Set to true to continue the last tone after on-off sequence." ::={ pktcSigDevToneEntry 19 } -- -- The following Table will provide endpoint configuration -- information that is common to all signaling Protocols. -- Currently only the signaling index is present in an effort -- not to deprecate any MIB objects. -- Schell/Kumar/Channabasappa Expires April 2003 [Page 29] Internet Draft PacketCable Signaling MIB October 2002 pktcSigEndPntConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigEndPntConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This table describes the packet cable EndPoint slected signaling type. The number of entries in this table represents the number of provisioned end points. For each conceptual row of pktcSigEndPntConfigTable Defined, an associated row MUST be defined in one on the specific signaling tables such as pktcNcsEndPntConfigTable." ::= { pktcSigEndPntConfigObjects 1 } pktcSigEndPntConfigEntry OBJECT-TYPE SYNTAX PktcSigEndPntConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " Entries in pktcSigEndPntConfigTable - Each entry describes what signaling type a particular enpoint uses." INDEX { ifIndex } ::= { pktcSigEndPntConfigTable 1 } PktcSigEndPntConfigEntry ::= SEQUENCE { pktcSigEndPntCapabilityIndex Integer32 } pktcSigEndPntCapabilityIndex OBJECT-TYPE SYNTAX Integer32 (1..16383) MAX-ACCESS read-create STATUS current DESCRIPTION " The associated index value in the pktcSigCapablityTable." ::= { pktcSigEndPntConfigEntry 1 } -- -- The NCS End Point Config Table is used to define attributes that -- are specific to connection EndPoints. -- -- pktcNcsEndPntConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcNcsEndPntConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This table describes the PacketCable(tm) NCS EndPoint configuration. The number of entries in this table represents the number of provisioned end points." ::= { pktcNcsEndPntConfigObjects 1 } Schell/Kumar/Channabasappa Expires April 2003 [Page 30] Internet Draft PacketCable Signaling MIB October 2002 pktcNcsEndPntConfigEntry OBJECT-TYPE SYNTAX PktcNcsEndPntConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " List of attributes for a single packet cable endpoint interface." INDEX { ifIndex } ::= { pktcNcsEndPntConfigTable 1 } PktcNcsEndPntConfigEntry ::= SEQUENCE { pktcNcsEndPntConfigCallAgentId SnmpAdminString, pktcNcsEndPntConfigCallAgentUdpPort InetPortNumber, pktcNcsEndPntConfigPartialDialTO Integer32, pktcNcsEndPntConfigCriticalDialTO Integer32, pktcNcsEndPntConfigBusyToneTO Integer32, pktcNcsEndPntConfigDialToneTO Integer32, pktcNcsEndPntConfigMessageWaitingTO Integer32, pktcNcsEndPntConfigOffHookWarnToneTO Integer32, pktcNcsEndPntConfigRingingTO Integer32, pktcNcsEndPntConfigRingBackTO Integer32, pktcNcsEndPntConfigReorderToneTO Integer32, pktcNcsEndPntConfigStutterDialToneTO Integer32, pktcNcsEndPntConfigTSMax Integer32, pktcNcsEndPntConfigMax1 Integer32, pktcNcsEndPntConfigMax2 Integer32, pktcNcsEndPntConfigMax1QEnable TruthValue, pktcNcsEndPntConfigMax2QEnable TruthValue, pktcNcsEndPntConfigMWD Integer32, pktcNcsEndPntConfigTdinit Integer32, pktcNcsEndPntConfigTdmin Integer32, pktcNcsEndPntConfigTdmax Integer32, pktcNcsEndPntConfigRtoMax Integer32, pktcNcsEndPntConfigRtoInit Integer32, pktcNcsEndPntConfigLongDurationKeepAlive Integer32, pktcNcsEndPntConfigThist Integer32, pktcNcsEndPntConfigStatus RowStatus, pktcNcsEndPntConfigCallWaitingMaxRep Integer32, pktcNcsEndPntConfigCallWaitingDelay Integer32, pktcNcsEndPntStatusCallIpAddressType InetAddressType, pktcNcsEndPntStatusCallIpAddress InetAddress, pktcNcsEndPntStatusError INTEGER, pktcNcsEndPntConfigMinHookFlash Integer32, pktcNcsEndPntConfigMaxHookFlash Integer32, pktcNcsEndPntConfigPulseDialInterdigitTime Integer32, pktcNcsEndPntConfigPulseDialMinMakeTime Integer32, pktcNcsEndPntConfigPulseDialMaxMakeTime Integer32, pktcNcsEndPntConfigPulseDialMinBreakTime Integer32, pktcNcsEndPntConfigPulseDialMaxBreakTime Integer32, pktcNcsEndPntConfigNomJitterBufferSize Integer32, pktcNcsEndPntConfigMaxJitterBufferSize Integer32, pktcNcsEndPntConfigOnHookDebounce Integer32, Schell/Kumar/Channabasappa Expires April 2003 [Page 31] Internet Draft PacketCable Signaling MIB October 2002 pktcNcsEndPntConfigOffHookDebounce Integer32, pktcNcsEndPntConfigTxGain Integer32, pktcNcsEndPntConfigRxGain Integer32 } pktcNcsEndPntConfigCallAgentId OBJECT-TYPE SYNTAX SnmpAdminString(SIZE (3..255)) MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains a string indicating the call agent name. (ex: ca@abc.def.com). The call agent name after the @ character must be a fully qualified domain name and have a corresponding pktcMtaDevCmsFqdn entry in pktcMtaDevCmsTable" ::= { pktcNcsEndPntConfigEntry 1 } pktcNcsEndPntConfigCallAgentUdpPort OBJECT-TYPE SYNTAX InetPortNumber (1025..65535) MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the call agent User Datagram Protocol (UDP) receive port that is being used for this instance of call signaling, i.e. the default port on which the call agent will receive NCS signaling from the gateway." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 2727 } ::= { pktcNcsEndPntConfigEntry 2 } pktcNcsEndPntConfigPartialDialTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains maximum value of the partial dial time out." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 16 } ::= { pktcNcsEndPntConfigEntry 3 } pktcNcsEndPntConfigCriticalDialTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the maximum value of the critical dial time out." REFERENCE Schell/Kumar/Channabasappa Expires April 2003 [Page 32] Internet Draft PacketCable Signaling MIB October 2002 " Refer to Packetcable NCS specification [17]" DEFVAL { 4 } ::= { pktcNcsEndPntConfigEntry 4 } pktcNcsEndPntConfigBusyToneTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the timeout value for busy tone." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 30 } ::= { pktcNcsEndPntConfigEntry 5 } pktcNcsEndPntConfigDialToneTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the timeout value for dial tone." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 16 } ::= { pktcNcsEndPntConfigEntry 6 } pktcNcsEndPntConfigMessageWaitingTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the timeout value for message waiting indicator." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 16 } ::= { pktcNcsEndPntConfigEntry 7 } pktcNcsEndPntConfigOffHookWarnToneTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains timeout value for off hook Warning tone" REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 0 } ::= { pktcNcsEndPntConfigEntry 8 } Schell/Kumar/Channabasappa Expires April 2003 [Page 33] Internet Draft PacketCable Signaling MIB October 2002 pktcNcsEndPntConfigRingingTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the timeout value for ringing." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 180 } ::= { pktcNcsEndPntConfigEntry 9 } pktcNcsEndPntConfigRingBackTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the timeout value for ring back." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 180 } ::= { pktcNcsEndPntConfigEntry 10 } pktcNcsEndPntConfigReorderToneTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the timeout value for reorder tone." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 30 } ::= { pktcNcsEndPntConfigEntry 11 } pktcNcsEndPntConfigStutterDialToneTO OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains timeout value for stutter dial tone." REFERENCE "Refer to Packetcable NCS specification [17]" DEFVAL { 16 } ::= { pktcNcsEndPntConfigEntry 12 } pktcNcsEndPntConfigTSMax OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current Schell/Kumar/Channabasappa Expires April 2003 [Page 34] Internet Draft PacketCable Signaling MIB October 2002 DESCRIPTION " This object contains the max time in seconds since the sending of the initial datagram." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 20 } ::= { pktcNcsEndPntConfigEntry 13 } pktcNcsEndPntConfigMax1 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the suspicious error threshold for signaling messages." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 5 } ::= { pktcNcsEndPntConfigEntry 14 } pktcNcsEndPntConfigMax2 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the disconnect error threshold for signaling messages." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 7 } ::= { pktcNcsEndPntConfigEntry 15 } pktcNcsEndPntConfigMax1QEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION " This object enables/disables the Max1 Domain Name Server (DNS) query operation when Max1 expires." DEFVAL { true } ::= { pktcNcsEndPntConfigEntry 16 } pktcNcsEndPntConfigMax2QEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION " This object enables/disables the Max2 DNS query operation when Max2 expires." DEFVAL { true } ::= { pktcNcsEndPntConfigEntry 17 } Schell/Kumar/Channabasappa Expires April 2003 [Page 35] Internet Draft PacketCable Signaling MIB October 2002 pktcNcsEndPntConfigMWD OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " Maximum Waiting Delay (MWD) contains the maximum number of seconds a MTA waits after a restart." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 600 } ::= { pktcNcsEndPntConfigEntry 18 } pktcNcsEndPntConfigTdinit OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the initial number of seconds a MTA waits after a disconnect." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 15 } ::= { pktcNcsEndPntConfigEntry 19 } pktcNcsEndPntConfigTdmin OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the minimum number of seconds a MTA waits after a disconnect." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 15 } ::= { pktcNcsEndPntConfigEntry 20 } pktcNcsEndPntConfigTdmax OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the maximum number of seconds a MTA waits after a disconnect." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 600 } Schell/Kumar/Channabasappa Expires April 2003 [Page 36] Internet Draft PacketCable Signaling MIB October 2002 ::= { pktcNcsEndPntConfigEntry 21 } pktcNcsEndPntConfigRtoMax OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the maximum number of seconds for the retansmission timer." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 4 } ::= { pktcNcsEndPntConfigEntry 22 } pktcNcsEndPntConfigRtoInit OBJECT-TYPE SYNTAX Integer32 UNITS "milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the initial number of seconds for the retransmission timer." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 200 } ::= { pktcNcsEndPntConfigEntry 23 } pktcNcsEndPntConfigLongDurationKeepAlive OBJECT-TYPE SYNTAX Integer32 UNITS "minutes" MAX-ACCESS read-create STATUS current DESCRIPTION " Specifies a timeout value in minutes for sending long duration call notification message." REFERENCE " Refer to Packetcable NCS specification [17]" DEFVAL { 60 } ::= { pktcNcsEndPntConfigEntry 24 } pktcNcsEndPntConfigThist OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " Timeout period in seconds before no response is declared." REFERENCE "Refer to Packetcable NCS specification [17]" DEFVAL { 30 } Schell/Kumar/Channabasappa Expires April 2003 [Page 37] Internet Draft PacketCable Signaling MIB October 2002 ::= { pktcNcsEndPntConfigEntry 25 } pktcNcsEndPntConfigStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the Row Status associated with the pktsNcsEndPntTable." ::= { pktcNcsEndPntConfigEntry 26 } pktcNcsEndPntConfigCallWaitingMaxRep OBJECT-TYPE SYNTAX Integer32 (0..10) MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the maximum number of repetitions of the call waiting tone that the MTA will play from a single CMS request. A value of zero (0) can be used if the CMS is to control the repetitions of the call waiting tone." DEFVAL { 1 } ::= { pktcNcsEndPntConfigEntry 27 } pktcNcsEndPntConfigCallWaitingDelay OBJECT-TYPE SYNTAX Integer32 (1..100) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the delay between repretitions of the call waiting tone that the MTA will play from a single CMS request." DEFVAL { 10 } ::= { pktcNcsEndPntConfigEntry 28 } pktcNcsEndPntStatusCallIpAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION " This object contains the type of Internet address of the CMS currently being used for this endpoint." ::= { pktcNcsEndPntConfigEntry 44 } pktcNcsEndPntStatusCallIpAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION " This object contains the Internet address of the CMS currently being used for this endpoint. Schell/Kumar/Channabasappa Expires April 2003 [Page 38] Internet Draft PacketCable Signaling MIB October 2002 This Internet address is used to create the appropriate security association." ::= { pktcNcsEndPntConfigEntry 29 } pktcNcsEndPntStatusError OBJECT-TYPE SYNTAX INTEGER { operational (1), noSecurityAssociation (2), disconnected (3) } MAX-ACCESS read-only STATUS current DESCRIPTION " This object contains the error status of the interface: The 'operational' state indicates that all operations necessary to put the line in service have occurred. The 'noSecurityAssociation' status indicates that no security association yet exists for this endpoint. The 'disconnected' status indicates that the Security Association has been established and the NCS signaling Software is process of establishing the NCS signaling Link via an RSIP exchange." ::= { pktcNcsEndPntConfigEntry 30 } pktcNcsEndPntConfigMinHookFlash OBJECT-TYPE SYNTAX Integer32 (1..1000) UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This is the minimum time a line needs to be on hook for a valid hook flash." DEFVAL { 300 } ::= { pktcNcsEndPntConfigEntry 31 } pktcNcsEndPntConfigMaxHookFlash OBJECT-TYPE SYNTAX Integer32 (1..1800) UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This is the maximum time a line needs to be on hook for a valid hook flash." DEFVAL { 1000 } ::= { pktcNcsEndPntConfigEntry 32 } pktcNcsEndPntConfigPulseDialInterdigitTime OBJECT-TYPE SYNTAX Integer32 (100..1500) UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION Schell/Kumar/Channabasappa Expires April 2003 [Page 39] Internet Draft PacketCable Signaling MIB October 2002 " This is the pulse dial inter-digit timeout." DEFVAL { 100 } ::= { pktcNcsEndPntConfigEntry 33 } pktcNcsEndPntConfigPulseDialMinMakeTime OBJECT-TYPE SYNTAX Integer32 (1..200) UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This is the minimum make pulse width for the dial pulse." DEFVAL { 25 } ::= { pktcNcsEndPntConfigEntry 34 } pktcNcsEndPntConfigPulseDialMaxMakeTime OBJECT-TYPE SYNTAX Integer32 (1..200) UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This is the maximum make pulse width for the dial pulse." DEFVAL { 55 } ::= { pktcNcsEndPntConfigEntry 35 } pktcNcsEndPntConfigPulseDialMinBreakTime OBJECT-TYPE SYNTAX Integer32 (1..200) UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This is the minimum break pulse width for the dial pulse." DEFVAL { 45 } ::= { pktcNcsEndPntConfigEntry 36 } pktcNcsEndPntConfigPulseDialMaxBreakTime OBJECT-TYPE SYNTAX Integer32 (1..200) UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This is the maximum break pulse width for the dial pulse." DEFVAL { 75 } ::= { pktcNcsEndPntConfigEntry 37 } pktcNcsEndPntConfigNomJitterBufferSize OBJECT-TYPE SYNTAX Integer32 UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " The current setting for the nominal amount of jitter the bti can compensate." Schell/Kumar/Channabasappa Expires April 2003 [Page 40] Internet Draft PacketCable Signaling MIB October 2002 ::= { pktcNcsEndPntConfigEntry 38 } pktcNcsEndPntConfigMaxJitterBufferSize OBJECT-TYPE SYNTAX Integer32 UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " The current setting for the maximum amount of jitter the bti can compensate ." ::= { pktcNcsEndPntConfigEntry 39 } pktcNcsEndPntConfigOnHookDebounce OBJECT-TYPE SYNTAX Integer32 (1..1000) UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " The length of the on-hook debounce." DEFVAL { 200 } ::= { pktcNcsEndPntConfigEntry 40 } pktcNcsEndPntConfigOffHookDebounce OBJECT-TYPE SYNTAX Integer32 (1..1000) UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " The length of the off hook debounce." DEFVAL { 100 } ::= { pktcNcsEndPntConfigEntry 41 } pktcNcsEndPntConfigTxGain OBJECT-TYPE SYNTAX Integer32 (-14..14) UNITS "dB" MAX-ACCESS read-create STATUS current DESCRIPTION " The per line transmitter gain." DEFVAL { 0 } ::= { pktcNcsEndPntConfigEntry 42 } pktcNcsEndPntConfigRxGain OBJECT-TYPE SYNTAX Integer32 (-14..14) UNITS "dB" MAX-ACCESS read-create STATUS current DESCRIPTION " The per line receiver gain." DEFVAL { 0 } ::= { pktcNcsEndPntConfigEntry 43 } Schell/Kumar/Channabasappa Expires April 2003 [Page 41] Internet Draft PacketCable Signaling MIB October 2002 -- -- notification group is for future extension. -- pktcSigNotification OBJECT IDENTIFIER ::= { pktcSigMib 2 } pktcSigConformance OBJECT IDENTIFIER ::= { pktcSigMib 3 } pktcSigCompliances OBJECT IDENTIFIER ::= { pktcSigConformance 1 } pktcSigGroups OBJECT IDENTIFIER ::= { pktcSigConformance 2 } -- compliance statements pktcSigBasicCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION " The compliance statement for devices that implement Signaling on the MTA." MODULE -- pktcSigMib -- unconditionally mandatory groups MANDATORY-GROUPS { pktcSigGroup } GROUP pktcNcsGroup DESCRIPTION " This group is mandatory for any MTA implementing NCS signaling" ::={ pktcSigCompliances 1 } -- units of conformance pktcSigGroup OBJECT-GROUP OBJECTS { pktcSigDevCodecType, pktcSigDevCodecMax, pktcSigDevEchoCancellation, pktcSigDevSilenceSuppression, pktcSigDevConnectionMode, pktcSigDevR0Cadence, pktcSigDevR6Cadence, pktcSigDevR7Cadence, pktcSigDefCallSigTos, pktcSigDefMediaStreamTos, pktcSigTosFormatSelector, pktcSignalingType, pktcSignalingVersion, pktcSignalingVendorExtension, pktcSigEndPntCapabilityIndex, pktcSigDefNcsReceiveUdpPort, pktcSigServiceClassNameUS, pktcSigServiceClassNameDS, Schell/Kumar/Channabasappa Expires April 2003 [Page 42] Internet Draft PacketCable Signaling MIB October 2002 pktcSigServiceClassNameMask, pktcSigNcsServiceFlowState, pktcSigDevR1Cadence, pktcSigDevR2Cadence, pktcSigDevR3Cadence, pktcSigDevR4Cadence, pktcSigDevR5Cadence, pktcSigDevRgCadence, pktcSigDevRsCadence, pktcSigDevRtCadence } STATUS current DESCRIPTION "Group of objects for the common portion of the PacketCable Signaling MIB." ::= { pktcSigGroups 1 } pktcNcsGroup OBJECT-GROUP OBJECTS { pktcNcsEndPntConfigCallAgentId, pktcNcsEndPntConfigCallAgentUdpPort, pktcNcsEndPntConfigPartialDialTO, pktcNcsEndPntConfigCriticalDialTO, pktcNcsEndPntConfigBusyToneTO, pktcNcsEndPntConfigDialToneTO, pktcNcsEndPntConfigMessageWaitingTO, pktcNcsEndPntConfigOffHookWarnToneTO, pktcNcsEndPntConfigRingingTO, pktcNcsEndPntConfigRingBackTO, pktcNcsEndPntConfigReorderToneTO, pktcNcsEndPntConfigStutterDialToneTO, pktcNcsEndPntConfigTSMax, pktcNcsEndPntConfigMax1, pktcNcsEndPntConfigMax2, pktcNcsEndPntConfigMax1QEnable, pktcNcsEndPntConfigMax2QEnable, pktcNcsEndPntConfigMWD, pktcNcsEndPntConfigTdinit, pktcNcsEndPntConfigTdmin, pktcNcsEndPntConfigTdmax, pktcNcsEndPntConfigRtoMax, pktcNcsEndPntConfigRtoInit, pktcNcsEndPntConfigLongDurationKeepAlive, pktcNcsEndPntConfigThist, pktcNcsEndPntConfigStatus, pktcNcsEndPntConfigCallWaitingMaxRep, pktcNcsEndPntConfigCallWaitingDelay, pktcNcsEndPntStatusCallIpAddressType, pktcNcsEndPntStatusCallIpAddress, pktcNcsEndPntStatusError } STATUS current Schell/Kumar/Channabasappa Expires April 2003 [Page 43] Internet Draft PacketCable Signaling MIB October 2002 DESCRIPTION "Group of objects for the NCS portion of the PacketCable Signaling MIB. This is mandatory for NCS signaling." ::= { pktcSigGroups 2 } pktcInternationalGroup OBJECT-GROUP OBJECTS { pktcNcsEndPntConfigMinHookFlash, pktcNcsEndPntConfigMaxHookFlash, pktcNcsEndPntConfigNomJitterBufferSize, pktcNcsEndPntConfigMaxJitterBufferSize, pktcNcsEndPntConfigOnHookDebounce, pktcNcsEndPntConfigOffHookDebounce, pktcNcsEndPntConfigTxGain, pktcNcsEndPntConfigRxGain, pktcNcsEndPntConfigPulseDialInterdigitTime, pktcNcsEndPntConfigPulseDialMinMakeTime, pktcNcsEndPntConfigPulseDialMaxMakeTime, pktcNcsEndPntConfigPulseDialMinBreakTime, pktcNcsEndPntConfigPulseDialMaxBreakTime, pktcSigDevRingCadence, pktcSigDevStandardRingCadence, pktcSigDevRingSplashCadence, pktcSigDevCIDMode, pktcSigDevCIDFskAfterRing, pktcSigDevCIDFskAfterDTAS, pktcSigDevCIDRingAfterFSK, pktcSigDevCIDDTASAfterLR, pktcSigPowerRingFrequency, pktcSigPCMCoding, pktcSigPulseSignalDuration, pktcSigPulseSignalType, pktcSigPulseSignalDbLevel, pktcSigPulseSignalFrequency, pktcSigPulseSignalRepeatCount, pktcSigPulseSignalPauseDuration, pktcSigDevToneType, pktcSigDevToneDbLevel, pktcSigDevToneFreqType, pktcSigDevToneNumFrequencies, pktcSigDevToneFirstFrequency, pktcSigDevToneSecondFrequency, pktcSigDevToneThirdFrequency, Schell/Kumar/Channabasappa Expires April 2003 [Page 44] Internet Draft PacketCable Signaling MIB October 2002 pktcSigDevToneFourthFrequency, pktcSigDevToneNumOnOffTimes, pktcSigDevToneFirstToneOn, pktcSigDevToneFirstToneOff, pktcSigDevToneSecondToneOn, pktcSigDevToneSecondToneOff, pktcSigDevToneThirdToneOn, pktcSigDevToneThirdToneOff, pktcSigDevToneFourthToneOn, pktcSigDevToneFourthToneOff, pktcSigDevToneWholeToneRepeatCount, pktcSigDevToneSteady } STATUS current DESCRIPTION " Group of objects that extend the behavior of existing objects to support operations in the widest possible set of international marketplaces. Note that many of these objects represent a superset of behaviors described in other objects within this MIB Module. In such cases, it is left to manufacturers to determine whether to support both objects in the same device." ::= { pktcSigGroups 3 } END 5. Acknowledgments This document is a production of the PacketCable Working Group. The current editors wish to express gratitude to: Angela Lyda Arris Interactive Sasha Medvinsky Motorola Roy Spitzer Telogy Networks, Inc. Rick Vetter Motorola Itay Sherman Texas Instruments Klaus Hermanns Cisco Systems Eugene Nechamkin Broadcom Corp Matt A. Osman CableLabs Jean-Francois Mule CableLabs 6. References [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [2] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. Schell/Kumar/Channabasappa Expires April 2003 [Page 45] Internet Draft PacketCable Signaling MIB October 2002 [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. and J. Schoenwaelder, "Structure of Management Information for Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [6] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [7] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Management Protocol", STD 15, RFC 1157, May 1990. [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 2572, April 1999. [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [14] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, April 1999. [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [17] Packetcable Network-Based Call Signaling protocol Specification PKT-SP-EC-MGCP-IO4-011221. [18] Bradner, S., "The Internet Standards Process, Revision 3", Schell/Kumar/Channabasappa Expires April 2003 [Page 46] Internet Draft PacketCable Signaling MIB October 2002 RFC 2026, October 1996. [19] ETSI TS 101 909-4:"Access and Terminals (AT); Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services; Part 4: Network Call Signalling Protocol". [20] ETSI TS 101 909-9:"Access and Terminals (AT); Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services; Part 9: IPCablecom Network Call Signalling (NCS) MIB Requirements". [21] EN 300 001 V1.5.1 (1998-10):"European Standard (Telecommunications series) Attachments to Public Switched Telephone Network (PSTN); General technical requirements for equipment connected to an analogue subscriber interface in the PSTN; Chapter 3: Ringing signal characteristics (national deviations are in Table 3.1.1)". 7. Security Considerations This MIB relates to a system which will provide metropolitan public telephony service. As such, improper manipulation of the objects represented by this MIB may result in random behavior of MTA. Improper manipulation of certain tables can result in failure to get telephony service from client(MTA) device. 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 [12] and the View- based Access Control Model RFC 2575 [15] 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. 8. 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 Schell/Kumar/Channabasappa Expires April 2003 [Page 47] Internet Draft PacketCable Signaling MIB October 2002 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 implementers 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 that may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 9. Authors' Addresses Charles Schell Motorola BCS/IPNS 101 Tournament Drive, Bldg. 3 Horsham, PA 19044, USA +1 215-323-1145 cschell@motorola.com Satish Kumar Mudugere Eswaraiah Texas Instruments India (P) Ltd., Golf view, Wind Tunnel Road Murugesh Palya Bangalore - - 560 017, INDIA +91 80 5269451 satish.kumar@ti.com Sumanth Channabasappa Alopa Networks Inc 248, McCaslin Bvld #101, Louisville, Colorado - 80027 U.S.A. +1 303 604 6595 Sumanth@alopa.com 10. Full Copyright Statement Copyright (C) The Internet Society (2002). All Rights Reserved. This document and translations of it may be copied and furnished to Schell/Kumar/Channabasappa Expires April 2003 [Page 48] Internet Draft PacketCable Signaling MIB October 2002 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. Schell/Kumar/Channabasappa Expires April 2003 [Page 49]