idnits 2.17.1 draft-ietf-ipcdn-pktc-signaling-01.txt: -(1705): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 3 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 354: '... MAY be supported. The lis...' RFC 2119 keyword, line 388: '... tone. 64 bits MUST be used for cade...' RFC 2119 keyword, line 392: '... bits MUST be used, otherwi...' RFC 2119 keyword, line 764: '...) string, an MTA MUST create the NCS S...' RFC 2119 keyword, line 768: '... MTA MUST delete the NCS S...' (16 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack 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 (May 2003) is 7653 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2119' is mentioned on line 92, but not defined == Unused Reference: 'RFC3289' is defined on line 2501, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 2505, but no explicit reference was found in the text == Unused Reference: 'RFC3435' is defined on line 2509, but no explicit reference was found in the text == Unused Reference: 'PKT-SP-MGCP-IO7-030415' is defined on line 2512, but no explicit reference was found in the text == Unused Reference: 'PKT-SP-PROV-IO6-030415' is defined on line 2516, but no explicit reference was found in the text == Unused Reference: 'PKT-SP-CODEC-IO4-021018' is defined on line 2519, but no explicit reference was found in the text == Unused Reference: 'RFC3261' is defined on line 2531, but no explicit reference was found in the text == Unused Reference: 'PKT-SP-MIB-MTA-I06-030415' is defined on line 2536, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) ** Downref: Normative reference to an Informational RFC: RFC 3435 -- Possible downref: Non-RFC (?) normative reference: ref. 'PKT-SP-MGCP-IO7-030415' -- Possible downref: Non-RFC (?) normative reference: ref. 'PKT-SP-PROV-IO6-030415' -- Possible downref: Non-RFC (?) normative reference: ref. 'PKT-SP-CODEC-IO4-021018' Summary: 5 errors (**), 0 flaws (~~), 12 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IPCDN 2 Internet Draft Gordon Beacham 3 Document: draft-ietf-ipcdn-pktc-signaling-01.txt Motorola, Inc 5 Satish Kumar 6 Texas Instruments 7 Sumanth 8 Channabasappa 9 Alopa Networks 10 Inc 11 Expires: November 2003 May 2003 13 Network Control Signaling (NCS) Signaling MIB for 14 PacketCable/IPCablecom MTAs 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance with 19 all provisions of Section 10 of RFC 2026 [RFC2026]. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other documents 28 at any time. It is inappropriate to use Internet-Drafts as 29 reference material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Copyright Notice 38 Copyright (C) The Internet Society (2003). All Rights Reserved. 40 Abstract 42 This memo defines the Signaling Management Information Base (MIB) 43 for use with network management protocols in the Internet community. 44 In particular, it provides a common data and format representation 45 for PacketCable/IPCablecom compliant Multimedia Terminal Adapter 46 devices. 48 This memo specifies a MIB module in a manner that is compliant to 49 the SNMP SMIv2. The set of objects are consistent with the SNMP 50 framework and existing SNMP standards. 52 Table of Contents 54 1. The Internet-Standard Management Framework....................2 55 2. Terminology...................................................2 56 2.1 MTA.......................................................3 57 3. Overview......................................................3 58 3.1 Structure of the MIB......................................3 59 3.2 pktcSigDevConfigObjects...................................3 60 3.3 pktcSigNotification.......................................5 61 3.4 pktcSigConformance........................................6 62 4. Definitions...................................................6 63 5. Acknowledgments..............................................51 64 6. Normative References.........................................51 65 7. Informative References.......................................52 66 8. Security Considerations......................................53 67 9. Intellectual Property........................................55 68 10. Authors' Addresses..........................................55 69 11. Full Copyright Statement....................................56 71 1. The Internet-Standard Management Framework 73 For a detailed overview of the documents that describe the current 74 Internet-Standard Management Framework, please refer to section 7 of 75 RFC 3410 [RFC3410]. 77 Managed objects are accessed via a virtual information store, termed 78 the Management Information Base or MIB. MIB objects are generally 79 accessed through the Simple Network Management Protocol (SNMP). 80 Objects in the MIB are defined using the mechanisms defined in the 81 Structure of Management Information (SMI). This memo specifies a MIB 82 module that is compliant to the SMIv2, which is described in STD 58, 83 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 84 [RFC2580]. 86 2. Terminology 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 90 "OPTIONAL", when used in the guidelines in this memo, are to be 91 interpreted as described in RFC 2119 [RFC2119]. 93 The terms "MIB module" and "information module" are used 94 interchangeably in this memo. As used here, both terms refer to any 95 of the three types of information modules defined in Section 3 of 96 RFC 2578 [RFC2578]. 98 2.1 MTA 100 Multimedia Terminal Adapter, a device that contains the interface(s) 101 to a physical voice device, a network interface, CODECs, and all 102 signaling and encapsulation functions required for VoIP transport, 103 class feature signaling and QoS signaling. 105 3. Overview 107 This MIB provides a set of objects required for Signaling 108 PacketCable and IPCablecom compliant MultiMedia Terminal Adapter 109 (MTA) devices. MTA devices include one or more endpoints (e.g., 110 telephone ports) which receive signaling information to establish 111 ring cadence, and codecs used for providing telephony service. 113 Telephone systems are typically very complex and often have a wide 114 distribution. It is therefore important for management systems to 115 support MTAs from multiple vendors at the same time, including those 116 from multiple countries. This MIB module provides objects suitable 117 for managing signaling for MTA devices in the widest possible 118 variety of marketplaces. 120 3.1 Structure of the MIB 122 This MIB is identified by pktcSigMib and is structured in three 123 groups: 125 - Signaling information that control device and endpoint 126 configuration objects (pktcSigMibObjects) 128 - Signaling Notification object, that notifies the status 129 (pktcSigNotification) 131 - Signaling Conformance has mandatory signaling objects 132 (pktcSigConformance) 134 Each group of objects is explained in detail. 136 3.2 pktcSigDevConfigObjects 138 pktcSigDevCodecTable - this table describes MTA supported codec 139 types. 141 pktcSigDevEchoCancellation - This object identifies the capability 142 of echo cancellation on the device. 144 pktcSigDevSilenceSuppression - This object specifies if the device 145 is capable of silence suppression (Voice Activity Detection). 147 pktcSigDevConnectionMode - This object specifies the connection 148 modes that the MTA device can support. 150 pktcSigDevR0Cadence - this object specifies ring cadence 0. 152 pktcSigDevR6Cadence - this object specifies ring cadence 6. 154 pktcSigDevR7Cadence - this object specifies ring cadence 7. 156 pktcSigDefCallSigDscp - this object specifies the default value used 157 in the IP header for setting the Differentiated Services Code Point 158 (DSCP) value for call signaling. 160 pktcSigDefMediaStreamDscp - this object specifies the default value 161 used in the IP header for setting the Differentiated Services Code 162 Point (DSCP) value for media stream packets. 164 pktcSigCapabilityTable - this table specifies list of supported 165 signaling types, versions and vendor extensions for MTA. 167 pktcSigDefNcsReceiveUdpPort - this object contains the MTA User 168 Datagram Protocol (UDP) receive port that is being used for NCS call 169 signaling. 171 pktcSigServiceClassNameUS - this object contains a string indicating 172 the Service Class Name to create an Upstream Service Flow for NCS. 174 pktcSigServiceClassNameDS - this object contains a string indicating 175 the Service Class Name to create an Downstream Service Flow for NCS. 177 pktcSigServiceClassNameMask - this object contains a value for the 178 Call Signaling Network Mask. 180 pktcSigNcsServiceFlowState - this object contains a status value of 181 the Call Signaling Service Flow. 183 pktcSigDevR1Cadence - this object specifies ring cadence 1. 185 pktcSigDevR2Cadence - this object specifies ring cadence 2. 187 pktcSigDevR3Cadence - this object specifies ring cadence 3. 189 pktcSigDevR4Cadence - this object specifies ring cadence 4. 191 pktcSigDevR5Cadence - this object specifies ring cadence 5. 193 pktcSigDevRgCadence - this object specifies ring cadence rg. 195 pktcSigDevRsCadence - this object specifies ring cadence rs. 197 pktcSigDevRtCadence - this object specifies ring cadence rt. 199 pktcSigDevCIDMode - this ETSI object selects various modes of caller 200 id in common use. 202 pktcSigDevCIDFskAfterRing - this ETSI object sets the delay between 203 the end of first ringing and the transmission of caller id 204 information. 206 pktcSigDevCIDFskAfterDTAS - this ETSI object sets the delay between 207 the dual-tone alert signal and the transmission of caller id 208 information. 210 pktcSigDevCIDRingAfterFSK - this ETSI object sets the delay between 211 the transmission of caller id information and the first ringing 212 pattern. 214 pktcSigDevCIDDTASAfterLR - this ETSI object sets the delay between 215 the end of a line reversal and the dual-tone alert signal. 217 pktcSigDevRingCadenceTable - this international object provides a 218 flexible structure within which to specify a variety of ring 219 cadences. 221 pktcSigDevStandardRingCadence - this international object specifies 222 the standard ring assumed by the MTA. 224 pktcSigDevRingSplashCadence - this international object specifies 225 the standard splash ring assumed by the MTA. 227 pktcSigDevToneTable - this international object specifies a flexible 228 structure within which to specify all of the tones used in the MTA. 230 pktcNcsEndPntConfigTable - this table describes the PacketCable NCS 231 EndPoint configuration. The number of entries in this table 232 represents the number of provisioned endpoints. 234 pktcSigEndPntConfigTable - this table describes the PacketCable 235 EndPoint selected signaling type. The number of entries in this 236 table represents the number of provisioned endpoints. 238 3.3 pktcSigNotification 240 pktcSigNotification - this object is used for signaling notification 241 and reserved for future use. 243 3.4 pktcSigConformance 245 pktcSigCompliances - this table has one object that has compliance 246 statements for devices that implement Signaling on the MTA. 248 pktcSigGroups - this table contains group of objects for the common 249 portion of the PacketCable NCS and Signaling MIB. 251 pktcInternationalGroup - this table extends this MIB Module by 252 establishing a set of objects designed to support operations over 253 the widest range of marketplaces as is possible. 255 4. Definitions 257 PKTC-IETF-SIG-MIB DEFINITIONS ::= BEGIN 259 IMPORTS 260 MODULE-IDENTITY, 261 OBJECT-TYPE, 262 Integer32, 263 Unsigned32, 264 mib-2 265 FROM SNMPv2-SMI 266 InetAddressType, 267 InetAddress, 268 InetPortNumber 269 FROM INET-ADDRESS-MIB 270 TEXTUAL-CONVENTION, 271 RowStatus, 272 TruthValue 273 FROM SNMPv2-TC 274 OBJECT-GROUP, 275 MODULE-COMPLIANCE 276 FROM SNMPv2-CONF 277 SnmpAdminString 278 FROM SNMP-FRAMEWORK-MIB 279 ifIndex 280 FROM IF-MIB 281 Dscp 282 FROM DIFFSERV-DSCP-TC; 284 pktcSigMib MODULE-IDENTITY 285 LAST-UPDATED "200305070000Z" -- May 7, 2003 286 ORGANIZATION "IETF IPCDN Working Group" 287 CONTACT-INFO 288 "Satish Kumar Mudugere Eswaraiah 289 Texas Instruments India (P) Ltd., 290 Golf view, Wind Tunnel Road 291 Murugesh Palya 292 Bangalore - 560 017, INDIA 293 Phone: +91 80 5269451 294 Email: satish.kumar@ti.com 296 Sumanth Channabasappa 297 Alopa Networks Inc 298 248, McCaslin Bvld #101, 299 Louisville, Colorado - 80027 300 U.S.A. 301 Phone: +1 303 604 6595 302 Email: Sumanth@alopa.com 304 Gordon Beacham 305 Motorola BCS/DCG 306 6450 Sequence Drive, Bldg. 1 307 San Diego, CA 92121, USA 308 Phone: +1 858-404-2335 309 E-Mail: gordon.beacham@motorola.com 311 IETF IPCDN Working Group 312 General Discussion: ipcdn@ietf.org 313 Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn 314 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 315 Co-Chair: Jean-Francois Mule, jf.mule@cablelabs.com 316 Co-Chair: Richard Woundy, Richard_Woundy@cable.comcast.com" 318 DESCRIPTION 319 "This MIB module supplies the basic management 320 object for the PacketCable/IPCablecom Signaling 321 protocols. This version of the MIB includes 322 common signaling and Network Call Signaling 323 (NCS) related signaling objects. 325 Copyright (C) The Internet Society (2003). This version of 326 this MIB module is part of RFC yyyy; see the RFC itself for 327 full legal notices." 328 -- RFC Ed: replace yyyy with actual RFC number and remove this note 330 REVISION "200305070000Z" 332 DESCRIPTION 333 "Initial version, published as RFC yyyy." 334 -- RFC Ed: replace yyyy with actual RFC number and remove this note 336 ::= { mib-2 XXX } 337 -- RFC Ed: replace XXX with IANA-assigned number and remove this 338 -- note 340 -- Textual Conventions 341 TenthdBm ::= TEXTUAL-CONVENTION 342 DISPLAY-HINT "d-1" 343 STATUS current 344 DESCRIPTION 345 "This data type represents power levels that are normally 346 expressed in dBm. Units are in tenths of a dBm; 347 for example, -13.5 dBm will be represented as -135." 348 SYNTAX Integer32 350 PktcCodecType ::= TEXTUAL-CONVENTION 351 STATUS current 352 DESCRIPTION 353 " Textual Convention defines various types of CODECs that 354 MAY be supported. The list of CODECs MUST be consistent 355 with the Codec RTP MAP Parameters Table in the PacketCable 356 CODEC specification. In-line embedded comments below 357 contain the Literal Codec Name for each CODEC. The Literal 358 Codec Name is the second column of the table with CODEC 359 RTP Map Parameters. Literal Codec Name Column contains the 360 CODEC name used in LCD of the NCS messages CRCX/MDCX and 361 is also used to identify the CODEC in the CMS 362 Provisioning Specification. RTP Map Parameter Column of 363 the Table contains the string used in the media attribute 364 line (a=) of the SDP parameters in NCS messages." 365 SYNTAX INTEGER { 366 other (1), 367 unknown (2), 368 g729 (3), -- G729 369 reserved (4), -- reserved for future use 370 g729E (5), -- G729E 371 pcmu (6), -- PCMU 372 g726at32 (7), -- G726-32 373 g728 (8), -- G728 374 pcma (9), -- PCMA 375 g726at16 (10), -- G726-16 376 g726at24 (11), -- G726-24 377 g726at40 (12) -- G726-40 378 } 380 PktcRingCadence ::= TEXTUAL-CONVENTION 381 STATUS current 382 DESCRIPTION 383 " This object represents a ring cadence and repeatable 384 characteristics in bit string format. The ring cadence 385 representation starts with the first 1 in the pattern (the 386 leading 0s in the MSB are padding and are to be ignored). 387 Each bit represents 100ms of tone; 1 is tone, 0 is no 388 tone. 64 bits MUST be used for cadence representation. The 389 LSB 4 bits of this object are used for representing 390 repeatable characteristics. 0000 means repeatable, and 391 1000 means non repeatable. During SNMP SET operations, 64 392 bits MUST be used, otherwise the MTA MUST reject the 393 value. As an example, the hex representation of a ring 394 cadence of 0.5 secs on; 4 secs off; repeatable would be: 395 0x0001F00000000000." 396 SYNTAX BITS { 397 interval1 (0), 398 interval2 (1), 399 interval3 (2), 400 interval4 (3), 401 interval5 (4), 402 interval6 (5), 403 interval7 (6), 404 interval8 (7), 405 interval9 (8), 406 interval10 (9), 407 interval11 (10), 408 interval12 (11), 409 interval13 (12), 410 interval14 (13), 411 interval15 (14), 412 interval16 (15), 413 interval17 (16), 414 interval18 (17), 415 interval19 (18), 416 interval20 (19), 417 interval21 (20), 418 interval22 (21), 419 interval23 (22), 420 interval24 (23), 421 interval25 (24), 422 interval26 (25), 423 interval27 (26), 424 interval28 (27), 425 interval29 (28), 426 interval30 (29), 427 interval31 (30), 428 interval32 (31), 429 interval33 (32), 430 interval34 (33), 431 interval35 (34), 432 interval36 (35), 433 interval37 (36), 434 interval38 (37), 435 interval39 (38), 436 interval40 (39), 437 interval41 (40), 438 interval42 (41), 439 interval43 (42), 440 interval44 (43), 441 interval45 (44), 442 interval46 (45), 443 interval47 (46), 444 interval48 (47), 445 interval49 (48), 446 interval50 (49), 447 interval51 (50), 448 interval52 (51), 449 interval53 (52), 450 interval54 (53), 451 interval55 (54), 452 interval56 (55), 453 interval57 (56), 454 interval58 (57), 455 interval59 (58), 456 interval60 (59), 457 repeat1 (60), 458 repeat2 (61), 459 repeat3 (62), 460 repeat4 (63) 461 } 463 PktcSigType ::= TEXTUAL-CONVENTION 464 STATUS current 465 DESCRIPTION 466 " This object lists the various types of signaling that may 467 be supported. 468 ncs - Network call signaling is a derivation of MGCP 469 (Media Gateway Control Protocol) defined for 470 PacketCable and IPCablecom MTAs. " 471 SYNTAX INTEGER { 472 other(1), 473 reserved(2), -- reserved for future use 474 ncs(3) 475 } 477 pktcSigMibObjects OBJECT IDENTIFIER ::= { pktcSigMib 1 } 478 pktcSigDevConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 1 479 } 480 pktcNcsEndPntConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 481 2 } 482 pktcSigEndPntConfigObjects OBJECT IDENTIFIER ::= { 483 pktcSigMibObjects 3 } 485 -- 486 -- The pktcSigDevCodecTable defines the codecs supported by the 487 -- Media Terminal Adapter (MTA). There is one entry for each codec 488 -- supported. 489 -- 491 pktcSigDevCodecTable OBJECT-TYPE 492 SYNTAX SEQUENCE OF PktcSigDevCodecEntry 493 MAX-ACCESS not-accessible 494 STATUS current 495 DESCRIPTION 496 " This table describes the MTA supported codec types." 497 ::= { pktcSigDevConfigObjects 1 } 499 pktcSigDevCodecEntry OBJECT-TYPE 500 SYNTAX PktcSigDevCodecEntry 501 MAX-ACCESS not-accessible 502 STATUS current 503 DESCRIPTION 504 " List of supported codec types for the MTA." 505 INDEX { pktcSigDevCodecIndex } 506 ::= { pktcSigDevCodecTable 1 } 508 PktcSigDevCodecEntry ::= SEQUENCE { 509 pktcSigDevCodecIndex Unsigned32, 510 pktcSigDevCodecType PktcCodecType, 511 pktcSigDevCodecMax Unsigned32 512 } 514 pktcSigDevCodecIndex OBJECT-TYPE 515 SYNTAX Unsigned32 (1..255) 516 MAX-ACCESS not-accessible 517 STATUS current 518 DESCRIPTION 519 " The index value which uniquely identifies an entry in the 520 pktcSigDevCodecTable." 521 ::= { pktcSigDevCodecEntry 1 } 523 pktcSigDevCodecType OBJECT-TYPE 524 SYNTAX PktcCodecType 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 " A codec type supported by this MTA." 529 ::= { pktcSigDevCodecEntry 2 } 531 pktcSigDevCodecMax OBJECT-TYPE 532 SYNTAX Unsigned32(1..255) 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 " The maximum number of simultaneous sessions of the 537 specific codec that the MTA can support. For example: 538 pktcSigDevCodecType PktcSigDevCodecMax 539 pcma 2 540 g728 2 541 The MTA can simultaneously support 2 sessions using a PCMA 542 codec AND 2 sessions using a G728 codec. In this example, 543 the MTA can NOT simultaneously support 1 PCMA codec and 3 544 G728 codecs." 545 ::= { pktcSigDevCodecEntry 3 } 547 -- 548 -- These are the common signaling related definitions that affect 549 -- the entire MTA device. 550 -- 552 pktcSigDevEchoCancellation OBJECT-TYPE 553 SYNTAX TruthValue 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 " This object specifies if the device is capable of echo 558 cancellation." 559 ::= { pktcSigDevConfigObjects 2 } 561 pktcSigDevSilenceSuppression OBJECT-TYPE 562 SYNTAX TruthValue 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 " This object specifies if the device is capable of 567 silence suppression (Voice Activity Detection)." 568 ::= { pktcSigDevConfigObjects 3 } 570 pktcSigDevConnectionMode OBJECT-TYPE 571 SYNTAX BITS { 572 voice(0), 573 fax(1), 574 modem(2) 575 } 576 MAX-ACCESS read-only 577 STATUS current 578 DESCRIPTION 579 " This object specifies the connection modes that the MTA 580 device can support." 581 ::= { pktcSigDevConfigObjects 4 } 583 -- 584 -- In the United States Ring Cadences 0, 6, and 7 are custom ring 585 -- cadences definable by the user. The following three objects are 586 -- used for these definitions. 587 -- 589 pktcSigDevR0Cadence OBJECT-TYPE 590 SYNTAX PktcRingCadence 591 MAX-ACCESS read-write 592 STATUS current 593 DESCRIPTION 594 " This object specifies ring cadence 0 (a user defined 595 field) where each bit represents a duration of 100 596 milliseconds (6 seconds total), except the LSB 4 bits 597 which are used to represent repeatable characteristics." 598 DEFVAL {{ interval1, interval2, interval3, interval4, interval5, 599 interval6, interval7, interval8, interval9, 600 interval10, interval11, interval12, interval13, 601 interval14, interval15, interval16, interval17, 602 interval18, interval19, interval20 }} 603 -- 11111111111111111111000000000000000000000000000000000000000 604 -- 00000 605 ::= { pktcSigDevConfigObjects 5 } 607 pktcSigDevR6Cadence OBJECT-TYPE 608 SYNTAX PktcRingCadence 609 MAX-ACCESS read-write 610 STATUS current 611 DESCRIPTION 612 " This object specifies ring cadence 6 (a user defined 613 field) where each bit represents a duration of 100 614 milliseconds (6 seconds total), except the LSB 4 bits 615 which are used to represent repeatable characteristics." 616 DEFVAL {{ interval1, interval2, interval3, interval4, interval5, 617 interval6, interval7, interval8, interval9, 618 interval10, interval11, interval12, interval13, 619 interval14, interval15, interval16, interval17, 620 interval18, interval19, interval20 }} 621 -- 11111111111111111111000000000000000000000000000000000000000 622 -- 00000 623 ::= { pktcSigDevConfigObjects 6 } 625 pktcSigDevR7Cadence OBJECT-TYPE 626 SYNTAX PktcRingCadence 627 MAX-ACCESS read-write 628 STATUS current 629 DESCRIPTION 630 " This object specifies ring cadence 7 (a user defined 631 field) where each bit represents a duration of 100 632 milliseconds (6 seconds total), except the LSB 4 bits 633 which are used to represent repeatable characteristics." 635 DEFVAL {{ interval1, interval2, interval3, interval4, interval5, 636 interval6, interval7, interval8, interval9, 637 interval10, interval11, interval12, interval13, 638 interval14, interval15, interval16, interval17, 639 interval18, interval19, interval20 }} 640 -- 11111111111111111111000000000000000000000000000000000000000 641 -- 00000 642 ::= { pktcSigDevConfigObjects 7 } 644 pktcSigDefCallSigDscp OBJECT-TYPE 645 SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC 646 MAX-ACCESS read-write 647 STATUS current 648 DESCRIPTION 649 " The default value used in the IP header for setting the 650 Differentiated Server Code Point (DSCP) value for call 651 signaling." 652 DEFVAL { 0 } 653 ::= { pktcSigDevConfigObjects 8 } 655 pktcSigDefMediaStreamDscp OBJECT-TYPE 656 SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC 657 MAX-ACCESS read-write 658 STATUS current 659 DESCRIPTION 660 " The default value used in the IP header for setting 661 the Differentiated Server Code Point (DSCP) value for 662 media stream packets." 663 DEFVAL { 0 } 664 ::= { pktcSigDevConfigObjects 9 } 666 -- 667 -- pktcSigCapabilityTable - This table defines the valid signaling 668 -- types supported by this MTA. 669 -- 671 pktcSigCapabilityTable OBJECT-TYPE 672 SYNTAX SEQUENCE OF PktcSigCapabilityEntry 673 MAX-ACCESS not-accessible 674 STATUS current 675 DESCRIPTION 676 " This table describes the signaling types supported by this 677 MTA." 678 ::= { pktcSigDevConfigObjects 10 } 680 pktcSigCapabilityEntry OBJECT-TYPE 681 SYNTAX PktcSigCapabilityEntry 682 MAX-ACCESS not-accessible 683 STATUS current 684 DESCRIPTION 685 " Entries in pktcMtaDevSigCapabilityTable - List of 686 supported signaling types, versions and vendor extensions 687 for this MTA. Each entry in the list provides for one 688 signaling type and version combination. If the device 689 supports multiple versions of the same signaling type it 690 will require multiple entries." 691 INDEX { pktcSignalingIndex } 692 ::= { pktcSigCapabilityTable 1 } 694 PktcSigCapabilityEntry ::= SEQUENCE { 695 pktcSignalingIndex Unsigned32, 696 pktcSignalingType PktcSigType, 697 pktcSignalingVersion SnmpAdminString, 698 pktcSignalingVendorExtension SnmpAdminString 699 } 701 pktcSignalingIndex OBJECT-TYPE 702 SYNTAX Unsigned32 (1..255) 703 MAX-ACCESS not-accessible 704 STATUS current 705 DESCRIPTION 706 " The index value which uniquely identifies an entry in the 707 pktcSigCapabilityTable." 708 ::= { pktcSigCapabilityEntry 1 } 710 pktcSignalingType OBJECT-TYPE 711 SYNTAX PktcSigType 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 " This object identifies the type of signaling used. This 716 value has to be associated with a single signaling 717 version." 718 ::= { pktcSigCapabilityEntry 2 } 720 pktcSignalingVersion OBJECT-TYPE 721 SYNTAX SnmpAdminString 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 " Provides the version of the signaling type - reference 726 pktcSignalingType. Examples would be 1.0 or 2.33 etc." 727 ::= { pktcSigCapabilityEntry 3 } 729 pktcSignalingVendorExtension OBJECT-TYPE 730 SYNTAX SnmpAdminString 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 " The vendor extension allows vendors to provide a list of 735 additional capabilities, vendors can decide how to encode 736 these extensions, although space separated text is 737 suggested." 738 ::= { pktcSigCapabilityEntry 4 } 740 pktcSigDefNcsReceiveUdpPort OBJECT-TYPE 741 SYNTAX InetPortNumber (1025..65535) 742 MAX-ACCESS read-only 743 STATUS current 744 DESCRIPTION 745 " This object contains the MTA User Datagram Protocol (UDP) 746 receive port that is being used for NCS call signaling. 747 This object should only be changed by the configuration 748 file." 749 REFERENCE 750 "Refer to the IPCablecom/PacketCable NCS Specification." 751 DEFVAL { 2427 } 752 ::= { pktcSigDevConfigObjects 11 } 754 pktcSigServiceClassNameUS OBJECT-TYPE 755 SYNTAX SnmpAdminString (SIZE (0..15)) 756 MAX-ACCESS read-write 757 STATUS current 758 DESCRIPTION 759 " This object contains a string indicating the Service 760 Class Name to create an Upstream Service Flow for NCS. 761 If the object has an empty string value then the NCS SF 762 is not created and the best effort primary SF is used for 763 NCS data. If this object is set to a non-empty (non-zero 764 length) string, an MTA MUST create the NCS SF if it does 765 not currently exist and the pktcSigServiceClassNameMask 766 object has a non-zero value. If this object is 767 subsequently set to an empty (zero-length) string , an 768 MTA MUST delete the NCS SF if it exists. Setting this 769 object to a different value does not cause the US SF to 770 be re-created. The string MUST contain printable ASCII 771 characters. The length of the string does not include a 772 terminating zero. The MTA MUST append a terminating zero 773 when the MTA creates the service flow." 774 DEFVAL { "" } 775 ::= { pktcSigDevConfigObjects 12 } 777 pktcSigServiceClassNameDS OBJECT-TYPE 778 SYNTAX SnmpAdminString (SIZE (0..15)) 779 MAX-ACCESS read-write 780 STATUS current 781 DESCRIPTION 782 " This object contains a string indicating the Service 783 Class Name to create a Downstream Service Flow for NCS. 784 If the object has an empty string value then the NCS SF 785 is not created and the best effort primary SF is used for 786 NCS data. If this object is set to a non-empty (non-zero 787 length) string, an MTA MUST create the NCS SF if it does 788 not currently exist and the pktcSigServiceClassNameMask 789 object has a non-zero value. If this object is 790 subsequently set to an empty (zero-length) string , an 791 MTA MUST delete the NCS SF if it exists. Setting this 792 object to a different value does not cause the DS SF to 793 be re-created. The string MUST contain printable ASCII 794 characters. The length of the string does not include a 795 terminating zero. The MTA MUST append a terminating zero 796 when the MTA creates the service flow." 797 DEFVAL { "" } 798 ::= { pktcSigDevConfigObjects 13 } 800 pktcSigServiceClassNameMask OBJECT-TYPE 801 SYNTAX Integer32 802 MAX-ACCESS read-write 803 STATUS current 804 DESCRIPTION 805 " This object contains a value used for the NCS Call 806 Signaling classifier mask. If this object is set to a 807 zero value, an MTA MUST delete both NCS SFs. When 808 this object is set to a non-zero value, an MTA MUST 809 create the NCS SF for which the corresponding MIB object 810 (pktcSigServiceClassNameUS or pktcSigServiceClassNameDS) 811 has a non-empty value, if the NCS SF does not already 812 exist." 813 DEFVAL { 0 } 814 ::= { pktcSigDevConfigObjects 14 } 816 pktcSigNcsServiceFlowState OBJECT-TYPE 817 SYNTAX INTEGER { 818 notactive (1), 819 active (2), 820 error (3) 821 } 822 MAX-ACCESS read-only 823 STATUS current 824 DESCRIPTION 825 "This object contains a status value of the Call Signaling 826 Service Flow. 827 - notactive indicates that the NCS SF is not being used, 828 and has not tried to be created, 829 - active indicates that the NCS SF is in use, 830 - error indicates that the NCS SF creation resulted in 831 an error and the best effort channel is used for NCS 832 Signaling." 833 ::= { pktcSigDevConfigObjects 15 } 835 pktcSigDevR1Cadence OBJECT-TYPE 836 SYNTAX PktcRingCadence 837 MAX-ACCESS read-write 838 STATUS current 839 DESCRIPTION 840 " This object specifies ring cadence 1 (a user defined 841 field) where each bit represents a duration of 100 842 milliseconds (6 seconds total), except the LSB 4 bits 843 which are used to represent repeatable characteristics." 844 DEFVAL {{ interval1, interval2, interval3, interval4, interval5, 845 interval6, interval7, interval8, interval9, 846 interval10, interval11, interval12, interval13, 847 interval14, interval15, interval16, interval17, 848 interval18, interval19, interval20 }} 849 -- 11111111111111111111000000000000000000000000000000000000000 850 -- 00000 851 ::= { pktcSigDevConfigObjects 16 } 853 pktcSigDevR2Cadence OBJECT-TYPE 854 SYNTAX PktcRingCadence 855 MAX-ACCESS read-write 856 STATUS current 857 DESCRIPTION 858 " This object specifies ring cadence 2 (a user defined 859 field) where each bit represents a duration of 100 860 milliseconds (6 seconds total), except the LSB 4 bits 861 which are used to represent repeatable characteristics." 862 DEFVAL {{ interval1, interval2, interval3, interval4, interval5, 863 interval6, interval7, interval8, interval13, 864 interval14, interval15, interval16, interval17, 865 interval18, interval19, interval20 }} 866 -- 11111111000011111111000000000000000000000000000000000000000 867 -- 00000 868 ::= { pktcSigDevConfigObjects 17 } 870 pktcSigDevR3Cadence OBJECT-TYPE 871 SYNTAX PktcRingCadence 872 MAX-ACCESS read-write 873 STATUS current 874 DESCRIPTION 875 " This object specifies ring cadence 3 (a user defined 876 field) where each bit represents a duration of 100 877 milliseconds (6 seconds total), except the LSB 4 bits 878 which are used to represent repeatable characteristics." 879 DEFVAL {{ interval1, interval2, interval3, interval4, interval7, 880 interval8, interval9, interval10, interval13, 881 interval14, interval15, interval16, interval17, 882 interval18, interval19, interval20 }} 883 -- 11110011110011111111000000000000000000000000000000000000000 884 -- 00000 885 ::= { pktcSigDevConfigObjects 18 } 887 pktcSigDevR4Cadence OBJECT-TYPE 888 SYNTAX PktcRingCadence 889 MAX-ACCESS read-write 890 STATUS current 891 DESCRIPTION 892 " This object specifies ring cadence 4 (a user defined 893 field) where each bit represents a duration of 100 894 milliseconds (6 seconds total), except the LSB 4 bits 895 which are used to represent repeatable characteristics." 896 DEFVAL {{ interval1, interval2, interval3, interval6, interval7, 897 interval8, interval9, interval10, interval11, 898 interval12, interval13, interval14, interval15, 899 interval18, interval19, interval20 }} 900 -- 11100111111111100111000000000000000000000000000000000000000 901 -- 00000 902 ::= { pktcSigDevConfigObjects 19 } 904 pktcSigDevR5Cadence OBJECT-TYPE 905 SYNTAX PktcRingCadence 906 MAX-ACCESS read-write 907 STATUS current 908 DESCRIPTION 909 " This object specifies ring cadence 5 (a user defined 910 field) where each bit represents a duration of 100 911 milliseconds, except the LSB 4 bits which are used to 912 represent repeatable characteristics." 913 DEFVAL {{ interval1, interval2, interval3, interval4, interval5, 914 repeat1 }} 915 -- 11111000000000000000000000000000000000000000000000000000000 916 -- 01000 917 ::= { pktcSigDevConfigObjects 20 } 919 pktcSigDevRgCadence OBJECT-TYPE 920 SYNTAX PktcRingCadence 921 MAX-ACCESS read-write 922 STATUS current 923 DESCRIPTION 924 " This object specifies ring cadence rg (a user defined 925 field) where each bit represents a duration of 100 926 milliseconds (6 seconds total), except the LSB 4 bits 927 which are used to represent repeatable characteristics." 928 DEFVAL {{ interval1, interval2, interval3, interval4, interval5, 929 interval6, interval7, interval8, interval9, 930 interval10, interval11, interval12, interval13, 931 interval14, interval15, interval16, interval17, 932 interval18, interval19, interval20 } } 933 -- 11111111111111111111000000000000000000000000000000000000000 934 -- 00000 935 ::= { pktcSigDevConfigObjects 21 } 937 pktcSigDevRsCadence OBJECT-TYPE 938 SYNTAX PktcRingCadence 939 MAX-ACCESS read-write 940 STATUS current 941 DESCRIPTION 942 " This object specifies ring cadence rs (a user defined 943 field) where each bit represents a duration of 100 944 milliseconds (6 seconds total), except the LSB 4 bits 945 which are used to represent repeatable characteristics. 946 The MTA MUST reject any attempt to make this object 947 repeatable." 948 DEFVAL {{ interval1, interval2, interval3, interval4, interval5, 949 repeat1 }} 950 -- 11111000000000000000000000000000000000000000000000000000000 951 -- 01000 952 ::= { pktcSigDevConfigObjects 22 } 954 pktcSigDevRtCadence OBJECT-TYPE 955 SYNTAX PktcRingCadence 956 MAX-ACCESS read-write 957 STATUS current 958 DESCRIPTION 959 " This object specifies ring cadence rt (a user defined 960 field) where each bit represents a duration of 100 961 milliseconds (6 seconds total), except the LSB 4 bits 962 which are used to represent repeatable characteristics." 963 DEFVAL {{ interval1, interval2, interval3, interval4, interval5, 964 interval6, interval7, interval8, interval9, 965 interval10, interval11, interval12, interval13, 966 interval14, interval15, interval16, interval17, 967 interval18, interval19, interval20 } } 968 -- 11111111111111111111000000000000000000000000000000000000000 969 -- 00000 970 ::= { pktcSigDevConfigObjects 23 } 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) 983 } 984 UNITS "Hertz" 985 MAX-ACCESS read-write 986 STATUS current 987 DESCRIPTION 988 " The power ring frequency is the frequency at which the 989 sinusoidal voltage must travel down the twisted pair to 990 make terminal equipment ring. Different countries define 991 different electrical characteristics to make terminal 992 equipment ring." 993 REFERENCE 994 " Refer to EN 300 001 for a list of frequency ranges that 995 are defined for each country." 996 DEFVAL { f20Hz } 997 ::= { pktcSigDevConfigObjects 24 } 999 pktcSigPCMCoding OBJECT-TYPE 1000 SYNTAX INTEGER { 1001 aLaw(1), 1002 uLaw(2) 1003 } 1004 MAX-ACCESS read-write 1005 STATUS current 1006 DESCRIPTION 1007 " This is the Pulse Code Modulation (PCM) format used by an 1008 MTA when coding and decoding analog telephone signals." 1009 DEFVAL { aLaw } 1010 ::= { pktcSigDevConfigObjects 25 } 1012 pktcSigPulseSignalTable OBJECT-TYPE 1013 SYNTAX SEQUENCE OF PktcSigPulseSignalEntry 1014 MAX-ACCESS not-accessible 1015 STATUS current 1016 DESCRIPTION 1017 " The Pulse signal table defines the pulse signal operation. 1018 There are four types of international pulse signals, 1019 initial ring, meter pulse, reverse polarity and no 1020 battery. The Pulse duration type is specific and it is 1021 specified with a 1 to 32 value." 1022 ::= { pktcSigDevConfigObjects 26 } 1024 pktcSigPulseSignalEntry OBJECT-TYPE 1025 SYNTAX PktcSigPulseSignalEntry 1026 MAX-ACCESS not-accessible 1027 STATUS current 1028 DESCRIPTION 1029 " Unique value ranging from 1 to 32 that will correspond to 1030 the value specified by the operator." 1031 INDEX { pktcSigPulseSignalIndex } 1032 ::= { pktcSigPulseSignalTable 1 } 1034 PktcSigPulseSignalEntry ::= SEQUENCE { 1035 pktcSigPulseSignalIndex Unsigned32, 1036 pktcSigPulseSignalDuration Unsigned32, 1037 pktcSigPulseSignalType INTEGER, 1038 pktcSigPulseSignalDbLevel TenthdBm, 1039 pktcSigPulseSignalFrequency INTEGER, 1040 pktcSigPulseSignalRepeatCount Unsigned32, 1041 pktcSigPulseSignalPauseDuration Unsigned32} 1043 pktcSigPulseSignalIndex OBJECT-TYPE 1044 SYNTAX Unsigned32 (1..32) 1045 MAX-ACCESS not-accessible 1046 STATUS current 1047 DESCRIPTION 1048 " The table index equivalent to the operator specific pulse 1049 type and duration." 1050 ::= { pktcSigPulseSignalEntry 1 } 1052 pktcSigPulseSignalDuration OBJECT-TYPE 1053 SYNTAX Unsigned32 (1..5000) 1054 UNITS "Milliseconds" 1055 MAX-ACCESS read-write 1056 STATUS current 1057 DESCRIPTION 1058 " The pulse duration varies according to the operator and 1059 country." 1060 REFERENCE 1061 " Refer to the EN 300 001 Specification." 1062 DEFVAL { 1000 } 1063 ::= {pktcSigPulseSignalEntry 2 } 1065 pktcSigPulseSignalType OBJECT-TYPE 1066 SYNTAX INTEGER 1067 { 1068 initialRing(1), 1069 meterPulse(2), 1070 reversePolarity(3), 1071 noBattery(4) 1072 } 1073 MAX-ACCESS read-write 1074 STATUS current 1075 DESCRIPTION 1076 " There are four types of international pulse signals." 1077 REFERENCE 1078 " Refer to the EN 300 001 Specification." 1079 DEFVAL { initialRing } 1080 ::= { pktcSigPulseSignalEntry 3 } 1082 pktcSigPulseSignalDbLevel OBJECT-TYPE 1083 SYNTAX TenthdBm (-250..150) 1084 UNITS "dbm" 1085 MAX-ACCESS read-write 1086 STATUS current 1087 DESCRIPTION 1088 " This object only applies if pktcSigPulseSignalType = 1089 meterPulse. This is the decibel level at which the meter 1090 pulse could be generated. Example: 1091 pktcSigPulseSignalType pktcSigPulseSignalDbLevel 1092 initialRing 0 (not used) 1093 meterPulse -135 1094 reversePolarity 0 (not used) 1095 noBattery 0 (not used)" 1096 REFERENCE 1097 " Refer to the EN 300 001 Specification." 1098 DEFVAL { -135 } 1099 ::={pktcSigPulseSignalEntry 4 } 1101 pktcSigPulseSignalFrequency OBJECT-TYPE 1102 SYNTAX INTEGER { 1103 zero (1), 1104 fifty(2), 1105 twelvethousand(3), 1106 sixteenthousand(4) 1107 } 1108 UNITS "Hertz" 1109 MAX-ACCESS read-write 1110 STATUS current 1111 DESCRIPTION 1112 " This object only applies if pktcSigPulseSignalType = 1113 meterPulse. This is the frequency at which the meter pulse 1114 could be generated. Example: 1115 pktcSigPulseSignalType pktcSigPulseSignalDbLevel 1116 initialRing zero (not used) 1117 meterPulse fifty 1118 reversePolarity zero (not used) 1119 noBattery zero (not used)" 1120 REFERENCE 1121 " Refer to the EN 300 001 Specification." 1122 DEFVAL { fifty } 1123 ::= { pktcSigPulseSignalEntry 5} 1125 pktcSigPulseSignalRepeatCount OBJECT-TYPE 1126 SYNTAX Unsigned32 (0..5000) 1127 MAX-ACCESS read-write 1128 STATUS current 1129 DESCRIPTION 1130 " This is the repeat count, which signifies how many times 1131 to repeat the pulse." 1132 ::={ pktcSigPulseSignalEntry 6 } 1134 pktcSigPulseSignalPauseDuration OBJECT-TYPE 1135 SYNTAX Unsigned32 (1..5000) 1136 UNITS "Milliseconds" 1137 MAX-ACCESS read-write 1138 STATUS current 1139 DESCRIPTION 1140 " The pause duration between pulses varies according to the 1141 operator and country." 1142 ::= { pktcSigPulseSignalEntry 7 } 1144 pktcSigDevCIDMode OBJECT-TYPE 1145 SYNTAX INTEGER { 1146 duringRingingETS(1), 1147 dtAsETS(2), 1148 rpAsETS(3), 1149 lrAsETS(4) 1150 } 1151 MAX-ACCESS read-write 1152 STATUS current 1153 DESCRIPTION 1154 " This object is used for ETSI systems only. For on-hook 1155 Caller ID, pktcSigDevCIDMode selects the method of Caller 1156 ID. For the duringRingingETS method, the FSK containing 1157 the Caller ID information is sent between the first and 1158 second ring pattern. For the dtAsETS, rpAsETS, and lrAsETS 1159 methods, the FSK containing the Caller ID information is 1160 sent before the first ring pattern. For the dtAsETS 1161 method, the FSK is sent after the Dual Tone Alert Signal. 1162 For the rpAsETS method, the FSK is sent after a Ring 1163 Pulse. For the lrAsETS method, the Line Reversal occurs 1164 first, then the Dual Tone Alert Signal, and finally the 1165 FSK is sent." 1166 DEFVAL { dtAsETS } 1167 ::= {pktcSigDevConfigObjects 27 } 1169 pktcSigDevCIDFskAfterRing OBJECT-TYPE 1170 SYNTAX Unsigned32 (0..2000) 1171 UNITS "Milliseconds" 1172 MAX-ACCESS read-write 1173 STATUS current 1174 DESCRIPTION 1175 " This object is used for ETSI systems only. This object 1176 specifies the delay between the end of first ringing 1177 pattern and the start of the transmission of the FSK 1178 containing the Caller ID information. It is only used when 1179 pktcSigDevCIDMode is duringRingingETS. 1180 pktcSigDevCIDMode pktcSigDevCIDFskAfterRing 1181 duringringingETS 550 ms 1182 dtAsETS 0 ms (not used) 1183 rpAsETS 0 ms (not used) 1184 lrAsETS 0 ms (not used)" 1185 REFERENCE 1186 " Refer to the ETS 300 659-1 Specification." 1187 DEFVAL { 550 } 1188 ::= {pktcSigDevConfigObjects 28 } 1190 pktcSigDevCIDFskAfterDTAS OBJECT-TYPE 1191 SYNTAX Unsigned32 (0..500) 1192 UNITS "Milliseconds" 1193 MAX-ACCESS read-write 1194 STATUS current 1195 DESCRIPTION 1196 " This object is used for ETSI systems only. This object 1197 specifies the delay between the end of the Dual Tone Alert 1198 Signal (DT-AS) and the start of the transmission of the 1199 FSK containing the Caller ID information. This object is 1200 only used when pktcSigDevCIDMode is dtAsETS or lrAsETS. 1201 pktcSigDevCIDMode pktcSigDevCIDFskAfterDTAS 1202 duringringingETS 0 ms (not used) 1203 dtAsETS 50 ms 1204 rpAsETS 0 ms (not used) 1205 lrAsETS 50 ms" 1206 REFERENCE 1207 " Refer to the ETS 300 659-1 Specification." 1208 DEFVAL { 50 } 1209 ::= {pktcSigDevConfigObjects 29 } 1211 pktcSigDevCIDRingAfterFSK OBJECT-TYPE 1212 SYNTAX Unsigned32 (0..500) 1213 UNITS "Milliseconds" 1214 MAX-ACCESS read-write 1215 STATUS current 1216 DESCRIPTION 1217 " This object is used for ETSI systems only. This object 1218 specifies the delay between the end of the complete 1219 transmission of the FSK containing the Caller ID 1220 information and the start of the first ring pattern. It is 1221 only used when pktcSigDevCIDMode is dtAsETS, rpAsETS or 1222 lrAsETS. 1224 pktcSigDevCIDMode pktcSigDevCIDFskAfterFSK 1225 duringringingETS 0 ms (not used) 1226 dtAsETS 250 ms 1227 rpAsETS 250 ms 1228 lrAsETS 250 ms" 1229 REFERENCE 1230 " Refer to the ETS 300 659-1 Specification." 1231 DEFVAL { 250 } 1232 ::= {pktcSigDevConfigObjects 30 } 1234 pktcSigDevCIDDTASAfterLR OBJECT-TYPE 1235 SYNTAX Unsigned32 (0..655) 1236 UNITS "Milliseconds" 1237 MAX-ACCESS read-write 1238 STATUS current 1239 DESCRIPTION 1240 " This object is used for ETSI systems only. This object 1241 specifies the delay between the end of the Line Reversal 1242 and the start of the Dual Tone Alert Signal (DT-AS). This 1243 object is only used when pktcSigDevCIDMode is lrAsETS. 1244 pktcSigDevCIDMode pktcSigDevCIDFskAfterLR 1245 duringringingETS 0 ms (not used) 1246 dtAsETS 0 ms (not used) 1247 rpAsETS 0 ms (not used) 1248 lrAsETS 250 ms" 1249 REFERENCE 1250 " Refer to the ETS 300 659-1 Specification." 1251 DEFVAL { 250 } 1253 ::= {pktcSigDevConfigObjects 31 } 1255 pktcSigDevRingCadenceTable OBJECT-TYPE 1256 SYNTAX SEQUENCE OF PktcSigDevRingCadenceEntry 1257 MAX-ACCESS not-accessible 1258 STATUS current 1259 DESCRIPTION 1260 " In V5.2, Cadence rings are defined by the telco governing 1261 body for each country. The MTA must be able to support 1262 various ranges of cadence patterns and cadence periods. 1263 The MTA will be able to support country specific 1264 provisioning of the cadence and idle period. There will be 1265 at most 3 on/off transitions per cadence period. Each 1266 cadence pattern will be assigned a unique value ranging 1267 from 1-128 corresponding to the value sent by the LE 1268 SIGNAL message plus one. The MTA will derive the cadence 1269 periods from the ring Cadence table entry as provisioned 1270 by the customer." 1271 ::= { pktcSigDevConfigObjects 32 } 1273 pktcSigDevRingCadenceEntry OBJECT-TYPE 1274 SYNTAX PktcSigDevRingCadenceEntry 1275 MAX-ACCESS not-accessible 1276 STATUS current 1277 DESCRIPTION 1278 " Unique value ranging from 1 to 128 that corresponds to the 1279 value sent by the LE (plus one) based on country specific 1280 cadences, one row per cadence cycle. In any given system 1281 implementation for a particular country, it is anticipated 1282 that a small number of ring cadences will be in use. Thus, 1283 this table most likely will not be populated to its full 1284 128-row size." 1285 INDEX { pktcSigDevRingCadenceIndex } 1286 ::= { pktcSigDevRingCadenceTable 1 } 1288 PktcSigDevRingCadenceEntry ::= SEQUENCE { 1289 pktcSigDevRingCadenceIndex Unsigned32, 1290 pktcSigDevRingCadence OCTET STRING 1291 } 1293 pktcSigDevRingCadenceIndex OBJECT-TYPE 1294 SYNTAX Unsigned32 (1..128) 1295 MAX-ACCESS not-accessible 1296 STATUS current 1297 DESCRIPTION 1298 " The table index equivalent to the country specific cadence 1299 (1 - 128)." 1300 ::= { pktcSigDevRingCadenceEntry 1 } 1302 pktcSigDevRingCadence OBJECT-TYPE 1303 SYNTAX OCTET STRING (SIZE(2..28)) 1304 MAX-ACCESS read-write 1305 STATUS current 1306 DESCRIPTION 1307 " This is the Ring Cadence Octet String. The first octet of 1308 the bit string represents the length in bits of the 1309 duration of the cadence. Each Bit after the first octet 1310 represents 50 ms and 1 represents ring and 0 represents 1311 silent. The first bit of the second octet is the first bit 1312 of the ring cadence. Only 216 Bits can be set total to 1313 represent 10800 ms of total cadence cycle." 1314 ::= { pktcSigDevRingCadenceEntry 2 } 1316 pktcSigDevStandardRingCadence OBJECT-TYPE 1317 SYNTAX OCTET STRING (SIZE(2..28)) 1318 MAX-ACCESS read-write 1319 STATUS current 1320 DESCRIPTION 1321 " This is the Ring Cadence Octet String for the standard 1322 ring. The first octet of the bit string represents the 1323 length in bits of the duration of the cadence Each Bit 1324 after the first octet represents 50 ms and 1 represents 1325 ring and 0 represents silent. The first bit of the second 1326 octet is the first bit of the ring cadence. Only 216 Bits 1327 can be set total to represent 10800 ms of total cadence 1328 cycle." 1329 ::= { pktcSigDevConfigObjects 33 } 1331 pktcSigDevRingSplashCadence OBJECT-TYPE 1332 SYNTAX OCTET STRING (SIZE(2..28)) 1333 MAX-ACCESS read-write 1334 STATUS current 1335 DESCRIPTION 1336 " This is the Ring Cadence Octet String for splash ring. The 1337 first octet of the bit string represents the length in 1338 bits of the duration of the cadence. Each Bit after the 1339 first octet represents 50 ms and 1 represents ring and 0 1340 represents silent. The first bit of the second octet is 1341 the first bit of the ring cadence. Only 216 Bits can be 1342 set total to represent 10800 ms of total cadence cycle." 1343 ::= { pktcSigDevConfigObjects 34 } 1345 pktcSigDevToneTable OBJECT-TYPE 1346 SYNTAX SEQUENCE OF PktcSigDevToneEntry 1347 MAX-ACCESS not-accessible 1348 STATUS current 1349 DESCRIPTION 1350 " The Tone Table defines the various tone operations." 1351 ::= { pktcSigDevConfigObjects 35 } 1353 pktcSigDevToneEntry OBJECT-TYPE 1354 SYNTAX PktcSigDevToneEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 " Unique value ranging from 1 to 49 that will correspond to 1359 the different tone types that are being supported by the 1360 device. These tones can be provisioned based on country 1361 specific needs." 1362 INDEX { pktcSigDevToneType } 1363 ::= { pktcSigDevToneTable 1 } 1365 PktcSigDevToneEntry ::= SEQUENCE { 1366 pktcSigDevToneType INTEGER, 1367 pktcSigDevToneDbLevel Integer32, 1368 pktcSigDevToneFreqType INTEGER, 1369 pktcSigDevToneNumFrequencies Unsigned32, 1370 pktcSigDevToneFirstFrequency Unsigned32, 1371 pktcSigDevToneSecondFrequency Unsigned32, 1372 pktcSigDevToneThirdFrequency Unsigned32, 1373 pktcSigDevToneFourthFrequency Unsigned32, 1374 pktcSigDevToneNumOnOffTimes Unsigned32, 1375 pktcSigDevToneFirstToneOn Unsigned32, 1376 pktcSigDevToneFirstToneOff Unsigned32, 1377 pktcSigDevToneSecondToneOn Unsigned32, 1378 pktcSigDevToneSecondToneOff Unsigned32, 1379 pktcSigDevToneThirdToneOn Unsigned32, 1380 pktcSigDevToneThirdToneOff Unsigned32, 1381 pktcSigDevToneFourthToneOn Unsigned32, 1382 pktcSigDevToneFourthToneOff Unsigned32, 1383 pktcSigDevToneWholeToneRepeatCount Unsigned32, 1384 pktcSigDevToneSteady TruthValue 1385 } 1387 pktcSigDevToneType OBJECT-TYPE 1388 SYNTAX INTEGER { 1389 dtmf0(0), 1390 dtmf1(1), 1391 dtmf2(2), 1392 dtmf3(3), 1393 dtmf4(4), 1394 dtmf5(5), 1395 dtmf6(6), 1396 dtmf7(7), 1397 dtmf8(8), 1398 dtmf9(9), 1399 dtmfToneStar(10), 1400 dtmfTonePound(11), 1401 dtmfA(12), 1402 dtmfB(13), 1403 dtmfC(14), 1404 dtmfD(15), 1405 busy(16), 1406 confirmation(17), 1407 dial(18), 1408 messageWaiting(19), 1409 offHookWarning(20), 1410 ringBack(21), 1411 reOrder(22), 1412 stutterdial(23), 1413 loopback(24), 1414 callWaiting1(25), 1415 callWaiting2(26), 1416 callWaiting3(27), 1417 callWaiting4(28), 1418 alertingSignal(29), 1419 testTone(30), 1420 specialDial(31), 1421 specialInfo(32), 1422 release(33), 1423 congestion(34), 1424 userDefinedOne(35) 1425 } 1426 MAX-ACCESS read-only 1427 STATUS current 1428 DESCRIPTION 1429 " This object defines the type of tone being accessed. Note: 1430 the values are enumerated starting at zero (e.g., dtmf0) 1431 to correspond to the digits on the telephone keypad." 1432 ::={pktcSigDevToneEntry 1 } 1434 pktcSigDevToneDbLevel OBJECT-TYPE 1435 SYNTAX Integer32 (-60..4) 1436 UNITS "dbm" 1437 MAX-ACCESS read-write 1438 STATUS current 1439 DESCRIPTION 1440 " This is the decibel level at which tones could be 1441 generated." 1442 DEFVAL { -4 } 1443 ::={pktcSigDevToneEntry 2 } 1445 pktcSigDevToneFreqType OBJECT-TYPE 1446 SYNTAX INTEGER { 1447 allFrequencies (1), 1448 singleFrequecySequence (2), 1449 dualFrequencySequence (3), 1450 allFrequenciesModulated (4) 1451 } 1452 MAX-ACCESS read-write 1453 STATUS current 1454 DESCRIPTION 1455 " This object describes how the frequencies are applied. 1456 allFrequencies indicates all frequences specifed by 1457 pktcSigDevToneNumFrequencies are mixed to form a single 1458 tone. The tone is then applied in sequence using the 1459 number of on/off times specified in 1460 pktcSigDevToneNumOnOffTimes. SingleFrequecySequence 1461 indicates all frequencies specified by 1462 pktcSigDevToneNumFrequencies are applied in sequence 1463 using the corresponding frequency number on/off time 1464 (e.g., pktcSigDevToneFirstFrequency uses 1465 pktcSigDevToneFirstToneOn and pktcSigDevToneFirstToneOff, 1466 pktcSigDevToneSecondFrequency uses 1467 pktcSigDevToneSecondToneOn and 1468 pktcSigDevToneSecondToneOff). For this tone type 1469 pktcSigDevToneNumFrequencies MUST equal 1470 pktcSigDevToneNumOnOffTimes. DualFrequencySequence 1471 indicates two pairs of frequencies are mixed to form two 1472 sequenced tones. The first and second frequency are mixed 1473 to form tone one and are applied using 1474 pktcSigDevToneFirstToneOn and pktcSigDevToneFirstToneOff. 1475 The third and forth frequency are mixed to form tone two 1476 and are applied using pktcSigDevToneSecondToneOn and 1477 pktcSigDevToneSecondToneOff. For this tone type 1478 pktcSigDevToneNumFrequencies MUST equal 4 and 1479 pktcSigDevToneNumOnOffTimes MUST equal 2. 1480 allFrequenciesModulated indicates all frequencies 1481 specified by pktcSigDevToneNumFrequencies are modulated to 1482 form a single tone. The tone is then applied in sequence 1483 using the number of on/off times specified in 1484 pktcSigDevToneNumOnOffTimes." 1485 DEFVAL { allFrequencies } 1486 ::={ pktcSigDevToneEntry 3 } 1488 pktcSigDevToneNumFrequencies OBJECT-TYPE 1489 SYNTAX Unsigned32 (1..4) 1490 MAX-ACCESS read-write 1491 STATUS current 1492 DESCRIPTION 1493 " Specifies the number of frequencies specified in the table 1494 entry." 1495 DEFVAL { 1 } 1496 ::={pktcSigDevToneEntry 4} 1498 pktcSigDevToneFirstFrequency OBJECT-TYPE 1499 SYNTAX Unsigned32 (0..4000) 1500 UNITS "Hertz" 1501 MAX-ACCESS read-write 1502 STATUS current 1503 DESCRIPTION 1504 " This is the first frequency at which the tones could be 1505 generated in a multiple frequency tone." 1506 ::={pktcSigDevToneEntry 5} 1508 pktcSigDevToneSecondFrequency OBJECT-TYPE 1509 SYNTAX Unsigned32 (0..4000) 1510 UNITS "Hertz" 1511 MAX-ACCESS read-write 1512 STATUS current 1513 DESCRIPTION 1514 " This is the second frequency at which the tones could be 1515 generated in a multiple frequency tone." 1516 ::={pktcSigDevToneEntry 6} 1518 pktcSigDevToneThirdFrequency OBJECT-TYPE 1519 SYNTAX Unsigned32 (0..4000) 1520 UNITS "Hertz" 1521 MAX-ACCESS read-write 1522 STATUS current 1523 DESCRIPTION 1524 " This is the third frequency at which the tones could be 1525 generated." 1526 ::={pktcSigDevToneEntry 7} 1528 pktcSigDevToneFourthFrequency OBJECT-TYPE 1529 SYNTAX Unsigned32 (0..4000) 1530 UNITS "Hertz" 1531 MAX-ACCESS read-write 1532 STATUS current 1533 DESCRIPTION 1534 " This is the fourth frequency at which the tones could be 1535 generated." 1536 ::={pktcSigDevToneEntry 8} 1538 pktcSigDevToneNumOnOffTimes OBJECT-TYPE 1539 SYNTAX Unsigned32 (1..4) 1540 MAX-ACCESS read-write 1541 STATUS current 1542 DESCRIPTION 1543 " Specifies the number of on/off times specified in the 1544 table entry." 1545 DEFVAL { 1 } 1546 ::={pktcSigDevToneEntry 9} 1548 pktcSigDevToneFirstToneOn OBJECT-TYPE 1549 SYNTAX Unsigned32 (0..5000) 1550 UNITS "Milliseconds" 1551 MAX-ACCESS read-write 1552 STATUS current 1553 DESCRIPTION 1554 " This is the first tone interval." 1555 ::={ pktcSigDevToneEntry 10} 1557 pktcSigDevToneFirstToneOff OBJECT-TYPE 1558 SYNTAX Unsigned32 (0..5000) 1559 UNITS "Milliseconds" 1560 MAX-ACCESS read-write 1561 STATUS current 1562 DESCRIPTION 1563 " This is the first idle interval." 1564 ::={ pktcSigDevToneEntry 11 } 1566 pktcSigDevToneSecondToneOn OBJECT-TYPE 1567 SYNTAX Unsigned32 (0..5000) 1568 UNITS "Milliseconds" 1569 MAX-ACCESS read-write 1570 STATUS current 1571 DESCRIPTION 1572 " This is the second tone interval." 1573 ::={ pktcSigDevToneEntry 12 } 1575 pktcSigDevToneSecondToneOff OBJECT-TYPE 1576 SYNTAX Unsigned32 (0..5000) 1577 UNITS "Milliseconds" 1578 MAX-ACCESS read-write 1579 STATUS current 1580 DESCRIPTION 1581 " This is the second idle interval." 1582 ::={ pktcSigDevToneEntry 13 } 1584 pktcSigDevToneThirdToneOn OBJECT-TYPE 1585 SYNTAX Unsigned32 (0..5000) 1586 UNITS "Milliseconds" 1587 MAX-ACCESS read-write 1588 STATUS current 1589 DESCRIPTION 1590 " This is the third tone interval." 1591 ::={ pktcSigDevToneEntry 14 } 1593 pktcSigDevToneThirdToneOff OBJECT-TYPE 1594 SYNTAX Unsigned32 (0..5000) 1595 UNITS "Milliseconds" 1596 MAX-ACCESS read-write 1597 STATUS current 1598 DESCRIPTION 1599 " This is the third idle interval." 1600 ::={ pktcSigDevToneEntry 15 } 1602 pktcSigDevToneFourthToneOn OBJECT-TYPE 1603 SYNTAX Unsigned32 (0..5000) 1604 UNITS "Milliseconds" 1605 MAX-ACCESS read-write 1606 STATUS current 1607 DESCRIPTION 1608 " This is the fourth tone interval." 1609 ::={ pktcSigDevToneEntry 16 } 1611 pktcSigDevToneFourthToneOff OBJECT-TYPE 1612 SYNTAX Unsigned32 (0..5000) 1613 UNITS "Milliseconds" 1614 MAX-ACCESS read-write 1615 STATUS current 1616 DESCRIPTION 1617 " This is the Fourth idle interval." 1618 ::={ pktcSigDevToneEntry 17 } 1620 pktcSigDevToneWholeToneRepeatCount OBJECT-TYPE 1621 SYNTAX Unsigned32 (0..5000) 1622 MAX-ACCESS read-write 1623 STATUS current 1624 DESCRIPTION 1625 " This is the repeat count, which signifies how many times 1626 to repeat the entire on-off sequence." 1627 ::={ pktcSigDevToneEntry 18 } 1629 pktcSigDevToneSteady OBJECT-TYPE 1630 SYNTAX TruthValue 1631 MAX-ACCESS read-write 1632 STATUS current 1633 DESCRIPTION 1634 " This is the steady tone. Set to true to continue the 1635 last tone after on-off sequence." 1636 ::={ pktcSigDevToneEntry 19 } 1638 -- 1639 -- The following Table provides endpoint configuration information 1640 -- that is common to all signaling Protocols. Currently only the 1641 -- signaling index is present in an effort not to deprecate any MIB 1642 -- objects. 1643 -- 1645 pktcSigEndPntConfigTable OBJECT-TYPE 1646 SYNTAX SEQUENCE OF PktcSigEndPntConfigEntry 1647 MAX-ACCESS not-accessible 1648 STATUS current 1649 DESCRIPTION 1650 " This table describes the PacketCable endpoint selected 1651 signaling type. The number of entries in this table 1652 represents the number of provisioned endpoints. 1653 For each conceptual row of pktcSigEndPntConfigTable 1654 defined, an associated row MUST be defined in one on the 1655 specific signaling tables such as 1656 pktcNcsEndPntConfigTable." 1657 ::= { pktcSigEndPntConfigObjects 1 } 1659 pktcSigEndPntConfigEntry OBJECT-TYPE 1660 SYNTAX PktcSigEndPntConfigEntry 1661 MAX-ACCESS not-accessible 1662 STATUS current 1663 DESCRIPTION 1664 " Entries in pktcSigEndPntConfigTable - Each entry describes 1665 what signaling type a particular endpoint uses." 1666 INDEX { ifIndex } 1667 ::= { pktcSigEndPntConfigTable 1 } 1669 PktcSigEndPntConfigEntry ::= SEQUENCE { 1670 pktcSigEndPntCapabilityIndex Unsigned32 1671 } 1673 pktcSigEndPntCapabilityIndex OBJECT-TYPE 1674 SYNTAX Unsigned32 (1..255) 1675 MAX-ACCESS read-create 1676 STATUS current 1677 DESCRIPTION 1678 " The associated index value in the pktcSigCapablityTable." 1679 ::= { pktcSigEndPntConfigEntry 1 } 1681 -- 1682 -- The NCS End Point Config Table is used to define attributes that 1683 -- are specific to connection EndPoints. 1684 -- 1686 pktcNcsEndPntConfigTable OBJECT-TYPE 1687 SYNTAX SEQUENCE OF PktcNcsEndPntConfigEntry 1688 MAX-ACCESS not-accessible 1689 STATUS current 1690 DESCRIPTION 1691 " This table describes the PacketCable NCS EndPoint 1692 selected signaling type. The number of entries in this 1693 table represents the number of provisioned endpoints. 1694 For each conceptual row of pktcSigEndPntConfigTable 1695 Defined, an associated row MUST be defined in one of 1696 The specific signaling tables such as the 1697 PktcNcsEndPntConfigTable." 1698 ::= { pktcNcsEndPntConfigObjects 1 } 1700 pktcNcsEndPntConfigEntry OBJECT-TYPE 1701 SYNTAX PktcNcsEndPntConfigEntry 1702 MAX-ACCESS not-accessible 1703 STATUS current 1704 DESCRIPTION 1705 " Entries in pktcNcsEndPntConfigTable � Each entry describes 1706 what signaling type a particular endpoint uses." 1707 INDEX { ifIndex } 1708 ::= { pktcNcsEndPntConfigTable 1 } 1710 PktcNcsEndPntConfigEntry ::= SEQUENCE { 1711 pktcNcsEndPntConfigCallAgentId SnmpAdminString, 1712 pktcNcsEndPntConfigCallAgentUdpPort InetPortNumber, 1713 pktcNcsEndPntConfigPartialDialTO Unsigned32, 1714 pktcNcsEndPntConfigCriticalDialTO Unsigned32, 1715 pktcNcsEndPntConfigBusyToneTO Unsigned32, 1716 pktcNcsEndPntConfigDialToneTO Unsigned32, 1717 pktcNcsEndPntConfigMessageWaitingTO Unsigned32, 1718 pktcNcsEndPntConfigOffHookWarnToneTO Unsigned32, 1719 pktcNcsEndPntConfigRingingTO Unsigned32, 1720 pktcNcsEndPntConfigRingBackTO Unsigned32, 1721 pktcNcsEndPntConfigReorderToneTO Unsigned32, 1722 pktcNcsEndPntConfigStutterDialToneTO Unsigned32, 1723 pktcNcsEndPntConfigTSMax Unsigned32, 1724 pktcNcsEndPntConfigMax1 Unsigned32, 1725 pktcNcsEndPntConfigMax2 Unsigned32, 1726 pktcNcsEndPntConfigMax1QEnable TruthValue, 1727 pktcNcsEndPntConfigMax2QEnable TruthValue, 1728 pktcNcsEndPntConfigMWD Unsigned32, 1729 pktcNcsEndPntConfigTdinit Unsigned32, 1730 pktcNcsEndPntConfigTdmin Unsigned32, 1731 pktcNcsEndPntConfigTdmax Unsigned32, 1732 pktcNcsEndPntConfigRtoMax Unsigned32, 1733 pktcNcsEndPntConfigRtoInit Unsigned32, 1734 pktcNcsEndPntConfigLongDurationKeepAlive Unsigned32, 1735 pktcNcsEndPntConfigThist Unsigned32, 1736 pktcNcsEndPntConfigStatus RowStatus, 1737 pktcNcsEndPntConfigCallWaitingMaxRep Unsigned32, 1738 pktcNcsEndPntConfigCallWaitingDelay Unsigned32, 1739 pktcNcsEndPntStatusCallIpAddressType InetAddressType, 1740 pktcNcsEndPntStatusCallIpAddress InetAddress, 1741 pktcNcsEndPntStatusError INTEGER, 1742 pktcNcsEndPntConfigMinHookFlash Unsigned32, 1743 pktcNcsEndPntConfigMaxHookFlash Unsigned32, 1744 pktcNcsEndPntConfigPulseDialInterdigitTime Unsigned32, 1745 pktcNcsEndPntConfigPulseDialMinMakeTime Unsigned32, 1746 pktcNcsEndPntConfigPulseDialMaxMakeTime Unsigned32, 1747 pktcNcsEndPntConfigPulseDialMinBreakTime Unsigned32, 1748 pktcNcsEndPntConfigPulseDialMaxBreakTime Unsigned32, 1749 pktcNcsEndPntConfigNomJitterBufferSize Unsigned32, 1750 pktcNcsEndPntConfigMaxJitterBufferSize Unsigned32, 1751 pktcNcsEndPntConfigOnHookDebounce Unsigned32, 1752 pktcNcsEndPntConfigOffHookDebounce Unsigned32, 1753 pktcNcsEndPntConfigTxGain Integer32, 1754 pktcNcsEndPntConfigRxGain Integer32 1755 } 1757 pktcNcsEndPntConfigCallAgentId OBJECT-TYPE 1758 SYNTAX SnmpAdminString(SIZE (3..255)) 1759 MAX-ACCESS read-create 1760 STATUS current 1761 DESCRIPTION 1762 " This object contains a string indicating the call agent 1763 name. (e.g.,: ca@abc.def.com). The call agent name after 1764 the @ character must be a fully qualified domain name and 1765 have a corresponding pktcMtaDevCmsFqdn entry in the 1766 pktcMtaDevCmsTable. The object pktcMtaDevCmsFqdn is 1767 defined in the PacketCable MIBMTA Specification." 1768 ::= { pktcNcsEndPntConfigEntry 1 } 1770 pktcNcsEndPntConfigCallAgentUdpPort OBJECT-TYPE 1771 SYNTAX InetPortNumber (1025..65535) 1772 MAX-ACCESS read-create 1773 STATUS current 1774 DESCRIPTION 1775 " This object contains the call agent User Datagram Protocol 1776 (UDP) receive port that is being used for this instance of 1777 call signaling, i.e. the default port on which the call 1778 agent will receive NCS signaling from the endpoint." 1779 REFERENCE 1780 " Refer to the IPCablecom/PacketCable NCS Specification." 1781 DEFVAL { 2727 } 1782 ::= { pktcNcsEndPntConfigEntry 2 } 1784 pktcNcsEndPntConfigPartialDialTO OBJECT-TYPE 1785 SYNTAX Unsigned32 1786 UNITS "seconds" 1787 MAX-ACCESS read-create 1788 STATUS current 1789 DESCRIPTION 1790 " This object contains maximum value of the partial dial 1791 time out." 1792 REFERENCE 1793 " Refer to the IPCablecom/PacketCable NCS Specification." 1794 DEFVAL { 16 } 1795 ::= { pktcNcsEndPntConfigEntry 3 } 1797 pktcNcsEndPntConfigCriticalDialTO OBJECT-TYPE 1798 SYNTAX Unsigned32 1799 UNITS "seconds" 1800 MAX-ACCESS read-create 1801 STATUS current 1802 DESCRIPTION 1803 " This object contains the maximum value of the critical 1804 dial time out." 1805 REFERENCE 1806 " Refer to the IPCablecom/PacketCable NCS Specification." 1807 DEFVAL { 4 } 1808 ::= { pktcNcsEndPntConfigEntry 4 } 1810 pktcNcsEndPntConfigBusyToneTO OBJECT-TYPE 1811 SYNTAX Unsigned32 1812 UNITS "seconds" 1813 MAX-ACCESS read-create 1814 STATUS current 1815 DESCRIPTION 1816 " This object contains the timeout value for busy tone." 1817 REFERENCE 1818 " Refer to the IPCablecom/PacketCable NCS Specification." 1819 DEFVAL { 30 } 1820 ::= { pktcNcsEndPntConfigEntry 5 } 1822 pktcNcsEndPntConfigDialToneTO OBJECT-TYPE 1823 SYNTAX Unsigned32 1824 UNITS "seconds" 1825 MAX-ACCESS read-create 1826 STATUS current 1827 DESCRIPTION 1828 " This object contains the timeout value for dial tone." 1829 REFERENCE 1830 " Refer to the IPCablecom/PacketCable NCS Specification." 1831 DEFVAL { 16 } 1832 ::= { pktcNcsEndPntConfigEntry 6 } 1834 pktcNcsEndPntConfigMessageWaitingTO OBJECT-TYPE 1835 SYNTAX Unsigned32 1836 UNITS "seconds" 1837 MAX-ACCESS read-create 1838 STATUS current 1839 DESCRIPTION 1840 " This object contains the timeout value for message waiting 1841 indicator." 1842 REFERENCE 1843 " Refer to the IPCablecom/PacketCable NCS Specification." 1844 DEFVAL { 16 } 1845 ::= { pktcNcsEndPntConfigEntry 7 } 1847 pktcNcsEndPntConfigOffHookWarnToneTO OBJECT-TYPE 1848 SYNTAX Unsigned32 1849 UNITS "seconds" 1850 MAX-ACCESS read-create 1851 STATUS current 1852 DESCRIPTION 1853 " This object contains timeout value for off hook Warning 1854 tone." 1855 REFERENCE 1856 " Refer to the IPCablecom/PacketCable NCS Specification." 1857 DEFVAL { 0 } 1858 ::= { pktcNcsEndPntConfigEntry 8 } 1860 pktcNcsEndPntConfigRingingTO OBJECT-TYPE 1861 SYNTAX Unsigned32 1862 UNITS "seconds" 1863 MAX-ACCESS read-create 1864 STATUS current 1865 DESCRIPTION 1866 " This object contains the timeout value for ringing." 1867 REFERENCE 1868 " Refer to the IPCablecom/PacketCable NCS Specification." 1869 DEFVAL { 180 } 1870 ::= { pktcNcsEndPntConfigEntry 9 } 1872 pktcNcsEndPntConfigRingBackTO OBJECT-TYPE 1873 SYNTAX Unsigned32 1874 UNITS "seconds" 1875 MAX-ACCESS read-create 1876 STATUS current 1877 DESCRIPTION 1878 " This object contains the timeout value for ring back." 1879 REFERENCE 1880 " Refer to the IPCablecom/PacketCable NCS Specification." 1881 DEFVAL { 180 } 1882 ::= { pktcNcsEndPntConfigEntry 10 } 1884 pktcNcsEndPntConfigReorderToneTO OBJECT-TYPE 1885 SYNTAX Unsigned32 1886 UNITS "seconds" 1887 MAX-ACCESS read-create 1888 STATUS current 1889 DESCRIPTION 1890 " This object contains the timeout value for reorder tone." 1891 REFERENCE 1892 " Refer to the IPCablecom/PacketCable NCS Specification." 1893 DEFVAL { 30 } 1894 ::= { pktcNcsEndPntConfigEntry 11 } 1896 pktcNcsEndPntConfigStutterDialToneTO OBJECT-TYPE 1897 SYNTAX Unsigned32 1898 UNITS "seconds" 1899 MAX-ACCESS read-create 1900 STATUS current 1901 DESCRIPTION 1902 " This object contains timeout value for stutter dial tone." 1903 REFERENCE 1904 " Refer to the IPCablecom/PacketCable NCS Specification." 1905 DEFVAL { 16 } 1906 ::= { pktcNcsEndPntConfigEntry 12 } 1908 pktcNcsEndPntConfigTSMax OBJECT-TYPE 1909 SYNTAX Unsigned32 1910 MAX-ACCESS read-create 1911 STATUS current 1912 DESCRIPTION 1913 " This object contains the max time in seconds since the 1914 sending of the initial datagram." 1915 REFERENCE 1916 " Refer to the IPCablecom/PacketCable NCS Specification." 1917 DEFVAL { 20 } 1918 ::= { pktcNcsEndPntConfigEntry 13 } 1920 pktcNcsEndPntConfigMax1 OBJECT-TYPE 1921 SYNTAX Unsigned32 1922 MAX-ACCESS read-create 1923 STATUS current 1924 DESCRIPTION 1925 " This object contains the suspicious error threshold for 1926 signaling messages." 1927 REFERENCE 1928 " Refer to the IPCablecom/PacketCable NCS Specification." 1929 DEFVAL { 5 } 1930 ::= { pktcNcsEndPntConfigEntry 14 } 1932 pktcNcsEndPntConfigMax2 OBJECT-TYPE 1933 SYNTAX Unsigned32 1934 MAX-ACCESS read-create 1935 STATUS current 1936 DESCRIPTION 1937 " This object contains the disconnect error threshold for 1938 signaling messages." 1939 REFERENCE 1940 " Refer to the IPCablecom/PacketCable NCS Specification." 1941 DEFVAL { 7 } 1942 ::= { pktcNcsEndPntConfigEntry 15 } 1944 pktcNcsEndPntConfigMax1QEnable OBJECT-TYPE 1945 SYNTAX TruthValue 1946 MAX-ACCESS read-create 1947 STATUS current 1948 DESCRIPTION 1949 " This object enables/disables the Max1 Domain Name Server 1950 (DNS) query operation when Max1 expires." 1951 DEFVAL { true } 1952 ::= { pktcNcsEndPntConfigEntry 16 } 1954 pktcNcsEndPntConfigMax2QEnable OBJECT-TYPE 1955 SYNTAX TruthValue 1956 MAX-ACCESS read-create 1957 STATUS current 1958 DESCRIPTION 1959 " This object enables/disables the Max2 DNS query operation 1960 when Max2 expires." 1961 DEFVAL { true } 1962 ::= { pktcNcsEndPntConfigEntry 17 } 1964 pktcNcsEndPntConfigMWD OBJECT-TYPE 1965 SYNTAX Unsigned32 1966 UNITS "seconds" 1967 MAX-ACCESS read-create 1968 STATUS current 1969 DESCRIPTION 1970 " Maximum Waiting Delay (MWD) contains the maximum number of 1971 seconds a MTA waits after a restart. When this timer 1972 expires the MTA initiates the restart procedure." 1973 REFERENCE 1974 " Refer to the IPCablecom/PacketCable NCS Specification." 1975 DEFVAL { 600 } 1976 ::= { pktcNcsEndPntConfigEntry 18 } 1978 pktcNcsEndPntConfigTdinit OBJECT-TYPE 1979 SYNTAX Unsigned32 1980 UNITS "seconds" 1981 MAX-ACCESS read-create 1982 STATUS current 1983 DESCRIPTION 1984 " This object contains the initial number of seconds an MTA 1985 waits after a disconnect. When this timer expires the MTA 1986 initiates the disconnected procedure." 1987 REFERENCE 1988 " Refer to the IPCablecom/PacketCable NCS Specification." 1989 DEFVAL { 15 } 1990 ::= { pktcNcsEndPntConfigEntry 19 } 1992 pktcNcsEndPntConfigTdmin OBJECT-TYPE 1993 SYNTAX Unsigned32 1994 UNITS "seconds" 1995 MAX-ACCESS read-create 1996 STATUS current 1997 DESCRIPTION 1998 " This object contains the minimum number of seconds an MTA 1999 waits after a disconnect. When this timer expires the MTA 2000 initiates the disconnected procedure." 2001 REFERENCE 2002 " Refer to the IPCablecom/PacketCable NCS Specification." 2003 DEFVAL { 15 } 2004 ::= { pktcNcsEndPntConfigEntry 20 } 2006 pktcNcsEndPntConfigTdmax OBJECT-TYPE 2007 SYNTAX Unsigned32 2008 UNITS "seconds" 2009 MAX-ACCESS read-create 2010 STATUS current 2011 DESCRIPTION 2012 " This object contains the maximum number of seconds an MTA 2013 waits after a disconnect. When this timer expires the MTA 2014 initiates the disconnected procedure. 2015 " 2016 REFERENCE 2017 " Refer to the IPCablecom/PacketCable NCS Specification." 2018 DEFVAL { 600 } 2019 ::= { pktcNcsEndPntConfigEntry 21 } 2021 pktcNcsEndPntConfigRtoMax OBJECT-TYPE 2022 SYNTAX Unsigned32 2023 UNITS "seconds" 2024 MAX-ACCESS read-create 2025 STATUS current 2026 DESCRIPTION 2027 " This object contains the maximum number of seconds for the 2028 retransmission timer. When this timer expires the MTA 2029 retransmits the message." 2030 REFERENCE 2031 " Refer to the IPCablecom/PacketCable NCS Specification." 2032 DEFVAL { 4 } 2033 ::= { pktcNcsEndPntConfigEntry 22 } 2035 pktcNcsEndPntConfigRtoInit OBJECT-TYPE 2036 SYNTAX Unsigned32 2037 UNITS "milliseconds" 2038 MAX-ACCESS read-create 2039 STATUS current 2040 DESCRIPTION 2041 " This object contains the initial number of seconds for the 2042 retransmission timer." 2043 REFERENCE 2044 " Refer to the IPCablecom/PacketCable NCS Specification." 2045 DEFVAL { 200 } 2046 ::= { pktcNcsEndPntConfigEntry 23 } 2048 pktcNcsEndPntConfigLongDurationKeepAlive OBJECT-TYPE 2049 SYNTAX Unsigned32 2050 UNITS "minutes" 2051 MAX-ACCESS read-create 2052 STATUS current 2053 DESCRIPTION 2054 " Specifies a timeout value in minutes for sending long 2055 duration call notification message." 2056 REFERENCE 2057 " Refer to the IPCablecom/PacketCable NCS Specification." 2058 DEFVAL { 60 } 2059 ::= { pktcNcsEndPntConfigEntry 24 } 2061 pktcNcsEndPntConfigThist OBJECT-TYPE 2062 SYNTAX Unsigned32 2063 UNITS "seconds" 2064 MAX-ACCESS read-create 2065 STATUS current 2066 DESCRIPTION 2067 " Timeout period in seconds before no response is declared." 2068 REFERENCE 2069 " Refer to the IPCablecom/PacketCable NCS Specification." 2070 DEFVAL { 30 } 2071 ::= { pktcNcsEndPntConfigEntry 25 } 2073 pktcNcsEndPntConfigStatus OBJECT-TYPE 2074 SYNTAX RowStatus 2075 MAX-ACCESS read-create 2076 STATUS current 2077 DESCRIPTION 2078 " This object contains the Row Status associated with the 2079 pktsNcsEndPntTable. " 2080 ::= { pktcNcsEndPntConfigEntry 26 } 2082 pktcNcsEndPntConfigCallWaitingMaxRep OBJECT-TYPE 2083 SYNTAX Unsigned32 (0..10) 2084 MAX-ACCESS read-create 2085 STATUS current 2086 DESCRIPTION 2087 " This object contains the maximum number of repetitions 2088 of the call waiting tone that the MTA will play from a 2089 single CMS request. A value of zero (0) can be used if 2090 the CMS is to control the repetitions of the call waiting 2091 tone." 2092 DEFVAL { 1 } 2093 ::= { pktcNcsEndPntConfigEntry 27 } 2095 pktcNcsEndPntConfigCallWaitingDelay OBJECT-TYPE 2096 SYNTAX Unsigned32 (1..100) 2097 UNITS "seconds" 2098 MAX-ACCESS read-create 2099 STATUS current 2100 DESCRIPTION 2101 " This object contains the delay between repetitions of the 2102 call waiting tone that the MTA will play from a single CMS 2103 request." 2104 DEFVAL { 10 } 2105 ::= { pktcNcsEndPntConfigEntry 28 } 2107 pktcNcsEndPntStatusCallIpAddress OBJECT-TYPE 2108 SYNTAX InetAddress 2109 MAX-ACCESS read-only 2110 STATUS current 2111 DESCRIPTION 2112 " This object contains the Internet address of the CMS 2113 currently being used for this endpoint. This Internet 2114 address is used to create the appropriate security 2115 association." 2116 ::= { pktcNcsEndPntConfigEntry 29 } 2118 pktcNcsEndPntStatusError OBJECT-TYPE 2119 SYNTAX INTEGER { 2120 operational (1), 2121 noSecurityAssociation (2), 2122 disconnected (3) 2123 } 2124 MAX-ACCESS read-only 2125 STATUS current 2126 DESCRIPTION 2127 " This object contains the error status for this interface. 2128 The operational status indicates that all operations 2129 necessary to put the line in service have occurred, and the 2130 CMS has acknowledged the RSIP message successfully. If 2131 pktcMtaDevCmsIpsecCtrl is enabled for the associated Call 2132 Agent, the noSecurityAssociation status indicates that no 2133 Security Association (SA) yet exists for this endpoint. 2134 Otherwise, the state is unused. The disconnected status 2135 indicates one of the following two: 2136 If pktcMtaDevCmsIpsecCtrl is disabled, then no security 2137 association is involved with this endpoint. The NCS 2138 signaling software is in process of establishing the NCS 2139 signaling link via an RSIP exchange. 2140 Otherwise, pktcMtaDevCmsIpsecCtrl is enabled, the security 2141 Association has been established, and the NCS signaling 2142 software is in process of establishing the NCS signaling 2143 link via an RSIP exchange." 2144 ::= { pktcNcsEndPntConfigEntry 30 } 2146 pktcNcsEndPntConfigMinHookFlash OBJECT-TYPE 2147 SYNTAX Unsigned32 (1..1000) 2148 UNITS "Milliseconds" 2149 MAX-ACCESS read-create 2150 STATUS current 2151 DESCRIPTION 2152 " This is the minimum time a line needs to be on hook for a 2153 valid hook flash." 2154 DEFVAL { 300 } 2155 ::= { pktcNcsEndPntConfigEntry 31 } 2157 pktcNcsEndPntConfigMaxHookFlash OBJECT-TYPE 2158 SYNTAX Unsigned32 (1..1800) 2159 UNITS "Milliseconds" 2160 MAX-ACCESS read-create 2161 STATUS current 2162 DESCRIPTION 2163 " This is the maximum time a line needs to be on hook for a 2164 valid hook flash." 2165 DEFVAL { 1000 } 2166 ::= { pktcNcsEndPntConfigEntry 32 } 2168 pktcNcsEndPntConfigPulseDialInterdigitTime OBJECT-TYPE 2169 SYNTAX Unsigned32 (100..1500) 2170 UNITS "Milliseconds" 2171 MAX-ACCESS read-create 2172 STATUS current 2173 DESCRIPTION 2174 " This is the pulse dial inter-digit timeout." 2175 DEFVAL { 100 } 2176 ::= { pktcNcsEndPntConfigEntry 33 } 2178 pktcNcsEndPntConfigPulseDialMinMakeTime OBJECT-TYPE 2179 SYNTAX Unsigned32 (1..200) 2180 UNITS "Milliseconds" 2181 MAX-ACCESS read-create 2182 STATUS current 2183 DESCRIPTION 2184 " This is the minimum make pulse width for the dial pulse." 2185 DEFVAL { 25 } 2186 ::= { pktcNcsEndPntConfigEntry 34 } 2188 pktcNcsEndPntConfigPulseDialMaxMakeTime OBJECT-TYPE 2189 SYNTAX Unsigned32 (1..200) 2190 UNITS "Milliseconds" 2191 MAX-ACCESS read-create 2192 STATUS current 2193 DESCRIPTION 2194 " This is the maximum make pulse width for the dial pulse." 2195 DEFVAL { 55 } 2196 ::= { pktcNcsEndPntConfigEntry 35 } 2198 pktcNcsEndPntConfigPulseDialMinBreakTime OBJECT-TYPE 2199 SYNTAX Unsigned32 (1..200) 2200 UNITS "Milliseconds" 2201 MAX-ACCESS read-create 2202 STATUS current 2203 DESCRIPTION 2204 " This is the minimum break pulse width for the dial pulse." 2205 DEFVAL { 45 } 2206 ::= { pktcNcsEndPntConfigEntry 36 } 2208 pktcNcsEndPntConfigPulseDialMaxBreakTime OBJECT-TYPE 2209 SYNTAX Unsigned32 (1..200) 2210 UNITS "Milliseconds" 2211 MAX-ACCESS read-create 2212 STATUS current 2213 DESCRIPTION 2214 " This is the maximum break pulse width for the dial pulse." 2215 DEFVAL { 75 } 2216 ::= { pktcNcsEndPntConfigEntry 37 } 2218 pktcNcsEndPntConfigNomJitterBufferSize OBJECT-TYPE 2219 SYNTAX Unsigned32 2220 UNITS "Milliseconds" 2221 MAX-ACCESS read-create 2222 STATUS current 2223 DESCRIPTION 2224 " The current setting for the nominal amount of jitter the 2225 MTA can compensate." 2226 ::= { pktcNcsEndPntConfigEntry 38 } 2228 pktcNcsEndPntConfigMaxJitterBufferSize OBJECT-TYPE 2229 SYNTAX Unsigned32 2230 UNITS "Milliseconds" 2231 MAX-ACCESS read-create 2232 STATUS current 2233 DESCRIPTION 2234 " The current setting for the maximum amount of jitter the 2235 MTA can compensate ." 2236 ::= { pktcNcsEndPntConfigEntry 39 } 2238 pktcNcsEndPntConfigOnHookDebounce OBJECT-TYPE 2239 SYNTAX Unsigned32 (1..1000) 2240 UNITS "Milliseconds" 2241 MAX-ACCESS read-create 2242 STATUS current 2243 DESCRIPTION 2244 " The length of the on-hook debounce." 2245 DEFVAL { 200 } 2246 ::= { pktcNcsEndPntConfigEntry 40 } 2248 pktcNcsEndPntConfigOffHookDebounce OBJECT-TYPE 2249 SYNTAX Unsigned32 (1..1000) 2250 UNITS "Milliseconds" 2251 MAX-ACCESS read-create 2252 STATUS current 2253 DESCRIPTION 2254 " The length of the off hook debounce." 2255 DEFVAL { 100 } 2256 ::= { pktcNcsEndPntConfigEntry 41 } 2258 pktcNcsEndPntConfigTxGain OBJECT-TYPE 2259 SYNTAX Integer32 (-14..14) 2260 UNITS "dB" 2261 MAX-ACCESS read-create 2262 STATUS current 2263 DESCRIPTION 2264 " The per line transmitter gain." 2265 DEFVAL { 0 } 2266 ::= { pktcNcsEndPntConfigEntry 42 } 2268 pktcNcsEndPntConfigRxGain OBJECT-TYPE 2269 SYNTAX Integer32 (-14..14) 2270 UNITS "dB" 2271 MAX-ACCESS read-create 2272 STATUS current 2273 DESCRIPTION 2274 " The per line receiver gain." 2275 DEFVAL { 0 } 2276 ::= { pktcNcsEndPntConfigEntry 43 } 2278 pktcNcsEndPntStatusCallIpAddressType OBJECT-TYPE 2279 SYNTAX InetAddressType 2280 MAX-ACCESS read-only 2281 STATUS current 2282 DESCRIPTION 2283 " This object contains the type of Internet address of the 2284 CMS currently being used for this endpoint." 2285 ::= { pktcNcsEndPntConfigEntry 44 } 2287 -- 2288 -- notification group is for future extension. 2289 -- 2290 pktcSigNotification OBJECT IDENTIFIER ::= { pktcSigMib 2 0 } 2291 pktcSigConformance OBJECT IDENTIFIER ::= { pktcSigMib 3 } 2292 pktcSigCompliances OBJECT IDENTIFIER ::= { pktcSigConformance 1 } 2293 pktcSigGroups OBJECT IDENTIFIER ::= { pktcSigConformance 2 } 2295 -- 2296 -- compliance statements 2297 -- 2299 pktcSigBasicCompliance MODULE-COMPLIANCE 2300 STATUS current 2301 DESCRIPTION 2302 " The compliance statement for devices that implement 2303 Signaling on the MTA." 2305 MODULE -- pktcSigMib 2307 -- 2308 -- unconditionally mandatory groups 2309 -- 2311 MANDATORY-GROUPS { 2312 pktcSigGroup 2313 } 2315 GROUP pktcNcsGroup 2316 DESCRIPTION 2317 " This group is mandatory for any MTA implementing NCS 2318 signaling" 2320 GROUP pktcInternationalGroup 2321 DESCRIPTION 2322 " This group is mandatory for any MTA implementing 2323 international telephony features. In such cases, it is 2324 left to manufacturers to determine whether to support both 2325 PacketCable and IPCablecom objects in the same MTA." 2326 ::={ pktcSigCompliances 1 } 2328 -- 2329 -- units of conformance 2330 -- 2332 pktcSigGroup OBJECT-GROUP 2333 OBJECTS { 2334 pktcSigDevCodecType, 2335 pktcSigDevCodecMax, 2336 pktcSigDevEchoCancellation, 2337 pktcSigDevSilenceSuppression, 2338 pktcSigDevConnectionMode, 2339 pktcSigDevR0Cadence, 2340 pktcSigDevR6Cadence, 2341 pktcSigDevR7Cadence, 2342 pktcSigDefCallSigDscp, 2343 pktcSigDefMediaStreamDscp, 2344 pktcSignalingType, 2345 pktcSignalingVersion, 2346 pktcSignalingVendorExtension, 2347 pktcSigEndPntCapabilityIndex, 2348 pktcSigDefNcsReceiveUdpPort, 2349 pktcSigServiceClassNameUS, 2350 pktcSigServiceClassNameDS, 2351 pktcSigServiceClassNameMask, 2352 pktcSigNcsServiceFlowState, 2353 pktcSigDevR1Cadence, 2354 pktcSigDevR2Cadence, 2355 pktcSigDevR3Cadence, 2356 pktcSigDevR4Cadence, 2357 pktcSigDevR5Cadence, 2358 pktcSigDevRgCadence, 2359 pktcSigDevRsCadence, 2360 pktcSigDevRtCadence 2361 } 2362 STATUS current 2363 DESCRIPTION 2364 "Group of objects for the common portion of the 2365 PacketCable Signaling MIB." 2366 ::= { pktcSigGroups 1 } 2368 pktcNcsGroup OBJECT-GROUP 2369 OBJECTS { 2370 pktcNcsEndPntConfigCallAgentId, 2371 pktcNcsEndPntConfigCallAgentUdpPort, 2372 pktcNcsEndPntConfigPartialDialTO, 2373 pktcNcsEndPntConfigCriticalDialTO, 2374 pktcNcsEndPntConfigBusyToneTO, 2375 pktcNcsEndPntConfigDialToneTO, 2376 pktcNcsEndPntConfigMessageWaitingTO, 2377 pktcNcsEndPntConfigOffHookWarnToneTO, 2378 pktcNcsEndPntConfigRingingTO, 2379 pktcNcsEndPntConfigRingBackTO, 2380 pktcNcsEndPntConfigReorderToneTO, 2381 pktcNcsEndPntConfigStutterDialToneTO, 2382 pktcNcsEndPntConfigTSMax, 2383 pktcNcsEndPntConfigMax1, 2384 pktcNcsEndPntConfigMax2, 2385 pktcNcsEndPntConfigMax1QEnable, 2386 pktcNcsEndPntConfigMax2QEnable, 2387 pktcNcsEndPntConfigMWD, 2388 pktcNcsEndPntConfigTdinit, 2389 pktcNcsEndPntConfigTdmin, 2390 pktcNcsEndPntConfigTdmax, 2391 pktcNcsEndPntConfigRtoMax, 2392 pktcNcsEndPntConfigRtoInit, 2393 pktcNcsEndPntConfigLongDurationKeepAlive, 2394 pktcNcsEndPntConfigThist, 2395 pktcNcsEndPntConfigStatus, 2396 pktcNcsEndPntConfigCallWaitingMaxRep, 2397 pktcNcsEndPntConfigCallWaitingDelay, 2398 pktcNcsEndPntStatusCallIpAddressType, 2399 pktcNcsEndPntStatusCallIpAddress, 2400 pktcNcsEndPntStatusError 2401 } 2402 STATUS current 2403 DESCRIPTION 2404 "Group of objects for the NCS portion of the PacketCable 2405 Signaling MIB. This is mandatory for NCS signaling." 2406 ::= { pktcSigGroups 2 } 2408 pktcInternationalGroup OBJECT-GROUP 2409 OBJECTS { 2410 pktcNcsEndPntConfigMinHookFlash, 2411 pktcNcsEndPntConfigMaxHookFlash, 2412 pktcNcsEndPntConfigNomJitterBufferSize, 2413 pktcNcsEndPntConfigMaxJitterBufferSize, 2414 pktcNcsEndPntConfigOnHookDebounce, 2415 pktcNcsEndPntConfigOffHookDebounce, 2416 pktcNcsEndPntConfigTxGain, 2417 pktcNcsEndPntConfigRxGain, 2418 pktcNcsEndPntConfigPulseDialInterdigitTime, 2419 pktcNcsEndPntConfigPulseDialMinMakeTime, 2420 pktcNcsEndPntConfigPulseDialMaxMakeTime, 2421 pktcNcsEndPntConfigPulseDialMinBreakTime, 2422 pktcNcsEndPntConfigPulseDialMaxBreakTime, 2423 pktcSigDevRingCadence, 2424 pktcSigDevStandardRingCadence, 2425 pktcSigDevRingSplashCadence, 2426 pktcSigDevCIDMode, 2427 pktcSigDevCIDFskAfterRing, 2428 pktcSigDevCIDFskAfterDTAS, 2429 pktcSigDevCIDRingAfterFSK, 2430 pktcSigDevCIDDTASAfterLR, 2431 pktcSigPowerRingFrequency, 2432 pktcSigPCMCoding, 2433 pktcSigPulseSignalDuration, 2434 pktcSigPulseSignalType, 2435 pktcSigPulseSignalDbLevel, 2436 pktcSigPulseSignalFrequency, 2437 pktcSigPulseSignalRepeatCount, 2438 pktcSigPulseSignalPauseDuration, 2439 pktcSigDevToneType, 2440 pktcSigDevToneDbLevel, 2441 pktcSigDevToneFreqType, 2442 pktcSigDevToneNumFrequencies, 2443 pktcSigDevToneFirstFrequency, 2444 pktcSigDevToneSecondFrequency, 2445 pktcSigDevToneThirdFrequency, 2446 pktcSigDevToneFourthFrequency, 2447 pktcSigDevToneNumOnOffTimes, 2448 pktcSigDevToneFirstToneOn, 2449 pktcSigDevToneFirstToneOff, 2450 pktcSigDevToneSecondToneOn, 2451 pktcSigDevToneSecondToneOff, 2452 pktcSigDevToneThirdToneOn, 2453 pktcSigDevToneThirdToneOff, 2454 pktcSigDevToneFourthToneOn, 2455 pktcSigDevToneFourthToneOff, 2456 pktcSigDevToneWholeToneRepeatCount, 2457 pktcSigDevToneSteady 2458 } 2459 STATUS current 2460 DESCRIPTION 2461 " Group of objects that extend the behavior of existing 2462 objects to support operations in the widest possible set 2463 of international marketplaces. Note that many of these 2464 objects represent a superset of behaviors described in 2465 other objects within this MIB Module." 2466 ::= { pktcSigGroups 3 } 2468 END 2470 5. Acknowledgments 2472 This document is a production of the PacketCable Working Group. 2474 The current editors wish to express gratitude to: 2476 Angela Lyda Arris Interactive 2477 Sasha Medvinsky Motorola 2478 Roy Spitzer Telogy Networks, Inc. 2479 Rick Vetter Motorola 2480 Itay Sherman Texas Instruments 2481 Klaus Hermanns Cisco Systems 2482 Eugene Nechamkin Broadcom Corp 2483 Matt A. Osman CableLabs 2484 Jean-Francois Mule CableLabs 2486 6. Normative References 2488 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2489 Rose, M. and S. Waldbusser, "Structure of Management 2490 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2491 1999. 2493 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2494 Rose, M. and S. Waldbusser, "Textual Conventions for 2495 SMIv2", STD 58, RFC 2579, April 1999. 2497 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2498 Rose, M. and S. Waldbusser, "Conformance Statements for 2499 SMIv2", STD 58, RFC 2580, April 1999. 2501 [RFC3289] Baker, F., Chan, K., Smith, A., "Management Information 2502 Base for the Differentiated Services Architecture", RFC 2503 3289, May 2002. 2505 [RFC3291] Daniel, M., Haberman, B., Routhier, S., Schoenwaelder, J., 2506 "Textual Conventions for Internet Network Addresses", RFC 2507 3291, May 2002. 2509 [RFC3435] Andreasen, F., Foster, B., "Media Gateway Control Protocol 2510 (MGCP)", RFC 3435, January 2003. 2512 [PKT-SP-MGCP-IO7-030415] Packetcable Network-Based Call Signaling 2513 Protocol Specification PKT-SP-EC-MGCP- 2514 IO7-030415. 2516 [PKT-SP-PROV-IO6-030415] Packetcable MTA Device Provisioning 2517 Specification PKT-SP-PROV-IO6-030415. 2519 [PKT-SP-CODEC-IO4-021018] Packetcable Audio/Video Codecs 2520 Specification PKT-SP-CODEC-IO4-021018. 2522 7. Informative References 2524 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2525 "Introduction and Applicability Statements for Internet- 2526 Standard Management Framework", RFC 3410, December 2002. 2528 [RFC2026] Bradner, S., "The Internet Standards Process, Revision 3", 2529 RFC 2026, October 1996. 2531 [RFC3261] Rosenberg, J., Schulzrinne H., Camarillo, G., Johnston, 2532 A., Peterson, J., Sparks, R., Handley, M., and Schooler, 2533 E. "SIP: Session Initiation Protocol", RFC 3261, June 2534 2002. 2536 [PKT-SP-MIB-MTA-I06-030415] Packetcable MTA MIB Specification PKT- 2537 SP-MIB-MTA-I06-030415. 2539 [ETSI TS 101 909-4] ETSI TS 101 909-4:"Access and Terminals (AT); 2540 Digital Broadband Cable Access to the Public 2541 Telecommunications Network; IP Multimedia Time 2542 Critical Services; Part 4: Network Call 2543 Signaling Protocol". 2545 [ETSI TS 101 909-9] ETSI TS 101 909-9:"Access and Terminals (AT); 2546 Digital Broadband Cable Access to the Public 2547 Telecommunications Network; IP Multimedia Time 2548 Critical Services; Part 9: IPCablecom Network 2549 Call Signalling (NCS) MIB Requirements". 2551 [EN 300 001] EN 300 001 V1.5.1 (1998-10):"European Standard 2552 (Telecommunications series) Attachments to Public 2553 Switched Telephone Network (PSTN); General technical 2554 requirements for equipment connected to an analogue 2555 subscriber interface in the PSTN; Chapter 3: Ringing 2556 signal characteristics (national deviations are in 2557 Table 3.1.1)". 2559 [EN 300 659-1] EN 300 659-1: �Public Switched Telephone Network 2560 (PSTN); Subscriber line protocol over the local loop 2561 for display (and related) services; Part 1: On hook 2562 data transmission�. 2564 8. Security Considerations 2566 There are a number of management objects defined in this MIB that 2567 have a MAX-ACCESS clause of read-write and/or read-create. Such 2568 objects may be considered sensitive or vulnerable in some network 2569 environments. The support for SET operations in a non-secure 2570 environment without proper protection can have a negative effect on 2571 network operations. 2573 The following Differentiated Services Code Point (DSCP) and mask 2574 objects are used to differentiate between various types of traffic 2575 in the service provider network: 2577 pktcSigDefCallSigDscp 2578 pktcSigDefMediaStreamDscp 2579 pktcSigServiceClassNameMask 2581 These objects may contain information that may be sensitive from a 2582 business perspective. For example, they may represent a customer's 2583 service contract that a service provider chooses to apply to a 2584 customer's ingress or egress traffic. If these objects are SET 2585 maliciously, it may permit unmarked or inappropriately marked 2586 signaling and media traffic to enter the service provider network, 2587 resulting in unauthorized levels of service for customers. 2589 The following objects determine ring cadence, repeatable 2590 characteristics, and signal duration for telephony operation: 2592 pktcSigDevR0Cadence 2593 pktcSigDevR1Cadence 2594 pktcSigDevR2Cadence 2595 pktcSigDevR3Cadence 2596 pktcSigDevR4Cadence 2597 pktcSigDevR5Cadence 2598 pktcSigDevR6Cadence 2599 pktcSigDevR7Cadence 2600 pktcSigDevRgCadence 2601 pktcSigDevRsCadence 2602 pktcSigDevRtCadence 2603 pktcSigPulseSignalDuration 2604 pktcSigPulseSignalPauseDuration 2606 If these objects are SET maliciously, it may result in unwanted 2607 operation, or a failure to obtain telephony service from client 2608 (MTA) devices. 2610 The objects in the pktcNcsEndPntConfigTable are used for end point 2611 signaling. The pktcNcsEndPntConfigCallAgentId object contains the 2612 name of the call agent, which includes the call agent FQDN. If this 2613 object is SET maliciously, the MTA will not be able to communicate 2614 with the call agent, resulting in a disruption of telephony service. 2615 The pktcNcsEndPntConfigCallAgentUdpPort object identifies the UDP 2616 port for NCS signaling traffic. If this object is SET maliciously, 2617 the call agent will not receive NCS signaling traffic from the MTA, 2618 also resulting in a disruption of telephony service. 2620 Some of the readable objects in this MIB module (i.e., objects with 2621 a MAX-ACCESS other than not-accessible) may be considered sensitive 2622 or vulnerable in some network environments. It is thus important to 2623 control even GET and/or NOTIFY access to these objects and possibly 2624 to even encrypt the values of these objects when sending them over 2625 the network via SNMP. The most sensitive is 2626 pktcNcsEndPntStatusCallIpAddress within pktcNcsEndPntConfigTable. 2627 This information itself may be valuable to would-be attackers. 2629 SNMP versions prior to SNMPv3 did not include adequate security. 2630 Even if the network itself is secure (for example by using IPSec), 2631 even then, there is no control as to who on the secure network is 2632 allowed to access and GET/SET (read/change/create/delete) the 2633 objects in this MIB module. 2635 It is RECOMMENDED that implementers consider the security features 2636 as provided by the SNMPv3 framework (see [RFC3410], section 8), 2637 including full support for the SNMPv3 cryptographic mechanisms (for 2638 authentication and privacy). 2640 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2641 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2642 enable cryptographic security. It is then a customer/operator 2643 responsibility to ensure that the SNMP entity giving access to an 2644 instance of this MIB module is properly configured to give access to 2645 the objects only to those principals (users) that have legitimate 2646 rights to indeed GET or SET (change/create/delete) them. 2648 9. Intellectual Property 2650 The IETF takes no position regarding the validity or scope of any 2651 intellectual property or other rights that might be claimed to 2652 pertain to the implementation or use of the technology described in 2653 document or the extent to which any license under such rights might 2654 or might not be available; neither does it represent that it has 2655 made any effort to identify any such rights. Information on the 2656 IETF's procedures with respect to rights in standards-track and 2657 standards-related documentation can be found in BCP-11. Copies of 2658 claims of rights made available for publication and any assurances 2659 of licenses to be made available, or the result of an attempt made 2660 to obtain a general license or permission for the use of such 2661 proprietary rights by implementers or users of this specification 2662 can be obtained from the IETF Secretariat. 2664 The IETF invites any interested party to bring to its attention any 2665 copyrights, patents or patent applications, or other proprietary 2666 rights that may cover technology that may be required to practice 2667 this standard. Please address the information to the IETF Executive 2668 Director. 2670 10. Authors' Addresses 2672 Gordon Beacham 2673 Motorola BCS/DCG 2674 6450 Sequence Drive, Bldg. 1 2675 San Diego, CA 92121, USA 2676 +1 858-404-2335 2677 gordon.beacham@motorola.com 2679 Satish Kumar Mudugere Eswaraiah 2680 Texas Instruments India (P) Ltd., 2681 Golf view, Wind Tunnel Road 2682 Murugesh Palya 2683 Bangalore - 560 017, INDIA 2684 +91 80 5269451 2685 satish.kumar@ti.com 2687 Sumanth Channabasappa 2688 Alopa Networks Inc 2689 248, McCaslin Bvld #101, 2690 Louisville, Colorado - 80027 2691 U.S.A. 2692 +1 303 604 6595 2693 Sumanth@alopa.com 2695 11. Full Copyright Statement 2697 The IETF takes no position regarding the validity or scope of any 2698 intellectual property or other rights that might be claimed to 2699 pertain to the implementation or use of the technology described in 2700 this document or the extent to which any license under such rights 2701 might or might not be available; neither does it represent that it 2702 has made any effort to identify any such rights. Information on the 2703 IETF's procedures with respect to rights in standards-track and 2704 standards-related documentation can be found in BCP-11. Copies of 2705 claims of rights made available for publication and any assurances 2706 of licenses to be made available, or the result of an attempt made 2707 to obtain a general license or permission for the use of such 2708 proprietary rights by implementers or users of this specification 2709 can be obtained from the IETF Secretariat. 2711 The IETF invites any interested party to bring to its attention any 2712 copyrights, patents or patent applications, or other proprietary 2713 rights which may cover technology that may be required to practice 2714 this standard. Please address the information to the IETF Executive 2715 Director. 2717 Copyright (C) The Internet Society (2003). All Rights Reserved. 2719 This document and translations of it may be copied and furnished to 2720 others, and derivative works that comment on or otherwise explain it 2721 or assist in its implmentation may be prepared, copied, published 2722 and distributed, in whole or in part, without restriction of any 2723 kind, provided that the above copyright notice and this paragraph 2724 are included on all such copies and derivative works. However, this 2725 document itself may not be modified in any way, such as by removing 2726 the copyright notice or references to the Internet Society or other 2727 Internet organizations, except as needed for the purpose of 2728 developing Internet standards in which case the procedures for 2729 copyrights defined in the Internet Standards process must be 2730 followed, or as required to translate it into languages other than 2731 English. 2733 The limited permissions granted above are perpetual and will not be 2734 revoked by the Internet Society or its successors or assigns. 2736 This document and the information contained herein is provided on an 2737 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2738 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2739 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2740 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2741 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.