RFC 2128 (rfc2128) - Page 3 of 34

Dial Control Management Information Base using SMIv2

RFC 2128                    Dial Control MIB                  March 1997


   o    Information to retain call history.

   The MIB, therefore, is structured into four groups.

   o    The dialCtlConfiguration group is used to specify general
        configuration information.

   o    The dialCtlPeer group is used to describe peer configuration
        and peer statistics.

   o    The callActive group is used to store active call information.

   o    The callHistory group is used to store call history information.
        These calls could be circuit switched or they could be virtual
        circuits. History of each and every call is stored, of successful
        calls as well as unsuccessful and rejected calls.  An entry will
        be created when a call is cleared.

2.2.  Relationship to the Interfaces MIB

   This section clarifies the relationship of this MIB to the Interfaces
   MIB [8].  Several areas of correlation are addressed in the following
   subsections.  The implementor is referred to the Interfaces MIB
   document in order to understand the general intent of these areas.

2.2.1.  Layering Model and Virtual Circuits

   On an occasional access channel, there are a number of peer systems
   that are permitted to call or be called, all of which need to be
   treated as active from a routing viewpoint, but most of which have no
   call in progress at any given time.

   On dialup interfaces, this is further complicated by the fact that
   calls to a given peer float from channel to channel. One cannot
   definitively say "I call this peer on that interface." It is
   necessary, therefore, to provide a mapping algorithm between the
   low-level interfaces, and the various logical interfaces supporting
   the peers.  This is solved by creating a logical interface (ifEntry)
   for each peer and a logical interface (ifEntry) for each low-level
   interface.  These are then correlated using the ifStackTable.

   The low-level interfaces are either physical interfaces, e.g.  modem
   interfaces, or logical interfaces, e.g. ISDN B channels, which then
   in turn are layered on top of physical ISDN interfaces.







Roeck                   Standards Track