idnits 2.17.1 draft-ietf-isdnmib-dial-control-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** 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 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 407: '... Several entries for one neighbor MUST...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 141 has weird spacing: '...|switch shad...' -- 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 () is 739377 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: '5' is defined on line 1276, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 1280, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1284, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) -- Possible downref: Non-RFC (?) normative reference: ref. '5' -- Possible downref: Non-RFC (?) normative reference: ref. '6' -- Possible downref: Non-RFC (?) normative reference: ref. '7' Summary: 14 errors (**), 0 flaws (~~), 6 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Dial Control Management Information Base 2 draft-ietf-isdnmib-dial-control-04.txt 4 Sat Apr 27 10:59:38 MET DST 1996 6 Guenter Roeck (editor) 7 Conware GmbH 8 roeck@conware.de 10 Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its Areas, and 14 its Working Groups. Note that other groups may also distribute working 15 documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference material 20 or to cite them other than as a "work in progress". 22 To learn the current status of any Internet-Draft, please check the 23 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 24 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 25 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 26 ftp.isi.edu (US West Coast). 28 1. Introduction 30 This draft defines an experimental portion of the Management Information 31 Base (MIB) for use with network management protocols in the Internet 32 community. In particular, it describes managed objects used for 33 managing demand access circuits, including ISDN. 35 This document specifies a MIB module in a manner that is both compliant 36 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 37 definitions. 39 This document is a product of the ISDN MIB working group within the 40 Internet Engineering Task Force. Comments are solicited and should be 41 addressed to the working group's mailing list at isdn-mib@cisco.com 42 and/or the author. 44 2. The SNMPv2 Network Management Framework 46 The SNMPv2 Network Management Framework presently consists of three 47 major components. They are: 49 o the SMI, described in RFC 1902 [1] - the mechanisms used for 50 describing and naming objects for the purpose of management. 52 o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects 53 for the Internet suite of protocols. 55 o the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for 56 accessing managed objects. 58 The Framework permits new objects to be defined for the purpose of 59 experimentation and evaluation. 61 2.1. Object Definitions 63 Managed objects are accessed via a virtual information store, termed the 64 Management Information Base or MIB. Objects in the MIB are defined 65 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 66 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 67 an administratively assigned name. The object type together with an 68 object instance serves to uniquely identify a specific instantiation of 69 the object. For human convenience, we often use a textual string, 70 termed the descriptor, to refer to the object type. 72 3. Overview 74 3.1. Structure of MIB 76 Managing Neighbors requires the following groups of information: 78 o General configuration information. 80 o Information to describe neighbors and neighbor statistics. 82 o Information to retain call history. 84 The MIB, therefore, consists of three groups. 86 o The dialCtlConfiguration group is used to specify general 87 configuration information. 89 o The dialCtlNeighbor group is used to describe neighbors and 90 neighbor statistics. 92 o The callHistory group is used to store call history information. 93 These calls could be circuit switched or they could be virtual 94 circuits. History of each and every call is stored, of successful 95 calls as well as unsuccessful and rejected calls. An entry will be 96 created when a call is cleared. 98 3.2. Relationship to RFC1573 100 RFC 1573, the Interface MIB Evolution, requires that any MIB module 101 which is an adjunct of the Interface MIB, clarify specific areas within 102 the Interface MIB. These areas were intentionally left vague in RFC 103 1573 to avoid over constraining the MIB module, thereby precluding 104 management of certain media-types. 106 Section 3.3 of RFC 1573 enumerates several areas which a media-specific 107 MIB module must clarify. Each of these areas is addressed in a 108 following subsection. The implementor is referred to RFC 1573 in order 109 to understand the general intent of these areas. 111 3.2.1. Layering Model and Virtual Circuits 113 On an occasional access channel, there are a number of neighboring 114 systems that are permitted to call or be called, all of which need to be 115 treated as active from a routing viewpoint, but most of which have no 116 call in progress at any given time. 118 On dialup interfaces, this is further complicated by the fact that calls 119 to a given neighbor float from channel to channel. One cannot 120 definitively say "I call this neighbor on that interface." It is 121 necessary, therefore, to provide a mapping algorithm between the low- 122 level interfaces, and the various logical interfaces supporting the 123 neighbors. This is solved by creating a logical interface (ifEntry) for 124 each neighbor and a logical interface (ifEntry) for each low-level 125 interface. These are then correlated using the ifStackTable. 127 The low-level interfaces will either be physical interfaces, e.g. modem 128 interfaces, or logical interfaces, e.g. ISDN B channels, which then in 129 turn will be layered on top of physical ISDN interfaces. 131 The model, therefore, looks something like this, taking ISDN as an 132 example: 134 +-------------------------------------------------------+ 135 | Network Layer Protocol | 136 +------+ +-------+ +-------+ +-------+ +-------+ +------+ 137 | | | | | | | | | | <== appears active 138 +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ 139 | PPP | | PPP | | F/R | | PPP | | F/R | 140 | for | | for | | for | | for | | for | ifEntry with 141 |Nbr 1| |Nbr 2| |switch |Nbr 3| |switch shadow 142 | | | | | A | | | | B | NeighborEntry 143 +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ 144 | | | | <== some actually are 145 +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ 146 | B | | B | | B | | B | | B | 147 |channel| |channel| |channel| |channel| |channel| 148 +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ 149 | | | | | | | | | | 150 +------+ +-------+ +-------+ +-------+ +-------+ +------+ 151 | Basic/Primary Rate Interface | 152 +-------------------------------------------------------+ 154 Mapping of IP interfaces to Called Neighbors to B Channels 156 IfEntries are maintained for each neighbor. 158 In this model, each neighbor is required to have an associated network 159 layer interface. This interface can be of any kind, e.g. PPP or LAPB. 161 In order to specify the network address for a given neighbor, one would 162 then usually add a routing/forwarding table entry, pointing to the 163 network layer interface through which this neighbor can be reached. 165 3.2.2. ifTestTable 167 The ifTestTable usage will be defined in the MIBs defining the 168 encapsulation below the network layer. For example, if PPP 169 encapsulation is being used, the ifTestTable will be defined by PPP. 171 3.2.3. ifRcvAddressTable 173 The ifRcvAddressTable usage will be defined in the MIBs defining the 174 encapsulation below the network layer. For example, if PPP 175 encapsulation is being used, the ifRcvAddressTable will be defined by 176 PPP. 178 3.2.3.1. ifEntry for a single neighbor 180 IfEntries will be defined in the MIBs defining the encapsulation below 181 the network layer. For example, if PPP encapsulation is being used, the 182 ifEntry will be defined by PPP. 184 3.3. Multilink and backup line support 186 In order to support multilink and backup procedures, there may be 187 several entries for a single neighbor in the dialCtlNbrCfgTable. 189 A single neighbor will be identified using the dialCtlNbrCfgId object of 190 the dialCtlNbrCfgTable. There may be several entries in 191 dialCtlNbrCfgTable with the same value of dialCtlNbrCfgId, but different 192 ifIndex values. Each of those entries will then describe a possible 193 connection to the same neighbor. Such entries can then be used to 194 handle multilink as well as backup procedures, e.g. by bundling the 195 attached ifEntries using PPP multilink. 197 3.4. Support for generic neighbors 199 Generic neighbors can for example be supported by permitting wild-card 200 characters (e.g., '?' or '*') in dialCtlNbrCfgAnswerAddress. A number 201 to be accepted could then be defined as partly (e.g., '*1234') or 202 entirely generic (e.g., '*'). 204 A detailed specification of such a functionality is outside the scope of 205 this document. 207 However, the implementor should be aware that supporting generic 208 neighbors may cause a security hole. The user would not know where a 209 call is from, which could potentially allow unauthorized access. 211 4. Definitions 213 4.1. Dial Control MIB 215 DIAL-CONTROL-MIB DEFINITIONS ::= BEGIN 217 IMPORTS 218 MODULE-IDENTITY, 219 NOTIFICATION-TYPE, 220 OBJECT-TYPE, 221 Counter32 222 FROM SNMPv2-SMI 223 DisplayString, 224 TimeStamp, 225 RowStatus, 226 TestAndIncr 227 FROM SNMPv2-TC 228 MODULE-COMPLIANCE, 229 OBJECT-GROUP 230 FROM SNMPv2-CONF 231 IANAifType 232 FROM IANAifType-MIB 233 ifOperStatus, 234 InterfaceIndex, 235 InterfaceIndexOrZero 236 FROM IF-MIB 237 transmission 238 FROM RFC1213-MIB; 240 dialControlMib MODULE-IDENTITY 241 LAST-UPDATED "9604271037Z" -- Apr 27, 1996 242 ORGANIZATION "IETF ISDN Working Group" 243 CONTACT-INFO 244 " Guenter Roeck 245 Postal: Conware GmbH 246 Killisfeldstrasse 64 247 76227 Karlsruhe 248 Germany 249 Tel: +49 721 9495 0 250 E-mail: roeck@conware.de" 251 DESCRIPTION 252 "The MIB module to describe neighbors 253 for demand access and possibly other 254 kinds of interfaces." 255 ::= { transmission 21 } 257 -- Dial Control Mib objects definitions 259 dialControlMibObjects OBJECT IDENTIFIER ::= { dialControlMib 1 } 260 -- General configuration group 262 dialCtlConfiguration OBJECT IDENTIFIER ::= { dialControlMibObjects 1 } 264 -- general configuration data/parameters 266 dialCtlAcceptMode OBJECT-TYPE 267 SYNTAX INTEGER { 268 acceptNone(1), 269 acceptAll(2), 270 acceptKnown(3) 271 } 272 MAX-ACCESS read-write 273 STATUS current 274 DESCRIPTION 275 "The security level for acceptance of incoming calls. 276 acceptNone(1) - incoming calls will not be accepted 277 acceptAll(2) - incoming calls will be accepted, 278 even if there is no matching entry 279 in the dialCtlNbrCfgTable 280 acceptKnown(3) - incoming calls will be accepted only 281 if there is a matching entry in the 282 dialCtlNbrCfgTable 283 " 284 ::= { dialCtlConfiguration 1 } 286 dialCtlCallInfoTrapEnable OBJECT-TYPE 287 SYNTAX INTEGER { 288 enabled(1), 289 disabled(2) 290 } 291 MAX-ACCESS read-create 292 STATUS current 293 DESCRIPTION 294 "This object indicates whether dialCtlNbrCallInformation 295 traps should be generated for all neighbors. If the value 296 of this object is enabled(1), dialCtlNbrCallInformation 297 traps will be generated for all neighbors. If the value 298 of this object is disabled(2), dialCtlNbrCallInformation 299 traps will be generated only for neighbors having 300 dialCtlNbrCallInfoTrapEnable set to enabled(1)." 301 DEFVAL { disabled } 302 ::= { dialCtlConfiguration 2 } 304 -- Neighbor group 306 dialCtlNeighbor OBJECT IDENTIFIER ::= { dialControlMibObjects 2 } 308 dialCtlNbrGetIndex OBJECT-TYPE 309 SYNTAX TestAndIncr 310 MAX-ACCESS read-write 311 STATUS current 312 DESCRIPTION 313 "The recommended procedure for selecting a new index for 314 dialCtlNbrCfgTable row creation is to GET the value of 315 this object, and then to SET the object with the same 316 value. If the SET operation succeeds, the manager can use 317 this value as an index to create a new row in this table." 318 REFERENCE 319 "RFC1903, TestAndIncr textual convention." 320 ::= { dialCtlNeighbor 1 } 322 -- neighbor configuration table 324 dialCtlNbrCfgTable OBJECT-TYPE 325 SYNTAX SEQUENCE OF DialCtlNbrCfgEntry 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "The list of neighbors from which the managed device 330 will accept calls or to which it will place them." 331 ::= { dialCtlNeighbor 2 } 333 dialCtlNbrCfgEntry OBJECT-TYPE 334 SYNTAX DialCtlNbrCfgEntry 335 MAX-ACCESS not-accessible 336 STATUS current 337 DESCRIPTION 338 "A single Neighbor. This entry is effectively permanent, 339 and contains information describing the neighbor and his 340 permissions. 341 The value of dialCtlNbrCfgOriginateAddress must be 342 specified before a new row in this table can become 343 active(1). Any writeable parameters in an existing entry 344 can be modified while the entry is active. The modification 345 will take effect when the neighbor in question will be 346 called the next time." 347 INDEX { dialCtlNbrCfgId, dialCtlNbrCfgIndex } 348 ::= { dialCtlNbrCfgTable 1 } 350 DialCtlNbrCfgEntry ::= SEQUENCE { 351 dialCtlNbrCfgId INTEGER, 352 -- neighbor ID 353 dialCtlNbrCfgIndex INTEGER, 354 -- index value 355 dialCtlNbrCfgIfIndex InterfaceIndex, 356 dialCtlNbrCfgIfType IANAifType, 357 dialCtlNbrCfgLowerIf InterfaceIndexOrZero, 358 -- ifIndex value of 359 -- lower interface 360 dialCtlNbrCfgOriginateAddress DisplayString, 361 -- Call Address (outgoing) 362 dialCtlNbrCfgAnswerAddress DisplayString, 363 -- Call Address (incoming) 365 dialCtlNbrCfgSubAddress DisplayString, 366 -- Call Subaddress 367 dialCtlNbrCfgClosedUserGroup DisplayString, 368 -- Closed User Group 369 dialCtlNbrCfgSpeed INTEGER, 370 -- desired speed in 371 -- bit/second 372 dialCtlNbrCfgPermission INTEGER, 373 -- applicable permissions 374 dialCtlNbrCfgInactivityTimer INTEGER, 375 -- disconnect idle timer 376 dialCtlNbrCfgMinDuration INTEGER, 377 -- Min call duration 378 dialCtlNbrCfgMaxDuration INTEGER, 379 -- Max call duration 380 dialCtlNbrCfgCarrierDelay INTEGER, 381 -- call connect time 382 dialCtlNbrCfgCallRetries INTEGER, 383 -- number of call retries 384 dialCtlNbrCfgRetryDelay INTEGER, 385 -- time between call 386 -- attempts 387 dialCtlNbrCfgFailureDelay INTEGER, 388 -- retry time after failure 389 dialCtlNbrCallInfoTrapEnable INTEGER, 390 -- to enable/disable traps 391 dialCtlNbrCfgStatus RowStatus 392 } 394 dialCtlNbrCfgId OBJECT-TYPE 395 SYNTAX INTEGER (1..2147483647) 396 MAX-ACCESS not-accessible 397 STATUS current 398 DESCRIPTION 399 "This object defines a single neighbor. There may 400 be several entries in this table for one neighbor, 401 defining different ways of reaching this neighbor. 402 Thus, there may be several entries in this table 403 with the same value of dialCtlNbrCfgId. 404 Multiple entries for one neighbor may be used to support 405 multilink as well as backup lines. 406 A single neighbor will be identified by a unique value 407 of this object. Several entries for one neighbor MUST 408 have the same value of dialCtlNbrCfgId, but different 409 ifEntries and thus different values of ifIndex and 410 dialCtlNbrCfgIndex." 411 ::= { dialCtlNbrCfgEntry 1 } 413 dialCtlNbrCfgIndex OBJECT-TYPE 414 SYNTAX INTEGER (1..2147483647) 415 MAX-ACCESS not-accessible 416 STATUS current 417 DESCRIPTION 418 "The index value which uniquely identifies an entry 419 in this table." 420 ::= { dialCtlNbrCfgEntry 2 } 422 dialCtlNbrCfgIfIndex OBJECT-TYPE 423 SYNTAX InterfaceIndex 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The ifIndex value of the interface associated with this 428 neighbor." 429 ::= { dialCtlNbrCfgEntry 3 } 431 dialCtlNbrCfgIfType OBJECT-TYPE 432 SYNTAX IANAifType 433 MAX-ACCESS read-create 434 STATUS current 435 DESCRIPTION 436 "The interface type to be used for calling this neighbor. 437 In case of ISDN, the value of isdn(63) is to be used." 438 DEFVAL { other } 439 ::= { dialCtlNbrCfgEntry 4 } 441 dialCtlNbrCfgLowerIf OBJECT-TYPE 442 SYNTAX InterfaceIndexOrZero 443 MAX-ACCESS read-create 444 STATUS current 445 DESCRIPTION 446 "ifIndex value of an interface the neighbor will have to be 447 called on. For example, on an ISDN interface, this can be 448 the ifIndex value of a D channel or the ifIndex value of a 449 B channel, whatever is appropriate for a given neighbor. 450 As an example, for Basic Rate leased lines it will be 451 necessary to specify a B channel ifIndex, while for 452 semi-permanent connections the D channel ifIndex has 453 to be specified. 454 If the interface can be dynamically assigned, this object 455 has a value of zero." 456 DEFVAL { 0 } 457 ::= { dialCtlNbrCfgEntry 5 } 459 dialCtlNbrCfgOriginateAddress OBJECT-TYPE 460 SYNTAX DisplayString 461 MAX-ACCESS read-create 462 STATUS current 463 DESCRIPTION 464 "Call Address at which the neighbor will be called. 465 Think of this as the set of characters following 'ATDT ' 466 or the 'phone number' included in a D channel call request. 468 The structure of this information will be switch type 469 specific." 470 ::= { dialCtlNbrCfgEntry 6 } 472 dialCtlNbrCfgAnswerAddress OBJECT-TYPE 473 SYNTAX DisplayString 474 MAX-ACCESS read-create 475 STATUS current 476 DESCRIPTION 477 "Calling Party Number information element, as for example 478 passed in an ISDN SETUP message by a PBX or switch, 479 for incoming calls. 480 This address can be used to identify the neighbor. 481 If this address is either unknown or identical 482 to dialCtlNbrCfgOriginateAddress, this object will be 483 a zero length string." 484 DEFVAL { "" } 485 ::= { dialCtlNbrCfgEntry 7 } 487 dialCtlNbrCfgSubAddress OBJECT-TYPE 488 SYNTAX DisplayString 489 MAX-ACCESS read-create 490 STATUS current 491 DESCRIPTION 492 "Subaddress at which the neighbor will be called. 493 If the subaddress is undefined for the given media or 494 unused, this is a zero length string." 495 DEFVAL { "" } 496 ::= { dialCtlNbrCfgEntry 8 } 498 dialCtlNbrCfgClosedUserGroup OBJECT-TYPE 499 SYNTAX DisplayString 500 MAX-ACCESS read-create 501 STATUS current 502 DESCRIPTION 503 "Closed User Group at which the neighbor will be called. 504 If the Closed User Group is undefined for the given media 505 or unused, this is a zero length string." 506 REFERENCE 507 "Q.931, chapter 4.6.1." 508 DEFVAL { "" } 509 ::= { dialCtlNbrCfgEntry 9 } 511 dialCtlNbrCfgSpeed OBJECT-TYPE 512 SYNTAX INTEGER (0..2147483647) 513 MAX-ACCESS read-create 514 STATUS current 515 DESCRIPTION 516 "The desired information transfer speed in bits/second 517 when calling this neighbor. 518 The detailed media specific information, e.g. information 519 type and information transfer rate for ISDN circuits, 520 has to be extracted from this object. 521 If the transfer speed to be used is unknown or the default 522 speed for this type of interfaces, the value of this object 523 may be zero." 524 DEFVAL { 0 } 525 ::= { dialCtlNbrCfgEntry 10 } 527 dialCtlNbrCfgPermission OBJECT-TYPE 528 SYNTAX INTEGER { 529 originate(1), 530 answer(2), 531 both(3), -- both originate & answer 532 callback(4), 533 none(5) 534 } 535 MAX-ACCESS read-create 536 STATUS current 537 DESCRIPTION 538 "Applicable permissions. callback(4) either rejects the 539 call and then calls back, or uses the 'Reverse charging' 540 information element if it is available. 541 Note that callback(4) is supposed to control charging, not 542 security, and applies to callback prior to accepting a 543 call. Callback for security reasons can be handled using 544 PPP callback." 545 DEFVAL { both } 546 ::= { dialCtlNbrCfgEntry 11 } 548 dialCtlNbrCfgInactivityTimer OBJECT-TYPE 549 SYNTAX INTEGER (0..2147483647) 550 UNITS "seconds" 551 MAX-ACCESS read-create 552 STATUS current 553 DESCRIPTION 554 "The connection will be automatically disconnected 555 if no longer carrying useful data for a time 556 period, in seconds, specified in this object. 557 Useful data in this context refers to forwarding 558 packets, including routing information; it 559 excludes the encapsulator maintenance frames. 560 A value of zero means the connection will not be 561 automatically taken down due to inactivity, 562 which implies that it is a dedicated circuit." 563 DEFVAL { 0 } 564 ::= { dialCtlNbrCfgEntry 12 } 566 dialCtlNbrCfgMinDuration OBJECT-TYPE 567 SYNTAX INTEGER (0..2147483647) 568 MAX-ACCESS read-create 569 STATUS current 570 DESCRIPTION 571 "Minimum duration of a call in seconds, starting from the 572 time the call is connected until the call is disconnected. 573 This is to accomplish the fact that in most countries 574 charging applies to units of time, which should be matched 575 as closely as possible." 576 DEFVAL { 0 } 577 ::= { dialCtlNbrCfgEntry 13 } 579 dialCtlNbrCfgMaxDuration OBJECT-TYPE 580 SYNTAX INTEGER (0..2147483647) 581 MAX-ACCESS read-create 582 STATUS current 583 DESCRIPTION 584 "Maximum call duration in seconds. Zero means 'unlimited'." 585 DEFVAL { 0 } 586 ::= { dialCtlNbrCfgEntry 14 } 588 dialCtlNbrCfgCarrierDelay OBJECT-TYPE 589 SYNTAX INTEGER (0..2147483647) 590 UNITS "seconds" 591 MAX-ACCESS read-create 592 STATUS current 593 DESCRIPTION 594 "The call timeout time in seconds. The default value 595 of zero means that the call timeout as specified for 596 the media in question will apply." 597 DEFVAL { 0 } 598 ::= { dialCtlNbrCfgEntry 15 } 600 dialCtlNbrCfgCallRetries OBJECT-TYPE 601 SYNTAX INTEGER (0..2147483647) 602 MAX-ACCESS read-create 603 STATUS current 604 DESCRIPTION 605 "The number of calls to a non-responding address 606 that may be made. A retry count of zero means 607 there is no bound. The intent is to bound 608 the number of successive calls to an address 609 which is inaccessible, or which refuses those calls. 611 Some countries regulate the number of call retries 612 to a given neighbor that can be made." 613 DEFVAL { 0 } 614 ::= { dialCtlNbrCfgEntry 16 } 616 dialCtlNbrCfgRetryDelay OBJECT-TYPE 617 SYNTAX INTEGER (0..2147483647) 618 UNITS "seconds" 619 MAX-ACCESS read-create 620 STATUS current 621 DESCRIPTION 622 "The time in seconds between call retries if a neighbor 623 cannot be reached. 625 A value of zero means that call retries may be done 626 without any delay." 627 DEFVAL { 0 } 628 ::= { dialCtlNbrCfgEntry 17 } 630 dialCtlNbrCfgFailureDelay OBJECT-TYPE 631 SYNTAX INTEGER (0..2147483647) 632 UNITS "seconds" 633 MAX-ACCESS read-create 634 STATUS current 635 DESCRIPTION 636 "The time in seconds after which call attempts are 637 to be placed again after a neighbor has been noticed 638 to be unreachable, i.e. after dialCtlNbrCfgCallRetries 639 unsuccessful call attempts. 640 A value of zero means that a neighbor will not be called 641 again after dialCtlNbrCfgCallRetries unsuccessful call 642 attempts." 643 DEFVAL { 0 } 644 ::= { dialCtlNbrCfgEntry 18 } 646 dialCtlNbrCallInfoTrapEnable OBJECT-TYPE 647 SYNTAX INTEGER { 648 enabled(1), 649 disabled(2) 650 } 651 MAX-ACCESS read-create 652 STATUS current 653 DESCRIPTION 654 "This object indicates whether dialCtlNbrCallInformation 655 traps should be generated for this neighbor." 656 DEFVAL { disabled } 657 ::= { dialCtlNbrCfgEntry 19 } 659 dialCtlNbrCfgStatus OBJECT-TYPE 660 SYNTAX RowStatus 661 MAX-ACCESS read-create 662 STATUS current 663 DESCRIPTION 664 "Status of one row in this table." 665 ::= { dialCtlNbrCfgEntry 20 } 667 -- Neighbor statistics table 669 dialCtlNbrStatsTable OBJECT-TYPE 670 SYNTAX SEQUENCE OF DialCtlNbrStatsEntry 671 MAX-ACCESS not-accessible 672 STATUS current 673 DESCRIPTION 674 "Statistics information for each neighbor entry. 675 There will be one entry in this table for each entry 676 in the dialCtlNbrCfgTable." 678 ::= { dialCtlNeighbor 3 } 680 dialCtlNbrStatsEntry OBJECT-TYPE 681 SYNTAX DialCtlNbrStatsEntry 682 MAX-ACCESS not-accessible 683 STATUS current 684 DESCRIPTION 685 "Statistics information for a single Neighbor. This entry 686 is effectively permanent, and contains information 687 describing the last call attempt as well as supplying 688 statistical information." 689 AUGMENTS { dialCtlNbrCfgEntry } 690 ::= { dialCtlNbrStatsTable 1 } 692 DialCtlNbrStatsEntry ::= 693 SEQUENCE { 694 dialCtlNbrStatsConnectTime Counter32, 695 -- total connect time to neighbor 696 dialCtlNbrStatsChargedUnits Counter32, 697 -- number of charged units to this neighbor 698 dialCtlNbrStatsSuccessCalls Counter32, 699 -- number of completed calls to neighbor 700 dialCtlNbrStatsFailCalls Counter32, 701 -- number of failed call attempts 702 dialCtlNbrStatsAcceptCalls Counter32, 703 -- number of calls from neighbor accepted 704 dialCtlNbrStatsRefuseCalls Counter32, 705 -- number of calls from neighbor refused 706 dialCtlNbrStatsLastDisconnectCause OCTET STRING, 707 dialCtlNbrStatsLastDisconnectText DisplayString, 708 -- textual and encoded reasons for last 709 -- call clearing 710 dialCtlNbrStatsLastSetupTime TimeStamp 711 -- time of last call attempt 712 } 714 dialCtlNbrStatsConnectTime OBJECT-TYPE 715 SYNTAX Counter32 716 UNITS "seconds" 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "Accumulated connect time to neighbor since system startup. 721 This is the total connect time, i.e. the connect time 722 for outgoing calls plus the time for incoming calls." 723 ::= { dialCtlNbrStatsEntry 1 } 725 dialCtlNbrStatsChargedUnits OBJECT-TYPE 726 SYNTAX Counter32 727 MAX-ACCESS read-only 728 STATUS current 729 DESCRIPTION 730 "The total number of charging units applying to this 731 neighbor since system startup. 732 Only the charging units applying to the local interface, 733 i.e. for originated calls or for calls with 'Reverse 734 charging' being active, will be counted here." 735 ::= { dialCtlNbrStatsEntry 2 } 737 dialCtlNbrStatsSuccessCalls OBJECT-TYPE 738 SYNTAX Counter32 739 MAX-ACCESS read-only 740 STATUS current 741 DESCRIPTION 742 "Number of completed calls to neighbor." 743 ::= { dialCtlNbrStatsEntry 3 } 745 dialCtlNbrStatsFailCalls OBJECT-TYPE 746 SYNTAX Counter32 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "Number of failed call attempts to neighbor since system 751 startup." 752 ::= { dialCtlNbrStatsEntry 4 } 754 dialCtlNbrStatsAcceptCalls OBJECT-TYPE 755 SYNTAX Counter32 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "Number of calls from neighbor accepted since system 760 startup." 761 ::= { dialCtlNbrStatsEntry 5 } 763 dialCtlNbrStatsRefuseCalls OBJECT-TYPE 764 SYNTAX Counter32 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "Number of calls from neighbor refused since system 769 startup." 770 ::= { dialCtlNbrStatsEntry 6 } 772 dialCtlNbrStatsLastDisconnectCause OBJECT-TYPE 773 SYNTAX OCTET STRING (SIZE (0..4)) 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "The encoded network cause value associated with the last 778 call. 779 This object will be updated whenever a call is started 780 or cleared. 781 The value of this object will depend on the interface type 782 as well as on the protocol and protocol version being 783 used on this interface. Some references for possible cause 784 values are given below." 785 REFERENCE 786 "- Bellcore SR-NWT-001953, Generic Guidelines for 787 ISDN Terminal Equipment On Basic Access Interfaces, 788 chapter 5.2.5.8. 789 - Bellcore SR-NWT-002343, ISDN Primary Rate Interface 790 Generic Guidelines for Customer Premises Equipment, 791 chapter 8.2.5.8. 792 - ITU-T Q.931, Annex I. 793 - ITU-T X.25, CAUSE and DIAGNOSTIC field values. 794 - German Telekom FTZ 1TR6, chapter 3.2.3.4.4.4." 795 ::= { dialCtlNbrStatsEntry 7 } 797 dialCtlNbrStatsLastDisconnectText OBJECT-TYPE 798 SYNTAX DisplayString 799 MAX-ACCESS read-only 800 STATUS current 801 DESCRIPTION 802 "ASCII text describing the reason for the last call 803 termination. 805 This object exists because it would be impossible for 806 a management station to store all possible cause values 807 for all types of interfaces. It should be used only if 808 a management station is unable to decode the value of 809 dialCtlNbrStatsLastDisconnectCause. 811 This object will be updated whenever a call is started 812 or cleared." 813 ::= { dialCtlNbrStatsEntry 8 } 815 dialCtlNbrStatsLastSetupTime OBJECT-TYPE 816 SYNTAX TimeStamp 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "The value of sysUpTime when the last call to this neighbor 821 was started. 822 For ISDN media, this will be the time when the setup 823 message was received from or sent to the network. 824 This object will be updated whenever a call is started 825 or cleared." 826 ::= { dialCtlNbrStatsEntry 9 } 828 -- 829 -- the call history group 830 -- 832 callHistory OBJECT IDENTIFIER ::= { dialControlMibObjects 3 } 833 callHistoryTableMaxLength OBJECT-TYPE 834 SYNTAX INTEGER (0..2147483647) 835 MAX-ACCESS read-write 836 STATUS current 837 DESCRIPTION 838 "The upper limit on the number of entries that the 839 callHistoryTable may contain. A value of 0 840 will prevent any history from being retained. When 841 this table is full, the oldest entry will be deleted 842 and the new one will be created." 843 ::= { callHistory 1 } 845 callHistoryRetainTimer OBJECT-TYPE 846 SYNTAX INTEGER (0..2147483647) 847 UNITS "minutes" 848 MAX-ACCESS read-write 849 STATUS current 850 DESCRIPTION 851 "The minimum amount of time that an callHistoryEntry 852 will be maintained before being deleted. A value of 853 0 will prevent any history from being retained in the 854 callHistoryTable, but will neither prevent callCompletion 855 traps being generated nor affect other tables." 856 ::= { callHistory 2 } 858 -- callHistoryTable 859 -- Table to store the past call information. The Destination number 860 -- and the call connect and disconnect time, the disconnection cause 861 -- are stored. These calls could be circuit switched or they could 862 -- be virtual circuits. History of each and every call is stored, 863 -- of successful calls as well as of unsuccessful and rejected calls. 864 -- An entry will be created when a call is cleared. 866 callHistoryTable OBJECT-TYPE 867 SYNTAX SEQUENCE OF CallHistoryEntry 868 MAX-ACCESS not-accessible 869 STATUS current 870 DESCRIPTION 871 "A table containing information about specific 872 calls to a specific destination." 873 ::= { callHistory 3 } 875 callHistoryEntry OBJECT-TYPE 876 SYNTAX CallHistoryEntry 877 MAX-ACCESS not-accessible 878 STATUS current 879 DESCRIPTION 880 "The information regarding a single Connection." 881 INDEX { callHistorySetupTime, callHistoryIndex } 882 ::= { callHistoryTable 1 } 884 CallHistoryEntry ::= 885 SEQUENCE { 886 callHistorySetupTime TimeStamp, 887 callHistoryIndex INTEGER, 888 callHistoryPeerAddress DisplayString, 889 callHistoryPeerSubAddress DisplayString, 890 callHistoryNeighborId INTEGER, 891 callHistoryNeighborIndex INTEGER, 892 callHistoryLogicalIfIndex InterfaceIndex, 893 callHistoryDisconnectCause OCTET STRING, 894 callHistoryDisconnectText DisplayString, 895 callHistoryConnectTime TimeStamp, 896 callHistoryDisconnectTime TimeStamp, 897 callHistoryCallOrigin INTEGER, 898 callHistoryChargedUnits Counter32, 899 callHistoryInfoType INTEGER, 900 callHistoryTransmitPackets Counter32, 901 callHistoryTransmitBytes Counter32, 902 callHistoryReceivePackets Counter32, 903 callHistoryReceiveBytes Counter32 904 } 906 callHistorySetupTime OBJECT-TYPE 907 SYNTAX TimeStamp 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION 911 "The value of sysUpTime when the call associated to this 912 entry was started. This will be useful for an NMS to 913 retrieve all calls after a specific time. Also, this object 914 can be useful in finding large delays between the time the 915 call was started and the time the call was connected. 916 For ISDN media, this will be the time when the setup 917 message was received from or sent to the network." 918 ::= { callHistoryEntry 1 } 920 callHistoryIndex OBJECT-TYPE 921 SYNTAX INTEGER (1..'7fffffff'h) 922 MAX-ACCESS not-accessible 923 STATUS current 924 DESCRIPTION 925 "Index variable to access the CallHistoryEntry objects 926 of the callHistoryTable." 927 ::= { callHistoryEntry 2 } 929 callHistoryPeerAddress OBJECT-TYPE 930 SYNTAX DisplayString 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "The number this call is connected to. If the number is 935 not available, then it will have a length of zero." 937 ::= { callHistoryEntry 3 } 939 callHistoryPeerSubAddress OBJECT-TYPE 940 SYNTAX DisplayString 941 MAX-ACCESS read-only 942 STATUS current 943 DESCRIPTION 944 "The subaddress this call is connected to. If the subaddress 945 is undefined or not available, this will be a zero length 946 string." 947 ::= { callHistoryEntry 4 } 949 callHistoryNeighborId OBJECT-TYPE 950 SYNTAX INTEGER (0..2147483647) 951 MAX-ACCESS read-only 952 STATUS current 953 DESCRIPTION 954 "This is the Id value of the neighbor table entry 955 to which this call was made. If a neighbor table entry 956 for this call does not exist, the value of this object 957 will be zero." 958 ::= { callHistoryEntry 5 } 960 callHistoryNeighborIndex OBJECT-TYPE 961 SYNTAX INTEGER (0..2147483647) 962 MAX-ACCESS read-only 963 STATUS current 964 DESCRIPTION 965 "This is the index value of the neighbor table entry 966 to which this call was made. If a neighbor table entry 967 for this call does not exist, the value of this object 968 will be zero." 969 ::= { callHistoryEntry 6 } 971 callHistoryLogicalIfIndex OBJECT-TYPE 972 SYNTAX InterfaceIndex 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "This is the ifIndex value of the logical interface through 977 which this call was made. For ISDN media, this would be 978 the ifIndex of the B channel which was used for this call." 979 ::= { callHistoryEntry 7 } 981 callHistoryDisconnectCause OBJECT-TYPE 982 SYNTAX OCTET STRING (SIZE (0..4)) 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION 986 "The encoded network cause value associated with this call. 988 The value of this object will depend on the interface type 989 as well as on the protocol and protocol version being 990 used on this interface. Some references for possible cause 991 values are given below." 992 REFERENCE 993 "- Bellcore SR-NWT-001953, Generic Guidelines for 994 ISDN Terminal Equipment On Basic Access Interfaces, 995 chapter 5.2.5.8. 996 - Bellcore SR-NWT-002343, ISDN Primary Rate Interface 997 Generic Guidelines for Customer Premises Equipment, 998 chapter 8.2.5.8. 999 - ITU-T Q.931, Annex I. 1000 - ITU-T X.25, CAUSE and DIAGNOSTIC field values. 1001 - German Telekom FTZ 1TR6, chapter 3.2.3.4.4.4." 1002 ::= { callHistoryEntry 8 } 1004 callHistoryDisconnectText OBJECT-TYPE 1005 SYNTAX DisplayString 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "ASCII text describing the reason for call termination. 1011 This object exists because it would be impossible for 1012 a management station to store all possible cause values 1013 for all types of interfaces. It should be used only if 1014 a management station is unable to decode the value of 1015 dialCtlNbrStatsLastDisconnectCause." 1016 ::= { callHistoryEntry 9 } 1018 callHistoryConnectTime OBJECT-TYPE 1019 SYNTAX TimeStamp 1020 MAX-ACCESS read-only 1021 STATUS current 1022 DESCRIPTION 1023 "The value of sysUpTime when the call was connected." 1024 ::= { callHistoryEntry 10 } 1026 callHistoryDisconnectTime OBJECT-TYPE 1027 SYNTAX TimeStamp 1028 MAX-ACCESS read-only 1029 STATUS current 1030 DESCRIPTION 1031 "The value of sysUpTime when the call was disconnected." 1032 ::= { callHistoryEntry 11 } 1034 callHistoryCallOrigin OBJECT-TYPE 1035 SYNTAX INTEGER { 1036 originate(1), 1037 answer(2), 1038 callback(3) 1039 } 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "The call origin." 1044 ::= { callHistoryEntry 12 } 1046 callHistoryChargedUnits OBJECT-TYPE 1047 SYNTAX Counter32 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "The number of charged units for this connection. 1052 For incoming calls or if charging information is 1053 not supplied by the switch, the value of this object 1054 will be zero." 1055 ::= { callHistoryEntry 13 } 1057 callHistoryInfoType OBJECT-TYPE 1058 SYNTAX INTEGER { 1059 other(1), -- e.g. for non-isdn media 1060 speech(2), 1061 unrestrictedDigital(3), -- 64k/s data 1062 unrestrictedDigital56(4), -- with 56k rate adaption 1063 restrictedDigital(5), 1064 audio31(6), -- 3.1 kHz audio 1065 audio7(7), -- 7 kHz audio 1066 video(8), 1067 packetSwitched(9) 1068 } 1069 MAX-ACCESS read-only 1070 STATUS current 1071 DESCRIPTION 1072 "The information type for this call." 1073 ::= { callHistoryEntry 14 } 1075 callHistoryTransmitPackets OBJECT-TYPE 1076 SYNTAX Counter32 1077 MAX-ACCESS read-only 1078 STATUS current 1079 DESCRIPTION 1080 "The number of packets which were transmitted while this 1081 call was active." 1082 ::= { callHistoryEntry 15 } 1084 callHistoryTransmitBytes OBJECT-TYPE 1085 SYNTAX Counter32 1086 MAX-ACCESS read-only 1087 STATUS current 1088 DESCRIPTION 1089 "The number of bytes which were transmitted while this 1090 call was active." 1091 ::= { callHistoryEntry 16 } 1093 callHistoryReceivePackets OBJECT-TYPE 1094 SYNTAX Counter32 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "The number of packets which were received while this 1099 call was active." 1100 ::= { callHistoryEntry 17 } 1102 callHistoryReceiveBytes OBJECT-TYPE 1103 SYNTAX Counter32 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "The number of bytes which were received while this 1108 call was active." 1109 ::= { callHistoryEntry 18 } 1111 -- Traps related to Connection management 1113 dialControlMibTrapPrefix OBJECT IDENTIFIER ::= { dialControlMib 2 } 1114 dialControlMibTraps OBJECT IDENTIFIER ::= { dialControlMibTrapPrefix 0 } 1116 dialCtlNbrCallInformation NOTIFICATION-TYPE 1117 OBJECTS { 1118 callHistoryNeighborId, 1119 callHistoryNeighborIndex, 1120 callHistoryLogicalIfIndex, 1121 ifOperStatus, 1122 callHistoryPeerAddress, 1123 callHistoryPeerSubAddress, 1124 callHistoryDisconnectCause, 1125 callHistoryConnectTime, 1126 callHistoryDisconnectTime, 1127 callHistoryInfoType, 1128 callHistoryCallOrigin 1129 } 1130 STATUS current 1131 DESCRIPTION 1132 "This trap/inform is sent to the manager whenever 1133 a successful call clears, or a failed call attempt 1134 is determined to have ultimately failed. In the 1135 event that call retry is active, then this is after 1136 all retry attempts have failed. However, only one such 1137 trap is sent in between successful call attempts; 1138 subsequent call attempts result in no trap. 1139 ifOperStatus will return the operational status of the 1140 virtual interface associated with the neighbor to whom 1141 this call was made to." 1142 ::= { dialControlMibTraps 1 } 1144 -- conformance information 1145 dialControlMibConformance OBJECT IDENTIFIER ::= 1146 { dialControlMib 3 } 1147 dialControlMibCompliances OBJECT IDENTIFIER ::= 1148 { dialControlMibConformance 1 } 1149 dialControlMibGroups OBJECT IDENTIFIER ::= 1150 { dialControlMibConformance 2 } 1152 -- compliance statements 1154 dialControlMibCompliance MODULE-COMPLIANCE 1155 STATUS current 1156 DESCRIPTION 1157 "The compliance statement for entities which 1158 implement the DIAL CONTROL MIB" 1159 MODULE -- this module 1160 MANDATORY-GROUPS 1161 { dialControlGroup, callHistoryGroup } 1162 ::= { dialControlMibCompliances 1 } 1164 -- units of conformance 1166 dialControlGroup OBJECT-GROUP 1167 OBJECTS { 1168 dialCtlAcceptMode, 1169 dialCtlCallInfoTrapEnable, 1170 dialCtlNbrGetIndex, 1171 dialCtlNbrCfgIfIndex, 1172 dialCtlNbrCfgIfType, 1173 dialCtlNbrCfgLowerIf, 1174 dialCtlNbrCfgOriginateAddress, 1175 dialCtlNbrCfgAnswerAddress, 1176 dialCtlNbrCfgSubAddress, 1177 dialCtlNbrCfgClosedUserGroup, 1178 dialCtlNbrCfgSpeed, 1179 dialCtlNbrCfgPermission, 1180 dialCtlNbrCfgInactivityTimer, 1181 dialCtlNbrCfgMinDuration, 1182 dialCtlNbrCfgMaxDuration, 1183 dialCtlNbrCfgCarrierDelay, 1184 dialCtlNbrCfgCallRetries, 1185 dialCtlNbrCfgRetryDelay, 1186 dialCtlNbrCfgFailureDelay, 1187 dialCtlNbrCallInfoTrapEnable, 1188 dialCtlNbrCfgStatus, 1189 dialCtlNbrStatsConnectTime, 1190 dialCtlNbrStatsChargedUnits, 1191 dialCtlNbrStatsSuccessCalls, 1192 dialCtlNbrStatsFailCalls, 1193 dialCtlNbrStatsAcceptCalls, 1194 dialCtlNbrStatsRefuseCalls, 1195 dialCtlNbrStatsLastDisconnectCause, 1196 dialCtlNbrStatsLastDisconnectText, 1197 dialCtlNbrStatsLastSetupTime 1198 } 1199 STATUS current 1200 DESCRIPTION 1201 "A collection of objects providing the DIAL CONTROL 1202 capability." 1203 ::= { dialControlMibGroups 1 } 1205 callHistoryGroup OBJECT-GROUP 1206 OBJECTS { 1207 callHistoryTableMaxLength, 1208 callHistoryRetainTimer, 1209 callHistoryPeerAddress, 1210 callHistoryPeerSubAddress, 1211 callHistoryNeighborId, 1212 callHistoryNeighborIndex, 1213 callHistoryLogicalIfIndex, 1214 callHistoryDisconnectCause, 1215 callHistoryDisconnectText, 1216 callHistoryConnectTime, 1217 callHistoryDisconnectTime, 1218 callHistoryCallOrigin, 1219 callHistoryChargedUnits, 1220 callHistoryInfoType, 1221 callHistoryTransmitPackets, 1222 callHistoryTransmitBytes, 1223 callHistoryReceivePackets, 1224 callHistoryReceiveBytes 1225 } 1226 STATUS current 1227 DESCRIPTION 1228 "A collection of objects providing the Call History 1229 capability." 1230 ::= { dialControlMibGroups 2 } 1232 END 1233 5. Acknowledgments 1235 This document was produced by the ISDN MIB Working Group. Special 1236 thanks is due to the following persons: 1238 Ed Alcoff 1239 Fred Baker 1240 Bibek A. Das 1241 Ken Grigg 1242 Jeffrey T. Johnson 1243 Glenn Kime 1244 Oliver Korfmacher 1245 Kedar Madineni 1246 Bill Miskovetz 1247 David M. Piscitello 1248 Lisa A. Phifer 1249 Randy Roberts 1250 Hascall H. Sharp 1251 Robert Snyder 1252 Ron Stoughton 1253 James Watt 1255 6. References 1257 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1258 S. Waldbusser, "Structure of Management Information for Version 2 1259 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1260 January 1996. 1262 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1263 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1264 RFC 1213, Hughes LAN Systems, Performance Systems International, 1265 March 1991. 1267 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A Simple 1268 Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP 1269 Research, Performance Systems International, MIT Lab for Computer 1270 Science, May 1990. 1272 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and 1273 S. Waldbusser, "Protocol Operations for Version 2 of the Simple 1274 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 1276 [5] ITU-T Recommendation "Digital subscriber Signalling System No. 1 1277 (DSS 1) - ISDN user-network interface layer 3 specification for 1278 basic call control", Rec. Q.931(I.451), March 1993. 1280 [6] ITU-T Recommendation "Generic procedures for the control of ISDN 1281 supplementary services ISDN user-network interface layer 3 1282 specification", Rec. Q.932(I.452). 1284 [7] ITU-T Recommendation "Digital subscriber Signalling System No. 1 1285 (DSS 1) - Signalling specification for frame-mode basic call 1286 control", Rec. Q.933. 1288 7. Security Considerations 1290 Information in this MIB may be used by upper protocol layers for 1291 security purpose. 1293 The implementor should be aware that supporting generic neighbors as 1294 described in section 3.4 may cause a security hole. The user would not 1295 know where a call is from, which could potentially allow unauthorized 1296 access if there is no other authentication scheme, e.g. PPP 1297 authentication, available. 1299 8. Author's Address 1301 Guenter Roeck 1302 Conware GmbH 1303 Killisfeldstrasse 64 1304 76137 Karlsruhe, Germany 1306 Phone: +49 721 9495 0 1307 Email: roeck@conware.de 1309 Table of Contents 1311 1 Introduction .................................................... 2 1312 2 The SNMPv2 Network Management Framework ......................... 3 1313 2.1 Object Definitions ............................................ 3 1314 3 Overview ........................................................ 4 1315 3.1 Structure of MIB .............................................. 4 1316 3.2 Relationship to RFC1573 ....................................... 4 1317 3.2.1 Layering Model and Virtual Circuits ......................... 4 1318 3.2.2 ifTestTable ................................................. 5 1319 3.2.3 ifRcvAddressTable ........................................... 6 1320 3.2.3.1 ifEntry for a single neighbor ............................. 6 1321 3.3 Multilink and backup line support ............................. 6 1322 3.4 Support for generic neighbors ................................. 6 1323 4 Definitions ..................................................... 7 1324 4.1 Dial Control MIB .............................................. 7 1325 5 Acknowledgments ................................................. 27 1326 6 References ...................................................... 27 1327 7 Security Considerations ......................................... 29 1328 8 Author's Address ................................................ 29