+---------------------------------------------------------------------------+
! HST Saphir Adapter                                   File  READMEE.DOC    !
! Copyright (c) 1993-2002 HST High Soft Tech GmbH,     All rights reserved. !
+---------------------------------------------------------------------------+

Additional Information
SAPHIR-ISDN.PDF D2.0R03/04.2001

                          Saphir Driver Release 2.5

As of now the HST Saphir family of ISDN and ATM adapters is being supplied in
the new driver release 2.5. Various features for ATM adapters have been added
to the powerful software, protocol and interface architecture. The following
additional features are now available:

1. Configuration of the ATM adapter

    Start configuration of the Saphir adapter, choose an ATM adapter and click
    on the "Properties" button. You can set the following extra features
    through the "ATM Configuration" tab:


1.1. Profile Management

   Here you can select and activate, modify or delete one of the existing
   interface profiles, or create a new profile. You cannot modify or remove
   the ".default" profile.

   NOTE: You must restart the driver software to be able to read a new
   profile.


1.2. Adding or Modifying a Profile

   When you are adding a new interface profile, an existing profile can be set
   in the first box next to the name as a basis for the new one. In this way
   you only have to alter those values that differ from the basic profile. No
   entries are necessary if an existing profile is to be modified.


1.3. Details of Parameters to be Set

   Click on the "Next" button to move on to the next parameter window.


1.3.1 Controller Configuration

   Connection Table Size: (dec)
      Maximum number of connections supported by the hardware.

      You can set: 512, 1024, 4096, 8192, 16k (16384)

      Figures of > 4096 bytes require an ATM adapter of 2 Mbytes. The present
      configuration level of 512 Kbytes is optimum support for 4096
      connections.

      Default: 4096

   Path Resolution in Bits:
      Number of bits that are to be used to identify the virtual path.

      Examples:
      0 bits - no path resolution. The entire communication is expected to
         occur on one path. On this path all channels (connections) set in
         connection table size are available (4096).
      2 bits - four consecutive paths can be resolved. 1/4 of the channels
         (connections) set in connection table size are available for each
         path (1024).
      8 bits - all of the 256 possible paths can be resolved. 1/256 of the
         channels (connections) set in "Connection Table Size" are available
         for each path (16).

      You can set: 0, 1, 2, 8

      All settings > 2 are interpreted as 8.

      Default: 0

   Path Mask: (hex)
      The paths that can be resolved can be shifted by masking the path
      resolution. The mask is ORed with the evaluated bits.

      Example:
      Path resolution = 2 bits, path mask = F0 - this corresponds to a setting
         111100xx, where x are the bits that can be evaluated. The paths 240-
         243 are evaluated.

      You can set: 0 to FF

      The bits that can be evaluated must not be masked (set to 1).

      Default: 0

   Virtual Channel Mask: (hex)
      With this mask you can shift the channels in increments of 4096 on all
      paths.

      Example:
      5000 - the channels on all paths start with channel 20480.

      You can set: 0 to F000

      The lower 12 bits must not be masked (set to 1).

      Default: 0x0000

   Hardware CPS Resolution: (dec)
      Resolution of transmit hardware in cells per second. No lower bit rates
      can be generated and the bit rate can only be incremented in multiples
      of this setting. This also applies to the signaling channel.

      You can set: 38 to 59259 for Saphir /2025
                   38 to 353207 for Saphir /2155

      Default: 171 (approx. 64 kbit/s)


1.3.2 Path Configuration

   Path configuration is only needed for SVCs (ATM switched connections).
   Currently SVC is only supported on one path.

   Virtual Path: (dec)
      Path for this SVC configuration.

      You can set the paths: 0 to 255.

      Default: 0

   Signal Mode: (dec)
      Type of signaling procedure (signaling channel protocol).
      You can set the protocols: DSS2 (Q.2931)
                                 UNI 3.1
                                 UNI 4.0

      Only DSS2 is supported at present.

      Default: DSS2

   Signal VCI: (dec)
      Number of signaling channel.

      You can set the channels: 0 to 65535.

      Default: 5

   Signal Transfer Cap.: (dec)
      Transfer contract of signaling connection.

      You can set the contracts: SBR.1/QoS2 (nrt VBR.1)
                                 SBR.3/QoS3 (nrt VBR.3)

      Default: SBR.3/QoS3 (nrt VBR.3) for Saphir /2025
               SBR.1/QoS2 (nrt VBR.1) for Saphir /2155

   Signal Peak Cell Rate (PCR): (dec)
      Maximum speed of signaling channel.

      You can set: 38 to 59259 for Saphir /2025
                   38 to 353207 for Saphir /2155

      A setting of 0 uses 441 for Saphir /2025 and 18939 for Saphir /2155.

      NOTE: The setting must never be smaller than the set hardware CPS
      resolution.

      Default: 0

   Signal Sustainable Cell Rate: (dec)
      Minimum speed of signaling channel.

      You can set: 38 to 59259 for Saphir /2025
                   38 to 353207 for Saphir /2155

      A setting of 0 uses 38 for Saphir /2025 and 150 for Saphir /2155.

      Default: 0

   Signal Max. Burst Size: (dec)
      Number of consecutive cells in "peak cell rate" (PCR).

      You can set: 1 to 16777215 (2^24-1)

      A setting of 0 uses 10 for Saphir /2025 and 16 for Saphir /2155.

      Default: 0

   Signal Protocol Options: (dec)
      These flags for protocol options allow you to suppress protocol messages
      that are not supported in the current networks and can have a negative
      effect on network response.

      You can set: 0 - no suppression
                   1 - suppress narrowband IE
                   2 - suppress setup connection identifier IE
                   3 - suppress both IEs

      Default: 3

   Max. Simult. Connections: (dec)
      Maximum number of simultaneous user connections that can be signaled to
      the network.

      You can set: 1 to 16k (16384)

      With the setting 0, all connections set in the hardware configuration
      can be signaled.

      Default: 0

   User Max. Cells Per Second: (dec)
      Maximum total user speed on this path that can be signaled to the
      network.

      You can set: 38 to 59259 for Saphir /2025
                   38 to 353207 for Saphir /2155

      With the setting 0, the maximum interface speed (total hardware
      bandwidth) can be signaled.

      NOTE: The setting must never be smaller than the set hardware CPS
      resolution.

      Default: 0

   User Lowest VPI: (dec)
      Lowest user path that can be signaled to the network.

      You can set: 0 to 255

      Default: 0

   User Highest VPI: (dec)
      Highest user path that can be signaled to the network.

      You can set: 0 to 255

      Default: 0

   User Lowest VCI: (dec)
      Lowest user channel that can be signaled to the network.

      You can set: 0 to 65535

      Default: 32

   User Highest VCI: (dec)
      Highest user channel that can be signaled to the network.

      You can set: 0 to 65535

      Default: 4095


1.3.3 ATM Number Mapping

   In "ATM Number Mapping" you can set how an ISDN application tells CAPI the
   parameters necessary for setting up an ATM connection or identifying the
   connection by means of the directory number/destination address.

   Subaddress Digits: (dec)
      Number of places that are split from the CDPN (directory number/
      destination address) and transmitted by the CDPS (subaddress) (virtual
      MSN/DDI). If this value is set, the CDPN and CDPS are combined into a
      CDPN for incoming connections and transferred to the application. The
      purpose of this is to be able to assign several applications a virtual
      directory number differing from the ATM address so that they can be
      distinguished when dialing.

      You can set: 0 to 20

      Default: 2

   Forward Speed Digits: (dec)
      Number of places in the CDPN (directory number/destination address) that
      are used to increase transmit speed.

      You can set: 0 to 20

      Default: 3

   Forward Speed Factor: (dec)
      Factor by which the peak cell rate for the particular BCIP in BCIP
      mapping and the forward speed in the CDPN (directory number/destination
      address) are multiplied.

      You can set: 1 to 1000

      Default: 1

   Backward Speed Digits: (dec)
      Number of places in the CDPN (directory number/destination address) that
      are used to increase receive speed.

      You can set: 0 to 20

      Default: 3

   Backward Speed Factor: (dec)
      Factor by which the peak cell rate for the particular BCIP in BCIP
      mapping and the backward speed in the CDPN (directory number/destination
      address) are multiplied.

      You can set: 1 to 1000

      Default : 1


1.3.4 ATM BCIP Mapping

   In "ATM BCIP Mapping" you can remap several ATM services to required ISDN
   services so that they can be evaluated by ISDN applications. You can
   add, modify or delete mapping in the overview window. Such mapping is only
   used in ISDN applications and ignored in "genuine" ATM applications.

   The meaning of the individual boxes of the overview is as follows:
      No.                - number of mapping
      Flags              - determines functionality of mapping
                           1 - mapping narrowband CIP to BCIP (outgoing)
                           2 - mapping BCIP to narrowband CIP (incoming)
                           3 - both directions
      CIP                - CIP value according to CAPI 2.0
      AAL                - AAL value according to CAPI 2.0 broadband
                           extensions
      Bearer             - bearer value according to CAPI 2.0 broadband
                           extensions
      Traffic Forw. PCR  - forward PCR according to CAPI 2.0 broadband
                           extensions
      Traffic Backw. PCR - backward PCR according to CAPI 2.0 broadband
                           extensions

      If mapping is modified or added, you can make the following settings in
      the dialog window:

   Narrowband CIP to BCIP
      If this box is activated, the mapping applies to outgoing calls.

      Default: on

   BCIP to narrowband CIP
      If this box is activated, the mapping applies to incoming calls.

      Default: on

   Narrowband CIP Value: (dec)
      CIP value according to CAPI 2.0.

      You can set: 0 to 31
         Their meaning according to CAPI 2.0 is as follows:

         CIP   Meaning
         0     all
         1     speech
         2     unrestricted digital information
         3     restricted digital information
         4     3.1 kHz audio
         5     7 kHz audio
         6     video
         7     packet mode
         8     56 kbit/s rate adaptation
         9     unrestricted digital information with tones/announcements
         10    reserved
         11    reserved
         12    reserved
         13    reserved
         14    reserved
         15    reserved
         16    telephony
         17    facsimile group 2/3
         18    facsimile group 4 class 1
         19    teletex service basic and mixed mode and facsimile service
               group 4 classes II and III
         20    teletex service basic mode and processable mode
         21    teletex service basic mode
         22    international interworking for videotex
         23    telex
         24    message handling systems in accordance with X.400
         25    OSI application in accordance with X.200
         26    7 kHz telephony
         27    video telephony, first connection
         28    video telephony, second connection
         29    not defined
         30    not defined
         31    not defined

      Default: 2 (unrestricted digital information)

   AAL Value: (dec)
      AAL value according to CAPI 2.0 broadband extensions.

      You can set: 0 to 5
         Their meaning according to CAPI 2.0 broadband extensions is as
         follows:

         BCIP AAL value  Service
         0               no predefined profile
         1               AAL voice
         2               AAL 1
         3               AAL 2
         4               AAL 3/4
         5               AAL 5

      Default: 0

   Bearer Value: (dec)
      Bearer value according to CAPI 2.0 broadband extensions.

      You can set: 0 to 5
         Their meaning according to CAPI 2.0 broadband extensions is as
         follows:

         BCIP Bearer value  Service
         0                  no predefined profile
         1                  constant bit rate (CBR)
         2                  variable bit rate (VBR real time)
         3                  variable bit rate (VBR non-real time)
         4                  unspecified bit rate (UBR)
         5                  available bit rate (ABR)

      Default: 3 (VBR nrt)

   Traffic Forward PCR: (dec)
      Forward PCR according to CAPI 2.0 broadband extensions. This value can
      be multiplied by the factors in the directory number/destination
      address.

      You can set: 38 to 59259 for Saphir /2025
                   38 to 353207 for Saphir /2155

      NOTE: The setting must never be smaller than the set hardware CPS
      resolution.

      Default: 171

   Traffic Backward PCR: (dec)
      Backward PCR according to CAPI 2.0 broadband extensions. This value can
      be multiplied by the factors in the directory number/destination
      address.

      You can set: 38 to 59259 for Saphir /2025
                   38 to 353207 for Saphir /2155

      NOTE: The setting must never be smaller than the set hardware CPS
      resolution.

      Default: 171

2. Data compression V.42bis for X.75 SLP and V.120

   Immediately data compression V.42bis is available for the protocols X.75
   SLP and V.120 (b-channel, layer 2). The following operating modes and
   options are adjustable:

   Operating modes

      "Deactivated"
      Configures the Saphir ISDN adapter for the operation without V.42bis.

      "V.42bis activation by application"
      The Saphir ISDN adapter uses V.42bis only if applications request a
      protocol extended by V.42bis. The receiving station must be compatible
      for this.

      "Activated with X.75/V.120"
      The Saphir ISDN adapter uses V.42bis with all CAPI 2.0 applications,
      which use the protocols X.75 and V.120. The receiving station must be
      compatible for this.

   Options

      "Start in the compressed mode"
      In accordance to the actually V.42bis specification the data
      communication is always started in the transparent mode. Afterwards if
      necessary the enkoder switches into the compressed mode. In a session of
      the "CAPI Association Subworkgroup V.42bis" however it was decided to
      start in the compressed mode. This resolution was not taken up at
      present to the CAPI document "CAPI V 2.0 August 1997". By activation of
      this option the Saphir ISDN adapters are compatible to the not published
      standard of the Subworkgroup.

      "Special Flush at the end of block"
      At present the entries into the V.42bis coding table (dictionary) were
      flushed by some applications also in the transparent mode on the X.75
      block boundaries. In the transparent mode this process is not necessary.
      By activation of this option the Saphir ISDN adapters are additionally
      also compatible to these applications.

3.  New T.30 protocol for FAX

    Beginning immediately, all driver versions (except DOS driver without DPMS
    support) will support the T.30 B channel protocol starting at release 2.2
    (Revision 06). This enables FAX software, such as WinFax Pro V 8.0, to be
    used on all Saphir ISDN adapters. To do so, the FAX software must merely
    set itself up on CAPI 2.0. At present, the Send function runs at 9600 baud
    and the Receive function at 4800. This also integrates all FAX protocols
    in the driver's software - no extra hardware is necessary. At a later
    point in time, higher speeds of up to 14,400 baud can be easily achieved
    by means of software updates. FAX still continues to be supported on all
    available B channels simultaneously, thus enabling sending and receiving
    at the same time, for instance. Required for the use of the B channel
    protocol  T.30 is a Pentium at least.

4.  OS/2 WARP 4 support

5.  Novell IntranetWare support for ISA version

6.  Windows NT 4.0 support

7.  Removal/Insertion support for Advanced Power Management (APM) under
    Windows 95 for PCMCIA version

8.  New 32 Bit CAPI 2.0 DLL for Windows 95 (CAPI2032.DLL)

9.  New B2 protocol V.120

10. New feature for B1 protocol V.110 asynchronous with RFC1662 for
    synchronous/asynchronous conversion, e.g. for access to V.110 terminal
    adapter

11. Multi TEI for simultaneous access to several X.25 providers (via X.31)

12. Support of dial-in as well as permanent connections for X.31 (SVCs/PVCs)

13. Support of permanent D64S connections

14. Support of internal cross-links (point-to-point) according to Q.SIG;
    particularly for Siemens HiCom with CoreNet Q.SIG extensions

15. EAZ mapper for CAPI 1.1 to Q.931 (DSS-1/5ESS/NI1)

    Command:
        /e<Controller>:<EAZ-Value>=<Calling-Party-Number>
        [*<Calling-Party-Subaddress>]

    INI Files:
        [HST_ISDN_ADAPTER_01]
        EAZ<EAZ-Value>=<Calling-Party-Number>[*<Calling-Party-Subaddress>]

    NT-Registry:
        Key:             Parameters/Adapter01/EAZ<EAZ-Value>
        Value (REG_SZ):  <Calling-Party-Number>[*<Calling-Party-Subaddress>]

    <Controller>
        The controller number valid for the mapping 0..n n=MaxAdapter

    <EAZ-Value>
        The CAPI 1.1 EAZ value 0..9 to be treated

    <Calling-Party-Number>
        20 characters IA5 character set

    <Calling-Party-Subaddress>
        20 characters IA5 character set

    Examples:
        EAZ0=
            (default 'Calling-Party-Number' "1" and no
            'Calling-Party-Subaddress')
        EAZ1=*
            (no 'Calling-Party-Number' and no
            'Calling-Party-Subaddressinfo elements')
        EAZ2=12345
            ('Calling-Party-Number' "12345" and no
            'Calling-Party-Subaddress')
        EAZ3=12345*67890
            ('Calling-Party-Number' "12345" and
            'Calling-Party-Subaddress' "67890")

    The number "empty" specifies an information element consisting only of
    one header.

16. New general purpose mapping for own telephone number via new driver
    parameter for Q.931 protocols (DSS-1, NI1 u. 5ESS)

    Command:
        /am<Controller>:<Pre-Number>[=<Post-Number>]

    INI Files:
        [HST_ISDN_ADAPTER_01]
        MAP<Map-Value>=<Pre-Number>[=<Post-Number>]

    NT-Registry:
        Key:             Parameters/Adapter01/MAP<Map-Value>
        Value (REG_SZ):  <Pre-Number>[=<Post-Number>]

    <Controller>
        The controller number valid for the mapping 0..n n=MaxAdapter

    <Map-Value>
        A consecutive number for the mapping 0..9

    <Pre-Number>
        Number before mapping, 20 characters IA5 character set

    <Post-Number>
        Number after mapping, 20 characters IA5 character set

    Examples:
        MAP0=12345=67890
            (application "12345" net "67890")
        MAP1=12345=
            (application "12345" net "")
        MAP2==67890
            (application "" net "67890")

    The number "empty" specifies an information element consisting only of
    one header.

17. Multi-SPID configuration for US protocols 5ESS (AT&T) and NI1 (Bellcore)

    The SPID configuration for AT&T 5ESS and Bellcore NI1 has been drastically
    extended.

    For DOS,DPMS,OS/2 and NetWare:
        /xs<SPID-Value>[,<Controller>][,<Num-BCH>][,<Service>][,<Fixed-BCH>]
        [,<CGPN>]

    For Windows 3.X and Windows 95 native VxD:
        In [HST_ISDN_ADAPTER] section of SYSTEM.INI SPID1 to SPID8 is
        inserted.

        SPID1=<SPID-Value>[,<Controller>][,<Num-BCH>][,<Service>]
        [,<Fixed-BCH>][,<CGPN>]

    For Windows NT:
        In "Parameters" subkey registry the keys "SPID1" to "SPID8"  inserted
        as REG_SZ.

        SPID1=<SPID-Value>[,<Controller>][,<Num-BCH>][,<Service>]
        [,<Fixed-BCH>][,<CGPN>]

    <SPID-Value>
        SPID character chain for up to 20 characters.

    <Controller>
        The valid controller number for the SPID. Numbering starts with 1
        (CAPI 2.0 style). A value of 0 allocates the SPID to all controllers.
        default : the number of the configuration is the number of the
                  controller.

    <Num-BCH>
        Number of B-channels supported by the SPID.
        default : 2

    <Service>
        The services supported by the SPID
            "speech"                                  => 1
            "unrestricted digital information / UDI"  => 2
            "restricted digital information / RDI"    => 4
            "3.1 kHz audio"                           => 8
            "7 kHz audio"                             => 16
            "video"                                   => 32

            For combinations, the values are summed up
            default : 63 (all services)

    <Fixed-BCH>
        A fixed B channel valid for the SPID (1 or 2 for a S0 connection)
        A value of 0 releases the SPID for all B channels
        default : 0

    <CGPN>
        Your own MSN or DDI valid for the SPID
        default : empty

18. Driver parameters can now also be configured for DOS and OS/2 via the
    INI-File (SAPHIR.INI)

    As from now, an INI file named SAPHIR.INI can be used for the
    parameterization of drivers, in parallel with the command parameters.
    The structure is 100% compatible to the structure of the HST sections of
    the SYSTEM.INI in Windows. The names of the files can be changed with the
    parameter /f<Filename>.

19. Responder integrated in all drivers for HST Communication Driver
    Maintenance System (CDMS) for local and remote ISDN- and X.31 protocol
    recording and evaluation

    The multi-session CDMS master software under Windows 95/NT for the
    evaluation of the ISDN- and X.31 protocol recordings created by the
    integrated CDMS responder are currently being prepared and can soon be
    purchased via janus HST Marketing GmbH.
