idnits 2.17.1 draft-ietf-ipcdn-pktc-signaling-00.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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 36 longer pages, the longest (page 13) being 63 lines 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 364 instances of too long lines in the document, the longest one being 23 characters in excess of 72. ** The abstract seems to contain references ([5], [6], [7]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 4 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** 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. RFC 2119 keyword, line 113: '...ng translated MIB MUST be semantically...' RFC 2119 keyword, line 1335: '...neNumFrequencies MUST equal btiToneNum...' RFC 2119 keyword, line 1343: '...neNumFrequencies MUST equal 4 and btiT...' RFC 2119 keyword, line 1344: '... MUST equal 2...' RFC 2119 keyword, line 1517: '...n associated row MUST be defined in on...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 295 has weird spacing: '...portion of th...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 25, 2002) is 7854 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '17' is defined on line 2376, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 2382, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 2387, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) -- Possible downref: Non-RFC (?) normative reference: ref. '17' -- Possible downref: Non-RFC (?) normative reference: ref. '19' -- Possible downref: Non-RFC (?) normative reference: ref. '20' -- Possible downref: Non-RFC (?) normative reference: ref. '21' Summary: 17 errors (**), 0 flaws (~~), 8 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Charles Schell 3 draft-ietf-ipcdn-pktc-signaling-00.txt Motorola 4 Satish Kumar 5 Texas Instruments 6 Sumanth Channabasappa 7 Alopa Networks Inc 8 Expires: April 25, 2003 October 25, 2002 10 Network Control Signaling (NCS) Signaling MIB 11 for PacketCable/IPCablecom MTAs 13 Status of this Memo 15 This document is an Internet-Draft and is in full conformance with 16 all provisions of RFC 2026 [18]. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 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 (2002). All Rights Reserved. 38 Abstract 40 This memo defines the Signaling 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/IPCablecom compliant Multimedia Terminal Adapter 44 devices. 45 This memo specifies a MIB module in a manner that is compliant to 46 the SNMP SMIv2 [5][6][7]. The set of objects are consistent with 47 the SNMP framework and existing SNMP standards. 49 Schell/Kumar/Channabasappa Page 1 10/25/2002 50 Table of Contents 52 1 The SNMP Management Framework ................................... 2 53 2 Glossary ........................................................ 3 54 2.1 MTA .......................................................... 3 55 3 Overview ........................................................ 3 56 3.1 Structure of the MIB .......................................... 3 57 3.1.1 pktcSigMibObjects ........................................... 3 58 3.1.1.1 pktcSigDevConfigObjects ................................... 4 59 3.1.1.2 pktcNcsEndPntConfigObjects ................................ 5 60 3.1.1.3 pktcSigEndPntConfigObjects ................................ 5 61 3.1.1.4 PktcDcsEndPntConfigObjects ................................ 5 62 3.1.2 pktcSigNotification ......................................... 5 63 3.1.3 pktcSigConformance .......................................... 6 64 4 Definitions ..................................................... 6 65 5 Acknowledgments ................................................ 28 66 6 References ..................................................... 28 67 7 Security Considerations ........................................ 30 68 8 Intellectual Property .......................................... 30 69 9 Authors Addresses .............................................. 31 70 10 Full Copyright Statement ...................................... 31 72 1. The SNMP Management Framework 74 The SNMP Management Framework presently consists of five major 75 components: 77 o An overall architecture, described in RFC 2571 [1]. 79 o Mechanisms for describing and naming objects and events for the 80 purpose of management. The first version of this Structure of 81 Management Information (SMI) is called SMIv1 and described in STD 82 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The 83 second version, called SMIv2, is described in STD 58, RFC 2578 84 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. 86 o Message protocols for transferring management information. The 87 first version of the SNMP message protocol is called SNMPv1 and 88 described in RFC 1157 [8]. A second version of the SNMP message 89 protocol, which is not an Internet standards track protocol, is 90 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 91 The third version of the message protocol is called SNMPv3 and 92 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 94 o Protocol operations for accessing management information. The 95 first set of protocol operations and associated PDU formats is 96 described in STD 15, RFC 1157 [8]. A second set of protocol 97 operations and associated PDU formats is described in RFC 1905 98 [13]. 100 o A set of fundamental applications described in RFC 2573 [14] and 101 the view-based access control mechanism described in RFC 2575 102 [15]. 104 A more detailed introduction to the current SNMP Management Framework 105 can be found in RFC 2570 [16]. 107 Managed objects are accessed via a virtual information store, termed 108 as Management Information Base or MIB. Objects in the MIB are 109 defined using the mechanisms defined in the SMI. 111 This memo specifies a MIB module that is compliant to the SMIv2. A 112 MIB conforming to the SMIv1 can be produced through the appropriate 113 translations. The resulting translated MIB MUST be semantically 114 equivalent, except where objects or events are omitted because no 115 translation is possible (use of Counter64). Some machine readable 116 information in SMIv2 will be converted into textual descriptions in 117 SMIv1 during the translation process. However, this loss of machine 118 readable information is not considered to change the semantics of the 119 MIB. 121 2. Glossary 123 The terms in this document are derived either from normal cable 124 system usage, or from the documents associated with the IPcablecom/PacketCable 125 Specification process. 127 2.1. MTA 129 Multimedia Terminal Adapter, a device that contains the interface(s) to a physical 130 voice device, a network interface, CODECs, and all signaling and encapsulation 131 functions required for VoIP transport, class feature signaling and QoS signaling. 133 3. Overview 135 This MIB provides a set of objects required for Signaling 136 PacketCable/IPCablecom compliant MultiMedia Terminal Adapter (MTA) devices. 137 The significance of each MIB object is defined along with applicable default 138 values. 140 Since telephone systems are typically very complex and often have a wide 141 distribution, it is important for management systems to support MTAs from 142 multiple vendors at the same time, including those from multiple countries. 143 As a result, this MIB module provides objects suitable for operating in the 144 widest variety of marketplaces as is possible. 146 3.1. Structure of the MIB 148 This MIB is identified by pktcSigMib and is structured in three groups: 150 o Signaling information that control device and endpoint configuration 151 objects(pktcSigMibObjects). 153 o Signaling Notification object, that notifies the status(pktcSigNotification) 155 o Signaling Conformance has mandatory signaling objects(pktcSigConformance) 157 Each group of objects is explained in detail. 159 3.1.1. pktcSigMibObjects 161 The objects in pktcSigMibObjects group is divided into four sub groups: 163 o Device configuration MIB explain MTA configuration (pktcSigDevConfigObjects). 165 o NCS Endpoint configuration MIB is explained in pktcNcsEndPntConfigObjects 167 o Endpoint signaling configuration MIB is in pktcSigEndPntConfigObjects 169 o DCS Endpoint configuration is explained in pktcDcsEndPntConfigObjects 171 Each group of objects are explained in detail. 173 3.1.1.1 pktcSigDevConfigObjects 175 pktcSigDevCodecTable - this table describes MTA supported codec types. 177 pktcSigDevEchoCancellation - This object identifies the capability of echo 178 cancellation on the device. 180 pktcSigDevSilenceSuppression - This object specifies if the device is 181 capable of silence suppression (Voice Activity Detection). 183 pktcSigDevConnectionMode - This object specifies the connection modes that 184 The MTA device can support. 186 pktcSigDevR0Cadence - this object specifies ring cadence 0. 188 pktcSigDevR6Cadence - this object specifies ring cadence 6. 190 pktcSigDevR7Cadence - this object specifies ring cadence 7. 192 pktcSigDefCallSigTos - this object specifies the default value used in the 193 IP header for setting the Type of Service (TOS) value for call signaling. 195 pktcSigDefMediaStreamTos - this object specifies the default value used in 196 the IP header for setting the Type of Service (TOS) value for media 197 stream packets. 199 pktcSigTosFormatSelector - this object specifies the format of the default 200 signaling and media Type of Service (TOS) values. 202 pktcSigCapabilityTable - this table specifies list of supported signaling 203 types, versions and vendor extensions for MTA. 205 pktcSigDefNcsReceiveUdpPort - this object contains the MTA User Datagram 206 Protocol (UDP) receive port that is being used for NCS call signaling. 208 pktcSigServiceClassNameUS - this object contains a string indicating the 209 Service Class Name to create an Upstream Service Flow for NCS. 211 pktcSigServiceClassNameDS - this object contains a string indicating the 212 Service Class Name to create an Downstream Service Flow for NCS. 214 pktcSigServiceClassNameMask - this object contains a value for the 215 Call Signaling Network Mask. 217 pktcSigNcsServiceFlowState - this object contains a status value of the 218 Call Signaling Service Flow. 220 pktcSigDevR1Cadence - this object specifies ring cadence 1. 222 pktcSigDevR2Cadence - this object specifies ring cadence 2. 224 pktcSigDevR3Cadence - this object specifies ring cadence 3. 226 pktcSigDevR4Cadence - this object specifies ring cadence 4. 228 pktcSigDevR5Cadence - this object specifies ring cadence 5. 230 pktcSigDevRgCadence - this object specifies ring cadence rg. 232 pktcSigDevRsCadence - this object specifies ring cadence rs. 234 pktcSigDevRtCadence - this object specifies ring cadence rt. 236 pktcSigDevCIDMode - this international object selects various 237 modes of caller id in common use throughout the world. 239 pktcSigDevCIDFskAfterRing - this international object sets the 240 delay between the end of first ringing and the transmission of 241 caller id information. 243 pktcSigDevCIDFskAfterDTAS - this international object sets the 244 delay between the dual-tone alert signal and the transmission of 245 caller id information. 247 pktcSigDevCIDRingAfterFSK - this international object sets the 248 delay between the transmission of caller id information and the 249 first ringing pattern. 251 pktcSigDevCIDDTASAfterLR - this international object sets the 252 delay between the end of a line reversal and the dual-tone alert 253 signal. 255 pktcSigDevRingCadenceTable - this international object provides 256 a flexible structure within which to specify a variety of ring 257 cadences. 259 pktcSigDevStandardRingCadence - this international object 260 specifies the standard ring assumed by the MTA. 262 pktcSigDevRingSplashCadence - this international object specifies 263 the standard splash ring assumed by the MTA. 265 pktcSigDevToneTable - this international object specifies a 266 flexible structure within which to specify all of the tones 267 used in the MTA. 269 3.1.1.2 pktcNcsEndPntConfigObjects 271 pktcNcsEndPntConfigTable - this table describes the PacketCable(tm) NCS 272 EndPoint configuration. The number of entries in this table represents 273 the number of provisioned end points. 275 3.1.1.3 pktcSigEndPntConfigObjects 277 pktcSigEndPntConfigTable - this table describes the packet cable EndPoint 278 slected signaling type. The number of entries in this table represents 279 the number of provisioned end points. 281 3.1.1.4 pktcDcsEndPntConfigObjects 283 This object is reserved for future use in Distributed Call Signaling (DCS). 285 3.1.2. pktcSigNotification 287 This object is used for signaling notification and reserved for future use. 289 3.1.3. pktcSigConformance 291 pktcSigCompliances - this tables has one object that has compliance 292 statement for devices that implement Signaling on the MTA. 294 pktcSigGroups - this table contains group of objects for the common 295 portion of the PacketCable NCS and Signaling MIB. 297 pktcInternationalGroup - this table extends this MIB Module by establishing 298 a set of objects designed to support operations over the widest range of 299 marketplaces as is possible. 301 4. Definitions 303 PKTC-SIG-MIB DEFINITIONS ::= BEGIN 305 IMPORTS 306 MODULE-IDENTITY, 307 OBJECT-TYPE, 308 Integer32, 309 mib-2 310 FROM SNMPv2-SMI 311 InetAddressType, 312 InetAddress, 313 InetPortNumber 314 FROM INET-ADDRESS-MIB 315 TEXTUAL-CONVENTION, 316 RowStatus, 317 TruthValue 318 FROM SNMPv2-TC 319 OBJECT-GROUP, 320 MODULE-COMPLIANCE 321 FROM SNMPv2-CONF 322 SnmpAdminString 323 FROM SNMP-FRAMEWORK-MIB 324 ifIndex 325 FROM IF-MIB; 327 pktcSigMib MODULE-IDENTITY 328 LAST-UPDATED "200210250000Z" -- October 25, 2002 329 ORGANIZATION "CableLabs - PacketCable OSS Group" 330 CONTACT-INFO 331 "Satish Kumar Mudugere Eswaraiah 332 Texas Instruments India (P) Ltd., 333 Golf view, Wind Tunnel Road 334 Murugesh Palya 335 Bangalore - 560 017, INDIA 336 Phone: +91 80 5269451 337 Email: satish.kumar@ti.com 339 Sumanth Channabasappa 340 Alopa Networks Inc 341 248, McCaslin Bvld #101, 342 Louisville, Colorado - 80027 343 U.S.A. 344 Phone: +1 303 604 6595 345 Email: Sumanth@alopa.com 347 Charles Schell 348 Motorola BCS/IPNS 349 101 Tournament Drive, Bldg. 3 350 Horsham, PA 19044, USA 351 Phone: +1 215-323-1145 352 E-Mail: cschell@motorola.com 354 IETF IPCDN Working Group 355 General Discussion: ipcdn@ietf.org 356 Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn 357 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 358 Chair: Richard Woundy, rwoundy@broadband.att.com" 360 DESCRIPTION 361 "This MIB module supplies the basic management 362 object for the PacketCable Signaling 363 protocols. This version of the MIB includes 364 common signaling and Network Call Signaling 365 (NCS) related signaling objects." 367 REVISION "200210210000Z" 369 DESCRIPTION 370 "Initial Introduction of the draft of the document." 372 ::= { mib-2 99992 } -- to be assigned by IANA. 374 -- Textual Conventions 376 PktcCodecType ::= TEXTUAL-CONVENTION 377 STATUS current 378 DESCRIPTION 379 " These are the various types of codecs that may be supported." 380 SYNTAX INTEGER { 381 other (1), 382 unknown (2), 383 g729 (3), 384 g729a (4), 385 g729e (5), 386 g711mu (6), 387 g726K32 (7), -- G.726 32 Khz 388 g728 (8), 389 g711a (9), 390 g726K16 (10), -- G.726 16 Khz 391 g726K24 (11), -- G.726 24 Khz 392 g726K40 (12) -- G.726 40 Khz 393 } 395 PktcRingCadence ::= TEXTUAL-CONVENTION 396 STATUS current 397 DESCRIPTION 398 " This object represents a ring cadence in bit string format. The 399 ring cadence representation starts with the first 1 in the 400 pattern (the leading 0s in the MSB are padding and are to be 401 ignored). Each bit represents 100ms of tone; 1 is tone, 0 is no 402 tone. Initial 60 bits are used for cadence representation. Bit 61 is 403 used to represent repeatable(when set to ZERO) and non repeatable 404 (when set to ONE) characteristic of cadence. Other three bits are 405 reserved for future use, and currently set to 000. Repeatable 406 characteristic of cadence is currently coded as 0000, and 1000 407 means non repeatable As an example, the hex representation of a 408 ring cadence of 0.5 secs on; 4 secs off; repeatable 409 would be: 0x1F0000000000." 410 SYNTAX BITS { 411 interval1 (0), 412 interval2 (1), 413 interval3 (2), 414 interval4 (3), 415 interval5 (4), 416 interval6 (5), 417 interval7 (6), 418 interval8 (7), 419 interval9 (8), 420 interval10 (9), 421 interval11 (10), 422 interval12 (11), 423 interval13 (12), 424 interval14 (13), 425 interval15 (14), 426 interval16 (15), 427 interval17 (16), 428 interval18 (17), 429 interval19 (18), 430 interval20 (19), 431 interval21 (20), 432 interval22 (21), 433 interval23 (22), 434 interval24 (23), 435 interval25 (24), 436 interval26 (25), 437 interval27 (26), 438 interval28 (27), 439 interval29 (28), 440 interval30 (29), 441 interval31 (30), 442 interval32 (31), 443 interval33 (32), 444 interval34 (33), 445 interval35 (34), 446 interval36 (35), 447 interval37 (36), 448 interval38 (37), 449 interval39 (38), 450 interval40 (39), 451 interval41 (40), 452 interval42 (41), 453 interval43 (42), 454 interval44 (43), 455 interval45 (44), 456 interval46 (45), 457 interval47 (46), 458 interval48 (47), 459 interval49 (48), 460 interval50 (49), 461 interval51 (50), 462 interval52 (51), 463 interval53 (52), 464 interval54 (53), 465 interval55 (54), 466 interval56 (55), 467 interval57 (56), 468 interval58 (57), 469 interval59 (58), 470 interval60 (59), 471 interval61 (60), 472 interval62 (61), 473 interval63 (62), 474 interval64 (63) 475 } 477 PktcSigType ::= TEXTUAL-CONVENTION 478 STATUS current 479 DESCRIPTION 480 " These are the various types of signaling that 481 may be supported. 483 ncs - network call signaling a derivation of 484 MGCP (Media Gateway Control Protocol) 485 version 1.0 487 dcs - distributed call signaling a derivation 488 of SIP (Session Initiation Protocol)RFC 2543" 489 SYNTAX INTEGER { 490 other(1), 491 unknown(2), 492 ncs(3), 493 dcs(4) 494 } 496 pktcSigMibObjects OBJECT IDENTIFIER ::= { pktcSigMib 1 } 497 pktcSigDevConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 1 } 498 pktcNcsEndPntConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 2 } 499 pktcSigEndPntConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 3 } 500 pktcDcsEndPntConfigObjects OBJECT IDENTIFIER ::= { pktcSigMibObjects 4 } 502 -- 503 -- The pktcSigDevCodecTable defines the codecs supported by the 504 -- Media Terminal Adapter (MTA). There is one entry for each 505 -- codecs supported. 506 -- 507 pktcSigDevCodecTable OBJECT-TYPE 508 SYNTAX SEQUENCE OF PktcSigDevCodecEntry 509 MAX-ACCESS not-accessible 510 STATUS current 511 DESCRIPTION 512 " This table describes the MTA supported codec types." 513 ::= { pktcSigDevConfigObjects 1 } 515 pktcSigDevCodecEntry OBJECT-TYPE 516 SYNTAX PktcSigDevCodecEntry 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 " List of supported codecs types for the MTA." 521 INDEX { pktcSigDevCodecIndex } 522 ::= { pktcSigDevCodecTable 1 } 524 PktcSigDevCodecEntry ::= SEQUENCE { 525 pktcSigDevCodecIndex Integer32, 526 pktcSigDevCodecType PktcCodecType, 527 pktcSigDevCodecMax Integer32 528 } 530 pktcSigDevCodecIndex OBJECT-TYPE 531 SYNTAX Integer32 (1..16383) 532 MAX-ACCESS not-accessible 533 STATUS current 534 DESCRIPTION 535 " The index value which uniquely identifies an entry 536 in the pktcSigDevCodecTable." 537 ::= { pktcSigDevCodecEntry 1 } 539 pktcSigDevCodecType OBJECT-TYPE 540 SYNTAX PktcCodecType 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 " A codec type supported by this MTA." 545 ::= { pktcSigDevCodecEntry 2 } 547 pktcSigDevCodecMax OBJECT-TYPE 548 SYNTAX Integer32(1..16383) 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 " The maximum number of simultaneous sessions of the specific 553 codec that the MTA can support" 554 ::= { pktcSigDevCodecEntry 3 } 556 -- 557 -- These are the common signaling related definitions that affect the 558 -- entire MTA device. 559 -- 561 pktcSigDevEchoCancellation OBJECT-TYPE 562 SYNTAX TruthValue 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 " This object specifies if the device is capable of echo 567 cancellation." 568 ::= { pktcSigDevConfigObjects 2 } 570 pktcSigDevSilenceSuppression OBJECT-TYPE 571 SYNTAX TruthValue 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 " This object specifies if the device is capable of silence 576 suppression (Voice Activity Detection)." 577 ::= { pktcSigDevConfigObjects 3 } 579 pktcSigDevConnectionMode OBJECT-TYPE 580 SYNTAX BITS { 581 voice(0), 582 fax(1), 583 modem(2) 584 } 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 " This object specifies the connection modes that the MTA 589 device can support." 590 ::= { pktcSigDevConfigObjects 4 } 592 -- 593 -- In the United States Ring Cadences 0, 6, and 7 are custom 594 -- ring cadences definable by the user. The following three 595 -- objects are used for these definitions. 596 -- 598 pktcSigDevR0Cadence OBJECT-TYPE 599 SYNTAX PktcRingCadence 600 MAX-ACCESS read-write 601 STATUS current 602 DESCRIPTION 603 " This object specifies ring cadence 0 (a user defined field) 604 where each bit (least significant bit) represents a duration 605 of 100 milliseconds (6 seconds total)." 607 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, 608 interval7, interval8, interval9, interval10, interval11, interval12, 609 interval13, interval14, interval15, interval16, interval17, 610 interval18, interval19, interval20 } } 611 ::= { pktcSigDevConfigObjects 5 } 613 pktcSigDevR6Cadence OBJECT-TYPE 614 SYNTAX PktcRingCadence 615 MAX-ACCESS read-write 616 STATUS current 617 DESCRIPTION 618 " This object specifies ring cadence 6 (a user defined field) 619 where each bit (least significant bit) represents a duration 620 of 100 milliseconds (6 seconds total)." 621 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, 622 interval7, interval8, interval9, interval10, interval11, interval12, 623 interval13, interval14, interval15, interval16, interval17, 624 interval18, interval19, interval20 } } 625 ::= { pktcSigDevConfigObjects 6 } 627 pktcSigDevR7Cadence OBJECT-TYPE 628 SYNTAX PktcRingCadence 629 MAX-ACCESS read-write 630 STATUS current 631 DESCRIPTION 632 " This object specifies ring cadence 6 (a user defined field) 633 where each bit (least significant bit) represents a duration 634 of 100 milliseconds (6 seconds total)." 635 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, 636 interval7, interval8, interval9, interval10, interval11, interval12, 637 interval13, interval14, interval15, interval16, interval17, 638 interval18, interval19, interval20 } } 639 ::= { pktcSigDevConfigObjects 7 } 641 pktcSigDefCallSigTos OBJECT-TYPE 642 SYNTAX Integer32 (0..63) 643 MAX-ACCESS read-write 644 STATUS current 645 DESCRIPTION 646 " The default value used in the IP header for setting the 647 Type of Service (TOS) value for call signaling. " 648 REFERENCE 649 " Refer to Packetcable NCS specification [17]" 650 DEFVAL { 0 } 651 ::= { pktcSigDevConfigObjects 8 } 653 pktcSigDefMediaStreamTos OBJECT-TYPE 654 SYNTAX Integer32 (0..63) 655 MAX-ACCESS read-write 656 STATUS current 657 DESCRIPTION 658 " The default value used in the IP header for setting 659 the Type of Service (TOS) value for media stream packets. " 660 REFERENCE 661 " Refer to Packetcable NCS specification [17]" 662 DEFVAL { 0 } 663 ::= { pktcSigDevConfigObjects 9 } 665 pktcSigTosFormatSelector OBJECT-TYPE 666 SYNTAX INTEGER { 667 ipv4TOSOctet(1), 668 dscpCodepoint(2) 669 } 670 MAX-ACCESS read-write 671 STATUS current 672 DESCRIPTION 673 " The format of the default signaling and media Type of Service 674 (TOS) values. " 675 DEFVAL { ipv4TOSOctet } 676 ::= { pktcSigDevConfigObjects 10 } 678 -- 679 -- pktcSigCapabilityTable - This table defines the valid signaling 680 -- types supported by this MTA. 681 -- 683 pktcSigCapabilityTable OBJECT-TYPE 684 SYNTAX SEQUENCE OF PktcSigCapabilityEntry 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 " This table describes the signaling types by this MTA." 689 ::= { pktcSigDevConfigObjects 11 } 691 pktcSigCapabilityEntry OBJECT-TYPE 692 SYNTAX PktcSigCapabilityEntry 693 MAX-ACCESS not-accessible 694 STATUS current 695 DESCRIPTION 696 " Entries in pktcMtaDevSigCapabilityTable - List of supported 697 signaling types, versions and vendor extensions for this MTA. 698 Each entry in the list provides for one signaling type and 699 version combination. If the device supports multiple versions 700 of the same signaling type - it will require mutiple entries." 701 INDEX { pktcSignalingIndex } 702 ::= { pktcSigCapabilityTable 1 } 704 PktcSigCapabilityEntry ::= SEQUENCE { 705 pktcSignalingIndex Integer32, 706 pktcSignalingType PktcSigType, 707 pktcSignalingVersion SnmpAdminString, 708 pktcSignalingVendorExtension SnmpAdminString 709 } 711 pktcSignalingIndex OBJECT-TYPE 712 SYNTAX Integer32 (1..16383) 713 MAX-ACCESS not-accessible 714 STATUS current 715 DESCRIPTION 716 " The index value which uniquely identifies 717 an entry in the pktcSigCapabilityTable." 719 ::= { pktcSigCapabilityEntry 1 } 721 pktcSignalingType OBJECT-TYPE 722 SYNTAX PktcSigType 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 " The Type indentifies the type of signaling 727 used, this can be NCS, DCS, etc. This value 728 has to be associated with a single signaling 729 version." 730 ::= { pktcSigCapabilityEntry 2 } 732 pktcSignalingVersion OBJECT-TYPE 733 SYNTAX SnmpAdminString 734 MAX-ACCESS read-only 735 STATUS current 736 DESCRIPTION 737 " Provides the version of the signaling type - reference 738 pktcSignalingType. Examples would be 1.0 or 2.33 etc." 739 ::= { pktcSigCapabilityEntry 3 } 741 pktcSignalingVendorExtension OBJECT-TYPE 742 SYNTAX SnmpAdminString 743 MAX-ACCESS read-only 744 STATUS current 745 DESCRIPTION 746 " The vendor extension allows vendors to 747 provide a list of additional capabilities, 748 vendors can decide how to encode these 749 Extensions, although space separated text is suggested." 750 ::= { pktcSigCapabilityEntry 4 } 752 pktcSigDefNcsReceiveUdpPort OBJECT-TYPE 753 SYNTAX InetPortNumber 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 " This object contains the MTA User Datagram Protocol (UDP) 758 receive port that is being used for NCS call signaling. 759 This object should only be changed by the configuration file." 760 REFERENCE 761 "Refer to Packetcable NCS specification [17]" 762 DEFVAL { 2427 } 763 ::= { pktcSigDevConfigObjects 12 } 765 pktcSigServiceClassNameUS OBJECT-TYPE 766 SYNTAX SnmpAdminString 767 MAX-ACCESS read-write 768 STATUS current 769 DESCRIPTION 770 " This object contains a string indicating the Service Class 771 Name to create an Upstream Service Flow for NCS. If the 772 object has an empty string value then the NCS SF is not 773 created and the best effort primary SF is used for NCS data. 774 Setting this object to a different value does not cause 775 the US SF to be re-created." 776 DEFVAL { "" } 777 ::= { pktcSigDevConfigObjects 13 } 779 pktcSigServiceClassNameDS OBJECT-TYPE 780 SYNTAX SnmpAdminString 781 MAX-ACCESS read-write 782 STATUS current 783 DESCRIPTION 784 " This object contains a string indicating the Service Class 785 Name to create a Downstream Service Flow for NCS. If the 786 object has an empty string value then the NCS SF is not 787 created and the best effort primary SF is used for NCS data. 788 Setting this object to a different value does not cause the 789 DS SF to be re-created." 790 DEFVAL { "" } 791 ::= { pktcSigDevConfigObjects 14 } 793 pktcSigServiceClassNameMask OBJECT-TYPE 794 SYNTAX Integer32 795 MAX-ACCESS read-write 796 STATUS current 797 DESCRIPTION 798 " This object contains a value for the Call Signaling Network 799 Mask. The value is used as the NCS Call Signaling classifier 800 mask. The object is used to delete the NCS SF when set to 801 zero. When the object is set to a non-zero value by the SNMP 802 Manager, the NCS SF are to be created" 803 DEFVAL { 0 } 804 ::= { pktcSigDevConfigObjects 15 } 806 pktcSigNcsServiceFlowState OBJECT-TYPE 807 SYNTAX INTEGER { 808 notactive (1), 809 active (2), 810 error (3) 811 } 812 MAX-ACCESS read-only 813 STATUS current 814 DESCRIPTION 815 "This object contains a status value of the Call Signaling 816 Service Flow. 817 - 'not-active' indicates that the NCS SF is not 818 being used, and has not tried to be created, 819 - 'active' indicates that the NCS SF is in use, 820 - 'error' indicates that the NCS SF creation resulted 821 in an error and the best effort channel is used for 822 NCS Signaling" 824 ::= { pktcSigDevConfigObjects 16 } 826 pktcSigDevR1Cadence OBJECT-TYPE 827 SYNTAX PktcRingCadence 828 MAX-ACCESS read-write 829 STATUS current 830 DESCRIPTION 831 " This object specifies ring cadence 1 (a user defined field) 832 where each bit (least significant bit) represents a duration 833 of 100 milliseconds (6 seconds total)." 834 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, 835 interval7, interval8, interval9, interval10, interval11, interval12, 836 interval13, interval14, interval15, interval16, interval17, 837 interval18, interval19, interval20 } } 838 ::= { pktcSigDevConfigObjects 17 } 840 pktcSigDevR2Cadence OBJECT-TYPE 841 SYNTAX PktcRingCadence 842 MAX-ACCESS read-write 843 STATUS current 844 DESCRIPTION 845 " This object specifies ring cadence 2 (a user defined field) 846 where each bit (least significant bit) represents a duration 847 of 100 milliseconds (6 seconds total)." 848 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, 849 interval7, interval8, interval13, interval14, interval15, interval16, 850 interval17, interval18, interval19, interval20 } } 851 ::= { pktcSigDevConfigObjects 18 } 853 pktcSigDevR3Cadence OBJECT-TYPE 854 SYNTAX PktcRingCadence 855 MAX-ACCESS read-write 856 STATUS current 857 DESCRIPTION 858 " This object specifies ring cadence 3 (a user defined field) 859 where each bit (least significant bit) represents a duration 860 of 100 milliseconds (6 seconds total)." 861 DEFVAL { { interval1, interval2, interval3, interval4, interval7, interval8, 862 interval9, interval10, interval13, interval14, interval15, interval16, 863 interval17, interval18, interval19, interval20 } } 864 ::= { pktcSigDevConfigObjects 19 } 866 pktcSigDevR4Cadence OBJECT-TYPE 867 SYNTAX PktcRingCadence 868 MAX-ACCESS read-write 869 STATUS current 870 DESCRIPTION 871 " This object specifies ring cadence 4 (a user defined field) 872 where each bit (least significant bit) represents a duration 873 of 100 milliseconds (6 seconds total)." 874 DEFVAL { { interval1, interval2, interval3, interval6, interval7, interval8, 875 interval9, interval10, interval11, interval12, interval13, interval14, 876 interval15, interval18, interval19, interval20 } } 877 ::= { pktcSigDevConfigObjects 20 } 879 pktcSigDevR5Cadence OBJECT-TYPE 880 SYNTAX PktcRingCadence 881 MAX-ACCESS read-write 882 STATUS current 883 DESCRIPTION 884 " This object specifies ring cadence 5 (a user defined field) 885 where each bit (least significant bit) represents a duration 886 of 100 milliseconds (6 seconds total)." 887 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval61 } } 888 ::= { pktcSigDevConfigObjects 21 } 889 pktcSigDevRgCadence OBJECT-TYPE 890 SYNTAX PktcRingCadence 891 MAX-ACCESS read-write 892 STATUS current 893 DESCRIPTION 894 " This object specifies ring cadence rg (a user defined field) 895 where each bit (least significant bit) represents a duration 896 of 100 milliseconds (6 seconds total)." 897 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, 898 interval7, interval8, interval9, interval10, interval11, interval12, 899 interval13, interval14, interval15, interval16, interval17, 900 interval18, interval19, interval20 } } 901 ::= { pktcSigDevConfigObjects 22 } 903 pktcSigDevRsCadence OBJECT-TYPE 904 SYNTAX PktcRingCadence 905 MAX-ACCESS read-write 906 STATUS current 907 DESCRIPTION 908 " This object specifies ring cadence rs (a user defined field) 909 where each bit (least significant bit) represents a duration 910 of 100 milliseconds (6 seconds total)." 911 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval61 } } 912 ::= { pktcSigDevConfigObjects 23 } 914 pktcSigDevRtCadence OBJECT-TYPE 915 SYNTAX PktcRingCadence 916 MAX-ACCESS read-write 917 STATUS current 918 DESCRIPTION 919 " This object specifies ring cadence rt (a user defined field) 920 where each bit (least significant bit) represents a duration 921 of 100 milliseconds (6 seconds total)." 922 DEFVAL { { interval1, interval2, interval3, interval4, interval5, interval6, 923 interval7, interval8, interval9, interval10, interval11, interval12, 924 interval13, interval14, interval15, interval16, interval17, 925 interval18, interval19, interval20 } } 926 ::= { pktcSigDevConfigObjects 24 } 928 pktcSigPowerRingFrequency OBJECT-TYPE 929 SYNTAX INTEGER { 930 twenty(1), 931 twentyFive(2), 932 thirtyThreePointThreeThree(3), 933 fifty(4) 934 } 935 UNITS "Hertz" 936 MAX-ACCESS read-write 937 STATUS current 938 DESCRIPTION 939 " The power ring frequency is the frequency at which the 940 sinusoidal voltage must travel down the twisted pair to make terminal 941 equipment ring. Different countries define different electrical 942 characteristics to make this happen. ETS 300 001 (1998) [21] lists the 943 frequency ranges that are defined for each country." 944 DEFVAL {twenty} 945 ::= { pktcSigDevConfigObjects 25 } 946 pktcSigPCMCoding OBJECT-TYPE 947 SYNTAX INTEGER { 948 aLaw(1), 949 uLaw(2) 950 } 951 MAX-ACCESS read-write 952 STATUS current 953 DESCRIPTION 954 " This is the Pulse Code Modulation (PCM) format used by an EMTA when coding 955 and decoding analog telephone signals. The default will be aLaw(1)." 956 ::= { pktcSigDevConfigObjects 26 } 958 pktcSigPulseSignalTable OBJECT-TYPE 959 SYNTAX SEQUENCE OF PktcSigPulseSignalEntry 960 MAX-ACCESS not-accessible 961 STATUS current 962 DESCRIPTION 963 " The Pulse signal table defines the pulse signal operation. There are four 964 types of international pulse signals, initial ring, meter pulse, reverse 965 polarity and no battery. The Pulse duration type is specific and it is 966 specified with a 1 to 32 value." 967 ::= { pktcSigDevConfigObjects 27 } 969 pktcSigPulseSignalEntry OBJECT-TYPE 970 SYNTAX PktcSigPulseSignalEntry 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 " Unique value ranging from 1 to 32 that will correspond to the 975 value specified by the operator." 976 INDEX { pktcSigPulseSignalIndex } 977 ::= { pktcSigPulseSignalTable 1 } 979 PktcSigPulseSignalEntry ::= SEQUENCE { 980 pktcSigPulseSignalIndex Integer32, 981 pktcSigPulseSignalDuration Integer32, 982 pktcSigPulseSignalType INTEGER, 983 pktcSigPulseSignalDbLevel Integer32, 984 pktcSigPulseSignalFrequency INTEGER, 985 pktcSigPulseSignalRepeatCount Integer32, 986 pktcSigPulseSignalPauseDuration Integer32} 988 pktcSigPulseSignalIndex OBJECT-TYPE 989 SYNTAX Integer32 (1..32) 990 MAX-ACCESS not-accessible 991 STATUS current 992 DESCRIPTION 993 " The table index equivalent to the operator specific pulse type 994 and duration." 995 ::= { pktcSigPulseSignalEntry 1 } 997 pktcSigPulseSignalDuration OBJECT-TYPE 998 SYNTAX Integer32 (1..5000) 999 UNITS "Milliseconds" 1000 MAX-ACCESS read-write 1001 STATUS current 1002 DESCRIPTION 1003 " The pulse duration varies according to the operator and country." 1004 DEFVAL { 1000 } 1005 ::= {pktcSigPulseSignalEntry 2 } 1007 pktcSigPulseSignalType OBJECT-TYPE 1008 SYNTAX INTEGER 1009 { 1010 initialRing(1), 1011 meterPulse(2), 1012 reversePolarity(3), 1013 noBattery(4) 1014 } 1015 MAX-ACCESS read-write 1016 STATUS current 1017 DESCRIPTION 1018 " There are four types of international pulse signals." 1019 DEFVAL { initialRing } 1020 ::= { pktcSigPulseSignalEntry 3 } 1022 pktcSigPulseSignalDbLevel OBJECT-TYPE 1023 SYNTAX Integer32 (-25..15) 1024 UNITS "dbm" 1025 MAX-ACCESS read-write 1026 STATUS current 1027 DESCRIPTION 1028 " This is the decibel level at which the meter pulse could be 1029 generated." 1030 ::={pktcSigPulseSignalEntry 4 } 1032 pktcSigPulseSignalFrequency OBJECT-TYPE 1033 SYNTAX INTEGER { 1034 fifty(1), 1035 twelvethousand(2), 1036 sixteenthousand(3) 1037 } 1038 UNITS "Hertz" 1039 MAX-ACCESS read-write 1040 STATUS current 1041 DESCRIPTION 1042 " This is the frequency at which the meter pulse could be generated." 1043 ::= { pktcSigPulseSignalEntry 5} 1045 pktcSigPulseSignalRepeatCount OBJECT-TYPE 1046 SYNTAX Integer32 (0..5000) 1047 MAX-ACCESS read-write 1048 STATUS current 1049 DESCRIPTION 1050 " This is the repeat count, which signifies how many times to 1051 repeat the pulse." 1052 ::={ pktcSigPulseSignalEntry 6 } 1054 pktcSigPulseSignalPauseDuration OBJECT-TYPE 1055 SYNTAX Integer32 (1..5000) 1056 UNITS "Milliseconds" 1057 MAX-ACCESS read-write 1058 STATUS current 1059 DESCRIPTION 1060 " The pause duration between pulses varies according to the 1061 operator and country." 1062 ::= {pktcSigPulseSignalEntry 7 } 1064 pktcSigDevCIDMode OBJECT-TYPE 1065 SYNTAX INTEGER { 1066 northAmerican(1), 1067 duringRingingETS(2), 1068 dtAsETS(3), 1069 rpAsETS(4), 1070 lrAsETS(5) 1071 } 1072 MAX-ACCESS read-write 1073 STATUS current 1074 DESCRIPTION 1075 " For both on-hook and off-hook Caller ID, pktcSigDevCIDMode selects 1076 between North American modulation (BellCore 202) and ETS modulation 1077 (V.23). For on-hook Caller ID, it also selects between sending the 1078 FSK between the first and second ring pattern (northAmerican and 1079 duringRingingETS), Dual Tone Alert Signal (DtAsETS), after a Ring 1080 Pulse (rsAsETS) or, after a Line Reversal followed by a Dual Tone 1081 Alert Signal (lrAsETS)." 1082 DEFVAL { northAmerican } 1083 ::= {pktcSigDevConfigObjects 28 } 1085 pktcSigDevCIDFskAfterRing OBJECT-TYPE 1086 SYNTAX Integer32 (500..2000) 1087 UNITS "Milliseconds" 1088 MAX-ACCESS read-write 1089 STATUS current 1090 DESCRIPTION 1091 " Determines the delay between the end of first ringing pattern and 1092 the transmission of the FSK containing the CallerID information. It 1093 is only used when pktcSigDevCIDMode is northAmerican or 1094 duringRingingETS." 1095 DEFVAL { 550 } 1096 ::= {pktcSigDevConfigObjects 29 } 1098 pktcSigDevCIDFskAfterDTAS OBJECT-TYPE 1099 SYNTAX Integer32 (45..500) 1100 UNITS "Milliseconds" 1101 MAX-ACCESS read-write 1102 STATUS current 1103 DESCRIPTION 1104 " Determines the delay between the Dual Tone Alert Signal (DT-AS) 1105 and the transmission of the FSK containing the Caller ID 1106 information. It is only used when pktcSigDevCIDMode is dtAsETS 1107 or lrAsETS." 1108 ::= {pktcSigDevConfigObjects 30 } 1110 pktcSigDevCIDRingAfterFSK OBJECT-TYPE 1111 SYNTAX Integer32 (200..500) 1112 UNITS "Milliseconds" 1113 MAX-ACCESS read-write 1114 STATUS current 1115 DESCRIPTION 1116 " Determines the delay between the complete transmission of the 1117 FSK containing the Caller ID information and the first ring 1118 pattern. It is only used when pktcSigDevCIDMode is dtAsETS, 1119 rpAsETS or lrAsETS." 1120 ::= {pktcSigDevConfigObjects 31 } 1122 pktcSigDevCIDDTASAfterLR OBJECT-TYPE 1123 SYNTAX Integer32 (100..655) 1124 UNITS "Milliseconds" 1125 MAX-ACCESS read-write 1126 STATUS current 1127 DESCRIPTION 1128 " Determines the delay between the end of the Line Reversal and 1129 Dual Tone Alert Signal (DT-AS). It is only used when 1130 pktcSigDevCIDMode is lrAsETS." 1131 ::= {pktcSigDevConfigObjects 32 } 1133 pktcSigDevRingCadenceTable OBJECT-TYPE 1134 SYNTAX SEQUENCE OF PktcSigDevRingCadenceEntry 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 " In V5.2, Cadence rings are defined by the telco governing body for each 1139 country. The MTA must be able to support various ranges of cadence patterns 1140 and cadence periods. The MTA will be able to support country specific 1141 provisioning of the cadence and idle period. There will be at most 3 on/off 1142 transitions per cadence period. Each cadence pattern will be assigned a 1143 unique value ranging 1-128 corresponding to the value sent by the LE SIGNAL 1144 message plus one. MTA will derive the cadence periods from the ring Cadence 1145 table entry as provisioned by the customer." 1146 ::= { pktcSigDevConfigObjects 33 } 1148 pktcSigDevRingCadenceEntry OBJECT-TYPE 1149 SYNTAX PktcSigDevRingCadenceEntry 1150 MAX-ACCESS not-accessible 1151 STATUS current 1152 DESCRIPTION 1153 " Unique value ranging from 1 to 128 that corresponds to the 1154 value sent by the LE (plus one) based on country specific cadences, 1155 one row per cadence cycle. In any given system implementation for a 1156 particular country, it is anticipated that a small number of 1157 ring cadences will be in use. Thus, this table most 1158 likely will not be populated to its full 128-row size." 1159 INDEX { pktcSigDevRingCadenceIndex } 1160 ::= { pktcSigDevRingCadenceTable 1 } 1162 PktcSigDevRingCadenceEntry ::= SEQUENCE { 1163 pktcSigDevRingCadenceIndex Integer32, 1164 pktcSigDevRingCadence OCTET STRING 1165 } 1167 pktcSigDevRingCadenceIndex OBJECT-TYPE 1168 SYNTAX Integer32 (1..128) 1169 MAX-ACCESS not-accessible 1170 STATUS current 1171 DESCRIPTION 1172 " The table index equivalent to the country specific cadence (1 - 128)." 1173 ::= { pktcSigDevRingCadenceEntry 1 } 1175 pktcSigDevRingCadence OBJECT-TYPE 1176 SYNTAX OCTET STRING (SIZE(2..28)) 1177 MAX-ACCESS read-write 1178 STATUS current 1179 DESCRIPTION 1180 " This is the Ring Cadence Octet String. The first octet of 1181 the bit string represents the length in bits of the duration 1182 of the cadence. Each Bit after the first octet represents 50 ms 1183 and 1 represents ring and 0 represent silent. The first bit of 1184 the second octet is the first bit of the ring cadence. Only 216 1185 Bits can be set total to represent 10800 ms of total cadence cycle." 1186 ::= { pktcSigDevRingCadenceEntry 2 } 1188 pktcSigDevStandardRingCadence OBJECT-TYPE 1189 SYNTAX OCTET STRING (SIZE(2..28)) 1190 MAX-ACCESS read-write 1191 STATUS current 1192 DESCRIPTION 1193 " This is the Ring Cadence Octet String for the standard ring. 1194 The first octet of the bit string represents the length in bits 1195 of the duration of the cadence Each Bit after the first octet 1196 represents 50 ms and 1 represents ring and 0 represent silent. 1197 The first bit of the second octet is the first bit of the ring 1198 cadence. Only 216 Bits can be set total to represent 10800 ms of 1199 total cadence cycle." 1200 ::= { pktcSigDevConfigObjects 34 } 1202 pktcSigDevRingSplashCadence OBJECT-TYPE 1203 SYNTAX OCTET STRING (SIZE(2..28)) 1204 MAX-ACCESS read-write 1205 STATUS current 1206 DESCRIPTION 1207 " This is the Ring Cadence Octet String for splash ring. The first 1208 octet of te bit string represents the length in bits of the 1209 duration of the cadence. Each Bit after the first octet represents 1210 50 ms and 1 represents ring and 0 represent silent. The first bit 1211 of the second octet is the first bit of the ring cadence. Only 1212 216 Bits can be set total to represent 10800 ms of total cadence 1213 cycle." 1214 ::= { pktcSigDevConfigObjects 35 } 1216 pktcSigDevToneTable OBJECT-TYPE 1217 SYNTAX SEQUENCE OF PktcSigDevToneEntry 1218 MAX-ACCESS not-accessible 1219 STATUS current 1220 DESCRIPTION 1221 " The Tone Table defines the various tone operations." 1222 ::= { pktcSigDevConfigObjects 36 } 1224 pktcSigDevToneEntry OBJECT-TYPE 1225 SYNTAX PktcSigDevToneEntry 1226 MAX-ACCESS not-accessible 1227 STATUS current 1228 DESCRIPTION 1229 " Unique value ranging from 1 to 49 that will correspond to the 1230 different tone types that are being supported by the device. 1231 These tones can be provisioned based on country specific needs." 1232 INDEX { pktcSigDevToneType } 1233 ::= { pktcSigDevToneTable 1 } 1235 PktcSigDevToneEntry ::= SEQUENCE { 1236 pktcSigDevToneType INTEGER, 1237 pktcSigDevToneDbLevel Integer32, 1238 pktcSigDevToneFreqType INTEGER, 1239 pktcSigDevToneNumFrequencies Integer32, 1240 pktcSigDevToneFirstFrequency Integer32, 1241 pktcSigDevToneSecondFrequency Integer32, 1242 pktcSigDevToneThirdFrequency Integer32, 1243 pktcSigDevToneFourthFrequency Integer32, 1244 pktcSigDevToneNumOnOffTimes Integer32, 1245 pktcSigDevToneFirstToneOn Integer32, 1246 pktcSigDevToneFirstToneOff Integer32, 1247 pktcSigDevToneSecondToneOn Integer32, 1248 pktcSigDevToneSecondToneOff Integer32, 1249 pktcSigDevToneThirdToneOn Integer32, 1250 pktcSigDevToneThirdToneOff Integer32, 1251 pktcSigDevToneFourthToneOn Integer32, 1252 pktcSigDevToneFourthToneOff Integer32, 1253 pktcSigDevToneWholeToneRepeatCount Integer32, 1254 pktcSigDevToneSteady TruthValue 1255 } 1257 pktcSigDevToneType OBJECT-TYPE 1258 SYNTAX INTEGER { 1259 dtmf0(0), 1260 dtmf1(1), 1261 dtmf2(2), 1262 dtmf3(3), 1263 dtmf4(4), 1264 dtmf5(5), 1265 dtmf6(6), 1266 dtmf7(7), 1267 dtmf8(8), 1268 dtmf9(9), 1269 dtmfToneStar(10), 1270 dtmfTonePound(11), 1271 dtmfA(12), 1272 dtmfB(13), 1273 dtmfC(14), 1274 dtmfD(15), 1275 busy(16), 1276 confirmation(17), 1277 dial(18), 1278 messageWaiting(19), 1279 offHookWarning(20), 1280 ringBack(21), 1281 reOrder(22), 1282 stutterdial(23), 1283 loopback(24), 1284 callWaiting1(25), 1285 callWaiting2(26), 1286 callWaiting3(27), 1287 callWaiting4(28), 1288 alertingSignal(29), 1289 testTone(30), 1290 specialDial(31), 1291 specialInfo(32), 1292 release(33), 1293 congestion(34), 1294 userDefinedOne(35) 1295 } 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 " This defines the type of tone being accessed." 1300 ::={pktcSigDevToneEntry 1 } 1302 pktcSigDevToneDbLevel OBJECT-TYPE 1303 SYNTAX Integer32 (-60..4) 1304 UNITS "dbm" 1305 MAX-ACCESS read-write 1306 STATUS current 1307 DESCRIPTION 1308 " This is the decibel level at which tones could be generated." 1309 DEFVAL { -4 } 1310 ::={pktcSigDevToneEntry 2 } 1312 pktcSigDevToneFreqType OBJECT-TYPE 1313 SYNTAX INTEGER { 1314 allFrequencies (1), 1315 singleFrequecySequence (2), 1316 dualFrequencySequence (3), 1317 allFrequenciesModulated (4) 1318 } 1319 MAX-ACCESS read-write 1320 STATUS current 1321 DESCRIPTION 1322 " This object describes how the frequencies are applied. 1324 allFrequencies indicates all frequences specifed by 1325 btiToneNumFrequencies are mixed to form a single tone. 1326 The tone is then applied in sequence using the number of on/off 1327 times specified in btiToneNumOnOffTimes. 1329 singleFrequecySequence indicates all frequencies specified by 1330 btiToneNumFrequencies are applied in sequence using the 1331 corresponding frequency number on/off time (eg. 1332 btiToneFirstFrequency uses btiToneFirstToneOn and btiToneFirstToneOff, 1333 btiToneSecondFrequency uses btiToneSecondToneOn and 1334 btiToneSecondToneOff, ... ). For this tone type 1335 btiToneNumFrequencies MUST equal btiToneNumOnOffTimes. 1337 dualFrequencySequence indicates two pairs of frequencies are 1338 mixed to form two sequenced tones. The first and second frequency 1339 are mixed to form tone one and are applied using 1340 btiToneFirstToneOn and btiToneFirstToneOff. The third and forth 1341 frequency are mixed to form tone two and are applied using 1342 btiToneSecondToneOn and btiToneSecondToneOff. For this tone 1343 type btiToneNumFrequencies MUST equal 4 and btiToneNumOnOffTimes 1344 MUST equal 2 1346 allFrequenciesModulated indicates all frequences specifed by 1347 btiToneNumFrequencies are modulated to form a single tone. The 1348 tone is then applied in sequence using the number of on/off 1349 times specified in btiToneNumOnOffTimes." 1350 DEFVAL { allFrequencies } 1351 ::={ pktcSigDevToneEntry 3 } 1353 pktcSigDevToneNumFrequencies OBJECT-TYPE 1354 SYNTAX Integer32 (1..4) 1355 MAX-ACCESS read-write 1356 STATUS current 1357 DESCRIPTION 1358 " Specifies the number of frequencies specified in the table entry." 1359 DEFVAL { 1 } 1360 ::={pktcSigDevToneEntry 4} 1362 pktcSigDevToneFirstFrequency OBJECT-TYPE 1363 SYNTAX Integer32 (0..4000) 1364 UNITS "Hertz" 1365 MAX-ACCESS read-write 1366 STATUS current 1367 DESCRIPTION 1368 " This is the first frequency at which the tones could be 1369 generated in a multiple frequency tone." 1370 ::={pktcSigDevToneEntry 5} 1372 pktcSigDevToneSecondFrequency OBJECT-TYPE 1373 SYNTAX Integer32 (0..4000) 1374 UNITS "Hertz" 1375 MAX-ACCESS read-write 1376 STATUS current 1377 DESCRIPTION 1378 " This is the second frequency at which the tones could be 1379 generated in a ultiple frequency tone." 1380 ::={pktcSigDevToneEntry 6} 1382 pktcSigDevToneThirdFrequency OBJECT-TYPE 1383 SYNTAX Integer32 (0..4000) 1384 UNITS "Hertz" 1385 MAX-ACCESS read-write 1386 STATUS current 1387 DESCRIPTION 1388 " This is the third frequency at which the tones could be 1389 generated." 1390 ::={pktcSigDevToneEntry 7} 1392 pktcSigDevToneFourthFrequency OBJECT-TYPE 1393 SYNTAX Integer32 (0..4000) 1394 UNITS "Hertz" 1395 MAX-ACCESS read-write 1396 STATUS current 1397 DESCRIPTION 1398 " This is the fourth frequency at which the tones could be 1399 generated." 1400 ::={pktcSigDevToneEntry 8} 1402 pktcSigDevToneNumOnOffTimes OBJECT-TYPE 1403 SYNTAX Integer32 (1..4) 1404 MAX-ACCESS read-write 1405 STATUS current 1406 DESCRIPTION 1407 " Specifies the number of on/off times specified in the 1408 table entry." 1409 DEFVAL { 1 } 1410 ::={pktcSigDevToneEntry 9} 1412 pktcSigDevToneFirstToneOn OBJECT-TYPE 1413 SYNTAX Integer32 (0..5000) 1414 UNITS "Milliseconds" 1415 MAX-ACCESS read-write 1416 STATUS current 1417 DESCRIPTION 1418 " This is the first tone interval." 1419 ::={ pktcSigDevToneEntry 10} 1421 pktcSigDevToneFirstToneOff OBJECT-TYPE 1422 SYNTAX Integer32 (0..5000) 1423 UNITS "Milliseconds" 1424 MAX-ACCESS read-write 1425 STATUS current 1426 DESCRIPTION 1427 " This is the first idle interval." 1428 ::={ pktcSigDevToneEntry 11 } 1430 pktcSigDevToneSecondToneOn OBJECT-TYPE 1431 SYNTAX Integer32 (0..5000) 1432 UNITS "Milliseconds" 1433 MAX-ACCESS read-write 1434 STATUS current 1435 DESCRIPTION 1436 " This is the second tone interval." 1437 ::={ pktcSigDevToneEntry 12 } 1439 pktcSigDevToneSecondToneOff OBJECT-TYPE 1440 SYNTAX Integer32 (0..5000) 1441 UNITS "Milliseconds" 1442 MAX-ACCESS read-write 1443 STATUS current 1444 DESCRIPTION 1445 " This is the second idle interval." 1446 ::={ pktcSigDevToneEntry 13 } 1448 pktcSigDevToneThirdToneOn OBJECT-TYPE 1449 SYNTAX Integer32 (0..5000) 1450 UNITS "Milliseconds" 1451 MAX-ACCESS read-write 1452 STATUS current 1453 DESCRIPTION 1454 " This is the third tone interval." 1455 ::={ pktcSigDevToneEntry 14 } 1457 pktcSigDevToneThirdToneOff OBJECT-TYPE 1458 SYNTAX Integer32 (0..5000) 1459 UNITS "Milliseconds" 1460 MAX-ACCESS read-write 1461 STATUS current 1462 DESCRIPTION 1463 " This is the third idle interval." 1464 ::={ pktcSigDevToneEntry 15 } 1466 pktcSigDevToneFourthToneOn OBJECT-TYPE 1467 SYNTAX Integer32 (0..5000) 1468 UNITS "Milliseconds" 1469 MAX-ACCESS read-write 1470 STATUS current 1471 DESCRIPTION 1472 " This is the fourth tone interval." 1473 ::={ pktcSigDevToneEntry 16 } 1475 pktcSigDevToneFourthToneOff OBJECT-TYPE 1476 SYNTAX Integer32 (0..5000) 1477 UNITS "Milliseconds" 1478 MAX-ACCESS read-write 1479 STATUS current 1480 DESCRIPTION 1481 " This is the Fourth idle interval." 1482 ::={ pktcSigDevToneEntry 17 } 1484 pktcSigDevToneWholeToneRepeatCount OBJECT-TYPE 1485 SYNTAX Integer32 (0..5000) 1486 MAX-ACCESS read-write 1487 STATUS current 1488 DESCRIPTION 1489 " This is the repeat count, which signifies how many times 1490 to repeat the entire on-off sequence." 1491 ::={ pktcSigDevToneEntry 18 } 1493 pktcSigDevToneSteady OBJECT-TYPE 1494 SYNTAX TruthValue 1495 MAX-ACCESS read-write 1496 STATUS current 1497 DESCRIPTION 1498 " This is the steady tone. Set to true to continue the 1499 last tone after on-off sequence." 1500 ::={ pktcSigDevToneEntry 19 } 1502 -- 1503 -- The following Table will provide endpoint configuration 1504 -- information that is common to all signaling Protocols. 1505 -- Currently only the signaling index is present in an effort 1506 -- not to deprecate any MIB objects. 1507 -- 1508 pktcSigEndPntConfigTable OBJECT-TYPE 1509 SYNTAX SEQUENCE OF PktcSigEndPntConfigEntry 1510 MAX-ACCESS not-accessible 1511 STATUS current 1512 DESCRIPTION 1513 " This table describes the packet cable EndPoint slected 1514 signaling type. The number of entries in this table 1515 represents the number of provisioned end points. 1516 For each conceptual row of pktcSigEndPntConfigTable 1517 Defined, an associated row MUST be defined in one on the 1518 specific signaling tables such as pktcNcsEndPntConfigTable." 1519 ::= { pktcSigEndPntConfigObjects 1 } 1521 pktcSigEndPntConfigEntry OBJECT-TYPE 1522 SYNTAX PktcSigEndPntConfigEntry 1523 MAX-ACCESS not-accessible 1524 STATUS current 1525 DESCRIPTION 1526 " Entries in pktcSigEndPntConfigTable - Each entry describes 1527 what signaling type a particular enpoint uses." 1528 INDEX { ifIndex } 1529 ::= { pktcSigEndPntConfigTable 1 } 1531 PktcSigEndPntConfigEntry ::= SEQUENCE { 1532 pktcSigEndPntCapabilityIndex Integer32 1533 } 1535 pktcSigEndPntCapabilityIndex OBJECT-TYPE 1536 SYNTAX Integer32 (1..16383) 1537 MAX-ACCESS read-create 1538 STATUS current 1539 DESCRIPTION 1540 " The associated index value in the pktcSigCapablityTable." 1541 ::= { pktcSigEndPntConfigEntry 1 } 1543 -- 1544 -- The NCS End Point Config Table is used to define attributes that 1545 -- are specific to connection EndPoints. 1546 -- 1547 -- 1549 pktcNcsEndPntConfigTable OBJECT-TYPE 1550 SYNTAX SEQUENCE OF PktcNcsEndPntConfigEntry 1551 MAX-ACCESS not-accessible 1552 STATUS current 1553 DESCRIPTION 1554 " This table describes the PacketCable(tm) NCS EndPoint 1555 configuration. The number of entries in this table 1556 represents the number of provisioned end points." 1557 ::= { pktcNcsEndPntConfigObjects 1 } 1559 pktcNcsEndPntConfigEntry OBJECT-TYPE 1560 SYNTAX PktcNcsEndPntConfigEntry 1561 MAX-ACCESS not-accessible 1562 STATUS current 1563 DESCRIPTION 1564 " List of attributes for a single packet cable endpoint interface." 1565 INDEX { ifIndex } 1566 ::= { pktcNcsEndPntConfigTable 1 } 1568 PktcNcsEndPntConfigEntry ::= SEQUENCE { 1569 pktcNcsEndPntConfigCallAgentId SnmpAdminString, 1570 pktcNcsEndPntConfigCallAgentUdpPort InetPortNumber, 1571 pktcNcsEndPntConfigPartialDialTO Integer32, 1572 pktcNcsEndPntConfigCriticalDialTO Integer32, 1573 pktcNcsEndPntConfigBusyToneTO Integer32, 1574 pktcNcsEndPntConfigDialToneTO Integer32, 1575 pktcNcsEndPntConfigMessageWaitingTO Integer32, 1576 pktcNcsEndPntConfigOffHookWarnToneTO Integer32, 1577 pktcNcsEndPntConfigRingingTO Integer32, 1578 pktcNcsEndPntConfigRingBackTO Integer32, 1579 pktcNcsEndPntConfigReorderToneTO Integer32, 1580 pktcNcsEndPntConfigStutterDialToneTO Integer32, 1581 pktcNcsEndPntConfigTSMax Integer32, 1582 pktcNcsEndPntConfigMax1 Integer32, 1583 pktcNcsEndPntConfigMax2 Integer32, 1584 pktcNcsEndPntConfigMax1QEnable TruthValue, 1585 pktcNcsEndPntConfigMax2QEnable TruthValue, 1586 pktcNcsEndPntConfigMWD Integer32, 1587 pktcNcsEndPntConfigTdinit Integer32, 1588 pktcNcsEndPntConfigTdmin Integer32, 1589 pktcNcsEndPntConfigTdmax Integer32, 1590 pktcNcsEndPntConfigRtoMax Integer32, 1591 pktcNcsEndPntConfigRtoInit Integer32, 1592 pktcNcsEndPntConfigLongDurationKeepAlive Integer32, 1593 pktcNcsEndPntConfigThist Integer32, 1594 pktcNcsEndPntConfigStatus RowStatus, 1595 pktcNcsEndPntConfigCallWaitingMaxRep Integer32, 1596 pktcNcsEndPntConfigCallWaitingDelay Integer32, 1597 pktcNcsEndPntStatusCallIpAddressType InetAddressType, 1598 pktcNcsEndPntStatusCallIpAddress InetAddress, 1599 pktcNcsEndPntStatusError INTEGER, 1600 pktcNcsEndPntConfigMinHookFlash Integer32, 1601 pktcNcsEndPntConfigMaxHookFlash Integer32, 1602 pktcNcsEndPntConfigPulseDialInterdigitTime Integer32, 1603 pktcNcsEndPntConfigPulseDialMinMakeTime Integer32, 1604 pktcNcsEndPntConfigPulseDialMaxMakeTime Integer32, 1605 pktcNcsEndPntConfigPulseDialMinBreakTime Integer32, 1606 pktcNcsEndPntConfigPulseDialMaxBreakTime Integer32, 1607 pktcNcsEndPntConfigNomJitterBufferSize Integer32, 1608 pktcNcsEndPntConfigMaxJitterBufferSize Integer32, 1609 pktcNcsEndPntConfigOnHookDebounce Integer32, 1610 pktcNcsEndPntConfigOffHookDebounce Integer32, 1611 pktcNcsEndPntConfigTxGain Integer32, 1612 pktcNcsEndPntConfigRxGain Integer32 1613 } 1615 pktcNcsEndPntConfigCallAgentId OBJECT-TYPE 1616 SYNTAX SnmpAdminString(SIZE (3..255)) 1617 MAX-ACCESS read-create 1618 STATUS current 1619 DESCRIPTION 1620 " This object contains a string indicating the call agent name. 1621 (ex: ca@abc.def.com). The call agent name after the @ 1622 character must be a fully qualified domain name and have 1623 a corresponding pktcMtaDevCmsFqdn entry in pktcMtaDevCmsTable" 1624 ::= { pktcNcsEndPntConfigEntry 1 } 1626 pktcNcsEndPntConfigCallAgentUdpPort OBJECT-TYPE 1627 SYNTAX InetPortNumber (1025..65535) 1628 MAX-ACCESS read-create 1629 STATUS current 1630 DESCRIPTION 1631 " This object contains the call agent User Datagram Protocol 1632 (UDP) receive port that is being used for this instance of 1633 call signaling, i.e. the default port on which the call agent 1634 will receive NCS signaling from the gateway." 1635 REFERENCE 1636 " Refer to Packetcable NCS specification [17]" 1637 DEFVAL { 2727 } 1638 ::= { pktcNcsEndPntConfigEntry 2 } 1640 pktcNcsEndPntConfigPartialDialTO OBJECT-TYPE 1641 SYNTAX Integer32 1642 UNITS "seconds" 1643 MAX-ACCESS read-create 1644 STATUS current 1645 DESCRIPTION 1646 " This object contains maximum value of the partial 1647 dial time out." 1648 REFERENCE 1649 " Refer to Packetcable NCS specification [17]" 1650 DEFVAL { 16 } 1651 ::= { pktcNcsEndPntConfigEntry 3 } 1653 pktcNcsEndPntConfigCriticalDialTO OBJECT-TYPE 1654 SYNTAX Integer32 1655 UNITS "seconds" 1656 MAX-ACCESS read-create 1657 STATUS current 1658 DESCRIPTION 1659 " This object contains the maximum value of the critical 1660 dial time out." 1661 REFERENCE 1662 " Refer to Packetcable NCS specification [17]" 1663 DEFVAL { 4 } 1664 ::= { pktcNcsEndPntConfigEntry 4 } 1666 pktcNcsEndPntConfigBusyToneTO OBJECT-TYPE 1667 SYNTAX Integer32 1668 UNITS "seconds" 1669 MAX-ACCESS read-create 1670 STATUS current 1671 DESCRIPTION 1672 " This object contains the timeout value for busy tone." 1673 REFERENCE 1674 " Refer to Packetcable NCS specification [17]" 1675 DEFVAL { 30 } 1676 ::= { pktcNcsEndPntConfigEntry 5 } 1678 pktcNcsEndPntConfigDialToneTO OBJECT-TYPE 1679 SYNTAX Integer32 1680 UNITS "seconds" 1681 MAX-ACCESS read-create 1682 STATUS current 1683 DESCRIPTION 1684 " This object contains the timeout value for dial tone." 1685 REFERENCE 1686 " Refer to Packetcable NCS specification [17]" 1687 DEFVAL { 16 } 1688 ::= { pktcNcsEndPntConfigEntry 6 } 1690 pktcNcsEndPntConfigMessageWaitingTO OBJECT-TYPE 1691 SYNTAX Integer32 1692 UNITS "seconds" 1693 MAX-ACCESS read-create 1694 STATUS current 1695 DESCRIPTION 1696 " This object contains the timeout value for message 1697 waiting indicator." 1698 REFERENCE 1699 " Refer to Packetcable NCS specification [17]" 1700 DEFVAL { 16 } 1701 ::= { pktcNcsEndPntConfigEntry 7 } 1703 pktcNcsEndPntConfigOffHookWarnToneTO OBJECT-TYPE 1704 SYNTAX Integer32 1705 UNITS "seconds" 1706 MAX-ACCESS read-create 1707 STATUS current 1708 DESCRIPTION 1709 " This object contains timeout value for off hook Warning tone" 1710 REFERENCE 1711 " Refer to Packetcable NCS specification [17]" 1712 DEFVAL { 0 } 1713 ::= { pktcNcsEndPntConfigEntry 8 } 1715 pktcNcsEndPntConfigRingingTO OBJECT-TYPE 1716 SYNTAX Integer32 1717 UNITS "seconds" 1718 MAX-ACCESS read-create 1719 STATUS current 1720 DESCRIPTION 1721 " This object contains the timeout value for ringing." 1722 REFERENCE 1723 " Refer to Packetcable NCS specification [17]" 1724 DEFVAL { 180 } 1725 ::= { pktcNcsEndPntConfigEntry 9 } 1727 pktcNcsEndPntConfigRingBackTO OBJECT-TYPE 1728 SYNTAX Integer32 1729 UNITS "seconds" 1730 MAX-ACCESS read-create 1731 STATUS current 1732 DESCRIPTION 1733 " This object contains the timeout value for ring back." 1734 REFERENCE 1735 " Refer to Packetcable NCS specification [17]" 1736 DEFVAL { 180 } 1737 ::= { pktcNcsEndPntConfigEntry 10 } 1739 pktcNcsEndPntConfigReorderToneTO OBJECT-TYPE 1740 SYNTAX Integer32 1741 UNITS "seconds" 1742 MAX-ACCESS read-create 1743 STATUS current 1744 DESCRIPTION 1745 " This object contains the timeout value for reorder tone." 1746 REFERENCE 1747 " Refer to Packetcable NCS specification [17]" 1748 DEFVAL { 30 } 1749 ::= { pktcNcsEndPntConfigEntry 11 } 1751 pktcNcsEndPntConfigStutterDialToneTO OBJECT-TYPE 1752 SYNTAX Integer32 1753 UNITS "seconds" 1754 MAX-ACCESS read-create 1755 STATUS current 1756 DESCRIPTION 1757 " This object contains timeout value for stutter dial tone." 1758 REFERENCE 1759 "Refer to Packetcable NCS specification [17]" 1760 DEFVAL { 16 } 1761 ::= { pktcNcsEndPntConfigEntry 12 } 1763 pktcNcsEndPntConfigTSMax OBJECT-TYPE 1764 SYNTAX Integer32 1765 MAX-ACCESS read-create 1766 STATUS current 1767 DESCRIPTION 1768 " This object contains the max time in seconds since the 1769 sending of the initial datagram." 1770 REFERENCE 1771 " Refer to Packetcable NCS specification [17]" 1772 DEFVAL { 20 } 1773 ::= { pktcNcsEndPntConfigEntry 13 } 1775 pktcNcsEndPntConfigMax1 OBJECT-TYPE 1776 SYNTAX Integer32 1777 MAX-ACCESS read-create 1778 STATUS current 1779 DESCRIPTION 1780 " This object contains the suspicious error threshold 1781 for signaling messages." 1782 REFERENCE 1783 " Refer to Packetcable NCS specification [17]" 1784 DEFVAL { 5 } 1785 ::= { pktcNcsEndPntConfigEntry 14 } 1787 pktcNcsEndPntConfigMax2 OBJECT-TYPE 1788 SYNTAX Integer32 1789 MAX-ACCESS read-create 1790 STATUS current 1791 DESCRIPTION 1792 " This object contains the disconnect error 1793 threshold for signaling messages." 1794 REFERENCE 1795 " Refer to Packetcable NCS specification [17]" 1796 DEFVAL { 7 } 1797 ::= { pktcNcsEndPntConfigEntry 15 } 1799 pktcNcsEndPntConfigMax1QEnable OBJECT-TYPE 1800 SYNTAX TruthValue 1801 MAX-ACCESS read-create 1802 STATUS current 1803 DESCRIPTION 1804 " This object enables/disables the Max1 Domain Name 1805 Server (DNS) query operation when Max1 expires." 1806 DEFVAL { true } 1807 ::= { pktcNcsEndPntConfigEntry 16 } 1809 pktcNcsEndPntConfigMax2QEnable OBJECT-TYPE 1810 SYNTAX TruthValue 1811 MAX-ACCESS read-create 1812 STATUS current 1813 DESCRIPTION 1814 " This object enables/disables the Max2 DNS query 1815 operation when Max2 expires." 1816 DEFVAL { true } 1817 ::= { pktcNcsEndPntConfigEntry 17 } 1819 pktcNcsEndPntConfigMWD OBJECT-TYPE 1820 SYNTAX Integer32 1821 UNITS "seconds" 1822 MAX-ACCESS read-create 1823 STATUS current 1824 DESCRIPTION 1825 " Maximum Waiting Delay (MWD) contains the maximum 1826 number of seconds a MTA waits after a restart." 1827 REFERENCE 1828 " Refer to Packetcable NCS specification [17]" 1829 DEFVAL { 600 } 1830 ::= { pktcNcsEndPntConfigEntry 18 } 1832 pktcNcsEndPntConfigTdinit OBJECT-TYPE 1833 SYNTAX Integer32 1834 UNITS "seconds" 1835 MAX-ACCESS read-create 1836 STATUS current 1837 DESCRIPTION 1838 " This object contains the initial number of seconds 1839 a MTA waits after a disconnect." 1840 REFERENCE 1841 " Refer to Packetcable NCS specification [17]" 1842 DEFVAL { 15 } 1843 ::= { pktcNcsEndPntConfigEntry 19 } 1845 pktcNcsEndPntConfigTdmin OBJECT-TYPE 1846 SYNTAX Integer32 1847 UNITS "seconds" 1848 MAX-ACCESS read-create 1849 STATUS current 1850 DESCRIPTION 1851 " This object contains the minimum number of 1852 seconds a MTA waits after a disconnect." 1853 REFERENCE 1854 " Refer to Packetcable NCS specification [17]" 1855 DEFVAL { 15 } 1856 ::= { pktcNcsEndPntConfigEntry 20 } 1858 pktcNcsEndPntConfigTdmax OBJECT-TYPE 1859 SYNTAX Integer32 1860 UNITS "seconds" 1861 MAX-ACCESS read-create 1862 STATUS current 1863 DESCRIPTION 1864 " This object contains the maximum number of seconds 1865 a MTA waits after a disconnect." 1866 REFERENCE 1867 " Refer to Packetcable NCS specification [17]" 1868 DEFVAL { 600 } 1869 ::= { pktcNcsEndPntConfigEntry 21 } 1871 pktcNcsEndPntConfigRtoMax OBJECT-TYPE 1872 SYNTAX Integer32 1873 UNITS "seconds" 1874 MAX-ACCESS read-create 1875 STATUS current 1876 DESCRIPTION 1877 " This object contains the maximum number of seconds 1878 for the retansmission timer." 1879 REFERENCE 1880 " Refer to Packetcable NCS specification [17]" 1881 DEFVAL { 4 } 1882 ::= { pktcNcsEndPntConfigEntry 22 } 1884 pktcNcsEndPntConfigRtoInit OBJECT-TYPE 1885 SYNTAX Integer32 1886 UNITS "milliseconds" 1887 MAX-ACCESS read-create 1888 STATUS current 1889 DESCRIPTION 1890 " This object contains the initial number of seconds 1891 for the retransmission timer." 1892 REFERENCE 1893 " Refer to Packetcable NCS specification [17]" 1894 DEFVAL { 200 } 1895 ::= { pktcNcsEndPntConfigEntry 23 } 1897 pktcNcsEndPntConfigLongDurationKeepAlive OBJECT-TYPE 1898 SYNTAX Integer32 1899 UNITS "minutes" 1900 MAX-ACCESS read-create 1901 STATUS current 1902 DESCRIPTION 1903 " Specifies a timeout value in minutes for sending 1904 long duration call notification message." 1905 REFERENCE 1906 " Refer to Packetcable NCS specification [17]" 1907 DEFVAL { 60 } 1908 ::= { pktcNcsEndPntConfigEntry 24 } 1910 pktcNcsEndPntConfigThist OBJECT-TYPE 1911 SYNTAX Integer32 1912 UNITS "seconds" 1913 MAX-ACCESS read-create 1914 STATUS current 1915 DESCRIPTION 1916 " Timeout period in seconds before no response is declared." 1917 REFERENCE 1918 "Refer to Packetcable NCS specification [17]" 1919 DEFVAL { 30 } 1920 ::= { pktcNcsEndPntConfigEntry 25 } 1922 pktcNcsEndPntConfigStatus OBJECT-TYPE 1923 SYNTAX RowStatus 1924 MAX-ACCESS read-create 1925 STATUS current 1926 DESCRIPTION 1927 " This object contains the Row Status associated with 1928 the pktsNcsEndPntTable." 1929 ::= { pktcNcsEndPntConfigEntry 26 } 1931 pktcNcsEndPntConfigCallWaitingMaxRep OBJECT-TYPE 1932 SYNTAX Integer32 (0..10) 1933 MAX-ACCESS read-create 1934 STATUS current 1935 DESCRIPTION 1936 " This object contains the maximum number of repetitions 1937 of the call waiting tone that the MTA will play from a 1938 single CMS request. A value of zero (0) can be used if 1939 the CMS is to control the repetitions of the call 1940 waiting tone." 1941 DEFVAL { 1 } 1942 ::= { pktcNcsEndPntConfigEntry 27 } 1944 pktcNcsEndPntConfigCallWaitingDelay OBJECT-TYPE 1945 SYNTAX Integer32 (1..100) 1946 UNITS "seconds" 1947 MAX-ACCESS read-create 1948 STATUS current 1949 DESCRIPTION 1950 " This object contains the delay between repretitions 1951 of the call waiting tone that the MTA will play from 1952 a single CMS request." 1953 DEFVAL { 10 } 1954 ::= { pktcNcsEndPntConfigEntry 28 } 1956 pktcNcsEndPntStatusCallIpAddressType OBJECT-TYPE 1957 SYNTAX InetAddressType 1958 MAX-ACCESS read-only 1959 STATUS current 1960 DESCRIPTION 1961 " This object contains the type of Internet address of 1962 the CMS currently being used for this endpoint." 1963 ::= { pktcNcsEndPntConfigEntry 44 } 1965 pktcNcsEndPntStatusCallIpAddress OBJECT-TYPE 1966 SYNTAX InetAddress 1967 MAX-ACCESS read-only 1968 STATUS current 1969 DESCRIPTION 1970 " This object contains the Internet address of 1971 the CMS currently being used for this endpoint. 1973 This Internet address is used to create the 1974 appropriate security association." 1975 ::= { pktcNcsEndPntConfigEntry 29 } 1977 pktcNcsEndPntStatusError OBJECT-TYPE 1978 SYNTAX INTEGER { 1979 operational (1), 1980 noSecurityAssociation (2), 1981 disconnected (3) 1982 } 1983 MAX-ACCESS read-only 1984 STATUS current 1985 DESCRIPTION 1986 " This object contains the error status of the interface: 1987 The 'operational' state indicates that all operations 1988 necessary to put the line in service have occurred. 1989 The 'noSecurityAssociation' status indicates that no 1990 security association yet exists for this endpoint. 1991 The 'disconnected' status indicates that the Security 1992 Association has been established and the NCS signaling 1993 Software is process of establishing the NCS signaling 1994 Link via an RSIP exchange." 1995 ::= { pktcNcsEndPntConfigEntry 30 } 1997 pktcNcsEndPntConfigMinHookFlash OBJECT-TYPE 1998 SYNTAX Integer32 (1..1000) 1999 UNITS "Milliseconds" 2000 MAX-ACCESS read-create 2001 STATUS current 2002 DESCRIPTION 2003 " This is the minimum time a line needs to be on hook for a valid 2004 hook flash." 2005 DEFVAL { 300 } 2006 ::= { pktcNcsEndPntConfigEntry 31 } 2008 pktcNcsEndPntConfigMaxHookFlash OBJECT-TYPE 2009 SYNTAX Integer32 (1..1800) 2010 UNITS "Milliseconds" 2011 MAX-ACCESS read-create 2012 STATUS current 2013 DESCRIPTION 2014 " This is the maximum time a line needs to be on hook for a valid 2015 hook flash." 2016 DEFVAL { 1000 } 2017 ::= { pktcNcsEndPntConfigEntry 32 } 2019 pktcNcsEndPntConfigPulseDialInterdigitTime OBJECT-TYPE 2020 SYNTAX Integer32 (100..1500) 2021 UNITS "Milliseconds" 2022 MAX-ACCESS read-create 2023 STATUS current 2024 DESCRIPTION 2025 " This is the pulse dial inter-digit timeout." 2026 DEFVAL { 100 } 2027 ::= { pktcNcsEndPntConfigEntry 33 } 2029 pktcNcsEndPntConfigPulseDialMinMakeTime OBJECT-TYPE 2030 SYNTAX Integer32 (1..200) 2031 UNITS "Milliseconds" 2032 MAX-ACCESS read-create 2033 STATUS current 2034 DESCRIPTION 2035 " This is the minimum make pulse width for the dial pulse." 2036 DEFVAL { 25 } 2037 ::= { pktcNcsEndPntConfigEntry 34 } 2039 pktcNcsEndPntConfigPulseDialMaxMakeTime OBJECT-TYPE 2040 SYNTAX Integer32 (1..200) 2041 UNITS "Milliseconds" 2042 MAX-ACCESS read-create 2043 STATUS current 2044 DESCRIPTION 2045 " This is the maximum make pulse width for the dial pulse." 2046 DEFVAL { 55 } 2047 ::= { pktcNcsEndPntConfigEntry 35 } 2049 pktcNcsEndPntConfigPulseDialMinBreakTime OBJECT-TYPE 2050 SYNTAX Integer32 (1..200) 2051 UNITS "Milliseconds" 2052 MAX-ACCESS read-create 2053 STATUS current 2054 DESCRIPTION 2055 " This is the minimum break pulse width for the dial pulse." 2056 DEFVAL { 45 } 2057 ::= { pktcNcsEndPntConfigEntry 36 } 2059 pktcNcsEndPntConfigPulseDialMaxBreakTime OBJECT-TYPE 2060 SYNTAX Integer32 (1..200) 2061 UNITS "Milliseconds" 2062 MAX-ACCESS read-create 2063 STATUS current 2064 DESCRIPTION 2065 " This is the maximum break pulse width for the dial pulse." 2066 DEFVAL { 75 } 2067 ::= { pktcNcsEndPntConfigEntry 37 } 2069 pktcNcsEndPntConfigNomJitterBufferSize OBJECT-TYPE 2070 SYNTAX Integer32 2071 UNITS "Milliseconds" 2072 MAX-ACCESS read-create 2073 STATUS current 2074 DESCRIPTION 2075 " The current setting for the nominal amount of jitter the 2076 bti can compensate." 2078 ::= { pktcNcsEndPntConfigEntry 38 } 2080 pktcNcsEndPntConfigMaxJitterBufferSize OBJECT-TYPE 2081 SYNTAX Integer32 2082 UNITS "Milliseconds" 2083 MAX-ACCESS read-create 2084 STATUS current 2085 DESCRIPTION 2086 " The current setting for the maximum amount of jitter the 2087 bti can compensate ." 2088 ::= { pktcNcsEndPntConfigEntry 39 } 2090 pktcNcsEndPntConfigOnHookDebounce OBJECT-TYPE 2091 SYNTAX Integer32 (1..1000) 2092 UNITS "Milliseconds" 2093 MAX-ACCESS read-create 2094 STATUS current 2095 DESCRIPTION 2096 " The length of the on-hook debounce." 2097 DEFVAL { 200 } 2098 ::= { pktcNcsEndPntConfigEntry 40 } 2100 pktcNcsEndPntConfigOffHookDebounce OBJECT-TYPE 2101 SYNTAX Integer32 (1..1000) 2102 UNITS "Milliseconds" 2103 MAX-ACCESS read-create 2104 STATUS current 2105 DESCRIPTION 2106 " The length of the off hook debounce." 2107 DEFVAL { 100 } 2108 ::= { pktcNcsEndPntConfigEntry 41 } 2110 pktcNcsEndPntConfigTxGain OBJECT-TYPE 2111 SYNTAX Integer32 (-14..14) 2112 UNITS "dB" 2113 MAX-ACCESS read-create 2114 STATUS current 2115 DESCRIPTION 2116 " The per line transmitter gain." 2117 DEFVAL { 0 } 2118 ::= { pktcNcsEndPntConfigEntry 42 } 2120 pktcNcsEndPntConfigRxGain OBJECT-TYPE 2121 SYNTAX Integer32 (-14..14) 2122 UNITS "dB" 2123 MAX-ACCESS read-create 2124 STATUS current 2125 DESCRIPTION 2126 " The per line receiver gain." 2127 DEFVAL { 0 } 2128 ::= { pktcNcsEndPntConfigEntry 43 } 2130 -- 2131 -- notification group is for future extension. 2132 -- 2133 pktcSigNotification OBJECT IDENTIFIER ::= { pktcSigMib 2 } 2134 pktcSigConformance OBJECT IDENTIFIER ::= { pktcSigMib 3 } 2135 pktcSigCompliances OBJECT IDENTIFIER ::= { pktcSigConformance 1 } 2136 pktcSigGroups OBJECT IDENTIFIER ::= { pktcSigConformance 2 } 2138 -- compliance statements 2140 pktcSigBasicCompliance MODULE-COMPLIANCE 2141 STATUS current 2142 DESCRIPTION 2143 " The compliance statement for devices that implement 2144 Signaling on the MTA." 2146 MODULE -- pktcSigMib 2148 -- unconditionally mandatory groups 2150 MANDATORY-GROUPS { 2151 pktcSigGroup 2152 } 2153 GROUP pktcNcsGroup 2154 DESCRIPTION 2155 " This group is mandatory for any MTA implementing NCS signaling" 2156 ::={ pktcSigCompliances 1 } 2158 -- units of conformance 2160 pktcSigGroup OBJECT-GROUP 2161 OBJECTS { 2162 pktcSigDevCodecType, 2163 pktcSigDevCodecMax, 2164 pktcSigDevEchoCancellation, 2165 pktcSigDevSilenceSuppression, 2166 pktcSigDevConnectionMode, 2167 pktcSigDevR0Cadence, 2168 pktcSigDevR6Cadence, 2169 pktcSigDevR7Cadence, 2170 pktcSigDefCallSigTos, 2171 pktcSigDefMediaStreamTos, 2172 pktcSigTosFormatSelector, 2173 pktcSignalingType, 2174 pktcSignalingVersion, 2175 pktcSignalingVendorExtension, 2176 pktcSigEndPntCapabilityIndex, 2177 pktcSigDefNcsReceiveUdpPort, 2178 pktcSigServiceClassNameUS, 2179 pktcSigServiceClassNameDS, 2180 pktcSigServiceClassNameMask, 2181 pktcSigNcsServiceFlowState, 2182 pktcSigDevR1Cadence, 2183 pktcSigDevR2Cadence, 2184 pktcSigDevR3Cadence, 2185 pktcSigDevR4Cadence, 2186 pktcSigDevR5Cadence, 2187 pktcSigDevRgCadence, 2188 pktcSigDevRsCadence, 2189 pktcSigDevRtCadence 2190 } 2191 STATUS current 2192 DESCRIPTION 2193 "Group of objects for the common portion of the 2194 PacketCable Signaling MIB." 2195 ::= { pktcSigGroups 1 } 2197 pktcNcsGroup OBJECT-GROUP 2198 OBJECTS { 2199 pktcNcsEndPntConfigCallAgentId, 2200 pktcNcsEndPntConfigCallAgentUdpPort, 2201 pktcNcsEndPntConfigPartialDialTO, 2202 pktcNcsEndPntConfigCriticalDialTO, 2203 pktcNcsEndPntConfigBusyToneTO, 2204 pktcNcsEndPntConfigDialToneTO, 2205 pktcNcsEndPntConfigMessageWaitingTO, 2206 pktcNcsEndPntConfigOffHookWarnToneTO, 2207 pktcNcsEndPntConfigRingingTO, 2208 pktcNcsEndPntConfigRingBackTO, 2209 pktcNcsEndPntConfigReorderToneTO, 2210 pktcNcsEndPntConfigStutterDialToneTO, 2211 pktcNcsEndPntConfigTSMax, 2212 pktcNcsEndPntConfigMax1, 2213 pktcNcsEndPntConfigMax2, 2214 pktcNcsEndPntConfigMax1QEnable, 2215 pktcNcsEndPntConfigMax2QEnable, 2216 pktcNcsEndPntConfigMWD, 2217 pktcNcsEndPntConfigTdinit, 2218 pktcNcsEndPntConfigTdmin, 2219 pktcNcsEndPntConfigTdmax, 2220 pktcNcsEndPntConfigRtoMax, 2221 pktcNcsEndPntConfigRtoInit, 2222 pktcNcsEndPntConfigLongDurationKeepAlive, 2223 pktcNcsEndPntConfigThist, 2224 pktcNcsEndPntConfigStatus, 2225 pktcNcsEndPntConfigCallWaitingMaxRep, 2226 pktcNcsEndPntConfigCallWaitingDelay, 2227 pktcNcsEndPntStatusCallIpAddressType, 2228 pktcNcsEndPntStatusCallIpAddress, 2229 pktcNcsEndPntStatusError 2230 } 2231 STATUS current 2232 DESCRIPTION 2233 "Group of objects for the NCS portion of the 2234 PacketCable Signaling MIB. This is mandatory for 2235 NCS signaling." 2236 ::= { pktcSigGroups 2 } 2238 pktcInternationalGroup OBJECT-GROUP 2239 OBJECTS { 2240 pktcNcsEndPntConfigMinHookFlash, 2241 pktcNcsEndPntConfigMaxHookFlash, 2242 pktcNcsEndPntConfigNomJitterBufferSize, 2243 pktcNcsEndPntConfigMaxJitterBufferSize, 2244 pktcNcsEndPntConfigOnHookDebounce, 2245 pktcNcsEndPntConfigOffHookDebounce, 2246 pktcNcsEndPntConfigTxGain, 2247 pktcNcsEndPntConfigRxGain, 2248 pktcNcsEndPntConfigPulseDialInterdigitTime, 2249 pktcNcsEndPntConfigPulseDialMinMakeTime, 2250 pktcNcsEndPntConfigPulseDialMaxMakeTime, 2251 pktcNcsEndPntConfigPulseDialMinBreakTime, 2252 pktcNcsEndPntConfigPulseDialMaxBreakTime, 2253 pktcSigDevRingCadence, 2254 pktcSigDevStandardRingCadence, 2255 pktcSigDevRingSplashCadence, 2256 pktcSigDevCIDMode, 2257 pktcSigDevCIDFskAfterRing, 2258 pktcSigDevCIDFskAfterDTAS, 2259 pktcSigDevCIDRingAfterFSK, 2260 pktcSigDevCIDDTASAfterLR, 2261 pktcSigPowerRingFrequency, 2262 pktcSigPCMCoding, 2263 pktcSigPulseSignalDuration, 2264 pktcSigPulseSignalType, 2265 pktcSigPulseSignalDbLevel, 2266 pktcSigPulseSignalFrequency, 2267 pktcSigPulseSignalRepeatCount, 2268 pktcSigPulseSignalPauseDuration, 2269 pktcSigDevToneType, 2270 pktcSigDevToneDbLevel, 2271 pktcSigDevToneFreqType, 2272 pktcSigDevToneNumFrequencies, 2273 pktcSigDevToneFirstFrequency, 2274 pktcSigDevToneSecondFrequency, 2275 pktcSigDevToneThirdFrequency, 2276 pktcSigDevToneFourthFrequency, 2277 pktcSigDevToneNumOnOffTimes, 2278 pktcSigDevToneFirstToneOn, 2279 pktcSigDevToneFirstToneOff, 2280 pktcSigDevToneSecondToneOn, 2281 pktcSigDevToneSecondToneOff, 2282 pktcSigDevToneThirdToneOn, 2283 pktcSigDevToneThirdToneOff, 2284 pktcSigDevToneFourthToneOn, 2285 pktcSigDevToneFourthToneOff, 2286 pktcSigDevToneWholeToneRepeatCount, 2287 pktcSigDevToneSteady 2288 } 2289 STATUS current 2290 DESCRIPTION 2291 " Group of objects that extend the behavior of existing 2292 objects to support operations in the widest possible 2293 set of international marketplaces. Note that many of 2294 these objects represent a superset of behaviors described 2295 in other objects within this MIB Module. In such cases, 2296 it is left to manufacturers to determine whether to 2297 support both objects in the same device." 2298 ::= { pktcSigGroups 3 } 2300 END 2302 5. Acknowledgments 2303 This document is a production of the PacketCable Working Group. 2305 The current editors wish to express gratitude to: 2307 Angela Lyda Arris Interactive 2308 Sasha Medvinsky Motorola 2309 Roy Spitzer Telogy Networks, Inc. 2310 Rick Vetter Motorola 2311 Itay Sherman Texas Instruments 2312 Klaus Hermanns Cisco Systems 2313 Eugene Nechamkin Broadcom Corp 2314 Matt A. Osman CableLabs 2315 Jean-Francois Mule CableLabs 2317 6. References 2319 [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for 2320 Describing SNMP Management Frameworks", RFC 2571, April 1999. 2322 [2] Rose, M. and K. McCloghrie, "Structure and Identification of 2323 Management Information for TCP/IP-based Internets", STD 16, RFC 2324 1155, May 1990. 2326 [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, 2327 RFC 1212, March 1991. 2329 [4] Rose, M., "A Convention for Defining Traps for use with the 2330 SNMP", RFC 1215, March 1991. 2332 [5] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of 2333 Management Information for Version 2 (SMIv2)", STD 58, RFC 2578, 2334 April 1999. 2336 [6] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual 2337 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 2339 [7] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance 2340 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2342 [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 2343 Management Protocol", STD 15, RFC 1157, May 1990. 2345 [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 2346 "Introduction to Community-based SNMPv2", RFC 1901, January 2347 1996. 2349 [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport 2350 Mappings for Version 2 of the Simple Network Management Protocol 2351 (SNMPv2)", RFC 1906, January 1996. 2353 [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 2354 Processing and Dispatching for the Simple Network Management 2355 Protocol (SNMP)", RFC 2572, April 1999. 2357 [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) 2358 for version 3 of the Simple Network Management Protocol 2359 (SNMPv3)", RFC 2574, April 1999. 2361 [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol 2362 Operations for Version 2 of the Simple Network Management 2363 Protocol (SNMPv2)", RFC 1905, January 1996. 2365 [14] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2366 2573, April 1999. 2368 [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 2369 Control Model (VACM) for the Simple Network Management Protocol 2370 (SNMP)", RFC 2575, April 1999. 2372 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, 2373 "Introduction to Version 3 of the Internet-standard Network 2374 Management Framework", RFC 2570, April 1999. 2376 [17] Packetcable Network-Based Call Signaling protocol Specification 2377 PKT-SP-EC-MGCP-IO4-011221. 2379 [18] Bradner, S., "The Internet Standards Process, Revision 3", 2380 RFC 2026, October 1996. 2382 [19] ETSI TS 101 909-4:"Access and Terminals (AT); Digital Broadband 2383 Cable Access to the Public Telecommunications Network; IP 2384 Multimedia Time Critical Services; Part 4: Network Call 2385 Signalling Protocol". 2387 [20] ETSI TS 101 909-9:"Access and Terminals (AT); Digital Broadband 2388 Cable Access to the Public Telecommunications Network; IP 2389 Multimedia Time Critical Services; Part 9: IPCablecom Network 2390 Call Signalling (NCS) MIB Requirements". 2392 [21] EN 300 001 V1.5.1 (1998-10):"European Standard (Telecommunications 2393 series) Attachments to Public Switched Telephone Network (PSTN); 2394 General technical requirements for equipment connected to an 2395 analogue subscriber interface in the PSTN; Chapter 3: Ringing 2396 signal characteristics (national deviations are in Table 3.1.1)". 2398 7. Security Considerations 2400 This MIB relates to a system which will provide metropolitan public 2401 telephony service. As such, improper manipulation of the objects 2402 represented by this MIB may result in random behavior of MTA. 2403 Improper manipulation of certain tables can result in failure to 2404 get telephony service from client(MTA) device. 2406 SNMPv1 by itself is not a secure environment. Even if the network 2407 itself is secure (for example by using IPSec), even then, there is no 2408 control as to who on the secure network is allowed to access and 2409 GET/SET (read/change/create/delete) the objects in this MIB. 2411 It is recommended that the implementers consider the security 2412 features as provided by the SNMPv3 framework. Specifically, the use 2413 of the User-based Security Model RFC 2574 [12] and the View- based 2414 Access Control Model RFC 2575 [15] is recommended. 2416 It is then a customer/user responsibility to ensure that the SNMP 2417 entity giving access to an instance of this MIB, is properly 2418 configured to give access to the objects only to those principals 2419 (users) that have legitimate rights to indeed GET or SET 2420 (change/create/delete) them. 2422 8. Intellectual Property 2424 The IETF takes no position regarding the validity or scope of any 2425 intellectual property or other rights that might be claimed to 2426 pertain to the implementation or use of the technology described in 2427 this document or the extent to which any license under such rights 2428 might or might not be available; neither does it represent that it 2429 has made any effort to identify any such rights. Information on the 2430 IETF's procedures with respect to rights in standards-track and 2431 standards-related documentation can be found in BCP-11. Copies of 2432 claims of rights made available for publication and any assurances of 2433 licenses to be made available, or the result of an attempt made to 2434 obtain a general license or permission for the use of such 2435 proprietary rights by implementers or users of this specification can 2436 be obtained from the IETF Secretariat. 2438 The IETF invites any interested party to bring to its attention any 2439 copyrights, patents or patent applications, or other proprietary 2440 rights that may cover technology that may be required to practice 2441 this standard. Please address the information to the IETF Executive 2442 Director. 2444 9. Authors' Addresses 2446 Charles Schell 2447 Motorola BCS/IPNS 2448 101 Tournament Drive, Bldg. 3 2449 Horsham, PA 19044, USA 2450 +1 215-323-1145 2451 cschell@motorola.com 2453 Satish Kumar Mudugere Eswaraiah 2454 Texas Instruments India (P) Ltd., 2455 Golf view, Wind Tunnel Road 2456 Murugesh Palya 2457 Bangalore - - 560 017, INDIA 2458 +91 80 5269451 2459 satish.kumar@ti.com 2461 Sumanth Channabasappa 2462 Alopa Networks Inc 2463 248, McCaslin Bvld #101, 2464 Louisville, Colorado - 80027 2465 U.S.A. 2466 +1 303 604 6595 2467 Sumanth@alopa.com 2469 10. Full Copyright Statement 2471 Copyright (C) The Internet Society (2002). All Rights Reserved. 2473 This document and translations of it may be copied and furnished to 2474 others, and derivative works that comment on or otherwise explain it 2475 or assist in its implementation may be prepared, copied, published 2476 and distributed, in whole or in part, without restriction of any 2477 kind, provided that the above copyright notice and this paragraph are 2478 included on all such copies and derivative works. However, this 2479 document itself may not be modified in any way, such as by removing 2480 the copyright notice or references to the Internet Society or other 2481 Internet organizations, except as needed for the purpose of 2482 developing Internet standards in which case the procedures for 2483 copyrights defined in the Internet Standards process must be 2484 followed, or as required to translate it into languages other than 2485 English. 2487 The limited permissions granted above are perpetual and will not be 2488 revoked by the Internet Society or its successors or assigns. 2490 This document and the information contained herein is provided on an 2491 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2492 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2493 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2494 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2495 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.