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