111111111111111111111111111111111111111111111111111111111111111111  
<trace_profile>
You can select trace profile dependent on the type of your
application and problem:
+ Standard trace level (default)
  Trace D-channel, Diva adapter state, call events, fax and modem
  events, CAPI messages (dumps only first 256 bytes of data), and
  TTY trace messages.
  Used by investigation of general problem (outgoing call failed,
  application not able to receive any call).
+ Standard trace level + B-channel
  Same as above plus B-channel data.
+ Diva TTY interface
  Trace D-channel, Diva adapter state, call events, fax and modem
  events, and TTY trace messages. Used by investigation of
  problems at application level.
+ Diva TTY interface + B-channel
  Same as above plus B-channel data.
  Used by investigation of Fax/PIAFS related problems.
+ Diva TTY interface, detailed
  Same as above plus Diva adapter host interface trace messages.
+ CAPI2.0 interface
  Trace D-channel, Diva adapter state, call events, fax and modem
  events, and CAPI messages (dumps only first 256 bytes of data).
  Used by investigation of problem at application level (i.e. if
  CAPI application fails to receive from CAPI interface requested
  functionality)
+ CAPI2.0 interface + B-channel
  Same as above plus B-channel data.
  Used by investigation of Fax/Voice related problems.
+ CAPI2.0 interface + data
  Same as above, but dumps entire context of DATA_B3 messages
+ CAPI2.0 interface, detailed
  Same as above plus Diva adapter host interface trace messages.
+ Audio Tap (Fax, Modem)
  Trace Audio data, B-channel data, Diva adapter state, call
  events, fax and modem events.
  Used by investigation of compatibility problems with 3th party
  modem/fax equipment.
<trace_profile/>

<trace_stop>
You cas stop trace daemon and compress binary trace file, if
necessary. The trace information will be stored in the file:
'/var/log/ditrace.bin'     - plain binary file
'/var/log/ditrace.bin.bz2' - if compressed by 'bzip2'
'/var/log/ditrace.bin.gz'  - if compressed by 'gzip'

You can use 'divactrl ditrace' to read plain binary trace file:
'divactrl ditrace -i ditrace.bin'        - read all trace records
'divactrl ditrace -i ditrace.bin -d X'   - read trace records
                                           related to driver
                                           number 'X'
The option '-UseMlogTime' allows you to select 'adapter time'
instead of local time for time stamp of Diva adapter relaled
trace records.
<trace_stop/>

<system_mode>
Allows to select required application scenario:
+ RAS/Wireless server (TTY interface, CO/Analog V.90 Modem (56000,
  V.42bis, MNP5), V.110, digital RAS, V.120 and X.75 w. V.42bis,
  call type detection, ASYNC/SYNC PPP conversion, Fax)
+ RAS/Wireless PIAFS server (TTY interface, misc. PIAFS options,
  PIAFS1.0, PIAFS2.0, PIAFS2.1, PIAFS with China extensions)
+ Fax/Voice system (TTY interface, misc. fax options,
  Fax up to V.34 (33600) with ECM, MR, MMR T.6, FAX CLASS 1 and 2)
+ Unified messaging/Media Gateway system (CAPI2.0 interface,
  Fax up to V.34 (33600) with ECM, MR, MMR T.6, G.168 EC, VoIP,
  Line Interconnect, DTMF/MF, Supplementary Services, Avalog Modem,
  V.110, PIAFS, V.120, X.75, V.42bis, X.25, T.70/T.90NL
+ Universal system (CAPI2.0 and TTY interfaces, allows access to
  all features provided by Diva Adapter)
<system_mode/>

<tty_cl2_opt>
Allows to override selected by application FAX CLASS 2 options:
+ Always use ECM, MR, MMR T.6 if supported by opposite side
  Diva Adapter will handle conversion between MR/MMR (MMR/MR)
  compressed data transparent to application
+ Always use V.34 (33600) Fax if supported by opposite side
  V.34 connections are handled transparent to application and
  indicated to application as V.17 (14400) connections
<tty_cl2_opt/>

<select_diva_adapter>
You can choose between:
+ Leave Diva configuration wizard and store changes (updates
  Diva startup/configuration script)
+ Leave Diva configuration wizard and discard all changes
+ Select one of the detected Diva adapters and continue with
  adapter configuration.

At any point of adapter configuration you can select 'Cancel'
button that will return you to begin of Adapter configuration.
This operation will preserve all configuration changes you made
for this adapter and provide for unchanged configuration
parameters default values.
<select_diva_adapter/>

<card_startup_opt>
Controls features of the adapter startup/configuration script
(/usr/share/eicon/divas_cfg.rc):
+ By default adapter startup script checks serial numbers of
  installed Diva adapters. In case you plan to 'clone' system
  configuration (i.e. use same 'divas_cfg.rc' file on different
  hosts with same hardware configuration) you should de-activate
  this option
+ Allows you to view trace/debug messages issued by Diva adapter
  control and configuration utility (divactrl) at adapter
  configuration time
<card_startup_opt/>

<adapter_te_nt_mode>
Select whether you want to operate your Diva Server adapter as
terminal equipment (TE) or as network termination (NT).
Normally, Diva Server adapters are operated as terminal equipment.
+ As terminal equipment they derive their timing from the signal
  received from the NT, e.g. PSTN or PBX, and use this derived
  timing to synchronize their transmitted signal. 
+ If you use the Diva Server adapter as network termination, it
  generates the timing from which the terminal equipment derives
  its timing and synchronization.

Using the Diva Server adapter as NT might be useful in the
following scenarios:
  - Diva Server adapters in network termination mode serve as
    master in PBX networks that use the Q-Sig protocol. This is
    the main field of application.
  - Two Diva Server adapters are operated back-to-back.
    Back-to-back operation allows to install network-independent
    test scenarios for trade shows and to run stress and long-time
    tests for application software.
  - Diva Server adapters are used as test or measuring device by
    running test scripts with third-party software that supports
    network emulation.
For information on properly connecting Diva Server adapters acting
as an NT to the respective TE, see the printed guide that came
with your adapter.
<adapter_te_nt_mode/>

<adapter_switch_type>
Please select your ISDN switch type (D-channel protocol), as
provided by your ISDN service provider.
<adapter_switch_type/>

<adapter_nt2>
Please specify whether you use a direct dialing in interface.
A direct dialing in interface provides you with an ISDN line with
a basic phone number that is able to accept any extension digits
and to pass them to the ISDN applications.
If you select 'Yes', you will need to enter the direct inward
dialing number length.
<adapter_nt2/>

<adapter_did_len>
Please select direct inward dialing number length.
This value specifies the number of digits that are used to
determine the called party number. Commonly, the number length is
set to '4' to match the length of telephone extensions generated
by PBX systems.
<adapter_did_len/>

<adapter_layer1_framing>
The 'National Default' setting automatically sets the correct
Layer 1 framing for the selected switch type.
In case you use Diva adapter in the non standard environment it is
possible that you may want to use different Layer 1 framing then
the national default in accordance with selected signalling
protocol.
You can select between 'Doubleframing (no CRC4) that is widely
used in the North American and Benelux area and
Multiframing (CRC4) that is widely used in the European Area.

INFO     :  You can use Led's on the backplate of the card or
            command 'divactrl mantool -rState\\Layer1' in order
            to determine the trunk state.
ATTENTION:  It is not allowed to use 'Autodetect' on the public
            trunk.
ATTENTION:  In case you select the wrong Layer 1 framing on the
            Public thrunk it can cause penalties or discontinued
            line service some countries . If you plan to connect
            card to the public trunk and are not sure, please
            always contact your trunk provider first to ensure
            that you use correct parameters
<adapter_layer1_framing/>

<adapter_companding_type>
The 'National Default' setting automatically sets the correct
voice coding for the selected switch type.
In case you implement the Diva cards in a non-standard
environment, for example if you use QSIG protocol in the
North American area, it is necessary to explicitly manually set
the standard used to process Voice Data.
You can select between G.711 'A-Law' and 'u-Law' coding.
Please select 'National Default' if you are not sure.
If the wrong value selected then this will cause poor voice
quality, poor Fax G3 performance and low speed of modem
connections.
<adapter_companding_type/>


<adapter_hunt_group>
ATTENTION: Please select only if you have configured your PABX for
           this operation (e.g. Hunt Group operation Mode).

When you select hunt group operation, dynamic layer 1 management 
(dynamic_l1_down) is activated. Dynamic layer 1 management effects
the following behaviour of your Diva Server adapter:
Layer 1 of the Diva Server adapter is switched to high-impedance
state until the application sends a LISTEN request to it. 
As long as the Diva Server adapter is in high-impedance state, the
PBX that manages the Hunt Group considers the line of the
Diva Server adapter as not being connected and thus, does not
deliver calls to it.
When the Diva Server adapter receives the first LISTEN request
from an application, i.e. the application is ready to receive
calls, it switches to normal operation mode. The PBX is signalled
that the adapter is attached to the port and that calls can be
routed to this port. If the application removes all LISTEN requests
from the Diva Server adapter (application terminated or application
failure), the Diva Server adapter switches back to high-impedance
state. Thus, the port is no longer available to the PBX.
This mechanism ensures that no calls are lost.
<adapter_hunt_group/>

<adapter_fractional_line>
Specify whether you are using a full E1/T1 line (i.e. 30/23/24
B-channels) or whether you ordered a fractional line.
Standard  : All B-channels in the trunk should be available for
            data transfer.
Fractional: This option should be selected in case you use your
            Diva adapter on a Fractional trunk line, (i.e. not all
            B-channels in the trunk are available for data
            transfer).
If you select 'Fractional' you must specify the number of lowest
available B-channel number,(i.e. channel number where B-channel
Fraction begins).
Your trunk provider can supply the required information.

INFO: Your Diva adapter should be populated with amount of DSP's
      equal to or greater than the amount of available fractional
      B-channels you plan to use.
<adapter_fractional_line/>

<adapter_fractional_lo_ch>
Please specify the number of lowest available B-channel number,
(i.e. channel number where B-channel Fraction begins).
Your trunk provider can supply the required information.
<adapter_fractional_lo_ch/>

<adapter_choose_tei>
Please select the TEI value for your line. The TEI value specifies
the Terminal Endpoint Identifier that is assigned to the ISDN
line.
Leave the standard value (0) unless your service provider
specifies a different TEI for your connections.
Please note that if an incorrect TEI value is selected, then
Layer 2 on the D-channel will fail to establish a connection, and
as result, call attempts will fail and report Layer 2 error.

INFO: You can use Led's on the backplate of the card or use the
      command 'divactrl mantool -rState\\Layer2 No1' in order to
      determine the trunk state.
<adapter_choose_tei/>

<adapter_in_band_tones>
Normally, local tones are generated by the ISDN equipment. If the
ISDN equipment is not able to generate in-band alert or busy
tones, the Diva adapter can generate these tones to signal to the
remote station if an application is ready to accept a call or if
it is busy etc.
<adapter_in_band_tones/>

<capi_go>
Group optimization allows the adapter to create application
groups depending on the LISTEN parameters that the application
passes to the adapter. Every incoming call will be distributed on
a per group basis instead of a per application basis. Thus, only
one idle application in each group and not every idle application
that matches the incoming call will receive the indication about
an incoming call.
This feature is useful if you start multiple instances of the same 
application (for example multiple instances of a fax server or
voice gateway application) or if your CAPI registers multiple CAPI 
applications that use the same LISTEN parameters. 
<capi_go/>

<adapter_fax_speed_limit>
Global fax options allow you to override parameters passed by fax
application to the card and control parameters running on the
card's T.30 protocols.
This provides a high level of flexibility, especially if the fax
application does not provide the all the required parameters.

NOTE: Normally, you do not need to limit the fax speed because the
      Diva Server adapter automatically negotiates the appropriate
      speed.
<adapter_fax_speed_limit/>

<adapter_fax_t30_options>
Global fax options allow you to override parameters passed by fax
application to the card and control parameters running on the
card's T.30 protocols.
This provides a high level of flexibility, especially if the fax
application does not provide the all the required parameters.

NOTE: Normally, you do not need to change the fax options because
      the Diva Server adapter automatically negotiates the
      appropriate setting.

+ Disable fine resolution
  Disables transmission of fax messages with High resolution
+ Disable Error Correction Mode (ECM):
  Disables transmission of fax messages using ECM (Error
  Correction Mode)
+ Use ECM frame length of 64 bytes
  Forces usage of HDLC frames with a maximum length of 64 Bytes if
  transmitting fax messages using ECM (Error Correction Mode).
+ Disable 2D fax document compression 
  Disables usage of 2D fax document compression. Additionally,
  this option disables automatic (transparent to application) fax
  document compression that is provided by the card in order to
  increase effective transfer speed of fax messages.
+ Disable T.6 fax document compression
  Disables usage of T.6 fax document compression. Additionally,
  this option disables automatic (transparent to application) fax
  document compression that is provided by the card in order to
  increase effective transfer speed of fax messages.
+ Disable uncompressed T.6 fax document lines 
  It is possible that compression of the fax document line gives,
  as a result, one line that is longer than an uncompressed
  original. T.6 protocol allows you to reduce fax transmission
  time by transmitting of similar lines without compression. This
  option disables this optimization.
+ Refuse incoming polling requests
  Disables incoming polling requests
+ Hide 'total pages' information in fax message
  Hides 'total pages' information field in the fax message.
+ Hide 'head line' information in fax message
  Hides 'headline' information field in the fax messages.
+ Hide 'page info' information in fax message
  Hides 'page info' (i.e. message head) field in the fax messages.
+ Disable fallback to lower speed on failure
  'Feature fallback' is used to prevent excessive resending of fax
   documents if working over the poor quality lines. The Diva card
   saves internally the Fax ID of the last peer and the results of
   the fax transmission from this peer. In case results of the
   last fax transmission were negative, and application starts
   message re-transmission Diva Card will detect this and
   'step down' (i.e. fallback) to a lower transfer speed. This
   setting allows you to disable this feature.
<adapter_fax_t30_options/>

<adapter_rbs_trunk_mode>
The trunk mode must correspond to the trunk mode of your switch. 
  
NOTE: The trunk modes are defined in the TIA/EIA-464
      specification.  WinkStart is also defined in AT&T TR41458.
<adapter_rbs_trunk_mode/>

<adapter_rbs_office>
You can select between following types of signaling:
+ FSX: Foreign Exchange Subscriber. What the user side sends
       to FXO.
+ FXO: Foreign Exchange Office. What the network side sends
       to FXS.
+ SAS: Special Access Subscrieber. What the used side sends
       to SAO.
+ SAO: Special Access Office. What the network side sends to SAS.

A foreign exchange is remotely located exchange that the
subscrieber is connected too. This normally will be a central
office.
Special access is dedicated line through the central office
connected directly to a long distance carrier.
<adapter_rbs_office/>

<adapter_rbs_answer_supervision>
Normally centrall office side provides digital signal that
indicates end of connection estabishement phase (i.e. Answer
Supervision).
If centrall office equipment does not provide Answer Supervision
then in band tones (BUSY, ALERT, ...) will be used to determine
the call state.

In case you fail to create outgoing connections, but opposite
side receives the call, it is possible that central office does
not provide Answer Supervision, and you should turn this feature
off.
<adapter_rbs_answer_supervision/>

<adapter_rbs_dial_type>
The dial type (i.e. way how dialing information is transferred
over the trunk) must correspond to the dial type of your
switch.
Most analog telephones use dual-tone multifrequency signaling.
<adapter_rbs_dial_type/>

<adapter_rbs_bc>
RBS protocol does not provide information about call type
(i.e. Bearer Capabilities). For this reason it is necessary to
configure call type that the card will indicate to the
applications in case of incomming call.
+ Select 'Voice/analog' if your application handles voice calls,
  fax group 3 calls, and analog modem calls.
+ Select 'Data/digital' if your application handles digital calls,
  e.g. digital RAS.
<adapter_rbs_bc/>

<adapter_rbs_glare_resolve>
If you select 'No', your server will not abort its call attempt
to resolve the call collision but will wait for the other party to
do so.  It will then start sending address digits.
If you select 'Yes', your server will stop dialing and return to
on-hook status. It will prepare to receive address digits and the
call attempt from the other end of the line can be completed.
<adapter_rbs_glare_resolve/>

<adapter_rbs_answer_timeout>
Specify the time interval, in seconds, after which the adapter
hangs up if the remote station does not answer a call.
Default setting is 120 seconds.
<adapter_rbs_answer_timeout/>

<adapter_rbs_send_dialing_digits>
In cases where the trunk uses 'Pulse Dialing', it is possible that
the called party accepts call immediatelly after an off hook
condition, i.e. it is not necessary to send dialing information
over the trunk.
+ If you select 'Yes' then dialing information will be sent over
  the trunk.
+ If you select 'No' then dialing information will not be sent
  over the trunk. This is the default setting.
<adapter_rbs_send_dialing_digits/>

<adapter_rbs_received_digit_timeout>
Select the time interval, in seconds, that may pass between the
incoming dialed digits. If the specified interval is exceeded, the
dialed number is assumed to be complete and the call is forwarded
to the application. 
The default setting is 10 seconds.
<adapter_rbs_received_digit_timeout/>

<adapter_bri_rev_1_optimization>
You can optimize 'Diva Server BRI-2M PCI' adapter configuration,
dependent on type of your application:
+ Select 'No optimization' if you plan to use basig adapter
  RAS/Fax/Voice features like Analog Modem (V.90, V42bis),
  V.110, V.120, X.75, Digital RAS, Fax (14400, ECM, MR, MMR, T.6),
  DTMF/MF/Tone processing.
+ Select 'Optimized for RAS' if you use your adapter for RAS
  applications and use enhanced RAS features, such as V.90
  Analog Modem (56000, V.42bis), V.110, V.120, X.75, Digital RAS.
+ Select 'Optimized for fax/voice/unified messaging' if you
  implement fax, voice, or unified-messaging applications, to be
  able to use enhanced unified messaging features like,
  Fax (14400, ECM, MR, MMR, T.6), enhanced voice processing,
  line interconnect, enhanced DTMF/MF/Tone processing.
<adapter_bri_rev_1_optimization/>

<adapter_layer2_activation_policy>
+ If you select 'On Demand' the D-channel layer 2 connection is
  activated to establish the B-channel data connection and is
  deactivated as soon as the B-channel data connection releases.
+ If you leave the default setting 'Deactivation only by NT side',
  the D-channel layer 2 connection is activated when a B-channel
  data connection is established for the first time and is kept
  active afterwards until disconnection is requested by the
  NT (opposite) side.
+ The setting 'Always active' effects that the D-channel layer 2
  connection is activated as soon as the ISDN protocol is loaded
  and is kept active afterwards.
   
NOTE: The American protocols 'NI', '5ESS', 'EWSD Siemens', and
      '5ESS NI' require the setting 'Always active'.
<adapter_layer2_activation_policy/>

<adapter_trunk_operation_mode>
Specify the type of ISDN interface to which your Diva Server
adapter is connected:
to:
+ Point to Multipoint (default)
  Allows multiple terminal devices (TEs) to be connected to the
  BRI line.
+ Only one TE can be connected to the BRI line. The TEI value must
  be set and the source of local tones must be specified in the
  following screens.

INFO: If an incorrect TEI value is selected, then Layer 2 on the
      D-channel will fail to establish a connection, and as
      result, call attempts will fail and report Layer 2 error.
      You can use Led's on the backplate of the card or use the
      command 'divactrl mantool -rState\\Layer2 No1' in order to
      determine the trunk state.
<adapter_trunk_operation_mode/>

<support_cause>
Diva support wizard allows you to capture relevant for your
support request information.
Please select type of the problem, and follow the istructions.
+ Driver start failed
  Diva support wizard will try to load device drivers and to start
  one of Diva adapters.
+ Kernel crash (Oops, lockup) after driver start
  Diva support wizard will load all device drivers, start all
  adapters and test Eicon Diva TTY and CAPI inerfaces.
+ No Eicon Diva adapter detected
  Diva support wizard will load Eicon Diva drivers and start all
  available adapters.
+ Eicon Diva adapter start failed
  Diva support wizard will load Eicon Diva drivers and start all
  available adapters.
+ Eicon Diva driver load failed (space expensive)
  Please select this option if you are not sure about the cause on
  the system failure (system crash, driver can't be loaded), only
  if you have general problem to activate support for Eicon Diva
  adapters on your system. Diva support wizard will capture all
  necessary information, necessary to reproduce your environment
  on the other hardware. This option requires about 20 MBbyte of
  the free disk space.
<support_cause/>

<qsig_charge_disabled>
If your PBX can not handle Charge Request then you can turn
this feature off.

PBX that can want this option:
 - MD110
<qsig_charge_disabled/>

<qsig_charge_location>
Diva Server adapter will issue Charge Request immediatelly after
CONNECT message.
If your PBX fails to handle Charge Request in this state then it
is possible to send Charge Request in SETUP message.

PBX that can want this option:
 - Hicom 300, ECMAV1 QSIG dialect
<qsig_charge_location/>

<qsig_charge_type>
Please select Charge Request types that are supported by your PBX
(by default all request types are used by Diva Server adapter).

ATTENTION:
  Please change this option only in case of problems or if you
  have informations that your PBX can't handle specific
  Charge Request type.
<qsig_charge_type/>


