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