draft-ietf-isdnmib-snmp-isdn-mib-00.txt   draft-ietf-isdnmib-snmp-isdn-mib-01.txt 
ISDN Management Information Base ISDN Management Information Base
draft-ietf-isdnmib-snmp-isdn-mib-00.txt draft-ietf-isdnmib-snmp-isdn-mib-01.txt
Mon Jun 19 19:13:44 MET DST 1995 Fri Oct 6 11:53:57 MET 1995
Guenter Roeck Guenter Roeck
Conware GmbH Conware GmbH
roeck@conware.de roeck@conware.de
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
skipping to change at page 2, line 7 skipping to change at page 2, line 7
or to cite them other than as a "work in progress". or to cite them other than as a "work in progress".
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
1. Introduction 1. Introduction
This memo defines an experimental portion of the Management Information This draft defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it defines a minimal set of managed objects community. In particular, it defines a minimal set of managed objects
for SNMP-based management of ISDN interfaces. ISDN interfaces are for SNMP-based management of ISDN interfaces. ISDN interfaces are
supported on a variety of equipment (for data and voice) including supported on a variety of equipment (for data and voice) including
terminal adapters, bridges, hosts, and routers. The set of objects will terminal adapters, bridges, hosts, and routers. The set of objects will
be consistent with the SNMP framework and existing SNMP standards. be consistent with the SNMP framework and existing SNMP standards.
This document is a product of the ISDN MIB working group within the
Internet Engineering Task Force. Comments are solicited and should be
addressed to the working group's mailing list at isdn-mib@combinet.com
and/or the author.
2. The SNMPv2 Network Management Framework 2. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major The SNMPv2 Network Management Framework consists of four major
components. They are: components. They are:
o RFC 1442 [1] which defines the SMI, the mechanisms used for o RFC 1442 [1] which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management. describing and naming objects for the purpose of management.
o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
objects for the Internet suite of protocols. objects for the Internet suite of protocols.
skipping to change at page 4, line 9 skipping to change at page 4, line 9
SMI. In particular, each object type is named by an OBJECT IDENTIFIER, SMI. In particular, each object type is named by an OBJECT IDENTIFIER,
an administratively assigned name. The object type together with an an administratively assigned name. The object type together with an
object instance serves to uniquely identify a specific instantiation of object instance serves to uniquely identify a specific instantiation of
the object. For human convenience, we often use a textual string, the object. For human convenience, we often use a textual string,
termed the descriptor, to refer to the object type. termed the descriptor, to refer to the object type.
3. Overview 3. Overview
3.1. Structure of MIB 3.1. Structure of MIB
For the management of ISDN interfaces, there are three groups of For managing ISDN interfaces, the following information is necessary:
information necessary. They are:
o A group for managing subscriber interfaces, often referred to as D
channels, and B channels.
o A group for managing neighbors
o A group returning call history information. o Information for managing physical interfaces. In case of ISDN
primary rate, this will usually be T1 or E1 lines, being managed in
the Trunk MIB. For Basic Rate lines, physical interfaces will be
managed by this MIB.
Within this document, these groups have been structured into three o Information for managing signalling channels, usually referred to
different MIBs, which will be described in the following chapters. The as D channels.
purpose of this structuring is to be able to use parts of this
information for non-ISDN interfaces as well. In particular, the call
control and call history MIBs might also be used for other types of
interfaces.
3.1.1. The ISDN MIB o Information for managing bearer channels, usually referred to as B
channels.
This MIB controls subscriber interfaces as well as B channel interfaces. Within this document, this information has been structured into three
It consists of three groups. groups, which will be described in the following chapters.
o The isdnMibGeneralGroup is used to return general information valid In order to manage connections over ISDN lines, the management of
for the entire ISDN subsystem. neighbors and call history information is required as well. This
information will be defined in the Dial Control MIB.
o The isdnMibSubscriberGroup is used to control ISDN subscriber The purpose for splitting the required information in two MIBs is to be
interfaces. It consists of two tables, the isdnSubscriberTable for able to use parts of this information for non-ISDN interfaces as well.
configuration information and the isdnSubscriberStatsTable for In particular, the Dial Control MIB might also be used for other types
statistics information. of interfaces.
o The isdnPortGroup is used to control B channels. It supports 3.1.1. General Description
configuration parameters as well as statistical information related
to B channels.
3.1.2. The call control MIB This MIB controls signalling channels as well as B channels and physical
Basic Rate interfaces. It consists of three groups.
The call control MIB describes neighbors for demand access lines as well o The isdnMibBasicRateGroup is used to provide information regarding
as for other kinds of interfaces. It basically consists of one table physical Basic Rate interfaces.
describing neighbor entries.
3.1.3. The call history MIB o The isdnMibSignallingGroup is used to control ISDN signalling
channels. It consists of two tables, the isdnSignallingTable for
configuration information and the isdnSignallingStatsTable for
statistics information.
The call history MIB describes and stores call information. This o The isdnBearerGroup is used to control bearer channels, usually
information can for example be used for accounting purposes. It referred to as B channels. It supports configuration parameters as
consists of one table with an entry for each call that has been made. well as statistical information related to B channels.
3.2. Relationship to RFC1573 3.2. Relationship to RFC1573
RFC 1573, the Interface MIB Evolution, requires that any MIB module RFC 1573, the Interface MIB Evolution, requires that any MIB module
which is an adjunct of the Interface MIB, clarify specific areas within which is an adjunct of the Interface MIB, clarify specific areas within
the Interface MIB. These areas were intentionally left vague in RFC the Interface MIB. These areas were intentionally left vague in RFC
1573 to avoid over constraining the MIB module, thereby precluding 1573 to avoid over constraining the MIB module, thereby precluding
management of certain media-types. management of certain media-types.
Section 3.3 of RFC 1573 enumerates several areas which a media-specific Section 3.3 of RFC 1573 enumerates several areas which a media-specific
MIB module must clarify. Each of these areas is addressed in a MIB module must clarify. Each of these areas is addressed in a
following subsection. The implementor is referred to RFC 1573 in order following subsection. The implementor is referred to RFC 1573 in order
to understand the general intent of these areas. to understand the general intent of these areas.
3.2.1. Layering Model and Virtual Circuits 3.2.1. Layering Model
On an occasional access channel, there are a number of neighboring An ISDN interface usually consists of a signalling channel (D channel)
systems that are permitted to call or be called, all of which need to be and a number of bearer channels (B channels), all of which will be
treated as active from a routing viewpoint, but most of which have no layered on top of a physical interface.
call in progress at any given time.
On an ISDN interface, this is complicated by the fact that calls to a This is accomplished in this MIB by creating a logical interface
given neighbor float from channel to channel. One cannot definitively (ifEntry) for each of the D channels and a logical interface (ifEntry)
say "I call this neighbor on that B channel." It is necessary, for each of the B channels. These are then correlated to each other and
therefore, to provide a mapping algorithm between the B or H channels, to the physical interface using the ifStack table of RFC 1573.
and the various logical interfaces supporting the neighbors. This is
solved by creating a logical interface (ifEntry) for each neighbor and a
logical interface (ifEntry) for each B channel. These are then
correlated using the ifStackTable.
The model, therefore, looks something like this: The basic model, therefore, looks something like this:
| | | | | | <== interface to upper
+--+ +--+ +--+ +--+ +--+ +--+ layers, to be handled
| D | | B | | B | by Dial Control MIB
|channel| |channel| .... |channel| and ifStack table
+--+ +--+ +--+ +--+ +--+ +--+
| | | | | | <== attachment to physical
+--+ +--------+ +------------+ +----+ interfaces, to be provided
| physical interface | by ifStack table
| (S0/Uk0 or T1/E1) |
+-----------------------------------+
Mapping of B/D channels to physical interfaces
IfEntries are maintained for D channels and for each B channel. The D
channel's interface ifType is one of the ISDN interface types; the B
channel ifType is isdn(63). The ifType for physical interfaces is the
matching IANA ifType, usually T1 or E1 for physical Primary Rate
interfaces and >>to be assigned<< for physical Basic Rate interfaces.
The ifStackTable is used to map B and D channels to physical interfaces.
Conceivably, X.25 or Frame Relay interface MIBs could then be layered on
the D channel.
Mapping of B channels to upper interface layers will usually be done
using the Dial Control MIB. For example, mapping on top of B channels
might look as follows:
+-------------------------------------------------------+ +-------------------------------------------------------+
| Network Layer Protocol | | Network Layer Protocol |
+------+ +-------+ +-------+ +-------+ +-------+ +------+ +------+ +-------+ +-------+ +-------+ +-------+ +------+
| | | | | | | | | | <== appears active | | | | | | | | | | <== appears active
+-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
| PPP | | PPP | | F/R | | PPP | | F/R | | PPP | | PPP | | F/R | | PPP | | F/R |
| for | | for | | for | | for | | for | ifEntry with | for | | for | | for | | for | | for | ifEntry with
|Nbr 1| |Nbr 2| |switch |Nbr 3| |switch shadow |Nbr 1| |Nbr 2| |switch |Nbr 3| |switch shadow
| | | | | A | | | | B | callCtlNbrEntry | | | | | A | | | | B | NeighborEntry
+-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
| | | | <== some actually are | | | | <== some actually are
+--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+
| B | | B | | B | | B | | B | | B | | B |
|channel| |channel| |channel| |channel| |channel| |channel| |channel|
+--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+
| | | | | | | | | | | | | |
+------+ +-------+ +-------+ +-------+ +-------+ +------+ +------+ +-------+ +-------+ +-------+ +-------+ +------+
| Basic/Primary Rate Interface | | Basic/Primary Rate Interface |
+-------------------------------------------------------+ +-------------------------------------------------------+
Mapping of IP interfaces to Called Neighbors to B Channels Mapping of IP interfaces to Called Neighbors to B Channels
IfEntries are maintained for D channels and for each B channel. The D In this model, ifEntries are maintained for each neighbor. Each
channel's interface ifType is one of the ISDN interface types; B channel neighbor is required to have an associated ifEntry. This interface can
ifTypes are all "other". The ifStackTable is used to map logical be of any kind, e.g. PPP or LAPB.
interfaces to B channel interfaces. Conceivably, X.25 or Frame Relay
interface MIBs could also be layered on the D channel.
3.2.2. ifTestTable 3.2.2. ifTestTable
The ifTestTable is not supported by this MIB. The ifTestTable is not supported by this MIB.
3.2.3. ifRcvAddressTable 3.2.3. ifRcvAddressTable
The ifRcvAddressTable is not supported by this MIB. The ifRcvAddressTable is not supported by this MIB.
3.2.3.1. ifEntry for a D channel 3.2.4. ifEntry
3.2.4.1. ifEntry for a Basic Rate hardware interface
The ifGeneralGroup of RFC 1573 is being supported for Basic Rate
hardware interfaces.
ifTable Comments ifTable Comments
============== =========================================== ============== ===========================================
ifIndex Each ISDN D channel is represented by an ifEntry. ifIndex Each ISDN Basic Rate hardware interface is
represented by an ifEntry.
ifDescr Textual port description. ifDescr Textual port description.
ifType The IANA value reserved for basicISDN(20) ifType An IANA value to be assigned.
and primaryISDN(21)
ifMtu The size of the largest frame which can be ifSpeed The overall bandwidth of this interface.
sent/received on this D Channel,
specified in octets.
ifSpeed The bandwidth of this D channel. ifPhysAddress Return zero.
ifPhysAddress The ISDN address assigned to this subscriber ifAdminStatus The desired administrative status of the
interface. This is a copy of isdnSubTblIfAddress. ISDN interface.
ifOperStatus The current operational status of this
interface. If the operational status is dormant(5),
the interface is in standby mode, i.e. connnected
to the network, but without call activity.
If the operational status is down(2), the hardware
has detected that there is no level 1 connection
to the switch.
ifLastChange Refer to RFC 1573.
ifLinkUpDownTrapEnable
Refer to RFC 1573.
ifConnectorPresent
Refer to RFC 1573.
ifHighSpeed Return zero.
ifName Refer to RFC 1573.
3.2.4.2. ifEntry for a D channel (signalling channel)
The ifEntry for a D channel supports the ifGeneralGroup and the
ifPacketGroup of RFC 1573.
ifTable Comments
============== ===========================================
ifIndex Each ISDN D channel is represented by an ifEntry.
ifDescr Textual port description.
ifType The IANA value of basicISDN(20) or primaryISDN(21),
depending on the media type.
ifSpeed The bandwidth of this D channel. Usually, this will
be the value of 16000 for basic rate interfaces or
64000 for primary rate interfaces.
ifPhysAddress The ISDN address assigned to this signalling
interface. This is a copy of isdnSigTblCalledAddress.
ifAdminStatus The desired administrative status of the ifAdminStatus The desired administrative status of the
ISDN port. ISDN interface.
ifOperStatus The current operational status of the ISDN ifOperStatus The current operational status of the ISDN
UNI (User Network Interface) port. If the UNI (User Network Interface) interface. If the
operational status is dormant(5), the D channel operational status is dormant(5), the D channel
is in standby mode (see [5], Annex F, D channel is in standby mode (see [5], Annex F, D channel
backup procedures). backup procedures).
ifLastChange Refer to RFC 1573. ifLastChange Refer to RFC 1573.
ifLinkUpDownTrapEnable
Refer to RFC 1573.
ifConnectorPresent
Refer to RFC 1573.
ifHighSpeed Return zero.
ifName Refer to RFC 1573.
ifMtu The size of the largest frame which can be
sent/received on this D Channel,
specified in octets.
ifInOctets The total number of octets received on this ifInOctets The total number of octets received on this
D channel. D channel.
ifInUcastPkts The number of frames received on this D channel ifInUcastPkts The number of frames received on this D channel
whose address is not TEI=127. whose address is not TEI=127.
ifInNUcastPkts Deprecated. Return the number of frames ifInNUcastPkts Deprecated. Return the number of frames
received on this D channel which is received on this D channel which is
targeted TEI=127. targeted TEI=127.
ifInDiscards The total number of received frames discards. ifInDiscards The total number of received frames which have been
discarded.
The possible reasons are: buffer shortage. The possible reasons are: buffer shortage.
ifInErrors The number of inbound frames that contained ifInErrors The number of inbound frames that contained
errors preventing them from being deliverable errors preventing them from being deliverable
to LAPD. to LAPD.
ifInUnknownProtos The number of frames with this interface's TEI, ifInUnknownProtos The number of frames with this interface's TEI,
but unknown SAPI. but unknown SAPI.
ifOutOctets The total number of octets transmitted on this ifOutOctets The total number of octets transmitted on this
D channel. D channel.
ifOutUcastPkts The number of frames transmitted on this ifOutUcastPkts The number of frames transmitted on this
D channel whose address is not TEI=127. D channel whose address is not TEI=127.
ifOutNUcastPkts Deprecated. Return the number of frames ifOutNUcastPkts Deprecated. Return the number of frames
transmitted on this D channel which transmitted on this D channel which
has TEI=127. have TEI=127.
ifOutDiscards The total number of outbound frames which ifOutDiscards The total number of outbound frames which
were discarded. Possible reasons are: were discarded. Possible reasons are:
buffer shortage. buffer shortage.
ifOutErrors The number of frames which could not be ifOutErrors The number of frames which could not be
transmitted due to errors. transmitted due to errors.
ifOutQlen Deprecated. Return zero. ifOutQlen Deprecated. Return zero.
ifSpecific Deprecated. Return {0 0}. ifSpecific Deprecated. Return {0 0}.
3.2.3.2. ifEntry for a B channel 3.2.4.3. ifEntry for a B channel (bearer channel)
The ifEntry for a B channel supports the ifGeneralGroup and the
ifPacketGroup of RFC 1573.
ifTable Comments ifTable Comments
============== =========================================== ============== ===========================================
ifIndex Each ISDN B channel is represented by an ifEntry. ifIndex Each ISDN B channel is represented by an ifEntry.
ifDescr Textual port description. ifDescr Textual port description.
ifType The IANA value reserved for other(1) ifType The IANA value of isdn(63).
ifMtu The size of the largest frame which can be
sent/received on this B Channel,
specified in octets.
ifSpeed The bandwidth of this B channel. ifSpeed The bandwidth of this B channel.
Usually, this will be the value Usually, this will be the value
of 64000. For ISDN leased lines of 56000 or 64000. For ISDN leased lines
(or eventually hyperchannels), (or eventually hyperchannels),
this will be the total capacity this will be the total capacity
of this interface. of this interface.
ifPhysAddress The ISDN address assigned to this port. ifPhysAddress The ISDN address assigned to this port.
This is a copy of isdnPortIfAddress. This is a copy of isdnBearerCalledAddress.
ifAdminStatus The desired administrative status of the ifAdminStatus The desired administrative status of the
ISDN port. ISDN port.
ifOperStatus The current operational status of the ISDN ifOperStatus The current operational status of the ISDN
port. Note that dormant(5) is explicitely being port. Note that dormant(5) is explicitely being
used as defined in RFC1573. used as defined in RFC1573.
ifLastChange Refer to RFC 1573. ifLastChange Refer to RFC 1573.
ifLinkUpDownTrapEnable
Refer to RFC 1573.
ifConnectorPresent
Refer to RFC 1573.
ifHighSpeed Return zero.
ifName Refer to RFC 1573.
ifMtu The size of the largest frame which can be
sent/received on this B Channel,
specified in octets.
ifInOctets The total number of octets received on this ifInOctets The total number of octets received on this
B channel. B channel.
ifInUcastPkts The number of frames received on this B channel. ifInUcastPkts The number of frames received on this B channel.
ifInNUcastPkts Deprecated. Return zero. ifInNUcastPkts Deprecated. Return zero.
ifInDiscards The total number of received frames discards. ifInDiscards The total number of received frames discards.
The possible reasons are: buffer shortage. The possible reasons are: buffer shortage.
skipping to change at page 10, line 16 skipping to change at page 13, line 9
transmitted due to errors. transmitted due to errors.
ifOutQlen Deprecated. Return zero. ifOutQlen Deprecated. Return zero.
ifSpecific Deprecated. Return {0 0}. ifSpecific Deprecated. Return {0 0}.
3.3. ISDN interface specific information 3.3. ISDN interface specific information
3.3.1. ISDN leased lines 3.3.1. ISDN leased lines
ISDN leased lines are being handled by setting isdnSubTblSwitchType to ISDN leased lines on Basic Rate interfaces can be specified by setting
the according type of leased line. In this case, there is no active D the value of isdnBasicTblConnectionType to one of the leased line types.
channel required, since a leased line does not require any signalling. There will be no signalling table entry for leased lines, since there is
If possible with the according type of leased line (e.g., leasedS01 or no signalling channel available. Thus, only B channel interfaces will
leasedS02 for Germany), the D channel may also be used for data exist in this case.
transfer. In this case, isdnSubTblDchannelIndex will point to itself,
which then identifies the possibility to use this channel for data For Primary Rate interfaces, a leased line does not have any ISDN
transfer. specifics. Therefore, Primary Rate leased lines will entirely be handled
by the according MIB for this kind of interfaces, i.e. the Trunk MIB for
E1/T1 interfaces. No ISDN ifEntries will exist in this case.
3.3.2. Hyperchannels 3.3.2. Hyperchannels
Hyperchannels can be defined using callCtlNbrInfoType and The switch protocol in use will define if hyperchannels are being
callCtlNbrInfoRate objects in the call control MIB. However, remember supported, and the actual support will be implementation dependent.
that the switch type has to support this type of connections. Hyperchannel connections itself will be requested by the interface user,
e.g. by the neighbor connection handling procedures.
In the ISDN MIB, the isdnBearerStatsMultirate object of
isdnBearerStatsTable can be used to check if hyperchannels are being
used for an active call.
3.3.3. D channel backup and NFAS trunks 3.3.3. D channel backup and NFAS trunks
D channel backup is defined in [5], Annex F. It describes non- D channel backup is defined in [5], Annex F. It describes non-
associated signalling and its use and functionality is basically associated signalling and its use and functionality is basically
identical to NFAS trunks. identical to NFAS trunks.
Non Facility Accociated Signalling (NFAS) basically means that a D Non Facility Accociated Signalling (NFAS) basically means that a D
channel on a PRI interface is used to manage calls on a second PRI channel on a PRI interface is used to manage calls on other PRI trunks.
trunk. This is required in North America for H11 channels, since all 24 This is required in North America for H11 channels, since all 24 time
time slots are being used for bearer channels. slots are being used for bearer channels.
According to [5], Annex F, the D channel backup feature can be provided According to [5], Annex F, the D channel backup feature can be provided
on a subscription basis and is network dependent. The D channel backup on a subscription basis and is network dependent. The D channel backup
procedure is described in detail in [5]. procedure is described in detail in [5].
D channel backup and NFAS trunks are being handled using the In case of D channel backup or NFAS trunks, the isdnSigTblPhysInterface
isdnSubTblDchannelIndex object of the isdnSubscriberTable. object defines the physical interface the D channel resides on. Using
the ifStack table, the active D channel is layered on top of all
physical interfaces being managed by this D channel.
In case of D channel backup, inactive D channels will have an
operational status of dormant(5).
3.3.4. X.25 data transfer in D channel 3.3.4. X.25 data transfer in D channel
Transfer of X.25 data over D channels can be handled by attaching an Transfer of X.25 data over D channels can be handled by attaching an
X.25 interface to a D channel using the ifStack table of RFC 1573. X.25 interface to a D channel using the ifStack table of RFC 1573.
3.3.5. SPID handling 3.3.5. SPID handling
Service Profile IDentifiers (SPID) are defined for BRI interfaces only, Service Profile IDentifiers (SPID) are defined for BRI interfaces only,
and being used in North America. SPIDs are required for DMS-100 and NI- and being used in North America. SPIDs are required for DMS-100 and NI-
skipping to change at page 11, line 29 skipping to change at page 14, line 32
Usually, each B channel has one SPID assigned. It is normally built from Usually, each B channel has one SPID assigned. It is normally built from
the party number (calling address for outgoing calls) with a number of the party number (calling address for outgoing calls) with a number of
digits prepended and appended. Since each network appears to be digits prepended and appended. Since each network appears to be
different, both the calling address and the SPID have to be stored. different, both the calling address and the SPID have to be stored.
The SPID identifies the particular services that have been provisioned The SPID identifies the particular services that have been provisioned
for a terminal. If there are two B channels on a BRI, there can be two 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. SPIDs, one for each of the two B channels.
The SPID gets registered with the switch after link establishment. The SPID gets registered with the switch after link establishment.
There is one data link for each SPID. As part of termina registration, There is one data link for each SPID. As part of terminal registration,
an endpoint ID is defined by the switch. On incoming calls, the switch an EID (Endpoint IDentifier) is defined by the switch. On incoming
may provide the endpoint ID, a called party number, or both, depending calls, the switch may provide the EID, a called party number, or both,
on the ISDN code implemented in the switch. depending on the ISDN code implemented in the switch.
In the ISDN MIB, the SPID can be entered using the idnPortAdditionalInfo The EID has two bytes: USID (User Service IDentifier) and TID (Terminal
object of isdnPortTable. The ifPhysaddress, already being used to IDentifier). These are later used by some of the software versions
specify the calling number, cannot be used for this purpose, since both running on the switch side (e.g. compliant with NI-1, 5ESS custom) to
may differ and be required in parallel. broadcast SETUP messages with these included, so the correct endpoint
would accept the call. Other switch software versions identify the
endpoint with the Called Party Number.
4. Definitions In the ISDN MIB, the SPID can be entered using the isdnBearerIfSpid
object of isdnBearerTable. The isdnBearerCallingAddress, already being
used to specify the calling number, cannot be used for this purpose,
since both may differ and be required in parallel.
4.1. ISDN MIB 3.3.6. Closed User Groups
Closed User Groups (CUG), as defined in [5], chapter 4.6.1, are being
supported for circuit mode calls at least by ETSI and 1TR6. In this
networks, an ISDN address can have one or more CUG numbers assigned. To
such addresses, only calls from attached Closed User Groups will be
accepted by the network.
Thus, Closed User Groups are a parameter for neighbor entries and will
thus be defined in the Dial Control MIB. A neighbor entry attached to a
Closed User Group will have to point to an ISDN interface which belongs
to the Closed User group in question.
3.3.7. Provision of point-to-point line topology
In the ISDN standards, there are two different meanings for the term
"point-to-point".
In ISDN standards, the term point-to-point will usually be used for data
link connections, i.e. layer 2 connections, where each layer 2
connection from the TE to the network is a single point-to-point
connection. Multiple connections of this kind may exist on one physical
(layer 1) connection, however, and in case of Basic Rate interfaces
there may be several TE's connected to one physical line 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 layer 1
connection will always be of the point-to-point type. For Basic Rate
interfaces, layer 1 point-to-point connections do exist in several
countries, usually being used for connecting PBX systems to the network.
The second meaning (layer 1 connections) is what will be referred to as
"point-to-point" connection throughout this document.
The isdnSignallingTable object isdnSigTblLineTopology can be used to
select the line topology. In case of Primary Rate interfaces, this
object will always have a value of pointToPoint(1).
3.3.8. Speech and audio bearer capability information elements
The objects speech(1), audio_31() and audio_7(), as being used in
isdnBearerStatsInfoType, refer to the Speech, 3.1 kHz Audio and old 7
kHz Audio (now Multi-use) bearer capabilities for ISDN, as defined in
[5], chapter 4.5.5, octet 3 of bearer capability information element.
These capabilities are signaling artifices that allow networks to do
certain things with the call. It is up to the network to decide what to
do.
The Speech Bearer Capability means that speech is being carried over the
channel, as in two people talking. This would be POTS-type speech. The
network may compress this, encrypt it or whatever it wants with it as
long as it delivers POTS quality speech to the other end. In other
words, a modem is not guaranteed to work over this connection.
The 3.1 kHz Audio capability indicates that the network carries the 3.1
kHz bandwidth across the network. This would (theoretically) allow
modem signals to be carried across the network. In the US, the network
automatically enters a capability of 3.1 kHz Audio on calls coming into
the ISDN from a POTS network. This capability restricts the network
from messing with the data channel in a way that would corrupt the 3.1
kHz VoiceBand data.
7 kHz Audio was meant to signal the use of a higher quality audio
connection (e.g., music from radio). It got changed to Multi-Use
capability to allow it to be used for videoconferencing with fall back
to audio or something like that.
In some cases, the Speech or 3.1 kHz Bearer Capability provides a 56
kbit/s data path through the network. Therefore, some people are
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 advantage of
favorable tariffs for Speech as opposed to Data.
On the incoming side, the equipment is usually configured to ignore the
Bearer Capability and either answer all Speech calls as 56 kbit/s data
or to use one Directory Number for real speech and another for data.
4. Definitions
ISDN-MIB DEFINITIONS ::= BEGIN ISDN-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Counter32, Counter32,
Integer32, Integer32
TimeTicks,
experimental
FROM SNMPv2-SMI FROM SNMPv2-SMI
DisplayString DisplayString,
TruthValue,
TimeStamp,
TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
ifIndex,
InterfaceIndex InterfaceIndex
FROM IF-MIB; FROM IF-MIB
transmission
FROM RFC1213-MIB;
isdnMib MODULE-IDENTITY isdnMib MODULE-IDENTITY
LAST-UPDATED "9506161200Z" LAST-UPDATED "9510061157Z"
ORGANIZATION "IETF ISDN Working Group" ORGANIZATION "IETF ISDN MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Guenter Roeck " Guenter Roeck
Postal: Conware GmbH Postal: Conware GmbH
Killisfeldstrasse 64 Killisfeldstrasse 64
76227 Karlsruhe 76227 Karlsruhe
Germany Germany
Tel: +49 721 9495 0 Tel: +49 721 9495 0
E-mail: roeck@conware.de" E-mail: roeck@conware.de"
DESCRIPTION DESCRIPTION
"The MIB module to describe the "The MIB module to describe the
management of ISDN interfaces." management of ISDN interfaces."
::= { experimental 98 } ::= { transmission 20 }
-- The ISDN hardware interface (BRI or PRI) will be represented -- The ISDN hardware interface (BRI or PRI) will be represented
-- by a media specific ifEntry.
--
-- For basic rate lines, the media specifics for the physical interface
-- will be defined in the physical interface group of the ISDN MIB.
-- The ifType for physical basic rate interfaces will be tbd(xxx).
--
-- For primary rate, the media specifics will be defined in the Trunk MIB.
-- The ifType will be one of E1 or T1, depending on the line type.
-- Each signalling channel, also called D channel, will be represented
-- by an entry in the isdnSignallingTable.
-- This will have an ifType value of basicISDN(20) -- This will have an ifType value of basicISDN(20)
-- or primaryISDN(21), refer to RFC 1213. -- or primaryISDN(21), refer to RFC 1213.
-- Each B channel will also be represented as an entry -- Each B channel will also be represented as an entry
-- in the ifTable. The B channels will have an ifType value -- in the ifTable. The B channels will have an ifType value
-- of isdn(63).
-- This model will be used while defining objects and tables -- This model will be used while defining objects and tables
-- for management. -- for management.
-- The ISDN MIB will allow sub-layers. For example, the data transfer -- The ISDN MIB will allow sub-layers. For example, the data transfer
-- over a B channel may take place with PPP encapsulation. While the -- over a B channel may take place with PPP encapsulation. While the
-- ISDN MIB will describe the D and B channels, a media specific MIB for -- ISDN MIB will describe the D and B channels, a media specific MIB for
-- PPP can be used on a layered basis. This will be as per RFC 1573. -- PPP can be used on a layered basis. This will be as per RFC 1573.
-- Textual conventions
IsdnSignallingProtocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used as the syntax of the
isdnSigTblSignallingProtocol object in the
definition of ISDN-MIB's isdnSignallingTable.
The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values should be made to IANA via
email (iana@isi.edu)."
SYNTAX INTEGER {
other(1), -- none of the following
dss1(2), -- ITU DSS1 (formerly CCITT) Q.931
etsi(3), -- Europe / ETSI ETS300-102
-- plus supplementary services
-- (ETSI 300-xxx)
-- note that NET3, NET5 define
-- test procedures for ETS300-102
-- and have been replaced by
-- I-CTR 3 and I-CTR 4.
btnr(4), -- U.K. / BTNR (BRI ?) (retired ?)
dass2(5), -- U.K. / DASS2 (PRI)
ess4(6), -- U.S.A. / AT&T 4ESS
ess5(7), -- U.S.A. / AT&T 5ESS
dms100(8), -- U.S.A. / Northern Telecom DMS100
dms250(9), -- U.S.A. / Northern Telecom DMS250
ni1(10), -- U.S.A. / National ISDN 1 (BRI)
ni2(11), -- U.S.A. / National ISDN 2 (BRI, PRI)
ni3(12), -- U.S.A. / next one ?
vn2(13), -- France / VN2
vn3(14), -- France / VN3
vn4(15), -- France / VN4 (ETSI with changes)
vn6(16), -- France / VN6 (ETSI with changes)
-- delta document CSE P 10-21 A
-- test document CSE P 10-20 A
kdd(17), -- Japan / KDD
ins64(18), -- Japan / NTT INS64
ins1500(19), -- Japan / NTT INS1500
itr6(20), -- Germany/ 1TR6 (BRI, PRI)
cornet(21), -- Germany/ Siemens HiCom CORNET
tad2(22), -- ??? / (BRI)
tad30(23), -- ??? / (PRI)
ts013(24), -- Australia / TS013 (formerly TPH 1962, BRI)
ts014(25), -- Australia / TS014 (formerly TPH 1856, PRI)
dpnss(26), -- ???
qsig(27) -- Q.SIG
}
-- Isdn Mib objects definitions -- Isdn Mib objects definitions
isdnMibObjects OBJECT IDENTIFIER ::= { isdnMib 1 } isdnMibObjects OBJECT IDENTIFIER ::= { isdnMib 1 }
-- ISDN physical interface group
-- This group describes physical basic rate interfaces.
-- Basic rate interfaces can either be dialup lines,
-- supporting B channels as well as having an active signalling
-- channel, or leased line interfaces connecting up to two B channels
-- and one D channel directly to a neighbor.
isdnFirmwareVersion OBJECT-TYPE -- In case of leased line interfaces, there will be no signalling
SYNTAX DisplayString
MAX-ACCESS read-only -- protocol active and thus be no isdnSignallingTable entry
-- layered on top of the physical interface.
isdnBasicRateGroup OBJECT IDENTIFIER ::= { isdnMibObjects 1 }
isdnBasicRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF IsdnBasicRateTableEntry
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ISDN firmware version." "Table containing configuration and operational
::= { isdnMibObjects 1 } parameters for all physical Basic Rate
interfaces on this managed device."
::= { isdnBasicRateGroup 1 }
isdnBasicRateTableEntry OBJECT-TYPE
SYNTAX IsdnBasicRateTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the ISDN Basic Rate Table."
INDEX { ifIndex }
::= { isdnBasicRateTable 1 }
IsdnBasicRateTableEntry ::= SEQUENCE {
isdnBasicTblIfType INTEGER,
isdnBasicTblConnectionType INTEGER
}
isdnSubscriberGroup OBJECT IDENTIFIER ::= { isdnMibObjects 2 } isdnBasicTblIfType OBJECT-TYPE
SYNTAX INTEGER {
isdnS0(1),
isdnUk0(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The physical interface type."
::= { isdnBasicRateTableEntry 1 }
isdnBasicTblConnectionType OBJECT-TYPE
SYNTAX INTEGER {
dialup(1), -- dialup line, with active signalling channel
leased1B(2), -- leased line, 1B channel
leased1B1D(3), -- leased line, 1B+D
leased2B(4), -- leased line, 2B
leased2B1D(5) -- leased line, 2B+D
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The particular connection being handled over this
physical interface."
::= { isdnBasicRateTableEntry 2 }
-- ISDN signalling group
isdnSignallingGroup OBJECT IDENTIFIER ::= { isdnMibObjects 2 }
-- Assumptions being made: -- Assumptions being made:
-- - BRI/PRI definition will be handled in ifTable, thus not -- - BRI/PRI definition will be handled in ifTable, thus not
-- be required here. -- be required here.
-- D channel configuration table -- D channel configuration table
-- There is one entry for each D channel (also called signalling
-- channel) in this table.
--
-- D channel backup and NFAS trunks will be handled using the
-- ifStack table.
isdnSubscriberTable OBJECT-TYPE isdnSignallingTable OBJECT-TYPE
SYNTAX SEQUENCE OF IsdnSubscriberTableEntry SYNTAX SEQUENCE OF IsdnSignallingTableEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ISDN subscriber table containing configuration and "ISDN signalling table containing configuration and
operational parameters for all ISDN subscriber operational parameters for all ISDN signalling
interfaces on this managed device." interfaces on this managed device."
::= { isdnSubscriberGroup 1 } ::= { isdnSignallingGroup 1 }
isdnSubscriberTableEntry OBJECT-TYPE isdnSignallingTableEntry OBJECT-TYPE
SYNTAX IsdnSubscriberTableEntry SYNTAX IsdnSignallingTableEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the ISDN Subscriber Table." "An entry in the ISDN Signalling Table."
INDEX { isdnSubTblIndex } INDEX { ifIndex }
::= { isdnSubscriberTable 1 } ::= { isdnSignallingTable 1 }
IsdnSubscriberTableEntry ::= SEQUENCE { IsdnSignallingTableEntry ::= SEQUENCE {
isdnSubTblIndex InterfaceIndex, isdnSigTblPhysInterface InterfaceIndex,
isdnSubTblDchannelIndex InterfaceIndex, isdnSigTblSignallingProtocol IsdnSignallingProtocol,
isdnSubTblSwitchType INTEGER, isdnSigTblLineTopology INTEGER,
isdnSubTblIfAddress DisplayString, isdnSigTblCalledAddress DisplayString,
isdnSubTblBchannelCount Integer32, isdnSigTblCallingAddress DisplayString,
isdnSubTblFlags Integer32 isdnSigTblSubAddress DisplayString,
isdnSigTblBchannelCount Integer32,
isdnSigTblOperStatus INTEGER
} }
isdnSubTblIndex OBJECT-TYPE isdnSigTblPhysInterface OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex of an subscriber interface
on this managed device."
::= { isdnSubscriberTableEntry 1 }
isdnSubTblDchannelIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex of the D channel currently associated "ifIndex value of the physical interface the D channel
with this subscriber interface. This has usually the resides on. In case of NFAS trunks, this object is required
same value as isdnSubTblIndex, but may differ in case to define the physical interface the D channel resides on,
D channel backup (see [5], Annex F) is active or NFAS since the attached ifEntry will be layered on top of all
trunks are being used. interfaces being managed by this signalling channel."
Editor's note: ::= { isdnSignallingTableEntry 1 }
Does this object have to be defined as read-write ?"
::= { isdnSubscriberTableEntry 2 }
-- --
-- Editor's note: -- Editor's note:
-- We decided to have IANA supporting the signalling protocols.
-- Thus, each switch manufacturer or anyone needing a new protocol
-- entry will be responsible for getting a value from IANA.
-- The definition has thereby been moved into a textual convention
-- defined above.
isdnSubTblSwitchType OBJECT-TYPE isdnSigTblSignallingProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX IsdnSignallingProtocol
other(1),
dss1(2), -- ITU DSS1 (formerly CCITT) Q.931
etsi(3), -- Europe / ETSI ETS300-102
-- plus supplementary services
-- (ETSI 300-xxx)
-- note that NET3, NET5 define
-- test procedures for ETS300-102
-- and are to be replaced by ICTR.
btnr(4), -- U.K. / BTNR (BRI ?)
dass2(5), -- U.K. / DASS2 (PRI)
ess4(6), -- U.S.A. / AT&T 4ESS
ess5(7), -- U.S.A. / AT&T 5ESS
dms100(8), -- U.S.A. / Northern Telecom DMS100/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 one ?
vn2(12), -- France / VN2
vn3(13), -- France / VN3
vn4(14), -- France / VN4 (ETSI with changes)
vn6(15), -- France / VN6 (ETSI with changes)
-- delta document CSE P 10-21 A
-- test document CSE P 10-20 A
kdd(16), -- Japan / KDD
ins64(17), -- Japan / NTT INS64
itr6(18), -- Germany/ 1TR6 (BRI, PRI)
cornet(19), -- Germany/ Siemens HiCom CORNET
tad2(20), -- ??? / (BRI)
tad30(21), -- ??? / (PRI)
ts013(22), -- Australia / TS013 (formerly TPH 1962, BRI)
ts014(23), -- Australia / TS014 (formerly TPH 1856, PRI)
--
-- some specifications for ISDN leased lines, as
-- existing in Germany and eventually in the U.S.,
-- follow.
--
leased64s(24), -- 1xB (Germany)
leasedS01(25), -- 1xB, 1xD (Germany)
leasedS02(26), -- 2xB, 1xD (Germany)
leasedH0(27), -- 6xB
leasedT1(28), -- 24xB
leasedE1(29) -- 30xB (Germany)
}
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The particular protocol type supported by the "The particular protocol type supported by the
switch providing access to the ISDN network switch providing access to the ISDN network
to which this subscriber interface is connected." to which this signalling interface is connected."
::= { isdnSubscriberTableEntry 3 } ::= { isdnSignallingTableEntry 2 }
isdnSubTblIfAddress OBJECT-TYPE isdnSigTblLineTopology OBJECT-TYPE
SYNTAX DisplayString SYNTAX INTEGER {
pointToPoint(1),
pointToMultipoint(2)
}
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ISDN Address to be assigned to this subscriber "The line topology to be used for this interface.
interface. This can be an EAZ (1TR6), a calling number On Primary Rate interfaces, this object must have
(DSS1, ETSI) or any other number necessary a value of pointToPoint(1) and should be read-only."
to identify a subscriber interface. ::= { isdnSignallingTableEntry 3 }
If there is no such number defined or
required, this is a zero length string.
It is represented in DisplayString form.
Editor's note:
This parameter can be specified on a
per-B-channel or per-D-channel base.
If specified here (e.g. on PRI interfaces,
also possible with EAZ or calling number
for BRI), all incoming calls will have to
be addressed to this number.
On the other side, calling numbers can be
defined on a per-B-channel base, thus
enabling structured access to B channels.
"
::= { isdnSubscriberTableEntry 4 }
isdnSubTblBchannelCount OBJECT-TYPE isdnSigTblCalledAddress OBJECT-TYPE
SYNTAX Integer32 (1..255) SYNTAX DisplayString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of B channels (bearer channels) managed "This object specifies the number being passed by the
by this subscriber interface." switch on incoming call setup messages as 'Called Number
::= { isdnSubscriberTableEntry 5 } information element'. This can be an EAZ (1TR6), a called
number (DSS1, ETSI) or any other number necessary to
identify a signalling interface. If there is no such number
defined or required, this is a zero length string.
It is represented in DisplayString form.
This parameter can be specified on a per-B-channel or
per-D-channel base. If specified here (e.g. on PRI
interfaces), all incoming calls will have to be addressed
to this number.
Called numbers for incoming calls can also be
defined on a per-B-channel base, thus
enabling structured access to B channels. "
::= { isdnSignallingTableEntry 4 }
isdnSubTblFlags OBJECT-TYPE isdnSigTblCallingAddress OBJECT-TYPE
SYNTAX Integer32 SYNTAX DisplayString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Special flags for this subscriber Interface. "The ISDN Address to be assigned to this signalling
interface. More specific, this is the 'Calling Address
information element' as being passed to the switch
in outgoing call setup messages.
The value is a sum. Starting from zero, for each It can be an EAZ (1TR6), a called number (DSS1, ETSI)
type of generic flag, 2 raised to a power is added or any other number necessary to identify a signalling
to the sum. The powers are according to the following interface. If there is no such number defined or required,
table: or if the called number on incoming calls is identical
to the calling number on outgoing calls, this is a zero
length string. It is represented in DisplayString form.
Power Meaning This parameter can be specified on a per-B-channel or
0 1TR6 specific per-D-channel base. If specified here (e.g. on PRI
If set, do not send the own EAZ on outgoing interfaces), all outgoig calls will use this number
calls. as 'calling address'.
This is required in 1TR6 for PABX systems
treating the EAZ as part of the called number
on outgoing calls.
"
::= { isdnSubscriberTableEntry 7 }
Calling numbers for outgoing calls can also be
defined on a per-B-channel base, thus
enabling structured access to B channels. "
::= { isdnSignallingTableEntry 5 }
isdnSubscriberStatsTable OBJECT-TYPE isdnSigTblSubAddress OBJECT-TYPE
SYNTAX SEQUENCE OF IsdnSubscriberStatsEntry SYNTAX DisplayString
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ISDN subscriber table containing statistics "Supplementary information to the ISDN address assigned
information for all ISDN subscriber interfaces to this interface. Usually, this will be the subaddress
on this managed device. as defined in Q.931.
Only statistical information which is not being counted If there is no such number defined or required, this is
in the ifTable is being defined in this table." a zero length string.
::= { isdnSubscriberGroup 2 } The subaddress will be used for incoming calls as well as
for outgoing calls.
It is represented in DisplayString form."
::= { isdnSignallingTableEntry 6 }
isdnSubscriberStatsEntry OBJECT-TYPE isdnSigTblBchannelCount OBJECT-TYPE
SYNTAX IsdnSubscriberStatsEntry SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the ISDN Subscriber statisctics Table" "The total number of B channels (bearer channels)
INDEX { isdnSubStatsIndex } managed by this signalling interface."
::= { isdnSubscriberStatsTable 1 } ::= { isdnSignallingTableEntry 7 }
IsdnSubscriberStatsEntry ::= SEQUENCE { isdnSigTblOperStatus OBJECT-TYPE
isdnSubStatsIndex InterfaceIndex, SYNTAX INTEGER {
isdnSubStatsLapdUnsolicResp Counter32, inactive (1),
isdnSubStatsLapdPeerSabme Counter32, l1_active (2),
isdnSubStatsLapdN200Errors Counter32, l2_active (3),
isdnSubStatsLapdNrSeqErrors Counter32, l3_active (4)
isdnSubStatsLapdRecvdFrmr Counter32,
isdnSubStatsLapdCntlErrors Counter32,
isdnSubStatsLapdInfoErrors Counter32,
isdnSubStatsLapdWrongSize Counter32,
isdnSubStatsLapdN201Errors Counter32,
isdnSubStatsInCalls Counter32,
isdnSubStatsInConnected Counter32, -- count rejects too ?
isdnSubStatsOutCalls Counter32,
isdnSubStatsOutConnected Counter32 -- count rejects too ?
-- total # of charged units
} }
isdnSubStatsIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex of an ISDN BRI, DBRI, PRI/T1 or PRI/E1
interface on this managed device."
::= { isdnSubscriberStatsEntry 1 }
isdnSubStatsLapdUnsolicResp OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of unsolicited LAPD response frames received "The operational status of this signalling interface:
on all data links associated with the D-channel of this
ISDN interface."
::= { isdnSubscriberStatsEntry 2 }
isdnSubStatsLapdPeerSabme OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of peer SABME frames received on all data links
associated with the D-channel of this ISDN interface."
::= { isdnSubscriberStatsEntry 3 }
isdnSubStatsLapdN200Errors OBJECT-TYPE inactive all layers are inactive
SYNTAX Counter32 l1_active layer 1 is activated,
MAX-ACCESS read-only layer 2 datalink not established
STATUS current l2_active layer 1 is activated,
DESCRIPTION layer 2 datalink established,
"The number of unsuccessful T200 timer recoveries no layer 3 call activity
after a frame has been retransmitted N200 times." l3_active layer 1 is activated,
::= { isdnSubscriberStatsEntry 4 } layer 2 datalink established,
layer 3 engaged in call activity
"
::= { isdnSignallingTableEntry 8 }
isdnSubStatsLapdNrSeqErrors OBJECT-TYPE -- Signalling channel statistics table
SYNTAX Counter32 -- There is one entry for each signalling connection
MAX-ACCESS read-only -- in this table.
STATUS current -- Note that the ifEntry also has some statistics information.
DESCRIPTION
"The number of N(R) sequence errors."
::= { isdnSubscriberStatsEntry 5 }
isdnSubStatsLapdRecvdFrmr OBJECT-TYPE isdnSignallingStatsTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF IsdnSignallingStatsEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of LAPD FRMR response frames received." "ISDN signalling table containing statistics
::= { isdnSubscriberStatsEntry 6 } information for all ISDN signalling interfaces
on this managed device.
Only statistical information which is not being counted
in the ifTable is being defined in this table."
::= { isdnSignallingGroup 2 }
isdnSubStatsLapdCntlErrors OBJECT-TYPE isdnSignallingStatsEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX IsdnSignallingStatsEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of LAPD frames received with an invalid "An entry in the ISDN Signalling statistics Table"
or non-implemented control field." INDEX { ifIndex }
::= { isdnSubscriberStatsEntry 7 } ::= { isdnSignallingStatsTable 1 }
isdnSubStatsLapdInfoErrors OBJECT-TYPE IsdnSignallingStatsEntry ::= SEQUENCE {
SYNTAX Counter32 isdnSigStatsLapdPeerSabme Counter32,
MAX-ACCESS read-only isdnSigStatsLapdRecvdFrmr Counter32,
STATUS current isdnSigStatsInCalls Counter32,
DESCRIPTION isdnSigStatsInConnected Counter32,
"The number of LAPD frames received with a non-permitted isdnSigStatsOutCalls Counter32,
information (I) field." isdnSigStatsOutConnected Counter32,
::= { isdnSubscriberStatsEntry 8 } isdnSigStatsChargedUnits Counter32
}
isdnSubStatsLapdWrongSize OBJECT-TYPE isdnSigStatsLapdPeerSabme OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of LAPD frames received which were the "The number of peer SABME frames received on all
wrong size." data links associated with the D-channel of this
::= { isdnSubscriberStatsEntry 9 } interface. This is the number of peer-initiated
new connections on this interface."
::= { isdnSignallingStatsEntry 1 }
isdnSubStatsLapdN201Errors OBJECT-TYPE isdnSigStatsLapdRecvdFrmr OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of LAPD frames received which contained "The number of LAPD FRMR response frames received.
and information field which exceeded N201." This is the number of framing errors on this
::= { isdnSubscriberStatsEntry 10 } interface."
::= { isdnSignallingStatsEntry 2 }
isdnSubStatsInCalls OBJECT-TYPE isdnSigStatsInCalls OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of incoming calls on this interface." "The number of incoming calls on this interface."
::= { isdnSubscriberStatsEntry 11 } ::= { isdnSignallingStatsEntry 3 }
isdnSubStatsInConnected OBJECT-TYPE isdnSigStatsInConnected OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of incoming calls on this interface "The number of incoming calls on this interface
which were actually connected." which were actually connected."
::= { isdnSubscriberStatsEntry 12 } ::= { isdnSignallingStatsEntry 4 }
isdnSubStatsOutCalls OBJECT-TYPE isdnSigStatsOutCalls OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of outgoing calls on this interface." "The number of outgoing calls on this interface."
::= { isdnSubscriberStatsEntry 13 } ::= { isdnSignallingStatsEntry 5 }
isdnSubStatsOutConnected OBJECT-TYPE isdnSigStatsOutConnected OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of outgoing calls on this interface "The number of outgoing calls on this interface
which were actually connected." which were actually connected."
::= { isdnSubscriberStatsEntry 14 } ::= { isdnSignallingStatsEntry 6 }
isdnSigStatsChargedUnits OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of charging units on this interface since system
startup.
Only the charging units applying to the local interface,
i.e. for originated calls or for calls with 'Reverse charging'
being active, will be counted here."
::= { isdnSignallingStatsEntry 7 }
-- The B channel (bearer channel) group
--
-- Note that disconnects can explicitely be handled using the
-- ifStack table. If a connection is to be disconnected,
-- the according ifStack entry has to be removed.
-- More specific, the ifStackTable entry which binds the high-layer
-- ifTable entry (and related dialCtlNbrCfgTable entry) to the
-- B channel ifTable entry (and related isdnBearerTable entry)
-- during an active call has to be removed.
isdnMibPorts OBJECT IDENTIFIER ::= { isdnMibObjects 3 } isdnBearerGroup OBJECT IDENTIFIER ::= { isdnMibObjects 3 }
isdnPortTable OBJECT-TYPE isdnBearerTable OBJECT-TYPE
SYNTAX SEQUENCE OF IsdnPortEntry SYNTAX SEQUENCE OF IsdnBearerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines port specific control and "This table defines port specific control data
statistics data for ISDN B channels." for ISDN B channels. Each entry in this table
::= { isdnMibPorts 1 } describes one B (bearer) channel."
::= { isdnBearerGroup 1 }
isdnPortEntry OBJECT-TYPE isdnBearerEntry OBJECT-TYPE
SYNTAX IsdnPortEntry SYNTAX IsdnBearerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information relating to the current port. "Configuration information relating to one port.
A port is a single B channel." A port is a single B channel."
INDEX { isdnPortSubIfIndex, isdnPortIfIndex } INDEX { ifIndex }
::= { isdnPortTable 1 } ::= { isdnBearerTable 1 }
IsdnPortEntry ::= IsdnBearerEntry ::=
SEQUENCE { SEQUENCE {
isdnPortSubIfIndex InterfaceIndex, isdnBearerCalledAddress DisplayString,
isdnPortIfIndex InterfaceIndex, isdnBearerCallingAddress DisplayString,
isdnPortIfAddress DisplayString, isdnBearerSubAddress DisplayString,
isdnPortAdditionalInfo DisplayString, isdnBearerIfSpid DisplayString,
isdnPortAdminStatus INTEGER, isdnBearerOperStatus INTEGER
isdnPortOperStatus INTEGER,
isdnPortRemoteAddress DisplayString,
isdnPortInfoType INTEGER,
isdnPortInfoRate INTEGER,
isdnPortCause INTEGER,
isdnPortCallOrigin INTEGER,
isdnPortChargedUnits Counter32,
isdnPortConnectionUpTime TimeTicks
} }
isdnPortSubIfIndex OBJECT-TYPE isdnBearerCalledAddress OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX DisplayString
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ifIndex describing the subscriber channel associated "The ISDN address for incoming calls which is assigned to
with this port. this B channel. This can be the EAZ (1TR6), the called number
Note that this does _not_ have to be the associated (DSS1) for incoming calls or any other necessary
D channel. If D channel backup is active, specification for other types of switch protocols.
the active D channel will be described in the If no address is to be assigned to this interface,
subscriber table entry." this object will be a zero length string."
::= { isdnPortEntry 1 } ::= { isdnBearerEntry 1 }
isdnPortIfIndex OBJECT-TYPE isdnBearerCallingAddress OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX DisplayString
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Port identifier being used to identify a "The ISDN address for outgoing calls which is assigned to
B channel. This value is identical to the this B channel. This can be the EAZ (1TR6), the calling number
ifIndex describing this B channel on this (DSS1) for outgoung calls or any other necessary
managed device." specification for other types of switch protocols.
::= { isdnPortEntry 2 } If no address is to be assigned to this interface,
or if the address to be assigned is identical to
isdnBearerCalledAddress, this object will be a zero length
string."
::= { isdnBearerEntry 2 }
isdnPortIfAddress OBJECT-TYPE isdnBearerSubAddress OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ISDN address assigned to this B channel. This can be "The ISDN subaddress assigned to this B channel, according
the EAZ (1TR6), the calling number and subaddress (DSS1) to Q.931. If no subaddress is being used or defined for
or any other necessary specification for other types of the signalling protocol being used, this can be a zero
switch protocols." length string."
::= { isdnPortEntry 3 } ::= { isdnBearerEntry 3 }
isdnPortAdditionalInfo OBJECT-TYPE isdnBearerIfSpid OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Additional addressing information required to configure "The SPID information required to configure a B channel.
a B channel. An example for this kind of information This information has to be defined in addition to
is a SPID, which has to be defined in addition to the the local number for some switch types.
local number for some switch types."
::= { isdnPortEntry 4 }
isdnPortAdminStatus OBJECT-TYPE If this object is not required, it will be a
zero length string."
::= { isdnBearerEntry 4 }
isdnBearerOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
normal(1), idle (1),
disconnect(2) connecting (2),
connected (3),
active (4)
} }
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administratively desired state of this port. "The current call control state for this port.
normal(1) will cause nothing when being set.
disconnect(2) will disconnect an active call or abort
any call in progress. The agent will then set the
value of isdnPortAdminStatus back to normal(1)."
::= { isdnPortEntry 5 }
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 process
of validation.
active(4): A call is active on this interface."
::= { isdnBearerEntry 5 }
isdnPortOperStatus OBJECT-TYPE isdnBearerStatsTable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX SEQUENCE OF IsdnBearerStatsEntry
idle (1), MAX-ACCESS not-accessible
initiated (2), STATUS current
overlapSend (3), DESCRIPTION
outgoing (4), "This table defines port specific statistics and
delivered (5), active call data for ISDN B channels. Each entry
present (6), in this table describes one B (bearer) channel."
received (7), ::= { isdnBearerGroup 2 }
connecting (8),
incoming (9), isdnBearerStatsEntry OBJECT-TYPE
active (10), SYNTAX IsdnBearerStatsEntry
disconReq (11), MAX-ACCESS not-accessible
disconInd (12), STATUS current
suspend (13), DESCRIPTION
resume (14), "Statistics information relating to one port.
release (15), A port is a single B channel."
overlapRecv (16) INDEX { ifIndex }
::= { isdnBearerStatsTable 1 }
IsdnBearerStatsEntry ::=
SEQUENCE {
isdnBearerStatsPeerAddress DisplayString,
isdnBearerStatsPeerSubAddress DisplayString,
isdnBearerStatsCallOrigin INTEGER,
isdnBearerStatsInfoType INTEGER,
isdnBearerStatsMultirate TruthValue,
isdnBearerStatsCallSetupTime TimeStamp,
isdnBearerStatsCallConnectTime TimeStamp,
isdnBearerStatsChargedUnits Integer32
} }
isdnBearerStatsPeerAddress OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Q.931 call control state for this port." "The ISDN address the current or last call is or was
::= { isdnPortEntry 6 } connected to. If the peer ISDN address is not available,
this object it will have a length of zero."
::= { isdnBearerStatsEntry 1 }
isdnPortRemoteAddress OBJECT-TYPE isdnBearerStatsPeerSubAddress OBJECT-TYPE
SYNTAX DisplayString -- (SIZE (0..40)) SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote ISDN address the current "The ISDN subaddress the current or last call is or was
or last call is or has been connected to." connected to. If the peer subaddress is not available,
::= { isdnPortEntry 7 } this object it will have a length of zero."
::= { isdnBearerStatsEntry 2 }
isdnPortCause OBJECT-TYPE isdnBearerStatsCallOrigin OBJECT-TYPE
SYNTAX INTEGER (0..255) SYNTAX INTEGER {
originate(1),
answer(2),
callback(3)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The cause value associated with the last call. "The call origin for the current or last call. If there was
For active calls, the value of this object will no call up to now on this interface, this object will have
be zero." a value of zero."
::= { isdnPortEntry 8 } ::= { isdnBearerStatsEntry 3 }
isdnPortInfoType OBJECT-TYPE isdnBearerStatsInfoType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
speech(1), speech(1),
unrestrictedDigital(2), -- as defined in [5] unrestrictedDigital(2), -- as defined in [5]
unrestrictedDigital_56(3), -- with 56k rate adaption unrestrictedDigital_56(3), -- with 56k rate adaption
restrictedDigital(4), restrictedDigital(4),
audio(5), audio_31(5), -- 3.1 kHz audio
video(6) audio_7(6), -- 7 kHz audio
video(7),
packetSwitched(8)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Information Transfer Capability for the current "The Information Transfer Capability for the current
or last call, as defined in [5], chapter 4.5.5, or last call, as defined in [5], chapter 4.5.5,
octet 3 of bearer capability information element, octet 3 of bearer capability information element,
combined with the User Rate (as defined in octet 5 combined with the User Rate (as defined in octet 5
and 5a to 5d), if rate adaption is being used." and 5a to 5d), if rate adaption is being used.
::= { isdnPortEntry 9 }
isdnPortInfoRate OBJECT-TYPE speech(1) refers to a non-data connection, whereas
SYNTAX INTEGER { audio_31(5) and audio_7(6) refer to data mode connections.
tr_64(1),
tr_2x64(2), Note that [5], chapter 4.5.5, originaly defined audio_7(6)
tr_384(3), as '7 kHz audio' and now defines it as 'Unrestricted
tr_1536(4), digital information with tones/announcements'.
tr_multirate(5) "
} ::= { isdnBearerStatsEntry 4 }
isdnBearerStatsMultirate OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Information Transfer Rate for the current "This flag describes if the current or last call used
or last call, as defined in [5], chapter 4.5.5, multirate as defined in [5], chapter 4.5.5.
octet 4 of bearer capability information element. The actual information transfer rate,
For tr_multirate(5), the actual information transfer rate,
in detail specified in octet 4.1 (rate multiplier), in detail specified in octet 4.1 (rate multiplier),
will be defined in ifSpeed for this interface." will be defined in ifSpeed for this interface."
::= { isdnPortEntry 10 } ::= { isdnBearerStatsEntry 5 }
isdnPortCallOrigin OBJECT-TYPE isdnBearerStatsCallSetupTime OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TimeStamp
none(1), -- e.g. has never been connected
outgoing(2), -- outgoing call (TE to NT)
incoming(3), -- incoming call (NT to TE)
callback(4) -- incoming call has been called back by TE
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Flag indicating who has initiated the "The value of sysUpTime when the ISDN setup message for the
current or last connection." current or last call was sent or received."
::= { isdnPortEntry 11 } ::= { isdnBearerStatsEntry 6 }
isdnPortChargedUnits OBJECT-TYPE isdnBearerStatsCallConnectTime OBJECT-TYPE
SYNTAX Counter32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of charged units for the current "The value of sysUpTime when the ISDN connect message for the
or last connection. This value will be counted current or last call was sent or received."
only if charging information is being supplied ::= { isdnBearerStatsEntry 7 }
by the network."
::= { isdnPortEntry 12 }
isdnPortConnectionUpTime OBJECT-TYPE isdnBearerStatsChargedUnits OBJECT-TYPE
SYNTAX TimeTicks SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time the current or last call has been active." "The number of charged units for the current or last
::= { isdnPortEntry 13 } connection. For incoming calls or if charging information
is not supplied by the switch, the value of this object
will be zero."
::= { isdnBearerStatsEntry 8 }
-- --
-- conformance information -- conformance information
-- --
isdnMibConformance OBJECT IDENTIFIER ::= { isdnMib 2 } isdnMibConformance OBJECT IDENTIFIER ::= { isdnMib 2 }
isdnMibCompliances OBJECT IDENTIFIER ::= { isdnMibConformance 1 } isdnMibCompliances OBJECT IDENTIFIER ::= { isdnMibConformance 1 }
isdnMibGroups OBJECT IDENTIFIER ::= { isdnMibConformance 2 } isdnMibGroups OBJECT IDENTIFIER ::= { isdnMibConformance 2 }
-- compliance statements -- compliance statements
isdnMibCompliance MODULE-COMPLIANCE isdnMibCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for entities which implement "The compliance statement for entities which implement
the ISDN MIB" the ISDN MIB. Note that the isdnMibBasicRateGroup
is mandatory only for entities supporting Basic Rate
interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
isdnMibGeneralGroup, isdnMibBasicRateGroup,
isdnMibSubscriberGroup, isdnMibSignallingGroup,
isdnMibPortGroup } isdnMibBearerGroup
::= { isdnMibCompliances 1 }
isdnMibGeneralGroup OBJECT-GROUP
OBJECTS {
isdnFirmwareVersion
}
STATUS current
DESCRIPTION
"General information relating to the ISDN interfaces on
the managed devices."
::= { isdnMibGroups 1 }
isdnMibSubscriberGroup OBJECT-GROUP
OBJECTS {
isdnSubTblDchannelIndex,
isdnSubTblSwitchType,
isdnSubTblIfAddress,
isdnSubTblBchannelCount,
isdnSubTblFlags,
isdnSubStatsLapdUnsolicResp,
isdnSubStatsLapdPeerSabme,
isdnSubStatsLapdN200Errors,
isdnSubStatsLapdNrSeqErrors,
isdnSubStatsLapdRecvdFrmr,
isdnSubStatsLapdCntlErrors,
isdnSubStatsLapdInfoErrors,
isdnSubStatsLapdWrongSize,
isdnSubStatsLapdN201Errors,
isdnSubStatsInCalls,
isdnSubStatsInConnected,
isdnSubStatsOutCalls,
isdnSubStatsOutConnected
}
STATUS current
DESCRIPTION
"A collection of objects required for ISDN subscriber
interface configuration and statistics."
::= { isdnMibGroups 2 }
isdnMibPortGroup OBJECT-GROUP
OBJECTS {
isdnPortIfAddress,
isdnPortAdditionalInfo,
isdnPortAdminStatus,
isdnPortOperStatus,
isdnPortRemoteAddress,
isdnPortInfoType,
isdnPortInfoRate,
isdnPortCause,
isdnPortCallOrigin,
isdnPortChargedUnits,
isdnPortConnectionUpTime
}
STATUS current
DESCRIPTION
"A collection of objects required for ISDN bearer channel
interface control and statistics."
::= { isdnMibGroups 3 }
END
4.2. Call Control MIB
CALL-CONTROL-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
NOTIFICATION-TYPE,
OBJECT-TYPE,
Counter32,
Integer32,
experimental
FROM SNMPv2-SMI
DisplayString,
TimeStamp,
RowStatus
FROM SNMPv2-TC
MODULE-COMPLIANCE,
OBJECT-GROUP
FROM SNMPv2-CONF
InterfaceIndex
FROM IF-MIB;
callControlMib MODULE-IDENTITY
LAST-UPDATED "9506161200Z"
ORGANIZATION "IETF ISDN Working Group"
CONTACT-INFO
" Guenter Roeck
Postal: Conware GmbH
Killisfeldstrasse 64
76227 Karlsruhe
Germany
Tel: +49 721 9495 0
E-mail: roeck@conware.de"
DESCRIPTION
"The MIB module to describe neighbors
for demand access and possibly other
kinds of interfaces."
::= { experimental 99 }
callControlMibObjects OBJECT IDENTIFIER ::= { callControlMib 1 }
callCtlConfiguration OBJECT IDENTIFIER ::= { callControlMibObjects 1 }
callCtlAcceptMode OBJECT-TYPE
SYNTAX INTEGER {
acceptNone(1),
acceptAll(2),
acceptKnown(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The security level for acceptance of incoming calls.
accept-none(1) - incoming calls will not be accepted
accept-all(2) - incoming calls will be accepted,
even if there is no matching entry
in the callCtlNbrTable
accept-known(3)- incoming calls will be accepted only
if there is a matching entry in the
callCtlNbrTable
"
::= { callControlMibObjects 2 }
callCtlNeighbor OBJECT IDENTIFIER ::= { callControlMibObjects 3 }
callCtlNbrTable OBJECT-TYPE
SYNTAX SEQUENCE OF CallCtlNbrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The list of neighbors from which the managed device
will accept calls or to which it will place them."
::= { callCtlNeighbor 1 }
callCtlNbrEntry OBJECT-TYPE
SYNTAX CallCtlNbrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A single Neighbor. This entry is effectively permanent, and contains
information describing the neighbor, his permissions, his last call
attempt, and his cumulative effects."
INDEX { callCtlNbrId }
::= { callCtlNbrTable 1 }
CallCtlNbrEntry ::=
SEQUENCE {
callCtlNbrId Integer32,
-- sequence number
callCtlNbrIfType INTEGER,
callCtlNbrPhysIf InterfaceIndex,
-- ifIndex value of D channel
callCtlNbrLogIf InterfaceIndex,
-- ifIndex value of virtual interface
callCtlNbrName DisplayString,
-- name of the neighbor
callCtlNbrAddress DisplayString,
-- Call Address
callCtlNbrInfoType INTEGER,
-- service to be used
callCtlNbrInfoRate INTEGER,
-- information rate to be used
callCtlNbrPermission INTEGER,
-- applicable permissions
callCtlNbrInactivityTimer INTEGER,
-- disconnect idle timer
callCtlNbrCallRetries INTEGER (0..2147483647),
-- number of call retries
callCtlNbrMaxDuration INTEGER (0..2147483647),
-- Max call duration in seconds
callCtlNbrLastDuration INTEGER (0..2147483647),
-- Duration of last call
callCtlNbrClearReason DisplayString,
-- reason last call completed
callCtlNbrClearCode OCTET STRING,
-- reason last call completed
callCtlNbrSuccessCalls Counter32,
-- number of completed calls to neighbor
callCtlNbrFailCalls Counter32,
-- number of failed call attempts
callCtlNbrAcceptCalls Counter32,
-- number of calls from neighbor accepted
callCtlNbrRefuseCalls Counter32,
-- number of calls from neighbor refused
callCtlNbrLastAttemptTime TimeStamp,
-- sysUpTime of last call attempt
callCtlNbrStatus RowStatus
}
callCtlNbrId OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"arbitrary sequence number associated with the neighbor."
::= { callCtlNbrEntry 1 }
callCtlNbrIfType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
isdn(2),
modem(3),
leasedLine(4),
x25(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of physical interface."
DEFVAL { other }
::= { callCtlNbrEntry 2 }
callCtlNbrPhysIf OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"ifIndex value of the physical interface the neighbor will be
called on. On an ISDN interface, this is the ifIndex value of
the D channel. If the physical interface can be dynamically
assigned, this object has a value of zero."
DEFVAL { 0 }
::= { callCtlNbrEntry 3 }
callCtlNbrLogIf OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"ifIndex value of virtual interface associated with the
neighbor. This interface maintains a queue of messages
holding for the neighbor awaiting call completion,
and all statistics."
::= { callCtlNbrEntry 4 }
callCtlNbrName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"ASCII name of the neighbor."
::= { callCtlNbrEntry 5 }
callCtlNbrAddress OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Call Address at which the neighbor will be called.
Think of this as the set of characters following 'ATDT '
or the 'phone number' included in a D channel call request.
This call address will include all switch specific
optional information, e.g. subaddress, closed user group or
semi-permanent connection.
The structure of this information will have to be
defined for each switch type."
::= { callCtlNbrEntry 6 }
callCtlNbrInfoType OBJECT-TYPE
SYNTAX INTEGER {
speech(1),
unrestrictedDigital(2), -- as defined in [5]
unrestrictedDigital_56(3), -- with 56k rate adaption
restrictedDigital(4),
audio(5),
video(6)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Information Transfer Capability for this neighbor,
as defined in [5], chapter 4.5.5, octet 3
of bearer capability information element,
combined with the User Rate (as defined in octet 5
and 5a to 5d), if rate adaption is being used.
This information is required for ISDN circuits."
::= { callCtlNbrEntry 7 }
callCtlNbrInfoRate OBJECT-TYPE
SYNTAX INTEGER (0..2048)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Information Transfer Rate to be used for this neighbor,
as defined in [5], chapter 4.5.5,
octet 4 and 4.1 of bearer capability information element.
The information transfer rate being specified has to be
a multiple of 64, defining the rate to be used in kbit/s.
If the information rate to be used is unknown or 64kBit/s,
the value of this object may be zero."
DEFVAL { 0 }
::= { callCtlNbrEntry 8 }
callCtlNbrPermission OBJECT-TYPE
SYNTAX INTEGER { outgoing (1),
incoming (2),
both (3), -- both outgoing & incoming
callback(4)
} }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Applicable permissions. callback(4) either rejects the
call and then calls back, or uses the 'Advice of Charge'
supplementary service if it is available."
DEFVAL { both }
::= { callCtlNbrEntry 9 }
callCtlNbrInactivityTimer OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The connection will be automatically disconnected
if no longer carrying useful data for a time
period, in seconds, specified in this object.
Useful data in this context refers to forwarding
packets, including routing information; it
excludes the encapsulator maintenance frames.
A value of zero means the connection will not be
automatically taken down due to inactivity,
which implies that it is a dedicated circuit."
DEFVAL { 0 }
::= { callCtlNbrEntry 10 }
callCtlNbrCallRetries OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of calls to a non-responding address
that may be made. A retry count of zero means
there is no bound. The intent is to bound
the number of successive calls to an address
which is inaccessible, or which refuses those calls."
DEFVAL { 0 }
::= { callCtlNbrEntry 11 }
callCtlNbrMaxDuration OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum call duration in seconds. Zero means 'unlimited'."
DEFVAL { 0 }
::= { callCtlNbrEntry 12 }
callCtlNbrLastDuration OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Duration of last call in seconds."
::= { callCtlNbrEntry 13 }
callCtlNbrClearReason OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ASCII reason that the last call terminated."
::= { callCtlNbrEntry 14 }
callCtlNbrClearCode OBJECT-TYPE OBJECT isdnBasicTblIfType
SYNTAX OCTET STRING MIN-ACCESS read-only
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"encoded reason last call completed."
::= { callCtlNbrEntry 15 }
callCtlNbrSuccessCalls OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"number of completed calls to neighbor since system reset."
::= { callCtlNbrEntry 16 }
callCtlNbrFailCalls OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"number of failed call attempts to neighbor since system reset."
::= { callCtlNbrEntry 17 }
callCtlNbrAcceptCalls OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"number of calls from neighbor accepted since system reset."
::= { callCtlNbrEntry 18 }
callCtlNbrRefuseCalls OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"number of calls from neighbor refused since system reset."
::= { callCtlNbrEntry 19 }
callCtlNbrLastAttemptTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION DESCRIPTION
"sysUpTime of last call attempt." "It is conformant to implement this object as read-only."
::= { callCtlNbrEntry 20 }
callCtlNbrStatus OBJECT-TYPE OBJECT isdnBasicTblConnectionType
SYNTAX RowStatus MIN-ACCESS read-only
MAX-ACCESS read-create
STATUS current
DESCRIPTION DESCRIPTION
"Status of one row in this table." "It is conformant to implement this object as read-only."
::= { callCtlNbrEntry 21 }
callControlMibTrapPrefix OBJECT IDENTIFIER ::= { callControlMib 3 }
callControlMibTraps OBJECT IDENTIFIER ::= { callControlMibTrapPrefix 0 }
callCtlNbrCallInformation NOTIFICATION-TYPE OBJECT isdnSigTblLineTopology
OBJECTS { MIN-ACCESS read-only
callCtlNbrLogIf,
callCtlNbrName,
callCtlNbrAddress,
callCtlNbrLastDuration,
callCtlNbrClearReason,
callCtlNbrClearCode
}
STATUS current
DESCRIPTION DESCRIPTION
"This trap/inform is sent to the manager whenever "It is conformant to implement this object as read-only.
a successful call clears, or a failed call attempt For Primary Rate ISDN interfaces, this object must be
is determined to have ultimately failed. In the implemented as read-only and has to return the value of
event that call retry is active, then this is after pointToPoint(1)."
all retry attempts have failed. However, only one such
trap is sent in between successful call attempts;
subsequent call attempts result in no trap."
::= { callControlMibTraps 1 }
callControlMibConformance OBJECT IDENTIFIER ::=
{ callControlMib 4 }
callControlMibCompliances OBJECT IDENTIFIER ::=
{ callControlMibConformance 1 }
callControlMibGroups OBJECT IDENTIFIER ::=
{ callControlMibConformance 2 }
callControlMibCompliance MODULE-COMPLIANCE ::= { isdnMibCompliances 1 }
STATUS current
DESCRIPTION
"The compliance statement for entities which
implement the CALL CONTROL MIB"
MODULE -- this module
MANDATORY-GROUPS { callControlMibGroup }
::= { callControlMibCompliances 1 }
-- units of conformance -- units of conformance
callControlMibGroup OBJECT-GROUP isdnMibBasicRateGroup OBJECT-GROUP
OBJECTS { OBJECTS {
callCtlAcceptMode, isdnBasicTblIfType,
callCtlNbrIfType, isdnBasicTblConnectionType
callCtlNbrPhysIf,
callCtlNbrLogIf,
callCtlNbrName,
callCtlNbrAddress,
callCtlNbrInfoType,
callCtlNbrInfoRate,
callCtlNbrPermission,
callCtlNbrInactivityTimer,
callCtlNbrCallRetries,
callCtlNbrMaxDuration,
callCtlNbrLastDuration,
callCtlNbrClearReason,
callCtlNbrClearCode,
callCtlNbrSuccessCalls,
callCtlNbrFailCalls,
callCtlNbrAcceptCalls,
callCtlNbrRefuseCalls,
callCtlNbrLastAttemptTime,
callCtlNbrStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing the CALL CONTROL MIB
capability."
::= { callControlMibGroups 1 }
END
4.3. Call History MIB
CALL-HISTORY-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Integer32,
experimental
FROM SNMPv2-SMI
DisplayString,
TimeStamp
FROM SNMPv2-TC
MODULE-COMPLIANCE,
OBJECT-GROUP
FROM SNMPv2-CONF
InterfaceIndex
FROM IF-MIB;
callHistoryMib MODULE-IDENTITY
LAST-UPDATED "9506121200Z"
ORGANIZATION "IETF ISDN Working Group"
CONTACT-INFO
" Guenter Roeck
Postal: Conware GmbH
Killisfeldstrasse 64
76227 Karlsruhe
Germany
Tel: +49 721 9495 0
E-mail: roeck@conware.de"
DESCRIPTION
"The MIB module to describe and store the call
information of the managed device for
accounting purposes."
::= { experimental 97 }
callHistoryMibObjects OBJECT IDENTIFIER ::= { callHistoryMib 1 }
callHistory OBJECT IDENTIFIER ::= { callHistoryMibObjects 1 }
callHistoryTableMaxLength OBJECT-TYPE
SYNTAX INTEGER (0..10000)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The upper limit on the number of entries that the
callHistoryTable may contain. A value of 0
will prevent any history from being retained. When
this table is full, the oldest entry will be deleted
and the new one will be created."
::= { callHistory 1 }
callHistoryRetainTimer OBJECT-TYPE
SYNTAX INTEGER (0..10080) -- one week
UNITS "minutes"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The minimum amount of time that an callHistoryEntry
will be maintained before being deleted. A value of
0 will prevent any history from being retained, but
will not prevent callCompletion traps being generated."
::= { callHistory 2 }
callHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF CallHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing information about specific
calls to a specific destination."
::= { callHistory 3 }
callHistoryEntry OBJECT-TYPE
SYNTAX CallHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The information regarding a single Connection."
INDEX { callHistoryStartTime, callHistoryIndex }
::= { callHistoryTable 1 }
CallHistoryEntry ::=
SEQUENCE {
callHistoryStartTime TimeStamp,
callHistoryIndex Integer32,
callHistoryCallingNumber OCTET STRING,
callHistoryCalledNumber OCTET STRING,
callHistoryInterfaceNumber InterfaceIndex,
callHistoryDestinationAddress OCTET STRING,
callHistoryDestinationHostName DisplayString,
callHistoryCallDisconnectCause INTEGER,
callHistoryCallConnectTime TimeStamp,
callHistoryCallDisconnectTime TimeStamp,
callHistoryCallOrigin INTEGER,
callHistoryChargedUnits Integer32
} }
callHistoryStartTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of sysUpTime when this call history entry was
created. This will be useful for an NMS to retrieve all
calls after a specific time."
::= { callHistoryEntry 1 }
callHistoryIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index variable to access the CallHistoryEntry objects
of the callHistoryTable."
::= { callHistoryEntry 2 }
callHistoryCallingNumber OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The calling number for this call. If the number is
not available, then it will have a length of zero."
::= { callHistoryEntry 3 }
callHistoryCalledNumber OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number this call is connected to."
::= { callHistoryEntry 4 }
callHistoryInterfaceNumber OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the ifIndex value of the highest number "A collection of objects required for ISDN basic rate
of interface through which the call was made." physical interface configuration and statistics."
::= { callHistoryEntry 5 } ::= { isdnMibGroups 1 }
callHistoryDestinationAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address of the host this call is
connected to. Most devices/routers connected to
an interface have an address and this object will
store that address."
::= { callHistoryEntry 6 }
callHistoryDestinationHostName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name of the host this call is
connected to. Most devices/routers connected to
an interface have a name and this object will
store that name."
::= { callHistoryEntry 7 }
callHistoryCallDisconnectCause OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The network cause value associated with this call."
::= { callHistoryEntry 8 }
callHistoryCallConnectTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the call was connected.
[Editor's note:
Can we use the time since 01:01:70 here ?]
"
::= { callHistoryEntry 9 }
callHistoryCallDisconnectTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the call got disconnected.
For active calls, the value of this object will be zero."
::= { callHistoryEntry 10 }
callHistoryCallOrigin OBJECT-TYPE isdnMibSignallingGroup OBJECT-GROUP
SYNTAX INTEGER { OBJECTS {
outgoing(1), isdnSigTblPhysInterface,
incoming(2), isdnSigTblSignallingProtocol,
callback(3) isdnSigTblLineTopology,
isdnSigTblCalledAddress,
isdnSigTblCallingAddress,
isdnSigTblSubAddress,
isdnSigTblBchannelCount,
isdnSigTblOperStatus,
isdnSigStatsLapdPeerSabme,
isdnSigStatsLapdRecvdFrmr,
isdnSigStatsInCalls,
isdnSigStatsInConnected,
isdnSigStatsOutCalls,
isdnSigStatsOutConnected,
isdnSigStatsChargedUnits
} }
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The call origin." "A collection of objects required for ISDN signalling
::= { callHistoryEntry 11 } interface configuration and statistics."
::= { isdnMibGroups 2 }
callHistoryChargedUnits OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of charged units for this connection.
For incoming calls or if charging information is
not supported by the switch, the value of this object
will be zero."
::= { callHistoryEntry 12 }
callHistoryMibConformance OBJECT IDENTIFIER ::= { callHistoryMib 3 }
callHistoryMibCompliances OBJECT IDENTIFIER ::= { callHistoryMibConformance 1 }
callHistoryMibGroups OBJECT IDENTIFIER ::= { callHistoryMibConformance 2 }
callHistoryMibCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for entities which implement
the call History MIB"
MODULE -- this module
MANDATORY-GROUPS { callHistoryMibGroup }
::= { callHistoryMibCompliances 1 }
callHistoryMibGroup OBJECT-GROUP isdnMibBearerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
callHistoryTableMaxLength, isdnBearerCalledAddress,
callHistoryRetainTimer, isdnBearerCallingAddress,
callHistoryCallingNumber, isdnBearerSubAddress,
callHistoryCalledNumber, isdnBearerIfSpid,
callHistoryInterfaceNumber, isdnBearerOperStatus,
callHistoryDestinationAddress, isdnBearerStatsPeerAddress,
callHistoryDestinationHostName, isdnBearerStatsPeerSubAddress,
callHistoryCallDisconnectCause, isdnBearerStatsCallOrigin,
callHistoryCallConnectTime, isdnBearerStatsInfoType,
callHistoryCallDisconnectTime, isdnBearerStatsMultirate,
callHistoryCallOrigin, isdnBearerStatsCallSetupTime,
callHistoryChargedUnits isdnBearerStatsCallConnectTime,
isdnBearerStatsChargedUnits
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing the call History MIB capability." "A collection of objects required for ISDN bearer channel
::= { callHistoryMibGroups 1 } interface control and statistics."
::= { isdnMibGroups 3 }
END END
5. Acknowledgements 5. Acknowledgements
This document was produced by the ISDN MIB Working Group. Special This document was produced by the ISDN MIB Working Group. Special
thanks is due to all the people and companies supplying enterprise- thanks is due to the following persons:
specific MIB modules. Special thanks is also due to Fred Baker, for
helping with details concerning MIB design, and to Randy Roberts and Ed Alcoff
Kedar Madineni, who supplied a lot of helpful information concerning Fred Baker
switch types and other ISDN related information. Bibek A. Das
Ken Grigg
Jeffrey T. Johnson
Glenn Kime
Oliver Korfmacher
Kedar Madineni
Bill Miskovetz
David M. Piscitello
Lisa A. Phifer
Randy Roberts
Hascall H. Sharp
Robert Snyder
Ron Stoughton
James Watt
6. References 6. References
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
of Management Information for version 2 of the Simple Network of Management Information for version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes
LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
University, April 1993. University, April 1993.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information Base [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base
skipping to change at page 51, line 12 skipping to change at page 38, line 12
Phone: (49) 721 9495-0 Phone: (49) 721 9495-0
Email: roeck@conware.de Email: roeck@conware.de
Table of Contents Table of Contents
1 Introduction .................................................... 2 1 Introduction .................................................... 2
2 The SNMPv2 Network Management Framework ......................... 3 2 The SNMPv2 Network Management Framework ......................... 3
2.1 Object Definitions ............................................ 3 2.1 Object Definitions ............................................ 3
3 Overview ........................................................ 4 3 Overview ........................................................ 4
3.1 Structure of MIB .............................................. 4 3.1 Structure of MIB .............................................. 4
3.1.1 The ISDN MIB ................................................ 4 3.1.1 General Description ......................................... 4
3.1.2 The call control MIB ........................................ 4 3.2 Relationship to RFC 1573 ...................................... 5
3.1.3 The call history MIB ........................................ 5 3.2.1 Layering Model .............................................. 5
3.2 Relationship to RFC1573 ....................................... 5 3.2.2 ifTestTable ................................................. 7
3.2.1 Layering Model and Virtual Circuits ......................... 5 3.2.3 ifRcvAddressTable ........................................... 7
3.2.2 ifTestTable ................................................. 6 3.2.4 ifEntry ..................................................... 8
3.2.3 ifRcvAddressTable ........................................... 6 3.2.4.1 ifEntry for a Basic Rate hardware interface ............... 8
3.2.3.1 ifEntry for a D channel ................................... 7 3.2.4.2 ifEntry for a D channel (signalling channel) .............. 9
3.2.3.2 ifEntry for a B channel ................................... 8 3.2.4.3 ifEntry for a B channel (bearer channel) .................. 11
3.3 ISDN interface specific information ........................... 10 3.3 ISDN interface specific information ........................... 13
3.3.1 ISDN leased lines ........................................... 10 3.3.1 ISDN leased lines ........................................... 13
3.3.2 Hyperchannels ............................................... 10 3.3.2 Hyperchannels ............................................... 13
3.3.3 D channel backup and NFAS trunks ............................ 10 3.3.3 D channel backup and NFAS trunks ............................ 13
3.3.4 X.25 data transfer in D channel ............................. 11 3.3.4 X.25 data transfer in D channel ............................. 14
3.3.5 SPID handling ............................................... 11 3.3.5 SPID handling ............................................... 14
4 Definitions ..................................................... 12 3.3.6 Closed User Groups .......................................... 15
4.1 ISDN MIB ...................................................... 12 3.3.7 Provision of point-to-point line topology ................... 15
4.2 Call Control MIB .............................................. 31 3.3.8 Speech and audio bearer capability information elements ..... 15
4.3 Call History MIB .............................................. 41 4 Definitions ..................................................... 17
5 Acknowledgements ................................................ 48 5 Acknowledgements ................................................ 36
6 References ...................................................... 49 6 References ...................................................... 36
7 Security Considerations ......................................... 50 7 Security Considerations ......................................... 37
8 Author's Address ................................................ 50 8 Author's Address ................................................ 37
 End of changes. 177 change blocks. 
1235 lines changed or deleted 872 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/