idnits 2.17.1 draft-ietf-ipcdn-pktc-signaling-14.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.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 3665. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3635. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3642. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3648. ** The document seems to lack an RFC 3978 Section 5.4 (updated by RFC 4748) Copyright Line. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (July 2007) is 6130 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 3597, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'PKT-SP-SEC' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-T-J169' -- 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' -- Obsolete informational reference (is this intentional?): RFC 4234 (Obsoleted by RFC 5234) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IPCDN Gordon Beacham 2 Internet-Draft Motorola, Inc. 3 Intended status: Proposed Standard Satish Kumar 4 Expires: January 2008 Texas Instruments 5 Sumanth Channabasappa 6 CableLabs 7 July 2007 9 Network-Based Call Signaling (NCS) MIB for PacketCable and 10 IPCablecom Multimedia Terminal Adapters (MTAs) 11 draft-ietf-ipcdn-pktc-signaling-14 13 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months and may be updated, replaced, or obsoleted by other documents 26 at any time. It is inappropriate to use Internet-Drafts as 27 reference material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 Abstract 37 This memo defines a portion of the Management Information Base (MIB) 38 for use with network management protocols in the Internet community. 39 In particular, it defines a basic set of managed objects for Simple 40 Network Management Protocol (SNMP)-based management of PacketCable- 41 and IPCablecom-compliant Multimedia Terminal Adapter devices. 43 Table of Contents 45 1. The Internet-Standard Management Framework....................2 46 2. Introduction..................................................2 47 3. Terminology...................................................3 48 3.1 MTA.......................................................3 49 3.2 Endpoint..................................................3 50 3.3 L Line Package............................................4 51 3.4 E Line Package............................................4 52 4. Overview......................................................4 53 4.1 Structure of the MIB......................................5 54 4.2 pktcSigDevObjects..............Error! Bookmark not defined. 55 4.3 pktcSigConformance........................................6 56 5. Definitions...................................................7 57 6. Examples.....................................................68 58 7. Acknowledgments..............................................70 59 8. Security Considerations......................................71 60 9. IANA Considerations..........................................73 61 10. Normative References........................................73 62 11. Informative References......................................75 63 Authors' Addresses..............................................76 64 Disclaimer of validity..........................................76 65 Full Copyright Statement........................................77 67 1. The Internet-Standard Management Framework 69 For a detailed overview of the documents that describe the current 70 Internet-Standard Management Framework, please refer to section 7 of 71 RFC 3410 [RFC3410]. 73 Managed objects are accessed via a virtual information store, termed 74 the Management Information Base or MIB. MIB objects are generally 75 accessed through the Simple Network Management Protocol (SNMP). 76 Objects in the MIB are defined using the mechanisms defined in the 77 Structure of Management Information (SMI). This memo specifies a MIB 78 module that is compliant to the SMIv2, which is described in STD 58, 79 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 80 [RFC2580]. 82 2. Introduction 84 A multimedia terminal adapter (MTA) is used to deliver broadband 85 Internet, data, and/or voice access jointly with telephony service 86 to a subscriber's or customer's premises using a cable network 87 infrastructure. An MTA is normally installed at the customer's or 88 subscriber's premises, and it is coupled to a multiple system 89 operator (MSO) using a hybrid fiber coax (HFC) access network. 91 An MTA is provisioned by the MSO for broadband Internet, data, 92 and/or voice service. For more information on MTA provisioning refer 93 to the PacketCable Provisioning Specification [PKT-SP-PROV] and 94 [RFC4682]. MTA devices include one or more endpoints (e.g., 95 telephone ports) which receive call signaling information to 96 establish ring cadence, and codecs used for providing telephony 97 service. For more information on call signaling refer to the 98 PacketCable Signaling Specification [PKT-SP-MGCP] and [RFC3435]. For 99 more information on codecs refer to the Packetcable Audio/Video 100 Codecs Specification [PKT-SP-CODEC]. 102 Telephone systems are typically very complex and often have a wide 103 distribution. It is therefore important for management systems to 104 support MTAs from multiple vendors at the same time, including those 105 from multiple countries. This MIB module provides objects suitable 106 for managing signaling for MTA devices in the widest possible range 107 of markets. 109 3. Terminology 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 113 document are to be interpreted as described in RFC 2119 [RFC2119]. 115 The terms "MIB module" and "information module" are used 116 interchangeably in this memo. As used here, both terms refer to any 117 of the three types of information modules defined in Section 3 of 118 RFC 2578 [RFC2578]. 120 3.1 MTA 122 An MTA is a PacketCable or IPCablecom compliant device providing 123 telephony services over a cable or hybrid system used to deliver 124 video signals to a community. It contains an interface to endpoints, 125 a network interface, codecs, and all signaling and encapsulation 126 functions required for Voice over IP transport, call signaling, and 127 Quality of Service signaling. An MTA can be an embedded or a 128 standalone device. An Embedded MTA (E-MTA) is an MTA device 129 containing an embedded Data Over Cable Service Interface 130 Specifications (DOCSIS) Cable Modem. A Standalone MTA (S-MTA) is an 131 MTA device separated from the DOCSIS Cable Modem by non-DOCSIS MAC 132 interface (e.g., Ethernet, USB). 134 3.2 Endpoint 136 An endpoint or MTA endpoint is a standard telephony physical port 137 located on the MTA and used for attaching the telephone device to 138 the MTA. 140 3.3 L Line Package 142 The L line package refers to the MGCP package for the core signaling 143 functionality as defined by PacketCable and IPCablecom. An MTA 144 provides all L package elements, however the operator determines 145 their application. 147 3.4 E Line Package 149 The E line package refers to the MGCP package extensions, over and 150 above the core L package, defined in support of international 151 requirements. E line package elements are optional, vary from 152 country to country, and are set by operator or regulatory 153 requirements. 155 4. Overview 156 This MIB module provides a set of objects required for Multimedia 157 Terminal Adapter (MTA) devices compliant with the PacketCable and 158 IPCablecom signaling specifications published by CableLabs, the 159 European Telecommunications Standards Institute (ETSI), and the 160 International Telecommunication Union Telecommunication 161 Standardization Sector (ITU-T)IPCablecom compliant Multimedia 162 Terminal Adapter (MTA) devices. The Signaling MIB module (PKTC-SIG- 163 MIB) is intended to update various Signaling MIB modules from which 164 it is partly derived: 165 - the PacketCable 1.0 Signaling MIB Specification 166 [PKT-SP-MIB-SIG-1.0], 167 - the PacketCable 1.5 Signaling MIB Specification 168 [PKT-SP-MIB-SIG-1.5], 169 - the ITU-T IPCablecom Signaling MIB requirements [ITU-T-J169], 170 - the ETSI Signaling MIB [ETSI-TS-101-909-9]. The ETSI Signaling 171 MIB requirements also refer to various signal characteristics 172 defined in [ETSI-TS-101-909-4], [ETSI-EN-300-001], 173 [ETSI-EN-300-659-1], [ETSI-EN-300-324-1] and [ETSI-TR-101-183]. 174 Several normative and informative references are used to help define 175 Signaling MIB objects. As a convention, wherever PacketCable and 176 IPCablecom requirements are equivalent, the PacketCable reference is 177 used in the object REFERENCE clause. IPCablecom compliant MTA 178 devices MUST use the equivalent IPCablecom references. 180 This MIB module describes the various Signaling MIB objects that are 181 directly related to the PacketCable MTA and the endpoints supported 182 on the MTA, each of which provides services independently. The 183 recognition and distinction of the endpoints is made by utilizing 184 the ifTable (IF-MIB [RFC2863]), where each index (ifIndex) refers to 185 a unique endpoint. This MIB module also utilizes the syntax 186 definition of the Differentiated Services Code Point (DSCP) from 187 DIFFSERV-DSCP-TC [RFC3289] for defining MIB objects that allow for 188 differentiation between various types of traffic in the service 189 provider network. 191 4.1 Structure of the MIB 193 This MIB module is identified by pktcSigMib and is structured into 194 two major parts: 196 - Signaling information that control device and endpoint 197 configuration (pktcSigMibObjects) 199 - Module Conformance information(pktcSigConformance) 201 The following sections explain each part in further detail. It is to 202 be noted that future enhancements to specify Notification Objects is 203 also allowed(pktcSigNotification). 205 4.2 pktcSigMibObjects 207 This is further divided into device-specific elements 208 (pktcSigDevObjects) and endpoint-specific elements 209 (pktcNcsEndPntConfigObjects). 211 Some highlights of the device-specific elements are as follows: 213 pktcSigDevCodecTable - this object identifies the codec types 214 available on the device. 216 pktcSigDevEchoCancellation - This object identifies the capability 217 of echo cancellation on the device. 219 pktcSigDevSilenceSuppression - This object specifies if the device 220 is capable of silence suppression (Voice Activity Detection). 222 pktcSigPulseSignalTable - this international object selects the 223 various signals used in the application of the metering pulse signal 224 to the twisted pair line. 226 pktcSigDevToneTable - this international table specifies a flexible 227 structure within which to specify all of the tones used in the MTA. 229 pktcSigDevMultiFreqToneTable - this table defines the 230 characteristics of tones with multiple frequencies. Each entry in 231 this table represents the frequency reference of a multi-frequency 232 tone. 234 The endpoint-specific elements are mostly confined to the Endpoint 235 configuration MIB table (pktcNcsEndPntConfigTable). This table 236 describes the PacketCable NCS endPoint configuration. The number of 237 entries in this table represents the number of provisioned 238 endpoints. 240 4.3 pktcSigConformance 242 pktcNcsDeviceGroup - this group contains all the MIB Objects that 243 apply on a per-device basis and need to be implemented by an MTA to 244 claim compliance with the specified MIB module. 246 pktcNcsEndpointGroup - this group contains all the MIB Objects that 247 apply on a per-endpoint basis and need to be implemented by an MTA 248 to claim compliance with the specified MIB module. 250 pktcLLinePackageGroup - this group contains the MIB Objects that 251 need to be implemented to support the L Line Package. 253 pktcELinePackageGroup - this group contains the MIB Objects that 254 need to be implemented to support the E Line Package. 256 pktcInternationalGroup - this group contains optional MIB Objects 257 designed to support operations over the widest possible range of 258 markets. 260 5. Definitions 262 PKTC-SIG-MIB DEFINITIONS ::= BEGIN 264 IMPORTS 265 MODULE-IDENTITY, 266 OBJECT-TYPE, 267 Integer32, 268 Unsigned32, 269 mib-2 270 FROM SNMPv2-SMI -- [RFC2578] 271 InetAddressType, 272 InetAddress, 273 InetPortNumber 274 FROM INET-ADDRESS-MIB -- [RFC4001] 275 TEXTUAL-CONVENTION, 276 RowStatus, 277 TruthValue 278 FROM SNMPv2-TC -- [RFC2579] 279 OBJECT-GROUP, 280 MODULE-COMPLIANCE 281 FROM SNMPv2-CONF -- [RFC2580] 282 SnmpAdminString 283 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 284 ifIndex 285 FROM IF-MIB -- [RFC2863] 286 Dscp 287 FROM DIFFSERV-DSCP-TC; -- [RFC3289] 289 pktcSigMib MODULE-IDENTITY 290 LAST-UPDATED "200707070000Z" -- July 07, 2007 291 ORGANIZATION "IETF IPCDN Working Group" 292 CONTACT-INFO 293 "Sumanth Channabasappa 294 Cable Television Laboratories, Inc. 295 858 Coal Creek Circle, 296 Louisville, CO 80027, USA 297 Phone: +1 303-661-3307 298 Email: Sumanth@cablelabs.com 299 Gordon Beacham 300 Motorola, Inc. 301 6450 Sequence Drive, Bldg. 1 302 San Diego, CA 92121, USA 303 Phone: +1 858-404-2335 304 Email: gordon.beacham@motorola.com 306 Satish Kumar Mudugere Eswaraiah 307 Texas Instruments India (P) Ltd., 308 Golf view, Wind Tunnel Road 309 Murugesh Palya 310 Bangalore 560 017, INDIA 311 Phone: +91 80 5269451 312 Email: satish.kumar@ti.com 314 IETF IPCDN Working Group 315 General Discussion: ipcdn@ietf.org 316 Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn 317 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 318 Co-Chair: Jean-Francois Mule, jf.mule@cablelabs.com 319 Co-Chair: Richard Woundy, Richard_Woundy@cable.comcast.com" 321 DESCRIPTION 322 "This MIB module supplies the basic management 323 object for the PacketCable and IPCablecom Signaling 324 protocols. This version of the MIB includes 325 common signaling and Network Call Signaling 326 (NCS) related signaling objects. 328 Copyright (C) The IETF Trust (2007). This version of 329 this MIB module is part of RFC yyyy; see the RFC itself for 330 full legal notices." 331 -- RFC Ed: replace yyyy with actual RFC number and remove this note 333 REVISION "200707070000Z" 335 DESCRIPTION 336 "Initial version, published as RFC yyyy." 337 -- RFC Ed: replace yyyy with actual RFC number and remove this note 339 ::= { mib-2 XXX } 340 -- RFC Ed: replace XXX with IANA-assigned number and remove this 341 -- note 343 -- Textual Conventions 345 TenthdBm ::= TEXTUAL-CONVENTION 346 DISPLAY-HINT "d-1" 347 STATUS current 348 DESCRIPTION 349 "This textual convention represents power levels that are 350 normally expressed in dBm. Units are in tenths of a dBm; 351 for example, -13.5 dBm will be represented as -135." 352 SYNTAX Integer32 354 PktcCodecType ::= TEXTUAL-CONVENTION 355 STATUS current 356 DESCRIPTION 357 " This textual convention defines various types of codecs 358 that MAY be supported. The description for each 359 enumeration is listed below: 360 Enumeration Description 361 other a defined codec not in the enumeration 362 unknown a codec not defined by the PacketCable 363 Codec Specification 364 g729 ITU-T Recommendation G.729 365 reserved for future use 366 g729E ITU-T Recommendation G.729E 367 pcmu Pulse Code Modulation u-law (PCMU) 368 g726at32 ITU-T Recommendation G.726-32 (32 kbit/s) 369 g728 ITU-T Recommendation G.728 370 pcma Pulse Code Modulation a-law (PCMA) 371 g726at16 ITU-T Recommendation G.726-16 (16 kbit/s) 372 g726at24 ITU-T Recommendation G.726-24 (24 kbit/s) 373 g726at40 ITU-T Recommendation G.726-40 (40 kbit/s) 374 ilbc IETF internet low bit rate codec 375 bv16 Broadcom BroadVoice16 377 The list of codecs is consistent with the IETF 378 Real Time Transport Protocol (RTP) Profile registry and 379 the RTP Map Parameters Table in Packetcable Audio/Video 380 Codecs Specification [PKT-SP-CODEC]. The literal codec 381 name for each codec is listed below: 382 Codec Literal Codec Name 383 g729 G729 384 g729E G729E 385 pcmu PCMU 386 g726at32 G726-32 387 g728 G728 388 pcma PCMA 389 g726at16 G726-16 390 g726at24 G726-24 391 g726at40 G726-40 392 ilbc iLBC 393 bv16 BV16 395 The literal codec name is the second column of the table 396 with codec RTP Map Parameters. Literal Codec Name Column 397 contains the codec name used in the local connection 398 options (LCO) of the NCS messages create connection 399 (CRCX)/modify connection (MDCX) and is also used to 400 identify the codec in the Call Management System (CMS) 401 Provisioning Specification. RTP Map Parameter Column of 402 the Table contains the string used in the media attribute 403 line (a=) of the session description protocol (SDP) 404 parameters in NCS messages." 405 SYNTAX INTEGER { 406 other (1), 407 unknown (2), 408 g729 (3), 409 reserved (4), 410 g729E (5), 411 pcmu (6), 412 g726at32 (7), 413 g728 (8), 414 pcma (9), 415 g726at16 (10), 416 g726at24 (11), 417 g726at40 (12), 418 ilbc (13), 419 bv16 (14) 420 } 422 PktcRingCadence ::= TEXTUAL-CONVENTION 423 STATUS current 424 DESCRIPTION 425 "This object provides an encoding scheme for ring 426 cadences, including repeatability characteristics. All 427 fields in this object MUST be encoded in network-byte 428 order. 430 The first three higher order octets are reserved. The 431 octets that follow are used to encode a 'bit-string', with 432 each bit corresponding to 50 milliseconds. A bit value of 433 '1' indicates the presence of a ring-tone and a bit value 434 of '0' indicates the absence of a ring-tone, for that 435 duration (50 ms) (Note: A minimum number of octets 436 required to encode the bit-string MUST be used). 438 The first two of the reserved octets MUST indicate the 439 length of the encoded cadence (in bits) and MUST range 440 between 1 and 264. (Note: The length in bits MUST also be 441 consistent with the number of octets that encode the 442 cadence). The MTA MUST ignore any unused bits in the last 443 octet, but MUST reflect the value as provided on 444 subsequent SNMP GETs. 446 The third of the reserved octets indicates 'repeatability' 447 and MUST be either 0x80 or 0x00 - the former value 448 indicating 'non-repeatability' and the latter indicating 449 'repeatability'. 451 The MTA MUST reject attempts to set a value that violates 452 any of the above requirements" 454 SYNTAX OCTET STRING (SIZE(4..36)) 456 PktcSigType ::= TEXTUAL-CONVENTION 457 STATUS current 458 DESCRIPTION 459 " This object lists the various types of signaling that may 460 be supported: 461 other(1) - set when signaling other than NCS is used 462 ncs(2) - Network call signaling is a derivation of MGCP 463 (Media Gateway Control Protocol) defined for 464 IPCablecom/PacketCable MTAs." 465 SYNTAX INTEGER { 466 other(1), 467 ncs(2) 468 } 470 DtmfCode::=TEXTUAL-CONVENTION 471 STATUS current 472 DESCRIPTION 473 "This textual convention represents the DTMF Character used 474 to indicate the start or end of the digit transition 475 sequence used for Caller ID or VMWI. 476 Note: The DTMF code '*' is indicated using 'dtmfcodeStar' 477 and the DTMF code '#' is indicated using ' dtmfcodeHash'." 478 SYNTAX INTEGER { 479 dtmfcode0(0), 480 dtmfcode1(1), 481 dtmfcode2(2), 482 dtmfcode3(3), 483 dtmfcode4(4), 484 dtmfcode5(5), 485 dtmfcode6(6), 486 dtmfcode7(7), 487 dtmfcode8(8), 488 dtmfcode9(9), 489 dtmfcodeStar(10), 490 dtmfcodeHash(11), 491 dtmfcodeA(12), 492 dtmfcodeB(13), 493 dtmfcodeC(14), 494 dtmfcodeD(15) 495 } 497 pktcSigMibObjects OBJECT IDENTIFIER ::= { pktcSigMib 1 } 498 pktcSigDevObjects OBJECT IDENTIFIER ::= 499 { pktcSigMibObjects 1 } 500 pktcNcsEndPntConfigObjects OBJECT IDENTIFIER ::= 501 { pktcSigMibObjects 2 } 502 -- 503 -- The codec table (pktcSigDevCodecTable) defines all combinations 504 -- of codecs supported by the Multimedia Terminal Adapter (MTA). 505 -- 506 pktcSigDevCodecTable OBJECT-TYPE 507 SYNTAX SEQUENCE OF PktcSigDevCodecEntry 508 MAX-ACCESS not-accessible 509 STATUS current 510 DESCRIPTION 511 " This table describes the MTA supported codec types. An MTA 512 MUST populate this table with all possible combinations of 513 codecs it supports for simultaneous operation. For 514 example, an MTA with two endpoints may be designed with a 515 particular DSP and memory architecture that allows it to 516 support the following fixed combinations of codecs for 517 simultaneous operation: 519 Codec Type Maximum Number of Simultaneous Codecs 520 PCMA 3 522 PCMA 2 523 PCMU 1 525 PCMA 1 526 PCMU 2 528 PCMU 3 530 PCMA 1 531 G729 1 533 G729 2 535 PCMU 1 536 G729 1 538 Based on this example, the entries in the codec table 539 would be: 541 pktcSigDev pktcSigDev pktcSigDev 542 CodecComboIndex CodecType CodecMax 543 1 pcma 3 544 2 pcma 2 545 2 pcmu 1 546 3 pcma 1 547 3 pcmu 2 548 4 pcmu 3 549 5 pcma 1 550 5 g729 1 551 6 g729 2 552 7 pcmu 1 553 7 g729 1 555 An operator querying this table is able to determine all 556 possible codec combinations the MTA is capable of 557 simultaneously supporting. 558 This table MUST NOT include non-voice codecs." 559 ::= { pktcSigDevObjects 1 } 561 pktcSigDevCodecEntry OBJECT-TYPE 562 SYNTAX PktcSigDevCodecEntry 563 MAX-ACCESS not-accessible 564 STATUS current 565 DESCRIPTION 566 "Each entry represents the maximum number of active 567 connections with a particular codec the MTA is capable of 568 supporting. Each row is indexed by a composite key 569 consisting of a number enumerating the particular codec 570 combination and the codec type." 571 INDEX { pktcSigDevCodecComboIndex, pktcSigDevCodecType } 572 ::= { pktcSigDevCodecTable 1 } 574 PktcSigDevCodecEntry ::= SEQUENCE { 575 pktcSigDevCodecComboIndex Unsigned32, 576 pktcSigDevCodecType PktcCodecType, 577 pktcSigDevCodecMax Unsigned32 578 } 580 pktcSigDevCodecComboIndex OBJECT-TYPE 581 SYNTAX Unsigned32 (1..255) 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 " The index value which enumerates a particular codec 586 combination in the pktcSigDevCodecTable." 587 ::= { pktcSigDevCodecEntry 1 } 588 pktcSigDevCodecType OBJECT-TYPE 589 SYNTAX PktcCodecType 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 " A codec type supported by this MTA." 594 ::= { pktcSigDevCodecEntry 2 } 596 pktcSigDevCodecMax OBJECT-TYPE 597 SYNTAX Unsigned32(1..255) 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 " The maximum number of simultaneous sessions of a 602 particular codec that the MTA can support." 603 ::= { pktcSigDevCodecEntry 3 } 605 -- 606 -- These are the common signaling related definitions that affect 607 -- the entire MTA device. 608 -- 610 pktcSigDevEchoCancellation OBJECT-TYPE 611 SYNTAX TruthValue 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 " This object specifies if the device is capable of echo 616 cancellation. The MTA MUST set this MIB Object to a 617 value of true(1) if it is capable of echo 618 cancellation; and a value of false(2) if not." 619 ::= { pktcSigDevObjects 2 } 621 pktcSigDevSilenceSuppression OBJECT-TYPE 622 SYNTAX TruthValue 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 " This object specifies if the device is capable of 627 silence suppression (as a result of Voice Activity 628 Detection). The MTA MUST set this MIB Object to a 629 value of true(1) if it is capable of silence 630 suppression; and a value of false(2) if not." 631 ::= { pktcSigDevObjects 3 } 633 pktcSigDevCidSigProtocol OBJECT-TYPE 634 SYNTAX INTEGER { 635 fsk (1), 636 dtmf (2) 637 } 638 MAX-ACCESS read-write 639 STATUS current 640 DESCRIPTION 641 "This object is used to configure the subscriber line 642 protocol used for signaling on-hook caller id information. 643 Different countries define different caller id signaling 644 protocols to support caller identification. 646 Setting this object at a value fsk(1) sets the subscriber 647 line protocol to be Frequency Shift Keying (FSK). 649 Setting this object at a value dtmf(2) sets the subscriber 650 line protocol to be Dual tone multi-frequency (DTMF). 652 The value of this MIB Object MUST NOT persist across MTA 653 reboots." 654 REFERENCE 655 "ETSI-EN-300-659-1 Specification" 656 DEFVAL { fsk } 657 ::= { pktcSigDevObjects 4 } 659 pktcSigDevR0Cadence OBJECT-TYPE 660 SYNTAX PktcRingCadence 661 MAX-ACCESS read-write 662 STATUS current 663 DESCRIPTION 664 " This object specifies ring cadence 0 (a user defined 665 field). 667 The value of this MIB Object MUST NOT persist across MTA 668 reboots." 669 ::= { pktcSigDevObjects 5 } 671 pktcSigDevR1Cadence OBJECT-TYPE 672 SYNTAX PktcRingCadence 673 MAX-ACCESS read-write 674 STATUS current 675 DESCRIPTION 676 " This object specifies ring cadence 1 (a user defined 677 field). 679 The value of this MIB Object MUST NOT persist across MTA 680 reboots." 681 ::= { pktcSigDevObjects 6 } 683 pktcSigDevR2Cadence OBJECT-TYPE 684 SYNTAX PktcRingCadence 685 MAX-ACCESS read-write 686 STATUS current 687 DESCRIPTION 688 " This object specifies ring cadence 2 (a user defined 689 field). 691 The value of this MIB Object MUST NOT persist across MTA 692 reboots." 693 ::= { pktcSigDevObjects 7 } 695 pktcSigDevR3Cadence OBJECT-TYPE 696 SYNTAX PktcRingCadence 697 MAX-ACCESS read-write 698 STATUS current 699 DESCRIPTION 700 " This object specifies ring cadence 3 (a user defined 701 field). 703 The value of this MIB Object MUST NOT persist across MTA 704 reboots." 705 ::= { pktcSigDevObjects 8 } 707 pktcSigDevR4Cadence OBJECT-TYPE 708 SYNTAX PktcRingCadence 709 MAX-ACCESS read-write 710 STATUS current 711 DESCRIPTION 712 " This object specifies ring cadence 4 (a user defined 713 field). 715 The value of this MIB Object MUST NOT persist across MTA 716 reboots." 717 ::= { pktcSigDevObjects 9 } 719 pktcSigDevR5Cadence OBJECT-TYPE 720 SYNTAX PktcRingCadence 721 MAX-ACCESS read-write 722 STATUS current 723 DESCRIPTION 724 " This object specifies ring cadence 5 (a user defined 725 field). 727 The value of this MIB Object MUST NOT persist across MTA 728 reboots." 729 ::= { pktcSigDevObjects 10 } 731 pktcSigDevR6Cadence OBJECT-TYPE 732 SYNTAX PktcRingCadence 733 MAX-ACCESS read-write 734 STATUS current 735 DESCRIPTION 736 " This object specifies ring cadence 6 (a user defined 737 field). 739 The value of this MIB Object MUST NOT persist across MTA 740 reboots." 741 ::= { pktcSigDevObjects 11 } 743 pktcSigDevR7Cadence OBJECT-TYPE 744 SYNTAX PktcRingCadence 745 MAX-ACCESS read-write 746 STATUS current 747 DESCRIPTION 748 " This object specifies ring cadence 7 (a user defined 749 field). 751 The value of this MIB Object MUST NOT persist across MTA 752 reboots." 753 ::= { pktcSigDevObjects 12 } 755 pktcSigDevRgCadence OBJECT-TYPE 756 SYNTAX PktcRingCadence 757 MAX-ACCESS read-write 758 STATUS current 759 DESCRIPTION 760 " This object specifies ring cadence rg (a user defined 761 field). 763 The value of this MIB Object MUST NOT persist across MTA 764 reboots." 765 ::= { pktcSigDevObjects 13 } 767 pktcSigDevRsCadence OBJECT-TYPE 768 SYNTAX PktcRingCadence 769 MAX-ACCESS read-write 770 STATUS current 771 DESCRIPTION 772 " This object specifies ring cadence rs (a user defined 773 field) The MTA MUST reject any attempt to make this object 774 repeatable. 776 The value of this MIB Object MUST NOT persist across MTA 777 reboots." 778 ::= { pktcSigDevObjects 14 } 780 pktcSigDefCallSigDscp OBJECT-TYPE 781 SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC 782 MAX-ACCESS read-write 783 STATUS current 784 DESCRIPTION 785 " The default value used in the IP header for setting the 786 Differentiated Services Code Point (DSCP) value for call 787 signaling. 789 The value of this MIB Object MUST NOT persist across MTA 790 reboots." 791 DEFVAL { 0 } 792 ::= { pktcSigDevObjects 15 } 794 pktcSigDefMediaStreamDscp OBJECT-TYPE 795 SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC 796 MAX-ACCESS read-write 797 STATUS current 798 DESCRIPTION 799 " This object contains the default value used in the IP 800 header for setting the Differentiated Services Code Point 801 (DSCP) value for media stream packets. The MTA MUST NOT 802 update this object with the value supplied by the CMS in 803 the NCS messages (if present). Any currently active 804 connections are not affected by updates to this object. 805 When the value of this object is updated by SNMP, the MTA 806 MUST use the new value as a default starting only from 807 new connections. 809 The value of this MIB Object MUST NOT persist across MTA 810 reboots." 811 DEFVAL { 0 } 812 ::= { pktcSigDevObjects 16 } 814 -- 815 -- pktcSigCapabilityTable - This table defines the valid signaling 816 -- types supported by this MTA. 817 -- 819 pktcSigCapabilityTable OBJECT-TYPE 820 SYNTAX SEQUENCE OF PktcSigCapabilityEntry 821 MAX-ACCESS not-accessible 822 STATUS current 823 DESCRIPTION 824 " This table describes the signaling types supported by this 825 MTA." 826 ::= { pktcSigDevObjects 17 } 828 pktcSigCapabilityEntry OBJECT-TYPE 829 SYNTAX PktcSigCapabilityEntry 830 MAX-ACCESS not-accessible 831 STATUS current 832 DESCRIPTION 833 " Entries in pktcMtaDevSigCapabilityTable - List of 834 supported signaling types, versions and vendor extensions 835 for this MTA. Each entry in the list provides for one 836 signaling type and version combination. If the device 837 supports multiple versions of the same signaling type it 838 will require multiple entries." 839 INDEX { pktcSigCapabilityIndex } 840 ::= { pktcSigCapabilityTable 1 } 842 PktcSigCapabilityEntry ::= SEQUENCE { 843 pktcSigCapabilityIndex Unsigned32, 844 pktcSigCapabilityType PktcSigType, 845 pktcSigCapabilityVersion SnmpAdminString, 846 pktcSigCapabilityVendorExt SnmpAdminString 847 } 849 pktcSigCapabilityIndex OBJECT-TYPE 850 SYNTAX Unsigned32 (1..255) 851 MAX-ACCESS not-accessible 852 STATUS current 853 DESCRIPTION 854 " The index value which uniquely identifies an entry in the 855 pktcSigCapabilityTable." 856 ::= { pktcSigCapabilityEntry 1 } 858 pktcSigCapabilityType OBJECT-TYPE 859 SYNTAX PktcSigType 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 " This object identifies the type of signaling used. This 864 value has to be associated with a single signaling 865 version." 866 ::= { pktcSigCapabilityEntry 2 } 868 pktcSigCapabilityVersion OBJECT-TYPE 869 SYNTAX SnmpAdminString 870 MAX-ACCESS read-only 871 STATUS current 872 DESCRIPTION 873 " Provides the version of the signaling type - reference 874 pktcSigCapabilityType. Examples would be 1.0 or 2.33 etc." 875 ::= { pktcSigCapabilityEntry 3 } 877 pktcSigCapabilityVendorExt OBJECT-TYPE 878 SYNTAX SnmpAdminString 879 MAX-ACCESS read-only 880 STATUS current 881 DESCRIPTION 882 " The vendor extension allows vendors to provide a list of 883 additional capabilities. 885 The syntax for this MIB Object in ABNF ([RFC4234]) is 886 specified to be zero or more occurrences of vendor 887 extensions, as follows: 889 pktcSigCapabilityVendorExt = *(vendor-extension) 890 vendor-extension = (ext symbol alphanum) DQUOTE ; DQUOTE 891 ext = DQUOTE %x58 DQUOTE 892 symbol = (DQUOTE %x2D DQUOTE)/(DQUOTE %x2D DQUOTE) 893 alphanum = 1*6(ALPHA/DIGIT) 895 " 896 ::= { pktcSigCapabilityEntry 4 } 898 pktcSigDefNcsReceiveUdpPort OBJECT-TYPE 899 SYNTAX InetPortNumber (1025..65535) 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 " This object contains the MTA User Datagram Protocol (UDP) 904 receive port that is being used for NCS call signaling. 905 This object should only be changed by the configuration 906 file. 907 Unless changed via configuration this MIB Object MUST 908 reflect a value of '2427'." 909 REFERENCE 910 "PacketCable NCS Specification" 911 ::= { pktcSigDevObjects 18 } 913 pktcSigPowerRingFrequency OBJECT-TYPE 914 SYNTAX INTEGER { 915 f20Hz(1), 916 f25Hz(2), 917 f33Point33Hz(3), 918 f50Hz(4), 919 f15Hz(5), 920 f16Hz(6), 921 f22Hz(7), 922 f23Hz(8), 923 f45Hz(9) 924 } 925 MAX-ACCESS read-only 926 STATUS current 927 DESCRIPTION 928 " This object must only be provided via the configuration 929 file during the provisioning process. The power ring 930 frequency is the frequency at which the sinusoidal voltage 931 must travel down the twisted pair to make terminal 932 equipment ring. Different countries define different 933 electrical characteristics to make terminal equipment 934 ring. 935 The f20Hz setting corresponds to a power ring frequency 936 of 20 Hertz. The f25Hz setting corresponds to a power ring 937 frequency of 25 Hertz. The f33Point33Hz setting 938 corresponds to a power ring frequency of 33.33 Hertz. The 939 f50Hz setting corresponds to a power ring frequency of 50 940 Hertz. The f15Hz setting corresponds to a power ring 941 frequency of 15 Hertz. The f16Hz setting corresponds to a 942 power ring frequency of 16 Hertz. The f22Hz setting 943 corresponds to a power ring frequency of 22 Hertz. The 944 f23Hz setting corresponds to a power ring frequency of 23 945 Hertz. The f45Hz setting corresponds to a power ring 946 frequency of 45 Hertz." 947 REFERENCE 948 "ETSI-EN-300-001 contains a list of frequency ranges 949 that are defined for each country." 950 ::= { pktcSigDevObjects 19 } 952 pktcSigPulseSignalTable OBJECT-TYPE 953 SYNTAX SEQUENCE OF PktcSigPulseSignalEntry 954 MAX-ACCESS not-accessible 955 STATUS current 956 DESCRIPTION 957 " The Pulse signal table defines the pulse signal operation. 958 There are nine types of international pulse signals, 959 with each signal having a set of provisionable parameters. 960 The values of the MIB objects in this table take effect 961 only if these parameters are not defined via signaling, in 962 which case the latter determines the values of the 963 parameters. This MIB table is required for the E line 964 package. 965 Objects in this table do not persist across MTA reboots." 966 REFERENCE 967 "ETSI-TS-101-909-4 Specification" 968 ::= { pktcSigDevObjects 20 } 970 pktcSigPulseSignalEntry OBJECT-TYPE 971 SYNTAX PktcSigPulseSignalEntry 972 MAX-ACCESS not-accessible 973 STATUS current 974 DESCRIPTION 975 " This object defines the set of parameters associated with 976 each particular value of pktcSigPulseSignalType. Each 977 entry in the pktcSigPulseSignalTable is indexed by the 978 pktcSigPulseSignalType object. 979 The conceptual rows MUST NOT persist across MTA reboots." 980 INDEX { pktcSigPulseSignalType } 981 ::= { pktcSigPulseSignalTable 1 } 983 PktcSigPulseSignalEntry ::= SEQUENCE { 984 pktcSigPulseSignalType INTEGER, 985 pktcSigPulseSignalFrequency INTEGER, 986 pktcSigPulseSignalDbLevel TenthdBm, 987 pktcSigPulseSignalDuration Unsigned32, 988 pktcSigPulseSignalPulseInterval Unsigned32, 989 pktcSigPulseSignalRepeatCount Unsigned32 990 } 992 pktcSigPulseSignalType OBJECT-TYPE 993 SYNTAX INTEGER 994 { 995 initialRing(1), 996 pulseLoopClose(2), 997 pulseLoopOpen(3), 998 enableMeterPulse(4), 999 meterPulseBurst(5), 1000 pulseNoBattery(6), 1001 pulseNormalPolarity(7), 1002 pulseReducedBattery(8), 1003 pulseReversePolarity(9) 1004 } 1005 MAX-ACCESS not-accessible 1006 STATUS current 1007 DESCRIPTION 1008 "There are nine types of international pulse signals. These 1009 signals are defined as follows: 1010 initial ring 1011 pulse loop close 1012 pulse loop open 1013 enable meter pulse 1014 meter pulse burst 1015 pulse no battery 1016 pulse normal polarity 1017 pulse reduced battery 1018 pulse reverse polarity" 1019 REFERENCE 1020 "ETSI-EN-300-324-1 Specification" 1022 ::= { pktcSigPulseSignalEntry 1 } 1024 pktcSigPulseSignalFrequency OBJECT-TYPE 1025 SYNTAX INTEGER { 1026 twentyfive (1), 1027 twelvethousand(2), 1028 sixteenthousand(3) 1029 } 1030 MAX-ACCESS read-write 1031 STATUS current 1032 DESCRIPTION 1033 " This object is only applicable to the initialRing, 1034 enableMeterPulse, and meterPulseBurst signal type. This 1035 object identifies the frequency of the generated signal. 1036 The following table defines the default values for this 1037 object depending on signal type: 1038 pktcSigPulseSignalType Default 1039 initialRing 25 1040 enableMeterPulse 16000 1041 meterPulseBurst 16000 1042 The value of twentyfive MUST only be used for the 1043 initialRing signal type. The values of twelvethousand and 1044 sixteenthousand MUST only be used for enableMeterPulse and 1045 meterPulseBurst signal types. An attempt to set this 1046 object while the value of pktcSigPulseSignalType is not 1047 initialRing, enableMeterPulse, or meterPulseBurst will 1048 result in an 'inconsistentValue' error." 1049 REFERENCE 1050 "ETSI-EN-300-001 Specification" 1051 ::= { pktcSigPulseSignalEntry 2} 1053 pktcSigPulseSignalDbLevel OBJECT-TYPE 1054 SYNTAX TenthdBm (-350..0) 1055 UNITS "1/10 of a dBm" 1056 MAX-ACCESS read-write 1057 STATUS current 1058 DESCRIPTION 1059 " This object is only applicable to the enableMeterPulse and 1060 meterPulseBurst signal types. This is the decibel level 1061 for each frequency at which tones could be generated at 1062 the a and b terminals (TE connection point). An attempt to 1063 set this object while the value of pktcSigPulseSignalType 1064 is not enableMeterPulse, or meterPulseBurst will result in 1065 an 'inconsistentValue' error." 1066 REFERENCE 1067 "ETSI-EN-300-001 Specification" 1068 DEFVAL { -135 } 1069 ::={pktcSigPulseSignalEntry 3 } 1071 pktcSigPulseSignalDuration OBJECT-TYPE 1072 SYNTAX Unsigned32 (0..5000) 1073 UNITS "Milliseconds" 1074 MAX-ACCESS read-write 1075 STATUS current 1076 DESCRIPTION 1077 " This object specifies the pulse duration for each 1078 signal type. In addition, the MTA must accept the values 1079 in the incremental steps specific for each signal type. 1080 The following table defines the default values and the 1081 incremental steps for this object depending on the signal 1082 type. 1083 pktcSigPulseSignaltype Default (ms) Increment (ms) 1084 initialRing 200 50 1085 pulseLoopClose 200 10 1086 pulseLoopOpen 200 10 1087 enableMeterPulse 150 10 1088 meterPulseBurst 150 10 1089 pulseNoBattery 200 10 1090 pulseNormalPolarity 200 10 1091 pulseReducedBattery 200 10 1092 pulseReversePolarity 200 10 1093 An attempt to set this object to a value that does not 1094 fall on one of the increment boundaries, or on the wrong 1095 increment boundary for the specific signal type will 1096 result in an 'inconsistentValue' error." 1097 REFERENCE 1098 "ETSI-EN-300-324-1 Specification" 1099 ::= {pktcSigPulseSignalEntry 4 } 1101 pktcSigPulseSignalPulseInterval OBJECT-TYPE 1102 SYNTAX Unsigned32 (0..5000) 1103 UNITS "Milliseconds" 1104 MAX-ACCESS read-write 1105 STATUS current 1106 DESCRIPTION 1107 " This object specifies the repeat interval, or the period 1108 for each signal type. In addition, the MTA must accept 1109 the values in the incremental steps specific for each 1110 signal type. The following table defines the default 1111 values and the incremental steps for this object depending 1112 on the signal type. 1113 pktcSigPulseSignaltype Default (ms) Increment (ms) 1114 initialRing 200 50 1115 pulseLoopClose 1000 10 1116 pulseLoopOpen 1000 10 1117 enableMeterPulse 1000 10 1118 meterPulseBurst 1000 10 1119 pulseNoBattery 1000 10 1120 pulseNormalPolarity 1000 10 1121 pulseReducedBattery 1000 10 1122 pulseReversePolarity 1000 10 1123 An attempt to set this object to a value that does not 1124 fall on one of the increment boundaries, or on the wrong 1125 increment boundary for the specific signal type will 1126 result in an 'inconsistentValue' error." 1127 REFERENCE 1128 "ETSI-EN-300-324-1 Specification" 1129 ::= { pktcSigPulseSignalEntry 5} 1131 pktcSigPulseSignalRepeatCount OBJECT-TYPE 1132 SYNTAX Unsigned32 (1..50) 1133 MAX-ACCESS read-write 1134 STATUS current 1135 DESCRIPTION 1136 " This object specifies how many times to repeat a pulse. 1137 This object is not used by the enableMeterPulse signal 1138 type and as such must have a value of zero. The following 1139 table defines the default values and the valid ranges for 1140 this object depending on the signal type. 1142 pktcSigPulseSignaltype Default Range 1144 initialRing 1 1-5 1145 pulseLoopClose 1 1-50 1146 pulseLoopOpen 1 1-50 1147 enableMeterPulse (any value)(not used) 1148 meterPulseBurst 1 1-50 1149 pulseNoBattery 1 1-50 1150 pulseNormalPolarity 1 1-50 1151 pulseReducedBattery 1 1-50 1152 pulseReversePolarity 1 1-50 1154 An attempt to set this object to a value that does not 1155 fall within the range for the specific 1156 signal type will result in an 'inconsistentValue' error." 1157 ::={ pktcSigPulseSignalEntry 6 } 1159 pktcSigDevCidMode OBJECT-TYPE 1160 SYNTAX INTEGER { 1161 duringRingingETS(1), 1162 dtAsETS(2), 1163 rpAsETS(3), 1164 lrAsETS(4), 1165 lrETS(5) 1166 } 1167 MAX-ACCESS read-write 1168 STATUS current 1169 DESCRIPTION 1170 " For on-hook Caller ID, pktcSigDevCidMode selects the 1171 method for representing and signaling Caller 1172 Identification. For the duringRingingETS method, the 1173 Frequency Shift Keying (FSK) or the Dual Tone Multi 1174 Frequency (DTMF) containing the Caller Identification 1175 information is sent between the first and second ring 1176 pattern. 1178 For the dtAsETS,rpAsETS, lrAsETS and lrETS 1179 methods, the FSK or DTMF containing the Caller ID 1180 information is sent before the first ring pattern. 1182 For the dtAsETS method, the FSK or DTMF is sent after the 1183 Dual Tone Alert Signal. For the rpAsETS method, the FSK or 1184 DTMF is sent after a Ring Pulse. 1186 For the lrAsETS method, the Line Reversal occurs first, 1187 then the Dual Tone Alert Signal, and finally the FSK or 1188 DTMF is sent. 1190 For the lrETS method, the Line Reversal occurs first 1191 then the FSK or DTMF is sent. 1193 The value of this MIB Object MUST NOT persist across MTA 1194 reboots." 1196 DEFVAL { rpAsETS} 1197 ::= {pktcSigDevObjects 21 } 1199 pktcSigDevCidAfterRing OBJECT-TYPE 1200 SYNTAX Unsigned32 (0|50..2000) 1201 UNITS "Milliseconds" 1202 MAX-ACCESS read-write 1203 STATUS current 1204 DESCRIPTION 1205 " This object specifies the delay between the end of first 1206 ringing pattern and the start of the transmission of the 1207 FSK or DTMF containing the Caller ID information. It is 1208 only used when pktcSigDevCidMode is set to a value of 1209 'duringRingingETS'. 1211 The following table defines the default values 1212 for this MIB Object, depending on the signal type 1213 (pktcSigDevCidMode) and MUST be followed: 1215 Value of pktcSigDevCidMode Default value 1217 duringringingETS 550 ms 1218 dtAsETS any value (not used) 1219 rpAsETS any value (not used) 1220 lrAsETS any value (not used) 1221 lrETS any value (not used) 1223 An attempt to set this object while the value of 1224 pktcSigDevCidMode is not duringringingETS will result in 1225 an 'inconsistentValue' error. 1227 The value of this MIB Object MUST NOT persist across MTA 1228 reboots." 1229 REFERENCE 1230 "ETSI-EN-300-659-1 Specification" 1231 DEFVAL { 550 } 1232 ::= {pktcSigDevObjects 22 } 1234 pktcSigDevCidAfterDTAS OBJECT-TYPE 1235 SYNTAX Unsigned32 (0|45..500) 1236 UNITS "Milliseconds" 1237 MAX-ACCESS read-write 1238 STATUS current 1239 DESCRIPTION 1240 " This object specifies the delay between the end of the 1241 Dual Tone Alert Signal (DT-AS) and the start of the 1242 transmission of the FSK or DTMF containing the Caller ID 1243 information. This object is only used when 1244 pktcSigDevCidMode is set to a value of 'dtAsETS' or 1245 'lrAsETS'. 1247 The following table defines the default values 1248 for this MIB Object, depending on the signal type 1249 (pktcSigDevCidMode) and MUST be followed: 1251 Value of pktcSigDevCidMode Default value 1253 duringringingETS any value (not used) 1254 dtAsETS 50 ms 1255 rpAsETS any value (not used) 1256 lrAsETS 50 ms 1257 lrETS any value (not used) 1259 An attempt to set this object while the value of 1260 pktcSigDevCidMode is not 'dtAsETS' or 'lrAsETS' will 1261 result in an 'inconsistentValue' error. 1263 The value of this MIB Object MUST NOT persist across MTA 1264 reboots." 1266 REFERENCE 1267 "ETSI-EN-300-659-1 Specification" 1268 DEFVAL { 50 } 1269 ::= {pktcSigDevObjects 23 } 1271 pktcSigDevCidAfterRPAS OBJECT-TYPE 1272 SYNTAX Unsigned32 (0|500..800) 1273 UNITS "Milliseconds" 1274 MAX-ACCESS read-write 1275 STATUS current 1276 DESCRIPTION 1277 " This object specifies the delay between the end of the 1278 Ring Pulse Alert Signal (RP-AS) and the start of the 1279 transmission of the FSK or DTMF containing the Caller ID 1280 information. This MIB object is only used when 1281 pktcSigDevCidMode is set to a value of 'rpAsETS'. 1282 The following table defines the default values 1283 for this MIB Object, depending on the signal type 1284 (pktcSigDevCidMode) and MUST be followed: 1286 Value of pktcSigDevCidMode Default value 1288 duringringingETS any value (not used) 1289 dtAsETS any value (not used) 1290 rpAsETS 650 ms 1291 lrAsETS any value (not used) 1292 lrETS any value (not used) 1294 An attempt to set this object while the value of 1295 pktcSigDevCidMode is not 'rpAsETS' will result in an 1296 'inconsistentValue' error. 1298 The value of this MIB Object MUST NOT persist across MTA 1299 reboots." 1300 REFERENCE 1301 "ETSI-EN-300-659-1 Specification" 1302 DEFVAL { 650 } 1303 ::= {pktcSigDevObjects 24 } 1305 pktcSigDevRingAfterCID OBJECT-TYPE 1306 SYNTAX Unsigned32 (0|50..500) 1307 UNITS "Milliseconds" 1308 MAX-ACCESS read-write 1309 STATUS current 1310 DESCRIPTION 1311 " This object specifies the delay between the end of the 1312 complete transmission of the FSK or DTMF containing the 1313 Caller ID information and the start of the first ring 1314 pattern. It is only used when pktcSigDevCidMode is 1315 set to a value of 'dtAsETS', 'rpAsETS', 'lrAsETS' or 1316 'lrETS'. 1317 The following table defines the default values 1318 for this MIB Object, depending on the signal type 1319 (pktcSigDevCidMode) and MUST be followed: 1321 Value of pktcSigDevCidMode Default value 1322 duringringingETS any value (not used) 1323 dtAsETS 250 ms 1324 rpAsETS 250 ms 1325 lrAsETS 250 ms 1326 lrETS 250 ms 1328 An attempt to set this object while the value of 1329 pktcSigDevCidMode is not 'dtAsETS', 'rpAsETS', 1330 'lrAsETS' or 'lrETS' will result in an 'inconsistent 1331 value' error. 1333 The value of this MIB Object MUST NOT persist across MTA 1334 reboots." 1335 REFERENCE 1336 "ETSI-EN-300-659-1 Specification" 1337 DEFVAL { 250 } 1338 ::= {pktcSigDevObjects 25 } 1340 pktcSigDevCidDTASAfterLR OBJECT-TYPE 1341 SYNTAX Unsigned32 (50..655) 1342 UNITS "Milliseconds" 1343 MAX-ACCESS read-write 1344 STATUS current 1345 DESCRIPTION 1346 " This object specifies the delay between the end of the 1347 Line Reversal and the start of the Dual Tone Alert Signal 1348 (DT-AS). This object is only used when pktcSigDevCidMode 1349 is set to a value of 'lrAsETS'. 1351 The following table defines the default values 1352 for this MIB Object, depending on the signal type 1353 (pktcSigDevCidMode) and MUST be followed: 1355 Value of pktcSigDevCidMode Default value 1357 duringringingETS any value (not used) 1358 dtAsETS any value (not used) 1359 rpAsETS any value (not used) 1360 lrAsETS 250 ms 1361 lrETS any value (not used) 1363 An attempt to set this object while the value of 1364 pktcSigDevCidMode is not lrAsETS will result in an 1365 'inconsistentValue' error. 1367 The value of this MIB Object MUST NOT persist across MTA 1368 reboots." 1369 REFERENCE 1370 "ETSI-EN-300-659-1 Specification" 1371 DEFVAL { 250 } 1373 ::= {pktcSigDevObjects 26 } 1375 pktcSigDevVmwiMode OBJECT-TYPE 1376 SYNTAX INTEGER { 1377 dtAsETS(1), 1378 rpAsETS(2), 1379 lrAsETS(3), 1380 osi(4), 1381 lrETS(5) 1382 } 1383 MAX-ACCESS read-write 1384 STATUS current 1385 DESCRIPTION 1386 " For visual message waiting indicator (VMWI), 1387 pktcSigDevVmwiMode selects the alerting signal method. For 1388 the dtAsETS, rpAsETS, lrAsETS, osi and lrETS methods, 1389 the FSK containing the VMWI information is sent after an 1390 alerting signal. 1392 For the dtAsETS method, the FSK or DTMF 1393 is sent after the Dual Tone Alert Signal. For the rpAsETS 1394 method, the FSK or DTMF is sent after a Ring Pulse. 1396 For the lrAsETS method, the Line Reversal occurs first, 1397 then the Dual Tone Alert Signal, and finally the FSK or 1398 DTMF is sent. 1400 For the OSI method, the FSK or DTMF is sent after the Open 1401 Switching Interval. 1403 For the lrETS method, the Line Reversal occurs first 1404 then the FSK or DTMF is sent. 1406 The value of this MIB Object MUST NOT persist across MTA 1407 reboots." 1408 DEFVAL { rpAsETS } 1409 ::= {pktcSigDevObjects 27 } 1411 pktcSigDevVmwiAfterDTAS OBJECT-TYPE 1412 SYNTAX Unsigned32 (0|45..500) 1413 UNITS "Milliseconds" 1414 MAX-ACCESS read-write 1415 STATUS current 1416 DESCRIPTION 1417 " This object specifies the delay between the end of the 1418 Dual Tone Alert Signal (DT-AS) and the start of the 1419 transmission of the FSK or DTMF containing the VMWI 1420 information. 1421 This object is only used when pktcSigDevVmwiMode is 1422 set to a value of 'dtAsETS' or 'lrAsETS'. 1424 The following table defines the default values 1425 for this MIB Object, depending on the signal type 1426 (pktcSigDevVmwiMode) and MUST be followed: 1428 Value of pktcSigDevVmwiMode Default value 1430 dtAsETS 50 ms 1431 rpAsETS any value (not used) 1432 lrAsETS 50 ms 1433 lrETS any value (not used) 1435 An attempt to set this object while the value of 1436 pktcSigDevVmwiMode is not 'dtAsETS' or 'lrAsETS' will 1437 result in an 'inconsistentValue' error. 1439 The value of this MIB Object MUST NOT persist across MTA 1440 reboots." 1442 REFERENCE 1443 "ETSI-EN-300-659-1 Specification" 1444 DEFVAL { 50 } 1445 ::= {pktcSigDevObjects 28 } 1447 pktcSigDevVmwiAfterRPAS OBJECT-TYPE 1448 SYNTAX Unsigned32 (0|500..800) 1449 UNITS "Milliseconds" 1450 MAX-ACCESS read-write 1451 STATUS current 1452 DESCRIPTION 1453 " This object specifies the delay between the end of the 1454 Ring Pulse Alert Signal (RP-AS) and the start of the 1455 transmission of the FSK or DTMF containing the VMWI 1456 information. 1457 This object is only used when pktcSigDevVmwiMode is 1458 set to a value of 'rpAsETS'. 1459 The following table defines the default values 1460 for this MIB Object, depending on the signal type 1461 (pktcSigDevVmwiMode) and MUST be followed: 1463 Value of pktcSigDevVmwiMode Default value 1465 dtAsETS any value (not used) 1466 rpAsETS 650 ms 1467 lrAsETS any value (not used) 1468 lrETS any value (not used) 1470 An attempt to set this object while the value of 1471 pktcSigDevVmwiMode is not 'rpAsETS' will result in an 1472 'inconsistentValue' error. 1474 The value of this MIB Object MUST NOT persist across MTA 1475 reboots." 1477 REFERENCE 1478 "ETSI-EN-300-659-1 Specification" 1479 DEFVAL { 650 } 1480 ::= {pktcSigDevObjects 29 } 1482 pktcSigDevVmwiDTASAfterLR OBJECT-TYPE 1483 SYNTAX Unsigned32 (0|50..655) 1484 UNITS "Milliseconds" 1485 MAX-ACCESS read-write 1486 STATUS current 1487 DESCRIPTION 1488 " This object specifies the delay between the end of the 1489 Line Reversal and the start of the Dual Tone Alert Signal 1490 (DT-AS) for VMWI information. This object is only used 1491 when pktcSigDevVmwiMode is set to a value of 'lrAsETS'. 1493 The following table defines the default values 1494 for this MIB Object, depending on the signal type 1495 (pktcSigDevVmwiMode) and MUST be followed: 1497 Value of pktcSigDevVmwiMode Default value 1499 dtAsETS any value (not used) 1500 rpAsETS any value (not used) 1501 lrAsETS 250 ms 1502 lrETS any value (not used) 1504 An attempt to set this object while the value of 1505 pktcSigDevVmwiMode is not 'lrAsETS' will result in an 1506 'inconsistentValue' error. 1508 The value of this MIB Object MUST NOT persist across MTA 1509 reboots." 1511 REFERENCE 1512 "ETSI-EN-300-659-1 Specification" 1513 DEFVAL { 250 } 1514 ::= {pktcSigDevObjects 30 } 1515 pktcSigDevRingCadenceTable OBJECT-TYPE 1516 SYNTAX SEQUENCE OF PktcSigDevRingCadenceEntry 1517 MAX-ACCESS not-accessible 1518 STATUS current 1519 DESCRIPTION 1520 "Cadence rings are defined by the telco governing 1521 body for each country. The MTA must be able to support 1522 various ranges of cadence patterns and cadence periods. 1523 The MTA will be able to support country specific 1524 provisioning of the cadence and idle period. Each 1525 cadence pattern will be assigned a unique value ranging 1526 from 0-127 (inclusive) corresponding to the value of x, 1527 where x is the value sent in the cadence ringing (cr) 1528 signal cr(x), requested per the appropriate NCS 1529 message, and defined in the E package. The MTA will derive 1530 the cadence periods from the ring cadence table entry as 1531 provisioned by the customer. The MTA is allowed to provide 1532 appropriate default values for each of the ring cadences. 1533 This table only needs to be supported when the MTA 1534 implements the E package." 1535 REFERENCE 1536 "ETSI-TS-101-909-4 Specification" 1537 ::= { pktcSigDevObjects 31 } 1539 pktcSigDevRingCadenceEntry OBJECT-TYPE 1540 SYNTAX PktcSigDevRingCadenceEntry 1541 MAX-ACCESS not-accessible 1542 STATUS current 1543 DESCRIPTION 1544 " Each entry in this row corresponds to a ring cadence 1545 that is being supported by the device. The conceptual 1546 rows MUST NOT persist across MTA reboots." 1547 INDEX { pktcSigDevRingCadenceIndex } 1548 ::= { pktcSigDevRingCadenceTable 1 } 1550 PktcSigDevRingCadenceEntry ::= SEQUENCE { 1551 pktcSigDevRingCadenceIndex Unsigned32, 1552 pktcSigDevRingCadence PktcRingCadence 1553 } 1555 pktcSigDevRingCadenceIndex OBJECT-TYPE 1556 SYNTAX Unsigned32 (0..127) 1557 MAX-ACCESS not-accessible 1558 STATUS current 1559 DESCRIPTION 1560 " Unique value ranging from 0 to 127 that corresponds to the 1561 value sent by the LE based on country specific cadences, 1562 one row per cadence cycle. In any given system 1563 implementation for a particular country, it is anticipated 1564 that a small number of ring cadences will be in use. Thus, 1565 this table most likely will not be populated to its full 1566 size." 1567 ::= { pktcSigDevRingCadenceEntry 1 } 1569 pktcSigDevRingCadence OBJECT-TYPE 1570 SYNTAX PktcRingCadence 1571 MAX-ACCESS read-write 1572 STATUS current 1573 DESCRIPTION 1574 "This is the Ring Cadence." 1575 ::= { pktcSigDevRingCadenceEntry 2 } 1577 pktcSigDevToneTable OBJECT-TYPE 1578 SYNTAX SEQUENCE OF PktcSigDevToneEntry 1579 MAX-ACCESS not-accessible 1580 STATUS current 1581 DESCRIPTION 1582 " The Tone Table defines the composition of tones and 1583 various tone operations. 1585 The definition of the tones callWaiting1 through 1586 callWaiting4 in this table MUST only contain the 1587 audible tone itself; the delay between tones or the value 1588 of the tone repeat count are not applicable for the call 1589 waiting tones. 1591 The delay between tones or the repeat count is controlled 1592 by the objects pktcNcsEndPntConfigCallWaitingDelay, and 1593 pktcNcsEndPntConfigCallWaitingMaxRep. If the 1594 pktcSigDevToneType is set to either of the values 1595 callWaiting1, callWaiting2, callWaiting3 or callWaiting4, 1596 then the value of the pktcSigDevToneWholeToneRepeatCount 1597 object indicates that the particular frequency group is 1598 applicable, as a repeatable part of the tone, based on the 1599 value of the MIB Object 1600 pktcSigDevToneWholeToneRepeatCount. 1602 The MTA MUST make sure that, after the provisioning 1603 cycle, the table is fully populated (i.e., for each 1604 possible index, an entry MUST be defined) using 1605 reasonable defaults for each row that was not defined 1606 by the provisioning information delivered via MTA 1607 Configuration. 1609 The frequency composition of each tone is defined by the 1610 pktcSigDevMultiFreqToneTable. For each ToneType defined 1611 in pktcSigDevToneTable, the MTA MUST populate at least 1612 one entry in the pktcSigDevMultiFreqToneTable. 1614 For each particular value of pktcSigDevToneType, the 1615 pktcSigDevToneTable table can define non-repeating and 1616 repeating groups of the frequencies defined by the 1617 pktcSigDevMultiFreqToneTable, such that each group is 1618 represented by the set of the consecutive rows 1619 (frequency group) in the pktcSigDevMultiFreqToneTable. 1621 Objects in this table do not persist across MTA reboots. 1622 For tones with multiple frequencies refer to the MIB table 1623 pktcSigDevMultiFreqToneTable." 1624 REFERENCE 1625 "PacketCable NCS Specification, ETSI-TS-101-909-4 1626 Specification." 1627 ::= { pktcSigDevObjects 32 } 1629 pktcSigDevToneEntry OBJECT-TYPE 1630 SYNTAX PktcSigDevToneEntry 1631 MAX-ACCESS not-accessible 1632 STATUS current 1633 DESCRIPTION 1634 " The different tone types that can be provisioned based on 1635 country specific needs. 1636 Each entry contains the tone generation parameters for 1637 a specific frequency group of the specific Tone Type. 1638 The different parameters can be provisioned via MTA 1639 configuration based on country specific needs. 1640 An MTA MUST populate all entries of this table for each 1641 tone type." 1642 INDEX { pktcSigDevToneType, pktcSigDevToneFreqGroup } 1643 ::= { pktcSigDevToneTable 1 } 1645 PktcSigDevToneEntry ::= SEQUENCE { 1646 pktcSigDevToneType INTEGER, 1647 pktcSigDevToneFreqGroup Unsigned32, 1648 pktcSigDevToneFreqCounter Unsigned32, 1649 pktcSigDevToneWholeToneRepeatCount Unsigned32, 1650 pktcSigDevToneSteady TruthValue 1651 } 1653 pktcSigDevToneType OBJECT-TYPE 1654 SYNTAX INTEGER { 1655 busy(1), 1656 confirmation(2), 1657 dial(3), 1658 messageWaiting(4), 1659 offHookWarning(5), 1660 ringBack(6), 1661 reOrder(7), 1662 stutterdial(8), 1663 callWaiting1(9), 1664 callWaiting2(10), 1665 callWaiting3(11), 1666 callWaiting4(12), 1667 alertingSignal(13), 1668 specialDial(14), 1669 specialInfo(15), 1670 release(16), 1671 congestion(17), 1672 userDefined1(18), 1673 userDefined2(19), 1674 userDefined3(20), 1675 userDefined4(21) 1676 } 1677 MAX-ACCESS not-accessible 1678 STATUS current 1679 DESCRIPTION 1680 "Unique value that will correspond to the different 1681 tone types. These tones can be provisioned based on 1682 country specific needs. This object defines the type 1683 of tone being accessed. 1684 The alertingSignal, specialDial, specialInfo, release, 1685 congestion, userDefined1, userDefined2, userDefined3 1686 and userDefined4 tone types are used in 1687 the E line package." 1688 ::= { pktcSigDevToneEntry 1 } 1690 pktcSigDevToneFreqGroup OBJECT-TYPE 1691 SYNTAX Unsigned32(1..4) 1692 MAX-ACCESS not-accessible 1693 STATUS current 1694 DESCRIPTION 1695 "This MIB Object represents the Tone Sequence reference 1696 of a multi-sequence tone." 1697 ::={ pktcSigDevToneEntry 2} 1699 pktcSigDevToneFreqCounter OBJECT-TYPE 1700 SYNTAX Unsigned32(1..8) 1701 MAX-ACCESS read-only 1702 STATUS current 1703 DESCRIPTION 1704 "This MIB Object represents the number of consecutive 1705 multi-frequency tones for the particular tone type in 1706 the multi-frequency table (pktcSigDevMultiFreqToneTable). 1708 Such a sequence of the consecutive multi-frequency tones 1709 forms the tone group for the particular tone type in the 1710 pktcSigDevToneTable." 1711 ::={ pktcSigDevToneEntry 3} 1713 pktcSigDevToneWholeToneRepeatCount OBJECT-TYPE 1714 SYNTAX Unsigned32 (0..5000) 1715 MAX-ACCESS read-only 1716 STATUS current 1717 DESCRIPTION 1718 "This is the repeat count, which signifies how many times 1719 to repeat the entire on-off cadence sequence. Setting this 1720 object may result in a cadence duration longer or shorter 1721 than the overall signal duration specified by the time out 1722 (TO) object for a particular signal. If the repeat count 1723 results in a longer tone duration than the signal duration 1724 specified by the TO, the tone duration defined by the 1725 TO object for a particular signal always represents 1726 the overall signal duration for a tone. In this case, the 1727 tone duration repeat count will not be fully exercised and 1728 the desired tone duration will be truncated per the TO 1729 setting. If the repeat count results in a shorter tone 1730 duration than the signal duration specified by the TO, the 1731 tone duration defined by the repeat count takes precedence 1732 over the TO and will end the signal event. In this case, 1733 the TO represents a time not to be exceeded for the signal. 1734 It is recommended to ensure proper telephony signaling that 1735 The TO duration setting should always be longer than the 1736 desired repeat count time duration." 1737 ::={ pktcSigDevToneEntry 4 } 1739 pktcSigDevToneSteady OBJECT-TYPE 1740 SYNTAX TruthValue 1741 MAX-ACCESS read-only 1742 STATUS current 1743 DESCRIPTION 1744 "This MIB Object represents the steady tone status. A value 1745 of 'true(1)' indicates that the steady tone is applied; and 1746 a value of 'false(2)' indicates otherwise. 1747 Devices must play out the on-off cadence sequence for 1748 the number of times indicated by the MIB Object 1749 'pktcSigDevToneWholeToneRepeatCount' prior to applying the 1750 last tone steadily, indefinitely. If the MIB table 1751 'pktcSigDevToneTable' contains multiple rows with this 1752 Object set to a value of 'true(1)', the steady tone is 1753 applied to the last repeating frequency group of the tone. 1755 Setting this MIB Object may result in a tone duration 1756 longer or shorter than the overall signal duration 1757 specified by the time out (TO) MIB Object for a particular 1758 signal. If the repeat count results in a longer tone 1759 duration than the signal duration specified by the TO, the 1760 tone duration defined by the TO object for a particular 1761 signal always represents the overall signal duration for a 1762 tone. In this case, the tone duration repeat count will 1763 not be fully exercised and the desired tone duration will 1764 be truncated per the TO setting. If the repeat count 1765 results in a shorter tone duration than the signal duration 1766 specified by the TO, the tone duration defined by the 1767 repeat count takes precedence over the TO and will end the 1768 signal event. In this case, the TO represents a time not to 1769 be exceeded for the signal. 1770 It is recommended to ensure proper telephony signaling that 1771 The TO duration setting should always be longer than the 1772 desired repeat count time duration plus the desired maximum 1773 steady tone period." 1774 ::={ pktcSigDevToneEntry 5 } 1776 pktcSigDevMultiFreqToneTable OBJECT-TYPE 1777 SYNTAX SEQUENCE OF PktcSigDevMultiFreqToneEntry 1778 MAX-ACCESS not-accessible 1779 STATUS current 1781 DESCRIPTION 1782 " This MIB table defines the characteristics of tones 1783 with multiple frequencies. The constraints imposed 1784 on the tones by the MIB table pktcSigDevToneTable 1785 need to be considered for MIB objects in this table 1786 as well. 1787 The MTA MUST populate the corresponding row(s) 1788 of the pktcSigDevMultiFreqToneTable for each tone 1789 defined in the pktcSigDevToneTable. 1790 The contents of the table may be provisioned via 1791 MTA configuration." 1792 REFERENCE 1793 "PacketCable NCS Specification, ETSI-TS-101-909-4 1794 Specification." 1795 ::= { pktcSigDevObjects 33 } 1797 pktcSigDevMultiFreqToneEntry OBJECT-TYPE 1798 SYNTAX PktcSigDevMultiFreqToneEntry 1799 MAX-ACCESS not-accessible 1800 STATUS current 1801 DESCRIPTION 1802 " The different tone types with multiple frequencies 1803 that can be provisioned based on country specific 1804 needs." 1805 INDEX {pktcSigDevToneType, pktcSigDevToneNumber} 1806 ::= { pktcSigDevMultiFreqToneTable 1 } 1808 PktcSigDevMultiFreqToneEntry ::= SEQUENCE { 1809 pktcSigDevToneNumber Unsigned32, 1810 pktcSigDevToneFirstFreqValue Unsigned32, 1811 pktcSigDevToneSecondFreqValue Unsigned32, 1812 pktcSigDevToneThirdFreqValue Unsigned32, 1813 pktcSigDevToneFourthFreqValue Unsigned32, 1814 pktcSigDevToneFreqMode INTEGER, 1815 pktcSigDevToneFreqAmpModePrtg Unsigned32, 1816 pktcSigDevToneDbLevel TenthdBm, 1817 pktcSigDevToneFreqOnDuration Unsigned32, 1818 pktcSigDevToneFreqOffDuration Unsigned32, 1819 pktcSigDevToneFreqRepeatCount Unsigned32 1820 } 1822 pktcSigDevToneNumber OBJECT-TYPE 1823 SYNTAX Unsigned32(1..8) 1824 MAX-ACCESS not-accessible 1825 STATUS current 1826 DESCRIPTION 1827 "This MIB Object represents the frequency reference 1828 of a multi-frequency tone." 1829 ::={ pktcSigDevMultiFreqToneEntry 1} 1831 pktcSigDevToneFirstFreqValue OBJECT-TYPE 1832 SYNTAX Unsigned32(0..4000) 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "This MIB Object represents the value of the first 1837 frequency of a tone type. A value of Zero implies 1838 absence of the referenced frequency." 1839 ::={ pktcSigDevMultiFreqToneEntry 2} 1841 pktcSigDevToneSecondFreqValue OBJECT-TYPE 1842 SYNTAX Unsigned32(0..4000) 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "This MIB Object represents the value of the second 1847 frequency of a tone type. A value of Zero implies 1848 absence of the referenced frequency." 1849 ::={ pktcSigDevMultiFreqToneEntry 3} 1851 pktcSigDevToneThirdFreqValue OBJECT-TYPE 1852 SYNTAX Unsigned32(0..4000) 1853 MAX-ACCESS read-only 1854 STATUS current 1855 DESCRIPTION 1856 "This MIB Object represents the value of the third 1857 frequency of a tone type. A value of Zero implies 1858 absence of the referenced frequency." 1859 ::={ pktcSigDevMultiFreqToneEntry 4} 1861 pktcSigDevToneFourthFreqValue OBJECT-TYPE 1862 SYNTAX Unsigned32(0..4000) 1863 MAX-ACCESS read-only 1864 STATUS current 1865 DESCRIPTION 1866 "This MIB Object represents the value of the fourth 1867 frequency of a tone type. A value of Zero implies 1868 absence of the referenced frequency." 1869 ::={ pktcSigDevMultiFreqToneEntry 5} 1871 pktcSigDevToneFreqMode OBJECT-TYPE 1872 SYNTAX INTEGER { 1873 firstModulatedBySecond(1), 1874 summation(2) 1875 } 1876 MAX-ACCESS read-only 1877 STATUS current 1878 DESCRIPTION 1879 "This MIB Object provides directive on the 1880 modulation or summation of the frequencies 1881 involved in the tone. 1883 It is to be noted that while summation can 1884 be done without any constraint on the number 1885 of frequencies, the modulation (amplitude) 1886 holds good only when there are two frequencies 1887 (first and second). 1889 Thus: 1890 - If the mode is set to a value of 1891 'firstModulatedBySecond(1)', the first frequency 1892 MUST be modulated by the second and the remaining 1893 frequencies (third and fourth) ignored. The 1894 percentage of amplitude modulation to be applied 1895 is defined by the MIB Object 1896 pktcSigDevToneFreqAmpModePrtg. 1897 - If the mode is set to a value of 1898 'summation(2)', all the frequencies MUST be 1899 summed, without any modulation 1901 " 1902 ::={ pktcSigDevMultiFreqToneEntry 6} 1904 pktcSigDevToneFreqAmpModePrtg OBJECT-TYPE 1905 SYNTAX Unsigned32(0..100) 1906 MAX-ACCESS read-only 1907 STATUS current 1908 DESCRIPTION 1909 "This MIB Object represents the percentage of amplitude 1910 modulation applied to the second frequency 1911 when the MIB Object pktcSigDevToneFreqMode is 1912 set to a value of 'firstModulatedBySecond (1)'. 1914 If the MIB Object pktcSigDevToneFreqMode is set to 1915 value of 'summation (2)' then this MIB Object MUST be 1916 ignored." 1917 ::={ pktcSigDevMultiFreqToneEntry 7} 1919 pktcSigDevToneDbLevel OBJECT-TYPE 1920 SYNTAX TenthdBm (-250..-110) 1921 UNITS "1/10 of a dBm" 1922 MAX-ACCESS read-only 1923 STATUS current 1924 DESCRIPTION 1925 "This MIB Object contains the decibel level for each 1926 analog signal (tone) that is locally generated 1927 (versus in band supervisory tones) and sourced to 1928 the a-b terminals (TE connection point). Each tone 1929 in itself may consist of multiple frequencies as 1930 defined by the MIB table pktcSigDevMultiFreqToneTable. 1932 This MIB Object reflects the desired level at 1933 the Telco (POTS) a-b (T/R) terminals including the 1934 affect of any MTA receiver gain (loss). This is required 1935 so that locally generated tones are consistent with 1936 remotely generated in band tones at the a-b terminals, 1937 consistent with user expectations. 1939 This MIB Object must be set for each tone. 1940 When tones are formed by combining multi-frequencies, 1941 the level of each frequency shall be set so as to result 1942 in the tone level specified in this object at the a-b 1943 (T/R) terminals. 1945 The wide range of levels for this Object is required 1946 to provide signal generator levels across the wide 1947 range of gains (loss) - but does not imply the entire 1948 range is to be achievable given the range of gains (loss) 1949 in the MTA." 1950 DEFVAL { -120 } 1951 ::={ pktcSigDevMultiFreqToneEntry 8} 1953 pktcSigDevToneFreqOnDuration OBJECT-TYPE 1954 SYNTAX Unsigned32(0..5000) 1955 UNITS "milliseconds" 1956 MAX-ACCESS read-only 1957 STATUS current 1958 DESCRIPTION 1959 "This MIB Object represents the duration for which the 1960 frequency reference corresponding to the tone type 1961 is turned on." 1962 ::={ pktcSigDevMultiFreqToneEntry 9} 1964 pktcSigDevToneFreqOffDuration OBJECT-TYPE 1965 SYNTAX Unsigned32(0..5000) 1966 UNITS "milliseconds" 1967 MAX-ACCESS read-only 1968 STATUS current 1969 DESCRIPTION 1970 "This MIB Object represents the duration for which the 1971 frequency reference corresponding to the tone type 1972 is turned off." 1973 ::={ pktcSigDevMultiFreqToneEntry 10} 1975 pktcSigDevToneFreqRepeatCount OBJECT-TYPE 1976 SYNTAX Unsigned32(0..5000) 1977 MAX-ACCESS read-only 1978 STATUS current 1979 DESCRIPTION 1980 "This MIB Object indicates the number of times 1981 to repeat the cadence cycle represented by the 1982 on/off durations (refer to the MIB Objects 1983 pktcSigDevToneFreqOnDuration and 1984 pktcSigDevToneFreqOffDuration). 1986 Setting this object may result in a tone duration 1987 longer or shorter than the overall signal duration 1988 specified by the time out (TO) object for the 1989 corresponding tone type. If the value of this MIB 1990 Object indicates a longer duration than the 1991 specified by the TO, the latter overrules the former 1992 and the desired tone duration will be truncated according 1993 to the TO. 1995 However, if the repeat count results in a shorter 1996 tone duration than the signal duration specified by 1997 the TO, the tone duration defined by the repeat count 1998 takes precedence over the TO and will end the signal 1999 event. In this case, the TO represents a time not to 2000 be exceeded for the signal. It is recommended to 2001 ensure proper telephony signaling that the TO 2002 duration setting should always be longer than the 2003 desired repeat count time duration. A value of zero 2004 means the tone sequence is to be played once but not 2005 repeated." 2006 ::={ pktcSigDevMultiFreqToneEntry 11} 2008 pktcSigDevCidDelayAfterLR OBJECT-TYPE 2009 SYNTAX Unsigned32 (300..800) 2010 UNITS "Milliseconds" 2011 MAX-ACCESS read-write 2012 STATUS current 2013 DESCRIPTION 2014 "This object specifies the delay between the end of the 2015 Line Reversal and the start of the FSK or DTMF signal. 2016 This MIB object is used only when pktcSigDevCidMode is 2017 set to a value of 'lrETS'. This timing has a range of 2018 300 to 800 ms. 2019 The following table defines the default values 2020 for this MIB Object, depending on the signal type 2021 (pktcSigDevCidMode) and MUST be followed: 2023 Value of pktcSigDevCidMode Default value 2025 duringringingETS any value (not used) 2026 dtAsETS any value (not used) 2027 rpAsETS any value (not used) 2028 lrAsETS any value (not used) 2029 lrETS 400 2031 An attempt to set this object while the value of 2032 pktcSigDevCidMode is not set to a value of 'lrETS' will 2033 result in an 'inconsistentValue' error. 2035 The value of this MIB Object MUST NOT persist across MTA 2036 reboots." 2037 DEFVAL { 400 } 2038 ::= {pktcSigDevObjects 34 } 2040 pktcSigDevCidDtmfStartCode OBJECT-TYPE 2041 SYNTAX DtmfCode 2042 MAX-ACCESS read-write 2043 STATUS current 2044 DESCRIPTION 2045 "This object identifies optional start codes used when 2046 the MIB object pktcSigDevCidSigProtocol is set 2047 to a value of 'dtmf(2)'. 2048 Different countries define different caller id signaling 2049 codes to support caller identification. When Dual tone 2050 multi-frequency (DTMF) is used the Caller ID digits are 2051 preceded by a 'start code' digit, followed by the digit 2052 transmission sequence ... (where Sx represents 2053 the digits 0-9) and terminated by the 'end code' digit. 2054 For e.g. 2055 ... ... ... . 2056 The start code for calling number delivery may be DTMF 2057 'A' or 'D'. The start code for redirecting number may be 2058 DTMF 'D'. The DTMF code 'B' may be sent by the network 2059 as start code for the transfer of information values, 2060 through which special events can be indicated to the 2061 user. In some countries the '*' or '#' may be used 2062 instead of 'A', 'B', 'C' or 'D'. 2064 The value of this MIB Object MUST NOT persist across MTA 2065 reboots." 2067 REFERENCE 2068 "ETSI-EN-300-659-1 specification" 2069 DEFVAL {dtmfcodeA} 2070 ::= { pktcSigDevObjects 35 } 2072 pktcSigDevCidDtmfEndCode OBJECT-TYPE 2073 SYNTAX DtmfCode 2074 MAX-ACCESS read-write 2075 STATUS current 2076 DESCRIPTION 2077 "This object identifies optional end codes used when the 2078 pktcSigDevCidSigProtocol is set to a value of 2079 'dtmf(2)'. 2080 Different countries define different caller id signaling 2081 protocols to support caller identification. When Dual 2082 tone multi-frequency (DTMF) is used the Caller ID digits 2083 are preceded by a 'start code' digit, followed by the 2084 digit transmission sequence ... (where Sx 2085 represents the digits 0-9) and terminated by the 'end 2086 code' digit. 2087 For e.g. 2088 ... ... ... . 2090 The DTMF code 'C' may be sent by the network as 2091 end code for the transfer of information values, through 2092 which special events can be indicated to the user. In 2093 some countries the '*' or '#' may be used instead of 2094 'A', 'B', 'C' or 'D'. 2096 The value of this MIB Object MUST NOT persist across MTA 2097 reboots." 2099 REFERENCE 2100 "ETSI-EN-300-659-1 specification" 2101 DEFVAL {dtmfcodeC} 2102 ::= { pktcSigDevObjects 36 } 2104 pktcSigDevVmwiSigProtocol OBJECT-TYPE 2105 SYNTAX INTEGER { 2106 fsk(1), 2107 dtmf(2) 2108 } 2109 MAX-ACCESS read-write 2110 STATUS current 2111 DESCRIPTION 2112 "This object identifies the subscriber line protocol used 2113 for signaling the Information on Visual Message Waiting 2114 Indicator (VMWI). Different countries define different 2115 VMWI signaling protocols to support VMWI service. 2116 Frequency shift keying (FSK) is most commonly used. 2117 Dual tone multi-frequency (DTMF) is an alternative. 2119 The value of this MIB Object MUST NOT persist across MTA 2120 reboots." 2121 DEFVAL { fsk } 2122 ::= { pktcSigDevObjects 37 } 2124 pktcSigDevVmwiDelayAfterLR OBJECT-TYPE 2125 SYNTAX Unsigned32 (0|300..800) 2126 UNITS "Milliseconds" 2127 MAX-ACCESS read-write 2128 STATUS current 2129 DESCRIPTION 2130 "This object specifies the delay between the end of the 2131 Line Reversal and the start of the FSK or DTMF signal. 2132 This object is only used when pktcSigDevVmwiMode is 2133 set to a value of 'lrETS'. 2134 This timing has a range of 300 to 800 ms. 2136 The following table defines the default values 2137 for this MIB Object, depending on the signal type 2138 (pktcSigDevVmwiMode) and MUST be followed: 2140 Value of pktcSigDevVmwiMode Default value 2142 duringringingETS any value (not used) 2143 dtAsETS any value (not used) 2144 rpAsETS any value (not used) 2145 lrAsETS any value (not used) 2146 lrETS 400 2148 An attempt to set this object while the value of 2149 pktcSigDevVmwiMode is not 'lrETS' will result in an 2150 'inconsistentValue' error. 2152 The value of this MIB Object MUST NOT persist across MTA 2153 reboots." 2155 DEFVAL {400} 2156 ::= {pktcSigDevObjects 38 } 2158 pktcSigDevVmwiDtmfStartCode OBJECT-TYPE 2159 SYNTAX DtmfCode 2160 MAX-ACCESS read-write 2161 STATUS current 2162 DESCRIPTION 2163 "This object identifies optional start codes used when 2164 the pktcSigDevVmwiSigProtocol is set to a value of 2165 'dtmf(2)'. Different countries define different On Hook 2166 Data Transmission Protocol signaling codes to support 2167 VMWI. 2169 When Dual tone multi-frequency (DTMF) is used the VMWI 2170 digits are preceded by a 'start code' digit, followed 2171 by the digit transmission sequence ... (where 2172 Sx represents the digits 0-9) and terminated by the 'end 2173 code' digit. 2175 For e.g. 2176 ... ... ... . 2178 The start code for redirecting VMWI may be DTMF 'D' 2179 The DTMF code 'B' may be sent by the network as start 2180 code for the transfer of information values, through 2181 which special events can be indicated to the user. In 2182 some countries the '*' or '#' may be used instead of 2183 'A', 'B', 'C' or 'D'. 2185 The value of this MIB Object MUST NOT persist across MTA 2186 reboots." 2188 REFERENCE 2189 "ETSI-EN-300-659-1 specification" 2190 DEFVAL {dtmfcodeA} 2191 ::= { pktcSigDevObjects 39 } 2193 pktcSigDevVmwiDtmfEndCode OBJECT-TYPE 2194 SYNTAX DtmfCode 2195 MAX-ACCESS read-write 2196 STATUS current 2197 DESCRIPTION 2198 "This object identifies optional end code used when the 2199 pktcSigDevVmwiSigProtocol is set to a value of 2200 'dtmf(2)'. Different countries define different On Hook 2201 Data Transmission Protocol signaling codes to support 2202 VMWI. 2204 When Dual tone multi-frequency (DTMF) is used the VMWI 2205 digits are preceded by a 'start code' digit, followed 2206 by the digit transmission sequence ... (where 2207 Sx represents the digits 0-9) and terminated by the 'end 2208 code' digit. 2210 For e.g. 2211 ... ... ... . 2213 The DTMF code 'C' may be sent by the network as end code 2214 for the transfer of information values, through which 2215 special events can be indicated to the user. In some 2216 countries the '*' or '#' may be used instead of 'A', 2217 'B', 'C' or 'D'. 2219 The value of this MIB Object MUST NOT persist across MTA 2220 reboots." 2222 REFERENCE 2223 "ETSI-EN-300-659-1 specification" 2224 DEFVAL {dtmfcodeC} 2225 ::= { pktcSigDevObjects 40 } 2227 pktcSigDevrpAsDtsDuration OBJECT-TYPE 2228 SYNTAX Unsigned32 (0|200..500) 2229 UNITS "Milliseconds" 2230 MAX-ACCESS read-write 2231 STATUS current 2232 DESCRIPTION 2233 " This object specifies the duration of the rpASDTS ring 2234 pulse prior to the start of the transmission of the 2235 FSK or DTMF containing the Caller ID information. It is 2236 only used when pktcSigDevCidMode is set to a value of 2237 'rpAsETS'. 2239 The following table defines the default values 2240 for this MIB Object, depending on the signal type 2241 (pktcSigDevCidMode) and MUST be followed: 2243 Value of pktcSigDevCidMode Default value 2245 duringringingETS any value (not used) 2246 dtAsETS any value (not used) 2247 rpAsETS 250 2248 lrAsETS any value (not used) 2249 lrETS any value (not used) 2251 An attempt to set this object while the value of 2252 pktcSigDevCidMode is not 'rpAsETS' will result in 2253 an 'inconsistentValue' error. 2255 The value of this MIB Object MUST NOT persist across MTA 2256 reboots." 2258 REFERENCE 2259 "ETSI-EN-300-659-1 Specification and Belgacom 2260 BGC_D_48_9811_30_09_EDOC version 3.3" 2261 DEFVAL { 250 } 2262 ::= {pktcSigDevObjects 41 } 2264 -- 2265 -- The NCS Endpoint Config Table is used to define attributes that 2266 -- are specific to connection EndPoints. 2267 -- 2269 pktcNcsEndPntConfigTable OBJECT-TYPE 2270 SYNTAX SEQUENCE OF PktcNcsEndPntConfigEntry 2271 MAX-ACCESS not-accessible 2272 STATUS current 2273 DESCRIPTION 2274 " This table describes the information pertaining to each 2275 endpoint of the MTA. All entries in this table represent 2276 the provisioned endpoints provisioned with the information 2277 required by the MTA to maintain the NCS protocol 2278 communication with the CMS. Each endpoint can be assigned 2279 to its own CMS. If the specific endpoint does not have 2280 the corresponding CMS information in this table, the 2281 endpoint is considered as not provisioned with voice 2282 services. Objects in this table do not persist across 2283 MTA reboots." 2284 ::= { pktcNcsEndPntConfigObjects 1 } 2286 pktcNcsEndPntConfigEntry OBJECT-TYPE 2287 SYNTAX PktcNcsEndPntConfigEntry 2288 MAX-ACCESS not-accessible 2289 STATUS current 2290 DESCRIPTION 2291 "Each entry in the pktcNcsEndPntConfigTable represents 2292 required signaling parameters for the specific endpoint 2293 provisioned with voice services. The conceptual rows MUST 2294 NOT persist across MTA reboots." 2295 INDEX { ifIndex } 2296 ::= { pktcNcsEndPntConfigTable 1 } 2298 PktcNcsEndPntConfigEntry ::= SEQUENCE { 2299 pktcNcsEndPntConfigCallAgentId SnmpAdminString, 2300 pktcNcsEndPntConfigCallAgentUdpPort InetPortNumber, 2301 pktcNcsEndPntConfigPartialDialTO Unsigned32, 2302 pktcNcsEndPntConfigCriticalDialTO Unsigned32, 2303 pktcNcsEndPntConfigBusyToneTO Unsigned32, 2304 pktcNcsEndPntConfigDialToneTO Unsigned32, 2305 pktcNcsEndPntConfigMessageWaitingTO Unsigned32, 2306 pktcNcsEndPntConfigOffHookWarnToneTO Unsigned32, 2307 pktcNcsEndPntConfigRingingTO Unsigned32, 2308 pktcNcsEndPntConfigRingBackTO Unsigned32, 2309 pktcNcsEndPntConfigReorderToneTO Unsigned32, 2310 pktcNcsEndPntConfigStutterDialToneTO Unsigned32, 2311 pktcNcsEndPntConfigTSMax Unsigned32, 2312 pktcNcsEndPntConfigMax1 Unsigned32, 2313 pktcNcsEndPntConfigMax2 Unsigned32, 2314 pktcNcsEndPntConfigMax1QEnable TruthValue, 2315 pktcNcsEndPntConfigMax2QEnable TruthValue, 2316 pktcNcsEndPntConfigMWD Unsigned32, 2317 pktcNcsEndPntConfigTdinit Unsigned32, 2318 pktcNcsEndPntConfigTdmin Unsigned32, 2319 pktcNcsEndPntConfigTdmax Unsigned32, 2320 pktcNcsEndPntConfigRtoMax Unsigned32, 2321 pktcNcsEndPntConfigRtoInit Unsigned32, 2322 pktcNcsEndPntConfigLongDurationKeepAlive Unsigned32, 2323 pktcNcsEndPntConfigThist Unsigned32, 2324 pktcNcsEndPntConfigStatus RowStatus, 2325 pktcNcsEndPntConfigCallWaitingMaxRep Unsigned32, 2326 pktcNcsEndPntConfigCallWaitingDelay Unsigned32, 2327 pktcNcsEndPntStatusCallIpAddressType InetAddressType, 2328 pktcNcsEndPntStatusCallIpAddress InetAddress, 2329 pktcNcsEndPntStatusError INTEGER, 2330 pktcNcsEndPntConfigMinHookFlash Unsigned32, 2331 pktcNcsEndPntConfigMaxHookFlash Unsigned32, 2332 pktcNcsEndPntConfigPulseDialInterdigitTime Unsigned32, 2333 pktcNcsEndPntConfigPulseDialMinMakeTime Unsigned32, 2334 pktcNcsEndPntConfigPulseDialMaxMakeTime Unsigned32, 2335 pktcNcsEndPntConfigPulseDialMinBreakTime Unsigned32, 2336 pktcNcsEndPntConfigPulseDialMaxBreakTime Unsigned32 2337 } 2339 pktcNcsEndPntConfigCallAgentId OBJECT-TYPE 2340 SYNTAX SnmpAdminString(SIZE (3..255)) 2341 MAX-ACCESS read-create 2342 STATUS current 2343 DESCRIPTION 2344 " This object contains a string indicating the call agent 2345 name (e.g.: ca@example.com). The call agent name, after 2346 the character '@', MUST be a fully qualified domain name 2347 (FQDN) and MUST have a corresponding pktcMtaDevCmsFqdn 2348 entry in the pktcMtaDevCmsTable. The object 2349 pktcMtaDevCmsFqdn is defined in the PacketCable MIBMTA 2350 Specification. For each particular endpoint, the MTA MUST 2351 use the current value of this object to communicate with 2352 the corresponding CMS. The MTA MUST update this object 2353 with the value of the 'Notified Entity' parameter of the 2354 NCS message. Because of the high importance of this object 2355 to the ability of the MTA to maintain reliable NCS 2356 communication with the CMS, it is highly recommended not 2357 to change this object's value using SNMP during normal 2358 operation." 2359 ::= { pktcNcsEndPntConfigEntry 1 } 2361 pktcNcsEndPntConfigCallAgentUdpPort OBJECT-TYPE 2362 SYNTAX InetPortNumber (1025..65535) 2363 MAX-ACCESS read-create 2364 STATUS current 2365 DESCRIPTION 2366 " This object contains the current value of the User 2367 Datagram Protocol (UDP) receive port on which the 2368 call agent will receive NCS from the endpoint. 2369 For each particular endpoint, the MTA MUST use the current 2370 value of this object to communicate with the corresponding 2371 CMS. The MTA MUST update this object with the value of the 2372 'Notified Entity' parameter of the NCS message. If the 2373 Notified Entity parameter does not contain a CallAgent 2374 port, the MTA MUST update this object with the default 2375 value of 2727. Because of the high importance of this 2376 object to the ability of the MTA to maintain reliable NCS 2377 communication with the CMS, it is highly recommended not 2378 to change this object's value using SNMP during normal 2379 operation." 2380 REFERENCE 2381 "PacketCable NCS Specification" 2382 DEFVAL { 2727 } 2383 ::= { pktcNcsEndPntConfigEntry 2 } 2385 pktcNcsEndPntConfigPartialDialTO OBJECT-TYPE 2386 SYNTAX Unsigned32 2387 UNITS "seconds" 2388 MAX-ACCESS read-create 2389 STATUS current 2390 DESCRIPTION 2391 "This object contains the value of the partial dial 2392 time out. 2393 The Time out (TO) elements are intended to limit the time a 2394 tone or frequency is generated. When this MIB Object is set 2395 to a value of '0', the MTA MUST NOT generate the 2396 corresponding frequency or tone regardless of the 2397 definitions pertaining to frequency, tone duration or 2398 cadence." 2399 REFERENCE 2400 "PacketCable NCS Specification" 2401 DEFVAL { 16 } 2402 ::= { pktcNcsEndPntConfigEntry 3 } 2404 pktcNcsEndPntConfigCriticalDialTO OBJECT-TYPE 2405 SYNTAX Unsigned32 2406 UNITS "seconds" 2407 MAX-ACCESS read-create 2408 STATUS current 2409 DESCRIPTION 2410 "This object contains the value of the critical 2411 dial time out. 2412 The Time out (TO) elements are intended to limit the time a 2413 tone or frequency is generated. When this MIB Object is set 2414 to a value of '0', the MTA MUST NOT generate the 2415 corresponding frequency or tone regardless of the 2416 definitions pertaining to frequency, tone duration or 2417 cadence." 2418 REFERENCE 2419 "PacketCable NCS Specification" 2420 DEFVAL { 4 } 2421 ::= { pktcNcsEndPntConfigEntry 4 } 2423 pktcNcsEndPntConfigBusyToneTO OBJECT-TYPE 2424 SYNTAX Unsigned32 2425 UNITS "seconds" 2426 MAX-ACCESS read-create 2427 STATUS current 2428 DESCRIPTION 2429 " This object contains the default timeout value for busy 2430 tone. The MTA MUST NOT update this object with the 2431 value provided in the NCS message (if present). If 2432 the value of the object is modified by the SNMP Management 2433 Station, the MTA MUST use the new value as a default only 2434 for a new signal requested by the NCS message. 2435 The Time out (TO) elements are intended to limit the time 2436 a tone or frequency is generated. When this MIB Object is 2437 set to a value of '0', the MTA MUST NOT generate the 2438 corresponding frequency or tone regardless of the 2439 definitions pertaining to frequency, tone duration or 2440 cadence." 2442 REFERENCE 2443 "PacketCable NCS Specification" 2444 DEFVAL { 30 } 2445 ::= { pktcNcsEndPntConfigEntry 5 } 2447 pktcNcsEndPntConfigDialToneTO OBJECT-TYPE 2448 SYNTAX Unsigned32 2449 UNITS "seconds" 2450 MAX-ACCESS read-create 2451 STATUS current 2452 DESCRIPTION 2453 " This object contains the default timeout value for dial 2454 tone. The MTA MUST NOT update this object with the 2455 value provided in the NCS message (if present). If 2456 the value of the object is modified by the SNMP Management 2457 Station, the MTA MUST use the new value as a default only 2458 for a new signal requested by the NCS message. 2459 The Time out (TO) elements are intended to limit the time 2460 a tone or frequency is generated. When this MIB Object is 2461 set to a value of '0', the MTA MUST NOT generate the 2462 corresponding frequency or tone regardless of the 2463 definitions pertaining to frequency, tone duration or 2464 cadence." 2466 REFERENCE 2467 "PacketCable NCS Specification" 2468 DEFVAL { 16 } 2469 ::= { pktcNcsEndPntConfigEntry 6 } 2471 pktcNcsEndPntConfigMessageWaitingTO OBJECT-TYPE 2472 SYNTAX Unsigned32 2473 UNITS "seconds" 2474 MAX-ACCESS read-create 2475 STATUS current 2476 DESCRIPTION 2477 " This object contains the default timeout value for message 2478 waiting indicator. The MTA MUST NOT update this object 2479 with the value provided in the NCS message (if 2480 present). If the value of the object is modified by the 2481 SNMP Manager application, the MTA MUST use the new value 2482 as a default only for a new signal requested by the NCS 2483 message. 2484 The Time out (TO) elements are intended to limit the time 2485 a tone or frequency is generated. When this MIB Object is 2486 set to a value of '0', the MTA MUST NOT generate the 2487 corresponding frequency or tone regardless of the 2488 definitions pertaining to frequency, tone duration or 2489 cadence." 2491 REFERENCE 2492 "PacketCable NCS Specification" 2493 DEFVAL { 16 } 2494 ::= { pktcNcsEndPntConfigEntry 7 } 2496 pktcNcsEndPntConfigOffHookWarnToneTO OBJECT-TYPE 2497 SYNTAX Unsigned32 2498 UNITS "seconds" 2499 MAX-ACCESS read-create 2500 STATUS current 2501 DESCRIPTION 2502 " This object contains the default timeout value for the off 2503 hook Warning tone. The MTA MUST NOT update this object 2504 with the value provided in the NCS message (if 2505 present). If the value of the object is modified by the 2506 SNMP Manager application, the MTA MUST use the new value 2507 as a default only for a new signal requested by the NCS 2508 message. 2509 The Time out (TO) elements are intended to limit the time 2510 a tone or frequency is generated. When this MIB Object is 2511 set to a value of '0', the MTA MUST NOT generate the 2512 corresponding frequency or tone regardless of the 2513 definitions pertaining to frequency, tone duration or 2514 cadence." 2516 REFERENCE 2517 "PacketCable NCS Specification" 2518 DEFVAL { 0 } 2519 ::= { pktcNcsEndPntConfigEntry 8 } 2521 pktcNcsEndPntConfigRingingTO OBJECT-TYPE 2522 SYNTAX Unsigned32 2523 UNITS "seconds" 2524 MAX-ACCESS read-create 2525 STATUS current 2526 DESCRIPTION 2527 " This object contains the default timeout value for 2528 ringing. The MTA MUST NOT update this object with the 2529 value provided in the NCS message (if present). If 2530 the value of the object is modified by the SNMP Management 2531 Station, the MTA MUST use the new value as a default only 2532 for a new signal requested by the NCS message. 2533 The Time out (TO) elements are intended to limit the time 2534 a tone or frequency is generated. When this MIB Object is 2535 set to a value of '0', the MTA MUST NOT generate the 2536 corresponding frequency or tone regardless of the 2537 definitions pertaining to frequency, tone duration or 2538 cadence." 2540 REFERENCE 2541 "PacketCable NCS Specification" 2542 DEFVAL { 180 } 2543 ::= { pktcNcsEndPntConfigEntry 9 } 2545 pktcNcsEndPntConfigRingBackTO OBJECT-TYPE 2546 SYNTAX Unsigned32 2547 UNITS "seconds" 2548 MAX-ACCESS read-create 2549 STATUS current 2550 DESCRIPTION 2551 " This object contains the default timeout value for ring 2552 back. The MTA MUST NOT update this object with the 2553 value provided in the NCS message (if present). If 2554 the value of the object is modified by the SNMP Management 2555 Station, the MTA MUST use the new value as a default only 2556 for a new signal requested by the NCS message. 2557 The Time out (TO) elements are intended to limit the time 2558 a tone or frequency is generated. When this MIB Object is 2559 set to a value of '0', the MTA MUST NOT generate the 2560 corresponding frequency or tone regardless of the 2561 definitions pertaining to frequency, tone duration or 2562 cadence." 2564 REFERENCE 2565 "PacketCable NCS Specification" 2566 DEFVAL { 180 } 2567 ::= { pktcNcsEndPntConfigEntry 10 } 2569 pktcNcsEndPntConfigReorderToneTO OBJECT-TYPE 2570 SYNTAX Unsigned32 2571 UNITS "seconds" 2572 MAX-ACCESS read-create 2573 STATUS current 2574 DESCRIPTION 2575 " This object contains the default timeout value for reorder 2576 tone. The MTA MUST NOT update this object with the 2577 value provided in the NCS message (if present). If 2578 the value of the object is modified by the SNMP Management 2579 Station, the MTA MUST use the new value as a default only 2580 for a new signal requested by the NCS message. 2581 The Time out (TO) elements are intended to limit the time 2582 a tone or frequency is generated. When this MIB Object is 2583 set to a value of '0', the MTA MUST NOT generate the 2584 corresponding frequency or tone regardless of the 2585 definitions pertaining to frequency, tone duration or 2586 cadence." 2588 REFERENCE 2589 "PacketCable NCS Specification" 2590 DEFVAL { 30 } 2591 ::= { pktcNcsEndPntConfigEntry 11 } 2593 pktcNcsEndPntConfigStutterDialToneTO OBJECT-TYPE 2594 SYNTAX Unsigned32 2595 UNITS "seconds" 2596 MAX-ACCESS read-create 2597 STATUS current 2598 DESCRIPTION 2599 " This object contains the default timeout value for stutter 2600 dial tone. The MTA MUST NOT update this object with the 2601 value provided in the NCS message (if present). If 2602 the value of the object is modified by the SNMP Management 2603 Station, the MTA MUST use the new value as a default only 2604 for a new signal requested by the NCS message. 2605 The Time out (TO) elements are intended to limit the time 2606 a tone or frequency is generated. When this MIB Object is 2607 set to a value of '0', the MTA MUST NOT generate the 2608 corresponding frequency or tone regardless of the 2609 definitions pertaining to frequency, tone duration or 2610 cadence." 2612 REFERENCE 2613 "PacketCable NCS Specification" 2614 DEFVAL { 16 } 2615 ::= { pktcNcsEndPntConfigEntry 12 } 2617 pktcNcsEndPntConfigTSMax OBJECT-TYPE 2618 SYNTAX Unsigned32 2619 MAX-ACCESS read-create 2620 STATUS current 2621 DESCRIPTION 2622 "This MIB object is used as part of an NCS 2623 retransmission algorithm. Prior to any retransmission, 2624 the MTA must check to make sure that the time elapsed 2625 since the sending of the initial datagram does not 2626 exceed the value specified by this MIB Object. If more 2627 than Tsmax time has elapsed, then the retransmissions 2628 MUST cease. 2630 Refer to the MIB Object pktcNcsEndPntConfigThist for 2631 information on when the endpoint becomes disconnected." 2632 REFERENCE 2633 "PacketCable NCS Specification" 2634 DEFVAL { 20 } 2635 ::= { pktcNcsEndPntConfigEntry 13 } 2637 pktcNcsEndPntConfigMax1 OBJECT-TYPE 2638 SYNTAX Unsigned32 2639 MAX-ACCESS read-create 2640 STATUS current 2641 DESCRIPTION 2642 "This object contains the suspicious error threshold for 2643 signaling messages. The pktcNcsEndPntConfigMax1 object 2644 indicates the retransmission threshold at which the MTA MAY 2645 actively query the domain name server (DNS) in order to 2646 detect the possible change of call agent interfaces." 2647 REFERENCE 2648 "PacketCable NCS Specification" 2649 DEFVAL { 5 } 2650 ::= { pktcNcsEndPntConfigEntry 14 } 2652 pktcNcsEndPntConfigMax2 OBJECT-TYPE 2653 SYNTAX Unsigned32 2654 MAX-ACCESS read-create 2655 STATUS current 2656 DESCRIPTION 2657 "This object contains the disconnect error threshold for 2658 signaling messages. The pktcNcsEndPntConfigMax2 object 2659 indicates the retransmission threshold at which the MTA 2660 SHOULD contact the DNS one more time to see if any other 2661 interfaces to the call agent have become available." 2662 REFERENCE 2663 "PacketCable NCS Specification" 2664 DEFVAL { 7 } 2665 ::= { pktcNcsEndPntConfigEntry 15 } 2667 pktcNcsEndPntConfigMax1QEnable OBJECT-TYPE 2668 SYNTAX TruthValue 2669 MAX-ACCESS read-create 2670 STATUS current 2671 DESCRIPTION 2672 "This object enables/disables the Max1 domain name server 2673 (DNS) query operation when the pktcNcsEndPntConfigMax1 2674 threshold has been reached. 2675 A value of true(1) indicates enabling, and a value of 2676 false(2) indicates disabling." 2677 DEFVAL { true } 2678 ::= { pktcNcsEndPntConfigEntry 16 } 2680 pktcNcsEndPntConfigMax2QEnable OBJECT-TYPE 2681 SYNTAX TruthValue 2682 MAX-ACCESS read-create 2683 STATUS current 2684 DESCRIPTION 2685 "This object enables/disables the Max2 domain name server 2686 (DNS) query operation when the pktcNcsEndPntConfigMax2 2687 threshold has been reached. 2688 A value of true(1) indicates enabling, and a value of 2689 false(2) indicates disabling." 2690 DEFVAL { true } 2691 ::= { pktcNcsEndPntConfigEntry 17 } 2693 pktcNcsEndPntConfigMWD OBJECT-TYPE 2694 SYNTAX Unsigned32 2695 UNITS "seconds" 2696 MAX-ACCESS read-create 2697 STATUS current 2698 DESCRIPTION 2699 "Maximum Waiting Delay (MWD) contains the maximum number of 2700 seconds an MTA waits after powering on, before initiating 2701 the restart procedure with the call agent." 2702 REFERENCE 2703 "PacketCable NCS Specification" 2704 DEFVAL { 600 } 2705 ::= { pktcNcsEndPntConfigEntry 18 } 2707 pktcNcsEndPntConfigTdinit OBJECT-TYPE 2708 SYNTAX Unsigned32 2709 UNITS "seconds" 2710 MAX-ACCESS read-create 2711 STATUS current 2712 DESCRIPTION 2713 "This MIB object represents the 'disconnected' initial 2714 waiting delay within the context of an MTA's 'disconnected 2715 procedure'. The 'disconnected procedure' is initiated when 2716 an endpoint becomes 'disconnected' while attempting to 2717 communicate with a Call Agent. 2719 The 'disconnected timer' associated with the 'disconnected 2720 Procedure' is initialized to a random value, uniformly 2721 distributed between zero and the value contained in this 2722 MIB Object. 2724 For more information on the usage of this timer, please 2725 refer to the PacketCable NCS Specification." 2727 REFERENCE 2728 "PacketCable NCS Specification" 2729 DEFVAL { 15 } 2730 ::= { pktcNcsEndPntConfigEntry 19 } 2732 pktcNcsEndPntConfigTdmin OBJECT-TYPE 2733 SYNTAX Unsigned32 2734 UNITS "seconds" 2735 MAX-ACCESS read-create 2736 STATUS current 2737 DESCRIPTION 2738 "This MIB object represents the 'disconnected' minimum 2739 waiting delay within the context of an MTA's 2740 'disconnected procedure', specifically when local user 2741 activity is detected. 2742 The 'disconnected procedure' is initiated when 2743 an endpoint becomes 'disconnected' while attempting to 2744 communicate with a Call Agent. 2745 For more information on the usage of this timer, please 2746 refer to the PacketCable NCS Specification." 2748 REFERENCE 2749 "PacketCable NCS Specification" 2750 DEFVAL { 15 } 2751 ::= { pktcNcsEndPntConfigEntry 20 } 2753 pktcNcsEndPntConfigTdmax OBJECT-TYPE 2754 SYNTAX Unsigned32 2755 UNITS "seconds" 2756 MAX-ACCESS read-create 2757 STATUS current 2758 DESCRIPTION 2759 " This object contains the maximum number of seconds the MTA 2760 waits after a disconnect, before initiating the 2761 disconnected procedure with the call agent. 2762 " 2763 REFERENCE 2764 "PacketCable NCS Specification" 2765 DEFVAL { 600 } 2766 ::= { pktcNcsEndPntConfigEntry 21 } 2768 pktcNcsEndPntConfigRtoMax OBJECT-TYPE 2769 SYNTAX Unsigned32 2770 UNITS "seconds" 2771 MAX-ACCESS read-create 2772 STATUS current 2773 DESCRIPTION 2774 "This object specifies the maximum number of seconds the MTA 2775 waits for a response to an NCS message before initiating 2776 a retransmission." 2777 REFERENCE 2778 "PacketCable NCS Specification" 2779 DEFVAL { 4 } 2780 ::= { pktcNcsEndPntConfigEntry 22 } 2781 pktcNcsEndPntConfigRtoInit OBJECT-TYPE 2782 SYNTAX Unsigned32 2783 UNITS "milliseconds" 2784 MAX-ACCESS read-create 2785 STATUS current 2786 DESCRIPTION 2787 " This object contains the initial number of seconds for the 2788 retransmission timer." 2789 REFERENCE 2790 "PacketCable NCS Specification" 2791 DEFVAL { 200 } 2792 ::= { pktcNcsEndPntConfigEntry 23 } 2794 pktcNcsEndPntConfigLongDurationKeepAlive OBJECT-TYPE 2795 SYNTAX Unsigned32 2796 UNITS "minutes" 2797 MAX-ACCESS read-create 2798 STATUS current 2799 DESCRIPTION 2800 " Specifies a timeout value in minutes for sending long 2801 duration call notification message." 2802 REFERENCE 2803 "PacketCable NCS Specification" 2804 DEFVAL { 60 } 2805 ::= { pktcNcsEndPntConfigEntry 24 } 2807 pktcNcsEndPntConfigThist OBJECT-TYPE 2808 SYNTAX Unsigned32 2809 UNITS "seconds" 2810 MAX-ACCESS read-create 2811 STATUS current 2812 DESCRIPTION 2813 " Timeout period in seconds before no response is declared." 2814 REFERENCE 2815 "PacketCable NCS Specification" 2816 DEFVAL { 30 } 2817 ::= { pktcNcsEndPntConfigEntry 25 } 2819 pktcNcsEndPntConfigStatus OBJECT-TYPE 2820 SYNTAX RowStatus 2821 MAX-ACCESS read-create 2822 STATUS current 2823 DESCRIPTION 2824 " This object contains the Row Status associated with the 2825 pktcNcsEndPntConfigTable. There are no restrictions or 2826 dependencies amidst the columnar objects before this 2827 row can be activated or for modifications of the 2828 columnar objects when this object is set to a 2829 value of 'active(1)." 2830 ::= { pktcNcsEndPntConfigEntry 26 } 2832 pktcNcsEndPntConfigCallWaitingMaxRep OBJECT-TYPE 2833 SYNTAX Unsigned32 (0..10) 2834 MAX-ACCESS read-create 2835 STATUS current 2836 DESCRIPTION 2837 " This object contains the default value of the maximum 2838 number of repetitions of the call waiting tone that the 2839 MTA will play from a single CMS request. The MTA MUST NOT 2840 update this object with the information provided in the 2841 NCS message (if present). If the value of the object is 2842 modified by the SNMP Manager application, the MTA MUST use 2843 the new value as a default only for a new signal 2844 requested by the NCS message." 2845 DEFVAL { 1 } 2846 ::= { pktcNcsEndPntConfigEntry 27 } 2848 pktcNcsEndPntConfigCallWaitingDelay OBJECT-TYPE 2849 SYNTAX Unsigned32 (1..100) 2850 UNITS "seconds" 2851 MAX-ACCESS read-create 2852 STATUS current 2853 DESCRIPTION 2854 " This object contains the delay between repetitions of the 2855 call waiting tone that the MTA will play from a single CMS 2856 request." 2857 DEFVAL { 10 } 2858 ::= { pktcNcsEndPntConfigEntry 28 } 2860 pktcNcsEndPntStatusCallIpAddressType OBJECT-TYPE 2861 SYNTAX InetAddressType 2862 MAX-ACCESS read-only 2863 STATUS current 2864 DESCRIPTION 2865 " This object contains the type of Internet address contained 2866 in the MIB Object 'pktcNcsEndPntStatusCallIpAddress'" 2867 ::= { pktcNcsEndPntConfigEntry 29 } 2869 pktcNcsEndPntStatusCallIpAddress OBJECT-TYPE 2870 SYNTAX InetAddress 2871 MAX-ACCESS read-only 2872 STATUS current 2873 DESCRIPTION 2874 " This MIB Object contains the chosen IP address of the CMS 2875 currently being used for the corresponding endpoint. 2877 The device determines the IP address by using DNS to 2878 resolve the IP address of the CMS from the FQDN stored in 2879 the MIB Object 'pktcNcsEndPntConfigCallAgentId'. The 2880 processes are outlined in the PacketCable NCS and Security 2881 specifications, and MUST be followed by the MTA. 2883 The type of this IP address is indicated by 2884 the MIB Object 'pktcNcsEndPntStatusCallIpAddressType'." 2885 REFERENCE 2886 "PacketCable NCS Specification; 2887 PacketCable Security specification, [PKT-SP-SEC]." 2888 ::= { pktcNcsEndPntConfigEntry 30 } 2890 pktcNcsEndPntStatusError OBJECT-TYPE 2891 SYNTAX INTEGER { 2892 operational (1), 2893 noSecurityAssociation (2), 2894 disconnected (3) 2895 } 2896 MAX-ACCESS read-only 2897 STATUS current 2898 DESCRIPTION 2899 " This object contains the error status for this interface. 2900 The operational status indicates that all operations 2901 necessary to put the line in service have occurred, and the 2902 CMS has acknowledged the Restart In Progress (RSIP) 2903 message successfully. If pktcMtaDevCmsIpsecCtrl is enabled 2904 for the associated Call Agent, the noSecurityAssociation 2905 status indicates that no Security Association (SA) yet 2906 exists for this endpoint. If pktcMtaDevCmsIpsecCtrl is 2907 disabled for the associated Call Agent, the 2908 noSecurityAssociation status is not applicable and should 2909 not be used by the MTA. The disconnected status indicates 2910 one of the following two: 2911 If pktcMtaDevCmsIpsecCtrl is disabled, then no security 2912 association is involved with this endpoint. The NCS 2913 signaling software is in process of establishing the NCS 2914 signaling link via an RSIP exchange. 2915 Otherwise, when pktcMtaDevCmsIpsecCtrl is enabled, 2916 security Association has been established, and the NCS 2917 signaling software is in process of establishing the NCS 2918 signaling link via an RSIP exchange." 2919 ::= { pktcNcsEndPntConfigEntry 31 } 2921 pktcNcsEndPntConfigMinHookFlash OBJECT-TYPE 2922 SYNTAX Unsigned32 (20..1550) 2923 UNITS "Milliseconds" 2924 MAX-ACCESS read-only 2925 STATUS current 2926 DESCRIPTION 2927 " This is the minimum time a line needs to be on hook for a 2928 valid hook flash. The value of this object MUST be 2929 greater than the value of 2930 pktcNcsEndPntConfigPulseDialMaxBreakTime. The value of 2931 pktcNcsEndPntConfigMinHookFlash MUST be less than 2932 pktcNcsEndPntConfigMaxHookFlash. This object MUST only be 2933 set via the MTA configuration during the provisioning 2934 process. 2935 Furthermore, given the possibility for the 'pulse dial' 2936 and 'hook flash' to overlap, the value of this object 2937 MUST be greater than the value contained by the MIB 2938 Object 'pktcNcsEndPntConfigPulseDialMaxMakeTime'." 2939 DEFVAL { 300 } 2940 ::= { pktcNcsEndPntConfigEntry 32 } 2942 pktcNcsEndPntConfigMaxHookFlash OBJECT-TYPE 2943 SYNTAX Unsigned32 (20..1550) 2944 UNITS "Milliseconds" 2945 MAX-ACCESS read-only 2946 STATUS current 2947 DESCRIPTION 2948 " This is the maximum time a line needs to be on hook for a 2949 valid hook flash. The value of 2950 pktcNcsEndPntConfigMaxHookFlash MUST be greater than 2951 pktcNcsEndPntConfigMinHookFlash. This object MUST only be 2952 set via the MTA configuration during the provisioning 2953 process." 2954 DEFVAL { 800 } 2955 ::= { pktcNcsEndPntConfigEntry 33 } 2957 pktcNcsEndPntConfigPulseDialInterdigitTime OBJECT-TYPE 2958 SYNTAX Unsigned32 (100..1500) 2959 UNITS "Milliseconds" 2960 MAX-ACCESS read-only 2961 STATUS current 2962 DESCRIPTION 2963 " This is the pulse dial inter-digit timeout. This object 2964 MUST only be set via the MTA configuration during the 2965 provisioning process." 2966 DEFVAL { 100 } 2967 ::= { pktcNcsEndPntConfigEntry 34 } 2969 pktcNcsEndPntConfigPulseDialMinMakeTime OBJECT-TYPE 2970 SYNTAX Unsigned32 (20..200) 2971 UNITS "Milliseconds" 2972 MAX-ACCESS read-only 2973 STATUS current 2974 DESCRIPTION 2975 " This is the minimum make pulse width for the dial pulse. 2976 The value of pktcNcsEndPntConfigPulseDialMinMakeTime MUST 2977 be less than pktcNcsEndPntConfigPulseDialMaxMakeTime. This 2978 object MUST only be set via the MTA configuration during 2979 the provisioning process." 2980 DEFVAL { 25 } 2981 ::= { pktcNcsEndPntConfigEntry 35 } 2983 pktcNcsEndPntConfigPulseDialMaxMakeTime OBJECT-TYPE 2984 SYNTAX Unsigned32 (20..200) 2985 UNITS "Milliseconds" 2986 MAX-ACCESS read-only 2987 STATUS current 2988 DESCRIPTION 2989 " This is the maximum make pulse width for the dial pulse. 2990 The value of pktcNcsEndPntConfigPulseDialMaxMakeTime MUST 2991 be greater than pktcNcsEndPntConfigPulseDialMinMakeTime. 2992 This object MUST only be provided via the configuration 2993 file during the provisioning process. 2994 Furthermore, given the possibility for the 'pulse dial' 2995 and 'hook flash' to overlap, the value of this object MUST 2996 be less than the value contained by the MIB Object 2997 pktcNcsEndPntConfigMinHookFlash." 2998 DEFVAL { 55 } 2999 ::= { pktcNcsEndPntConfigEntry 36 } 3001 pktcNcsEndPntConfigPulseDialMinBreakTime OBJECT-TYPE 3002 SYNTAX Unsigned32 (20..200) 3003 UNITS "Milliseconds" 3004 MAX-ACCESS read-only 3005 STATUS current 3006 DESCRIPTION 3007 " This is the minimum break pulse width for the dial pulse. 3008 The value of pktcNcsEndPntConfigPulseDialMinBreakTime MUST 3009 be less than pktcNcsEndPntConfigPulseDialMaxBreakTime. 3010 This object must only be provided via the configuration 3011 file during the provisioning process." 3012 DEFVAL { 45 } 3013 ::= { pktcNcsEndPntConfigEntry 37 } 3015 pktcNcsEndPntConfigPulseDialMaxBreakTime OBJECT-TYPE 3016 SYNTAX Unsigned32 (20..200) 3017 UNITS "Milliseconds" 3018 MAX-ACCESS read-only 3019 STATUS current 3020 DESCRIPTION 3021 " This is the maximum break pulse width for the dial pulse. 3022 The value of pktcNcsEndPntConfigPulseDialMaxBreakTime MUST 3023 be greater than pktcNcsEndPntConfigPulseDialMinBreakTime. 3024 This object MUST only be provided via the configuration 3025 file during the provisioning process." 3026 DEFVAL { 75 } 3027 ::= { pktcNcsEndPntConfigEntry 38 } 3029 -- 3030 -- notification group is for future extension. 3031 -- 3032 pktcSigNotification OBJECT IDENTIFIER ::= { pktcSigMib 0 } 3033 pktcSigConformance OBJECT IDENTIFIER ::= { pktcSigMib 2 } 3034 pktcSigCompliances OBJECT IDENTIFIER ::= { pktcSigConformance 1 } 3035 pktcSigGroups OBJECT IDENTIFIER ::= { pktcSigConformance 2 } 3037 -- 3038 -- compliance statements 3039 -- 3041 pktcSigBasicCompliance MODULE-COMPLIANCE 3042 STATUS current 3043 DESCRIPTION 3044 " The compliance statement for MTAs that implement 3045 NCS Signaling." 3047 MODULE -- pktcSigMib 3049 --- 3050 -- Unconditionally mandatory groups for all MTAs 3051 --- 3053 MANDATORY-GROUPS { 3054 pktcNcsDeviceGroup, 3055 pktcNcsEndpointGroup 3056 } 3057 --- 3058 -- Conditionally mandatory groups for MTAs 3059 --- 3061 GROUP pktcInternationalGroup 3062 DESCRIPTION 3063 " This group is mandatory only for MTAs implementing 3064 international telephony features." 3066 GROUP pktcLLinePackageGroup 3067 DESCRIPTION 3068 " This group is mandatory only for MTAs implementing the L 3069 Line Package" 3071 GROUP pktcELinePackageGroup 3072 DESCRIPTION 3073 " This group is mandatory only for MTAs implementing the E 3074 Line Package" 3076 ::={ pktcSigCompliances 1 } 3078 pktcNcsDeviceGroup OBJECT-GROUP 3079 OBJECTS { 3080 pktcSigDevCodecMax, 3081 pktcSigDevEchoCancellation, 3082 pktcSigDevSilenceSuppression, 3083 pktcSigDevR0Cadence, 3084 pktcSigDevR1Cadence, 3085 pktcSigDevR2Cadence, 3086 pktcSigDevR3Cadence, 3087 pktcSigDevR4Cadence, 3088 pktcSigDevR5Cadence, 3089 pktcSigDevR6Cadence, 3090 pktcSigDevR7Cadence, 3091 pktcSigDevRgCadence, 3092 pktcSigDevRsCadence, 3093 pktcSigDefCallSigDscp, 3094 pktcSigDefMediaStreamDscp, 3095 pktcSigDevVmwiMode, 3096 pktcSigCapabilityType, 3097 pktcSigCapabilityVersion, 3098 pktcSigCapabilityVendorExt, 3099 pktcSigDefNcsReceiveUdpPort 3100 } 3101 STATUS current 3102 DESCRIPTION 3103 "Group of MIB Objects containing signaling configuration 3104 information that is applicable per-device." 3105 ::= { pktcSigGroups 1 } 3107 pktcNcsEndpointGroup OBJECT-GROUP 3108 OBJECTS { 3109 pktcNcsEndPntConfigCallAgentId, 3110 pktcNcsEndPntConfigCallAgentUdpPort, 3111 pktcNcsEndPntConfigPartialDialTO, 3112 pktcNcsEndPntConfigCriticalDialTO, 3113 pktcNcsEndPntConfigBusyToneTO, 3114 pktcNcsEndPntConfigDialToneTO, 3115 pktcNcsEndPntConfigMessageWaitingTO, 3116 pktcNcsEndPntConfigOffHookWarnToneTO, 3117 pktcNcsEndPntConfigRingingTO, 3118 pktcNcsEndPntConfigRingBackTO, 3119 pktcNcsEndPntConfigReorderToneTO, 3120 pktcNcsEndPntConfigStutterDialToneTO, 3121 pktcNcsEndPntConfigTSMax, 3122 pktcNcsEndPntConfigMax1, 3123 pktcNcsEndPntConfigMax2, 3124 pktcNcsEndPntConfigMax1QEnable, 3125 pktcNcsEndPntConfigMax2QEnable, 3126 pktcNcsEndPntConfigMWD, 3127 pktcNcsEndPntConfigTdinit, 3128 pktcNcsEndPntConfigTdmin, 3129 pktcNcsEndPntConfigTdmax, 3130 pktcNcsEndPntConfigRtoMax, 3131 pktcNcsEndPntConfigRtoInit, 3132 pktcNcsEndPntConfigLongDurationKeepAlive, 3133 pktcNcsEndPntConfigThist, 3134 pktcNcsEndPntConfigStatus, 3135 pktcNcsEndPntConfigCallWaitingMaxRep, 3136 pktcNcsEndPntConfigCallWaitingDelay, 3137 pktcNcsEndPntStatusCallIpAddressType, 3138 pktcNcsEndPntStatusCallIpAddress, 3139 pktcNcsEndPntStatusError 3140 } 3141 STATUS current 3142 DESCRIPTION 3143 "Group of MIB Objects containing signaling configuration 3144 information that is applicable per-endpoint." 3145 ::= { pktcSigGroups 2 } 3147 pktcInternationalGroup OBJECT-GROUP 3148 OBJECTS { 3149 pktcNcsEndPntConfigMinHookFlash, 3150 pktcNcsEndPntConfigMaxHookFlash, 3151 pktcNcsEndPntConfigPulseDialInterdigitTime, 3152 pktcNcsEndPntConfigPulseDialMinMakeTime, 3153 pktcNcsEndPntConfigPulseDialMaxMakeTime, 3154 pktcNcsEndPntConfigPulseDialMinBreakTime, 3155 pktcNcsEndPntConfigPulseDialMaxBreakTime, 3156 pktcSigDevRingCadence, 3157 pktcSigDevCidSigProtocol, 3158 pktcSigDevCidDelayAfterLR, 3159 pktcSigDevCidDtmfStartCode, 3160 pktcSigDevCidDtmfEndCode, 3161 pktcSigDevVmwiSigProtocol, 3162 pktcSigDevVmwiDelayAfterLR, 3163 pktcSigDevVmwiDtmfStartCode, 3164 pktcSigDevVmwiDtmfEndCode, 3165 pktcSigDevrpAsDtsDuration, 3166 pktcSigDevCidMode, 3167 pktcSigDevCidAfterRing, 3168 pktcSigDevCidAfterDTAS, 3169 pktcSigDevCidAfterRPAS, 3170 pktcSigDevRingAfterCID, 3171 pktcSigDevCidDTASAfterLR, 3172 pktcSigDevVmwiMode, 3173 pktcSigDevVmwiAfterDTAS, 3174 pktcSigDevVmwiAfterRPAS, 3175 pktcSigDevVmwiDTASAfterLR, 3176 pktcSigPowerRingFrequency, 3177 pktcSigPulseSignalFrequency, 3178 pktcSigPulseSignalDbLevel, 3179 pktcSigPulseSignalDuration, 3180 pktcSigPulseSignalPulseInterval, 3181 pktcSigPulseSignalRepeatCount, 3182 pktcSigDevToneDbLevel, 3183 pktcSigDevToneFreqCounter, 3184 pktcSigDevToneWholeToneRepeatCount, 3185 pktcSigDevToneSteady, 3186 pktcSigDevToneFirstFreqValue, 3187 pktcSigDevToneSecondFreqValue, 3188 pktcSigDevToneThirdFreqValue, 3189 pktcSigDevToneFourthFreqValue, 3190 pktcSigDevToneFreqMode, 3191 pktcSigDevToneFreqAmpModePrtg, 3192 pktcSigDevToneFreqOnDuration, 3193 pktcSigDevToneFreqOffDuration, 3194 pktcSigDevToneFreqRepeatCount 3195 } 3196 STATUS current 3197 DESCRIPTION 3198 " Group of objects that extend the behavior of existing 3199 objects to support operations in the widest possible set 3200 of international marketplaces. Note that many of these 3201 objects represent a superset of behaviors described in 3202 other objects within this MIB Module." 3203 ::= { pktcSigGroups 3 } 3205 pktcLLinePackageGroup OBJECT-GROUP 3206 OBJECTS { 3207 pktcSigDevR0Cadence, 3208 pktcSigDevR1Cadence, 3209 pktcSigDevR2Cadence, 3210 pktcSigDevR3Cadence, 3211 pktcSigDevR4Cadence, 3212 pktcSigDevR5Cadence, 3213 pktcSigDevR6Cadence, 3214 pktcSigDevR7Cadence, 3215 pktcSigDevRgCadence, 3216 pktcSigDevRsCadence 3217 } 3218 STATUS current 3219 DESCRIPTION 3220 "Group of Objects to support the L Line Package." 3221 ::= { pktcSigGroups 4 } 3223 pktcELinePackageGroup OBJECT-GROUP 3224 OBJECTS { 3225 pktcSigDevR0Cadence, 3226 pktcSigDevR1Cadence, 3227 pktcSigDevR2Cadence, 3228 pktcSigDevR3Cadence, 3229 pktcSigDevR4Cadence, 3230 pktcSigDevR5Cadence, 3231 pktcSigDevR6Cadence, 3232 pktcSigDevR7Cadence, 3233 pktcSigDevRgCadence, 3234 pktcSigDevRsCadence, 3235 pktcSigPulseSignalFrequency, 3236 pktcSigPulseSignalDbLevel, 3237 pktcSigPulseSignalDuration, 3238 pktcSigPulseSignalPulseInterval, 3239 pktcSigPulseSignalRepeatCount, 3240 pktcSigDevRingCadence 3241 } 3242 STATUS current 3243 DESCRIPTION 3244 "Group of Objects to support the E Line Package." 3245 ::= { pktcSigGroups 5 } 3247 END 3249 6. Examples 3250 This section provides a couple of examples, specifically related 3251 to the MIB tables pktcSigDevToneTable and 3252 pktcSigDevMultiFreqToneTable. 3254 Example A: Call waiting tone defined per ITU-T E.180: 3256 1) 400 Hz AM modulated by 16 Hz, on for 500ms at -4 dBm 3257 2) 400 Hz AM modulated by 16 Hz, off for 400ms 3258 3) 400 Hz not AM modulated, on for 50 ms at -4 dBm 3259 4) 400 Hz not AM modulated, off for 450 ms 3260 5) 400 Hz not AM modulated, on for 50 ms at -4 dBm 3261 6) 400 Hz not AM modulated, off for 3450 ms 3262 7) 400 Hz not AM modulated, on for 50 ms at -4 dBm 3263 8) 400 Hz not AM modulated, off for 450 ms 3264 9) 400 Hz not AM modulated, on for 50 ms at -4 dBm 3265 10) 400 Hz not AM modulated, off for 3450 ms 3266 11) not repeated, not continuous 3268 Assume userDefined1(18) is assigned to this tone: 3270 pktcSigDevMultiFreqToneTable: 3271 ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count 3272 =================================================================== 3273 18 400 16 0 0 1 90 -40 500 400 0 3274 18 400 0 0 0 2 0 -40 50 450 0 3275 18 400 0 0 0 2 0 -40 50 3450 0 3276 18 400 0 0 0 2 0 -40 50 450 0 3277 18 400 0 0 0 2 0 -40 50 3450 0 3279 pktcSigDevToneTable: 3280 ToneType|ToneFreqGroup|ToneFreqCounter|ToneRep-Count|Steady 3281 ============================================================= 3282 18 1 5 0 false(2) 3284 The single row of the pktcSigDevToneTable defines one multi- 3285 frequency group of five rows (ToneFreqCounter) defined in the 3286 pktcSigDevMultiFreqToneTable and instructs the MTA to play this 3287 group only once (non-repeatable as ToneRep-Count equals 0). 3289 Example B - Congestion Tone - congestion(17): 3291 Note: This example of an embedded cadence is based on an operator 3292 variation. 3294 1) 400Hz on for 400ms -10 dBm 3295 2) 400Hz off for 350ms 3296 3) 400Hz on for 225ms -4 dBm 3297 4) 400Hz off for 525ms 3298 5) repeat (1) through (4) 5000 times or T0 timeout (which ever is 3299 shortest period) 3301 pktcSigDevMultiFreqToneTable: 3302 ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count 3303 =================================================================== 3304 17 400 0 0 0 2 0 -100 400 350 0 3305 17 400 0 0 0 2 0 -40 225 525 0 3307 pktcSigDevToneTable: 3309 ToneType|ToneFreqGroup|ToneFreqCounter|ToneRep-Count|Steady 3310 ============================================================= 3311 17 1 2 5000 false(2) 3313 Example C - Call Waiting Tone - callWaiting1(9): 3315 1) 16 Hz is modulated to carry the 400 Hz signal, ModulationRate 3316 within 85%, on for 500msec, at -25 dBm or more but less than -14 dBm 3317 2) 16 Hz is modulated to carry the 400 Hz signal, off for 0 ~ 4 secs 3318 3) 400 Hz not modulated, on for 50 ms at -25 dBm or more but less 3319 than -14 dBm 3320 4) 400 Hz not modulated, off for 450ms 3321 5) 400 Hz not modulated, on for 50 ms at -25 dBm or more but less 3322 than -14 dBm 3323 6) 400 Hz not modulated, off for 3450ms ([4000 - (50+450+50)]) 3324 7) Steps 3 thru 6 are repeated. 3326 pktcSigDevMultiFreqToneTable: 3327 ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count 3328 =================================================================== 3329 9 1 400 16 0 0 1 85 -25 500 1000 0 3330 9 2 400 0 0 0 2 0 -25 50 450 0 3331 9 3 400 0 0 0 2 0 -25 50 3450 0 3333 pktcSigDevToneTable: 3334 ToneType|ToneFreqGroup|ToneFreqCounter|ToneRep-Count|Steady 3335 ============================================================= 3336 9 1 1 0 false(2) 3337 9 2 2 1 false(2) 3339 The first row of the pktcSigDevToneTable table instructs the MTA to 3340 play one row (ToneFreqCounter) of the pktcSigDevMultiFreqToneTable 3341 table only once (non-repeatable as ToneRep-Count equals 0). The 3342 second row of the pktcSigDevToneTable table instructs the MTA to 3343 play next two rows (ToneFreqCounter) of the 3344 pktcSigDevMultiFreqToneTable table and make this frequency group 3345 repeatable (ToneRep-Count is not 0). 3347 7. Acknowledgments 3349 The current editors would like to thank the members of the IETF 3350 IPCDN working group and the CableLabs PacketCable Provisioning focus 3351 team for their contributions, comments and suggestions. 3353 Specifically, the following individuals are recognized: 3355 Angela Lyda Arris Interactive 3356 Romascanu, Dan Avaya 3357 Chad Griffiths Broadcom Corp. 3358 Eugene Nechamkin Broadcom Corp. 3359 Jean-Francois Mule CableLabs(R) 3360 Matt A. Osman CableLabs(R) 3361 Klaus Hermanns Cisco Systems, Inc. 3362 Rich Woundy Comcast Corp. 3363 Bert Wijnen Lucent Technologies 3364 Randy Presuhn Mindspring 3365 Phillip Freyman Motorola, Inc. 3366 Rick Vetter Motorola, Inc. 3367 Sasha Medvinsky Motorola, Inc. 3368 Wim De Ketelaere tComLabs 3369 David De Reu tComLabs 3370 Kristof Sercu tComLabs 3371 Roy Spitzer Telogy Networks, Inc. 3372 Itay Sherman Texas Instruments, Inc. 3373 Mauricio Sanchez Texas Instruments, Inc. 3374 Shivakumar Thangapandi Texas Instruments, Inc. 3375 Mike Heard Consultant 3377 For the international objects, the authors are especially thankful 3378 to Phillip Freyman and Eugene Nechamkin for their recommendations 3379 and contributions. Stephane Bortzmeyer is thanked for verifying the 3380 ABNF. 3382 Special appreciation is also expressed to the IPCDN co-chairs (Jean- 3383 Francois, Rich woundy) and Dan Romascanu for the numerous reviews 3384 and valuable comments. Special appreciation is also extended to Bert 3385 Wijnen as the MIB doctor, for his ever useful and constructive 3386 comments. 3388 8. Security Considerations 3390 There are a number of management objects defined in this MIB that 3391 have a MAX-ACCESS clause of read-write and/or read-create. Such 3392 objects may be considered sensitive or vulnerable in some network 3393 environments. The support for SET operations in a non-secure 3394 environment without proper protection can have a negative effect on 3395 network operations. 3397 The following Differentiated Services Code Point (DSCP) and mask 3398 objects are used to differentiate between various types of traffic 3399 in the service provider network: 3401 pktcSigDefCallSigDscp 3402 pktcSigDefMediaStreamDscp 3404 These objects may contain information that may be sensitive from a 3405 business perspective. For example, they may represent a customer's 3406 service contract that a service provider chooses to apply to a 3407 customer's ingress or egress traffic. If these objects are SET 3408 maliciously, it may permit unmarked or inappropriately marked 3409 signaling and media traffic to enter the service provider network, 3410 resulting in unauthorized levels of service for customers. 3412 The following objects determine ring cadence, repeatable 3413 characteristics, signal duration, and caller id subscriber line 3414 protocol for telephony operation: 3416 pktcSigDevR0Cadence 3417 pktcSigDevR1Cadence 3418 pktcSigDevR2Cadence 3419 pktcSigDevR3Cadence 3420 pktcSigDevR4Cadence 3421 pktcSigDevR5Cadence 3422 pktcSigDevR6Cadence 3423 pktcSigDevR7Cadence 3424 pktcSigDevRgCadence 3425 pktcSigDevRsCadence 3426 pktcSigDevCidSigProtocol 3427 pktcSigDevVmwiSigProtocol 3428 pktcSigPulseSignalDuration 3429 pktcSigPulseSignalPauseDuration 3431 If these objects are SET maliciously, it may result in unwanted 3432 operation, or a failure to obtain telephony service from client 3433 (MTA) devices. 3435 The objects in the pktcNcsEndPntConfigTable are used for endpoint 3436 signaling. The pktcNcsEndPntConfigCallAgentId object contains the 3437 name of the call agent, which includes the call agent Fully 3438 Qualified Domain Name (FQDN). If this object is SET maliciously, the 3439 MTA will not be able to communicate with the call agent, resulting 3440 in a disruption of telephony service. The 3441 pktcNcsEndPntConfigCallAgentUdpPort object identifies the UDP port 3442 for NCS traffic. If this object is SET maliciously, the call agent 3443 will not receive NCS traffic from the MTA, also resulting in a 3444 disruption of telephony service. 3446 Some of the readable objects in this MIB module (i.e., objects with 3447 a MAX-ACCESS other than not-accessible) may be considered sensitive 3448 or vulnerable in some network environments. It is thus important to 3449 control even GET and/or NOTIFY access to these objects and possibly 3450 to even encrypt the values of these objects when sending them over 3451 the network via SNMP. The most sensitive is 3452 pktcNcsEndPntStatusCallIpAddress within pktcNcsEndPntConfigTable. 3453 This information itself may be valuable to would-be attackers. 3455 SNMP versions prior to SNMPv3 did not include adequate security. 3456 Even if the network itself is secure (for example by using IPsec), 3457 even then, there is no control as to who on the secure network is 3458 allowed to access and GET/SET (read/change/create/delete) the 3459 objects in this MIB module. 3461 It is RECOMMENDED that implementers consider the security features 3462 as provided by the SNMPv3 framework (see [RFC3410], section 8), 3463 including full support for the SNMPv3 cryptographic mechanisms (for 3464 authentication and privacy). 3466 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3467 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3468 enable cryptographic security. It is then a customer/operator 3469 responsibility to ensure that the SNMP entity giving access to an 3470 instance of this MIB module is properly configured to give access to 3471 the objects only to those principals (users) that have legitimate 3472 rights to indeed GET or SET (change/create/delete) them. 3474 9. IANA Considerations 3476 The MIB module in this document uses the following IANA-assigned 3477 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 3479 Descriptor OBJECT IDENTIFIER Value 3480 ---------- ----------------------- 3481 pktcSigMib { mib-2 XXX } 3483 Editor's Note (to be removed prior to publication): the IANA is 3484 requested to assign a value for XXX under the mib-2 subtree and to 3485 record the assignment in the SMI Numbers registry. When the 3486 assignment has been made, the RFC Editor is asked to replace XXX 3487 (here and in the MIB module) with the assigned value and to remove 3488 this note. 3490 10. Normative References 3492 [PKT-SP-MIB-SIG-1.0] PacketCable(TM) 1.0 Signaling MIB 3493 Specification, Issued, PKT-SP-MIB-SIG-I09-050812, 3494 August 2005. 3495 http://www.packetcable.com/specifications/ 3496 http://www.cablelabs.com/specifications/archives/ 3498 [PKT-SP-MIB-SIG-1.5] PacketCable(TM) 1.5 Signaling MIB 3499 Specification, Issued, PKT-SP-MIB-SIG1.5-I01-050128, 3500 January 2005. 3501 http://www.packetcable.com/specifications/ 3502 http://www.cablelabs.com/specifications/archives/ 3504 [PKT-SP-SEC] PacketCable Security Specification, Issued, PKT-SP- 3505 SEC-I12-050812, August 2005. 3506 http://www.packetcable.com/specifications/ 3507 http://www.cablelabs.com/specifications/archives/ 3509 [ITU-T-J169] IPCablecom Network Call Signaling (NCS) MIB 3510 requirements, J.169, ITU-T, March, 2001. 3512 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3513 Requirement Levels", BCP 14, RFC 2119, March 1997. 3515 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3516 Rose, M., and S. Waldbusser, "Structure of Management 3517 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3518 1999. 3520 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3521 Rose, M., and S. Waldbusser, "Textual Conventions for 3522 SMIv2", STD 58, RFC 2579, April 1999. 3524 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3525 Rose, M., and S. Waldbusser, "Conformance Statements for 3526 SMIv2", STD 58, RFC 2580, April 1999. 3528 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information 3529 Base for the Differentiated Services Architecture", RFC 3530 3289, May 2002. 3532 [RFC4001] Daniel, M., Haberman, B., Routhier, S., and 3533 Schoenwaelder, J., "Textual Conventions for Internet 3534 Network 3535 Addresses", RFC 4001, May 2002. 3537 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen "An 3538 Architecture for Describing Simple Network Management 3539 Protocol (SNMP) Management Frameworks", RFC 3411, December 3540 2002. 3541 [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB" 3542 ,RFC2863, June 2000. 3544 [PKT-SP-CODEC] Packetcable Audio/Video Codecs Specification 3545 PKT-SP-CODEC-IO5-040113. 3547 [PKT-SP-MGCP] Packetcable Network-Based Call Signaling Protocol 3548 Specification PKT-SP-EC-MGCP-I10-040402. 3550 [PKT-SP-PROV] Packetcable MTA Device Provisioning Specification 3551 PKT-SP-PROV-I10-040730. 3553 11. Informative References 3555 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 3556 "Introduction and Applicability Statements for Internet- 3557 Standard Management Framework", RFC 3410, December 2002. 3559 [RFC3435] Andreasen, F., and B. Foster, "Media Gateway Control 3560 Protocol (MGCP)", RFC 3435, January 2003. 3562 [RFC4234] D. Crocker, Ed. and P. Overell, "Augmented BNF for Syntax 3563 Specifications: ABNF", RFC4234, October 2005. 3565 [RFC4682] Nechamkin, E., and Mule J., "Multimedia Terminal Adapter 3566 (MTA) Management Information Base for PacketCable and 3567 IPCablecom compliant devices", RFC4682, . 3569 [ETSI-TS-101-909-4] ETSI TS 101 909-4:"Access and Terminals (AT); 3570 Digital Broadband Cable Access to the Public 3571 Telecommunications Network; IP Multimedia Time Critical 3572 Services; Part 4: Network Call Signaling Protocol". 3574 [ETSI-TS-101-909-9] ETSI TS 101 909-9:"Access and Terminals (AT); 3575 Digital Broadband Cable Access to the Public 3576 Telecommunications Network; IP Multimedia Time Critical 3577 Services; Part 9: IPCablecom Network Call Signalling 3578 (NCS) MIB Requirements". 3580 [ETSI-EN-300-001] ETSI EN 300-001 V1.5.1 (1998-10):"European 3581 Standard (Telecommunications series) Attachments 3582 to Public Switched Telephone Network (PSTN); 3583 General technical requirements for equipment connected to 3584 an analogue subscriber interface in the PSTN; Chapter 3: 3585 Ringing signal characteristics (national deviations are in 3586 Table 3.1.1)". 3588 [ETSI-EN-300-324-1] ETSI EN 300 324-1 V2.1.1 (2000-04):"V Interfaces 3589 at the digital Loop Exchange (LE); V5.1 interface for the 3590 support of Access Network (AN); Part 1: V5.1 interface 3591 specification". 3593 [ETSI-EN-300-659-1] ETSI EN 300 659-1: "Public Switched Telephone 3594 Network (PSTN); Subscriber line protocol over the local 3595 loop for display (and related) services; Part 1: On hook 3596 data transmission". 3597 [ITU-T-E.180] ITU-T E.180: "Various Tones Used in National Networks, 3598 Supplement 2 to Recommendation E.180". 3600 [ETSI-TR-101-183] ETSI TR-101-183: "Public Switched Telephone 3601 Network (PSTN) Analogue Ringing Signals". 3603 Authors' Addresses 3605 Gordon Beacham 3606 Motorola, Inc. 3607 6450 Sequence Drive, Bldg. 1 3608 San Diego, CA 92121, USA 3609 +1 858-404-2334 3610 gordon.beacham@motorola.com 3612 Satish Kumar Mudugere Eswaraiah 3613 Texas Instruments India (P) Ltd., 3614 Golf view, Wind Tunnel Road 3615 Murugesh Palya 3616 Bangalore 560 017, INDIA 3617 +91 80 5269451 3618 satish.kumar@ti.com 3620 Sumanth Channabasappa 3621 Cable Television Laboratories, Inc. 3622 858 Coal Creek Circle, 3623 Louisville, CO 80027, USA 3624 +1 303-661-3307 3625 Sumanth@cablelabs.com 3627 Disclaimer of validity 3628 The IETF takes no position regarding the validity or scope of any 3629 Intellectual Property Rights or other rights that might be claimed 3630 to pertain to the implementation or use of the technology described 3631 in this document or the extent to which any license under such 3632 rights might or might not be available; nor does it represent that 3633 it has made any independent effort to identify any such rights. 3634 Information on the procedures with respect to rights in RFC 3635 documents can be found in BCP 78 and BCP 79. 3637 Copies of IPR disclosures made to the IETF Secretariat and any 3638 assurances of licenses to be made available, or the result of an 3639 attempt made to obtain a general license or permission for the use 3640 of such proprietary rights by implementers or users of this 3641 specification can be obtained from the IETF on-line IPR repository 3642 at http://www.ietf.org/ipr. 3644 The IETF invites any interested party to bring to its attention any 3645 copyrights, patents or patent applications, or other proprietary 3646 rights that may cover technology that may be required to implement 3647 this standard. Please address the information to the IETF at 3648 ietf-ipr@ietf.org. 3650 Full Copyright Statement 3652 Copyright (C) The IETF Trust (2007). 3654 This document is subject to the rights, licenses and restrictions 3655 contained in BCP 78, and except as set forth therein, the authors 3656 retain all their rights. 3658 This document and the information contained herein are provided on 3659 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 3660 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 3661 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 3662 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 3663 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 3664 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 3665 FOR A PARTICULAR PURPOSE.