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