--- 1/draft-ietf-ipcdn-pktc-signaling-08.txt 2006-02-04 17:15:04.000000000 +0100 +++ 2/draft-ietf-ipcdn-pktc-signaling-09.txt 2006-02-04 17:15:04.000000000 +0100 @@ -1,84 +1,80 @@ + INTERNET-DRAFT Gordon Beacham Motorola, Inc. - draft-ietf-ipcdn-pktc-signaling-08.txt Satish Kumar + draft-ietf-ipcdn-pktc-signaling-09.txt Satish Kumar Texas Instruments Sumanth Channabasappa - CableLabs, Inc. - Expires: February 2005 August 2005 + CableLabs(R) + Expires: March 2006 September 2005 Network-Based Call Signaling (NCS) Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs) Status of this Memo By submitting this Internet-Draft, each author represents that any - applicable patent or other Intellectual Property Rights (IPR) claims - of which he or she is aware have been or will be disclosed, and any - of which he or she becomes aware will be disclosed, in accordance - with Section 6 of RFC 3668. + applicable patent or other IPR claims of which he or she is aware + have been or will be disclosed, and any of which he or she becomes + aware will be disclosed, in accordance with Section 6 of BCP 79. 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.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html -Copyright Notice - - Copyright (C) The Internet Society (2005). All Rights Reserved. - 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 provides a common data and format representation for PacketCable and IPCablecom compliant Multimedia Terminal Adapter devices. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2. The set of objects are consistent with the SNMP framework and existing SNMP standards. Table of Contents - - 1. The Internet-Standard Management Framework...................23 - 2. Introduction.................................................23 - 3. Terminology...................................................3 - 3.1 MTA......................................................34 - 3.2 Endpoint.................................................34 - 3.3 L Line Package............................................4 - 3.4 E Line Package............................................4 - 4. Overview......................................................4 - 4.1 Structure of the MIB......................................5 - 4.2 pktcSigDevConfigObjects...................................5 - 4.3 pktcSigNotification.......................................7 - 4.4 pktcSigConformance........................................7 - 5. Definitions..................................................78 - 6. Acknowledgments............................................5662 - 7. Security Considerations....................................5662 - 8. IANA Considerations........................................5864 - 9. Normative References.......................................5864 - 10. Informative References....................................6065 - Authors' Addresses............................................6166 - Disclaimer of validity........................................6167 - Full Copyright Statement......................................6267 + 1. The Internet-Standard Management Framework..................2 + 2. Introduction............................................2 + 3. Terminology.............................................3 + 3.1 MTA................................................3 + 3.2 Endpoint............................................3 + 3.3 L Line Package.......................................4 + 3.4 E Line Package.......................................4 + 4. Overview...............................................4 + 4.1 Structure of the MIB.................................5 + 4.2 pktcSigDevConfigObjects...............................5 + 4.3 pktcSigNotification..................................7 + 4.4 pktcSigConformance...................................7 + 5. Definitions.............................................7 + 6. Examples..............................................55 + 7. Acknowledgments........................................57 + 8. Security Considerations.................................57 + 9. IANA Considerations.....................................59 + 10. Normative References...................................59 + 11. Informative References.................................61 + Authors' Addresses........................................62 + Disclaimer of validity.....................................62 + Full Copyright Statement...................................63 1. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). @@ -86,27 +82,27 @@ Structure of Management Information (SMI). This memo specifies a MIBmodule that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 2. Introduction A multimedia terminal adapter (MTA) is used to deliver broadband Internet, data, and/or voice access jointly with telephony service to a subscriber's or customer's premises using a cable network - infrastructure. A MTA is normally installed at the customer's or + infrastructure. An MTA is normally installed at the customer's or subscriber's premises, and it is coupled to a multiple system operator (MSO) using a hybrid fiber coax (HFC) access network. - A MTA is provisioned by the MSO for broadband Internet, data, and/or - voice service. For more information on MTA provisioning refer to - [PKT-SP-PROV] and [PKT-SP-MIB-MTA]. MTA devices include one or more + An MTA is provisioned by the MSO for broadband Internet, data, + and/or voice service. For more information on MTA provisioning refer + to [PKT-SP-PROV] and [RFCXYZ]. MTA devices include one or more endpoints (e.g., telephone ports) which receive call signaling information to establish ring cadence, and codecs used for providing telephony service. For more information on call signaling refer to [PKT-SP-MGCP] and [RFC3435]. For more information on codecs refer to [PKT-SP-CODEC]. Telephone systems are typically very complex and often have a wide distribution. It is therefore important for management systems to support MTAs from multiple vendors at the same time, including those from multiple countries. This MIB module provides objects suitable @@ -120,33 +116,34 @@ "OPTIONAL", when used in the guidelines in this memo, are to be interpreted as described in RFC 2119 [RFC2119]. The terms "MIB module" and "information module" are used interchangeably in this memo. As used here, both terms refer to any of the three types of information modules defined in Section 3 of RFC 2578 [RFC2578]. 3.1 MTA - A MTA is a PacketCable or IPCablecom compliant device providing + An MTA is a PacketCable or IPCablecom compliant device providing telephony services over a cable or hybrid system used to deliver video signals to a community. It contains an interface to endpoints, a network interface, codecs, and all signaling and encapsulation functions required for Voice over IP transport, call signaling, and - Quality of Service signaling. A MTA can be an embedded or a - standalone device. An Embedded MTA (E-MTA) is a MTA device + Quality of Service signaling. An MTA can be an embedded or a + standalone device. An Embedded MTA (E-MTA) is an MTA device containing an embedded Data Over Cable Service Interface - Specifications (DOCSIS) Cable Modem. A Standalone MTA (S-MTA) is a + Specifications (DOCSIS) Cable Modem. A Standalone MTA (S-MTA) is an MTA device separated from the DOCSIS Cable Modem by non-DOCSIS MAC interface (e.g., Ethernet, USB). 3.2 Endpoint + An endpoint or MTA endpoint is a standard telephony physical port located on the MTA and used for attaching the telephone device to the MTA. 3.3 L Line Package The L line package refers to the core signaling functionality as defined by PacketCable and IPCablecom. An MTA provides all L package elements, however the operator determines their application. @@ -163,23 +160,24 @@ PacketCable, European Telecommunications Standards Institute(ETSI), and International Telecommunication Union Telecommunication Standardization Sector (ITU-T) IPCablecom compliant Multimedia Terminal Adapter (MTA) devices. The SIG MIB module is intended to supersede various SIG MIB modules from which it is partly derived: - the PacketCable 1.0 Signaling MIB Specification [PKT-SP-MIB-SIG-1.0], - the PacketCable 1.5 Signaling MIB Specification [PKT-SP-MIB-SIG-1.5], - the ITU-T IPCablecom SIG MIB requirements [ITU-T-J169], - - the ETSI SIG MIB [ETSI TS 101 909-9]. The ETSI SIG MIB + - the ETSI SIG MIB [ETSI-TS-101-909-9]. The ETSI SIG MIB requirements also refer to various signal characteristics - defined in [EN 300 001], [EN 300 659-1], and [TR 101 183]. + defined in [ETSI-EN-300-001], [ETSI-EN-300-659-1], and + [ETSI-TR-101-183]. Several normative and informative references are used to help define NCS Signaling MIB objects. As a convention, wherever PacketCable and IPCablecom requirements are equivalent, the PacketCable reference is used in the object REFERENCE clause. IPCablecom compliant MTA devices MUST use the equivalent IPCablecom references. This MIB module describes the various Signaling MIB objects that are directly related to the PacketCable MTA and the endpoints supported on the MTA, each of which provides services independently. The recognition and distinction of the endpoints is made by utilizing @@ -286,23 +283,28 @@ visual message waiting information. pktcSigDevVwmiDTASAfterLR - this international object sets the delay between the end of a line reversal and the dual-tone alert signal for visual message waiting information. pktcSigDevRingCadenceTable - this international object provides a flexible structure within which to specify a variety of ring cadences. - pktcSigDevToneTable - this international object specifies a flexible + pktcSigDevToneTable - this international table specifies a flexible structure within which to specify all of the tones used in the MTA. + pktcSigDevMultiFreqToneTable - this table defines the + characteristics of tones with multiple frequencies. Each entry in + this table represents the frequency reference of a multi-frequency + tone. + pktcNcsEndPntConfigTable - this table describes the PacketCable NCS endPoint configuration. The number of entries in this table represents the number of provisioned endpoints. pktcSigEndPntConfigTable - this table describes the PacketCable endPoint selected signaling type. The number of entries in this table represents the number of provisioned endpoints. 4.3 pktcSigNotification @@ -324,57 +326,57 @@ 5. Definitions PKTC-IETF-SIG-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, mib-2 - FROM SNMPv2-SMI + FROM SNMPv2-SMI -- [RFC2578] InetAddressType, InetAddress, InetPortNumber - FROM INET-ADDRESS-MIB + FROM INET-ADDRESS-MIB -- [RFC4001] TEXTUAL-CONVENTION, RowStatus, TruthValue - FROM SNMPv2-TC + FROM SNMPv2-TC -- [RFC2579] OBJECT-GROUP, MODULE-COMPLIANCE - FROM SNMPv2-CONF + FROM SNMPv2-CONF -- [RFC2580] SnmpAdminString - FROM SNMP-FRAMEWORK-MIB + FROM SNMP-FRAMEWORK-MIB -- [RFC3411] ifIndex - FROM IF-MIB + FROM IF-MIB -- [RFC2863] Dscp - FROM DIFFSERV-DSCP-TC; + FROM DIFFSERV-DSCP-TC; -- [RFC3289] pktcIetfSigMib MODULE-IDENTITY - LAST-UPDATED "200502200000Z" -- February 20, 2005 + LAST-UPDATED "200509090000Z" -- September 9, 2005 ORGANIZATION "IETF IPCDN Working Group" CONTACT-INFO - "Gordon Beacham - Motorola, Inc. - 6450 Sequence Drive, Bldg. 1 - San Diego, CA 92121, USA - Phone: +1 858-404-2335 - Email: gordon.beacham@motorola.com - - Sumanth Channabasappa + "Sumanth Channabasappa Cable Television Laboratories, Inc. 858 Coal Creek Circle, Louisville, CO 80027, USA Phone: +1 303-661-3307 Email: Sumanth@cablelabs.com + Gordon Beacham + Motorola, Inc. + 6450 Sequence Drive, Bldg. 1 + San Diego, CA 92121, USA + Phone: +1 858-404-2335 + Email: gordon.beacham@motorola.com + 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 IETF IPCDN Working Group General Discussion: ipcdn@ietf.org @@ -387,21 +389,21 @@ object for the PacketCable and IPCablecom Signaling protocols. This version of the MIB includes common signaling and Network Call Signaling (NCS) related signaling objects. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices." -- RFC Ed: replace yyyy with actual RFC number and remove this note - REVISION "200502200000Z" + REVISION "200509090000Z" DESCRIPTION "Initial version, published as RFC yyyy." -- RFC Ed: replace yyyy with actual RFC number and remove this note ::= { mib-2 XXX } -- RFC Ed: replace XXX with IANA-assigned number and remove this -- note -- Textual Conventions @@ -417,32 +419,32 @@ PktcCodecType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION " This textual convention defines various types of codecs that MAY be supported. The description for each enumeration is listed below: Enumeration Description other a defined codec not in the enumeration unknown a codec not defined in PacketCable - g729 ITU-T Recommendation G.722 + g729 ITU-T Recommendation G.729 reserved for future use g729E ITU-T Recommendation G.729E pcmu Pulse Code Modulation u-law (PCMU) g726at32 ITU-T Recommendation G.726-32 (32 kbit/s) g728 ITU-T Recommendation G.728 pcma Pulse Code Modulation a-law (PCMA) g726at16 ITU-T Recommendation G.726-16 (16 kbit/s) g726at24 ITU-T Recommendation G.726-24 (24 kbit/s) g726at40 ITU-T Recommendation G.726-40 (40 kbit/s) - ilbc internet low bit rate codec - bv16 BroadVoice16 + ilbc IETF internet low bit rate codec + bv16 Broadcom BroadVoice16 . The list of codecs is consistent with the IETF Real Time Transport Protocol (RTP) Profile registry and the RTP Map Parameters Table in [PKT-SP-CODEC]. The literal codec name for each codec is listed below: Codec Literal Codec Name g729 G729 g729E G729E pcmu PCMU g726at32 G726-32 g728 G728 @@ -536,24 +537,24 @@ { pktcSigMibObjects 2 } -- -- The codec table (pktcSigDevCodecTable) defines all combinations -- of codecs supported by the Multimedia Terminal Adapter (MTA). -- pktcSigDevCodecTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigDevCodecEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - " This table describes the MTA supported codec types. A MTA + " This table describes the MTA supported codec types. An MTA MUST populate this table with all possible combinations of codecs it supports for simultaneous operation. For - example, a MTA with two endpoints may be designed with a + example, an MTA with two endpoints may be designed with a particular DSP and memory architecture that allows it to support the following fixed combinations of codecs for simultaneous operation: Codec Type Maximum Number of Simultaneous Codecs PCMA 3 PCMA 2 PCMU 1 @@ -667,21 +669,21 @@ MAX-ACCESS read-write STATUS current DESCRIPTION "This object identifies the subscriber line protocol used for signaling on-hook caller id information. Different countries define different caller id signaling protocols to support caller identification. Frequency shift keying (FSK) is most commonly used. Dual tone multi-frequency (DTMF) is an alternative." REFERENCE - "EN 300 659-1 Specification" + "ETSI-EN-300-659-1 Specification" DEFVAL { fsk } ::= { pktcSigDevConfigObjects 4 } pktcSigDevR0Cadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies ring cadence 0 (a user defined field). This object is required for the L line package." @@ -895,62 +896,62 @@ f15Hz(5), f16Hz(6), f22Hz(7), f23Hz(8), f45Hz(9) } UNITS "Hertz" MAX-ACCESS read-only STATUS current DESCRIPTION - " This object must only be set via the configuration file - during the provisioning process. 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 terminal equipment ring. The f20Hz - setting corresponds to a power ring frequency of 20 Hertz. - The f25Hz setting corresponds to a power ring frequency of - 25 Hertz. The f33Point33Hz setting corresponds to a power - ring frequency of 33.33 Hertz. The f50Hz setting - corresponds to a power ring frequency of 50 Hertz. The - f15Hz setting corresponds to a power ring frequency of 15 - Hertz. The f16Hz setting corresponds to a power ring - frequency of 16 Hertz. The f22Hz setting corresponds to a - power ring frequency of 22 Hertz. The f23Hz setting - corresponds to a power ring frequency of 23 Hertz. The - f45Hz setting corresponds to a power ring frequency of 45 - Hertz. - " + " This object must only be provided via the configuration + file during the provisioning process. 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 terminal equipment + ring. + The f20Hz setting corresponds to a power ring frequency + of 20 Hertz. The f25Hz setting corresponds to a power ring + frequency of 25 Hertz. The f33Point33Hz setting + corresponds to a power ring frequency of 33.33 Hertz. The + f50Hz setting corresponds to a power ring frequency of 50 + Hertz. The f15Hz setting corresponds to a power ring + frequency of 15 Hertz. The f16Hz setting corresponds to a + power ring frequency of 16 Hertz. The f22Hz setting + corresponds to a power ring frequency of 22 Hertz. The + f23Hz setting corresponds to a power ring frequency of 23 + Hertz. The f45Hz setting corresponds to a power ring + frequency of 45 Hertz." REFERENCE - "EN 300 001 contains a list of frequency ranges that - are defined for each country." + "ETSI-EN-300-001 contains a list of frequency ranges + that are defined for each country." DEFVAL { f20Hz } ::= { pktcSigDevConfigObjects 19 } 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 nine types of international pulse signals, with each signal having a set of provisionable parameters. The values of the MIB objects in this table take effect only if these parameters are not defined via signaling, in which case the latter determines the values of the parameters. This object is required for the E line package. Signals defined in this table are triggered using the E line package. Objects in this table do not persist across MTA reboots." REFERENCE - "TS 101 909-4 Specification" + "ETSI-TS-101-909-4 Specification" ::= { pktcSigDevConfigObjects 20 } pktcSigPulseSignalEntry OBJECT-TYPE SYNTAX PktcSigPulseSignalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This object defines the set of parameters associated with each particular value of pktcSigPulseSignalType. Each entry in the pktcSigPulseSignalTable is indexed by the @@ -988,21 +988,21 @@ initial ring pulse loop close pulse loop open enable meter pulse meter pulse burst pulse no battery pulse normal polarity pulse reduced battery pulse reverse polarity" REFERENCE - "EN 300 324-1 Specification" + "ETSI-EN-300-324-1 Specification" ::= { pktcSigPulseSignalEntry 1 } pktcSigPulseSignalFrequency OBJECT-TYPE SYNTAX INTEGER { twentyfive (1), twelvethousand(2), sixteenthousand(3) } UNITS "Hertz" @@ -1017,40 +1017,40 @@ pktcSigPulseSignalType Default initialRing 25 enableMeterPulse 16000 meterPulseBurst 16000 The value of twentyfive MUST only be used for the initialRing signal type. The values of twelvethousand and sixteenthousand MUST only be used for enableMeterPulse and meterPulseBurst signal types. An attempt to set this object while the value of pktcSigPulseSignalType is not initialRing,enableMeterPulse, or meterPulseBurst will - result in an inconsistentValue error." + result in an 'inconsistent value' error." REFERENCE - "EN 300 001 Specification" + "ETSI-EN-300-001 Specification" ::= { pktcSigPulseSignalEntry 2} pktcSigPulseSignalDbLevel OBJECT-TYPE SYNTAX TenthdBm (-350..0) UNITS "dBm" MAX-ACCESS read-write STATUS current DESCRIPTION " This object is only applicable to the enableMeterPulse and meterPulseBurst signal types. This is the decibel level for each frequency at which tones could be generated at the a and b terminals (TE connection point). An attempt to set this object while the value of pktcSigPulseSignalType is not enableMeterPulse, or meterPulseBurst will result in - an inconsistentValue error." + an 'inconsistent value' error." REFERENCE - "EN 300 001 Specification" + "ETSI-EN-300-001 Specification" DEFVAL { -135 } ::={pktcSigPulseSignalEntry 3 } pktcSigPulseSignalDuration OBJECT-TYPE SYNTAX Unsigned32 (0..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies the pulse duration for each @@ -1065,23 +1065,23 @@ pulseLoopOpen 200 10 enableMeterPulse 150 10 meterPulseBurst 150 10 pulseNoBattery 200 10 pulseNormalPolarity 200 10 pulseReducedBattery 200 10 pulseReversePolarity 200 10 An attempt to set this object to a value that does not fall on one of the increment boundaries, or on the wrong increment boundary for the specific signal type will - result in an inconsistentValue error." + result in an 'inconsistent value' error." REFERENCE - "EN 300 324-1 Specification" + "ETSI-EN-300-324-1 Specification" ::= {pktcSigPulseSignalEntry 4 } pktcSigPulseSignalPulseInterval OBJECT-TYPE SYNTAX Unsigned32 (0..5000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies the repeat interval, or the period for each signal type. In addition, the MTA must accept @@ -1095,31 +1095,32 @@ pulseLoopOpen 1000 10 enableMeterPulse 1000 10 meterPulseBurst 1000 10 pulseNoBattery 1000 10 pulseNormalPolarity 1000 10 pulseReducedBattery 1000 10 pulseReversePolarity 1000 10 An attempt to set this object to a value that does not fall on one of the increment boundaries, or on the wrong increment boundary for the specific signal type will - result in an inconsistentValue error." + result in an 'inconsistent value' error." REFERENCE - "EN 300 324-1 Specification" + "ETSI-EN-300-324-1 Specification" ::= { pktcSigPulseSignalEntry 5} pktcSigPulseSignalRepeatCount OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies how many times to repeat a pulse. + This object is not used by the enableMeterPulse signal type and as such must have a value of zero. The following table defines the default values and the valid ranges for this object depending on the signal type. pktcSigPulseSignaltype Default Range initialRing 1 1-5 pulseLoopClose 1 1-50 pulseLoopOpen 1 1-50 enableMeterPulse 0 Not Used meterPulseBurst 1 1-50 @@ -1122,176 +1123,170 @@ pulseLoopClose 1 1-50 pulseLoopOpen 1 1-50 enableMeterPulse 0 Not Used meterPulseBurst 1 1-50 pulseNoBattery 1 1-50 pulseNormalPolarity 1 1-50 pulseReducedBattery 1 1-50 pulseReversePolarity 1 1-50 An attempt to set this object to a value that does not fall within the range (or is not used) for the specific - signal type will result in an inconsistentValue error." + signal type will result in an 'inconsistent value' error." ::={ pktcSigPulseSignalEntry 6 } pktcSigDevCIDMode OBJECT-TYPE SYNTAX INTEGER { duringRingingETS(1), dtAsETS(2), rpAsETS(3), lrAsETS(4) } MAX-ACCESS read-write STATUS current DESCRIPTION - " This object is required only for Euro-PacketCable. - For on-hook Caller ID, pktcSigDevCIDMode selects the + " For on-hook Caller ID, pktcSigDevCIDMode selects the method of Caller ID. For the duringRingingETS method, the Frequency Shift Keying (FSK) containing the Caller ID information is sent between the first and second ring pattern. For the dtAsETS,rpAsETS, and lrAsETS methods, the FSK containing the Caller ID information is sent before the first ring pattern. For the dtAsETS method, the FSK is sent after the Dual Tone Alert Signal. For the rpAsETS method, the FSK is sent after a Ring Pulse. For the lrAsETS method, the Line Reversal occurs first, then the Dual Tone Alert Signal, and finally the FSK is sent." DEFVAL { rpAsETS} ::= {pktcSigDevConfigObjects 21 } pktcSigDevCIDFskAfterRing OBJECT-TYPE SYNTAX Unsigned32 (50..2000) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION - " This object is required only for Euro-PacketCable. This - object specifies the delay between the end of first + " This object specifies the delay between the end of first ringing pattern and the start of the transmission of the FSK containing the Caller ID information. It is only used when pktcSigDevCIDMode is duringRingingETS. The following table defines the default values for this object depending on signal type: pktcSigDevCIDMode Default duringringingETS 550 ms dtAsETS not used rpAsETS not used lrAsETS not used An attempt to set this object while the value of pktcSigDevCIDMode is not duringringingETS will result in - an inconsistentValue error." + an 'inconsistent value' error." REFERENCE - "EN 300 659-1 Specification" + "ETSI-EN-300-659-1 Specification" DEFVAL { 550 } ::= {pktcSigDevConfigObjects 22 } pktcSigDevCIDFskAfterDTAS OBJECT-TYPE SYNTAX Unsigned32 (45..500) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION - " This object is required only for Euro-PacketCable. This - object specifies the delay between the end of the Dual - Tone Alert Signal (DT-AS) and the start of the + " This object specifies the delay between the end of the + Dual Tone Alert Signal (DT-AS) and the start of the transmission of the FSK containing the Caller ID information. This object is only used when pktcSigDevCIDMode is dtAsETS or lrAsETS. The following table defines the default values for this object depending on signal type: pktcSigDevCIDMode Default duringringingETS not used dtAsETS 50 ms rpAsETS not used lrAsETS 50 ms An attempt to set this object while the value of pktcSigDevCIDMode is not dtAsETS or lrAsETS will result in - an inconsistentValue error." + an 'inconsistent value' error." REFERENCE - "EN 300 659-1 Specification" + "ETSI-EN-300-659-1 Specification" DEFVAL { 50 } ::= {pktcSigDevConfigObjects 23 } pktcSigDevCIDFskAfterRPAS OBJECT-TYPE SYNTAX Unsigned32 (500..800) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION - " This object is required only for Euro-PacketCable. This - object specifies the delay between the end of the Ring - Pulse Alert Signal (RP-AS) and the start of the + " This object specifies the delay between the end of the + Ring Pulse Alert Signal (RP-AS) and the start of the transmission of the FSK containing the Caller ID information. This object is only used when pktcSigDevCIDMode is rpAsETS. The following table defines the default values for this object depending on signal type: pktcSigDevCIDMode Default duringringingETS not used dtAsETS not used rpAsETS 650 ms lrAsETS not used An attempt to set this object while the value of pktcSigDevCIDMode is not rpAsETS will result in an - inconsistentValue error." + 'inconsistent value' error." REFERENCE - "EN 300 659-1 Specification" + "ETSI-EN-300-659-1 Specification" DEFVAL { 650 } ::= {pktcSigDevConfigObjects 24 } pktcSigDevCIDRingAfterFSK OBJECT-TYPE SYNTAX Unsigned32 (50..500) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION - " This object is required only for Euro-PacketCable. This - object specifies the delay between the end of the complete - transmission of the FSK containing the Caller ID + " This object specifies the delay between the end of the + complete transmission of the FSK containing the Caller ID information and the start of the first ring pattern. It is only used when pktcSigDevCIDMode is dtAsETS, rpAsETS or lrAsETS. The following table defines the default values for this object depending on signal type: pktcSigDevCIDMode Default duringringingETS not used dtAsETS 250 ms rpAsETS 250 ms lrAsETS 250 ms An attempt to set this object while the value of pktcSigDevCIDMode is not dtAsETS, rpAsETS, or lrAsETS will - result in an inconsistentValue error." + result in an 'inconsistent value' error." REFERENCE - "EN 300 659-1 Specification" + "ETSI-EN-300-659-1 Specification" DEFVAL { 250 } ::= {pktcSigDevConfigObjects 25 } pktcSigDevCIDDTASAfterLR OBJECT-TYPE SYNTAX Unsigned32 (50..655) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION - " This object is required only for Euro-PacketCable. This - object specifies the delay between the end of the Line - Reversal and the start of the Dual Tone Alert Signal + " This object specifies the delay between the end of the + Line Reversal and the start of the Dual Tone Alert Signal (DT-AS). This object is only used when pktcSigDevCIDMode is lrAsETS. The following table defines the default values for this object depending on signal type: pktcSigDevCIDMode Default duringringingETS not used dtAsETS not used rpAsETS not used lrAsETS 250 ms An attempt to set this object while the value of pktcSigDevCIDMode is not lrAsETS will result in an - inconsistentValue error." + 'inconsistent value' error." REFERENCE - "EN 300 659-1 Specification" + "ETSI-EN-300-659-1 Specification" DEFVAL { 250 } ::= {pktcSigDevConfigObjects 26 } pktcSigDevVmwiMode OBJECT-TYPE SYNTAX INTEGER { dtAsETS(1), rpAsETS(2), lrAsETS(3), osi(4) @@ -1312,86 +1307,83 @@ Interval." DEFVAL { dtAsETS } ::= {pktcSigDevConfigObjects 27 } pktcSigDevVmwiFskAfterDTAS OBJECT-TYPE SYNTAX Unsigned32 (45..500) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION - " This object is required only for Euro-PacketCable. This - object specifies the delay between the end of the Dual - Tone Alert Signal (DT-AS) and the start of the + " This object specifies the delay between the end of the + Dual Tone Alert Signal (DT-AS) and the start of the transmission of the FSK containing the VMWI information. This object is only used when pktcSigDevVmwiMode is dtAsETS or lrAsETS. The following table defines the default values for this object depending on signal type: pktcSigDevVmwiMode Default dtAsETS 50 ms rpAsETS not used lrAsETS 50 ms An attempt to set this object while the value of pktcSigDevVmwiMode is not dtAsETS or lrAsETS will result - in an inconsistentValue error." + in an 'inconsistent value' error." REFERENCE - "EN 300 659-1 Specification" + "ETSI-EN-300-659-1 Specification" DEFVAL { 50 } ::= {pktcSigDevConfigObjects 28 } pktcSigDevVmwiFskAfterRPAS OBJECT-TYPE SYNTAX Unsigned32 (500..800) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION - " This object is required only for Euro-PacketCable. This - object specifies the delay between the end of the Ring - Pulse Alert Signal (RP-AS) and the start of the + " This object specifies the delay between the end of the + Ring Pulse Alert Signal (RP-AS) and the start of the transmission of the FSK containing the VMWI information. This object is only used when pktcSigDevVmwiMode is rpAsETS. The following table defines the default values for this object depending on signal type: pktcSigDevVmwiMode Default dtAsETS not used rpAsETS 650 ms lrAsETS not used An attempt to set this object while the value of pktcSigDevVmwiMode is not rpAsETS will result in an - inconsistentValue error." + 'inconsistent value' error." REFERENCE - "EN 300 659-1 Specification" + "ETSI-EN-300-659-1 Specification" DEFVAL { 650 } ::= {pktcSigDevConfigObjects 29 } pktcSigDevVmwiDTASAfterLR OBJECT-TYPE SYNTAX Unsigned32 (50..655) UNITS "Milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION - " This object is required only for Euro-PacketCable. This - object specifies the delay between the end of the Line - Reversal and the start of the Dual Tone Alert Signal + " This object specifies the delay between the end of the + Line Reversal and the start of the Dual Tone Alert Signal (DT-AS) for VMWI information. This object is only used when pktcSigDevVmwiMode is lrAsETS. The following table defines the default values for this object depending on signal type: pktcSigDevVmwiMode Default dtAsETS not used rpAsETS not used lrAsETS 250 ms An attempt to set this object while the value of pktcSigDevVmwiMode is not lrAsETS will result in an - inconsistentValue error." + 'inconsistent value' error." REFERENCE - "EN 300 659-1 Specification" + "ETSI-EN-300-659-1 Specification" DEFVAL { 250 } ::= {pktcSigDevConfigObjects 30 } pktcSigDevRingCadenceTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigDevRingCadenceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Cadence rings are defined by the telco governing body for each country. The MTA must be able to support @@ -1403,21 +1395,21 @@ where x is the value sent in the cadence ringing (cr) signal cr(x), requested per the appropriate NCS message, and defined in the E package. The MTA will derive the cadence periods from the ring cadence table entry as provisioned by the customer. The MTA is allowed to provide appropriate default values for each of the ring cadences. This table only needs to be supported when the MTA implements the E package. Objects in this table do not persist across MTA reboots." REFERENCE - "TS 101 909-4 Specification" + "ETSI-TS-101-909-4 Specification" ::= { pktcSigDevConfigObjects 31 } pktcSigDevRingCadenceEntry OBJECT-TYPE SYNTAX PktcSigDevRingCadenceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " Unique value ranging from 0 to 127 that will correspond to the different ring cadences that are being supported by the device." @@ -1444,172 +1436,147 @@ ::= { pktcSigDevRingCadenceEntry 1 } pktcSigDevRingCadence OBJECT-TYPE SYNTAX PktcRingCadence MAX-ACCESS read-write STATUS current DESCRIPTION "This is the Ring Cadence. This object is required for the E line package." ::= { pktcSigDevRingCadenceEntry 2 } - pktcSigDevToneType OBJECT-TYPE - SYNTAX INTEGER { - busy(1), - confirmation(2), - dial(3), - messageWaiting(4), - offHookWarning(5), - ringBack(6), - reOrder(7), - stutterdial(8), - callWaiting1(9), - callWaiting2(10), - callWaiting3(11), - callWaiting4(12), - alertingSignal(13), - specialDial(14), - specialInfo(15), - release(16), - congestion(17), - userDefined1(18), - userDefined2(19), - userDefined3(20), - userDefined4(21) - } - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "Unique value ranging from 1 to 21 that will correspond - to the different tone types. These tones can be - provisioned based on country specific needs. This - object defines the type of tone being accessed. - The alertingSignal, specialDial, specialInfo, release, - congestion and userDefined1-4 tone types are used in - the E line package." - ::= { pktcSigDevConfigObjects 32 } - - pktcSigDevToneNumFrequencies OBJECT-TYPE - SYNTAX INTEGER(5..16) - MAX-ACCESS read-write - STATUS current - DESCRIPTION - "This MIB Object specifies the number of frequencies - supported by the PacketCable MTA for each tone type." - ::={ pktcSigDevConfigObjects 33} pktcSigDevToneTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigDevToneEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " The Tone Table defines the various tone operations. Any definition of the tones callWaiting1-4 in this table should just contain the audible tone itself and NOT contain the delay between tones or the tone repeat count. The delay between tones or the repeat count is controlled by the objects pktcNcsEndPntConfigCallWaitingDelay, and pktcNcsEndPntConfigCallWaitingMaxRep. If the pktcSigDevToneType is set to either of the values callWaiting1, callWaiting2, callWaiting3 or callWaiting4, then the value of the pktcSigDevToneWholeToneRepeatCount object has no effect on the tone. The MTA MUST make sure that, after the provisioning cycle, the table is fully populated (i.e., for each possible index, an entry MUST be defined) using reasonable defaults for each row - that was not defined by the provisioning information. + that was not defined by the provisioning information + delivered by the MTA Configuration File. + The frequency composition of each tone is defined by the + pktcSigDevMultiFreqToneTable. For each ToneType defined + in pktcSigDevToneTable, the MTA MUST populate at least + one entry in the pktcSigDevMultiFreqToneTable. Objects in this table do not persist across MTA reboots. For tones with multiple frequencies refer to the MIB table pktcSigDevMultiFreqToneTable." REFERENCE - "NCS Specification, TS 101 909-4 Specification" - ::= { pktcSigDevConfigObjects 34 } + "PacketCable NCS Specification, ETSI-TS-101-909-4 + Specification." + ::= { pktcSigDevConfigObjects 32 } pktcSigDevToneEntry OBJECT-TYPE SYNTAX PktcSigDevToneEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " The different tone types that can be provisioned based on - country specific needs." + country specific needs. + Each entry contains the tone generation parameters for + a specific Tone Type. The different parameters can be + provisioned by the MTA configuration file based on + country specific needs. An MTA MUST populate all entries + of this table for each tone type." INDEX { pktcSigDevToneType } ::= { pktcSigDevToneTable 1 } PktcSigDevToneEntry ::= SEQUENCE { - pktcSigDevToneDbLevel TenthdBm, + pktcSigDevToneType INTEGER, pktcSigDevToneWholeToneRepeatCount Unsigned32, pktcSigDevToneSteady TruthValue } - pktcSigDevToneDbLevel OBJECT-TYPE - SYNTAX TenthdBm (-250..-30) - UNITS "dBm" - MAX-ACCESS read-write + pktcSigDevToneType OBJECT-TYPE + SYNTAX INTEGER { + busy(1), + confirmation(2), + dial(3), + messageWaiting(4), + offHookWarning(5), + ringBack(6), + reOrder(7), + stutterdial(8), + callWaiting1(9), + callWaiting2(10), + callWaiting3(11), + callWaiting4(12), + alertingSignal(13), + specialDial(14), + specialInfo(15), + release(16), + congestion(17), + userDefined1(18), + userDefined2(19), + userDefined3(20), + userDefined4(21) + } + MAX-ACCESS not-accessible STATUS current DESCRIPTION - - "This MIB Object contains the decibel level for each - analog signal (tone) that is locally generated - versus in band supervisory tones) and sourced to - the a-b terminals (TE connection point). Each tone - in itself may consist of multiple frequencies as - defined by the MIB table - 'pktcSigDevMultiFreqToneTable'. - - This MIB Object MUST reflect the desired level at - the Telco (POTS) a-b (T/R) terminals including the - affect of the pktcNcsEndPntConfigRxGain setting on - the delivered tone. - - The wide range of levels for this Object is required - to provide signal generator levels across the wide - range of gains - but does not imply the entire range - is to be achievable given the range of negative - values of gain (positive loss). This MIB Object must - be set for each tone so as to generate the combined - frequency level at the a-b (T/R) terminals." - - DEFVAL { -40 } + "Unique value that will correspond to the different + tone types. These tones can be provisioned based on + country specific needs. This object defines the type + of tone being accessed. + The alertingSignal, specialDial, specialInfo, release, + congestion, userDefined1, userDefined2, userDefined3 + and userDefined4 tone types are used in + the E line package." ::={pktcSigDevToneEntry 1 } pktcSigDevToneWholeToneRepeatCount OBJECT-TYPE SYNTAX Unsigned32 (0..5000) - MAX-ACCESS read-write + MAX-ACCESS read-only STATUS current DESCRIPTION "This is the repeat count, which signifies how many times - to repeat the entire on-off sequence. Setting this object - may result in a tone duration longer or shorter than the + to repeat the entire on-off cadence sequence. Setting this + object + may result in a cadence duration longer or shorter than the overall signal duration specified by the time out (TO) object for a particular signal. If the repeat count results in a longer tone duration than the signal duration specified by the TO, the tone duration defined by the TO object for a particular signal always represents the overall signal duration for a tone. In this case, the tone duration repeat count will not be fully exercised and the desired tone duration will be truncated per the TO setting. If the repeat count results in a shorter tone duration than the signal duration specified by the TO, the tone duration defined by the repeat count takes precedence over the TO and will end the signal event. In this case, the TO represents a time not to be exceeded for the signal. It is recommended to ensure proper telephony signaling that The TO duration setting should always be longer than the desired repeat count time duration." ::={ pktcSigDevToneEntry 2 } pktcSigDevToneSteady OBJECT-TYPE SYNTAX TruthValue - MAX-ACCESS read-write + MAX-ACCESS read-only STATUS current DESCRIPTION "This is the steady tone. Device must play out the on-off - sequence for pktcSigDevToneWholeRepeatCount times and + cadence sequence for pktcSigDevToneWholeRepeatCount times + and then apply the last tone forever. Setting this object may result in a tone duration longer or shorter than the overall signal duration specified by the time out (TO) object for a particular signal. If the repeat count results in a longer tone duration than the signal duration specified by the TO, the tone duration defined by the TO object for a particular signal always represents the overall signal duration for a tone. In this case, the tone duration repeat count will not be fully exercised and the desired tone duration will be truncated per the TO @@ -1627,142 +1594,210 @@ pktcSigDevMultiFreqToneTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcSigDevMultiFreqToneEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This MIB table defines the characteristics of tones with multiple frequencies. The constraints imposed on the tones by the MIB table pktcSigDevToneTable need to be considered for MIB objects in this table - as well." + as well. + The MTA MUST populate the corresponding row(s) + of the pktcSigDevMultiFreqToneTable for each tone + defined in the pktcSigDevToneTable. + The contents of the table may be provisioned using + the MTA configuration file." REFERENCE - "NCS Specification, TS 101 909-4 Specification" + "PacketCable NCS Specification, ETSI-TS-101-909-4 + Specification." ::= { pktcSigDevConfigObjects 35 } pktcSigDevMultiFreqToneEntry OBJECT-TYPE SYNTAX PktcSigDevMultiFreqToneEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " The different tone types with multiple frequencies that can be provisioned based on country specific needs." - INDEX { pktcSigDevToneType, pktcSigDevToneFrequencyNumber } + INDEX {pktcSigDevToneType, pktcSigDevToneNumber} ::= { pktcSigDevMultiFreqToneTable 1 } PktcSigDevMultiFreqToneEntry ::= SEQUENCE { - pktcSigDevToneFrequencyNumber Unsigned32 , - pktcSigDevToneFreqPriCompValue Unsigned32, - pktcSigDevToneFreqSecCompValue Unsigned32, - pktcSigDevToneFreqSecCompMode INTEGER, - pktcSigDevToneFreqSecCompPrtg Integer32, + pktcSigDevToneNumber Unsigned32, + pktcSigDevToneFirstFreqValue Unsigned32, + pktcSigDevToneSecondFreqValue Unsigned32, + pktcSigDevToneThirdFreqValue Unsigned32, + pktcSigDevToneFourthFreqValue Unsigned32, + pktcSigDevToneFreqMode INTEGER, + pktcSigDevToneFreqAmpModePrtg Integer32, + pktcSigDevToneDbLevel TenthdBm, pktcSigDevToneFreqOnDuration Unsigned32, pktcSigDevToneFreqOffDuration Unsigned32, pktcSigDevToneFreqRepeatCount Unsigned32 } - pktcSigDevToneFrequencyNumber OBJECT-TYPE - SYNTAX Unsigned32(5..16) + pktcSigDevToneNumber OBJECT-TYPE + SYNTAX Unsigned32(1..8) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This MIB Object represents the frequency reference - of a multi-frequency tone. It is to be noted that - the maximum number of frequencies for a - multi-frequency tone is limited by the MIB Object - pktcSigDevToneNumFrequencies." + of a multi-frequency tone." ::={ pktcSigDevMultiFreqToneEntry 1} - pktcSigDevToneFreqPriCompValue OBJECT-TYPE + pktcSigDevToneFirstFreqValue OBJECT-TYPE SYNTAX Unsigned32(0..4000) - MAX-ACCESS read-write + MAX-ACCESS read-only STATUS current DESCRIPTION - "This MIB Object represents the value of the primary - component frequency specific to the frequency reference - of a tone type." + "This MIB Object represents the value of the first + frequency of a tone type. A value of Zero implies + absence of the referenced frequency." ::={ pktcSigDevMultiFreqToneEntry 2} - pktcSigDevToneFreqSecCompValue OBJECT-TYPE + pktcSigDevToneSecondFreqValue OBJECT-TYPE SYNTAX Unsigned32(0..4000) - MAX-ACCESS read-write + MAX-ACCESS read-only STATUS current DESCRIPTION - "This MIB Object represents the value of the secondary - component frequency specific to the frequency reference - of a tone type." + "This MIB Object represents the value of the second + frequency of a tone type. A value of Zero implies + absence of the referenced frequency." ::={ pktcSigDevMultiFreqToneEntry 3} - pktcSigDevToneFreqSecCompMode OBJECT-TYPE + pktcSigDevToneThirdFreqValue OBJECT-TYPE + SYNTAX Unsigned32(0..4000) + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This MIB Object represents the value of the third + frequency of a tone type. A value of Zero implies + absence of the referenced frequency." + ::={ pktcSigDevMultiFreqToneEntry 4} + + pktcSigDevToneFourthFreqValue OBJECT-TYPE + SYNTAX Unsigned32(0..4000) + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This MIB Object represents the value of the fourth + frequency of a tone type. A value of Zero implies + absence of the referenced frequency." + ::={ pktcSigDevMultiFreqToneEntry 5} + + pktcSigDevToneFreqMode OBJECT-TYPE SYNTAX INTEGER { - ignoreSecondary (1), - primaryModulatedBySecondary (2), - primarySummedWithSecondary (3) + firstModulatedBySecond (1), + summation (2) } - MAX-ACCESS read-write + MAX-ACCESS read-only STATUS current DESCRIPTION - "This MIB Object indicates the way the primary - and secondary frequency components indicated - by the MIB Objects 'pktcSigDevToneFreqPriCompValue' - and 'pktcSigDevToneFreqSecCompValue' are to be used. + "This MIB Object provides directive on the + modulation or summation of the frequencies + involved in the tone. - A value of primaryModulatedBySecondary(2) indicates - that the primary must be used to amplitude modulate - the secondary. The percentage of amplitude modulation - to be applied to the secondary is defined by the MIB - Object 'pktcSigDevToneFreqSecCompPrtg'. + It is to be noted that while summation can + be done without any constraint on the number + of frequencies, the modulation (amplitude) + holds good only when there are two frequencies + (first and second). - A value of primarySummedWithSecondary(3) indicates - that the primary must be summed with the secondary, - without any modulation + Thus: + - If the mode is set to a value of + firstModulatedBySecond (1), the first frequency + MUST be modulated by the second and the remaining + frequencies (third and fourth) ignored. The + percentage of amplitude modulation to be applied + is defined by the MIB Object + 'pktcSigDevToneFreqAmpModePrtg'. + - If the mode is set to a value of + summation (2), all the frequencies MUST be + summed, without any modulation - A value of ignoreSecondary(1) indicates that the - secondary must not be used." - ::={ pktcSigDevMultiFreqToneEntry 4} + " + ::={ pktcSigDevMultiFreqToneEntry 6} - pktcSigDevToneFreqSecCompPrtg OBJECT-TYPE + pktcSigDevToneFreqAmpModePrtg OBJECT-TYPE SYNTAX Integer32(0..100) - MAX-ACCESS read-write + MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB Object represents the percentage of amplitude - modulation applied to the secondary frequency component - when the MIB Object 'pktcSigDevToneFreqSecCompMode' is - set to a value of 'primaryModulatedBySecondary(2)'. - In all other cases this MIB Object has no meaning." - ::={ pktcSigDevMultiFreqToneEntry 5} + modulation applied to the second frequency + when the MIB Object 'pktcSigDevToneFreqMode' is + set to a value of 'firstModulatedBySecond (1)'. + + If the MIB Object 'pktcSigDevToneFreqMode' is set to + value of 'summation (2)' then this MIB Object MUST be + ignored." + ::={ pktcSigDevMultiFreqToneEntry 7} + + pktcSigDevToneDbLevel OBJECT-TYPE + SYNTAX TenthdBm (-250..-30) + UNITS "dBm" + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This MIB Object contains the decibel level for each + analog signal (tone) that is locally generated + (versus in band supervisory tones) and sourced to + the a-b terminals (TE connection point). Each tone + in itself may consist of multiple frequencies as + defined by the MIB table 'pktcSigDevMultiFreqToneTable'. + + This MIB Object MUST reflect the desired level at + the Telco (POTS) a-b (T/R) terminals including the + affect of any MTA receiver gain (loss). This is required + so that locally generated tones are consistent with + remotely generated in band tones at the a-b terminals, + consistent with user expectations. + + This MIB Object must be set for each tone. + When tones are formed by combining multi-frequencies, + the level of each frequency shall be set so as to result + in the tone level specified in this object at the a-b + (T/R) terminals. + + The wide range of levels for this Object is required + to provide signal generator levels across the wide + range of gains (loss) - but does not imply the entire + range is to be achievable given the range of gains (loss) + in the MTA." + DEFVAL { -40 } + ::={ pktcSigDevMultiFreqToneEntry 8} pktcSigDevToneFreqOnDuration OBJECT-TYPE SYNTAX Unsigned32(0..5000) - MAX-ACCESS read-write + MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB Object represents the duration for which the frequency reference corresponding to the tone type is turned on." - ::={ pktcSigDevMultiFreqToneEntry 6} + ::={ pktcSigDevMultiFreqToneEntry 9} pktcSigDevToneFreqOffDuration OBJECT-TYPE SYNTAX Unsigned32(0..5000) - MAX-ACCESS read-write + MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB Object represents the duration for which the frequency reference corresponding to the tone type is turned off." - ::={ pktcSigDevMultiFreqToneEntry 7} + ::={ pktcSigDevMultiFreqToneEntry 10} pktcSigDevToneFreqRepeatCount OBJECT-TYPE SYNTAX Unsigned32(0..5000) - MAX-ACCESS read-write + MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB Object indicates the number of times to repeat the cadence cycle represented by the on/off durations (refer to the MIB Objects pktcSigDevToneFreqOnDuration and pktcSigDevToneFreqOffDuration). Setting this object may result in a tone duration longer or shorter than the overall signal duration @@ -1777,24 +1812,24 @@ tone duration than the signal duration specified by the TO, the tone duration defined by the repeat count takes precedence over the TO and will end the signal event. In this case, the TO represents a time not to be exceeded for the signal. It is recommended to ensure proper telephony signaling that the TO duration setting should always be longer than the desired repeat count time duration. A value of zero means the tone sequence is to be played once but not repeated." - ::={ pktcSigDevMultiFreqToneEntry 8} + ::={ pktcSigDevMultiFreqToneEntry 11} -- - -- The NCS End Point Config Table is used to define attributes that + -- The NCS Endpoint 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 information pertaining to each endpoint of the MTA. All entries in this table represent @@ -1850,25 +1885,22 @@ pktcNcsEndPntConfigCallWaitingDelay Unsigned32, pktcNcsEndPntStatusCallIpAddressType InetAddressType, pktcNcsEndPntStatusCallIpAddress InetAddress, pktcNcsEndPntStatusError INTEGER, pktcNcsEndPntConfigMinHookFlash Unsigned32, pktcNcsEndPntConfigMaxHookFlash Unsigned32, pktcNcsEndPntConfigPulseDialInterdigitTime Unsigned32, pktcNcsEndPntConfigPulseDialMinMakeTime Unsigned32, pktcNcsEndPntConfigPulseDialMaxMakeTime Unsigned32, pktcNcsEndPntConfigPulseDialMinBreakTime Unsigned32, - pktcNcsEndPntConfigPulseDialMaxBreakTime Unsigned32, - pktcNcsEndPntConfigTxGain Integer32, - pktcNcsEndPntConfigRxGain Integer32 + pktcNcsEndPntConfigPulseDialMaxBreakTime Unsigned32 } - 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 (e.g.: ca@example.com). The call agent name, after the character '@', MUST be a fully qualified domain name (FQDN) and MUST have a corresponding pktcMtaDevCmsFqdn entry in the pktcMtaDevCmsTable. The object @@ -2072,21 +2105,22 @@ ::= { pktcNcsEndPntConfigEntry 12 } pktcNcsEndPntConfigTSMax OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "This MIB object is used as part of an NCS retransmission algorithm. Prior to any retransmission, the MTA must check to make sure that the time elapsed - since the sending of the initial datagram does not exceed + since the sending of the initial datagram does not + exceed the value specified by this MIB Object. If more than Tsmax time has elapsed, then the retransmissions MUST cease. Refer to the MIB Object pktcNcsEndPntConfigThist for Information on when the endpoint becomes disconnected." REFERENCE "PacketCable NCS Specification" DEFVAL { 20 } ::= { pktcNcsEndPntConfigEntry 13 } @@ -2143,21 +2177,21 @@ DEFVAL { true } ::= { pktcNcsEndPntConfigEntry 17 } pktcNcsEndPntConfigMWD OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Maximum Waiting Delay (MWD) contains the maximum number of - seconds a MTA waits after powering on, before initiating + seconds an MTA waits after powering on, before initiating the restart procedure with the call agent." REFERENCE "PacketCable NCS Specification" DEFVAL { 600 } ::= { pktcNcsEndPntConfigEntry 18 } pktcNcsEndPntConfigTdinit OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create @@ -2181,21 +2216,22 @@ DEFVAL { 15 } ::= { pktcNcsEndPntConfigEntry 19 } pktcNcsEndPntConfigTdmin OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "This MIB object represents the 'disconnected' minimum - waiting delay within the context of an MTA's 'disconnected + waiting delay within the context of an MTA's + 'disconnected procedure', specifically when local user activity is detected. The 'disconnected procedure' is initiated when an endpoint becomes 'disconnected' while attempting to communicate with a Call Agent. For more information on the usage of this timer, please refer to the PacketCable NCS Specification." REFERENCE "PacketCable NCS Specification" @@ -2216,23 +2252,23 @@ "PacketCable NCS Specification" DEFVAL { 600 } ::= { pktcNcsEndPntConfigEntry 21 } pktcNcsEndPntConfigRtoMax OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION - " This object contains the maximum number of seconds for the - retransmission timer. When this timer expires the MTA - retransmits the message." + "This object specifies the maximum number of seconds the MTA + waits for a response to an NCS message before initiating + a retransmission." REFERENCE "PacketCable NCS Specification" DEFVAL { 4 } ::= { pktcNcsEndPntConfigEntry 22 } pktcNcsEndPntConfigRtoInit OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-create STATUS current @@ -2356,42 +2391,43 @@ association is involved with this endpoint. The NCS signaling software is in process of establishing the NCS signaling link via an RSIP exchange. Otherwise, when pktcMtaDevCmsIpsecCtrl is enabled, security Association has been established, and the NCS signaling software is in process of establishing the NCS signaling link via an RSIP exchange." ::= { pktcNcsEndPntConfigEntry 31 } pktcNcsEndPntConfigMinHookFlash OBJECT-TYPE - SYNTAX Unsigned32 (20..1000) + SYNTAX Unsigned32 (20..1550) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the minimum time a line needs to be on hook for a valid hook flash. The value of this object MUST be greater than the value of pktcNcsEndPntConfigPulseDialMaxBreakTime. The value of pktcNcsEndPntConfigMinHookFlash MUST be less than pktcNcsEndPntConfigMaxHookFlash. This object MUST only be set via the configuration file during the provisioning process. Furthermore, given the possibility for the 'pulse dial' - and 'hook flash' to overlap, the value of this object MUST + and 'hook flash' to overlap, the value of this object + MUST be greater than the value contained by the MIB Object pktcNcsEndPntConfigPulseDialMaxMakeTime." DEFVAL { 300 } ::= { pktcNcsEndPntConfigEntry 32 } pktcNcsEndPntConfigMaxHookFlash OBJECT-TYPE - SYNTAX Unsigned32 (20..1000) + SYNTAX Unsigned32 (20..1550) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the maximum time a line needs to be on hook for a valid hook flash. The value of pktcNcsEndPntConfigMaxHookFlash MUST be greater than pktcNcsEndPntConfigMinHookFlash. This object MUST only be set via the configuration file during the provisioning process." @@ -2426,99 +2462,56 @@ pktcNcsEndPntConfigPulseDialMaxMakeTime OBJECT-TYPE SYNTAX Unsigned32 (20..200) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the maximum make pulse width for the dial pulse. The value of pktcNcsEndPntConfigPulseDialMaxMakeTime MUST be greater than pktcNcsEndPntConfigPulseDialMinMakeTime. - This object MUST only be set via the configuration file - during the provisioning process. + This object MUST only be provided via the configuration + file during the provisioning process. Furthermore, given the possibility for the 'pulse dial' and 'hook flash' to overlap, the value of this object MUST be less than the value contained by the MIB Object pktcNcsEndPntConfigMinHookFlash." DEFVAL { 55 } ::= { pktcNcsEndPntConfigEntry 36 } - pktcNcsEndPntConfigPulseDialMinBreakTime OBJECT-TYPE SYNTAX Unsigned32 (20..200) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the minimum break pulse width for the dial pulse. The value of pktcNcsEndPntConfigPulseDialMinBreakTime MUST be less than pktcNcsEndPntConfigPulseDialMaxBreakTime. - This object must only be set via the configuration file - during the provisioning process." + This object must only be provided via the configuration + file during the provisioning process." DEFVAL { 45 } ::= { pktcNcsEndPntConfigEntry 37 } pktcNcsEndPntConfigPulseDialMaxBreakTime OBJECT-TYPE SYNTAX Unsigned32 (20..200) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the maximum break pulse width for the dial pulse. The value of pktcNcsEndPntConfigPulseDialMaxBreakTime MUST be greater than pktcNcsEndPntConfigPulseDialMinBreakTime. - This object MUST only be set via the configuration file - during the provisioning process." + This object MUST only be provided via the configuration + file during the provisioning process." DEFVAL { 75 } ::= { pktcNcsEndPntConfigEntry 38 } - pktcNcsEndPntConfigTxGain OBJECT-TYPE - SYNTAX Integer32 - UNITS "dB" - MAX-ACCESS read-create - STATUS current - DESCRIPTION - "This MIB Object represents the per line transmitter (A/D) - gain. A positive number reflects a signal gain, a negative - number reflects a signal loss. This MIB Object may provision - the gain or it may be used to document a non-provisionable - gain between the telco (POTS) a-b (T/R) terminals and the - analog codec maximum PCM coding limit (PCM maximum coding - limit). Based on the default G.711 Vocoder maximum of 3.14 - or 3.17 dBm the -4 dB gain default provides Vocoder coding - protection against TE maximum signals while also providing - an initial loss to minimize analog signal echo. " - DEFVAL { -4 } - ::= { pktcNcsEndPntConfigEntry 39 } - - pktcNcsEndPntConfigRxGain OBJECT-TYPE - SYNTAX Integer32 - UNITS "dB" - MAX-ACCESS read-create - STATUS current - DESCRIPTION - "This MIB Object represents the per line receiver (D/A) - gain. A positive number reflects a signal gain, a negative - number reflects a signal loss. This MIB Object may provision - the gain or it may be used to document a non-provisionable - gain for use with the pktcSigDevToneDbLevel Object to set - the desired level at the a-b (T/R) terminals. - - The default values are based on the deployed markets. Some - recommendations are made as follows: - - Based on the default G.711 Vocoder maximum of 3.14 or 3.17 - dBm a default value of '-4 dB' provides a maximum analog - signal level at the a-b (T/R) termination point - - Based on [ETSI TS 101 909-4], which provides guidance of - 11 dB loss (-11 dB gain), a default value of '-11 dB' is - recommended." - ::= { pktcNcsEndPntConfigEntry 40 } - -- -- notification group is for future extension. -- pktcSigNotification OBJECT IDENTIFIER ::= { pktcIetfSigMib 0 } pktcSigConformance OBJECT IDENTIFIER ::= { pktcIetfSigMib 2 } pktcSigCompliances OBJECT IDENTIFIER ::= { pktcSigConformance 1 } pktcSigGroups OBJECT IDENTIFIER ::= { pktcSigConformance 2 } -- -- compliance statements @@ -2628,86 +2620,146 @@ pktcInternationalGroup OBJECT-GROUP OBJECTS { pktcNcsEndPntConfigMinHookFlash, pktcNcsEndPntConfigMaxHookFlash, pktcNcsEndPntConfigPulseDialInterdigitTime, pktcNcsEndPntConfigPulseDialMinMakeTime, pktcNcsEndPntConfigPulseDialMaxMakeTime, pktcNcsEndPntConfigPulseDialMinBreakTime, pktcNcsEndPntConfigPulseDialMaxBreakTime, - pktcNcsEndPntConfigTxGain, - pktcNcsEndPntConfigRxGain, pktcSigDevRingCadence, pktcSigDevCallerIdSigProtocol, pktcSigDevCIDMode, pktcSigDevCIDFskAfterRing, pktcSigDevCIDFskAfterDTAS, pktcSigDevCIDFskAfterRPAS, pktcSigDevCIDRingAfterFSK, pktcSigDevCIDDTASAfterLR, pktcSigDevVmwiFskAfterDTAS, pktcSigDevVmwiFskAfterRPAS, pktcSigDevVmwiDTASAfterLR, pktcSigPowerRingFrequency, pktcSigPulseSignalFrequency, pktcSigPulseSignalDbLevel, pktcSigPulseSignalDuration, pktcSigPulseSignalPulseInterval, pktcSigPulseSignalRepeatCount, pktcSigDevToneDbLevel, pktcSigDevToneWholeToneRepeatCount, pktcSigDevToneSteady, - pktcSigDevToneNumFrequencies, - pktcSigDevToneFreqPriCompValue, - pktcSigDevToneFreqSecCompValue, - pktcSigDevToneFreqSecCompMode, - pktcSigDevToneFreqSecCompPrtg, + pktcSigDevToneFirstFreqValue, + pktcSigDevToneSecondFreqValue, + pktcSigDevToneThirdFreqValue, + pktcSigDevToneFourthFreqValue, + pktcSigDevToneFreqMode, + pktcSigDevToneFreqAmpModePrtg, pktcSigDevToneFreqOnDuration, pktcSigDevToneFreqOffDuration, pktcSigDevToneFreqRepeatCount } 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." ::= { pktcSigGroups 3 } END -6. Acknowledgments +6. Examples + This section provides a couple of examples, specifically related + to the MIB tables 'pktcSigDevToneTable' and + 'pktcSigDevMultiFreqToneTable'. + + Example A: Call waiting tone defined per ITU-T E.180: + + 1) 400 Hz AM modulated by 16 Hz, on for 500ms at -4 dBm + 2) 400 Hz AM modulated by 16 Hz, off for 400ms + 3) 400 Hz not AM modulated, on for 50 ms at -4 dBm + 4) 400 Hz not AM modulated, off for 450 ms + 5) 400 Hz not AM modulated, on for 50 ms at -4 dBm + 6) 400 Hz not AM modulated, off for 3450 ms + 7) 400 Hz not AM modulated, on for 50 ms at -4 dBm + 8) 400 Hz not AM modulated, off for 450 ms + 9) 400 Hz not AM modulated, on for 50 ms at -4 dBm + 10) 400 Hz not AM modulated, off for 3450 ms + 11) not repeated, not continuous + + Assume userDefined1(17) is assigned to this tone: + + pktcSigDevMultiFreqToneTable: + ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count + =================================================================== + 17 400 16 0 0 1 90 -40 500 400 0 + 17 400 0 0 0 2 0 -40 50 450 0 + 17 400 0 0 0 2 0 -40 50 3450 0 + 17 400 0 0 0 2 0 -40 50 450 0 + 17 400 0 0 0 2 0 -40 50 3450 0 + + pktcSigDevToneTable: + ToneType|ToneRep-Count|Steady + ============================= + 17 0 false(2) + + Example B - Congestion Tone - congestion(17): + + Note: This example of an embedded cadence is based on an operator + variation. + + 1) 400Hz on for 400ms -10 dBm + 2) 400Hz off for 350ms + 3) 400Hz on for 225ms -4 dBm + 4) 400Hz off for 525ms + 5) repeat (1) through (4) 5000 times or T0 timeout (which ever is + shortest period) + pktcSigDevMultiFreqToneTable: + ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count + =================================================================== + 17 400 0 0 0 2 0 -100 400 350 0 + 17 400 0 0 0 2 0 -40 225 525 0 + + pktcSigDevToneTable: + ToneType|ToneRep-Count|Steady + ============================= + 17 5000 false(0) + +7. Acknowledgments This document is a production of the PacketCable Working Group. - The current editors wish to express gratitude to: + The editors wish to express gratitude to: Angela Lyda Arris Interactive + Chad Griffiths Broadcom Corp. Eugene Nechamkin Broadcom Corp. - Jean-Francois Mule CableLabs, Inc. - Matt A. Osman CableLabs, Inc. + Jean-Francois Mule CableLabs(R) + Matt A. Osman CableLabs(R) Klaus Hermanns Cisco Systems, Inc. Rich Woundy Comcast Corp. Bert Wijnen Lucent Technologies - Phil Freyman Motorola, Inc. + Randy Presuhn Mindspring + Phillip Freyman Motorola, Inc. Rick Vetter Motorola, Inc. Sasha Medvinsky Motorola, Inc. Wim De Ketelaere tComLabs David De Reu tComLabs Kristof Sercu tComLabs Roy Spitzer Telogy Networks, Inc. Itay Sherman Texas Instruments, Inc. + Mauricio Sanchez Texas Instruments, Inc. + Shivakumar Thangapandi Texas Instruments, Inc. Mike Heard Consultant -7. Security Considerations +8. 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 environment without proper protection can have a negative effect on network operations. The following Differentiated Services Code Point (DSCP) and mask objects are used to differentiate between various types of traffic @@ -2778,44 +2830,48 @@ authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module 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. IANA Considerations +9. IANA Considerations The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry: Descriptor OBJECT IDENTIFIER Value ---------- ----------------------- pktcIetfSigMib { mib-2 XXX } - EditorÆs Note (to be removed prior to publication): the IANA is + Editor's Note (to be removed prior to publication): the IANA is requested to assign a value for XXX under the mib-2 subtree and to record the assignment in the SMI Numbers registry. When the assignment has been made, the RFC Editor is asked to replace XXX (here and in the MIB module) with the assigned value and to remove this note. -9. Normative References - - [PKT-SP-MIB-SIG-1.0] PacketCableÖ 1.0 Signaling MIB - Specification, PKT-SP-MIB-SIG-I08-040113, January 2004. +10. Normative References + [PKT-SP-MIB-SIG-1.0] PacketCable(TM) 1.0 Signaling MIB + Specification, Issued, PKT-SP-MIB-SIG-I09-050812, + August 2005. + http://www.packetcable.com/specifications/ + http://www.cablelabs.com/specifications/archives/ - [PKT-SP-MIB-SIG-1.5] PacketCableÖ 1.5 Signaling MIB - Specification, PKT-SP-MIB-SIG1.5-I01-050128, January - 2005. + [PKT-SP-MIB-SIG-1.5] PacketCable(TM) 1.5 Signaling MIB + Specification, Issued, PKT-SP-MIB-SIG1.5-I01-050128, + January 2005. + http://www.packetcable.com/specifications/ + http://www.cablelabs.com/specifications/archives/ [ITU-T-J169] IPCablecom Network Call Signaling (NCS) MIB requirements, J.169, ITU-T, March, 2001. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] 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 @@ -2855,67 +2911,73 @@ [PKT-SP-CODEC] Packetcable Audio/Video Codecs Specification PKT-SP-CODEC-IO5-040113. [PKT-SP-MGCP] Packetcable Network-Based Call Signaling Protocol Specification PKT-SP-EC-MGCP-I10-040402. [PKT-SP-PROV] Packetcable MTA Device Provisioning Specification PKT-SP-PROV-I10-040730. -10. Informative References +11. Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC3435] Andreasen, F., and B. Foster, "Media Gateway Control Protocol (MGCP)", RFC 3435, January 2003. - [PKT-SP-MIB-MTA] Packetcable MTA MIB Specification PKT-SP-MIB-MTA- - I09-040402. + [RFCXYZ] Nechamkin, E., and Mule J., "Multimedia Terminal Adapter + (MTA) Management Information Base for PacketCable and + IPCablecom compliant devices", RFCXYZ, . - [ETSI TS 101 909-4] ETSI TS 101 909-4:"Access and Terminals (AT); + Editor's Note (to be removed prior to publication): This is the + reference to 'draft-ietf-ipcdn-pktc-mtamib' which is expected to + accepted at the same time as this draft. When the draft is accepted, + the RFC Editor is asked to replace XYZ (and in the reference + earlier) with the assigned value and to remove this note. + + [ETSI-TS-101-909-4] 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 - Signaling Protocol". + Telecommunications Network; IP Multimedia Time Critical + Services; Part 4: Network Call Signaling Protocol". - [ETSI TS 101 909-9] ETSI TS 101 909-9:"Access and Terminals (AT); + [ETSI-TS-101-909-9] 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". + Telecommunications Network; IP Multimedia Time Critical + Services; Part 9: IPCablecom Network Call Signalling + (NCS) MIB Requirements". - [EN 300 001] 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 + [ETSI-EN-300-001] ETSI 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)". - [EN 300 324-1] EN 300 324-1 V2.1.1 (2000-04):"V Interfaces at the - digital Loop Exchange (LE); V5.1 interface for the - support of Access Network (AN); Part 1: V5.1 - interface specification". + [ETSI-EN-300-324-1] ETSI EN 300 324-1 V2.1.1 (2000-04):"V Interfaces + at the digital Loop Exchange (LE); V5.1 interface for the + support of Access Network (AN); Part 1: V5.1 interface + specification". - [EN 300 659-1] EN 300 659-1: "Public Switched Telephone Network - (PSTN); Subscriber line protocol over the local loop - for display (and related) services; Part 1: On hook + [ETSI-EN-300-659-1] ETSI EN 300 659-1: "Public Switched Telephone + Network (PSTN); Subscriber line protocol over the local + loop for display (and related) services; Part 1: On hook data transmission". - [ITU-T E.180] ITU-T: "Various Tones Used in National Networks, + [ITU-T-E.180] ITU-T E.180: "Various Tones Used in National Networks, Supplement 2 to Recommendation E.180". - [TR 101 183] TR 101 183: "Public Switched Telephone Network (PSTN) - Analogue Ringing Signals". + [ETSI-TR-101-183] ETSI TR-101-183: "Public Switched Telephone + Network (PSTN) Analogue Ringing Signals". Authors' Addresses Gordon Beacham Motorola, Inc. 6450 Sequence Drive, Bldg. 1 San Diego, CA 92121, USA +1 858-404-2335 gordon.beacham@motorola.com