As per Relevance of the word terminal, we have this rfc below:
Network Working Group G. Roeck,
Request for Comments: 2127 cisco
Category: Standards Track March 1997
ISDN Management Information Base using SMIv
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it defines a minimal set of managed objects for SNMP
based management of ISDN terminal interfaces. ISDN interfaces
supported on a variety of equipment (for data and voice)
terminal adapters, bridges, hosts, and routers
This document specifies a MIB module in a manner that is compliant
the SNMPv2 SMI. The set of objects is consistent with the
framework and existing SNMP standards
This document is a product of the ISDN MIB working group within
Internet Engineering Task Force. Comments are solicited and
be addressed to the working group's mailing list at isdn
mib@cisco.com and/or the author
The current version of this document reflects changes made during
last call period and the IESG review
Table of
1 The SNMPv2 Network Management Framework ...................... 2
2 Object Definitions ........................................... 2
3 Overview ..................................................... 3
3.1 Structure of the MIB ....................................... 3
3.1.1 General Description ...................................... 3
3.2 Relationship to the Interfaces MIB ......................... 4
3.2.1 Layering Model ........................................... 4
3.2.2 ifTestTable .............................................. 8
3.2.3 ifRcvAddressTable ........................................ 8
3.2.4 ifEntry .................................................. 8
Roeck Standards Track [Page 1]
RFC 2127 ISDN MIB March 1997
3.2.4.1 ifEntry for a Basic Rate hardware interface ............ 8
3.2.4.2 ifEntry for a B channel ................................ 9
3.2.4.3 ifEntry for LAPD (D channel Data Link Layer) ........... 10
3.2.4.4 ifEntry for a signaling channel ........................ 12
3.3 Relationship to other MIBs ................................. 14
3.3.1 Relationship to the DS1/E1 MIB ........................... 14
3.3.2 Relationship to the DS0 and DS0Bundle MIBs ............... 14
3.3.3 Relationship to the Dial Control MIB ..................... 14
3.4 ISDN interface specific information and implementation
........................................................... 14
3.4.1 ISDN leased lines ........................................ 14
3.4.2 Hyperchannels ............................................ 15
3.4.3 D channel backup and NFAS trunks ......................... 16
3.4.4 X.25 based packet-mode service in B and D channels ....... 16
3.4.5 SPID handling ............................................ 17
3.4.6 Closed User Groups ....................................... 17
3.4.7 Provision of point-to-point line topology ................ 18
3.4.8 Speech and audio bearer capability information elements .. 18
3.4.9 Attaching incoming calls to router ports ................. 19
3.4.10 Usage of isdnMibDirectoryGroup and isdnDirectoryTable ... 20
4 Definitions .................................................. 21
5 Acknowledgments .............................................. 47
6 References ................................................... 47
7 Security Considerations ...................................... 49
8 Author's Address ............................................. 49
1. The SNMPv2 Network Management
The SNMPv2 Network Management Framework presently consists of
major components. They are
o the SMI, described in RFC 1902 [1] - the mechanisms used
describing and naming objects for the purpose of management
o the MIB-II, STD 17, RFC 1213 [2] - the core set of
objects for the Internet suite of protocols
o the protocol, STD 15, RFC 1157 [3] and/or RFC 1905 [4], -
the protocol for accessing managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
2. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
Roeck Standards Track [Page 2]
RFC 2127 ISDN MIB March 1997
defined in the SMI. In particular, each object type is named by
OBJECT IDENTIFIER, an administratively assigned name. The
type together with an object instance serves to uniquely identify
specific instantiation of the object. For human convenience,
often use a textual string, termed the descriptor, to refer to
object type
3.
3.1. Structure of the
For managing ISDN interfaces, the following information is necessary
o Information for managing physical interfaces. In case of
primary rate, this are usually T1 or E1 lines, being managed
the DS1/E1 MIB [12]. For Basic Rate lines, physical
are managed by this MIB
o Information for managing B channels
o Information for managing signaling channels
o Optionally, information for managing Terminal Endpoints (TE).
A Terminal Endpoint is a link layer connection to a switch
o Optionally, information for managing a list of directory numbers
In order to manage connections over ISDN lines, the management
peer information and call history information is required as well
This information is defined in the Dial Control MIB [15].
The purpose for splitting the required information in two MIBs is
be able to use parts of this information for non-ISDN interfaces
well. In particular, the Dial Control MIB might also be used
other types of interfaces, e.g. modems or X.25 virtual connections
Within this document, information has been structured into
groups, which are described in the following chapters
3.1.1. General
This MIB controls all aspects of ISDN interfaces. It consists
five groups
o The isdnMibBasicRateGroup is used to provide
regarding physical Basic Rate interfaces
o The isdnMibBearerGroup is used to control B (bearer) channels
Roeck Standards Track [Page 3]
RFC 2127 ISDN MIB March 1997
It supports configuration parameters as well as
information related to B channels
o The isdnMibSignalingGroup is used to control D (delta) channels
There are three tables in this group. The isdnSignalingTable
isdnSignalingStatsTable support ISDN Network Layer
and statistics. The isdnLapdTable supports ISDN Data Link
(LAPD) configuration and statistics
o The optional isdnMibEndpointGroup can be used to
Terminal Endpoints. It is required only if there are non-
endpoints defined for a given D channel, or if
information like Terminal Endpoint Identifier (TEI) values
Service Profile IDentifiers (SPID) is required to identify
given ISDN user
o The optional isdnMibDirectoryGroup can be used to specify
list of directory numbers for each signaling channel. It
required only if the directory numbers to be accepted
from the isdnSignalingCallingAddress as specified in
isdnSignalingTable
3.2. Relationship to the Interfaces
This section clarifies the relationship of this MIB to the
MIB [11]. Several areas of correlation are addressed in
following subsections. The implementor is referred to the
MIB document in order to understand the general intent of
areas
3.2.1. Layering
An ISDN interface usually consists of a D channel and a number of
channels, all of which are layered on top of a physical interface
Furthermore, there are multiple interface layers for each D channel
There are Data Link Layer (LAPD) as well as Network Layer entities
This is accomplished in this MIB by creating a logical
(ifEntry) for each of the D channel entities and a logical
(ifEntry) for each of the B channels. These are then correlated
each other and to the physical interface using the ifStack table
the Interfaces MIB [11].
Roeck Standards Track [Page 4]
RFC 2127 ISDN MIB March 1997
The basic model, therefore, looks something like this
| |
+--+ +--+
| D ch. |
|Layer 3|
+--+ +--+
| | | | | | <== interface to
+--+ +--+ +--+ +--+ +--+ +--+ layers, to be
| D ch. | | B | | B | by ifStack
|Layer 2| |channel| .... |channel
+--+ +--+ +--+ +--+ +--+ +--+
| | | | | | <== attachment to
+--+ +--------+ +------------+ +----+ interfaces, to be
| physical interface | by ifStack
| (S/T, U or T1/E1) |
+-----------------------------------+
Mapping of B/D channels to physical
Each D channel can support multiple Terminal Endpoints.
Endpoints can either be one or multiple ISDN signaling channels,
channels supporting X.25 based packet mode services
To accomplish this, there can be multiple Network Layer entities
top of each ISDN Data Link Layer (LAPD) interface. The
model therefore looks something like this, including interface
as examples
+------+ +----+ +----+
|x25ple| |isdn| |isdn| Terminal Endpoints (X.25 or ISDN
+--+---+ +-+--+ +-+--+
| | |
| +------+ | | | <== Interface to upper layers
| | +------------+ | | to be provided by
| | | | |
++-+-++ +-+-+ +-+-+
|lapd | D channel |ds0| |ds0| B
+--+--+ Data Link Layer +-+-+ +-+-+
| | |
+--+----------------------+------+--------------------+
| ds1 or isdns/isdnu |
+-----------------------------------------------------+
Detailed interface
IfEntries are maintained for each D channel Network Layer
(Terminal Endpoint), for LAPD and for each B channel
Roeck Standards Track [Page 5]
RFC 2127 ISDN MIB March 1997
The ifType for a Terminal Endpoint can be isdn(63) for ISDN
channels or x25ple(40) for X.25 based packet mode services.
ifType for D channel Data Link Layer (LAPD) interfaces is lapd(77).
The ifType for B channels is ds0(81). The ifType for
interfaces is the matching IANA ifType, usually ds1(18) for
Rate interfaces or isdns(75)/isdnu(76) for Basic Rate interfaces
The ifStackTable is used to map B channels and LAPD interfaces
physical interfaces and to map D channel Network Layer
(Terminal Endpoints) to LAPD
In the example given above, the assignment of index values could
example be as follows
ifIndex ifType ISDN MIB tables
indexed by
1 isdns(75) isdnBasicRateTable Basic Rate physical
2 lapd(77) isdnLapdTable LAPD
3 x25ple(40) isdnEndpointTable X.25 Packet
4 isdn(63) isdnSignalingTable ISDN signaling channel #1
5 isdn(63) isdnSignalingTable ISDN signaling channel #2
6 ds0(81) isdnBearerTable B channel #1
7 ds0(81) isdnBearerTable B channel #2
8 ppp(23) peer entry #1 (see below
9 ppp(23) peer entry #2 (see below
Roeck Standards Track [Page 6]
RFC 2127 ISDN MIB March 1997
The corresponding ifStack table entries would then be
ifStackTable
HigherLayer
0 3
0 4
0 5
0 8
0 9
1 0
2 1
3 2
4 2
5 2
6 1
7 1
8 6
9 7
Mapping of B channels to upper interface layers is usually done
the Dial Control MIB. For example, mapping on top of B channels
look as follows
+-------------------------------------------------------+
| Network Layer Protocol |
+------+ +-------+ +-------+ +-------+ +-------+ +------+
| | | | | | | | | | <== appears
+-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
| PPP | | PPP | | F/R | | PPP | | F/R |
| for | | for | | for | | for | | for | ifEntry
|Peer1| |Peer2| |switch |Peer3| |switch shadow
| | | | | A | | | | B |
+-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
| | | | <== some actually
+--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+
| B | | B | | B | | B | | B |
|channel| |channel| |channel| |channel| |channel
+--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+
| | | | | | | | | |
+------+ +-------+ +-------+ +-------+ +-------+ +------+
| Basic/Primary Rate Interface |
+-------------------------------------------------------+
Mapping of IP interfaces to Called Peers to B
Roeck Standards Track [Page 7]
RFC 2127 ISDN MIB March 1997
In this model, ifEntries are maintained for each peer. Each peer
required to have an associated ifEntry. This interface can be of
kind, e.g. PPP or LAPB
The Dial Control MIB can be used for all types of demand-
interfaces, e.g., ISDN, modems or X.25 virtual connections
3.2.2.
The ifTestTable is not supported by this MIB
3.2.3.
The ifRcvAddressTable is not supported by this MIB
3.2.4.
3.2.4.1. ifEntry for a Basic Rate hardware
The ifGeneralGroup is supported for Basic Rate hardware interfaces
ifTable
============== ===========================================
ifIndex Each ISDN Basic Rate hardware interface
represented by an ifEntry
ifDescr Textual port description
ifType The IANA value of isdns(75) or isdnu(76),
whichever is appropriate
ifSpeed The overall bandwidth of this interface
ifPhysAddress Return an empty string
ifAdminStatus The administrative status of the ISDN interface
ifOperStatus The current operational status of this interface
The operational status is dormant(5)
the interface is in standby mode, i.e.
to the network, but without call activity
The operational status is down(2) if the
has detected that there is no layer 1
to the switch
For other values, refer to the Interfaces MIB
ifLastChange Refer to the Interfaces MIB
Roeck Standards Track [Page 8]
RFC 2127 ISDN MIB March 1997
Refer to the Interfaces MIB
Refer to the Interfaces MIB
ifHighSpeed Return zero
ifName Refer to the Interfaces MIB
3.2.4.2. ifEntry for a B
The ifEntry for a B channel supports the ifGeneralGroup of
Interfaces MIB
ifTable
============== ===========================================
ifIndex Each ISDN B channel is represented by an ifEntry
ifDescr Textual port description
ifType The IANA value of ds0(81).
ifSpeed The bandwidth of this B channel
Usually, this is the value of 56000 or 64000.
ifPhysAddress Return an empty string
ifAdminStatus The administrative status of this interface
ifOperStatus The current operational status of this interface
Note that dormant(5) is explicitly being
as defined in the Interfaces MIB
For other values, refer to the Interfaces MIB
ifLastChange Refer to the Interfaces MIB
Refer to the Interfaces MIB
Refer to the Interfaces MIB
ifHighSpeed Return zero
ifName Refer to the Interfaces MIB
Roeck Standards Track [Page 9]
RFC 2127 ISDN MIB March 1997
3.2.4.3. ifEntry for LAPD (D channel Data Link Layer
The ifEntry for LAPD (D channel Data Link Layer) supports
ifGeneralGroup and the ifPacketGroup of the Interfaces MIB
ifTable
============== ===========================================
ifIndex Each ISDN D channel Data Link layer is
by an ifEntry
ifDescr Textual port description
ifType The IANA value of lapd(77).
ifSpeed The bandwidth of this interface. Usually, this
the value of 16000 for basic rate interfaces
64000 for primary rate interfaces
ifPhysAddress Return an empty string
ifAdminStatus The administrative status of this interface
ifOperStatus The current operational status of the
LAPD interface. The operational status
dormant(5) if the interface is in standby
(see Q.931 [8], Annex F, D channel
procedures).
For other values, refer to the Interfaces MIB
ifLastChange Refer to the Interfaces MIB
Refer to the Interfaces MIB
Refer to the Interfaces MIB
ifHighSpeed Return zero
ifName Refer to the Interfaces MIB
ifMtu The size of the largest frame which can
sent/received on this interface
specified in octets. Usually, this is
default value of 260 as specified in Q.921
[6], chapter 5.9.3.
Roeck Standards Track [Page 10]
RFC 2127 ISDN MIB March 1997
ifInOctets The total number of octets received on
interface
ifInUcastPkts The number of frames received on this
whose address is not TEI=127.
ifInNUcastPkts Deprecated. Return the number of
received on this interface with TEI=127.
ifInMulticastPkts Return zero
ifInBroadcastPkts Return the number of frames
on this interface with TEI=127.
ifInDiscards The total number of received frames which
been discarded
The possible reasons are: buffer shortage
ifInErrors The number of inbound frames that
errors preventing them from being
to LAPD
ifInUnknownProtos The number of frames with known TEI, but
SAPI (Service Access Point Identifier
see Q.921 [6], chapter 3.3.3).
ifOutOctets The total number of octets transmitted on
interface
ifOutUcastPkts The number of frames transmitted on
interface whose address is not TEI=127.
ifOutNUcastPkts Deprecated. Return the number of
transmitted on this interface with TEI=127.
Return zero
Return the number of frames
on this interface with TEI=127.
ifOutDiscards The total number of outbound frames
were discarded. Possible reasons are
buffer shortage
ifOutErrors The number of frames which could not
transmitted due to errors
Roeck Standards Track [Page 11]
RFC 2127 ISDN MIB March 1997
ifOutQlen Deprecated. Return zero
ifSpecific Deprecated. Return {0 0}.
3.2.4.4. ifEntry for a signaling
The ifEntry for a signaling channel supports the ifGeneralGroup
the ifPacketGroup of the Interfaces MIB
ifTable
============== ===========================================
ifIndex Each ISDN signaling channel is represented
an ifEntry
ifDescr Textual port description
ifType The IANA value of isdn(63).
ifSpeed The bandwidth of this signaling channel. Usually
this is the same value as for LAPD, i.e. 16000
for basic rate interfaces or 64000 for primary
interfaces
ifPhysAddress The ISDN address assigned to this signaling channel
This is a copy of isdnSignalingCallingAddress
ifAdminStatus The administrative status of the signaling channel
ifOperStatus The current operational status of this
channel. The operational status is dormant(5)
the signaling channel is currently not activated
For other values, refer to the Interfaces MIB
ifLastChange Refer to the Interfaces MIB
Refer to the Interfaces MIB
Refer to the Interfaces MIB
ifHighSpeed Return zero
ifName Refer to the Interfaces MIB
Roeck Standards Track [Page 12]
RFC 2127 ISDN MIB March 1997
ifMtu The size of the largest frame which can
sent/received on this signaling channel
specified in octets. Usually, this is
default value of 260 as specified in Q.921
[6], chapter 5.9.3.
ifInOctets The total number of octets received on
signaling channel
ifInUcastPkts The number of frames received which are
to this channel
ifInNUcastPkts Deprecated. Return the number of
received on this signaling channel with TEI=127.
ifInMulticastPkts Return zero
ifInBroadcastPkts Return the number of frames
on this signaling channel with TEI=127.
ifInDiscards The total number of received frames which have
discarded
The possible reasons are: buffer shortage
ifInErrors The number of inbound frames that
errors preventing them from being
to the signaling channel
ifInUnknownProtos Return zero
ifOutOctets The total number of octets transmitted on
signaling channel
ifOutUcastPkts The number of frames transmitted on
signaling channel whose address is not TEI=127.
ifOutNUcastPkts Deprecated. Return the number of
transmitted on this signaling channel with TEI=127.
Return zero
Return the number of frames
on this signaling channel with TEI=127.
Roeck Standards Track [Page 13]
RFC 2127 ISDN MIB March 1997
ifOutDiscards The total number of outbound frames
were discarded. Possible reasons are
buffer shortage
ifOutErrors The number of frames which could not
transmitted due to errors
ifOutQlen Deprecated. Return zero
ifSpecific Deprecated. Return {0 0}.
3.3. Relationship to other
3.3.1. Relationship to the DS1/E1
Implementation of the DS1/E1 MIB [12] is not required for
this MIB. It is however recommended to implement the DS1/E1 MIB
entities supporting Primary Rate interfaces
3.3.2. Relationship to the DS0 and DS0Bundle
Implementation of the DS0 MIB [13] is optional
Implementation of the DS0Bundle MIB [13] may be required only
hyperchannels are to be supported, depending on the
scheme used in a given implementation. See chapter 3.4.2 for
on how to implement hyperchannels
3.3.3. Relationship to the Dial Control
Implementation of the Dial Control MIB [15] is required
3.4. ISDN interface specific information and implementation
3.4.1. ISDN leased
ISDN leased lines can be specified on a per-B-channel basis. To
so, the value of isdnBearerChannelType has to be set to leased(2).
There is no signaling protocol support for leased line B channels
since there is no signaling protocol action for these kinds
interfaces
Roeck Standards Track [Page 14]
RFC 2127 ISDN MIB March 1997
If there is no signaling support available for an ISDN interface
this must be specified in the appropriate interface specific table
For Basic Rate interfaces, isdnBasicRateSignalMode
isdnBasicRateTable must be set to inactive(2). For Primary
interfaces, dsx1SignalMode of dsx1ConfigTable in DS1/E1 MIB [12]
be set to none(1). There are no isdnLapdTable or
entries for such interfaces
Depending on the leased line type and the service provider, the
channel can be used for data transfer. If this is the case the
channel interface type is ds0(81) instead of lapd(77) and its
is identical to B channel usage if there is no signaling
available
For a Primary Rate interface which is entirely used as a leased line
there is no ISDN specific information available or required.
leased lines can entirely be handled by the DS1/E1 MIB
3.4.2.
The active switch protocol defines if hyperchannels are supported
and the actual support is implementation dependent.
connections will be requested by the interface user at call
time, e.g. by the peer connection handling procedures
In the ISDN MIB, the isdnBearerMultirate object of
can be used to check if hyperchannels are being used for an
call
If hyperchannels are being used, multiplexing between
encapsulation layer and the B channels is required, since there
one encapsulation layer interface connected to several B
interfaces. This can be accomplished in two ways
o The DS0Bundle MIB [13] can be used to provide the multiplexing
See the DS0Bundle MIB document for details
o The ifStackTable can be used to provide the multiplexing.
this case, there are several ifStackTable entries with the
value of HigherLayer, and different values of LowerLayer
It is up to the implementor to decide which multiplexing scheme
use
Each hyperchannel call is treated as one call in
isdnSignalingStatsTable, independent of the number of B
involved
Roeck Standards Track [Page 15]
RFC 2127 ISDN MIB March 1997
For a hyperchannel call, all objects in the isdnBearerTable
related to this call (i.e., all isdnBearerTable entries associated
B channels used by the hyperchannel) have identical values.
related objects in the isdnBearerTable are
3.4.3. D channel backup and NFAS
D channel backup is defined in Q.931 [8], Annex F. It describes Non
Associated signaling and its use and functionality is
identical to Non Facility Associated Signaling (NFAS) trunks
Non Facility Accociated Signaling (NFAS) basically means that a
channel on a PRI interface is used to manage calls on other
trunks. This is required in North America for H11 channels,
all 24 time slots are being used for B channels
According to Q.931, Annex F, the D channel backup feature can
provided on a subscription basis and is network dependent. The
channel backup procedure is described in detail in Q.931.
For D channel backup, the controlling isdnSignalingTable entry
layered on top of all attached LAPD interfaces. This layering
done using the ifStack table. There is only one active
interface, however. Inactive LAPD interfaces have an ifOperStatus
dormant(5).
NFAS trunks are also handled using the ifStack table. In this case,
signaling channel is layered on top of a LAPD interface as well as
top of all physical interfaces which are controlled by the
channel, but do not supply a D channel
3.4.4. X.25 based packet-mode service in B and D
X.25 based packet mode service over B channels can be handled
the Dial Control MIB by creating an appropriate peer entry. The
entry ifType can then be x25(5), thus providing access to X.25
service
Roeck Standards Track [Page 16]
RFC 2127 ISDN MIB March 1997
X.25 based packet mode service over D channels can be handled
creating an ifEndpointTable entry with an isdnEndpointIfType
x25ple(40). The upper protocol layers can then be attached to
interface using the ifStack table
3.4.5. SPID
Service Profile IDentifiers (SPIDs) are defined for BRI
only, and being used in North America. SPIDs are required for DMS
100, NI-1 and NI-2, and are optional for 5ESS. A switch can
up to 8 SPIDs per BRI
Each Terminal Endpoint has a SPID assigned. It is normally
from the party number (calling address for outgoing calls) with
number of digits prepended and appended. Since each network
to be different, both the calling address and the SPID have to
stored
The SPID identifies the particular services that have
provisioned for a terminal. If there are two B channels on a BRI
there can be two SPIDs, one for each of the two B channels.
can also be a single SPID, providing access to both B channels
The SPID gets registered with the switch after link establishment
There is one data link for each SPID. As part of
registration, an EID (Endpoint IDentifier) is defined by the switch
On incoming calls, the switch may provide the EID, a called
number, or both, depending on the ISDN code implemented in
switch
The EID has two bytes: USID (User Service IDentifier) and
(Terminal IDentifier). These are later used by some of the
versions running on the switch side (e.g. compliant with NI-1, 5
custom) to broadcast SETUP messages with these included, so
correct endpoint would accept the call. Other switch
versions identify the endpoint with the Called Party Number
In the ISDN MIB, the SPID can be entered using the
object of isdnEndpointTable. The isdnSignalingCallingAddress
already being used to specify the calling number, cannot be used
record the SPID since the values of the SPID and the Calling
may differ and both may be required to be present
3.4.6. Closed User
Closed User Groups (CUG), as defined in I.255.1 [14], are
for circuit mode calls by ETSI (ETS 300 138) and 1TR6. In
networks, an ISDN address can have one or more Closed User
Roeck Standards Track [Page 17]
RFC 2127 ISDN MIB March 1997
assigned. If there is more than one Closed User Group assigned to
given address, one of those is the preferred Closed User Group.
such addresses, only calls from assigned Closed User Groups
accepted by the network
Thus, Closed User Groups are a parameter for peer entries and
defined in the Dial Control MIB. A peer entry attached to a
User Group has to point to an ISDN interface which is attached to
Closed User Group in question
3.4.7. Provision of point-to-point line
In the ISDN standards, there are two different meanings for the
"point-to-point".
In ISDN standards, the term point-to-point are usually used for
link connections, i.e. layer 2 connections, where each layer 2
connection from the TE to the network is a single point-to-
connection. Multiple connections of this kind may exist on
physical (layer 1) connection, however, and in case of Basic
interfaces there may be several TE's connected to one physical
to the network
The second meaning of "point-to-point" refers to the line topology
i.e. to layer 1 connections. For Primary Rate interfaces, the
topology is always point-to-point. For Basic Rate interfaces,
1 point-to- point connections do exist in several countries,
being used for connecting PBX systems to the network
The second meaning (layer 1 connections) is what will be referred
as "point-to-point" connection throughout this document
For Basic Rate interfaces, the isdnBasicRateTable
isdnBasicRateLineTopology can be used to select the line topology
3.4.8. Speech and audio bearer capability information
The objects speech(2), audio31(6) and audio7(7), as being used
isdnBearerInfoType, refer to the Speech, 3.1 kHz Audio and old 7
Audio (now Multi-use) bearer capabilities for ISDN, as defined
Q.931 [8], chapter 4.5.5, octet 3 of bearer capability
element
These capabilities are signaling artifices that allow networks to
certain things with the call. It is up to the network to decide
to do
Roeck Standards Track [Page 18]
RFC 2127 ISDN MIB March 1997
The Speech Bearer Capability means that speech is being carried
the channel, as in two people talking. This would be POTS-
speech. The network may compress this, encrypt it or whatever
wants with it as long as it delivers POTS quality speech to the
end. In other words, a modem is not guaranteed to work over
connection
The 3.1 kHz Audio capability indicates that the network carries
3.1 kHz bandwidth across the network. This would (theoretically
allow modem signals to be carried across the network. In the US,
network automatically enters a capability of 3.1 kHz Audio on
coming into the ISDN from a POTS network. This capability
the network from interfering with the data channel in a way
would corrupt the 3.1 kHz VoiceBand data
7 kHz Audio was meant to signal the use of a higher quality
connection (e.g., music from radio). It was changed to Multi-
capability to allow it to be used for video-conferencing with
back to audio
In some cases, the Speech or 3.1 kHz Bearer Capability provides a 56
kbit/s data path through the network. Therefore, some people
setting up calls with the Speech or 3.1 kHz BC and transmitting 56
kbit/s data over the connection. This is usually to take
of favorable tariffs for Speech as opposed to Data
On the incoming side, the equipment is usually configured to
the Bearer Capability and either answer all Speech calls as 56 kbit/
data or to use one Directory Number for real speech and another
data
3.4.9. Attaching incoming calls to router
In ISDN, there are several ways to identify an incoming call and
attach a router port to this call
o The call can be identified and attached to a router port
the ISDN Calling Address, that is, the peer ISDN address.
the peer address is defined in a Dial Control MIB
entry for this peer, this would be the most natural way
attach an incoming call to a router port
In this configuration, only a single isdnSignalingTable entry
required for each physical ISDN interface. Unfortunately,
ISDN Calling Address is not available in all countries and/
switch protocols. Therefore, other means for attaching
calls to router ports must be provided
Roeck Standards Track [Page 19]
RFC 2127 ISDN MIB March 1997
o The call can also be identified and attached to a router
using the ISDN Called Address. In this case, a distinct
address or subaddress must be specified for each of the
ports. This can be accomplished in the ISDN MIB by creating
isdnSignalingTable entry for each of the router ports, and
connecting Dial Control MIB peer entries to the thereby
interface using the dialCtlPeerCfgLowerIf object
dialCtlPeerCfgTable
If this type of router port identification is used in
implementation, it is up to the implementor to decide if
should be distinct TEI values assigned for each of
isdnSignalingTable entries. For this reason,
isdnEndpointTable permits specifying the same TEI value
multiple entries. It is recommended to use dynamic
assignment whenever possible
The implementor should be aware that this type of
requires a lot of configuration work for the customer, since
entry in isdnSignalingTable must be created for each of
router ports
o Incoming calls can also be identified and attached to
ports using a higher layer functionality, such as
authentication. Defining this functionality is outside
scope of this document
3.4.10. Usage of isdnMibDirectoryGroup and
In some switch protocol or PBX implementations, the Called
Information Element on incoming calls can differ from the
Number on outgoing calls. Sometimes, the Called Number can
different for incoming Local Calls, Long Distance Calls
International Calls. For Hunt Groups, the Called Number can be
of the numbers in the Hunt Group
The isdnDirectoryTable can be used to specify all these numbers
Entries in the isdnDirectoryTable are always connected to
isdnSignalingTable entries. No ifEntry is created
isdnDirectoryTable entries. Therefore, the isdnDirectoryTable
not be used to attach incoming calls to router ports. For
port identification, isdnSignalingTable entries should be
instead
Roeck Standards Track [Page 20]
RFC 2127 ISDN MIB March 1997
4.
ISDN-MIB DEFINITIONS ::=
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Counter32,
Gauge32,
Integer32
FROM SNMPv2-
DisplayString
TruthValue
TimeStamp
RowStatus
TestAndIncr
TEXTUAL-
FROM SNMPv2-
MODULE-COMPLIANCE
OBJECT-GROUP
NOTIFICATION-
FROM SNMPv2-
ifIndex
FROM IF-
FROM IANAifType-
FROM RFC1213-MIB
isdnMib MODULE-
LAST-UPDATED "9609231642Z" -- Sep 23, 1996
ORGANIZATION "IETF ISDN MIB Working Group
CONTACT-
" Guenter
Postal: cisco
170 West Tasman
San Jose, CA 95134
U.S.A
Phone: +1 408 527 3143
E-mail: groeck@cisco.com
"The MIB module to describe
management of ISDN interfaces."
::= { transmission 20 }
-- The ISDN hardware interface (BRI or PRI) is
Roeck Standards Track [Page 21]
RFC 2127 ISDN MIB March 1997
-- by a media specific ifEntry
--
-- For basic rate lines, the media specifics for the physical
-- is defined in the physical interface group of the ISDN MIB
-- The ifType for physical basic rate interfaces is isdns(75)
-- or isdnu(76), whichever is appropriate
--
-- For primary rate, the media specifics are defined in the
-- MIB and the ifType has a value of ds1(18).
-- Each signaling channel is represented by an
-- in the isdnSignalingTable
-- The signaling channel has an ifType value of isdn(63).
-- Each B channel is also represented as an
-- in the ifTable. The B channels have an ifType
-- of ds0(81).
-- This model is used while defining objects and
-- for management
-- The ISDN MIB allows sub-layers. For example, the data
-- over a B channel may take place with PPP encapsulation. While
-- ISDN MIB describes the D and B channels, a media specific
-- for PPP can be used on a layered basis. This is as
-- the interfaces MIB
-- Textual
IsdnSignalingProtocol ::= TEXTUAL-
STATUS
"This data type is used as the syntax of
isdnSignalingProtocol object in
definition of ISDN-MIB's isdnSignalingTable
The definition of this textual convention with
addition of newly assigned values is
periodically by the IANA, in either the
Numbers RFC, or some derivative of it specific
Internet Network Management number assignments. (
latest arrangements can be obtained by contacting
IANA.)
Requests for new values should be made to IANA
email (iana@iana.org)."
SYNTAX INTEGER {
other(1), -- none of the
dss1(2), -- ITU DSS1 (formerly CCITT) Q.931
etsi(3), -- Europe / ETSI ETS300-102
-- plus supplementary
Roeck Standards Track [Page 22]
RFC 2127 ISDN MIB March 1997
-- (ETSI 300-xxx
-- note that NET3, NET5
-- test procedures for ETS300-102
-- and have been replaced
-- I-CTR 3 and I-CTR 4.
dass2(4), -- U.K. / DASS2 (PRI
ess4(5), -- U.S.A. / AT&T 4
ess5(6), -- U.S.A. / AT&T 5
dms100(7), -- U.S.A. / Northern Telecom DMS100
dms250(8), -- U.S.A. / Northern Telecom DMS250
ni1(9), -- U.S.A. / National ISDN 1 (BRI
ni2(10), -- U.S.A. / National ISDN 2 (BRI, PRI
ni3(11), -- U.S.A. / next
vn2(12), -- France / VN
vn3(13), -- France / VN
vn4(14), -- France / VN4 (ETSI with changes
vn6(15), -- France / VN6 (ETSI with changes
-- delta document CSE P 10-21
-- test document CSE P 10-20
kdd(16), -- Japan /
ins64(17), -- Japan / NTT INS64
ins1500(18), -- Japan / NTT INS1500
itr6(19), -- Germany/ 1TR6 (BRI, PRI
cornet(20), -- Germany/ Siemens HiCom
ts013(21), -- Australia / TS013
-- (formerly TPH 1962, BRI
ts014(22), -- Australia / TS014
-- (formerly TPH 1856, PRI
qsig(23), -- Q.
swissnet2(24), -- SwissNet-2
swissnet3(25) -- SwissNet-3
}
-- Isdn Mib objects
isdnMibObjects OBJECT IDENTIFIER ::= { isdnMib 1 }
-- ISDN physical interface
-- This group describes physical basic rate interfaces
isdnBasicRateGroup OBJECT IDENTIFIER ::= { isdnMibObjects 1 }
isdnBasicRateTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
Roeck Standards Track [Page 23]
RFC 2127 ISDN MIB March 1997
"Table containing configuration and
parameters for all physical Basic
interfaces on this managed device."
::= { isdnBasicRateGroup 1 }
isdnBasicRateEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the ISDN Basic Rate Table."
INDEX { ifIndex }
::= { isdnBasicRateTable 1 }
IsdnBasicRateEntry ::= SEQUENCE {
isdnBasicRateIfType INTEGER
isdnBasicRateLineTopology INTEGER
isdnBasicRateIfMode INTEGER
isdnBasicRateSignalMode
}
isdnBasicRateIfType OBJECT-
SYNTAX INTEGER {
isdns(75),
isdnu(76)
}
MAX-ACCESS read-
STATUS
"The physical interface type. For 'S/T' interfaces
also called 'Four-wire Basic Access Interface',
the value of this object is isdns(75).
For 'U' interfaces, also called 'Two-wire
Access Interface', the value of this object
isdnu(76)."
::= { isdnBasicRateEntry 1 }
isdnBasicRateLineTopology OBJECT-
SYNTAX INTEGER {
pointToPoint(1),
pointToMultipoint(2)
}
MAX-ACCESS read-
STATUS
"The line topology to be used for this interface
Note that setting isdnBasicRateIfType to isdns(75)
does not necessarily mean a line topology
Roeck Standards Track [Page 24]
RFC 2127 ISDN MIB March 1997
point-to-multipoint."
::= { isdnBasicRateEntry 2 }
isdnBasicRateIfMode OBJECT-
SYNTAX INTEGER {
te(1),
nt(2)
}
MAX-ACCESS read-
STATUS
"The physical interface mode. For TE mode, the
of this object is te(1). For NT mode, the
of this object is nt(2)."
::= { isdnBasicRateEntry 3 }
isdnBasicRateSignalMode OBJECT-
SYNTAX INTEGER {
active(1),
inactive(2)
}
MAX-ACCESS read-
STATUS
"The signaling channel operational mode for this interface
If active(1) there is a signaling channel on
interface. If inactive(2) a signaling channel
not available."
::= { isdnBasicRateEntry 4 }
-- The B channel (bearer channel)
-- Note that disconnects can explicitely be handled using
-- ifStack table. If a connection is to be disconnected
-- the according ifStack entry has to be removed
-- More specifically, the ifStackTable entry which binds the high-
-- ifTable entry (and related dialCtlNbrCfgTable entry) to
-- B channel ifTable entry (and related isdnBearerTable entry
-- during an active call has to be removed
isdnBearerGroup OBJECT IDENTIFIER ::= { isdnMibObjects 2 }
isdnBearerTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table defines port specific operational,
Roeck Standards Track [Page 25]
RFC 2127 ISDN MIB March 1997
and active call data for ISDN B channels. Each
in this table describes one B (bearer) channel."
::= { isdnBearerGroup 1 }
isdnBearerEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Operational and statistics information relating
one port. A port is a single B channel."
INDEX { ifIndex }
::= { isdnBearerTable 1 }
IsdnBearerEntry ::=
SEQUENCE {
isdnBearerChannelType INTEGER
isdnBearerOperStatus INTEGER
isdnBearerChannelNumber INTEGER
isdnBearerPeerAddress DisplayString
isdnBearerPeerSubAddress DisplayString
isdnBearerCallOrigin INTEGER
isdnBearerInfoType INTEGER
isdnBearerMultirate TruthValue
isdnBearerCallSetupTime TimeStamp
isdnBearerCallConnectTime TimeStamp
isdnBearerChargedUnits Gauge32
}
isdnBearerChannelType OBJECT-
SYNTAX INTEGER {
dialup(1),
leased(2)
}
MAX-ACCESS read-
STATUS
"The B channel type. If the B channel is
to a dialup line, this object has a value
dialup(1). In this case, it is controlled
an associated signaling channel. If the B
is connected to a leased line, this object
a value of leased(2). For leased line B channels,
is no signaling channel control available."
::= { isdnBearerEntry 1 }
isdnBearerOperStatus OBJECT-
SYNTAX INTEGER {
Roeck Standards Track [Page 26]
RFC 2127 ISDN MIB March 1997
idle(1),
connecting(2),
connected(3),
active(4)
}
MAX-ACCESS read-
STATUS
"The current call control state for this port
idle(1): The B channel is idle
No call or call attempt is going on
connecting(2): A connection attempt (outgoing call
is being made on this interface
connected(3): An incoming call is in the
of validation
active(4): A call is active on this interface."
::= { isdnBearerEntry 2 }
isdnBearerChannelNumber OBJECT-
SYNTAX INTEGER (1..30)
MAX-ACCESS read-
STATUS
"The identifier being used by a signaling
to identify this B channel, also referred to
B channel number. If the Agent also supports the DS0 MIB
the values of isdnBearerChannelNumber and dsx0Ds0
must be identical for a given B channel."
::= { isdnBearerEntry 3 }
isdnBearerPeerAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The ISDN address the current or last call is or
connected to
In some cases, the format of this information can
be predicted, since it largely depends on the
of switch or PBX the device is connected to. Therefore
the detailed format of this information is
specified and is implementation dependent
If possible, the agent should supply this
using the E.164 format. In this case, the number
start with '+'. Otherwise, IA5 number digits must be used
Roeck Standards Track [Page 27]
RFC 2127 ISDN MIB March 1997
If the peer ISDN address is not available
this object has a length of zero."
"ITU-T E.164, Q.931 chapter 4.5.10"
::= { isdnBearerEntry 4 }
isdnBearerPeerSubAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The ISDN subaddress the current or last call is or
connected to
The subaddress is an user supplied string of up to 20
IA5 characters and is transmitted transparently
the network
If the peer subaddress is not available, this
has a length of zero."
"ITU-T I.330, Q.931 chapter 4.5.11"
::= { isdnBearerEntry 5 }
isdnBearerCallOrigin OBJECT-
SYNTAX INTEGER {
unknown(1),
originate(2),
answer(3),
callback(4)
}
MAX-ACCESS read-
STATUS
"The call origin for the current or last call. If
system startup there was no call on this interface
this object has a value of unknown(1)."
::= { isdnBearerEntry 6 }
isdnBearerInfoType OBJECT-
SYNTAX INTEGER {
unknown(1),
speech(2),
unrestrictedDigital(3), -- as defined in Q.931
unrestrictedDigital56(4), -- with 56k rate
restrictedDigital(5),
audio31(6), -- 3.1 kHz
audio7(7), -- 7 kHz
Roeck Standards Track [Page 28]
RFC 2127 ISDN MIB March 1997
video(8),
packetSwitched(9)
}
MAX-ACCESS read-
STATUS
"The Information Transfer Capability for the
or last call
speech(2) refers to a non-data connection,
audio31(6) and audio7(7) refer to data mode connections
Note that Q.931, chapter 4.5.5, originally
audio7(7) as '7 kHz audio' and now defines it
'Unrestricted digital information with tones
announcements'.
If since system startup there has been no call on
interface, this object has a value of unknown(1)."
"Q.931 [8], chapter 4.5.5, octet 3 of bearer
information element, combined with the User
(as defined in octets 5 and 5a to 5d), if rate
is being used."
::= { isdnBearerEntry 7 }
isdnBearerMultirate OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This flag indicates if the current or last call
multirate. The actual information transfer rate
in detail specified in octet 4.1 (rate multiplier),
is the sum of all B channel ifSpeed values
the hyperchannel
If since system startup there was no call on
interface, this object has a value of false(2)."
"Q.931 [8], chapter 4.5.5."
::= { isdnBearerEntry 8 }
isdnBearerCallSetupTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Roeck Standards Track [Page 29]
RFC 2127 ISDN MIB March 1997
"The value of sysUpTime when the ISDN setup message
the current or last call was sent or received. If
system startup there has been no call on this interface
this object has a value of zero."
::= { isdnBearerEntry 9 }
isdnBearerCallConnectTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime when the ISDN connect message
the current or last call was sent or received. If
system startup there has been no call on this interface
this object has a value of zero."
::= { isdnBearerEntry 10 }
isdnBearerChargedUnits OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"The number of charged units for the current or
connection. For incoming calls or if charging
is not supplied by the switch, the value of this
is zero."
::= { isdnBearerEntry 11 }
-- ISDN signaling
isdnSignalingGroup OBJECT IDENTIFIER ::= { isdnMibObjects 3 }
-- signaling channel configuration
-- There is one entry in this table for each Terminal
-- (link layer connection to the switch).
-- Usually, there is one endpoint per D channel. In
-- cases, however, there can be multiple endpoints
-- Thus, entries in this table can be created and deleted
-- This also means the creation of an associated ifEntry
--
-- D channel backup and NFAS trunks are handled using
-- ifStack table
-- In case of D channel backup, there are
-- Data Link Layer (LAPD) interfaces. Only one interface
-- active; all others are dormant(5).
-- In case of NFAS trunks, one lower interface is
-- LAPD interface, while the other lower interfaces are
-- interfaces
Roeck Standards Track [Page 30]
RFC 2127 ISDN MIB March 1997
-- If directory number and calling address differ from each
-- or multiple directory numbers are being used
-- the isdnDirectoryTable has to be used to enter
-- directory numbers
isdnSignalingGetIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The recommended procedure for selecting a new index
isdnSignalingTable row creation is to GET the value
this object, and then to SET the object with the
value. If the SET operation succeeds, the manager can
this value as an index to create a new row in this table."
"RFC1903, TestAndIncr textual convention."
::= { isdnSignalingGroup 1 }
isdnSignalingTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"ISDN signaling table containing configuration
operational parameters for all ISDN
channels on this managed device."
::= { isdnSignalingGroup 2 }
isdnSignalingEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the ISDN Signaling Table. To create a
entry, only isdnSignalingProtocol needs to be
before isdnSignalingStatus can become active(1)."
INDEX { isdnSignalingIndex }
::= { isdnSignalingTable 1 }
IsdnSignalingEntry ::= SEQUENCE {
isdnSignalingIndex INTEGER
isdnSignalingIfIndex InterfaceIndex
isdnSignalingProtocol IsdnSignalingProtocol
isdnSignalingCallingAddress DisplayString
isdnSignalingSubAddress DisplayString
isdnSignalingBchannelCount Integer32,
isdnSignalingInfoTrapEnable INTEGER
Roeck Standards Track [Page 31]
RFC 2127 ISDN MIB March 1997
isdnSignalingStatus
}
isdnSignalingIndex OBJECT-
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-
STATUS
"The index value which uniquely identifies an
in the isdnSignalingTable."
::= { isdnSignalingEntry 1 }
isdnSignalingIfIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The ifIndex value of the interface associated with
signaling channel."
::= { isdnSignalingEntry 2 }
isdnSignalingProtocol OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The particular protocol type supported by
switch providing access to the ISDN
to which this signaling channel is connected."
::= { isdnSignalingEntry 3 }
isdnSignalingCallingAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The ISDN Address to be assigned to this
channel. More specifically, this is the 'Calling
information element' as being passed to the
in outgoing call setup messages
It can be an EAZ (1TR6), a calling number (DSS1, ETSI
or any other number necessary to identify a
interface. If there is no such number defined or required
this is a zero length string. It is represented
DisplayString form
Incoming calls can also be identified by this number
Roeck Standards Track [Page 32]
RFC 2127 ISDN MIB March 1997
If the Directory Number, i.e. the Called Number
incoming calls, is different to this number,
isdnDirectoryTable has to be used to specify
possible Directory Numbers
The format of this information largely depends on the
of switch or PBX the device is connected to. Therefore
the detailed format of this information is
specified and is implementation dependent
If possible, the agent should implement this
using the E.164 number format. In this case, the
must start with '+'. Otherwise, IA5 number digits
be used."
"ITU-T E.164, Q.931 chapter 4.5.10"
DEFVAL { "" }
::= { isdnSignalingEntry 4 }
isdnSignalingSubAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Supplementary information to the ISDN address
to this signaling channel. Usually, this is
subaddress as defined in Q.931.
If there is no such number defined or required, this
a zero length string
The subaddress is used for incoming calls as well
for outgoing calls
The subaddress is an user supplied string of up to 20
IA5 characters and is transmitted transparently
the network."
"ITU-T I.330, Q.931 chapter 4.5.11"
DEFVAL { "" }
::= { isdnSignalingEntry 5 }
isdnSignalingBchannelCount OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The total number of B channels (bearer channels
managed by this signaling channel. The default
of this object depends on the physical interface
and is either 2 for Basic Rate interfaces
Roeck Standards Track [Page 33]
RFC 2127 ISDN MIB March 1997
24 (30) for Primary Rate interfaces."
::= { isdnSignalingEntry 6 }
isdnSignalingInfoTrapEnable OBJECT-
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-
STATUS
"Indicates whether isdnMibCallInformation
should be generated for calls on this
channel."
DEFVAL { disabled }
::= { isdnSignalingEntry 7 }
isdnSignalingStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object is used to create and delete rows in
isdnSignalingTable."
::= { isdnSignalingEntry 8 }
-- Signaling channel statistics
-- There is one entry for each signaling
-- in this table
-- Note that the ifEntry also has some statistics information
isdnSignalingStatsTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"ISDN signaling table containing
information for all ISDN signaling
on this managed device
Only statistical information which is not already
counted in the ifTable is being defined in this table."
::= { isdnSignalingGroup 3 }
isdnSignalingStatsEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
Roeck Standards Track [Page 34]
RFC 2127 ISDN MIB March 1997
"An entry in the ISDN Signaling statistics Table."
AUGMENTS { isdnSignalingEntry }
::= { isdnSignalingStatsTable 1 }
IsdnSignalingStatsEntry ::= SEQUENCE {
isdnSigStatsInCalls Counter32,
isdnSigStatsInConnected Counter32,
isdnSigStatsOutCalls Counter32,
isdnSigStatsOutConnected Counter32,
isdnSigStatsChargedUnits Counter32
}
isdnSigStatsInCalls OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of incoming calls on this interface."
::= { isdnSignalingStatsEntry 1 }
isdnSigStatsInConnected OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of incoming calls on this
which were actually connected."
::= { isdnSignalingStatsEntry 2 }
isdnSigStatsOutCalls OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of outgoing calls on this interface."
::= { isdnSignalingStatsEntry 3 }
isdnSigStatsOutConnected OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of outgoing calls on this
which were actually connected."
::= { isdnSignalingStatsEntry 4 }
isdnSigStatsChargedUnits OBJECT-
SYNTAX Counter32
Roeck Standards Track [Page 35]
RFC 2127 ISDN MIB March 1997
MAX-ACCESS read-
STATUS
"The number of charging units on this interface
system startup
Only the charging units applying to the local interface
i.e. for originated calls or for calls with '
charging' being active, are counted here."
::= { isdnSignalingStatsEntry 5 }
--
-- The LAPD
isdnLapdTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Table containing configuration and
information for all LAPD (D channel Data Link
interfaces on this managed device
Only statistical information which is not already
counted in the ifTable is being defined in this table."
::= { isdnSignalingGroup 4 }
isdnLapdEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the LAPD Table."
INDEX { ifIndex }
::= { isdnLapdTable 1 }
IsdnLapdEntry ::= SEQUENCE {
isdnLapdPrimaryChannel TruthValue
isdnLapdOperStatus INTEGER
isdnLapdPeerSabme Counter32,
isdnLapdRecvdFrmr Counter32
}
isdnLapdPrimaryChannel OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"If set to true(1), this D channel is the
primary D channel if D channel backup is active
Roeck Standards Track [Page 36]
RFC 2127 ISDN MIB March 1997
There must be exactly one primary D
configured. If D channel backup is not used,
object has a value of true(1)."
"Q.931 [8], Annex F, D channel backup procedures."
::= { isdnLapdEntry 1 }
isdnLapdOperStatus OBJECT-
SYNTAX INTEGER {
inactive(1),
l1Active(2),
l2Active(3)
}
MAX-ACCESS read-
STATUS
"The operational status of this interface
inactive all layers are
l1Active layer 1 is activated
layer 2 datalink not
l2Active layer 1 is activated
layer 2 datalink established."
::= { isdnLapdEntry 2 }
isdnLapdPeerSabme OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of peer SABME frames received on
interface. This is the number of peer-
new connections on this interface."
::= { isdnLapdEntry 3 }
isdnLapdRecvdFrmr OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of LAPD FRMR response frames received
This is the number of framing errors on
interface."
::= { isdnLapdEntry 4 }
--
-- Optional groups follow here
Roeck Standards Track [Page 37]
RFC 2127 ISDN MIB March 1997
-- The Terminal Endpoint group and
-- This table is required only if TEI values or SPID
-- have to be entered
-- The ifIndex values for this table are identical to those
-- the isdnSignalingChannel table
isdnEndpointGroup OBJECT IDENTIFIER ::= { isdnMibObjects 4 }
isdnEndpointGetIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The recommended procedure for selecting a new index
isdnEndpointTable row creation is to GET the value
this object, and then to SET the object with the
value. If the SET operation succeeds, the manager can
this value as an index to create a new row in this table."
"RFC1903, TestAndIncr textual convention."
::= { isdnEndpointGroup 1 }
isdnEndpointTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Table containing configuration for
Endpoints."
::= { isdnEndpointGroup 2 }
isdnEndpointEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the Terminal Endpoint Table. The
of isdnEndpointIfType must be supplied for a
in this table to become active."
INDEX { isdnEndpointIndex }
::= { isdnEndpointTable 1 }
IsdnEndpointEntry ::= SEQUENCE {
isdnEndpointIndex INTEGER
isdnEndpointIfIndex InterfaceIndex
isdnEndpointIfType IANAifType
isdnEndpointTeiType INTEGER
Roeck Standards Track [Page 38]
RFC 2127 ISDN MIB March 1997
isdnEndpointTeiValue INTEGER
isdnEndpointSpid DisplayString
isdnEndpointStatus
}
isdnEndpointIndex OBJECT-
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-
STATUS
"The index value which uniquely identifies an
in the isdnEndpointTable."
::= { isdnEndpointEntry 1 }
isdnEndpointIfIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The ifIndex value of the interface associated with
Terminal Endpoint."
::= { isdnEndpointEntry 2 }
isdnEndpointIfType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The interface type for this Terminal Endpoint
Interface types of x25ple(40) and isdn(63) are allowed
The interface type is identical to the value
ifType in the associated ifEntry."
::= { isdnEndpointEntry 3 }
isdnEndpointTeiType OBJECT-
SYNTAX INTEGER {
dynamic(