idnits 2.17.1 draft-ietf-isdnmib-snmp-isdn-mib-07.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-03-29) 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 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 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 307 has weird spacing: '...|switch shad...' == Line 1692 has weird spacing: '...nactive all l...' == Line 1693 has weird spacing: '...1Active layer...' == Line 1695 has weird spacing: '...2Active layer...' -- 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 (August 1996) is 10088 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 2197, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 2205, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 2213, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 2217, 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' -- Possible downref: Non-RFC (?) normative reference: ref. '8' -- Possible downref: Non-RFC (?) normative reference: ref. '9' -- Possible downref: Non-RFC (?) normative reference: ref. '10' ** Obsolete normative reference: RFC 1573 (ref. '11') (Obsoleted by RFC 2233) -- Possible downref: Non-RFC (?) normative reference: ref. '12' -- Possible downref: Non-RFC (?) normative reference: ref. '13' -- Possible downref: Non-RFC (?) normative reference: ref. '14' -- Possible downref: Non-RFC (?) normative reference: ref. '15' Summary: 12 errors (**), 0 flaws (~~), 9 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT ISDN MIB August 1996 3 ISDN Management Information Base 4 draft-ietf-isdnmib-snmp-isdn-mib-07.txt 6 Fri Aug 23 09:15:06 PDT 1996 8 Guenter Roeck (editor) 9 cisco Systems 10 groeck@cisco.com 12 Status of this Memo 14 This document is an Internet-Draft. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its Areas, and 16 its Working Groups. Note that other groups may also distribute working 17 documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference material 22 or to cite them other than as a "work in progress". 24 To learn the current status of any Internet-Draft, please check the 25 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 26 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 27 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 28 ftp.isi.edu (US West Coast). 30 Abstract 32 This memo defines an experimental portion of the Management Information 33 Base (MIB) for use with network management protocols in the Internet 34 community. In particular, it defines a minimal set of managed objects 35 for SNMP-based management of ISDN terminal interfaces. ISDN interfaces 36 are supported on a variety of equipment (for data and voice) including 37 terminal adapters, bridges, hosts, and routers. 39 This document specifies a MIB module in a manner that is compliant to 40 the SNMPv2 SMI. The set of objects is consistent with the SNMP 41 framework and existing SNMP standards. 43 This document is a product of the ISDN MIB working group within the 44 Internet Engineering Task Force. Comments are solicited and should be 45 addressed to the working group's mailing list at isdn-mib@cisco.com 46 and/or the author. 48 The current version of this document reflects changes made during the 49 last call period and the IESG review. 51 Table of Contents 53 1 The SNMPv2 Network Management Framework ......................... 3 54 2 Object Definitions .............................................. 3 55 3 Overview ........................................................ 4 56 3.1 Structure of the MIB .......................................... 4 57 3.1.1 General Description ......................................... 4 58 3.2 Relationship to the Interfaces MIB ............................ 5 59 3.2.1 Layering Model .............................................. 5 60 3.2.2 ifTestTable ................................................. 8 61 3.2.3 ifRcvAddressTable ........................................... 8 62 3.2.4 ifEntry ..................................................... 8 63 3.2.4.1 ifEntry for a Basic Rate hardware interface ............... 8 64 3.2.4.2 ifEntry for a B channel ................................... 9 65 3.2.4.3 ifEntry for LAPD (D channel Data Link Layer) .............. 10 66 3.2.4.4 ifEntry for a signaling channel ........................... 12 67 3.3 Relationship to other MIBs .................................... 14 68 3.3.1 Relationship to the DS1/E1 MIB .............................. 14 69 3.3.2 Relationship to the DS0 and DS0Bundle MIBs .................. 14 70 3.3.3 Relationship to the Dial Control MIB ........................ 14 71 3.4 ISDN interface specific information and implementation hints 72 .............................................................. 14 73 3.4.1 ISDN leased lines ........................................... 14 74 3.4.2 Hyperchannels ............................................... 15 75 3.4.3 D channel backup and NFAS trunks ............................ 15 76 3.4.4 X.25 based packet-mode service in B and D channels .......... 16 77 3.4.5 SPID handling ............................................... 16 78 3.4.6 Closed User Groups .......................................... 17 79 3.4.7 Provision of point-to-point line topology ................... 17 80 3.4.8 Speech and audio bearer capability information elements ..... 18 81 3.4.9 Attaching incoming calls to router ports .................... 18 82 3.4.10 Usage of isdnMibDirectoryGroup and isdnDirectoryTable ...... 19 83 4 Definitions ..................................................... 20 84 5 Acknowledgments ................................................. 44 85 6 References ...................................................... 44 86 7 Security Considerations ......................................... 45 87 8 Author's Address ................................................ 46 88 1. The SNMPv2 Network Management Framework 90 The SNMPv2 Network Management Framework presently consists of three 91 major components. They are: 93 o the SMI, described in RFC 1902 [1] - the mechanisms used for 94 describing and naming objects for the purpose of management. 96 o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects 97 for the Internet suite of protocols. 99 o the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for 100 accessing managed objects. 102 The Framework permits new objects to be defined for the purpose of 103 experimentation and evaluation. 105 2. Object Definitions 107 Managed objects are accessed via a virtual information store, termed the 108 Management Information Base or MIB. Objects in the MIB are defined 109 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 110 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 111 an administratively assigned name. The object type together with an 112 object instance serves to uniquely identify a specific instantiation of 113 the object. For human convenience, we often use a textual string, 114 termed the descriptor, to refer to the object type. 116 3. Overview 118 3.1. Structure of the MIB 120 For managing ISDN interfaces, the following information is necessary: 122 o Information for managing physical interfaces. In case of ISDN 123 primary rate, this are usually T1 or E1 lines, being managed in the 124 DS1/E1 MIB [12]. For Basic Rate lines, physical interfaces are 125 managed by this MIB. 127 o Information for managing B channels. 129 o Information for managing signaling channels. 131 o Optionally, information for managing Terminal Endpoints (TE). A 132 Terminal Endpoint is a link layer connection to a switch. 134 o Optionally, information for managing a list of directory numbers. 136 In order to manage connections over ISDN lines, the management of 137 neighbors and call history information is required as well. This 138 information is defined in the Dial Control MIB [15]. 140 The purpose for splitting the required information in two MIBs is to be 141 able to use parts of this information for non-ISDN interfaces as well. 142 In particular, the Dial Control MIB might also be used for other types 143 of interfaces, e.g. modems or X.25 virtual connections. 145 Within this document, information has been structured into five groups, 146 which are described in the following chapters. 148 3.1.1. General Description 150 This MIB controls all aspects of ISDN interfaces. It consists of five 151 groups. 153 o The isdnMibBasicRateGroup is used to provide information regarding 154 physical Basic Rate interfaces. 156 o The isdnMibBearerGroup is used to control B (bearer) channels. It 157 supports configuration parameters as well as statistical 158 information related to B channels. 160 o The isdnMibSignalingGroup is used to control D (delta) channels. 161 There are three tables in this group. The isdnSignalingTable and 162 isdnSignalingStatsTable support ISDN Network Layer configuration 163 and statistics. The isdnLapdTable supports ISDN Data Link Layer 164 (LAPD) configuration and statistics. 166 o The optional isdnMibEndpointGroup can be used to specify Terminal 167 Endpoints. It is required only if there are non-ISDN endpoints 168 defined for a given D channel, or if additional information like 169 Terminal Endpoint Identifier (TEI) values or Service Profile 170 IDentifiers (SPID) is required to identify a given ISDN user. 172 o The optional isdnMibDirectoryGroup can be used to specify a list of 173 directory numbers for each signaling channel. It is required only 174 if the directory numbers to be accepted differ from the 175 isdnSignalingCallingAddress as specified in the isdnSignalingTable. 177 3.2. Relationship to the Interfaces MIB 179 This section clarifies the relationship of this MIB to the Interfaces 180 MIB [11]. Several areas of correlation are addressed in the following 181 subsections. The implementor is referred to the Interfaces MIB document 182 in order to understand the general intent of these areas. 184 3.2.1. Layering Model 186 An ISDN interface usually consists of a D channel and a number of B 187 channels, all of which are layered on top of a physical interface. 189 Furthermore, there are multiple interface layers for each D channel. 190 There are Data Link Layer (LAPD) as well as Network Layer entities. 192 This is accomplished in this MIB by creating a logical interface 193 (ifEntry) for each of the D channel entities and a logical interface 194 (ifEntry) for each of the B channels. These are then correlated to each 195 other and to the physical interface using the ifStack table of the 196 Interfaces MIB [11]. 198 The basic model, therefore, looks something like this: 200 | | 201 +--+ +--+ 202 | D ch. | 203 |Layer 3| 204 +--+ +--+ 205 | | | | | | <== interface to upper 206 +--+ +--+ +--+ +--+ +--+ +--+ layers, to be provided 207 | D ch. | | B | | B | by ifStack table 208 |Layer 2| |channel| .... |channel| 209 +--+ +--+ +--+ +--+ +--+ +--+ 210 | | | | | | <== attachment to physical 211 +--+ +--------+ +------------+ +----+ interfaces, to be provided 212 | physical interface | by ifStack table 213 | (S/T, U or T1/E1) | 214 +-----------------------------------+ 216 Mapping of B/D channels to physical interfaces 218 Each D channel can support multiple Terminal Endpoints. Terminal 219 Endpoints can either be one or multiple ISDN signaling channels, or 220 channels supporting X.25 based packet mode services. 222 To accomplish this, there can be multiple Network Layer entities on top 223 of each ISDN Data Link Layer (LAPD) interface. The detailed model 224 therefore looks something like this, including interface types as 225 examples: 227 +------+ +----+ +----+ 228 |x25ple| |isdn| |isdn| Terminal Endpoints (X.25 or ISDN) 229 +--+---+ +-+--+ +-+--+ 230 | | | 231 | +------+ | | | <== Interface to upper layers, 232 | | +------------+ | | to be provided by ifStack 233 | | | | | table 234 ++-+-++ +-+-+ +-+-+ 235 |lapd | D channel |ds0| |ds0| B channels 236 +--+--+ Data Link Layer +-+-+ +-+-+ 237 | | | 238 +--+----------------------+------+--------------------+ 239 | ds1 or isdns/isdnu | 240 +-----------------------------------------------------+ 242 Detailed interface mapping 244 IfEntries are maintained for each D channel Network Layer entity 245 (Terminal Endpoint), for LAPD and for each B channel. 247 The ifType for a Terminal Endpoint can be isdn(63) for ISDN signaling 248 channels or x25ple(40) for X.25 based packet mode services. The ifType 249 for D channel Data Link Layer (LAPD) interfaces is lapd(77). The ifType 250 for B channels is ds0(81). The ifType for physical interfaces is the 251 matching IANA ifType, usually ds1(18) for Primary Rate interfaces or 252 isdns(75)/isdnu(76) for Basic Rate interfaces. 254 The ifStackTable is used to map B channels and LAPD interfaces to 255 physical interfaces and to map D channel Network Layer interfaces 256 (Terminal Endpoints) to LAPD. 258 In the example given above, the assignment of index values could for 259 example be as follows: 261 ifIndex ifType ISDN MIB tables Description 262 indexed by ifIndex 264 1 isdns(75) isdnBasicRateTable Basic Rate physical interface 265 2 lapd(77) isdnLapdTable LAPD interface 266 3 x25ple(40) isdnEndpointTable X.25 Packet Layer 267 4 isdn(63) isdnSignalingTable ISDN signaling channel #1 268 isdnEndpointTable 269 5 isdn(63) isdnSignalingTable ISDN signaling channel #2 270 isdnEndpointTable 271 6 ds0(81) isdnBearerTable B channel #1 272 7 ds0(81) isdnBearerTable B channel #2 273 8 ppp(23) neighbor entry #1 (see below) 274 9 ppp(23) neighbor entry #2 (see below) 276 The corresponding ifStack table entries would then be: 278 ifStackTable Entries 280 HigherLayer LowerLayer 281 0 3 282 0 4 283 0 5 284 0 8 285 0 9 286 1 0 287 2 1 288 3 2 289 4 2 290 5 2 291 6 1 292 7 1 293 8 6 294 9 7 296 Mapping of B channels to upper interface layers is usually done using 297 the Dial Control MIB. For example, mapping on top of B channels might 298 look as follows: 300 +-------------------------------------------------------+ 301 | Network Layer Protocol | 302 +------+ +-------+ +-------+ +-------+ +-------+ +------+ 303 | | | | | | | | | | <== appears active 304 +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ 305 | PPP | | PPP | | F/R | | PPP | | F/R | 306 | for | | for | | for | | for | | for | ifEntry with 307 |Nbr 1| |Nbr 2| |switch |Nbr 3| |switch shadow 308 | | | | | A | | | | B | NeighborEntry 309 +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ 310 | | | | <== some actually are 311 +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ 312 | B | | B | | B | | B | | B | 313 |channel| |channel| |channel| |channel| |channel| 314 +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ 315 | | | | | | | | | | 316 +------+ +-------+ +-------+ +-------+ +-------+ +------+ 317 | Basic/Primary Rate Interface | 318 +-------------------------------------------------------+ 320 Mapping of IP interfaces to Called Neighbors to B Channels 322 In this model, ifEntries are maintained for each neighbor. Each 323 neighbor is required to have an associated ifEntry. This interface can 324 be of any kind, e.g. PPP or LAPB. 326 The Dial Control MIB can be used for all types of demand-access 327 interfaces, e.g., ISDN, modems or X.25 virtual connections. 329 3.2.2. ifTestTable 331 The ifTestTable is not supported by this MIB. 333 3.2.3. ifRcvAddressTable 335 The ifRcvAddressTable is not supported by this MIB. 337 3.2.4. ifEntry 339 3.2.4.1. ifEntry for a Basic Rate hardware interface 341 The ifGeneralGroup is supported for Basic Rate hardware interfaces. 343 ifTable Comments 344 ============== =========================================== 345 ifIndex Each ISDN Basic Rate hardware interface is 346 represented by an ifEntry. 348 ifDescr Textual port description. 350 ifType The IANA value of isdns(75) or isdnu(76), 351 whichever is appropriate. 353 ifSpeed The overall bandwidth of this interface. 355 ifPhysAddress Return an empty string. 357 ifAdminStatus The administrative status of the ISDN interface. 359 ifOperStatus The current operational status of this interface. 360 The operational status is dormant(5) if 361 the interface is in standby mode, i.e. connected 362 to the network, but without call activity. 363 The operational status is down(2) if the hardware 364 has detected that there is no layer 1 connection 365 to the switch. 366 For other values, refer to the Interfaces MIB. 368 ifLastChange Refer to the Interfaces MIB. 370 ifLinkUpDownTrapEnable 371 Refer to the Interfaces MIB. 373 ifConnectorPresent 374 Refer to the Interfaces MIB. 376 ifHighSpeed Return zero. 378 ifName Refer to the Interfaces MIB. 380 3.2.4.2. ifEntry for a B channel 382 The ifEntry for a B channel supports the ifGeneralGroup of the 383 Interfaces MIB. 385 ifTable Comments 386 ============== =========================================== 387 ifIndex Each ISDN B channel is represented by an ifEntry. 389 ifDescr Textual port description. 391 ifType The IANA value of ds0(81). 393 ifSpeed The bandwidth of this B channel. 394 Usually, this is the value of 56000 or 64000. 396 ifPhysAddress Return an empty string. 398 ifAdminStatus The administrative status of this interface. 400 ifOperStatus The current operational status of this interface. 402 Note that dormant(5) is explicitly being used 403 as defined in the Interfaces MIB. 404 For other values, refer to the Interfaces MIB. 406 ifLastChange Refer to the Interfaces MIB. 408 ifLinkUpDownTrapEnable 409 Refer to the Interfaces MIB. 411 ifConnectorPresent 412 Refer to the Interfaces MIB. 414 ifHighSpeed Return zero. 416 ifName Refer to the Interfaces MIB. 418 3.2.4.3. ifEntry for LAPD (D channel Data Link Layer) 420 The ifEntry for LAPD (D channel Data Link Layer) supports the 421 ifGeneralGroup and the ifPacketGroup of the Interfaces MIB. 423 ifTable Comments 424 ============== =========================================== 425 ifIndex Each ISDN D channel Data Link layer is represented 426 by an ifEntry. 428 ifDescr Textual port description. 430 ifType The IANA value of lapd(77). 432 ifSpeed The bandwidth of this interface. Usually, this is 433 the value of 16000 for basic rate interfaces or 434 64000 for primary rate interfaces. 436 ifPhysAddress Return an empty string. 438 ifAdminStatus The administrative status of this interface. 440 ifOperStatus The current operational status of the ISDN 441 LAPD interface. The operational status is 442 dormant(5) if the interface is in standby mode 443 (see Q.931 [8], Annex F, D channel backup 444 procedures). 445 For other values, refer to the Interfaces MIB. 447 ifLastChange Refer to the Interfaces MIB. 449 ifLinkUpDownTrapEnable 450 Refer to the Interfaces MIB. 452 ifConnectorPresent 453 Refer to the Interfaces MIB. 455 ifHighSpeed Return zero. 457 ifName Refer to the Interfaces MIB. 459 ifMtu The size of the largest frame which can be 460 sent/received on this interface, 461 specified in octets. Usually, this is the 462 default value of 260 as specified in Q.921 463 [6], chapter 5.9.3. 465 ifInOctets The total number of octets received on this 466 interface. 468 ifInUcastPkts The number of frames received on this interface 469 whose address is not TEI=127. 471 ifInNUcastPkts Deprecated. Return the number of frames 472 received on this interface with TEI=127. 474 ifInMulticastPkts Return zero. 476 ifInBroadcastPkts Return the number of frames received 477 on this interface with TEI=127. 479 ifInDiscards The total number of received frames which have been 480 discarded. 481 The possible reasons are: buffer shortage. 483 ifInErrors The number of inbound frames that contained 484 errors preventing them from being deliverable 485 to LAPD. 487 ifInUnknownProtos The number of frames with known TEI, but unknown 488 SAPI (Service Access Point Identifier, 489 see Q.921 [6], chapter 3.3.3). 491 ifOutOctets The total number of octets transmitted on this 492 interface. 494 ifOutUcastPkts The number of frames transmitted on this 495 interface whose address is not TEI=127. 497 ifOutNUcastPkts Deprecated. Return the number of frames 498 transmitted on this interface with TEI=127. 500 ifOutMulticastPkts 501 Return zero. 503 ifOutBroadcastPkts 504 Return the number of frames transmitted 505 on this interface with TEI=127. 507 ifOutDiscards The total number of outbound frames which 508 were discarded. Possible reasons are: 509 buffer shortage. 511 ifOutErrors The number of frames which could not be 512 transmitted due to errors. 514 ifOutQlen Deprecated. Return zero. 516 ifSpecific Deprecated. Return {0 0}. 518 3.2.4.4. ifEntry for a signaling channel 520 The ifEntry for a signaling channel supports the ifGeneralGroup and the 521 ifPacketGroup of the Interfaces MIB. 523 ifTable Comments 524 ============== =========================================== 525 ifIndex Each ISDN signaling channel is represented by 526 an ifEntry. 528 ifDescr Textual port description. 530 ifType The IANA value of isdn(63). 532 ifSpeed The bandwidth of this signaling channel. Usually, 533 this is the same value as for LAPD, i.e. 16000 534 for basic rate interfaces or 64000 for primary rate 535 interfaces. 537 ifPhysAddress The ISDN address assigned to this signaling channel. 538 This is a copy of isdnSignalingCallingAddress. 540 ifAdminStatus The administrative status of the signaling channel. 542 ifOperStatus The current operational status of this signaling 543 channel. The operational status is dormant(5) if 544 the signaling channel is currently not activated. 545 For other values, refer to the Interfaces MIB. 547 ifLastChange Refer to the Interfaces MIB. 549 ifLinkUpDownTrapEnable 550 Refer to the Interfaces MIB. 552 ifConnectorPresent 553 Refer to the Interfaces MIB. 555 ifHighSpeed Return zero. 557 ifName Refer to the Interfaces MIB. 559 ifMtu The size of the largest frame which can be 560 sent/received on this signaling channel, 561 specified in octets. Usually, this is the 562 default value of 260 as specified in Q.921 563 [6], chapter 5.9.3. 565 ifInOctets The total number of octets received on this 566 signaling channel. 568 ifInUcastPkts The number of frames received which are targeted 569 to this channel. 571 ifInNUcastPkts Deprecated. Return the number of frames 572 received on this signaling channel with TEI=127. 574 ifInMulticastPkts Return zero. 576 ifInBroadcastPkts Return the number of frames received 577 on this signaling channel with TEI=127. 579 ifInDiscards The total number of received frames which have been 580 discarded. 581 The possible reasons are: buffer shortage. 583 ifInErrors The number of inbound frames that contained 584 errors preventing them from being deliverable 585 to the signaling channel. 587 ifInUnknownProtos Return zero. 589 ifOutOctets The total number of octets transmitted on this 590 signaling channel. 592 ifOutUcastPkts The number of frames transmitted on this 593 signaling channel whose address is not TEI=127. 595 ifOutNUcastPkts Deprecated. Return the number of frames 596 transmitted on this signaling channel with TEI=127. 598 ifOutMulticastPkts 599 Return zero. 601 ifOutBroadcastPkts 602 Return the number of frames transmitted 603 on this signaling channel with TEI=127. 605 ifOutDiscards The total number of outbound frames which 606 were discarded. Possible reasons are: 607 buffer shortage. 609 ifOutErrors The number of frames which could not be 610 transmitted due to errors. 612 ifOutQlen Deprecated. Return zero. 614 ifSpecific Deprecated. Return {0 0}. 616 3.3. Relationship to other MIBs 618 3.3.1. Relationship to the DS1/E1 MIB 620 Implementation of the DS1/E1 MIB [12] is not required for supporting 621 this MIB. It is however recommended to implement the DS1/E1 MIB on 622 entities supporting Primary Rate interfaces. 624 3.3.2. Relationship to the DS0 and DS0Bundle MIBs 626 Implementation of the DS0 MIB [13] is optional. 628 Implementation of the DS0Bundle MIB [13] is required only if 629 hyperchannels are to be supported. 631 3.3.3. Relationship to the Dial Control MIB 633 Implementation of the Dial Control MIB [15] is required. 635 3.4. ISDN interface specific information and implementation hints 637 3.4.1. ISDN leased lines 639 ISDN leased lines can be specified on a per-B-channel basis. To do so, 640 the value of isdnBearerChannelType has to be set to leased(2). There is 641 no signaling protocol support for leased line B channels, since there is 642 no signaling protocol action for these kinds of interfaces. 644 If there is no signaling support available for an ISDN interface, this 645 must be specified in the appropriate interface specific table. For 646 Basic Rate interfaces, isdnBasicRateSignalMode of isdnBasicRateTable 647 must be set to inactive(2). For Primary Rate interfaces, dsx1SignalMode 648 of dsx1ConfigTable in DS1/E1 MIB [12] must be set to none(1). There are 649 no isdnLapdTable or isdnSignalingTable entries for such interfaces. 651 Depending on the leased line type and the service provider, the D 652 channel can be used for data transfer. If this is the case the D 653 channel interface type is ds0(81) instead of lapd(77) and its usage is 654 identical to B channel usage if there is no signaling channel available. 656 For a Primary Rate interface which is entirely used as a leased line, 657 there is no ISDN specific information available or required. Such 658 leased lines can entirely be handled by the DS1/E1 MIB. 660 3.4.2. Hyperchannels 662 The active switch protocol defines if hyperchannels are supported, and 663 the actual support is implementation dependent. Hyperchannel 664 connections will be requested by the interface user at call setup time, 665 e.g. by the neighbor connection handling procedures. 667 In the ISDN MIB, the isdnBearerMultirate object of isdnBearerTable can 668 be used to check if hyperchannels are being used for an active call. 670 If hyperchannels are being used, another interface layer is required to 671 map multiple B channels to a single hyperchannel. This is accomplished 672 by using the DS0Bundle MIB [13]. 674 Each hyperchannel call is treated as one call in the 675 isdnSignalingStatsTable, independent of the number of B channels 676 involved. 678 For a hyperchannel call, all objects in the isdnBearerTable entries 679 related to this call (i.e., all isdnBearerTable entries associated to B 680 channels used by the hyperchannel) have identical values. The related 681 objects in the isdnBearerTable are: 683 isdnBearerPeerAddress 684 isdnBearerPeerSubAddress 685 isdnBearerCallOrigin 686 isdnBearerInfoType 687 isdnBearerMultirate 688 isdnBearerCallSetupTime 689 isdnBearerCallConnectTime 690 isdnBearerChargedUnits 692 3.4.3. D channel backup and NFAS trunks 694 D channel backup is defined in Q.931 [8], Annex F. It describes Non- 695 Associated signaling and its use and functionality is basically 696 identical to Non Facility Associated Signaling (NFAS) trunks. 698 Non Facility Accociated Signaling (NFAS) basically means that a D 699 channel on a PRI interface is used to manage calls on other PRI trunks. 700 This is required in North America for H11 channels, since all 24 time 701 slots are being used for B channels. 703 According to Q.931, Annex F, the D channel backup feature can be 704 provided on a subscription basis and is network dependent. The D 705 channel backup procedure is described in detail in Q.931. 707 For D channel backup, the controlling isdnSignalingTable entry is 708 layered on top of all attached LAPD interfaces. This layering is done 709 using the ifStack table. There is only one active LAPD interface, 710 however. Inactive LAPD interfaces have an ifOperStatus of dormant(5). 712 NFAS trunks are also handled using the ifStack table. In this case, a 713 signaling channel is layered on top of a LAPD interface as well as on 714 top of all physical interfaces which are controlled by the signaling 715 channel, but do not supply a D channel. 717 3.4.4. X.25 based packet-mode service in B and D channels 719 X.25 based packet mode service over B channels can be handled using the 720 Dial Control MIB by creating an appropriate neighbor entry. The 721 neighbor entry ifType can then be x25(5), thus providing access to X.25 722 service. 724 X.25 based packet mode service over D channels can be handled by 725 creating an ifEndpointTable entry with an isdnEndpointIfType of 726 x25ple(40). The upper protocol layers can then be attached to this 727 interface using the ifStack table. 729 3.4.5. SPID handling 731 Service Profile IDentifiers (SPIDs) are defined for BRI interfaces only, 732 and being used in North America. SPIDs are required for DMS-100, NI-1 733 and NI-2, and are optional for 5ESS. A switch can define up to 8 SPIDs 734 per BRI. 736 Each Terminal Endpoint has a SPID assigned. It is normally built from 737 the party number (calling address for outgoing calls) with a number of 738 digits prepended and appended. Since each network appears to be 739 different, both the calling address and the SPID have to be stored. 741 The SPID identifies the particular services that have been provisioned 742 for a terminal. If there are two B channels on a BRI, there can be two 743 SPIDs, one for each of the two B channels. There can also be a single 744 SPID, providing access to both B channels. 746 The SPID gets registered with the switch after link establishment. 747 There is one data link for each SPID. As part of terminal registration, 748 an EID (Endpoint IDentifier) is defined by the switch. On incoming 749 calls, the switch may provide the EID, a called party number, or both, 750 depending on the ISDN code implemented in the switch. 752 The EID has two bytes: USID (User Service IDentifier) and TID (Terminal 753 IDentifier). These are later used by some of the software versions 754 running on the switch side (e.g. compliant with NI-1, 5ESS custom) to 755 broadcast SETUP messages with these included, so the correct endpoint 756 would accept the call. Other switch software versions identify the 757 endpoint with the Called Party Number. 759 In the ISDN MIB, the SPID can be entered using the isdnEndpointSpid 760 object of isdnEndpointTable. The isdnSignalingCallingAddress, already 761 being used to specify the calling number, cannot be used to record the 762 SPID since the values of the SPID and the Calling Address may differ and 763 both may be required to be present. 765 3.4.6. Closed User Groups 767 Closed User Groups (CUG), as defined in I.255.1 [14], are supported for 768 circuit mode calls by ETSI (ETS 300 138) and 1TR6. In these networks, 769 an ISDN address can have one or more Closed User Groups assigned. If 770 there is more than one Closed User Group assigned to a given address, 771 one of those is the preferred Closed User Group. For such addresses, 772 only calls from assigned Closed User Groups are accepted by the network. 774 Thus, Closed User Groups are a parameter for neighbor entries and are 775 defined in the Dial Control MIB. A neighbor entry attached to a Closed 776 User Group has to point to an ISDN interface which is attached to the 777 Closed User Group in question. 779 3.4.7. Provision of point-to-point line topology 781 In the ISDN standards, there are two different meanings for the term 782 "point-to-point". 784 In ISDN standards, the term point-to-point are usually used for data 785 link connections, i.e. layer 2 connections, where each layer 2 786 connection from the TE to the network is a single point-to-point 787 connection. Multiple connections of this kind may exist on one physical 788 (layer 1) connection, however, and in case of Basic Rate interfaces 789 there may be several TE's connected to one physical line to the network. 791 The second meaning of "point-to-point" refers to the line topology, i.e. 792 to layer 1 connections. For Primary Rate interfaces, the line topology 793 is always point-to-point. For Basic Rate interfaces, layer 1 point-to- 794 point connections do exist in several countries, usually being used for 795 connecting PBX systems to the network. 797 The second meaning (layer 1 connections) is what will be referred to as 798 "point-to-point" connection throughout this document. 800 For Basic Rate interfaces, the isdnBasicRateTable object 801 isdnBasicRateLineTopology can be used to select the line topology. 803 3.4.8. Speech and audio bearer capability information elements 805 The objects speech(2), audio31(6) and audio7(7), as being used in 806 isdnBearerInfoType, refer to the Speech, 3.1 kHz Audio and old 7 kHz 807 Audio (now Multi-use) bearer capabilities for ISDN, as defined in Q.931 808 [8], chapter 4.5.5, octet 3 of bearer capability information element. 810 These capabilities are signaling artifices that allow networks to do 811 certain things with the call. It is up to the network to decide what to 812 do. 814 The Speech Bearer Capability means that speech is being carried over the 815 channel, as in two people talking. This would be POTS-type speech. The 816 network may compress this, encrypt it or whatever it wants with it as 817 long as it delivers POTS quality speech to the other end. In other 818 words, a modem is not guaranteed to work over this connection. 820 The 3.1 kHz Audio capability indicates that the network carries the 3.1 821 kHz bandwidth across the network. This would (theoretically) allow 822 modem signals to be carried across the network. In the US, the network 823 automatically enters a capability of 3.1 kHz Audio on calls coming into 824 the ISDN from a POTS network. This capability restricts the network 825 from interfering with the data channel in a way that would corrupt the 826 3.1 kHz VoiceBand data. 828 7 kHz Audio was meant to signal the use of a higher quality audio 829 connection (e.g., music from radio). It was changed to Multi-Use 830 capability to allow it to be used for video-conferencing with fall back 831 to audio. 833 In some cases, the Speech or 3.1 kHz Bearer Capability provides a 56 834 kbit/s data path through the network. Therefore, some people are 835 setting up calls with the Speech or 3.1 kHz BC and transmitting 56 836 kbit/s data over the connection. This is usually to take advantage of 837 favorable tariffs for Speech as opposed to Data. 839 On the incoming side, the equipment is usually configured to ignore the 840 Bearer Capability and either answer all Speech calls as 56 kbit/s data 841 or to use one Directory Number for real speech and another for data. 843 3.4.9. Attaching incoming calls to router ports 845 In ISDN, there are several ways to identify an incoming call and to 846 attach a router port to this call. 848 o The call can be identified and attached to a router port using the 849 ISDN Calling Address, that is, the peer ISDN address. Since the 850 peer address is defined in a Dial Control MIB configuration entry 851 for this peer, this would be the most natural way to attach an 852 incoming call to a router port. 854 In this configuration, only a single isdnSignalingTable entry is 855 required for each physical ISDN interface. Unfortunately, the ISDN 856 Calling Address is not available in all countries and/or switch 857 protocols. Therefore, other means for attaching incoming calls to 858 router ports must be provided. 860 o The call can also be identified and attached to a router port using 861 the ISDN Called Address. In this case, a distinct ISDN address or 862 subaddress must be specified for each of the router ports. 864 This can be accomplished in the ISDN MIB by creating a 865 isdnSignalingTable entry for each of the router ports, and by 866 connecting Dial Control MIB neighbor entries to the thereby created 867 interface using the dialCtlNbrCfgLowerIf object of 868 dialCtlNbrCfgTable. 870 If this type of router port identification is used in an 871 implementation, it is up to the implementor to decide if there 872 should be distinct TEI values assigned for each of the 873 isdnSignalingTable entries. For this reason, the isdnEndpointTable 874 permits specifying the same TEI value in multiple entries. It is 875 recommended to use dynamic TEI assignment whenever possible. 877 The implementor should be aware that this type of configuration 878 requires a lot of configuration work for the customer, since an 879 entry in isdnSignalingTable must be created for each of the router 880 ports. 882 o Incoming calls can also be identified and attached to router ports 883 using a higher layer functionality, such as PPP authentication. 884 Defining this functionality is outside the scope of this document. 886 3.4.10. Usage of isdnMibDirectoryGroup and isdnDirectoryTable 888 In some switch protocol or PBX implementations, the Called Number 889 Information Element on incoming calls can differ from the Calling Number 890 on outgoing calls. Sometimes, the Called Number can be different for 891 incoming Local Calls, Long Distance Calls and International Calls. For 892 Hunt Groups, the Called Number can be any of the numbers in the Hunt 893 Group. 895 The isdnDirectoryTable can be used to specify all these numbers. 897 Entries in the isdnDirectoryTable are always connected to specific 898 isdnSignalingTable entries. No ifEntry is created for 899 isdnDirectoryTable entries. Therefore, the isdnDirectoryTable can not 900 be used to attach incoming calls to router ports. For router port 901 identification, isdnSignalingTable entries should be created instead. 903 4. Definitions 905 ISDN-MIB DEFINITIONS ::= BEGIN 907 IMPORTS 908 MODULE-IDENTITY, 909 NOTIFICATION-TYPE, 910 OBJECT-TYPE, 911 Counter32, 912 Gauge32, 913 Integer32 914 FROM SNMPv2-SMI 915 DisplayString, 916 TruthValue, 917 TimeStamp, 918 RowStatus, 919 TestAndIncr, 920 TEXTUAL-CONVENTION 921 FROM SNMPv2-TC 922 MODULE-COMPLIANCE, 923 OBJECT-GROUP 924 FROM SNMPv2-CONF 925 ifIndex, 926 InterfaceIndex 927 FROM IF-MIB 928 IANAifType 929 FROM IANAifType-MIB 930 transmission 931 FROM RFC1213-MIB; 933 isdnMib MODULE-IDENTITY 934 LAST-UPDATED "9608230910Z" -- Aug 23, 1996 935 ORGANIZATION "IETF ISDN MIB Working Group" 936 CONTACT-INFO 937 " Guenter Roeck 938 Postal: cisco Systems 939 170 West Tasman Drive 940 San Jose, CA 95134 941 U.S.A. 942 Phone: +1 408 527 3143 943 E-mail: groeck@cisco.com" 944 DESCRIPTION 945 "The MIB module to describe the 946 management of ISDN interfaces." 947 ::= { transmission 20 } 949 -- The ISDN hardware interface (BRI or PRI) is represented 950 -- by a media specific ifEntry. 951 -- 952 -- For basic rate lines, the media specifics for the physical interface 953 -- is defined in the physical interface group of the ISDN MIB. 955 -- The ifType for physical basic rate interfaces is isdns(75) 956 -- or isdnu(76), whichever is appropriate. 957 -- 958 -- For primary rate, the media specifics are defined in the Trunk 959 -- MIB and the ifType has a value of ds1(18). 961 -- Each signaling channel is represented by an entry 962 -- in the isdnSignalingTable. 963 -- The signaling channel has an ifType value of isdn(63). 964 -- Each B channel is also represented as an entry 965 -- in the ifTable. The B channels have an ifType value 966 -- of ds0(81). 967 -- This model is used while defining objects and tables 968 -- for management. 969 -- The ISDN MIB allows sub-layers. For example, the data transfer 970 -- over a B channel may take place with PPP encapsulation. While the 971 -- ISDN MIB describes the D and B channels, a media specific MIB 972 -- for PPP can be used on a layered basis. This is as per 973 -- the interfaces MIB. 975 -- Textual conventions 977 IsdnSignalingProtocol ::= TEXTUAL-CONVENTION 978 STATUS current 979 DESCRIPTION 980 "This data type is used as the syntax of the 981 isdnSignalingProtocol object in the 982 definition of ISDN-MIB's isdnSignalingTable. 984 The definition of this textual convention with the 985 addition of newly assigned values is published 986 periodically by the IANA, in either the Assigned 987 Numbers RFC, or some derivative of it specific to 988 Internet Network Management number assignments. (The 989 latest arrangements can be obtained by contacting the 990 IANA.) 992 Requests for new values should be made to IANA via 993 email (iana@isi.edu)." 994 SYNTAX INTEGER { 995 other(1), -- none of the following 996 dss1(2), -- ITU DSS1 (formerly CCITT) Q.931 997 etsi(3), -- Europe / ETSI ETS300-102 998 -- plus supplementary services 999 -- (ETSI 300-xxx) 1000 -- note that NET3, NET5 define 1001 -- test procedures for ETS300-102 1002 -- and have been replaced by 1003 -- I-CTR 3 and I-CTR 4. 1004 dass2(4), -- U.K. / DASS2 (PRI) 1005 ess4(5), -- U.S.A. / AT&T 4ESS 1006 ess5(6), -- U.S.A. / AT&T 5ESS 1007 dms100(7), -- U.S.A. / Northern Telecom DMS100 1008 dms250(8), -- U.S.A. / Northern Telecom DMS250 1009 ni1(9), -- U.S.A. / National ISDN 1 (BRI) 1010 ni2(10), -- U.S.A. / National ISDN 2 (BRI, PRI) 1011 ni3(11), -- U.S.A. / next one 1012 vn2(12), -- France / VN2 1013 vn3(13), -- France / VN3 1014 vn4(14), -- France / VN4 (ETSI with changes) 1015 vn6(15), -- France / VN6 (ETSI with changes) 1016 -- delta document CSE P 10-21 A 1017 -- test document CSE P 10-20 A 1018 kdd(16), -- Japan / KDD 1019 ins64(17), -- Japan / NTT INS64 1020 ins1500(18), -- Japan / NTT INS1500 1021 itr6(19), -- Germany/ 1TR6 (BRI, PRI) 1022 cornet(20), -- Germany/ Siemens HiCom CORNET 1023 ts013(21), -- Australia / TS013 1024 -- (formerly TPH 1962, BRI) 1025 ts014(22), -- Australia / TS014 1026 -- (formerly TPH 1856, PRI) 1027 qsig(23), -- Q.SIG 1028 swissnet2(24), -- SwissNet-2 1029 swissnet3(25) -- SwissNet-3 1030 } 1032 -- Isdn Mib objects definitions 1034 isdnMibObjects OBJECT IDENTIFIER ::= { isdnMib 1 } 1036 -- ISDN physical interface group 1038 -- This group describes physical basic rate interfaces. 1040 isdnBasicRateGroup OBJECT IDENTIFIER ::= { isdnMibObjects 1 } 1042 isdnBasicRateTable OBJECT-TYPE 1043 SYNTAX SEQUENCE OF IsdnBasicRateEntry 1044 MAX-ACCESS not-accessible 1045 STATUS current 1046 DESCRIPTION 1047 "Table containing configuration and operational 1048 parameters for all physical Basic Rate 1049 interfaces on this managed device." 1050 ::= { isdnBasicRateGroup 1 } 1052 isdnBasicRateEntry OBJECT-TYPE 1053 SYNTAX IsdnBasicRateEntry 1054 MAX-ACCESS not-accessible 1055 STATUS current 1056 DESCRIPTION 1057 "An entry in the ISDN Basic Rate Table." 1058 INDEX { ifIndex } 1059 ::= { isdnBasicRateTable 1 } 1061 IsdnBasicRateEntry ::= SEQUENCE { 1062 isdnBasicRateIfType INTEGER, 1063 isdnBasicRateLineTopology INTEGER, 1064 isdnBasicRateIfMode INTEGER, 1065 isdnBasicRateSignalMode INTEGER 1066 } 1068 isdnBasicRateIfType OBJECT-TYPE 1069 SYNTAX INTEGER { 1070 isdns(75), 1071 isdnu(76) 1072 } 1073 MAX-ACCESS read-write 1074 STATUS current 1075 DESCRIPTION 1076 "The physical interface type. For 'S/T' interfaces, 1077 also called 'Four-wire Basic Access Interface', 1078 the value of this object is isdns(75). 1079 For 'U' interfaces, also called 'Two-wire Basic 1080 Access Interface', the value of this object is 1081 isdnu(76)." 1082 ::= { isdnBasicRateEntry 1 } 1084 isdnBasicRateLineTopology OBJECT-TYPE 1085 SYNTAX INTEGER { 1086 pointToPoint(1), 1087 pointToMultipoint(2) 1088 } 1089 MAX-ACCESS read-write 1090 STATUS current 1091 DESCRIPTION 1092 "The line topology to be used for this interface. 1093 Note that setting isdnBasicRateIfType to isdns(75) 1094 does not necessarily mean a line topology of 1095 point-to-multipoint." 1096 ::= { isdnBasicRateEntry 2 } 1098 isdnBasicRateIfMode OBJECT-TYPE 1099 SYNTAX INTEGER { 1100 te(1), 1101 nt(2) 1102 } 1103 MAX-ACCESS read-write 1104 STATUS current 1105 DESCRIPTION 1106 "The physical interface mode. For TE mode, the value 1107 of this object is te(1). For NT mode, the value 1108 of this object is nt(2)." 1109 ::= { isdnBasicRateEntry 3 } 1111 isdnBasicRateSignalMode OBJECT-TYPE 1112 SYNTAX INTEGER { 1113 active(1), 1114 inactive(2) 1115 } 1116 MAX-ACCESS read-write 1117 STATUS current 1118 DESCRIPTION 1119 "The signaling channel operational mode for this interface. 1120 If active(1) there is a signaling channel on this 1121 interface. If inactive(2) a signaling channel is 1122 not available." 1123 ::= { isdnBasicRateEntry 4 } 1125 -- The B channel (bearer channel) group 1127 -- Note that disconnects can explicitely be handled using the 1128 -- ifStack table. If a connection is to be disconnected, 1129 -- the according ifStack entry has to be removed. 1130 -- More specifically, the ifStackTable entry which binds the high-layer 1131 -- ifTable entry (and related dialCtlNbrCfgTable entry) to the 1132 -- B channel ifTable entry (and related isdnBearerTable entry) 1133 -- during an active call has to be removed. 1135 isdnBearerGroup OBJECT IDENTIFIER ::= { isdnMibObjects 2 } 1137 isdnBearerTable OBJECT-TYPE 1138 SYNTAX SEQUENCE OF IsdnBearerEntry 1139 MAX-ACCESS not-accessible 1140 STATUS current 1141 DESCRIPTION 1142 "This table defines port specific operational, statistics 1143 and active call data for ISDN B channels. Each entry 1144 in this table describes one B (bearer) channel." 1145 ::= { isdnBearerGroup 1 } 1147 isdnBearerEntry OBJECT-TYPE 1148 SYNTAX IsdnBearerEntry 1149 MAX-ACCESS not-accessible 1150 STATUS current 1151 DESCRIPTION 1152 "Operational and statistics information relating to 1153 one port. A port is a single B channel." 1154 INDEX { ifIndex } 1155 ::= { isdnBearerTable 1 } 1157 IsdnBearerEntry ::= 1158 SEQUENCE { 1159 isdnBearerChannelType INTEGER, 1160 isdnBearerOperStatus INTEGER, 1161 isdnBearerChannelNumber INTEGER, 1162 isdnBearerPeerAddress DisplayString, 1163 isdnBearerPeerSubAddress DisplayString, 1164 isdnBearerCallOrigin INTEGER, 1165 isdnBearerInfoType INTEGER, 1166 isdnBearerMultirate TruthValue, 1167 isdnBearerCallSetupTime TimeStamp, 1168 isdnBearerCallConnectTime TimeStamp, 1169 isdnBearerChargedUnits Gauge32 1170 } 1172 isdnBearerChannelType OBJECT-TYPE 1173 SYNTAX INTEGER { 1174 dialup(1), 1175 leased(2) 1176 } 1177 MAX-ACCESS read-write 1178 STATUS current 1179 DESCRIPTION 1180 "The B channel type. If the B channel is connected 1181 to a dialup line, this object has a value of 1182 dialup(1). In this case, it is controlled by 1183 an associated signaling channel. If the B channel 1184 is connected to a leased line, this object has 1185 a value of leased(2). For leased line B channels, there 1186 is no signaling channel control available." 1187 ::= { isdnBearerEntry 1 } 1189 isdnBearerOperStatus OBJECT-TYPE 1190 SYNTAX INTEGER { 1191 idle(1), 1192 connecting(2), 1193 connected(3), 1194 active(4) 1195 } 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "The current call control state for this port. 1200 idle(1): The B channel is idle. 1201 No call or call attempt is going on. 1202 connecting(2): A connection attempt (outgoing call) 1203 is being made on this interface. 1204 connected(3): An incoming call is in the process 1205 of validation. 1206 active(4): A call is active on this interface." 1207 ::= { isdnBearerEntry 2 } 1209 isdnBearerChannelNumber OBJECT-TYPE 1210 SYNTAX INTEGER (1..30) 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "The identifier being used by a signaling protocol 1215 to identify this B channel, also referred to as 1216 B channel number. If the Agent also supports the DS0 MIB, 1217 the values of isdnBearerChannelNumber and dsx0Ds0Number 1218 must be identical for a given B channel." 1219 ::= { isdnBearerEntry 3 } 1221 isdnBearerPeerAddress OBJECT-TYPE 1222 SYNTAX DisplayString 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "The ISDN address the current or last call is or was 1227 connected to. 1229 In some cases, the format of this information can not 1230 be predicted, since it largely depends on the type 1231 of switch or PBX the device is connected to. Therefore, 1232 the detailed format of this information is not 1233 specified and is implementation dependent. 1235 If possible, the agent should supply this information 1236 using the E.164 format. In this case, the number must 1237 start with '+'. Otherwise, IA5 number digits must be used. 1239 If the peer ISDN address is not available, 1240 this object has a length of zero." 1241 REFERENCE 1242 "ITU-T E.164, Q.931 chapter 4.5.10" 1243 ::= { isdnBearerEntry 4 } 1245 isdnBearerPeerSubAddress OBJECT-TYPE 1246 SYNTAX DisplayString 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "The ISDN subaddress the current or last call is or was 1251 connected to. 1253 The subaddress is an user supplied string of up to 20 1254 IA5 characters and is transmitted transparently through 1255 the network. 1257 If the peer subaddress is not available, this object 1258 has a length of zero." 1259 REFERENCE 1260 "ITU-T I.330, Q.931 chapter 4.5.11" 1261 ::= { isdnBearerEntry 5 } 1263 isdnBearerCallOrigin OBJECT-TYPE 1264 SYNTAX INTEGER { 1265 unknown(1), 1266 originate(2), 1267 answer(3), 1268 callback(4) 1269 } 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The call origin for the current or last call. If since 1274 system startup there was no call on this interface, 1275 this object has a value of unknown(1)." 1276 ::= { isdnBearerEntry 6 } 1278 isdnBearerInfoType OBJECT-TYPE 1279 SYNTAX INTEGER { 1280 unknown(1), 1281 speech(2), 1282 unrestrictedDigital(3), -- as defined in Q.931 1283 unrestrictedDigital56(4), -- with 56k rate adaption 1284 restrictedDigital(5), 1285 audio31(6), -- 3.1 kHz audio 1286 audio7(7), -- 7 kHz audio 1287 video(8), 1288 packetSwitched(9) 1289 } 1290 MAX-ACCESS read-only 1291 STATUS current 1292 DESCRIPTION 1293 "The Information Transfer Capability for the current 1294 or last call. 1296 speech(2) refers to a non-data connection, whereas 1297 audio31(6) and audio7(7) refer to data mode connections. 1299 Note that Q.931, chapter 4.5.5, originally defined 1300 audio7(7) as '7 kHz audio' and now defines it as 1301 'Unrestricted digital information with tones/ 1302 announcements'. 1304 If since system startup there has been no call on this 1305 interface, this object has a value of unknown(1)." 1306 REFERENCE 1307 "Q.931 [8], chapter 4.5.5, octet 3 of bearer capability 1308 information element, combined with the User Rate 1309 (as defined in octets 5 and 5a to 5d), if rate adaption 1310 is being used." 1311 ::= { isdnBearerEntry 7 } 1313 isdnBearerMultirate OBJECT-TYPE 1314 SYNTAX TruthValue 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "This flag indicates if the current or last call used 1319 multirate. The actual information transfer rate, 1320 in detail specified in octet 4.1 (rate multiplier), 1321 is the sum of all B channel ifSpeed values for 1322 the hyperchannel. 1324 If since system startup there was no call on this 1325 interface, this object has a value of false(2)." 1326 REFERENCE 1327 "Q.931 [8], chapter 4.5.5." 1328 ::= { isdnBearerEntry 8 } 1330 isdnBearerCallSetupTime OBJECT-TYPE 1331 SYNTAX TimeStamp 1332 MAX-ACCESS read-only 1333 STATUS current 1334 DESCRIPTION 1335 "The value of sysUpTime when the ISDN setup message for 1336 the current or last call was sent or received. If since 1337 system startup there has been no call on this interface, 1338 this object has a value of zero." 1339 ::= { isdnBearerEntry 9 } 1341 isdnBearerCallConnectTime OBJECT-TYPE 1342 SYNTAX TimeStamp 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "The value of sysUpTime when the ISDN connect message for 1347 the current or last call was sent or received. If since 1348 system startup there has been no call on this interface, 1349 this object has a value of zero." 1350 ::= { isdnBearerEntry 10 } 1352 isdnBearerChargedUnits OBJECT-TYPE 1353 SYNTAX Gauge32 1354 MAX-ACCESS read-only 1355 STATUS current 1356 DESCRIPTION 1357 "The number of charged units for the current or last 1358 connection. For incoming calls or if charging information 1359 is not supplied by the switch, the value of this object 1360 is zero." 1361 ::= { isdnBearerEntry 11 } 1363 -- ISDN signaling group 1365 isdnSignalingGroup OBJECT IDENTIFIER ::= { isdnMibObjects 3 } 1367 -- signaling channel configuration table 1368 -- There is one entry in this table for each Terminal Endpoint 1369 -- (link layer connection to the switch). 1370 -- Usually, there is one endpoint per D channel. In some 1371 -- cases, however, there can be multiple endpoints. 1372 -- Thus, entries in this table can be created and deleted. 1373 -- This also means the creation of an associated ifEntry. 1374 -- 1375 -- D channel backup and NFAS trunks are handled using the 1376 -- ifStack table. 1377 -- In case of D channel backup, there are multiple 1378 -- Data Link Layer (LAPD) interfaces. Only one interface is 1379 -- active; all others are dormant(5). 1380 -- In case of NFAS trunks, one lower interface is the 1381 -- LAPD interface, while the other lower interfaces are physical 1382 -- interfaces. 1384 -- If directory number and calling address differ from each other 1385 -- or multiple directory numbers are being used, 1386 -- the isdnDirectoryTable has to be used to enter such 1387 -- directory numbers. 1389 isdnSignalingGetIndex OBJECT-TYPE 1390 SYNTAX TestAndIncr 1391 MAX-ACCESS read-write 1392 STATUS current 1393 DESCRIPTION 1394 "The recommended procedure for selecting a new index for 1395 isdnSignalingTable row creation is to GET the value of 1396 this object, and then to SET the object with the same 1397 value. If the SET operation succeeds, the manager can use 1398 this value as an index to create a new row in this table." 1399 REFERENCE 1400 "RFC1903, TestAndIncr textual convention." 1401 ::= { isdnSignalingGroup 1 } 1403 isdnSignalingTable OBJECT-TYPE 1404 SYNTAX SEQUENCE OF IsdnSignalingEntry 1405 MAX-ACCESS not-accessible 1406 STATUS current 1407 DESCRIPTION 1408 "ISDN signaling table containing configuration and 1409 operational parameters for all ISDN signaling 1410 channels on this managed device." 1411 ::= { isdnSignalingGroup 2 } 1413 isdnSignalingEntry OBJECT-TYPE 1414 SYNTAX IsdnSignalingEntry 1415 MAX-ACCESS not-accessible 1416 STATUS current 1417 DESCRIPTION 1418 "An entry in the ISDN Signaling Table. To create a new 1419 entry, only isdnSignalingProtocol needs to be specified 1420 before isdnSignalingStatus can become active(1)." 1421 INDEX { isdnSignalingIndex } 1422 ::= { isdnSignalingTable 1 } 1424 IsdnSignalingEntry ::= SEQUENCE { 1425 isdnSignalingIndex INTEGER, 1426 isdnSignalingIfIndex InterfaceIndex, 1427 isdnSignalingProtocol IsdnSignalingProtocol, 1428 isdnSignalingCallingAddress DisplayString, 1429 isdnSignalingSubAddress DisplayString, 1430 isdnSignalingBchannelCount Integer32, 1431 isdnSignalingInfoTrapEnable INTEGER, 1432 isdnSignalingStatus RowStatus 1433 } 1435 isdnSignalingIndex OBJECT-TYPE 1436 SYNTAX INTEGER (1..2147483647) 1437 MAX-ACCESS not-accessible 1438 STATUS current 1439 DESCRIPTION 1440 "The index value which uniquely identifies an entry 1441 in the isdnSignalingTable." 1442 ::= { isdnSignalingEntry 1 } 1444 isdnSignalingIfIndex OBJECT-TYPE 1445 SYNTAX InterfaceIndex 1446 MAX-ACCESS read-only 1447 STATUS current 1448 DESCRIPTION 1449 "The ifIndex value of the interface associated with this 1450 signaling channel." 1451 ::= { isdnSignalingEntry 2 } 1453 isdnSignalingProtocol OBJECT-TYPE 1454 SYNTAX IsdnSignalingProtocol 1455 MAX-ACCESS read-create 1456 STATUS current 1457 DESCRIPTION 1458 "The particular protocol type supported by the 1459 switch providing access to the ISDN network 1460 to which this signaling channel is connected." 1461 ::= { isdnSignalingEntry 3 } 1463 isdnSignalingCallingAddress OBJECT-TYPE 1464 SYNTAX DisplayString 1465 MAX-ACCESS read-create 1466 STATUS current 1467 DESCRIPTION 1468 "The ISDN Address to be assigned to this signaling 1469 channel. More specifically, this is the 'Calling Address 1470 information element' as being passed to the switch 1471 in outgoing call setup messages. 1473 It can be an EAZ (1TR6), a calling number (DSS1, ETSI) 1474 or any other number necessary to identify a signaling 1475 interface. If there is no such number defined or required, 1476 this is a zero length string. It is represented in 1477 DisplayString form. 1479 Incoming calls can also be identified by this number. 1480 If the Directory Number, i.e. the Called Number in 1481 incoming calls, is different to this number, the 1482 isdnDirectoryTable has to be used to specify all 1483 possible Directory Numbers. 1485 The format of this information largely depends on the type 1486 of switch or PBX the device is connected to. Therefore, 1487 the detailed format of this information is not 1488 specified and is implementation dependent. 1490 If possible, the agent should implement this information 1491 using the E.164 number format. In this case, the number 1492 must start with '+'. Otherwise, IA5 number digits must 1493 be used." 1494 REFERENCE 1495 "ITU-T E.164, Q.931 chapter 4.5.10" 1496 DEFVAL { "" } 1497 ::= { isdnSignalingEntry 4 } 1499 isdnSignalingSubAddress OBJECT-TYPE 1500 SYNTAX DisplayString 1501 MAX-ACCESS read-create 1502 STATUS current 1503 DESCRIPTION 1504 "Supplementary information to the ISDN address assigned 1505 to this signaling channel. Usually, this is the 1506 subaddress as defined in Q.931. 1507 If there is no such number defined or required, this is 1508 a zero length string. 1509 The subaddress is used for incoming calls as well as 1510 for outgoing calls. 1511 The subaddress is an user supplied string of up to 20 1512 IA5 characters and is transmitted transparently through 1513 the network." 1514 REFERENCE 1515 "ITU-T I.330, Q.931 chapter 4.5.11" 1516 DEFVAL { "" } 1517 ::= { isdnSignalingEntry 5 } 1519 isdnSignalingBchannelCount OBJECT-TYPE 1520 SYNTAX Integer32 (1..65535) 1521 MAX-ACCESS read-create 1522 STATUS current 1523 DESCRIPTION 1524 "The total number of B channels (bearer channels) 1525 managed by this signaling channel. The default value 1526 of this object depends on the physical interface type 1527 and is either 2 for Basic Rate interfaces or 1528 24 (30) for Primary Rate interfaces." 1529 ::= { isdnSignalingEntry 6 } 1531 isdnSignalingInfoTrapEnable OBJECT-TYPE 1532 SYNTAX INTEGER { 1533 enabled(1), 1534 disabled(2) 1535 } 1536 MAX-ACCESS read-create 1537 STATUS current 1538 DESCRIPTION 1539 "Indicates whether isdnMibCallInformation traps 1540 should be generated for calls on this signaling 1541 channel." 1542 DEFVAL { disabled } 1543 ::= { isdnSignalingEntry 7 } 1545 isdnSignalingStatus OBJECT-TYPE 1546 SYNTAX RowStatus 1547 MAX-ACCESS read-create 1548 STATUS current 1549 DESCRIPTION 1550 "This object is used to create and delete rows in the 1551 isdnSignalingTable." 1552 ::= { isdnSignalingEntry 8 } 1554 -- Signaling channel statistics table 1555 -- There is one entry for each signaling connection 1556 -- in this table. 1557 -- Note that the ifEntry also has some statistics information. 1559 isdnSignalingStatsTable OBJECT-TYPE 1560 SYNTAX SEQUENCE OF IsdnSignalingStatsEntry 1561 MAX-ACCESS not-accessible 1562 STATUS current 1563 DESCRIPTION 1564 "ISDN signaling table containing statistics 1565 information for all ISDN signaling channels 1566 on this managed device. 1567 Only statistical information which is not already being 1568 counted in the ifTable is being defined in this table." 1569 ::= { isdnSignalingGroup 3 } 1571 isdnSignalingStatsEntry OBJECT-TYPE 1572 SYNTAX IsdnSignalingStatsEntry 1573 MAX-ACCESS not-accessible 1574 STATUS current 1575 DESCRIPTION 1576 "An entry in the ISDN Signaling statistics Table." 1577 AUGMENTS { isdnSignalingEntry } 1578 ::= { isdnSignalingStatsTable 1 } 1580 IsdnSignalingStatsEntry ::= SEQUENCE { 1581 isdnSigStatsInCalls Counter32, 1582 isdnSigStatsInConnected Counter32, 1583 isdnSigStatsOutCalls Counter32, 1584 isdnSigStatsOutConnected Counter32, 1585 isdnSigStatsChargedUnits Counter32 1586 } 1588 isdnSigStatsInCalls OBJECT-TYPE 1589 SYNTAX Counter32 1590 MAX-ACCESS read-only 1591 STATUS current 1592 DESCRIPTION 1593 "The number of incoming calls on this interface." 1594 ::= { isdnSignalingStatsEntry 1 } 1596 isdnSigStatsInConnected OBJECT-TYPE 1597 SYNTAX Counter32 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "The number of incoming calls on this interface 1602 which were actually connected." 1603 ::= { isdnSignalingStatsEntry 2 } 1605 isdnSigStatsOutCalls OBJECT-TYPE 1606 SYNTAX Counter32 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "The number of outgoing calls on this interface." 1611 ::= { isdnSignalingStatsEntry 3 } 1613 isdnSigStatsOutConnected OBJECT-TYPE 1614 SYNTAX Counter32 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "The number of outgoing calls on this interface 1619 which were actually connected." 1620 ::= { isdnSignalingStatsEntry 4 } 1622 isdnSigStatsChargedUnits OBJECT-TYPE 1623 SYNTAX Counter32 1624 MAX-ACCESS read-only 1625 STATUS current 1626 DESCRIPTION 1627 "The number of charging units on this interface since 1628 system startup. 1629 Only the charging units applying to the local interface, 1630 i.e. for originated calls or for calls with 'Reverse 1631 charging' being active, are counted here." 1633 ::= { isdnSignalingStatsEntry 5 } 1635 -- 1636 -- The LAPD table 1638 isdnLapdTable OBJECT-TYPE 1639 SYNTAX SEQUENCE OF IsdnLapdEntry 1640 MAX-ACCESS not-accessible 1641 STATUS current 1642 DESCRIPTION 1643 "Table containing configuration and statistics 1644 information for all LAPD (D channel Data Link) 1645 interfaces on this managed device. 1646 Only statistical information which is not already being 1647 counted in the ifTable is being defined in this table." 1648 ::= { isdnSignalingGroup 4 } 1650 isdnLapdEntry OBJECT-TYPE 1651 SYNTAX IsdnLapdEntry 1652 MAX-ACCESS not-accessible 1653 STATUS current 1654 DESCRIPTION 1655 "An entry in the LAPD Table." 1656 INDEX { ifIndex } 1657 ::= { isdnLapdTable 1 } 1659 IsdnLapdEntry ::= SEQUENCE { 1660 isdnLapdPrimaryChannel TruthValue, 1661 isdnLapdOperStatus INTEGER, 1662 isdnLapdPeerSabme Counter32, 1663 isdnLapdRecvdFrmr Counter32 1664 } 1666 isdnLapdPrimaryChannel OBJECT-TYPE 1667 SYNTAX TruthValue 1668 MAX-ACCESS read-write 1669 STATUS current 1670 DESCRIPTION 1671 "If set to true(1), this D channel is the designated 1672 primary D channel if D channel backup is active. 1673 There must be exactly one primary D channel 1674 configured. If D channel backup is not used, this 1675 object has a value of true(1)." 1676 REFERENCE 1677 "Q.931 [8], Annex F, D channel backup procedures." 1678 ::= { isdnLapdEntry 1 } 1680 isdnLapdOperStatus OBJECT-TYPE 1681 SYNTAX INTEGER { 1682 inactive(1), 1683 l1Active(2), 1684 l2Active(3) 1686 } 1687 MAX-ACCESS read-only 1688 STATUS current 1689 DESCRIPTION 1690 "The operational status of this interface: 1692 inactive all layers are inactive 1693 l1Active layer 1 is activated, 1694 layer 2 datalink not established 1695 l2Active layer 1 is activated, 1696 layer 2 datalink established." 1697 ::= { isdnLapdEntry 2 } 1699 isdnLapdPeerSabme OBJECT-TYPE 1700 SYNTAX Counter32 1701 MAX-ACCESS read-only 1702 STATUS current 1703 DESCRIPTION 1704 "The number of peer SABME frames received on this 1705 interface. This is the number of peer-initiated 1706 new connections on this interface." 1707 ::= { isdnLapdEntry 3 } 1709 isdnLapdRecvdFrmr OBJECT-TYPE 1710 SYNTAX Counter32 1711 MAX-ACCESS read-only 1712 STATUS current 1713 DESCRIPTION 1714 "The number of LAPD FRMR response frames received. 1715 This is the number of framing errors on this 1716 interface." 1717 ::= { isdnLapdEntry 4 } 1719 -- 1720 -- Optional groups follow here. 1722 -- The Terminal Endpoint group and table 1724 -- This table is required only if TEI values or SPID numbers 1725 -- have to be entered. 1726 -- The ifIndex values for this table are identical to those of 1727 -- the isdnSignalingChannel table. 1729 isdnEndpointGroup OBJECT IDENTIFIER ::= { isdnMibObjects 4 } 1731 isdnEndpointGetIndex OBJECT-TYPE 1732 SYNTAX TestAndIncr 1733 MAX-ACCESS read-write 1734 STATUS current 1735 DESCRIPTION 1736 "The recommended procedure for selecting a new index for 1737 isdnEndpointTable row creation is to GET the value of 1738 this object, and then to SET the object with the same 1739 value. If the SET operation succeeds, the manager can use 1740 this value as an index to create a new row in this table." 1741 REFERENCE 1742 "RFC1903, TestAndIncr textual convention." 1743 ::= { isdnEndpointGroup 1 } 1745 isdnEndpointTable OBJECT-TYPE 1746 SYNTAX SEQUENCE OF IsdnEndpointEntry 1747 MAX-ACCESS not-accessible 1748 STATUS current 1749 DESCRIPTION 1750 "Table containing configuration for Terminal 1751 Endpoints." 1752 ::= { isdnEndpointGroup 2 } 1754 isdnEndpointEntry OBJECT-TYPE 1755 SYNTAX IsdnEndpointEntry 1756 MAX-ACCESS not-accessible 1757 STATUS current 1758 DESCRIPTION 1759 "An entry in the Terminal Endpoint Table. The value 1760 of isdnEndpointIfType must be supplied for a row 1761 in this table to become active." 1762 INDEX { isdnEndpointIndex } 1763 ::= { isdnEndpointTable 1 } 1765 IsdnEndpointEntry ::= SEQUENCE { 1766 isdnEndpointIndex INTEGER, 1767 isdnEndpointIfIndex InterfaceIndex, 1768 isdnEndpointIfType IANAifType, 1769 isdnEndpointTeiType INTEGER, 1770 isdnEndpointTeiValue INTEGER, 1771 isdnEndpointSpid DisplayString, 1772 isdnEndpointStatus RowStatus 1773 } 1775 isdnEndpointIndex OBJECT-TYPE 1776 SYNTAX INTEGER (1..2147483647) 1777 MAX-ACCESS not-accessible 1778 STATUS current 1779 DESCRIPTION 1780 "The index value which uniquely identifies an entry 1781 in the isdnEndpointTable." 1782 ::= { isdnEndpointEntry 1 } 1784 isdnEndpointIfIndex OBJECT-TYPE 1785 SYNTAX InterfaceIndex 1786 MAX-ACCESS read-only 1787 STATUS current 1788 DESCRIPTION 1789 "The ifIndex value of the interface associated with this 1790 Terminal Endpoint." 1791 ::= { isdnEndpointEntry 2 } 1793 isdnEndpointIfType OBJECT-TYPE 1794 SYNTAX IANAifType 1795 MAX-ACCESS read-create 1796 STATUS current 1797 DESCRIPTION 1798 "The interface type for this Terminal Endpoint. 1799 Interface types of x25ple(40) and isdn(63) are allowed. 1800 The interface type is identical to the value of 1801 ifType in the associated ifEntry." 1802 ::= { isdnEndpointEntry 3 } 1804 isdnEndpointTeiType OBJECT-TYPE 1805 SYNTAX INTEGER { 1806 dynamic(1), 1807 static(2) 1808 } 1809 MAX-ACCESS read-create 1810 STATUS current 1811 DESCRIPTION 1812 "The type of TEI (Terminal Endpoint Identifier) 1813 used for this Terminal Endpoint. In case of dynamic(1), 1814 the TEI value is selected by the switch. In 1815 case of static(2), a valid TEI value has to be 1816 entered in the isdnEndpointTeiValue object. 1817 The default value for this object depends on the 1818 interface type as well as the Terminal Endpoint type. 1819 On Primary Rate interfaces the default value is 1820 static(2). On Basic Rate interfaces the default value 1821 is dynamic(1) for isdn(63) Terminal Endpoints and 1822 static(2) for x25ple(40) Terminal Endpoints." 1823 ::= { isdnEndpointEntry 4 } 1825 isdnEndpointTeiValue OBJECT-TYPE 1826 SYNTAX INTEGER ( 0..255 ) 1827 MAX-ACCESS read-create 1828 STATUS current 1829 DESCRIPTION 1830 "The TEI (Terminal Endpoint Identifier) value 1831 for this Terminal Endpoint. If isdnEndpointTeiType 1832 is set to static(2), valid numbers are 0..63, 1833 while otherwise the value is set internally. 1834 The default value of this object is 0 for static 1835 TEI assignment. 1836 The default value for dynamic TEI assignment is also 1837 0 as long as no TEI has been assigned. After TEI 1838 assignment, the assigned TEI value is returned." 1839 ::= { isdnEndpointEntry 5 } 1841 isdnEndpointSpid OBJECT-TYPE 1842 SYNTAX DisplayString 1843 MAX-ACCESS read-create 1844 STATUS current 1845 DESCRIPTION 1846 "The Service profile IDentifier (SPID) information 1847 for this Terminal Endpoint. 1849 The SPID is composed of 9-20 numeric characters. 1851 This information has to be defined in addition to 1852 the local number for some switch protocol types, 1853 e.g. Bellcore NI-1 and NI-2. 1855 If this object is not required, it is a 1856 zero length string." 1857 REFERENCE 1858 "Bellcore SR-NWT-001953, Generic Guidelines for ISDN 1859 Terminal Equipment on Basic Access Interfaces, 1860 Chapter 8.5.1." 1861 DEFVAL { "" } 1862 ::= { isdnEndpointEntry 6 } 1864 isdnEndpointStatus OBJECT-TYPE 1865 SYNTAX RowStatus 1866 MAX-ACCESS read-create 1867 STATUS current 1868 DESCRIPTION 1869 "This object is used to create and delete rows in the 1870 isdnEndpointTable." 1871 ::= { isdnEndpointEntry 7 } 1873 -- 1874 -- The Directory Number group 1875 -- 1877 isdnDirectoryGroup OBJECT IDENTIFIER ::= { isdnMibObjects 5 } 1879 isdnDirectoryTable OBJECT-TYPE 1880 SYNTAX SEQUENCE OF IsdnDirectoryEntry 1881 MAX-ACCESS not-accessible 1882 STATUS current 1883 DESCRIPTION 1884 "Table containing Directory Numbers." 1885 ::= { isdnDirectoryGroup 1 } 1887 isdnDirectoryEntry OBJECT-TYPE 1888 SYNTAX IsdnDirectoryEntry 1889 MAX-ACCESS not-accessible 1890 STATUS current 1891 DESCRIPTION 1892 "An entry in the Directory Number Table. All objects 1893 in an entry must be set for a new row to become active." 1895 INDEX { isdnDirectoryIndex } 1896 ::= { isdnDirectoryTable 1 } 1898 IsdnDirectoryEntry ::= SEQUENCE { 1899 isdnDirectoryIndex INTEGER, 1900 isdnDirectoryNumber DisplayString, 1901 isdnDirectorySigIndex INTEGER, 1902 isdnDirectoryStatus RowStatus 1903 } 1905 isdnDirectoryIndex OBJECT-TYPE 1906 SYNTAX INTEGER ( 1..'7fffffff'h ) 1907 MAX-ACCESS not-accessible 1908 STATUS current 1909 DESCRIPTION 1910 "The index value which uniquely identifies an entry 1911 in the isdnDirectoryTable." 1912 ::= { isdnDirectoryEntry 1 } 1914 isdnDirectoryNumber OBJECT-TYPE 1915 SYNTAX DisplayString 1916 MAX-ACCESS read-create 1917 STATUS current 1918 DESCRIPTION 1919 "A Directory Number. Directory Numbers are used 1920 to identify incoming calls on the signaling 1921 channel given in isdnDirectorySigIndex. 1923 The format of this information largely depends on the type 1924 of switch or PBX the device is connected to. Therefore, 1925 the detailed format of this information is not 1926 specified and is implementation dependent. 1928 If possible, the agent should implement this information 1929 using the E.164 number format. In this case, the number 1930 must start with '+'. Otherwise, IA5 number digits must 1931 be used." 1932 REFERENCE 1933 "ITU-T E.164, Q.931 chapter 4.5.10" 1934 ::= { isdnDirectoryEntry 2 } 1936 isdnDirectorySigIndex OBJECT-TYPE 1937 SYNTAX INTEGER (1..2147483647) 1938 MAX-ACCESS read-create 1939 STATUS current 1940 DESCRIPTION 1941 "An index pointing to an ISDN signaling channel. 1942 Incoming calls are accepted on this 1943 signaling channel if the isdnDirectoryNumber is 1944 presented as Called Number in the SETUP message." 1945 ::= { isdnDirectoryEntry 3 } 1947 isdnDirectoryStatus OBJECT-TYPE 1948 SYNTAX RowStatus 1949 MAX-ACCESS read-create 1950 STATUS current 1951 DESCRIPTION 1952 "This object is used to create and delete rows in the 1953 isdnDirectoryTable." 1954 ::= { isdnDirectoryEntry 4 } 1956 -- Traps 1958 isdnMibTrapPrefix OBJECT IDENTIFIER ::= { isdnMib 2 } 1959 isdnMibTraps OBJECT IDENTIFIER ::= { isdnMibTrapPrefix 0 } 1961 isdnMibCallInformation NOTIFICATION-TYPE 1962 OBJECTS { 1963 ifIndex, -- isdnBearerTable ifIndex 1964 isdnBearerOperStatus, 1965 isdnBearerPeerAddress, 1966 isdnBearerPeerSubAddress, 1967 isdnBearerCallSetupTime, 1968 isdnBearerInfoType, 1969 isdnBearerCallOrigin 1970 } 1971 STATUS current 1972 DESCRIPTION 1973 "This trap/inform is sent to the manager under the 1974 following condidions: 1975 - on incoming calls for each call which is rejected for 1976 policy reasons (e.g. unknown neighbor or access 1977 violation) 1978 - on outgoing calls whenever a call attempt is determined 1979 to have ultimately failed. In the event that call retry 1980 is active, then this will be after all retry attempts 1981 have failed. 1982 - whenever a call connects. In this case, the object 1983 isdnBearerCallConnectTime should be included in the 1984 trap. 1986 Only one such trap is sent in between successful or 1987 unsuccessful call attempts from or to a single neighbor; 1988 subsequent call attempts result in no trap. 1990 If the Dial Control MIB objects dialCtlNbrCfgId and 1991 dialCtlNbrCfgIndex are known by the entity generating 1992 this trap, both objects should be included in the trap 1993 as well. The receipt of this trap with no dial neighbor 1994 information indicates that the manager must poll the 1995 callHistoryTable of the Dial Control MIB to see what 1996 changed." 1997 ::= { isdnMibTraps 1 } 1999 -- 2000 -- conformance information 2001 -- 2003 isdnMibConformance OBJECT IDENTIFIER ::= { isdnMib 2 } 2004 isdnMibCompliances OBJECT IDENTIFIER ::= { isdnMibConformance 1 } 2005 isdnMibGroups OBJECT IDENTIFIER ::= { isdnMibConformance 2 } 2007 -- compliance statements 2009 isdnMibCompliance MODULE-COMPLIANCE 2010 STATUS current 2011 DESCRIPTION 2012 "The compliance statement for entities which implement 2013 the ISDN MIB." 2014 MODULE -- this module 2016 -- unconditionally mandatory groups 2017 MANDATORY-GROUPS { 2018 isdnMibSignalingGroup, 2019 isdnMibBearerGroup 2020 } 2022 -- conditionally mandatory group 2023 GROUP isdnMibBasicRateGroup 2024 DESCRIPTION 2025 "The isdnMibBasicRateGroup is mandatory for entities 2026 supporting ISDN Basic Rate interfaces." 2028 -- optional groups 2029 GROUP isdnMibEndpointGroup 2030 DESCRIPTION 2031 "Implementation of this group is optional for all systems 2032 that attach to ISDN interfaces." 2034 GROUP isdnMibDirectoryGroup 2035 DESCRIPTION 2036 "Implementation of this group is optional for all systems 2037 that attach to ISDN interfaces." 2039 OBJECT isdnBasicRateIfType 2040 MIN-ACCESS read-only 2041 DESCRIPTION 2042 "It is conformant to implement this object as read-only." 2044 OBJECT isdnBasicRateLineTopology 2045 MIN-ACCESS read-only 2046 DESCRIPTION 2047 "It is conformant to implement this object as read-only." 2049 OBJECT isdnBasicRateIfMode 2050 MIN-ACCESS read-only 2051 DESCRIPTION 2052 "It is conformant to implement this object as read-only." 2054 OBJECT isdnBasicRateSignalMode 2055 MIN-ACCESS read-only 2056 DESCRIPTION 2057 "It is conformant to implement this object as read-only." 2059 ::= { isdnMibCompliances 1 } 2061 -- units of conformance 2063 isdnMibBasicRateGroup OBJECT-GROUP 2064 OBJECTS { 2065 isdnBasicRateIfType, 2066 isdnBasicRateLineTopology, 2067 isdnBasicRateIfMode, 2068 isdnBasicRateSignalMode 2069 } 2070 STATUS current 2071 DESCRIPTION 2072 "A collection of objects required for ISDN Basic Rate 2073 physical interface configuration and statistics." 2074 ::= { isdnMibGroups 1 } 2076 isdnMibBearerGroup OBJECT-GROUP 2077 OBJECTS { 2078 isdnBearerChannelType, 2079 isdnBearerOperStatus, 2080 isdnBearerChannelNumber, 2081 isdnBearerPeerAddress, 2082 isdnBearerPeerSubAddress, 2083 isdnBearerCallOrigin, 2084 isdnBearerInfoType, 2085 isdnBearerMultirate, 2086 isdnBearerCallSetupTime, 2087 isdnBearerCallConnectTime, 2088 isdnBearerChargedUnits 2089 } 2090 STATUS current 2091 DESCRIPTION 2092 "A collection of objects required for ISDN Bearer channel 2093 control and statistics." 2094 ::= { isdnMibGroups 2 } 2096 isdnMibSignalingGroup OBJECT-GROUP 2097 OBJECTS { 2098 isdnSignalingGetIndex, 2099 isdnSignalingIfIndex, 2100 isdnSignalingProtocol, 2101 isdnSignalingCallingAddress, 2102 isdnSignalingSubAddress, 2103 isdnSignalingBchannelCount, 2104 isdnSignalingInfoTrapEnable, 2105 isdnSignalingStatus, 2106 isdnSigStatsInCalls, 2107 isdnSigStatsInConnected, 2108 isdnSigStatsOutCalls, 2109 isdnSigStatsOutConnected, 2110 isdnSigStatsChargedUnits, 2111 isdnLapdPrimaryChannel, 2112 isdnLapdOperStatus, 2113 isdnLapdPeerSabme, 2114 isdnLapdRecvdFrmr 2115 } 2116 STATUS current 2117 DESCRIPTION 2118 "A collection of objects required for ISDN D channel 2119 configuration and statistics." 2120 ::= { isdnMibGroups 3 } 2122 isdnMibEndpointGroup OBJECT-GROUP 2123 OBJECTS { 2124 isdnEndpointGetIndex, 2125 isdnEndpointIfIndex, 2126 isdnEndpointIfType, 2127 isdnEndpointTeiType, 2128 isdnEndpointTeiValue, 2129 isdnEndpointSpid, 2130 isdnEndpointStatus 2131 } 2132 STATUS current 2133 DESCRIPTION 2134 "A collection of objects describing Terminal Endpoints." 2135 ::= { isdnMibGroups 4 } 2137 isdnMibDirectoryGroup OBJECT-GROUP 2138 OBJECTS { 2139 isdnDirectoryNumber, 2140 isdnDirectorySigIndex, 2141 isdnDirectoryStatus 2142 } 2143 STATUS current 2144 DESCRIPTION 2145 "A collection of objects describing directory numbers." 2146 ::= { isdnMibGroups 5 } 2148 END 2149 5. Acknowledgments 2151 This document was produced by the ISDN MIB Working Group. Special 2152 thanks is due to the following persons: 2154 Ed Alcoff 2155 Fred Baker 2156 Scott Bradner 2157 Bibek A. Das 2158 Maria Greene 2159 Ken Grigg 2160 Stefan Hochuli 2161 Jeffrey T. Johnson 2162 Glenn Kime 2163 Oliver Korfmacher 2164 Kedar Madineni 2165 Bill Miskovetz 2166 Mike O'Dowd 2167 David M. Piscitello 2168 Lisa A. Phifer 2169 Randy Roberts 2170 Hascall H. Sharp 2171 John Shriver 2172 Robert Snyder 2173 Ron Stoughton 2174 James Watt 2176 6. References 2178 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2179 S. Waldbusser, "Structure of Management Information for Version 2 2180 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2181 January 1996. 2183 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2184 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2185 RFC 1213, Hughes LAN Systems, Performance Systems International, 2186 March 1991. 2188 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A Simple 2189 Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP 2190 Research, Performance Systems International, MIT Lab for Computer 2191 Science, May 1990. 2193 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and 2194 S. Waldbusser, "Protocol Operations for Version 2 of the Simple 2195 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 2197 [5] ITU-T Recommendation "Digital subscriber Signaling System No. 1 2198 (DSS 1) - ISDN User-Network Interface Data Link Layer - General 2199 Aspects Rec. Q.920. 2201 [6] ITU-T Recommendation "Digital subscriber Signaling System No. 1 2202 (DSS 1) - ISDN User-Network Interface - Data Link Layer 2203 Specification Rec. Q.921. 2205 [7] ITU-T Recommendation "Digital subscriber Signaling System No. 1 2206 (DSS 1) - ISDN Data Link Layer Specification for Frame Mode Bearer 2207 Services (LAPF) Rec. Q.922. 2209 [8] ITU-T Recommendation "Digital subscriber Signaling System No. 1 2210 (DSS 1) - ISDN user-network interface layer 3 specification for 2211 basic call control", Rec. Q.931(I.451), March 1993. 2213 [9] ITU-T Recommendation "Generic procedures for the control of ISDN 2214 supplementary services ISDN user-network interface layer 3 2215 specification", Rec. Q.932(I.452). 2217 [10] ITU-T Recommendation "Digital subscriber Signaling System No. 1 2218 (DSS 1) - Signaling specification for frame-mode basic call 2219 control", Rec. Q.933. 2221 [11] McCloghrie, K. and F. Kastenholz, "Evolution of the Interfaces 2222 Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, 2223 January 1994. 2225 [12] D. Fowler, "Definitions of Managed Objects for the DS1/E1/DS2/E2 2226 Interface Types", RFCxxxx, Newbridge Networks, February 1996. 2228 [13] D. Fowler, "Definitions of Managed Objects for the DS0 and 2229 DS0Bundle Interface Types", RFCxxxx, Newbridge Networks, February 2230 1996. 2232 [14] ITU-T Recommendation "Integrated Services Digital Network (ISDN) 2233 General Structure and Service Capabilities - Closed User Group", 2234 Rec. I.255.1. 2236 [15] G. Roeck, "Dial Control Management Information Base", RFCxxxx, 2237 cisco Systems, June 1996. 2239 7. Security Considerations 2241 Security issues are not discussed in this memo. 2243 8. Author's Address 2245 Guenter Roeck 2246 cisco Systems 2247 170 West Tasman Drive 2248 San Jose, CA 95134 2249 U.S.A. 2251 Phone: +1 408 527 3143 2252 Email: groeck@cisco.com