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