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