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