idnits 2.17.1 draft-ietf-ipcdn-pktc-signaling-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2982. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2955. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2962. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2968. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 2974), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 38. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 3 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 2005) is 6822 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'ITU-T E.180' is defined on line 2916, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-T-J169' ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) -- Possible downref: Non-RFC (?) normative reference: ref. 'PKT-SP-CODEC' -- Possible downref: Non-RFC (?) normative reference: ref. 'PKT-SP-MGCP' -- Possible downref: Non-RFC (?) normative reference: ref. 'PKT-SP-PROV' Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Gordon Beacham 2 Motorola, Inc. 3 draft-ietf-ipcdn-pktc-signaling-08.txt Satish Kumar 4 Texas Instruments 5 Sumanth Channabasappa 6 CableLabs, Inc. 7 Expires: February 2005 August 2005 9 Network-Based Call Signaling (NCS) Signaling MIB for PacketCable and 10 IPCablecom Multimedia Terminal Adapters (MTAs) 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other Intellectual Property Rights (IPR) claims 16 of which he or she is aware have been or will be disclosed, and any 17 of which he or she becomes aware will be disclosed, in accordance 18 with Section 6 of RFC 3668. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other documents 27 at any time. It is inappropriate to use Internet-Drafts as 28 reference material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 Copyright Notice 38 Copyright (C) The Internet Society (2005). All Rights Reserved. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in the Internet community. 44 In particular, it provides a common data and format representation 45 for PacketCable and IPCablecom compliant Multimedia Terminal Adapter 46 devices. 48 This memo specifies a MIB module in a manner that is compliant to 49 the SNMP SMIv2. The set of objects are consistent with the SNMP 50 framework and existing SNMP standards. 52 Table of Contents 54 1. The Internet-Standard Management Framework...................23 55 2. Introduction.................................................23 56 3. Terminology...................................................3 57 3.1 MTA......................................................34 58 3.2 Endpoint.................................................34 59 3.3 L Line Package............................................4 60 3.4 E Line Package............................................4 61 4. Overview......................................................4 62 4.1 Structure of the MIB......................................5 63 4.2 pktcSigDevConfigObjects...................................5 64 4.3 pktcSigNotification.......................................7 65 4.4 pktcSigConformance........................................7 66 5. Definitions..................................................78 67 6. Acknowledgments............................................5662 68 7. Security Considerations....................................5662 69 8. IANA Considerations........................................5864 70 9. Normative References.......................................5864 71 10. Informative References....................................6065 72 Authors' Addresses............................................6166 73 Disclaimer of validity........................................6167 74 Full Copyright Statement......................................6267 76 1. The Internet-Standard Management Framework 78 For a detailed overview of the documents that describe the current 79 Internet-Standard Management Framework, please refer to section 7 of 80 RFC 3410 [RFC3410]. 82 Managed objects are accessed via a virtual information store, termed 83 the Management Information Base or MIB. MIB objects are generally 84 accessed through the Simple Network Management Protocol (SNMP). 85 Objects in the MIB are defined using the mechanisms defined in the 86 Structure of Management Information (SMI). This memo specifies a 87 MIBmodule that is compliant to the SMIv2, which is described in STD 88 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 89 2580 [RFC2580]. 91 2. Introduction 93 A multimedia terminal adapter (MTA) is used to deliver broadband 94 Internet, data, and/or voice access jointly with telephony service 95 to a subscriber's or customer's premises using a cable network 96 infrastructure. A MTA is normally installed at the customer's or 97 subscriber's premises, and it is coupled to a multiple system 98 operator (MSO) using a hybrid fiber coax (HFC) access network. 100 A MTA is provisioned by the MSO for broadband Internet, data, and/or 101 voice service. For more information on MTA provisioning refer to 102 [PKT-SP-PROV] and [PKT-SP-MIB-MTA]. MTA devices include one or more 103 endpoints (e.g., telephone ports) which receive call signaling 104 information to establish ring cadence, and codecs used for providing 105 telephony service. For more information on call signaling refer to 106 [PKT-SP-MGCP] and [RFC3435]. For more information on codecs refer to 107 [PKT-SP-CODEC]. 109 Telephone systems are typically very complex and often have a wide 110 distribution. It is therefore important for management systems to 111 support MTAs from multiple vendors at the same time, including those 112 from multiple countries. This MIB module provides objects suitable 113 for managing signaling for MTA devices in the widest possible range 114 of markets. 116 3. Terminology 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 120 "OPTIONAL", when used in the guidelines in this memo, are to be 121 interpreted as described in RFC 2119 [RFC2119]. 123 The terms "MIB module" and "information module" are used 124 interchangeably in this memo. As used here, both terms refer to any 125 of the three types of information modules defined in Section 3 of 126 RFC 2578 [RFC2578]. 128 3.1 MTA 130 A MTA is a PacketCable or IPCablecom compliant device providing 131 telephony services over a cable or hybrid system used to deliver 132 video signals to a community. It contains an interface to endpoints, 133 a network interface, codecs, and all signaling and encapsulation 134 functions required for Voice over IP transport, call signaling, and 135 Quality of Service signaling. A MTA can be an embedded or a 136 standalone device. An Embedded MTA (E-MTA) is a MTA device 137 containing an embedded Data Over Cable Service Interface 138 Specifications (DOCSIS) Cable Modem. A Standalone MTA (S-MTA) is a 139 MTA device separated from the DOCSIS Cable Modem by non-DOCSIS MAC 140 interface (e.g., Ethernet, USB). 142 3.2 Endpoint 143 An endpoint or MTA endpoint is a standard telephony physical port 144 located on the MTA and used for attaching the telephone device to 145 the MTA. 147 3.3 L Line Package 149 The L line package refers to the core signaling functionality as 150 defined by PacketCable and IPCablecom. An MTA provides all L package 151 elements, however the operator determines their application. 153 3.4 E Line Package 155 The E line package refers to extensions, over and above the core L 156 package, defined in support of international requirements. E line 157 package elements are optional, vary from country to country, and are 158 set by operator or regulatory requirements. 160 4. Overview 162 This MIB module provides a set of objects required for Signaling 163 PacketCable, European Telecommunications Standards Institute(ETSI), 164 and International Telecommunication Union Telecommunication 165 Standardization Sector (ITU-T) IPCablecom compliant Multimedia 166 Terminal Adapter (MTA) devices. The SIG MIB module is intended to 167 supersede various SIG MIB modules from which it is partly derived: 168 - the PacketCable 1.0 Signaling MIB Specification 169 [PKT-SP-MIB-SIG-1.0], 170 - the PacketCable 1.5 Signaling MIB Specification 171 [PKT-SP-MIB-SIG-1.5], 172 - the ITU-T IPCablecom SIG MIB requirements [ITU-T-J169], 173 - the ETSI SIG MIB [ETSI TS 101 909-9]. The ETSI SIG MIB 174 requirements also refer to various signal characteristics 175 defined in [EN 300 001], [EN 300 659-1], and [TR 101 183]. 176 Several normative and informative references are used to help define 177 NCS Signaling MIB objects. As a convention, wherever PacketCable and 178 IPCablecom requirements are equivalent, the PacketCable reference is 179 used in the object REFERENCE clause. IPCablecom compliant MTA 180 devices MUST use the equivalent IPCablecom references. 182 This MIB module describes the various Signaling MIB objects that are 183 directly related to the PacketCable MTA and the endpoints supported 184 on the MTA, each of which provides services independently. The 185 recognition and distinction of the endpoints is made by utilizing 186 the ifTable (IF-MIB), where each index (ifIndex) refers to a unique 187 endpoint. This MIB module also utilizes the syntax definition of the 188 Differentiated Services Code Point (DSCP) from DIFFSERV-DSCP-TC 189 [RFC3289] for signaling MIB objects to allow for differentiation 190 between various types of traffic in the service provider network. 192 This MIB module also utilizes SNMP management MIB architecture from 193 SNMP-FRAMEWORK-MIB [RFC3411]. 195 4.1 Structure of the MIB 197 This MIB is structured in three groups: 199 - Signaling information that control device and endpoint 200 configuration objects (pktcSigMibObjects) 202 - Signaling Notification object, that notifies the status 203 (pktcSigNotification) 205 - Signaling Conformance has mandatory signaling objects 206 (pktcSigConformance) 208 Each group of objects is explained in detail. 210 4.2 pktcSigDevConfigObjects 212 pktcSigDevEchoCancellation - This object identifies the capability 213 of echo cancellation on the device. 215 pktcSigDevSilenceSuppression - This object specifies if the device 216 is capable of silence suppression (Voice Activity Detection). 218 pktcSigDevR0Cadence - this object specifies ring cadence 0. 220 pktcSigDevR1Cadence - this object specifies ring cadence 1. 222 pktcSigDevR2Cadence - this object specifies ring cadence 2. 224 pktcSigDevR3Cadence - this object specifies ring cadence 3. 226 pktcSigDevR4Cadence - this object specifies ring cadence 4. 228 pktcSigDevR5Cadence - this object specifies ring cadence 5. 230 pktcSigDevR6Cadence - this object specifies ring cadence 6. 232 pktcSigDevR7Cadence - this object specifies ring cadence 7. 234 pktcSigDevRgCadence - this object specifies ring cadence for ringing 235 (rg). 237 pktcSigDevRsCadence - this object specifies ring cadence for ring 238 splash (rs). 240 pktcSigDefCallSigDscp - this object specifies the default value used 241 in the IP header for setting the Differentiated Services Code Point 242 (DSCP) value for call signaling. 244 pktcSigDefMediaStreamDscp - this object specifies the default value 245 used in the IP header for setting the Differentiated Services Code 246 Point (DSCP) value for media stream packets. 248 pktcSigCapabilityTable - this table specifies list of supported 249 signaling types, versions and vendor extensions for MTA. 251 pktcSigDefNcsReceiveUdpPort - this object contains the MTA User 252 Datagram Protocol (UDP) receive port that is being used for NCS call 253 signaling. 255 pktcSigDevCIDMode - this international object selects various modes 256 of caller id in common use. 258 pktcSigDevCIDFskAfterRing - this international object sets the delay 259 between the end of first ringing and the transmission of caller id 260 information. 262 pktcSigDevCIDFskAfterDTAS - this international object sets the delay 263 between the dual-tone alert signal and the transmission of caller id 264 information. 266 pktcSigDevCIDFskAfterRPAS - this international object sets the delay 267 between the ring pulse alert signal and the transmission of caller 268 id information. 270 pktcSigDevCIDRingAfterFSK - this international object sets the delay 271 between the transmission of caller id information and the first 272 ringing pattern. 274 pktcSigDevCIDDTASAfterLR - this international object sets the delay 275 between the end of a line reversal and the dual-tone alert signal. 277 pktcSigDevVmwiMode - this object selects various modes of visual 278 message waiting indicator service in common use. 280 pktcSigDevVmwiFskAfterDTAS - this international object sets the 281 delay between the dual-tone alert signal and the transmission of 282 visual message waiting information. 284 pktcSigDevVwmiFskAfterRPAS - this international object sets the 285 delay between the ring pulse alert signal and the transmission of 286 visual message waiting information. 288 pktcSigDevVwmiDTASAfterLR - this international object sets the delay 289 between the end of a line reversal and the dual-tone alert signal 290 for visual message waiting information. 292 pktcSigDevRingCadenceTable - this international object provides a 293 flexible structure within which to specify a variety of ring 294 cadences. 296 pktcSigDevToneTable - this international object specifies a flexible 297 structure within which to specify all of the tones used in the MTA. 299 pktcNcsEndPntConfigTable - this table describes the PacketCable NCS 300 endPoint configuration. The number of entries in this table 301 represents the number of provisioned endpoints. 303 pktcSigEndPntConfigTable - this table describes the PacketCable 304 endPoint selected signaling type. The number of entries in this 305 table represents the number of provisioned endpoints. 307 4.3 pktcSigNotification 309 pktcSigNotification - this object is used for signaling notification 310 and reserved for future use. 312 4.4 pktcSigConformance 314 pktcSigCompliances - this table has one object that has compliance 315 statements for devices that implement Signaling on the MTA. 317 pktcSigGroups - this table contains group of objects for the common 318 portion of the PacketCable NCS and Signaling MIB. 320 pktcInternationalGroup - this table extends this MIB Module by 321 establishing a set of objects designed to support operations over 322 the widest possible range of markets. 324 5. Definitions 326 PKTC-IETF-SIG-MIB DEFINITIONS ::= BEGIN 328 IMPORTS 329 MODULE-IDENTITY, 330 OBJECT-TYPE, 331 Integer32, 332 Unsigned32, 333 mib-2 334 FROM SNMPv2-SMI 335 InetAddressType, 336 InetAddress, 337 InetPortNumber 338 FROM INET-ADDRESS-MIB 339 TEXTUAL-CONVENTION, 340 RowStatus, 341 TruthValue 342 FROM SNMPv2-TC 343 OBJECT-GROUP, 344 MODULE-COMPLIANCE 345 FROM SNMPv2-CONF 346 SnmpAdminString 347 FROM SNMP-FRAMEWORK-MIB 348 ifIndex 349 FROM IF-MIB 350 Dscp 351 FROM DIFFSERV-DSCP-TC; 353 pktcIetfSigMib MODULE-IDENTITY 354 LAST-UPDATED "200502200000Z" -- February 20, 2005 355 ORGANIZATION "IETF IPCDN Working Group" 356 CONTACT-INFO 357 "Gordon Beacham 358 Motorola, Inc. 359 6450 Sequence Drive, Bldg. 1 360 San Diego, CA 92121, USA 361 Phone: +1 858-404-2335 362 Email: gordon.beacham@motorola.com 364 Sumanth Channabasappa 365 Cable Television Laboratories, Inc. 366 858 Coal Creek Circle, 367 Louisville, CO 80027, USA 368 Phone: +1 303-661-3307 369 Email: Sumanth@cablelabs.com 371 Satish Kumar Mudugere Eswaraiah 372 Texas Instruments India (P) Ltd., 373 Golf view, Wind Tunnel Road 374 Murugesh Palya 375 Bangalore 560 017, INDIA 376 Phone: +91 80 5269451 377 Email: satish.kumar@ti.com 379 IETF IPCDN Working Group 380 General Discussion: ipcdn@ietf.org 381 Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn 382 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 383 Co-Chair: Jean-Francois Mule, jf.mule@cablelabs.com 384 Co-Chair: Richard Woundy, Richard_Woundy@cable.comcast.com" 386 DESCRIPTION 387 "This MIB module supplies the basic management 388 object for the PacketCable and IPCablecom Signaling 389 protocols. This version of the MIB includes 390 common signaling and Network Call Signaling 391 (NCS) related signaling objects. 393 Copyright (C) The Internet Society (2005). This version of 394 this MIB module is part of RFC yyyy; see the RFC itself for 395 full legal notices." 396 -- RFC Ed: replace yyyy with actual RFC number and remove this note 398 REVISION "200502200000Z" 400 DESCRIPTION 401 "Initial version, published as RFC yyyy." 402 -- RFC Ed: replace yyyy with actual RFC number and remove this note 404 ::= { mib-2 XXX } 405 -- RFC Ed: replace XXX with IANA-assigned number and remove this 406 -- note 408 -- Textual Conventions 410 TenthdBm ::= TEXTUAL-CONVENTION 411 DISPLAY-HINT "d-1" 412 STATUS current 413 DESCRIPTION 414 "This textual convention represents power levels that are 415 normally expressed in dBm. Units are in tenths of a dBm; 416 for example, -13.5 dBm will be represented as -135." 417 SYNTAX Integer32 419 PktcCodecType ::= TEXTUAL-CONVENTION 420 STATUS current 421 DESCRIPTION 422 " This textual convention defines various types of codecs 423 that MAY be supported. The description for each 424 enumeration is listed below: 425 Enumeration Description 426 other a defined codec not in the enumeration 427 unknown a codec not defined in PacketCable 428 g729 ITU-T Recommendation G.722 429 reserved for future use 430 g729E ITU-T Recommendation G.729E 431 pcmu Pulse Code Modulation u-law (PCMU) 432 g726at32 ITU-T Recommendation G.726-32 (32 kbit/s) 433 g728 ITU-T Recommendation G.728 434 pcma Pulse Code Modulation a-law (PCMA) 435 g726at16 ITU-T Recommendation G.726-16 (16 kbit/s) 436 g726at24 ITU-T Recommendation G.726-24 (24 kbit/s) 437 g726at40 ITU-T Recommendation G.726-40 (40 kbit/s) 438 ilbc internet low bit rate codec 439 bv16 BroadVoice16 440 . The list of codecs is consistent with the IETF 441 Real Time Transport Protocol (RTP) Profile registry and 442 the RTP Map Parameters Table in [PKT-SP-CODEC]. The 443 literal codec name for each codec is listed below: 444 Codec Literal Codec Name 445 g729 G729 446 g729E G729E 447 pcmu PCMU 448 g726at32 G726-32 449 g728 G728 450 pcma PCMA 451 g726at16 G726-16 452 g726at24 G726-24 453 g726at40 G726-40 454 ilbc iLBC 455 bv16 BV16 456 The literal codec name is the second column of the table 457 with codec RTP Map Parameters. Literal Codec Name Column 458 contains the codec name used in the local connection 459 options (LCO) of the NCS messages create connection 460 (CRCX)/modify connection (MDCX) and is also used to 461 identify the codec in the Call Management System (CMS) 462 Provisioning Specification. RTP Map Parameter Column of 463 the Table contains the string used in the media attribute 464 line (a=) of the session description protocol (SDP) 465 parameters in NCS messages." 466 SYNTAX INTEGER { 467 other (1), 468 unknown (2), 469 g729 (3), 470 reserved (4), 471 g729E (5), 472 pcmu (6), 473 g726at32 (7), 474 g728 (8), 475 pcma (9), 476 g726at16 (10), 477 g726at24 (11), 478 g726at40 (12), 479 ilbc (13), 480 bv16 (14) 481 } 483 PktcRingCadence ::= TEXTUAL-CONVENTION 484 STATUS current 485 DESCRIPTION 486 "This object provides an encoding scheme for ring 487 cadences, including repeatability characteristics. All 488 fields in this object MUST be encoded in network-byte 489 order. 491 The first three higher order octets are reserved. The 492 octets that follow are used to encode a 'bit-string', with 493 each bit corresponding to 50 milliseconds. A bit value of 494 '1' indicates the presence of a ring-tone and a bit value 495 of '0' indicates the absence of a ring-tone, for that 496 duration (50 ms) (Note: A minimum number of octets 497 required to encode the bit-string MUST be used). 499 The first two of the reserved octets MUST indicate the 500 length of the encoded cadence (in bits) and MUST range 501 between 1 and 264. (Note: The length in bits MUST also be 502 consistent with the number of octets that encode the 503 cadence). The MTA MUST ignore any unused bits in the last 504 octet, but MUST reflect the value as provided on 505 subsequent SNMP GETs. 507 The third of the reserved octets indicates 'repeatability' 508 and MUST be either 0x80 or 0x00 - the former value 509 indicating 'non-repeatability' and the latter indicating 510 'repeatability'. 512 The MTA MUST reject attempts to set a value that violates 513 any of the above requirements" 515 SYNTAX OCTET STRING (SIZE(4..36)) 517 PktcSigType ::= TEXTUAL-CONVENTION 518 STATUS current 519 DESCRIPTION 520 " This object lists the various types of signaling that may 521 be supported: 522 other - set when signaling other than ncs is used 523 reserved - for future use 524 ncs - Network call signaling is a derivation of MGCP 525 (Media Gateway Control Protocol) defined for 526 IPCablecom/PacketCable MTAs." 527 SYNTAX INTEGER { 528 other(1), 529 reserved(2), 530 ncs(3) 532 } 534 pktcSigMibObjects OBJECT IDENTIFIER ::= { pktcIetfSigMib 1 } 535 pktcSigDevConfigObjects OBJECT IDENTIFIER ::= 536 { pktcSigMibObjects 1 } 537 pktcNcsEndPntConfigObjects OBJECT IDENTIFIER ::= 538 { pktcSigMibObjects 2 } 539 -- 540 -- The codec table (pktcSigDevCodecTable) defines all combinations 541 -- of codecs supported by the Multimedia Terminal Adapter (MTA). 542 -- 543 pktcSigDevCodecTable OBJECT-TYPE 544 SYNTAX SEQUENCE OF PktcSigDevCodecEntry 545 MAX-ACCESS not-accessible 546 STATUS current 547 DESCRIPTION 548 " This table describes the MTA supported codec types. A MTA 549 MUST populate this table with all possible combinations of 550 codecs it supports for simultaneous operation. For 551 example, a MTA with two endpoints may be designed with a 552 particular DSP and memory architecture that allows it to 553 support the following fixed combinations of codecs for 554 simultaneous operation: 556 Codec Type Maximum Number of Simultaneous Codecs 557 PCMA 3 559 PCMA 2 560 PCMU 1 562 PCMA 1 563 PCMU 2 565 PCMU 3 567 PCMA 1 568 G729 1 570 G729 2 572 PCMU 1 573 G729 1 575 Based on this example, the entries in the codec table 576 would be: 578 CodecComboIndex pktcSigDevCodecType pktcSigDevCodecMax 579 1 pcma 3 580 2 pcma 2 581 2 pcmu 1 582 3 pcma 1 583 3 pcmu 2 584 4 pcmu 3 585 5 pcma 1 586 5 g729 1 587 6 g729 2 588 7 pcmu 1 589 7 g729 1 591 An operator querying this table is able to determine all 592 possible codec combinations the MTA is capable of 593 simultaneously supporting. 594 This table MUST NOT include non-voice codecs." 595 ::= { pktcSigDevConfigObjects 1 } 597 pktcSigDevCodecEntry OBJECT-TYPE 598 SYNTAX PktcSigDevCodecEntry 599 MAX-ACCESS not-accessible 600 STATUS current 601 DESCRIPTION 602 "Each entry represents the maximum number of active 603 connections with a particular codec the MTA is capable of 604 supporting. Each row is indexed by a composite key 605 consisting of a number enumerating the particular codec 606 combination and the codec type." 607 INDEX { pktcSigDevCodecComboIndex, pktcSigDevCodecType } 608 ::= { pktcSigDevCodecTable 1 } 610 PktcSigDevCodecEntry ::= SEQUENCE { 611 pktcSigDevCodecComboIndex Unsigned32, 612 pktcSigDevCodecType PktcCodecType, 613 pktcSigDevCodecMax Unsigned32 614 } 616 pktcSigDevCodecComboIndex OBJECT-TYPE 617 SYNTAX Unsigned32 (1..255) 618 MAX-ACCESS not-accessible 619 STATUS current 620 DESCRIPTION 621 " The index value which enumerates a particular codec 622 combination in the pktcSigDevCodecTable." 623 ::= { pktcSigDevCodecEntry 1 } 625 pktcSigDevCodecType OBJECT-TYPE 626 SYNTAX PktcCodecType 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION 630 " A codec type supported by this MTA." 631 ::= { pktcSigDevCodecEntry 2 } 633 pktcSigDevCodecMax OBJECT-TYPE 634 SYNTAX Unsigned32(1..255) 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 " The maximum number of simultaneous sessions of a 639 particular codec that the MTA can support." 640 ::= { pktcSigDevCodecEntry 3 } 642 -- 643 -- These are the common signaling related definitions that affect 644 -- the entire MTA device. 645 -- 647 pktcSigDevEchoCancellation OBJECT-TYPE 648 SYNTAX TruthValue 649 MAX-ACCESS read-only 650 STATUS current 651 DESCRIPTION 652 " This object specifies if the device is capable of echo 653 cancellation." 654 ::= { pktcSigDevConfigObjects 2 } 656 pktcSigDevSilenceSuppression OBJECT-TYPE 657 SYNTAX TruthValue 658 MAX-ACCESS read-only 659 STATUS current 660 DESCRIPTION 661 " This object specifies if the device is capable of 662 silence suppression (Voice Activity Detection)." 663 ::= { pktcSigDevConfigObjects 3 } 665 pktcSigDevCallerIdSigProtocol OBJECT-TYPE 666 SYNTAX INTEGER { 667 fsk (1), 668 dtmf (2) 669 } 670 MAX-ACCESS read-write 671 STATUS current 672 DESCRIPTION 673 "This object identifies the subscriber line protocol used 674 for signaling on-hook caller id information. Different 675 countries define different caller id signaling protocols to 676 support caller identification. Frequency shift keying (FSK) 677 is most commonly used. Dual tone multi-frequency (DTMF) 678 is an alternative." 679 REFERENCE 680 "EN 300 659-1 Specification" 681 DEFVAL { fsk } 682 ::= { pktcSigDevConfigObjects 4 } 684 pktcSigDevR0Cadence OBJECT-TYPE 685 SYNTAX PktcRingCadence 686 MAX-ACCESS read-write 687 STATUS current 688 DESCRIPTION 689 " This object specifies ring cadence 0 (a user defined 690 field). This object is required for the L line package." 691 ::= { pktcSigDevConfigObjects 5 } 693 pktcSigDevR1Cadence OBJECT-TYPE 694 SYNTAX PktcRingCadence 695 MAX-ACCESS read-write 696 STATUS current 697 DESCRIPTION 698 " This object specifies ring cadence 1 (a user defined 699 field). This object is required for the L line package." 700 ::= { pktcSigDevConfigObjects 6 } 702 pktcSigDevR2Cadence OBJECT-TYPE 703 SYNTAX PktcRingCadence 704 MAX-ACCESS read-write 705 STATUS current 706 DESCRIPTION 707 " This object specifies ring cadence 2 (a user defined 708 field). This object is required for the L line package." 709 ::= { pktcSigDevConfigObjects 7 } 711 pktcSigDevR3Cadence OBJECT-TYPE 712 SYNTAX PktcRingCadence 713 MAX-ACCESS read-write 714 STATUS current 715 DESCRIPTION 716 " This object specifies ring cadence 3 (a user defined 717 field). This object is required for the L line package." 718 ::= { pktcSigDevConfigObjects 8 } 720 pktcSigDevR4Cadence OBJECT-TYPE 721 SYNTAX PktcRingCadence 722 MAX-ACCESS read-write 723 STATUS current 724 DESCRIPTION 725 " This object specifies ring cadence 4 (a user defined 726 field). This object is required for the L line package." 727 ::= { pktcSigDevConfigObjects 9 } 729 pktcSigDevR5Cadence OBJECT-TYPE 730 SYNTAX PktcRingCadence 731 MAX-ACCESS read-write 732 STATUS current 733 DESCRIPTION 734 " This object specifies ring cadence 5 (a user defined 735 field). This object is required for the L line package." 736 ::= { pktcSigDevConfigObjects 10 } 738 pktcSigDevR6Cadence OBJECT-TYPE 739 SYNTAX PktcRingCadence 740 MAX-ACCESS read-write 741 STATUS current 742 DESCRIPTION 743 " This object specifies ring cadence 6 (a user defined 744 field). This object is required for the L line package." 745 ::= { pktcSigDevConfigObjects 11 } 747 pktcSigDevR7Cadence OBJECT-TYPE 748 SYNTAX PktcRingCadence 749 MAX-ACCESS read-write 750 STATUS current 751 DESCRIPTION 752 " This object specifies ring cadence 7 (a user defined 753 field). This object is required for the L line package." 754 ::= { pktcSigDevConfigObjects 12 } 756 pktcSigDevRgCadence OBJECT-TYPE 757 SYNTAX PktcRingCadence 758 MAX-ACCESS read-write 759 STATUS current 760 DESCRIPTION 761 " This object specifies ring cadence rg (a user defined 762 field). This object is required for the L line package." 763 ::= { pktcSigDevConfigObjects 13 } 765 pktcSigDevRsCadence OBJECT-TYPE 766 SYNTAX PktcRingCadence 767 MAX-ACCESS read-write 768 STATUS current 769 DESCRIPTION 770 " This object specifies ring cadence rs (a user defined 771 field) The MTA MUST reject any attempt to make this object 772 repeatable. This object is required for the L line 773 package." 774 ::= { pktcSigDevConfigObjects 14 } 776 pktcSigDefCallSigDscp OBJECT-TYPE 777 SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC 778 MAX-ACCESS read-write 779 STATUS current 780 DESCRIPTION 781 " The default value used in the IP header for setting the 782 Differentiated Services Code Point (DSCP) value for call 783 signaling." 784 DEFVAL { 0 } 785 ::= { pktcSigDevConfigObjects 15 } 787 pktcSigDefMediaStreamDscp OBJECT-TYPE 788 SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC 789 MAX-ACCESS read-write 790 STATUS current 791 DESCRIPTION 792 " This object contains the default value used in the IP 793 header for setting the Differentiated Services Code Point 794 (DSCP) value for media stream packets. The MTA MUST NOT 795 update this object with the value supplied by the CMS in 796 the NCS messages (if present). Any currently active 797 connections are not affected by updates to this object. 798 When the value of this object is updated by SNMP, the MTA 799 MUST use the new value as a default starting only from 800 new connections." 801 DEFVAL { 0 } 802 ::= { pktcSigDevConfigObjects 16 } 804 -- 805 -- pktcSigCapabilityTable - This table defines the valid signaling 806 -- types supported by this MTA. 807 -- 809 pktcSigCapabilityTable OBJECT-TYPE 810 SYNTAX SEQUENCE OF PktcSigCapabilityEntry 811 MAX-ACCESS not-accessible 812 STATUS current 813 DESCRIPTION 814 " This table describes the signaling types supported by this 815 MTA." 816 ::= { pktcSigDevConfigObjects 17 } 818 pktcSigCapabilityEntry OBJECT-TYPE 819 SYNTAX PktcSigCapabilityEntry 820 MAX-ACCESS not-accessible 821 STATUS current 822 DESCRIPTION 823 " Entries in pktcMtaDevSigCapabilityTable - List of 824 supported signaling types, versions and vendor extensions 825 for this MTA. Each entry in the list provides for one 826 signaling type and version combination. If the device 827 supports multiple versions of the same signaling type it 828 will require multiple entries." 829 INDEX { pktcSignalingIndex } 830 ::= { pktcSigCapabilityTable 1 } 832 PktcSigCapabilityEntry ::= SEQUENCE { 833 pktcSignalingIndex Unsigned32, 834 pktcSignalingType PktcSigType, 835 pktcSignalingVersion SnmpAdminString, 836 pktcSignalingVendorExtension SnmpAdminString 837 } 839 pktcSignalingIndex OBJECT-TYPE 840 SYNTAX Unsigned32 (1..255) 841 MAX-ACCESS not-accessible 842 STATUS current 843 DESCRIPTION 844 " The index value which uniquely identifies an entry in the 845 pktcSigCapabilityTable." 846 ::= { pktcSigCapabilityEntry 1 } 848 pktcSignalingType OBJECT-TYPE 849 SYNTAX PktcSigType 850 MAX-ACCESS read-only 851 STATUS current 852 DESCRIPTION 853 " This object identifies the type of signaling used. This 854 value has to be associated with a single signaling 855 version." 856 ::= { pktcSigCapabilityEntry 2 } 858 pktcSignalingVersion OBJECT-TYPE 859 SYNTAX SnmpAdminString 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 " Provides the version of the signaling type - reference 864 pktcSignalingType. Examples would be 1.0 or 2.33 etc." 865 ::= { pktcSigCapabilityEntry 3 } 867 pktcSignalingVendorExtension OBJECT-TYPE 868 SYNTAX SnmpAdminString 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 " The vendor extension allows vendors to provide a list of 873 additional capabilities, vendors can decide how to encode 874 these extensions, although space separated text is 875 suggested." 876 ::= { pktcSigCapabilityEntry 4 } 878 pktcSigDefNcsReceiveUdpPort OBJECT-TYPE 879 SYNTAX InetPortNumber (1025..65535) 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 " This object contains the MTA User Datagram Protocol (UDP) 884 receive port that is being used for NCS call signaling. 885 This object should only be changed by the configuration 886 file." 887 REFERENCE 888 "PacketCable NCS Specification" 889 DEFVAL { 2427 } 890 ::= { pktcSigDevConfigObjects 18 } 892 pktcSigPowerRingFrequency OBJECT-TYPE 893 SYNTAX INTEGER { 894 f20Hz(1), 895 f25Hz(2), 896 f33Point33Hz(3), 897 f50Hz(4), 898 f15Hz(5), 899 f16Hz(6), 900 f22Hz(7), 901 f23Hz(8), 902 f45Hz(9) 903 } 904 UNITS "Hertz" 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 " This object must only be set via the configuration file 909 during the provisioning process. The power ring frequency 910 is the frequency at which the sinusoidal voltage must 911 travel down the twisted pair to make terminal equipment 912 ring. Different countries define different electrical 913 characteristics to make terminal equipment ring. The f20Hz 914 setting corresponds to a power ring frequency of 20 Hertz. 915 The f25Hz setting corresponds to a power ring frequency of 916 25 Hertz. The f33Point33Hz setting corresponds to a power 917 ring frequency of 33.33 Hertz. The f50Hz setting 918 corresponds to a power ring frequency of 50 Hertz. The 919 f15Hz setting corresponds to a power ring frequency of 15 920 Hertz. The f16Hz setting corresponds to a power ring 921 frequency of 16 Hertz. The f22Hz setting corresponds to a 922 power ring frequency of 22 Hertz. The f23Hz setting 923 corresponds to a power ring frequency of 23 Hertz. The 924 f45Hz setting corresponds to a power ring frequency of 45 925 Hertz. 926 " 927 REFERENCE 928 "EN 300 001 contains a list of frequency ranges that 929 are defined for each country." 930 DEFVAL { f20Hz } 931 ::= { pktcSigDevConfigObjects 19 } 933 pktcSigPulseSignalTable OBJECT-TYPE 934 SYNTAX SEQUENCE OF PktcSigPulseSignalEntry 935 MAX-ACCESS not-accessible 936 STATUS current 937 DESCRIPTION 938 " The Pulse signal table defines the pulse signal operation. 939 There are nine types of international pulse signals, 940 with each signal having a set of provisionable parameters. 941 The values of the MIB objects in this table take effect 942 only if these parameters are not defined via signaling, in 943 which case the latter determines the values of the 944 parameters. This object is required for the E line 945 package. Signals defined in this table are triggered using 946 the E line package. 947 Objects in this table do not persist across MTA reboots." 948 REFERENCE 949 "TS 101 909-4 Specification" 950 ::= { pktcSigDevConfigObjects 20 } 952 pktcSigPulseSignalEntry OBJECT-TYPE 953 SYNTAX PktcSigPulseSignalEntry 954 MAX-ACCESS not-accessible 955 STATUS current 956 DESCRIPTION 957 " This object defines the set of parameters associated with 958 each particular value of pktcSigPulseSignalType. Each 959 entry in the pktcSigPulseSignalTable is indexed by the 960 pktcSigPulseSignalType object." 961 INDEX { pktcSigPulseSignalType } 962 ::= { pktcSigPulseSignalTable 1 } 964 PktcSigPulseSignalEntry ::= SEQUENCE { 965 pktcSigPulseSignalType INTEGER, 966 pktcSigPulseSignalFrequency INTEGER, 967 pktcSigPulseSignalDbLevel TenthdBm, 968 pktcSigPulseSignalDuration Unsigned32, 969 pktcSigPulseSignalPulseInterval Unsigned32, 970 pktcSigPulseSignalRepeatCount Unsigned32 971 } 973 pktcSigPulseSignalType OBJECT-TYPE 974 SYNTAX INTEGER 975 { 976 initialRing(1), 977 pulseLoopClose(2), 978 pulseLoopOpen(3), 979 enableMeterPulse(4), 980 meterPulseBurst(5), 981 pulseNoBattery(6), 982 pulseNormalPolarity(7), 983 pulseReducedBattery(8), 984 pulseReversePolarity(9) 985 } 986 MAX-ACCESS not-accessible 987 STATUS current 988 DESCRIPTION 989 "There are nine types of international pulse signals. These 990 signals are defined as follows: 991 initial ring 992 pulse loop close 993 pulse loop open 994 enable meter pulse 995 meter pulse burst 996 pulse no battery 997 pulse normal polarity 998 pulse reduced battery 999 pulse reverse polarity" 1000 REFERENCE 1001 "EN 300 324-1 Specification" 1003 ::= { pktcSigPulseSignalEntry 1 } 1005 pktcSigPulseSignalFrequency OBJECT-TYPE 1006 SYNTAX INTEGER { 1007 twentyfive (1), 1008 twelvethousand(2), 1009 sixteenthousand(3) 1010 } 1011 UNITS "Hertz" 1012 MAX-ACCESS read-write 1013 STATUS current 1014 DESCRIPTION 1015 " This object is only applicable to the initialRing, 1016 enableMeterPulse, and meterPulseBurst signal type. This 1017 object identifies the frequency of the generated signal. 1018 The following table defines the default values for this 1019 object depending on signal type: 1020 pktcSigPulseSignalType Default 1021 initialRing 25 1022 enableMeterPulse 16000 1023 meterPulseBurst 16000 1024 The value of twentyfive MUST only be used for the 1025 initialRing signal type. The values of twelvethousand and 1026 sixteenthousand MUST only be used for enableMeterPulse and 1027 meterPulseBurst signal types. An attempt to set this 1028 object while the value of pktcSigPulseSignalType is not 1029 initialRing,enableMeterPulse, or meterPulseBurst will 1030 result in an inconsistentValue error." 1031 REFERENCE 1032 "EN 300 001 Specification" 1033 ::= { pktcSigPulseSignalEntry 2} 1035 pktcSigPulseSignalDbLevel OBJECT-TYPE 1036 SYNTAX TenthdBm (-350..0) 1037 UNITS "dBm" 1038 MAX-ACCESS read-write 1039 STATUS current 1040 DESCRIPTION 1041 " This object is only applicable to the enableMeterPulse and 1042 meterPulseBurst signal types. This is the decibel level 1043 for each frequency at which tones could be generated at 1044 the a and b terminals (TE connection point). An attempt to 1045 set this object while the value of pktcSigPulseSignalType 1046 is not enableMeterPulse, or meterPulseBurst will result in 1047 an inconsistentValue error." 1048 REFERENCE 1049 "EN 300 001 Specification" 1050 DEFVAL { -135 } 1051 ::={pktcSigPulseSignalEntry 3 } 1053 pktcSigPulseSignalDuration OBJECT-TYPE 1054 SYNTAX Unsigned32 (0..5000) 1055 UNITS "Milliseconds" 1056 MAX-ACCESS read-write 1057 STATUS current 1058 DESCRIPTION 1059 " This object specifies the pulse duration for each 1060 signal type. In addition, the MTA must accept the values 1061 in the incremental steps specific for each signal type. 1062 The following table defines the default values and the 1063 incremental steps for this object depending on the signal 1064 type. 1065 pktcSigPulseSignaltype Default (ms) Increment (ms) 1066 initialRing 200 50 1067 pulseLoopClose 200 10 1068 pulseLoopOpen 200 10 1069 enableMeterPulse 150 10 1070 meterPulseBurst 150 10 1071 pulseNoBattery 200 10 1072 pulseNormalPolarity 200 10 1073 pulseReducedBattery 200 10 1074 pulseReversePolarity 200 10 1075 An attempt to set this object to a value that does not 1076 fall on one of the increment boundaries, or on the wrong 1077 increment boundary for the specific signal type will 1078 result in an inconsistentValue error." 1079 REFERENCE 1080 "EN 300 324-1 Specification" 1081 ::= {pktcSigPulseSignalEntry 4 } 1083 pktcSigPulseSignalPulseInterval OBJECT-TYPE 1084 SYNTAX Unsigned32 (0..5000) 1085 UNITS "Milliseconds" 1086 MAX-ACCESS read-write 1087 STATUS current 1088 DESCRIPTION 1089 " This object specifies the repeat interval, or the period 1090 for each signal type. In addition, the MTA must accept 1091 the values in the incremental steps specific for each 1092 signal type. The following table defines the default 1093 values and the incremental steps for this object depending 1094 on the signal type. 1095 pktcSigPulseSignaltype Default (ms) Increment (ms) 1096 initialRing 200 50 1097 pulseLoopClose 1000 10 1098 pulseLoopOpen 1000 10 1099 enableMeterPulse 1000 10 1100 meterPulseBurst 1000 10 1101 pulseNoBattery 1000 10 1102 pulseNormalPolarity 1000 10 1103 pulseReducedBattery 1000 10 1104 pulseReversePolarity 1000 10 1105 An attempt to set this object to a value that does not 1106 fall on one of the increment boundaries, or on the wrong 1107 increment boundary for the specific signal type will 1108 result in an inconsistentValue error." 1109 REFERENCE 1110 "EN 300 324-1 Specification" 1111 ::= { pktcSigPulseSignalEntry 5} 1113 pktcSigPulseSignalRepeatCount OBJECT-TYPE 1114 SYNTAX Unsigned32 1115 MAX-ACCESS read-write 1116 STATUS current 1117 DESCRIPTION 1118 " This object specifies how many times to repeat a pulse. 1119 This object is not used by the enableMeterPulse signal 1120 type and as such must have a value of zero. The following 1121 table defines the default values and the valid ranges for 1122 this object depending on the signal type. 1123 pktcSigPulseSignaltype Default Range 1124 initialRing 1 1-5 1125 pulseLoopClose 1 1-50 1126 pulseLoopOpen 1 1-50 1127 enableMeterPulse 0 Not Used 1128 meterPulseBurst 1 1-50 1129 pulseNoBattery 1 1-50 1130 pulseNormalPolarity 1 1-50 1131 pulseReducedBattery 1 1-50 1132 pulseReversePolarity 1 1-50 1133 An attempt to set this object to a value that does not 1134 fall within the range (or is not used) for the specific 1135 signal type will result in an inconsistentValue error." 1136 ::={ pktcSigPulseSignalEntry 6 } 1138 pktcSigDevCIDMode OBJECT-TYPE 1139 SYNTAX INTEGER { 1140 duringRingingETS(1), 1141 dtAsETS(2), 1142 rpAsETS(3), 1143 lrAsETS(4) 1144 } 1145 MAX-ACCESS read-write 1146 STATUS current 1147 DESCRIPTION 1148 " This object is required only for Euro-PacketCable. 1149 For on-hook Caller ID, pktcSigDevCIDMode selects the 1150 method of Caller ID. For the duringRingingETS method, the 1151 Frequency Shift Keying (FSK) containing the Caller ID 1152 information is sent between the first and second ring 1153 pattern. For the dtAsETS,rpAsETS, and lrAsETS methods, the 1154 FSK containing the Caller ID information is sent before 1155 the first ring pattern. For the dtAsETS method, the FSK is 1156 sent after the Dual Tone Alert Signal. For the rpAsETS 1157 method, the FSK is sent after a Ring Pulse. For the 1158 lrAsETS method, the Line Reversal occurs first, then the 1159 Dual Tone Alert Signal, and finally the FSK is sent." 1160 DEFVAL { rpAsETS} 1161 ::= {pktcSigDevConfigObjects 21 } 1163 pktcSigDevCIDFskAfterRing OBJECT-TYPE 1164 SYNTAX Unsigned32 (50..2000) 1165 UNITS "Milliseconds" 1166 MAX-ACCESS read-write 1167 STATUS current 1168 DESCRIPTION 1169 " This object is required only for Euro-PacketCable. This 1170 object specifies the delay between the end of first 1171 ringing pattern and the start of the transmission of the 1172 FSK containing the Caller ID information. It is only used 1173 when pktcSigDevCIDMode is duringRingingETS. The following 1174 table defines the default values for this object depending 1175 on signal type: 1176 pktcSigDevCIDMode Default 1177 duringringingETS 550 ms 1178 dtAsETS not used 1179 rpAsETS not used 1180 lrAsETS not used 1181 An attempt to set this object while the value of 1182 pktcSigDevCIDMode is not duringringingETS will result in 1183 an inconsistentValue error." 1184 REFERENCE 1185 "EN 300 659-1 Specification" 1186 DEFVAL { 550 } 1187 ::= {pktcSigDevConfigObjects 22 } 1189 pktcSigDevCIDFskAfterDTAS OBJECT-TYPE 1190 SYNTAX Unsigned32 (45..500) 1191 UNITS "Milliseconds" 1192 MAX-ACCESS read-write 1193 STATUS current 1194 DESCRIPTION 1195 " This object is required only for Euro-PacketCable. This 1196 object specifies the delay between the end of the Dual 1197 Tone Alert Signal (DT-AS) and the start of the 1198 transmission of the FSK containing the Caller ID 1199 information. This object is only used when 1200 pktcSigDevCIDMode is dtAsETS or lrAsETS. The following 1201 table defines the default values for this object depending 1202 on signal type: 1203 pktcSigDevCIDMode Default 1204 duringringingETS not used 1205 dtAsETS 50 ms 1206 rpAsETS not used 1207 lrAsETS 50 ms 1208 An attempt to set this object while the value of 1209 pktcSigDevCIDMode is not dtAsETS or lrAsETS will result in 1210 an inconsistentValue error." 1211 REFERENCE 1212 "EN 300 659-1 Specification" 1214 DEFVAL { 50 } 1215 ::= {pktcSigDevConfigObjects 23 } 1217 pktcSigDevCIDFskAfterRPAS OBJECT-TYPE 1218 SYNTAX Unsigned32 (500..800) 1219 UNITS "Milliseconds" 1220 MAX-ACCESS read-write 1221 STATUS current 1222 DESCRIPTION 1223 " This object is required only for Euro-PacketCable. This 1224 object specifies the delay between the end of the Ring 1225 Pulse Alert Signal (RP-AS) and the start of the 1226 transmission of the FSK containing the Caller ID 1227 information. This object is only used when 1228 pktcSigDevCIDMode is rpAsETS. The following table defines 1229 the default values for this object depending on signal 1230 type: 1231 pktcSigDevCIDMode Default 1232 duringringingETS not used 1233 dtAsETS not used 1234 rpAsETS 650 ms 1235 lrAsETS not used 1236 An attempt to set this object while the value of 1237 pktcSigDevCIDMode is not rpAsETS will result in an 1238 inconsistentValue error." 1239 REFERENCE 1240 "EN 300 659-1 Specification" 1241 DEFVAL { 650 } 1242 ::= {pktcSigDevConfigObjects 24 } 1244 pktcSigDevCIDRingAfterFSK OBJECT-TYPE 1245 SYNTAX Unsigned32 (50..500) 1246 UNITS "Milliseconds" 1247 MAX-ACCESS read-write 1248 STATUS current 1249 DESCRIPTION 1250 " This object is required only for Euro-PacketCable. This 1251 object specifies the delay between the end of the complete 1252 transmission of the FSK containing the Caller ID 1253 information and the start of the first ring pattern. It is 1254 only used when pktcSigDevCIDMode is dtAsETS, rpAsETS or 1255 lrAsETS. The following table defines the default values 1256 for this object depending on signal type: 1257 pktcSigDevCIDMode Default 1258 duringringingETS not used 1259 dtAsETS 250 ms 1260 rpAsETS 250 ms 1261 lrAsETS 250 ms 1262 An attempt to set this object while the value of 1263 pktcSigDevCIDMode is not dtAsETS, rpAsETS, or lrAsETS will 1264 result in an inconsistentValue error." 1265 REFERENCE 1266 "EN 300 659-1 Specification" 1267 DEFVAL { 250 } 1268 ::= {pktcSigDevConfigObjects 25 } 1270 pktcSigDevCIDDTASAfterLR OBJECT-TYPE 1271 SYNTAX Unsigned32 (50..655) 1272 UNITS "Milliseconds" 1273 MAX-ACCESS read-write 1274 STATUS current 1275 DESCRIPTION 1276 " This object is required only for Euro-PacketCable. This 1277 object specifies the delay between the end of the Line 1278 Reversal and the start of the Dual Tone Alert Signal 1279 (DT-AS). This object is only used when pktcSigDevCIDMode 1280 is lrAsETS. The following table defines the default values 1281 for this object depending on signal type: 1282 pktcSigDevCIDMode Default 1283 duringringingETS not used 1284 dtAsETS not used 1285 rpAsETS not used 1286 lrAsETS 250 ms 1287 An attempt to set this object while the value of 1288 pktcSigDevCIDMode is not lrAsETS will result in an 1289 inconsistentValue error." 1290 REFERENCE 1291 "EN 300 659-1 Specification" 1292 DEFVAL { 250 } 1294 ::= {pktcSigDevConfigObjects 26 } 1296 pktcSigDevVmwiMode OBJECT-TYPE 1297 SYNTAX INTEGER { 1298 dtAsETS(1), 1299 rpAsETS(2), 1300 lrAsETS(3), 1301 osi(4) 1302 } 1303 MAX-ACCESS read-write 1304 STATUS current 1305 DESCRIPTION 1306 " For visual message waiting indicator (VMWI), 1307 pktcSigDevVmwiMode selects the alerting signal method. For 1308 the dtAsETS, rpAsETS, lrAsETS, and OSI methods, 1309 the FSK containing the VMWI information is sent after an 1310 alerting signal. For the dtAsETS method, the FSK is sent 1311 after the Dual Tone Alert Signal. For the rpAsETS method, 1312 the FSK is sent after a Ring Pulse. For the lrAsETS 1313 method, the Line Reversal occurs first, then the Dual Tone 1314 Alert Signal, and finally the FSK is sent. For the OSI 1315 method, the FSK is sent after the Open Switching 1316 Interval." 1317 DEFVAL { dtAsETS } 1318 ::= {pktcSigDevConfigObjects 27 } 1320 pktcSigDevVmwiFskAfterDTAS OBJECT-TYPE 1321 SYNTAX Unsigned32 (45..500) 1322 UNITS "Milliseconds" 1323 MAX-ACCESS read-write 1324 STATUS current 1325 DESCRIPTION 1326 " This object is required only for Euro-PacketCable. This 1327 object specifies the delay between the end of the Dual 1328 Tone Alert Signal (DT-AS) and the start of the 1329 transmission of the FSK containing the VMWI information. 1330 This object is only used when pktcSigDevVmwiMode is 1331 dtAsETS or lrAsETS. The following table defines the 1332 default values for this object depending on signal type: 1333 pktcSigDevVmwiMode Default 1334 dtAsETS 50 ms 1335 rpAsETS not used 1336 lrAsETS 50 ms 1337 An attempt to set this object while the value of 1338 pktcSigDevVmwiMode is not dtAsETS or lrAsETS will result 1339 in an inconsistentValue error." 1340 REFERENCE 1341 "EN 300 659-1 Specification" 1342 DEFVAL { 50 } 1343 ::= {pktcSigDevConfigObjects 28 } 1345 pktcSigDevVmwiFskAfterRPAS OBJECT-TYPE 1346 SYNTAX Unsigned32 (500..800) 1347 UNITS "Milliseconds" 1348 MAX-ACCESS read-write 1349 STATUS current 1350 DESCRIPTION 1351 " This object is required only for Euro-PacketCable. This 1352 object specifies the delay between the end of the Ring 1353 Pulse Alert Signal (RP-AS) and the start of the 1354 transmission of the FSK containing the VMWI information. 1355 This object is only used when pktcSigDevVmwiMode is 1356 rpAsETS. The following table defines the default values 1357 for this object depending on signal type: 1358 pktcSigDevVmwiMode Default 1359 dtAsETS not used 1360 rpAsETS 650 ms 1361 lrAsETS not used 1362 An attempt to set this object while the value of 1363 pktcSigDevVmwiMode is not rpAsETS will result in an 1364 inconsistentValue error." 1365 REFERENCE 1366 "EN 300 659-1 Specification" 1367 DEFVAL { 650 } 1368 ::= {pktcSigDevConfigObjects 29 } 1370 pktcSigDevVmwiDTASAfterLR OBJECT-TYPE 1371 SYNTAX Unsigned32 (50..655) 1372 UNITS "Milliseconds" 1373 MAX-ACCESS read-write 1374 STATUS current 1375 DESCRIPTION 1376 " This object is required only for Euro-PacketCable. This 1377 object specifies the delay between the end of the Line 1378 Reversal and the start of the Dual Tone Alert Signal 1379 (DT-AS) for VMWI information. This object is only used 1380 when pktcSigDevVmwiMode is lrAsETS. The following table 1381 defines the default values for this object depending on 1382 signal type: 1383 pktcSigDevVmwiMode Default 1384 dtAsETS not used 1385 rpAsETS not used 1386 lrAsETS 250 ms 1387 An attempt to set this object while the value of 1388 pktcSigDevVmwiMode is not lrAsETS will result in an 1389 inconsistentValue error." 1390 REFERENCE 1391 "EN 300 659-1 Specification" 1392 DEFVAL { 250 } 1393 ::= {pktcSigDevConfigObjects 30 } 1395 pktcSigDevRingCadenceTable OBJECT-TYPE 1396 SYNTAX SEQUENCE OF PktcSigDevRingCadenceEntry 1397 MAX-ACCESS not-accessible 1398 STATUS current 1399 DESCRIPTION 1400 "Cadence rings are defined by the telco governing 1401 body for each country. The MTA must be able to support 1402 various ranges of cadence patterns and cadence periods. 1403 The MTA will be able to support country specific 1404 provisioning of the cadence and idle period. Each 1405 cadence pattern will be assigned a unique value ranging 1406 from 0-127 (inclusive) corresponding to the value of x, 1407 where x is the value sent in the cadence ringing (cr) 1408 signal cr(x), requested per the appropriate NCS 1409 message, and defined in the E package. The MTA will derive 1410 the cadence periods from the ring cadence table entry as 1411 provisioned by the customer. The MTA is allowed to provide 1412 appropriate default values for each of the ring cadences. 1413 This table only needs to be supported when the MTA 1414 implements the E package. Objects in this table do not 1415 persist across MTA reboots." 1416 REFERENCE 1417 "TS 101 909-4 Specification" 1418 ::= { pktcSigDevConfigObjects 31 } 1420 pktcSigDevRingCadenceEntry OBJECT-TYPE 1421 SYNTAX PktcSigDevRingCadenceEntry 1422 MAX-ACCESS not-accessible 1423 STATUS current 1424 DESCRIPTION 1425 " Unique value ranging from 0 to 127 that will correspond to 1426 the different ring cadences that are being supported by 1427 the device." 1428 INDEX { pktcSigDevRingCadenceIndex } 1429 ::= { pktcSigDevRingCadenceTable 1 } 1431 PktcSigDevRingCadenceEntry ::= SEQUENCE { 1432 pktcSigDevRingCadenceIndex Unsigned32, 1433 pktcSigDevRingCadence PktcRingCadence 1434 } 1436 pktcSigDevRingCadenceIndex OBJECT-TYPE 1437 SYNTAX Unsigned32 (0..127) 1438 MAX-ACCESS not-accessible 1439 STATUS current 1440 DESCRIPTION 1441 " Unique value ranging from 0 to 127 that corresponds to the 1442 value sent by the LE based on country specific cadences, 1443 one row per cadence cycle. In any given system 1444 implementation for a particular country, it is anticipated 1445 that a small number of ring cadences will be in use. Thus, 1446 this table most likely will not be populated to its full 1447 size." 1448 ::= { pktcSigDevRingCadenceEntry 1 } 1450 pktcSigDevRingCadence OBJECT-TYPE 1451 SYNTAX PktcRingCadence 1452 MAX-ACCESS read-write 1453 STATUS current 1454 DESCRIPTION 1455 "This is the Ring Cadence. This object is required for the 1456 E line package." 1457 ::= { pktcSigDevRingCadenceEntry 2 } 1459 pktcSigDevToneType OBJECT-TYPE 1460 SYNTAX INTEGER { 1461 busy(1), 1462 confirmation(2), 1463 dial(3), 1464 messageWaiting(4), 1465 offHookWarning(5), 1466 ringBack(6), 1467 reOrder(7), 1468 stutterdial(8), 1469 callWaiting1(9), 1470 callWaiting2(10), 1471 callWaiting3(11), 1472 callWaiting4(12), 1473 alertingSignal(13), 1474 specialDial(14), 1475 specialInfo(15), 1476 release(16), 1477 congestion(17), 1478 userDefined1(18), 1479 userDefined2(19), 1480 userDefined3(20), 1481 userDefined4(21) 1482 } 1483 MAX-ACCESS not-accessible 1484 STATUS current 1485 DESCRIPTION 1486 "Unique value ranging from 1 to 21 that will correspond 1487 to the different tone types. These tones can be 1488 provisioned based on country specific needs. This 1489 object defines the type of tone being accessed. 1490 The alertingSignal, specialDial, specialInfo, release, 1491 congestion and userDefined1-4 tone types are used in 1492 the E line package." 1493 ::= { pktcSigDevConfigObjects 32 } 1495 pktcSigDevToneNumFrequencies OBJECT-TYPE 1496 SYNTAX INTEGER(5..16) 1497 MAX-ACCESS read-write 1498 STATUS current 1499 DESCRIPTION 1500 "This MIB Object specifies the number of frequencies 1501 supported by the PacketCable MTA for each tone type." 1502 ::={ pktcSigDevConfigObjects 33} 1504 pktcSigDevToneTable OBJECT-TYPE 1505 SYNTAX SEQUENCE OF PktcSigDevToneEntry 1506 MAX-ACCESS not-accessible 1507 STATUS current 1508 DESCRIPTION 1509 " The Tone Table defines the various tone operations. Any 1510 definition of the tones callWaiting1-4 in this table 1511 should just contain the audible tone itself and NOT 1512 contain the delay between tones or the tone repeat count. 1513 The delay between tones or the repeat count is controlled 1514 by the objects pktcNcsEndPntConfigCallWaitingDelay, and 1515 pktcNcsEndPntConfigCallWaitingMaxRep. If the 1516 pktcSigDevToneType is set to either of the values 1517 callWaiting1, callWaiting2, callWaiting3 or callWaiting4, 1518 then the value of the pktcSigDevToneWholeToneRepeatCount 1519 object has no effect on the tone. The MTA MUST 1520 make sure that, after the provisioning cycle, the table is 1521 fully populated (i.e., for each possible index, an entry 1522 MUST be defined) using reasonable defaults for each row 1523 that was not defined by the provisioning information. 1524 Objects in this table do not persist across MTA reboots. 1525 For tones with multiple frequencies refer to the MIB table 1526 pktcSigDevMultiFreqToneTable." 1527 REFERENCE 1528 "NCS Specification, TS 101 909-4 Specification" 1529 ::= { pktcSigDevConfigObjects 34 } 1531 pktcSigDevToneEntry OBJECT-TYPE 1532 SYNTAX PktcSigDevToneEntry 1533 MAX-ACCESS not-accessible 1534 STATUS current 1535 DESCRIPTION 1536 " The different tone types that can be provisioned based on 1537 country specific needs." 1538 INDEX { pktcSigDevToneType } 1539 ::= { pktcSigDevToneTable 1 } 1541 PktcSigDevToneEntry ::= SEQUENCE { 1542 pktcSigDevToneDbLevel TenthdBm, 1543 pktcSigDevToneWholeToneRepeatCount Unsigned32, 1544 pktcSigDevToneSteady TruthValue 1545 } 1547 pktcSigDevToneDbLevel OBJECT-TYPE 1548 SYNTAX TenthdBm (-250..-30) 1549 UNITS "dBm" 1550 MAX-ACCESS read-write 1551 STATUS current 1552 DESCRIPTION 1554 "This MIB Object contains the decibel level for each 1555 analog signal (tone) that is locally generated 1556 versus in band supervisory tones) and sourced to 1557 the a-b terminals (TE connection point). Each tone 1558 in itself may consist of multiple frequencies as 1559 defined by the MIB table 1560 'pktcSigDevMultiFreqToneTable'. 1562 This MIB Object MUST reflect the desired level at 1563 the Telco (POTS) a-b (T/R) terminals including the 1564 affect of the pktcNcsEndPntConfigRxGain setting on 1565 the delivered tone. 1567 The wide range of levels for this Object is required 1568 to provide signal generator levels across the wide 1569 range of gains - but does not imply the entire range 1570 is to be achievable given the range of negative 1571 values of gain (positive loss). This MIB Object must 1572 be set for each tone so as to generate the combined 1573 frequency level at the a-b (T/R) terminals." 1575 DEFVAL { -40 } 1576 ::={pktcSigDevToneEntry 1 } 1578 pktcSigDevToneWholeToneRepeatCount OBJECT-TYPE 1579 SYNTAX Unsigned32 (0..5000) 1580 MAX-ACCESS read-write 1581 STATUS current 1582 DESCRIPTION 1583 "This is the repeat count, which signifies how many times 1584 to repeat the entire on-off sequence. Setting this object 1585 may result in a tone duration longer or shorter than the 1586 overall signal duration specified by the time out (TO) 1587 object for a particular signal. If the repeat count results 1588 in a longer tone duration than the signal duration 1589 specified by the TO, the tone duration defined 1590 by the TO object for a particular signal always represents 1591 the overall signal duration for a tone. In this case, the 1592 tone duration repeat count will not be fully exercised and 1593 the desired tone duration will be truncated per the TO 1594 setting. If the repeat count results in a shorter tone 1595 duration than the signal duration specified by the TO, the 1596 tone duration defined by the repeat count takes precedence 1597 over the TO and will end the signal event. In this case, 1598 the TO represents a time not to be exceeded for the signal. 1599 It is recommended to ensure proper telephony signaling that 1600 The TO duration setting should always be longer than the 1601 desired repeat count time duration." 1602 ::={ pktcSigDevToneEntry 2 } 1604 pktcSigDevToneSteady OBJECT-TYPE 1605 SYNTAX TruthValue 1606 MAX-ACCESS read-write 1607 STATUS current 1608 DESCRIPTION 1609 "This is the steady tone. Device must play out the on-off 1610 sequence for pktcSigDevToneWholeRepeatCount times and 1611 then apply the last tone forever. Setting this object 1612 may result in a tone duration longer or shorter than the 1613 overall signal duration specified by the time out (TO) 1614 object for a particular signal. If the repeat count results 1615 in a longer tone duration than the signal duration 1616 specified by the TO, the tone duration defined 1617 by the TO object for a particular signal always represents 1618 the overall signal duration for a tone. In this case, the 1619 tone duration repeat count will not be fully exercised and 1620 the desired tone duration will be truncated per the TO 1621 setting. If the repeat count results in a shorter tone 1622 duration than the signal duration specified by the TO, the 1623 tone duration defined by the repeat count takes precedence 1624 over the TO and will end the signal event. In this case, 1625 the TO represents a time not to be exceeded for the signal. 1626 It is recommended to ensure proper telephony signaling that 1627 The TO duration setting should always be longer than the 1628 desired repeat count time duration plus the desired maximum 1629 steady tone period." 1630 ::={ pktcSigDevToneEntry 3 } 1632 pktcSigDevMultiFreqToneTable OBJECT-TYPE 1633 SYNTAX SEQUENCE OF PktcSigDevMultiFreqToneEntry 1634 MAX-ACCESS not-accessible 1635 STATUS current 1637 DESCRIPTION 1638 " This MIB table defines the characteristics of tones 1639 with multiple frequencies. The constraints imposed 1640 on the tones by the MIB table pktcSigDevToneTable 1641 need to be considered for MIB objects in this table 1642 as well." 1643 REFERENCE 1644 "NCS Specification, TS 101 909-4 Specification" 1645 ::= { pktcSigDevConfigObjects 35 } 1647 pktcSigDevMultiFreqToneEntry OBJECT-TYPE 1648 SYNTAX PktcSigDevMultiFreqToneEntry 1649 MAX-ACCESS not-accessible 1650 STATUS current 1651 DESCRIPTION 1652 " The different tone types with multiple frequencies 1653 that can be provisioned based on country specific 1654 needs." 1655 INDEX { pktcSigDevToneType, pktcSigDevToneFrequencyNumber } 1656 ::= { pktcSigDevMultiFreqToneTable 1 } 1658 PktcSigDevMultiFreqToneEntry ::= SEQUENCE { 1659 pktcSigDevToneFrequencyNumber Unsigned32 , 1660 pktcSigDevToneFreqPriCompValue Unsigned32, 1661 pktcSigDevToneFreqSecCompValue Unsigned32, 1662 pktcSigDevToneFreqSecCompMode INTEGER, 1663 pktcSigDevToneFreqSecCompPrtg Integer32, 1664 pktcSigDevToneFreqOnDuration Unsigned32, 1665 pktcSigDevToneFreqOffDuration Unsigned32, 1666 pktcSigDevToneFreqRepeatCount Unsigned32 1667 } 1669 pktcSigDevToneFrequencyNumber OBJECT-TYPE 1670 SYNTAX Unsigned32(5..16) 1671 MAX-ACCESS not-accessible 1672 STATUS current 1673 DESCRIPTION 1674 "This MIB Object represents the frequency reference 1675 of a multi-frequency tone. It is to be noted that 1676 the maximum number of frequencies for a 1677 multi-frequency tone is limited by the MIB Object 1678 pktcSigDevToneNumFrequencies." 1679 ::={ pktcSigDevMultiFreqToneEntry 1} 1681 pktcSigDevToneFreqPriCompValue OBJECT-TYPE 1682 SYNTAX Unsigned32(0..4000) 1683 MAX-ACCESS read-write 1684 STATUS current 1685 DESCRIPTION 1686 "This MIB Object represents the value of the primary 1687 component frequency specific to the frequency reference 1688 of a tone type." 1689 ::={ pktcSigDevMultiFreqToneEntry 2} 1691 pktcSigDevToneFreqSecCompValue OBJECT-TYPE 1692 SYNTAX Unsigned32(0..4000) 1693 MAX-ACCESS read-write 1694 STATUS current 1695 DESCRIPTION 1696 "This MIB Object represents the value of the secondary 1697 component frequency specific to the frequency reference 1698 of a tone type." 1699 ::={ pktcSigDevMultiFreqToneEntry 3} 1701 pktcSigDevToneFreqSecCompMode OBJECT-TYPE 1702 SYNTAX INTEGER { 1703 ignoreSecondary (1), 1704 primaryModulatedBySecondary (2), 1705 primarySummedWithSecondary (3) 1706 } 1707 MAX-ACCESS read-write 1708 STATUS current 1709 DESCRIPTION 1710 "This MIB Object indicates the way the primary 1711 and secondary frequency components indicated 1712 by the MIB Objects 'pktcSigDevToneFreqPriCompValue' 1713 and 'pktcSigDevToneFreqSecCompValue' are to be used. 1715 A value of primaryModulatedBySecondary(2) indicates 1716 that the primary must be used to amplitude modulate 1717 the secondary. The percentage of amplitude modulation 1718 to be applied to the secondary is defined by the MIB 1719 Object 'pktcSigDevToneFreqSecCompPrtg'. 1721 A value of primarySummedWithSecondary(3) indicates 1722 that the primary must be summed with the secondary, 1723 without any modulation 1725 A value of ignoreSecondary(1) indicates that the 1726 secondary must not be used." 1727 ::={ pktcSigDevMultiFreqToneEntry 4} 1729 pktcSigDevToneFreqSecCompPrtg OBJECT-TYPE 1730 SYNTAX Integer32(0..100) 1731 MAX-ACCESS read-write 1732 STATUS current 1733 DESCRIPTION 1734 "This MIB Object represents the percentage of amplitude 1735 modulation applied to the secondary frequency component 1736 when the MIB Object 'pktcSigDevToneFreqSecCompMode' is 1737 set to a value of 'primaryModulatedBySecondary(2)'. 1738 In all other cases this MIB Object has no meaning." 1739 ::={ pktcSigDevMultiFreqToneEntry 5} 1741 pktcSigDevToneFreqOnDuration OBJECT-TYPE 1742 SYNTAX Unsigned32(0..5000) 1743 MAX-ACCESS read-write 1744 STATUS current 1745 DESCRIPTION 1746 "This MIB Object represents the duration for which the 1747 frequency reference corresponding to the tone type 1748 is turned on." 1749 ::={ pktcSigDevMultiFreqToneEntry 6} 1751 pktcSigDevToneFreqOffDuration OBJECT-TYPE 1752 SYNTAX Unsigned32(0..5000) 1753 MAX-ACCESS read-write 1754 STATUS current 1755 DESCRIPTION 1756 "This MIB Object represents the duration for which the 1757 frequency reference corresponding to the tone type 1758 is turned off." 1759 ::={ pktcSigDevMultiFreqToneEntry 7} 1761 pktcSigDevToneFreqRepeatCount OBJECT-TYPE 1762 SYNTAX Unsigned32(0..5000) 1763 MAX-ACCESS read-write 1764 STATUS current 1765 DESCRIPTION 1766 "This MIB Object indicates the number of times 1767 to repeat the cadence cycle represented by the 1768 on/off durations (refer to the MIB Objects 1769 pktcSigDevToneFreqOnDuration and 1770 pktcSigDevToneFreqOffDuration). 1772 Setting this object may result in a tone duration 1773 longer or shorter than the overall signal duration 1774 specified by the time out (TO) object for the 1775 corresponding tone type. If the value of this MIB 1776 Object indicates a longer duration than the 1777 specified by the TO, the latter overrules the former 1778 and the desired tone duration will be truncated according 1779 to the TO. 1781 However, if the repeat count results in a shorter 1782 tone duration than the signal duration specified by 1783 the TO, the tone duration defined by the repeat count 1784 takes precedence over the TO and will end the signal 1785 event. In this case, the TO represents a time not to 1786 be exceeded for the signal. It is recommended to 1787 ensure proper telephony signaling that the TO 1788 duration setting should always be longer than the 1789 desired repeat count time duration. A value of zero 1790 means the tone sequence is to be played once but not 1791 repeated." 1792 ::={ pktcSigDevMultiFreqToneEntry 8} 1794 -- 1795 -- The NCS End Point Config Table is used to define attributes that 1796 -- are specific to connection EndPoints. 1797 -- 1799 pktcNcsEndPntConfigTable OBJECT-TYPE 1800 SYNTAX SEQUENCE OF PktcNcsEndPntConfigEntry 1801 MAX-ACCESS not-accessible 1802 STATUS current 1803 DESCRIPTION 1804 " This table describes the information pertaining to each 1805 endpoint of the MTA. All entries in this table represent 1806 the provisioned endpoints provisioned with the information 1807 required by the MTA to maintain the NCS signaling protocol 1808 communication with the CMS. Each endpoint can be assigned 1809 to its own CMS. If the specific endpoint does not have 1810 the corresponding CMS information in this table, the 1811 endpoint is considered as not provisioned with voice 1812 services. Objects in this table do not persist across 1813 MTA reboots." 1814 ::= { pktcNcsEndPntConfigObjects 1 } 1816 pktcNcsEndPntConfigEntry OBJECT-TYPE 1817 SYNTAX PktcNcsEndPntConfigEntry 1818 MAX-ACCESS not-accessible 1819 STATUS current 1820 DESCRIPTION 1821 "Each entry in the pktcNcsEndPntConfigTable represents 1822 required signaling parameters for the specific endpoint 1823 provisioned with voice services." 1824 INDEX { ifIndex } 1825 ::= { pktcNcsEndPntConfigTable 1 } 1827 PktcNcsEndPntConfigEntry ::= SEQUENCE { 1828 pktcNcsEndPntConfigCallAgentId SnmpAdminString, 1829 pktcNcsEndPntConfigCallAgentUdpPort InetPortNumber, 1830 pktcNcsEndPntConfigPartialDialTO Unsigned32, 1831 pktcNcsEndPntConfigCriticalDialTO Unsigned32, 1832 pktcNcsEndPntConfigBusyToneTO Unsigned32, 1833 pktcNcsEndPntConfigDialToneTO Unsigned32, 1834 pktcNcsEndPntConfigMessageWaitingTO Unsigned32, 1835 pktcNcsEndPntConfigOffHookWarnToneTO Unsigned32, 1836 pktcNcsEndPntConfigRingingTO Unsigned32, 1837 pktcNcsEndPntConfigRingBackTO Unsigned32, 1838 pktcNcsEndPntConfigReorderToneTO Unsigned32, 1839 pktcNcsEndPntConfigStutterDialToneTO Unsigned32, 1840 pktcNcsEndPntConfigTSMax Unsigned32, 1841 pktcNcsEndPntConfigMax1 Unsigned32, 1842 pktcNcsEndPntConfigMax2 Unsigned32, 1843 pktcNcsEndPntConfigMax1QEnable TruthValue, 1844 pktcNcsEndPntConfigMax2QEnable TruthValue, 1845 pktcNcsEndPntConfigMWD Unsigned32, 1846 pktcNcsEndPntConfigTdinit Unsigned32, 1847 pktcNcsEndPntConfigTdmin Unsigned32, 1848 pktcNcsEndPntConfigTdmax Unsigned32, 1849 pktcNcsEndPntConfigRtoMax Unsigned32, 1850 pktcNcsEndPntConfigRtoInit Unsigned32, 1851 pktcNcsEndPntConfigLongDurationKeepAlive Unsigned32, 1852 pktcNcsEndPntConfigThist Unsigned32, 1853 pktcNcsEndPntConfigStatus RowStatus, 1854 pktcNcsEndPntConfigCallWaitingMaxRep Unsigned32, 1855 pktcNcsEndPntConfigCallWaitingDelay Unsigned32, 1856 pktcNcsEndPntStatusCallIpAddressType InetAddressType, 1857 pktcNcsEndPntStatusCallIpAddress InetAddress, 1858 pktcNcsEndPntStatusError INTEGER, 1859 pktcNcsEndPntConfigMinHookFlash Unsigned32, 1860 pktcNcsEndPntConfigMaxHookFlash Unsigned32, 1861 pktcNcsEndPntConfigPulseDialInterdigitTime Unsigned32, 1862 pktcNcsEndPntConfigPulseDialMinMakeTime Unsigned32, 1863 pktcNcsEndPntConfigPulseDialMaxMakeTime Unsigned32, 1864 pktcNcsEndPntConfigPulseDialMinBreakTime Unsigned32, 1865 pktcNcsEndPntConfigPulseDialMaxBreakTime Unsigned32, 1866 pktcNcsEndPntConfigTxGain Integer32, 1867 pktcNcsEndPntConfigRxGain Integer32 1868 } 1870 pktcNcsEndPntConfigCallAgentId OBJECT-TYPE 1871 SYNTAX SnmpAdminString(SIZE (3..255)) 1872 MAX-ACCESS read-create 1873 STATUS current 1874 DESCRIPTION 1875 " This object contains a string indicating the call agent 1876 name (e.g.: ca@example.com). The call agent name, after 1877 the character '@', MUST be a fully qualified domain name 1878 (FQDN) and MUST have a corresponding pktcMtaDevCmsFqdn 1879 entry in the pktcMtaDevCmsTable. The object 1880 pktcMtaDevCmsFqdn is defined in the PacketCable MIBMTA 1881 Specification. For each particular endpoint, the MTA MUST 1882 use the current value of this object to communicate with 1883 the corresponding CMS. The MTA MUST update this object 1884 with the value of the 'Notified Entity' parameter of the 1885 NCS message. Because of the high importance of this object 1886 to the ability of the MTA to maintain reliable NCS 1887 communication with the CMS, it is highly recommended not 1888 to change this object's value using SNMP during normal 1889 operation." 1890 ::= { pktcNcsEndPntConfigEntry 1 } 1892 pktcNcsEndPntConfigCallAgentUdpPort OBJECT-TYPE 1893 SYNTAX InetPortNumber (1025..65535) 1894 MAX-ACCESS read-create 1895 STATUS current 1896 DESCRIPTION 1897 " This object contains the current value of the User 1898 Datagram Protocol (UDP) receive port on which the 1899 call agent will receive NCS signaling from the endpoint. 1900 For each particular endpoint, the MTA MUST use the current 1901 value of this object to communicate with the corresponding 1902 CMS. The MTA MUST update this object with the value of the 1903 'Notified Entity' parameter of the NCS message. If the 1904 Notified Entity parameter does not contain a CallAgent 1905 port, the MTA MUST update this object with the default 1906 value of 2727. Because of the high importance of this 1907 object to the ability of the MTA to maintain reliable NCS 1908 communication with the CMS, it is highly recommended not 1909 to change this object's value using SNMP during normal 1910 operation." 1911 REFERENCE 1912 "PacketCable NCS Specification" 1913 DEFVAL { 2727 } 1914 ::= { pktcNcsEndPntConfigEntry 2 } 1916 pktcNcsEndPntConfigPartialDialTO OBJECT-TYPE 1917 SYNTAX Unsigned32 1918 UNITS "seconds" 1919 MAX-ACCESS read-create 1920 STATUS current 1921 DESCRIPTION 1922 "This object contains the value of the partial dial 1923 time out." 1924 REFERENCE 1925 "PacketCable NCS Specification" 1926 DEFVAL { 16 } 1927 ::= { pktcNcsEndPntConfigEntry 3 } 1929 pktcNcsEndPntConfigCriticalDialTO OBJECT-TYPE 1930 SYNTAX Unsigned32 1931 UNITS "seconds" 1932 MAX-ACCESS read-create 1933 STATUS current 1934 DESCRIPTION 1935 "This object contains the value of the critical 1936 dial time out." 1937 REFERENCE 1938 "PacketCable NCS Specification" 1939 DEFVAL { 4 } 1940 ::= { pktcNcsEndPntConfigEntry 4 } 1942 pktcNcsEndPntConfigBusyToneTO OBJECT-TYPE 1943 SYNTAX Unsigned32 1944 UNITS "seconds" 1945 MAX-ACCESS read-create 1946 STATUS current 1947 DESCRIPTION 1948 " This object contains the default timeout value for busy 1949 tone. The MTA MUST NOT update this object with the 1950 value provided in the NCS message (if present). If 1951 the value of the object is modified by the SNMP Management 1952 Station, the MTA MUST use the new value as a default only 1953 for a new signal requested by the NCS message." 1954 REFERENCE 1955 "PacketCable NCS Specification" 1956 DEFVAL { 30 } 1957 ::= { pktcNcsEndPntConfigEntry 5 } 1959 pktcNcsEndPntConfigDialToneTO OBJECT-TYPE 1960 SYNTAX Unsigned32 1961 UNITS "seconds" 1962 MAX-ACCESS read-create 1963 STATUS current 1964 DESCRIPTION 1965 " This object contains the default timeout value for dial 1966 tone. The MTA MUST NOT update this object with the 1967 value provided in the NCS message (if present). If 1968 the value of the object is modified by the SNMP Management 1969 Station, the MTA MUST use the new value as a default only 1970 for a new signal requested by the NCS message." 1971 REFERENCE 1972 "PacketCable NCS Specification" 1973 DEFVAL { 16 } 1974 ::= { pktcNcsEndPntConfigEntry 6 } 1976 pktcNcsEndPntConfigMessageWaitingTO OBJECT-TYPE 1977 SYNTAX Unsigned32 1978 UNITS "seconds" 1979 MAX-ACCESS read-create 1980 STATUS current 1981 DESCRIPTION 1982 " This object contains the default timeout value for message 1983 waiting indicator. The MTA MUST NOT update this object 1984 with the value provided in the NCS message (if 1985 present). If the value of the object is modified by the 1986 SNMP Management Station, the MTA MUST use the new value as 1987 a default only for a new signal requested by the NCS 1988 message." 1989 REFERENCE 1990 "PacketCable NCS Specification" 1992 DEFVAL { 16 } 1993 ::= { pktcNcsEndPntConfigEntry 7 } 1995 pktcNcsEndPntConfigOffHookWarnToneTO OBJECT-TYPE 1996 SYNTAX Unsigned32 1997 UNITS "seconds" 1998 MAX-ACCESS read-create 1999 STATUS current 2000 DESCRIPTION 2001 " This object contains the default timeout value for the off 2002 hook Warning tone. The MTA MUST NOT update this object 2003 with the value provided in the NCS message (if 2004 present). If the value of the object is modified by the 2005 SNMP Management Station, the MTA MUST use the new value as 2006 a default only for a new signal requested by the NCS 2007 message." 2008 REFERENCE 2009 "PacketCable NCS Specification" 2010 DEFVAL { 0 } 2011 ::= { pktcNcsEndPntConfigEntry 8 } 2013 pktcNcsEndPntConfigRingingTO OBJECT-TYPE 2014 SYNTAX Unsigned32 2015 UNITS "seconds" 2016 MAX-ACCESS read-create 2017 STATUS current 2018 DESCRIPTION 2019 " This object contains the default timeout value for 2020 ringing. The MTA MUST NOT update this object with the 2021 value provided in the NCS message (if present). If 2022 the value of the object is modified by the SNMP Management 2023 Station, the MTA MUST use the new value as a default only 2024 for a new signal requested by the NCS message." 2025 REFERENCE 2026 "PacketCable NCS Specification" 2027 DEFVAL { 180 } 2028 ::= { pktcNcsEndPntConfigEntry 9 } 2030 pktcNcsEndPntConfigRingBackTO OBJECT-TYPE 2031 SYNTAX Unsigned32 2032 UNITS "seconds" 2033 MAX-ACCESS read-create 2034 STATUS current 2035 DESCRIPTION 2036 " This object contains the default timeout value for ring 2037 back. The MTA MUST NOT update this object with the 2038 value provided in the NCS message (if present). If 2039 the value of the object is modified by the SNMP Management 2040 Station, the MTA MUST use the new value as a default only 2041 for a new signal requested by the NCS message." 2042 REFERENCE 2043 "PacketCable NCS Specification" 2044 DEFVAL { 180 } 2045 ::= { pktcNcsEndPntConfigEntry 10 } 2047 pktcNcsEndPntConfigReorderToneTO OBJECT-TYPE 2048 SYNTAX Unsigned32 2049 UNITS "seconds" 2050 MAX-ACCESS read-create 2051 STATUS current 2052 DESCRIPTION 2053 " This object contains the default timeout value for reorder 2054 tone. The MTA MUST NOT update this object with the 2055 value provided in the NCS message (if present). If 2056 the value of the object is modified by the SNMP Management 2057 Station, the MTA MUST use the new value as a default only 2058 for a new signal requested by the NCS message." 2059 REFERENCE 2060 "PacketCable NCS Specification" 2061 DEFVAL { 30 } 2062 ::= { pktcNcsEndPntConfigEntry 11 } 2064 pktcNcsEndPntConfigStutterDialToneTO OBJECT-TYPE 2065 SYNTAX Unsigned32 2066 UNITS "seconds" 2067 MAX-ACCESS read-create 2068 STATUS current 2069 DESCRIPTION 2070 " This object contains the default timeout value for stutter 2071 dial tone. The MTA MUST NOT update this object with the 2072 value provided in the NCS message (if present). If 2073 the value of the object is modified by the SNMP Management 2074 Station, the MTA MUST use the new value as a default only 2075 for a new signal requested by the NCS message." 2076 REFERENCE 2077 "PacketCable NCS Specification" 2078 DEFVAL { 16 } 2079 ::= { pktcNcsEndPntConfigEntry 12 } 2081 pktcNcsEndPntConfigTSMax OBJECT-TYPE 2082 SYNTAX Unsigned32 2083 MAX-ACCESS read-create 2084 STATUS current 2085 DESCRIPTION 2086 "This MIB object is used as part of an NCS 2087 retransmission algorithm. Prior to any retransmission, 2088 the MTA must check to make sure that the time elapsed 2089 since the sending of the initial datagram does not exceed 2090 the value specified by this MIB Object. If more than 2091 Tsmax time has elapsed, then the retransmissions MUST 2092 cease. 2094 Refer to the MIB Object pktcNcsEndPntConfigThist for 2095 Information on when the endpoint becomes disconnected." 2096 REFERENCE 2097 "PacketCable NCS Specification" 2098 DEFVAL { 20 } 2099 ::= { pktcNcsEndPntConfigEntry 13 } 2101 pktcNcsEndPntConfigMax1 OBJECT-TYPE 2102 SYNTAX Unsigned32 2103 MAX-ACCESS read-create 2104 STATUS current 2105 DESCRIPTION 2106 "This object contains the suspicious error threshold for 2107 signaling messages. The pktcNcsEndPntConfigMax1 object 2108 indicates the retransmission threshold at which the MTA MAY 2109 actively query the domain name server (DNS) in order to 2110 detect the possible change of call agent interfaces." 2111 REFERENCE 2112 "PacketCable NCS Specification" 2113 DEFVAL { 5 } 2114 ::= { pktcNcsEndPntConfigEntry 14 } 2116 pktcNcsEndPntConfigMax2 OBJECT-TYPE 2117 SYNTAX Unsigned32 2118 MAX-ACCESS read-create 2119 STATUS current 2120 DESCRIPTION 2121 "This object contains the disconnect error threshold for 2122 signaling messages. The pktcNcsEndPntConfigMax2 object 2123 indicates the retransmission threshold at which the MTA 2124 SHOULD contact the DNS one more time to see if any other 2125 interfaces to the call agent have become available." 2126 REFERENCE 2127 "PacketCable NCS Specification" 2128 DEFVAL { 7 } 2129 ::= { pktcNcsEndPntConfigEntry 15 } 2131 pktcNcsEndPntConfigMax1QEnable OBJECT-TYPE 2132 SYNTAX TruthValue 2133 MAX-ACCESS read-create 2134 STATUS current 2135 DESCRIPTION 2136 "This object enables/disables the Max1 domain name server 2137 (DNS) query operation when the pktcNcsEndPntConfigMax1 2138 threshold has been reached." 2139 DEFVAL { true } 2140 ::= { pktcNcsEndPntConfigEntry 16 } 2142 pktcNcsEndPntConfigMax2QEnable OBJECT-TYPE 2143 SYNTAX TruthValue 2144 MAX-ACCESS read-create 2145 STATUS current 2146 DESCRIPTION 2147 "This object enables/disables the Max2 domain name server 2148 (DNS) query operation when the pktcNcsEndPntConfigMax2 2149 threshold has been reached." 2150 DEFVAL { true } 2151 ::= { pktcNcsEndPntConfigEntry 17 } 2153 pktcNcsEndPntConfigMWD OBJECT-TYPE 2154 SYNTAX Unsigned32 2155 UNITS "seconds" 2156 MAX-ACCESS read-create 2157 STATUS current 2158 DESCRIPTION 2159 "Maximum Waiting Delay (MWD) contains the maximum number of 2160 seconds a MTA waits after powering on, before initiating 2161 the restart procedure with the call agent." 2162 REFERENCE 2163 "PacketCable NCS Specification" 2164 DEFVAL { 600 } 2165 ::= { pktcNcsEndPntConfigEntry 18 } 2167 pktcNcsEndPntConfigTdinit OBJECT-TYPE 2168 SYNTAX Unsigned32 2169 UNITS "seconds" 2170 MAX-ACCESS read-create 2171 STATUS current 2172 DESCRIPTION 2173 "This MIB object represents the 'disconnected' initial 2174 waiting delay within the context of an MTA's 'disconnected 2175 procedure'. The 'disconnected procedure' is initiated when 2176 an endpoint becomes 'disconnected' while attempting to 2177 communicate with a Call Agent. 2179 The 'disconnected timer' associated with the 'disconnected 2180 Procedure' is initialized to a random value, uniformly 2181 distributed between zero and the value contained in this 2182 MIB Object. 2184 For more information on the usage of this timer, please 2185 refer to the PacketCable NCS Specification." 2187 REFERENCE 2188 "PacketCable NCS Specification" 2189 DEFVAL { 15 } 2190 ::= { pktcNcsEndPntConfigEntry 19 } 2192 pktcNcsEndPntConfigTdmin OBJECT-TYPE 2193 SYNTAX Unsigned32 2194 UNITS "seconds" 2195 MAX-ACCESS read-create 2196 STATUS current 2197 DESCRIPTION 2198 "This MIB object represents the 'disconnected' minimum 2199 waiting delay within the context of an MTA's 'disconnected 2200 procedure', specifically when local user activity is 2201 detected. 2202 The 'disconnected procedure' is initiated when 2203 an endpoint becomes 'disconnected' while attempting to 2204 communicate with a Call Agent. 2205 For more information on the usage of this timer, please 2206 refer to the PacketCable NCS Specification." 2208 REFERENCE 2209 "PacketCable NCS Specification" 2210 DEFVAL { 15 } 2211 ::= { pktcNcsEndPntConfigEntry 20 } 2213 pktcNcsEndPntConfigTdmax OBJECT-TYPE 2214 SYNTAX Unsigned32 2215 UNITS "seconds" 2216 MAX-ACCESS read-create 2217 STATUS current 2218 DESCRIPTION 2219 " This object contains the maximum number of seconds the MTA 2220 waits after a disconnect, before initiating the 2221 disconnected procedure with the call agent. 2222 " 2223 REFERENCE 2224 "PacketCable NCS Specification" 2225 DEFVAL { 600 } 2226 ::= { pktcNcsEndPntConfigEntry 21 } 2228 pktcNcsEndPntConfigRtoMax OBJECT-TYPE 2229 SYNTAX Unsigned32 2230 UNITS "seconds" 2231 MAX-ACCESS read-create 2232 STATUS current 2233 DESCRIPTION 2234 " This object contains the maximum number of seconds for the 2235 retransmission timer. When this timer expires the MTA 2236 retransmits the message." 2237 REFERENCE 2238 "PacketCable NCS Specification" 2239 DEFVAL { 4 } 2240 ::= { pktcNcsEndPntConfigEntry 22 } 2242 pktcNcsEndPntConfigRtoInit OBJECT-TYPE 2243 SYNTAX Unsigned32 2244 UNITS "milliseconds" 2245 MAX-ACCESS read-create 2246 STATUS current 2247 DESCRIPTION 2248 " This object contains the initial number of seconds for the 2249 retransmission timer." 2250 REFERENCE 2251 "PacketCable NCS Specification" 2252 DEFVAL { 200 } 2253 ::= { pktcNcsEndPntConfigEntry 23 } 2255 pktcNcsEndPntConfigLongDurationKeepAlive OBJECT-TYPE 2256 SYNTAX Unsigned32 2257 UNITS "minutes" 2258 MAX-ACCESS read-create 2259 STATUS current 2260 DESCRIPTION 2261 " Specifies a timeout value in minutes for sending long 2262 duration call notification message." 2263 REFERENCE 2264 "PacketCable NCS Specification" 2265 DEFVAL { 60 } 2266 ::= { pktcNcsEndPntConfigEntry 24 } 2268 pktcNcsEndPntConfigThist OBJECT-TYPE 2269 SYNTAX Unsigned32 2270 UNITS "seconds" 2271 MAX-ACCESS read-create 2272 STATUS current 2273 DESCRIPTION 2274 " Timeout period in seconds before no response is declared." 2275 REFERENCE 2276 "PacketCable NCS Specification" 2277 DEFVAL { 30 } 2278 ::= { pktcNcsEndPntConfigEntry 25 } 2280 pktcNcsEndPntConfigStatus OBJECT-TYPE 2281 SYNTAX RowStatus 2282 MAX-ACCESS read-create 2283 STATUS current 2284 DESCRIPTION 2285 " This object contains the Row Status associated with the 2286 pktcNcsEndPntConfigTable. There are no restrictions or 2287 dependencies amidst the columnar objects before this 2288 row can be activated or for modifications of the 2289 columnar objects when this object is set to active(1)." 2290 ::= { pktcNcsEndPntConfigEntry 26 } 2292 pktcNcsEndPntConfigCallWaitingMaxRep OBJECT-TYPE 2293 SYNTAX Unsigned32 (0..10) 2294 MAX-ACCESS read-create 2295 STATUS current 2296 DESCRIPTION 2297 " This object contains the default value of the maximum 2298 number of repetitions of the call waiting tone that the 2299 MTA will play from a single CMS request. The MTA MUST NOT 2300 update this object with the information provided in the 2301 NCS message (if present). If the value of the object is 2302 modified by the SNMP Management Station, the MTA MUST use 2303 the new value as a default only for a new signal 2304 requested by the NCS message." 2305 DEFVAL { 1 } 2306 ::= { pktcNcsEndPntConfigEntry 27 } 2308 pktcNcsEndPntConfigCallWaitingDelay OBJECT-TYPE 2309 SYNTAX Unsigned32 (1..100) 2310 UNITS "seconds" 2311 MAX-ACCESS read-create 2312 STATUS current 2313 DESCRIPTION 2314 " This object contains the delay between repetitions of the 2315 call waiting tone that the MTA will play from a single CMS 2316 request." 2317 DEFVAL { 10 } 2318 ::= { pktcNcsEndPntConfigEntry 28 } 2320 pktcNcsEndPntStatusCallIpAddressType OBJECT-TYPE 2321 SYNTAX InetAddressType 2322 MAX-ACCESS read-only 2323 STATUS current 2324 DESCRIPTION 2325 " This object contains the type of Internet address of the 2326 CMS currently being used for this endpoint." 2327 ::= { pktcNcsEndPntConfigEntry 29 } 2329 pktcNcsEndPntStatusCallIpAddress OBJECT-TYPE 2330 SYNTAX InetAddress 2331 MAX-ACCESS read-only 2332 STATUS current 2333 DESCRIPTION 2334 " This object contains the Internet address of the CMS 2335 currently being used for this endpoint. This Internet 2336 address is used to create the appropriate security 2337 association. The type of this IP address is determined by 2338 the value of the pktcNcsEndPntStatusCallIpAddressType 2339 object." 2340 ::= { pktcNcsEndPntConfigEntry 30 } 2342 pktcNcsEndPntStatusError OBJECT-TYPE 2343 SYNTAX INTEGER { 2344 operational (1), 2345 noSecurityAssociation (2), 2346 disconnected (3) 2347 } 2348 MAX-ACCESS read-only 2349 STATUS current 2350 DESCRIPTION 2351 " This object contains the error status for this interface. 2352 The operational status indicates that all operations 2353 necessary to put the line in service have occurred, and the 2354 CMS has acknowledged the Restart In Progress (RSIP) 2355 message successfully. If pktcMtaDevCmsIpsecCtrl is enabled 2356 for the associated Call Agent, the noSecurityAssociation 2357 status indicates that no Security Association (SA) yet 2358 exists for this endpoint. If pktcMtaDevCmsIpsecCtrl is 2359 disabled for the associated Call Agent, the 2360 noSecurityAssociation status is not applicable and should 2361 not be used by the MTA. The disconnected status indicates 2362 one of the following two: 2363 If pktcMtaDevCmsIpsecCtrl is disabled, then no security 2364 association is involved with this endpoint. The NCS 2365 signaling software is in process of establishing the NCS 2366 signaling link via an RSIP exchange. 2367 Otherwise, when pktcMtaDevCmsIpsecCtrl is enabled, 2368 security Association has been established, and the NCS 2369 signaling software is in process of establishing the NCS 2370 signaling link via an RSIP exchange." 2371 ::= { pktcNcsEndPntConfigEntry 31 } 2373 pktcNcsEndPntConfigMinHookFlash OBJECT-TYPE 2374 SYNTAX Unsigned32 (20..1000) 2375 UNITS "Milliseconds" 2376 MAX-ACCESS read-only 2377 STATUS current 2378 DESCRIPTION 2379 " This is the minimum time a line needs to be on hook for a 2380 valid hook flash. The value of this object MUST be 2381 greater than the value of 2382 pktcNcsEndPntConfigPulseDialMaxBreakTime. The value of 2383 pktcNcsEndPntConfigMinHookFlash MUST be less than 2384 pktcNcsEndPntConfigMaxHookFlash. This object MUST only be 2385 set via the configuration file during the provisioning 2386 process. 2387 Furthermore, given the possibility for the 'pulse dial' 2388 and 'hook flash' to overlap, the value of this object MUST 2389 be greater than the value contained by the MIB Object 2390 pktcNcsEndPntConfigPulseDialMaxMakeTime." 2391 DEFVAL { 300 } 2392 ::= { pktcNcsEndPntConfigEntry 32 } 2394 pktcNcsEndPntConfigMaxHookFlash OBJECT-TYPE 2395 SYNTAX Unsigned32 (20..1000) 2396 UNITS "Milliseconds" 2397 MAX-ACCESS read-only 2398 STATUS current 2399 DESCRIPTION 2400 " This is the maximum time a line needs to be on hook for a 2401 valid hook flash. The value of 2402 pktcNcsEndPntConfigMaxHookFlash MUST be greater than 2403 pktcNcsEndPntConfigMinHookFlash. This object MUST only be 2404 set via the configuration file during the provisioning 2405 process." 2406 DEFVAL { 800 } 2407 ::= { pktcNcsEndPntConfigEntry 33 } 2409 pktcNcsEndPntConfigPulseDialInterdigitTime OBJECT-TYPE 2410 SYNTAX Unsigned32 (100..1500) 2411 UNITS "Milliseconds" 2412 MAX-ACCESS read-only 2413 STATUS current 2414 DESCRIPTION 2415 " This is the pulse dial inter-digit timeout. This object 2416 MUST only be set via the configuration file during the 2417 provisioning process." 2418 DEFVAL { 100 } 2419 ::= { pktcNcsEndPntConfigEntry 34 } 2421 pktcNcsEndPntConfigPulseDialMinMakeTime OBJECT-TYPE 2422 SYNTAX Unsigned32 (20..200) 2423 UNITS "Milliseconds" 2424 MAX-ACCESS read-only 2425 STATUS current 2426 DESCRIPTION 2427 " This is the minimum make pulse width for the dial pulse. 2428 The value of pktcNcsEndPntConfigPulseDialMinMakeTime MUST 2429 be less than pktcNcsEndPntConfigPulseDialMaxMakeTime. This 2430 object MUST only be set via the configuration file during 2431 the provisioning process." 2432 DEFVAL { 25 } 2433 ::= { pktcNcsEndPntConfigEntry 35 } 2435 pktcNcsEndPntConfigPulseDialMaxMakeTime OBJECT-TYPE 2436 SYNTAX Unsigned32 (20..200) 2437 UNITS "Milliseconds" 2438 MAX-ACCESS read-only 2439 STATUS current 2440 DESCRIPTION 2441 " This is the maximum make pulse width for the dial pulse. 2442 The value of pktcNcsEndPntConfigPulseDialMaxMakeTime MUST 2443 be greater than pktcNcsEndPntConfigPulseDialMinMakeTime. 2444 This object MUST only be set via the configuration file 2445 during the provisioning process. 2446 Furthermore, given the possibility for the 'pulse dial' 2447 and 'hook flash' to overlap, the value of this object MUST 2448 be less than the value contained by the MIB Object 2449 pktcNcsEndPntConfigMinHookFlash." 2450 DEFVAL { 55 } 2451 ::= { pktcNcsEndPntConfigEntry 36 } 2453 pktcNcsEndPntConfigPulseDialMinBreakTime OBJECT-TYPE 2454 SYNTAX Unsigned32 (20..200) 2455 UNITS "Milliseconds" 2456 MAX-ACCESS read-only 2457 STATUS current 2458 DESCRIPTION 2459 " This is the minimum break pulse width for the dial pulse. 2460 The value of pktcNcsEndPntConfigPulseDialMinBreakTime MUST 2461 be less than pktcNcsEndPntConfigPulseDialMaxBreakTime. 2462 This object must only be set via the configuration file 2463 during the provisioning process." 2464 DEFVAL { 45 } 2465 ::= { pktcNcsEndPntConfigEntry 37 } 2467 pktcNcsEndPntConfigPulseDialMaxBreakTime OBJECT-TYPE 2468 SYNTAX Unsigned32 (20..200) 2469 UNITS "Milliseconds" 2470 MAX-ACCESS read-only 2471 STATUS current 2472 DESCRIPTION 2473 " This is the maximum break pulse width for the dial pulse. 2474 The value of pktcNcsEndPntConfigPulseDialMaxBreakTime MUST 2475 be greater than pktcNcsEndPntConfigPulseDialMinBreakTime. 2476 This object MUST only be set via the configuration file 2477 during the provisioning process." 2479 DEFVAL { 75 } 2480 ::= { pktcNcsEndPntConfigEntry 38 } 2482 pktcNcsEndPntConfigTxGain OBJECT-TYPE 2483 SYNTAX Integer32 2484 UNITS "dB" 2485 MAX-ACCESS read-create 2486 STATUS current 2487 DESCRIPTION 2488 "This MIB Object represents the per line transmitter (A/D) 2489 gain. A positive number reflects a signal gain, a negative 2490 number reflects a signal loss. This MIB Object may provision 2491 the gain or it may be used to document a non-provisionable 2492 gain between the telco (POTS) a-b (T/R) terminals and the 2493 analog codec maximum PCM coding limit (PCM maximum coding 2494 limit). Based on the default G.711 Vocoder maximum of 3.14 2495 or 3.17 dBm the -4 dB gain default provides Vocoder coding 2496 protection against TE maximum signals while also providing 2497 an initial loss to minimize analog signal echo. " 2498 DEFVAL { -4 } 2499 ::= { pktcNcsEndPntConfigEntry 39 } 2501 pktcNcsEndPntConfigRxGain OBJECT-TYPE 2502 SYNTAX Integer32 2503 UNITS "dB" 2504 MAX-ACCESS read-create 2505 STATUS current 2506 DESCRIPTION 2507 "This MIB Object represents the per line receiver (D/A) 2508 gain. A positive number reflects a signal gain, a negative 2509 number reflects a signal loss. This MIB Object may provision 2510 the gain or it may be used to document a non-provisionable 2511 gain for use with the pktcSigDevToneDbLevel Object to set 2512 the desired level at the a-b (T/R) terminals. 2514 The default values are based on the deployed markets. Some 2515 recommendations are made as follows: 2516 - Based on the default G.711 Vocoder maximum of 3.14 or 3.17 2517 dBm a default value of '-4 dB' provides a maximum analog 2518 signal level at the a-b (T/R) termination point 2519 - Based on [ETSI TS 101 909-4], which provides guidance of 2520 11 dB loss (-11 dB gain), a default value of '-11 dB' is 2521 recommended." 2522 ::= { pktcNcsEndPntConfigEntry 40 } 2524 -- 2525 -- notification group is for future extension. 2526 -- 2527 pktcSigNotification OBJECT IDENTIFIER ::= { pktcIetfSigMib 0 } 2528 pktcSigConformance OBJECT IDENTIFIER ::= { pktcIetfSigMib 2 } 2529 pktcSigCompliances OBJECT IDENTIFIER ::= { pktcSigConformance 1 } 2530 pktcSigGroups OBJECT IDENTIFIER ::= { pktcSigConformance 2 } 2532 -- 2533 -- compliance statements 2534 -- 2536 pktcSigBasicCompliance MODULE-COMPLIANCE 2537 STATUS current 2538 DESCRIPTION 2539 " The compliance statement for devices that implement 2540 Signaling on the MTA." 2542 MODULE -- pktcIetfSigMib 2544 -- 2545 -- unconditionally mandatory groups 2546 -- 2548 MANDATORY-GROUPS { 2549 pktcSigGroup 2550 } 2552 GROUP pktcNcsGroup 2553 DESCRIPTION 2554 " This group is mandatory for any MTA implementing NCS 2555 signaling" 2557 GROUP pktcInternationalGroup 2558 DESCRIPTION 2559 " This group is mandatory for any MTA implementing 2560 international telephony features. In such cases, it is 2561 left to manufacturers to determine whether to support both 2562 PacketCable and IPCablecom objects in the same MTA." 2563 ::={ pktcSigCompliances 1 } 2565 -- 2566 -- units of conformance 2567 -- 2569 pktcSigGroup OBJECT-GROUP 2570 OBJECTS { 2571 pktcSigDevCodecMax, 2572 pktcSigDevEchoCancellation, 2573 pktcSigDevSilenceSuppression, 2574 pktcSigDevR0Cadence, 2575 pktcSigDevR1Cadence, 2576 pktcSigDevR2Cadence, 2577 pktcSigDevR3Cadence, 2578 pktcSigDevR4Cadence, 2579 pktcSigDevR5Cadence, 2580 pktcSigDevR6Cadence, 2581 pktcSigDevR7Cadence, 2582 pktcSigDevRgCadence, 2583 pktcSigDevRsCadence, 2584 pktcSigDefCallSigDscp, 2585 pktcSigDefMediaStreamDscp, 2586 pktcSigDevVmwiMode, 2587 pktcSignalingType, 2588 pktcSignalingVersion, 2589 pktcSignalingVendorExtension, 2590 pktcSigDefNcsReceiveUdpPort 2591 } 2592 STATUS current 2593 DESCRIPTION 2594 "Group of objects for the common portion of the 2595 PacketCable Signaling MIB." 2596 ::= { pktcSigGroups 1 } 2598 pktcNcsGroup OBJECT-GROUP 2599 OBJECTS { 2600 pktcNcsEndPntConfigCallAgentId, 2601 pktcNcsEndPntConfigCallAgentUdpPort, 2602 pktcNcsEndPntConfigPartialDialTO, 2603 pktcNcsEndPntConfigCriticalDialTO, 2604 pktcNcsEndPntConfigBusyToneTO, 2605 pktcNcsEndPntConfigDialToneTO, 2606 pktcNcsEndPntConfigMessageWaitingTO, 2607 pktcNcsEndPntConfigOffHookWarnToneTO, 2608 pktcNcsEndPntConfigRingingTO, 2609 pktcNcsEndPntConfigRingBackTO, 2610 pktcNcsEndPntConfigReorderToneTO, 2611 pktcNcsEndPntConfigStutterDialToneTO, 2612 pktcNcsEndPntConfigTSMax, 2613 pktcNcsEndPntConfigMax1, 2614 pktcNcsEndPntConfigMax2, 2615 pktcNcsEndPntConfigMax1QEnable, 2616 pktcNcsEndPntConfigMax2QEnable, 2617 pktcNcsEndPntConfigMWD, 2618 pktcNcsEndPntConfigTdinit, 2619 pktcNcsEndPntConfigTdmin, 2620 pktcNcsEndPntConfigTdmax, 2621 pktcNcsEndPntConfigRtoMax, 2622 pktcNcsEndPntConfigRtoInit, 2623 pktcNcsEndPntConfigLongDurationKeepAlive, 2624 pktcNcsEndPntConfigThist, 2625 pktcNcsEndPntConfigStatus, 2626 pktcNcsEndPntConfigCallWaitingMaxRep, 2627 pktcNcsEndPntConfigCallWaitingDelay, 2628 pktcNcsEndPntStatusCallIpAddressType, 2629 pktcNcsEndPntStatusCallIpAddress, 2630 pktcNcsEndPntStatusError 2631 } 2632 STATUS current 2633 DESCRIPTION 2634 "Group of objects for the NCS portion of the PacketCable 2635 Signaling MIB. This is mandatory for NCS signaling." 2636 ::= { pktcSigGroups 2 } 2638 pktcInternationalGroup OBJECT-GROUP 2639 OBJECTS { 2640 pktcNcsEndPntConfigMinHookFlash, 2641 pktcNcsEndPntConfigMaxHookFlash, 2642 pktcNcsEndPntConfigPulseDialInterdigitTime, 2643 pktcNcsEndPntConfigPulseDialMinMakeTime, 2644 pktcNcsEndPntConfigPulseDialMaxMakeTime, 2645 pktcNcsEndPntConfigPulseDialMinBreakTime, 2646 pktcNcsEndPntConfigPulseDialMaxBreakTime, 2647 pktcNcsEndPntConfigTxGain, 2648 pktcNcsEndPntConfigRxGain, 2649 pktcSigDevRingCadence, 2650 pktcSigDevCallerIdSigProtocol, 2651 pktcSigDevCIDMode, 2652 pktcSigDevCIDFskAfterRing, 2653 pktcSigDevCIDFskAfterDTAS, 2654 pktcSigDevCIDFskAfterRPAS, 2655 pktcSigDevCIDRingAfterFSK, 2656 pktcSigDevCIDDTASAfterLR, 2657 pktcSigDevVmwiFskAfterDTAS, 2658 pktcSigDevVmwiFskAfterRPAS, 2659 pktcSigDevVmwiDTASAfterLR, 2660 pktcSigPowerRingFrequency, 2661 pktcSigPulseSignalFrequency, 2662 pktcSigPulseSignalDbLevel, 2663 pktcSigPulseSignalDuration, 2664 pktcSigPulseSignalPulseInterval, 2665 pktcSigPulseSignalRepeatCount, 2666 pktcSigDevToneDbLevel, 2667 pktcSigDevToneWholeToneRepeatCount, 2668 pktcSigDevToneSteady, 2669 pktcSigDevToneNumFrequencies, 2670 pktcSigDevToneFreqPriCompValue, 2671 pktcSigDevToneFreqSecCompValue, 2672 pktcSigDevToneFreqSecCompMode, 2673 pktcSigDevToneFreqSecCompPrtg, 2674 pktcSigDevToneFreqOnDuration, 2675 pktcSigDevToneFreqOffDuration, 2676 pktcSigDevToneFreqRepeatCount 2677 } 2678 STATUS current 2679 DESCRIPTION 2680 " Group of objects that extend the behavior of existing 2681 objects to support operations in the widest possible set 2682 of international marketplaces. Note that many of these 2683 objects represent a superset of behaviors described in 2684 other objects within this MIB Module." 2685 ::= { pktcSigGroups 3 } 2687 END 2689 6. Acknowledgments 2691 This document is a production of the PacketCable Working Group. 2693 The current editors wish to express gratitude to: 2695 Angela Lyda Arris Interactive 2696 Eugene Nechamkin Broadcom Corp. 2697 Jean-Francois Mule CableLabs, Inc. 2698 Matt A. Osman CableLabs, Inc. 2699 Klaus Hermanns Cisco Systems, Inc. 2700 Rich Woundy Comcast Corp. 2701 Bert Wijnen Lucent Technologies 2702 Phil Freyman Motorola, Inc. 2703 Rick Vetter Motorola, Inc. 2704 Sasha Medvinsky Motorola, Inc. 2705 Wim De Ketelaere tComLabs 2706 David De Reu tComLabs 2707 Kristof Sercu tComLabs 2708 Roy Spitzer Telogy Networks, Inc. 2709 Itay Sherman Texas Instruments, Inc. 2710 Mike Heard Consultant 2712 7. Security Considerations 2714 There are a number of management objects defined in this MIB that 2715 have a MAX-ACCESS clause of read-write and/or read-create. Such 2716 objects may be considered sensitive or vulnerable in some network 2717 environments. The support for SET operations in a non-secure 2718 environment without proper protection can have a negative effect on 2719 network operations. 2721 The following Differentiated Services Code Point (DSCP) and mask 2722 objects are used to differentiate between various types of traffic 2723 in the service provider network: 2725 pktcSigDefCallSigDscp 2726 pktcSigDefMediaStreamDscp 2728 These objects may contain information that may be sensitive from a 2729 business perspective. For example, they may represent a customer's 2730 service contract that a service provider chooses to apply to a 2731 customer's ingress or egress traffic. If these objects are SET 2732 maliciously, it may permit unmarked or inappropriately marked 2733 signaling and media traffic to enter the service provider network, 2734 resulting in unauthorized levels of service for customers. 2736 The following objects determine ring cadence, repeatable 2737 characteristics, signal duration, and caller id subscriber line 2738 protocol for telephony operation: 2740 pktcSigDevR0Cadence 2741 pktcSigDevR1Cadence 2742 pktcSigDevR2Cadence 2743 pktcSigDevR3Cadence 2744 pktcSigDevR4Cadence 2745 pktcSigDevR5Cadence 2746 pktcSigDevR6Cadence 2747 pktcSigDevR7Cadence 2748 pktcSigDevRgCadence 2749 pktcSigDevRsCadence 2750 pktcSigDevCallerIdSigProtocol 2751 pktcSigPulseSignalDuration 2752 pktcSigPulseSignalPauseDuration 2754 If these objects are SET maliciously, it may result in unwanted 2755 operation, or a failure to obtain telephony service from client 2756 (MTA) devices. 2758 The objects in the pktcNcsEndPntConfigTable are used for end point 2759 signaling. The pktcNcsEndPntConfigCallAgentId object contains the 2760 name of the call agent, which includes the call agent Fully 2761 Qualified Domain Name (FQDN). If this object is SET maliciously, the 2762 MTA will not be able to communicate with the call agent, resulting 2763 in a disruption of telephony service. The 2764 pktcNcsEndPntConfigCallAgentUdpPort object identifies the UDP port 2765 for NCS signaling traffic. If this object is SET maliciously, the 2766 call agent will not receive NCS signaling traffic from the MTA, also 2767 resulting in a disruption of telephony service. 2769 Some of the readable objects in this MIB module (i.e., objects with 2770 a MAX-ACCESS other than not-accessible) may be considered sensitive 2771 or vulnerable in some network environments. It is thus important to 2772 control even GET and/or NOTIFY access to these objects and possibly 2773 to even encrypt the values of these objects when sending them over 2774 the network via SNMP. The most sensitive is 2775 pktcNcsEndPntStatusCallIpAddress within pktcNcsEndPntConfigTable. 2776 This information itself may be valuable to would-be attackers. 2778 SNMP versions prior to SNMPv3 did not include adequate security. 2779 Even if the network itself is secure (for example by using IPSec), 2780 even then, there is no control as to who on the secure network is 2781 allowed to access and GET/SET (read/change/create/delete) the 2782 objects in this MIB module. 2784 It is RECOMMENDED that implementers consider the security features 2785 as provided by the SNMPv3 framework (see [RFC3410], section 8), 2786 including full support for the SNMPv3 cryptographic mechanisms (for 2787 authentication and privacy). 2789 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2790 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2791 enable cryptographic security. It is then a customer/operator 2792 responsibility to ensure that the SNMP entity giving access to an 2793 instance of this MIB module is properly configured to give access to 2794 the objects only to those principals (users) that have legitimate 2795 rights to indeed GET or SET (change/create/delete) them. 2797 8. IANA Considerations 2799 The MIB module in this document uses the following IANA-assigned 2800 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2802 Descriptor OBJECT IDENTIFIER Value 2803 ---------- ----------------------- 2804 pktcIetfSigMib { mib-2 XXX } 2806 Editor�s Note (to be removed prior to publication): the IANA is 2807 requested to assign a value for XXX under the mib-2 subtree and to 2808 record the assignment in the SMI Numbers registry. When the 2809 assignment has been made, the RFC Editor is asked to replace XXX 2810 (here and in the MIB module) with the assigned value and to remove 2811 this note. 2813 9. Normative References 2815 [PKT-SP-MIB-SIG-1.0] PacketCable� 1.0 Signaling MIB 2816 Specification, PKT-SP-MIB-SIG-I08-040113, January 2004. 2818 [PKT-SP-MIB-SIG-1.5] PacketCable� 1.5 Signaling MIB 2819 Specification, PKT-SP-MIB-SIG1.5-I01-050128, January 2820 2005. 2822 [ITU-T-J169] IPCablecom Network Call Signaling (NCS) MIB 2823 requirements, J.169, ITU-T, March, 2001. 2825 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2826 Requirement Levels", BCP 14, RFC 2119, March 1997. 2828 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2829 Rose, M., and S. Waldbusser, "Structure of Management 2830 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2831 1999. 2833 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2834 Rose, M., and S. Waldbusser, "Textual Conventions for 2835 SMIv2", STD 58, RFC 2579, April 1999. 2837 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2838 Rose, M., and S. Waldbusser, "Conformance Statements for 2839 SMIv2", STD 58, RFC 2580, April 1999. 2841 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information 2842 Base for the Differentiated Services Architecture", RFC 2843 3289, May 2002. 2845 [RFC3291] Daniel, M., Haberman, B., Routhier, S., and J. 2846 Schoenwaelder, "Textual Conventions for Internet Network 2847 Addresses", RFC 3291, May 2002. 2849 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen "An 2850 Architecture for Describing Simple Network Management 2851 Protocol (SNMP) Management Frameworks", RFC 3411, December 2852 2002. 2854 -- 2855 -- NOTES TO RFC EDITOR (to be removed prior to publication) 2856 -- 2857 -- The I-D (or a successor) is 2858 -- expected to eventually replace RFC 3291. If that draft (or a 2859 -- successor) is published as an RFC prior to, or concurrently with 2860 -- this document, then the normative reference [RFC3291] should be 2861 -- updated to point to the replacement RFC, and the reference tag 2862 -- [RFC3291] should be updated to match. 2863 -- 2865 [PKT-SP-CODEC] Packetcable Audio/Video Codecs Specification 2866 PKT-SP-CODEC-IO5-040113. 2868 [PKT-SP-MGCP] Packetcable Network-Based Call Signaling Protocol 2869 Specification PKT-SP-EC-MGCP-I10-040402. 2871 [PKT-SP-PROV] Packetcable MTA Device Provisioning Specification 2872 PKT-SP-PROV-I10-040730. 2874 10. Informative References 2876 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2877 "Introduction and Applicability Statements for Internet- 2878 Standard Management Framework", RFC 3410, December 2002. 2880 [RFC3435] Andreasen, F., and B. Foster, "Media Gateway Control 2881 Protocol (MGCP)", RFC 3435, January 2003. 2883 [PKT-SP-MIB-MTA] Packetcable MTA MIB Specification PKT-SP-MIB-MTA- 2884 I09-040402. 2886 [ETSI TS 101 909-4] ETSI TS 101 909-4:"Access and Terminals (AT); 2887 Digital Broadband Cable Access to the Public 2888 Telecommunications Network; IP Multimedia Time 2889 Critical Services; Part 4: Network Call 2890 Signaling Protocol". 2892 [ETSI TS 101 909-9] ETSI TS 101 909-9:"Access and Terminals (AT); 2893 Digital Broadband Cable Access to the Public 2894 Telecommunications Network; IP Multimedia Time 2895 Critical Services; Part 9: IPCablecom Network 2896 Call Signalling (NCS) MIB Requirements". 2898 [EN 300 001] EN 300 001 V1.5.1 (1998-10):"European Standard 2899 (Telecommunications series) Attachments to Public 2900 Switched Telephone Network (PSTN); General technical 2901 requirements for equipment connected to an analogue 2902 subscriber interface in the PSTN; Chapter 3: Ringing 2903 signal characteristics (national deviations are in 2904 Table 3.1.1)". 2906 [EN 300 324-1] EN 300 324-1 V2.1.1 (2000-04):"V Interfaces at the 2907 digital Loop Exchange (LE); V5.1 interface for the 2908 support of Access Network (AN); Part 1: V5.1 2909 interface specification". 2911 [EN 300 659-1] EN 300 659-1: "Public Switched Telephone Network 2912 (PSTN); Subscriber line protocol over the local loop 2913 for display (and related) services; Part 1: On hook 2914 data transmission". 2916 [ITU-T E.180] ITU-T: "Various Tones Used in National Networks, 2917 Supplement 2 to Recommendation E.180". 2919 [TR 101 183] TR 101 183: "Public Switched Telephone Network (PSTN) 2920 Analogue Ringing Signals". 2922 Authors' Addresses 2924 Gordon Beacham 2925 Motorola, Inc. 2926 6450 Sequence Drive, Bldg. 1 2927 San Diego, CA 92121, USA 2928 +1 858-404-2335 2929 gordon.beacham@motorola.com 2931 Satish Kumar Mudugere Eswaraiah 2932 Texas Instruments India (P) Ltd., 2933 Golf view, Wind Tunnel Road 2934 Murugesh Palya 2935 Bangalore 560 017, INDIA 2936 +91 80 5269451 2937 satish.kumar@ti.com 2939 Sumanth Channabasappa 2940 Cable Television Laboratories, Inc. 2941 858 Coal Creek Circle, 2942 Louisville, CO 80027, USA 2943 +1 303-661-3307 2944 Sumanth@cablelabs.com 2946 Disclaimer of validity 2948 The IETF takes no position regarding the validity or scope of any 2949 Intellectual Property Rights or other rights that might be claimed 2950 to pertain to the implementation or use of the technology described 2951 in this document or the extent to which any license under such 2952 rights might or might not be available; nor does it represent that 2953 it has made any independent effort to identify any such rights. 2954 Information on the procedures with respect to rights in RFC 2955 documents can be found in BCP 78 and BCP 79. 2957 Copies of IPR disclosures made to the IETF Secretariat and any 2958 assurances of licenses to be made available, or the result of an 2959 attempt made to obtain a general license or permission for the use 2960 of such proprietary rights by implementers or users of this 2961 specification can be obtained from the IETF on-line IPR repository 2962 at http://www.ietf.org/ipr. 2964 The IETF invites any interested party to bring to its attention any 2965 copyrights, patents or patent applications, or other proprietary 2966 rights that may cover technology that may be required to implement 2967 this standard. Please address the information to the IETF at 2968 ietf-ipr@ietf.org. 2970 Full Copyright Statement 2972 Copyright (C) The Internet Society (2005). This document is subject 2973 to the rights, licenses and restrictions contained in BCP 78, and 2974 except as set forth therein, the authors retain all their rights. 2976 This document and the information contained herein are provided on 2977 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 2978 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 2979 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 2980 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2981 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2982 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.