Sophie: divactrl-2.1-1mdv2008.1 x86

divactrl-2.1-1mdv2008.1.x86_64.rpm

--------------------------------------------------------------------------------
Diva Server for Linux - Reference Guide
--------------------------------------------------------------------------------

Third Edition (May 2001) 206-324-03

Diva ISDN is a registered trademark of Eicon Networks Corporation.
Linux is a registered trademark of Linus Torvalds.
All other brand and product names are trademarks or registered trademarks
of their respective owners.
Changes are periodically made to the information herein; these changes will be
incorporated into new editions of the publication. Eicon Networks may make
improvements and/or changes in the products and/or programs described in this
publication at any time.
For information on contacting Customer Services see the printed guide that came
with your adapter.
Eicon Networks may use or distribute whatever information you supply in any
way it believes appropriate without incurring any obligations to you.
Copyright (c) 2000-2001 Eicon Networks Corporation. All rights reserved,
including those to reproduce this publication or parts thereof in any form
without permission in writing from Eicon Networks.

--------------------------------------------------------------------------------
Contents
--------------------------------------------------------------------------------
About this Online Guide
How to use this online guide
Structure of this guide
About Diva Server for Linux
Open Diva and Diva Server for Linux
Differences between Open Diva and Diva Server for Linux
General features
General product features
Fax and voice features
Eicon ISDN Serial Driver
Common ISDN API (CAPI) Version 2.0 Support
Supported hardware
System Requirements
Installation and Configuration
Software Installation using RPM
Configuring Diva Server for Linux
Physical and logical adapter number
'/proc' file system
Configuring Diva Server PRI adapters
Advanced configuration - Diva Server PRI adapters
Configuring Diva Server BRI and 4BRI adapters
Advanced configuration - Diva Server BRI and 4BRI adapters
Configuring Diva Client Adapters
Advanced configuration - Diva Client adapters
Loading the Diva Server modules
Manual adapter configuration
Special configuration features
Testing adapter functionality and connectivity
Configuring the Diva Server TTY Serial ports
General AT commands
AT FAX commands (excerpt of complete list)
Supported TTY profiles
ESCAPE sequence
AT command responses
TTY control interface (/dev/ttydsctrl and ttydsctrl utility)
Setting up a Linux PPP (RAS) server
Uninstalling Diva Server for Linux
Unloading the Diva Server modules
Uninstalling the Diva Server package
Troubleshooting
XLOG trace and debug utility
Core dump generation utility
MLOG trace and debug utility
DCHANNEL trace and d-channel health monitoring utility
Trouble-shooting procedure
'tty_test' utility
Building a back-to-back cable for PRI adapters
Management Interface
Features

--------------------------------------------------------------------------------
Structure of this guide
--------------------------------------------------------------------------------
This guide provides a detailed description of how to install and configure
Diva Server for Linux, and how to troubleshoot your ISDN connection.

This guide is structured as follows:

- About Diva Server for Linux
Diva Server for Linux features, supported hardware, and system
requirements.
- Installation and Configuration
Installation and configuration of Diva Server for Linux with Diva
Server PRI and Diva Server BRI adapters.
- Completing the Installation
Loading Diva Server modules: Eicon ISDN Serial Driver (analog, fax,
V.110 and V.120 capabilities) and CAPI support and testing adapter
function and connection.
- Configuring the Diva Server TTY Serial ports
AT commands to configure the Diva Server TTY Serial ports, setting up
a Linux server to accept digital or analog connections.
- Uninstalling Diva Server for Linux
Uninstalling the Diva Server for Linux software.
- Troubleshooting
ISDN trace utility and customer support procedure.
- Management interface description
Directories and variables that can be read, written, or used to generate
events and to control adapter status and configuration.
- Features
Overview of the functions provided by the various interfaces.

--------------------------------------------------------------------------------
About Diva Server for Linux
--------------------------------------------------------------------------------
Diva Server for Linux enables you to use your Eicon Diva Server adapter with
Linux, providing analog, digital, and fax modem emulation over TTY, a CAPI 2.0
interface for ISDN-based applications, an ISDN Direct Interface (IDI) for
access to the management interface, and B- and D-channel tracing.

--------------------------------------------------------------------------------
Open Diva and Diva Server for Linux
--------------------------------------------------------------------------------
'Open Diva' is the name of the freely available source code of:
- DIDD driver
- XDI driver for Diva Server adapters
- CAPI2.0 driver
- User Mode IDI driver
- Card configuration, control and management interface access utility
- Diva configuration wizard (shell scripts)

and on request available source code of:
- Diva Server TTY test utility (tty_test)
- ISDN ACOPY2 file server/remote maintenance utility (acopy2)
- FAX AFAX2 server (afax2)
Please, note that the source files of tty_test, acopy2 and afax2 utilities are
supplied for the exclusive use with Eicon Networks' range of Diva adapters.

'Diva Server for Linux' is a product that is available as binary package, precompiled for
specific kernels and distributions. This product consists of three parts:

1. Drivers and utilities built from the same source code as 'Open Diva'.
The source code of these components is also freely available as 'Open Diva'.
- DIDD driver
- XDI driver for Diva Server adapters
- CAPI2.0 driver
- User Mode IDI driver
- Card configuration, control and management interface access utility
- Diva configuration wizard (shell scripts)

2. Drivers and utilities available only in binary form.
- Diva Server TTY interface driver
- XDI driver for passive and intelligent Diva adapters

3. User mode utilities that are not part of 'Open Diva', but available as
source code if requested.
- Diva ACOPY2 ISDN file/remote maintenance server
- Diva AFAX2 fax server

--------------------------------------------------------------------------------
Differences between Open Diva and Diva Server for Linux
--------------------------------------------------------------------------------
1. 'Open Diva' protocol code and configuration scripts are installed
in the '/usr/share/eicon' directory. User mode utilities are installed
in the '/sbin' directory.
'Diva Server for Linux' protocol code, user mode utilities and configuration
scripts are installed in the '/usr/lib/eicon/divas' directory.
2. In order to minimize the package size, only limited protocol, DSP, and FPGA code
support is provided with 'Open Diva' (Diva Server BRI - ETSI only,
all other adapters - all protocols except 1TR6 and JAPAN).
In order to get full/newest protocol, DSP, and FPGA code support, you have to
download it from the Eicon web site as separate package.
'Diva Server for Linux' provides full protocol/dsp/FPGA code support, so
no additional download is necessary.
3. 'Open Diva' does not contain support for intelligent and passive Diva adapters.
You should download it from the Eicon web site as separate package.
'Diva Server for Linux' provides support for intelligent and passive
Diva adapters, so no additional download is necessary.
4. 'Diva Server for Linux' provides additional utilities that are not part
of 'Open Diva'.
5. You can compile the 'Open Diva' driver in the way you prefer, as
loadable kernel modules or as part of the kernel code.
'Diva Server for Linux' provides device drivers only as loadable kernel
modules.

--------------------------------------------------------------------------------
General features
--------------------------------------------------------------------------------

Dependent on used hardware and D-channel protocol Eicon Diva cards offers
the following features:

Supported signalling protocols:
- 1TR6, Germany
- ETSI DSS1, Europe, Germany
- VN3, France
- NET3, Belgien
- DSS1 with CRC4 off, Sweden, Benelux
- NI1, NI2, North America, National ISDN
- 5ESS, North America, AT&T
- INS-NET64, Japan
- ATEL, Australia, old TPH1962
- North America, Auto Detect
- DSS1, Italy
- DSS1, Taiwan
- Australia, Microlink (TPH1962), On Ramp ETSI
- 4ESS Software Defined Network
- 4ESS Switched Digital Service
- 4ESS Long Distance Service
- 4ESS Megacom
- 4ESS Megacom International PRI
- Hongkong PRI & BRI
- CAS, Robbed Bit Signaling PRI
+ 24 channel operation
+ Ground Start
+ Wink Start
+ Pulse dialing
+ Tone dialing
- QSIG
- EWSD, Siemens, National ISDN EWSD
- 5ESS switch National ISDN Lucent

General hardware/protocol related features:
- E1 operation mode (PRI cards only)
+ 30 channels operation mode
+ 2.1 Mbit/Sec line support
- T1 operation mode (PRI cards only)
+ 24 channels operation mode
+ 23 channels operation mode
+ 1.5 Mbit/Sec line support
- Fractiona line support (PRI cards only)
- TE mode support
- NT mode support
(Diva Server PRI, 4BRI Revision 2 and BRI Revision 2 cards only)
- High Impedance Mode support
- Permanent channel support
- Point to Point operation mode (fixed TEI)
- Point to Multipoint operation mode (BRI cards only)
- LAPD multiple SAPI support
- Configurable D-channel Layers 2 activation strategy
+ On Demand
+ Disconnect only from NT side
+ Permanent
- Configurable Layer 1 framing (PRI cards only)
+ CRC4
+ No CRC4
+ Autodetection

QSig (i.e. QSig D-channel signalling protocol) features:
- Basic Call additions to BRI interface (PRI was OK)
- Redirected Number
- Connected Name
- Several QSig derivatives
(ETSI-SS, ECMA-QSIG, ETSI-QSIG)
- Advice Of Charge (AOC)
- Indefinite length of IEs (to support more switches like Lucent)
- Segmented Message
- Configuration of QSig parameters
(Channel Identified length, Call reference length)
- Currently tested with:
+ Alcatel 4200/4400 BRI & PRI
+ Siemens Hicom 150/300 BRI & PRI
+ Nortel Meridian PRI

Basic Call features:
- Large CPNs (segmented CPN with the Setup and with the Info messages)
- Message Register (IDI interface only)
- Message Facility with active CR
- Message Facility, with Dummy CR
- Message Restart (IDI interface only)
- Connected Number, Redirected & Redirecting Number IE
- NT-2 functionality
+ Free configuranle
+ Digits collection by card (transparent to application)
+ Digits collection by application
- Built-in "Eicon Call Guard" Interface *
+ Filtering of all inbound calls
+ Filtering of all outpound calls
+ Filtering of all supported supplementary services related facilities
- Trace of D-channel data over Management Interface
(* = protocol type independent)

Supplementary Services features:
- Number Identification Services:
+ MSN Multiple Subscriber Number *
+ DDI Direct-Dialling-In *
+ SUB Sub-Addressing *
+ CLIP Calling Line Identification Presentation *
+ CLIR Calling Line Identification Restriction *
+ COLP Connected Line Identification Presentation *
+ COLR Connected Line Identification Restriction *
+ KEY Keypad Protocol *
- Call Offering Services
+ TP Terminal Portability *
+ Call Forwarding Unconditional
+ Call Forwarding Busy
+ Call Forwarding No Reply
+ Call Deflection
+ Interrogate Services
+ Interrogate Numbers
- Call Completion Services
+ CW Call Waiting *
+ HOLD (Hold/Retrieve a call) *
+ Explicit Call Transfer
- Charging Services
+ AOC Advice Of Charge *
- Multiparty
+ 3rd Party Conference
- Other
+ User-To-User Signaling *
+ Provide Messages & Information Elements (on application level!)
+ Call Forwarding/Deflection, CCBS *
- Hunt Group Support (tristate Layer 1 while booting and after Capi Release)*
(* = protocol type independent)

B-channel/DSP related:
- Digital V.90 Modem (Central Office) and Analog V.90 Modem (Client) *
+ V.34, V.32bis, V.22B, V.22, V.23, V.21, BELL212A, BELL103
+ V.42/LAPM error correction
+ V.42bis data compression
+ Configurable Guard Tone generation
+ Configurable Answer Tone supression
+ Configurable max/min connection norm and connection speed
- DTMF procedures to detect or to transmit DTMF tones
- Fax 14.400 *
+ Fax tone detection
+ Fax with Error Correction Mode (ECM)
+ Fax with Modified Read (D2 coding)
+ Fax with Modified Modified Read (T.6 coding)
+ Fax Polling/Fax on Demand
+ SEP (Selective polling), SUB (Subaddress) and PWD (Password)
+ Indicate Speed and Features (Polling and ECM)
+ New Fax Header Line
+ Fax (or any other protocols) in reversal direction
+ Page formats ISO A4, ISO B4 and ISO A3
+ Resolutions: R8 x 3.85, R8 x 7.7, R8 x 15.4, R16 x 15.4, 200 x 200,
300 x 300, 400 x 400
- Fax Group 4
+ T.90/ISO8208 detection
+ Modulo Mode detection
- Line Interconnect *
+ switch loops, digital mixer, multi conference, DTMF procedures
- Line Interconnect between multiple Diva Server adapter **
+ switch loops, digital mixer, multi conference, DTMF procedures
+ data trasport without host intervention via PCI Bus Master
directly from card to card
- VoPACKET support ***
(i.e. Voice over Packet Networks, that includes VoIP)
+ G.711 A-Law, m-Law
+ G.723 High and Low rate
+ G.165
+ G.168
+ DTMF payload support
+ Full RTP (Real Time Protocol) processing
(on the card's RISC CPU)
- HDLC
+ 64 KBit/Sec line operaion
+ 56 KBit/Sec line operaion
- Bit Transpatent
+ DTMF detection/generation
+ Fax tone detection
+ Modem tone detection
- V.120
+ V.42bis
- X.75
+ V.42bis
- LAPD
- ISO8208
- T.90/T.70 NL
- X.25 in B-channel
+ Multiple logical channels in one B-channel
- PIAFS *
+ 64 KBit/Sec
+ 32 KBit/Sec
+ Variable speed (auto-detection)
- Change the B-channel protocol while the duration of the call
(Example: Voice to Fax, Fax to Voice, Voice to Modem, etc.)
- Any of supported protocols in reversal direction
- Protocol independent Voice compounding (A-Law/m-Law) selection
- Trace of B-channel data over Management Interface
(* = DSP cards only)
(** = PRI, 4BRI and BRI Revision 2 cards only)
(*** = Only "Voice" cards)

Diva CT related (i.e Diva CT ISDN PCI hardware related):
- Headset plug detection
- External Micro plug detection
- Seperate adjustments of the two headset ports
- Programmable Tone Generator (10 different sounds, 'intrusion tones')
- Programmable Tone Ringer (10 different sounds)
- Hands free phone
- Loudhearing
- Multiple calls on Hold (max. 23 Call References active)
- Microphone Mute
- High Pass filter for a better speech quality
- Configuration of (over Management Interface State\Codec directory):
+ Micro Volume Headset
+ Speaker Volume Headset
+ Micro Volume Handsfree
+ Speaker Volume Handsfree
+ Transmitter Gain
+ Receiver Gain
+ Sidetone Gain
+ Ringer Volume
+ Ringer Melody
+ Intrusion Tone Volume
+ Intrusion Tone Melody
+ Muting on/off
+ Headset status (operating, unplugged, hook-on)
+ Hook emulation (on/off)
+ Switch/codec status (external mic, head/handset on, off)
+ execute switch from handsfree to headset and back
+ Sidetone Gain
+ Select Micro Voltage (1.5 / 5 V)

--------------------------------------------------------------------------------
General product features
--------------------------------------------------------------------------------
Diva Server for Linux offers the following features:
- RAS - Connection to a Linux-based RAS server from digital, analog, and mobile
networks with only one telephone number
- LAN-to-LAN connection with a transfer rate of 64/56 kbps or 128/112 kbps for
Diva Server BRI and Diva Client adapters and 2 (E1) or 1.5 (T1) Mbps for Diva
Server PRI adapters.
- Fax, voice server or unified messaging server
- Support for B-channel protocols: HDLC, X.75, X. 75 with 42bis, V.120,
V.120 with 42bis, ISO8208, T.70/T.90NL, LAPD, X.25, V.110 (up to 56 kbps)
- Change of used B-channel protocol on demand
- Independent ports and channels, any combination of B-channel protocols possible
- V.90 analog modem connections with V.42/LAPM (error correction) and V.42bis
compression
- Fax connections up to 14.4 kbps (see also fax and voice features below)
- Automatic synchronous/asynchronous conversion
- Automatic detection of incoming call type (Generic modem only)
- Support for all known D-channel protocols (switch types)
- Change of selected D-channel protocol or related parameters on demand via
the management interface, without driver and adapter restart
- Support for numerous supplementary services
- Support for lines with a transfer rate of 64 and 56 kps lines (e.g. USA)
- Automatic detection of Eicon Diva Server adapters during configuration
- Diva configuration wizard for easy adapter configuration
- Up to 150 B-channels can be used simultaneously (up to 5 Diva Server PRI
adapters in a system)
- TTY Serial Port (modem emulation) provides a rich AT-command set and
supports Fax Class 1 and Fax Class 2 AT-command set
- Support for CAPI-based applications through CAPI 2.0.
- Support for IDI (ISDN Direct Interface)
- Management interface for access to call state, status, statistics, and line
or interface events
- B-channel and D-channel data trace (send and receive) capability through
the management interface
- Hot-plugging support (Diva Pro PC Card only)

--------------------------------------------------------------------------------
Fax and Voice Features
--------------------------------------------------------------------------------
- Fax Class 1 and 2
- Fax and voice support via CAPI
- Fax compression (MH, MR 2Dcoding, MMR T.6 coding) and error correction
mode (ECM)
- SFF and plain text (ASCII) support
- Fax connections up to 14.4 kbps
- Fax polling
- Extended fax
- Fax tone detection
- Dynamic switching of B-channel protocols
- DTMF transmission, detection

--------------------------------------------------------------------------------
Eicon ISDN Serial Driver
--------------------------------------------------------------------------------
The Eicon ISDN Serial Driver provides access to the analog (V.90), digital
(HDLC, V.120, X.75 and X.75+V.42bis, and BTX), fax (send and receive with
14400 bps by FAX CLASS 1 or FAX CLASS 2 AT command set), V.110 (up to
56 kbps), B-channel protocol detection, Caller ID and Voice (G.711)
capabilities of Diva Server adapters by providing a standard serial driver
interface. This allows Diva Server adapters to be used in a variety of
configurations:
- As a Remote Access Server (RAS), allowing multiple incoming analog and
digital connections. These connections may be simply login sessions or
alternatively IP over PPP connections.
- As a fax server or gateway, allowing 3rd-party fax software that works
with fax modems to be installed and configured to work with Diva Server
adapters.
- As a WAP gateway or WAP application server, utilizing the V.110 protocol
(or combined with RAS server).

--------------------------------------------------------------------------------
Common ISDN API (CAPI) Version 2.0 Support
--------------------------------------------------------------------------------
The Common ISDN Application Programmers Interface (CAPI) 2.0 driver allows
CAPI-based applications to be used with Diva Server adapters, as well as
providing a mechanism for the customized development of applications to use
the capabilities of ISDN. For full information on the CAPI interface
specification, refer to the CAPI Association web site at http://www.capi.org.

--------------------------------------------------------------------------------
Supported Hardware
--------------------------------------------------------------------------------
Diva Server for Linux supports the following Diva Server ISDN PCI adapters:

ISDN BRI server adapters:
- Diva Server BRI-2M PCI
- Diva Server 4BRI-8M PCI
- Diva Server Voice 4BRI-8M PCI
ISDN PRI server adapters:
- Diva Server PRI PCI: Diva Server PRI PCI, Diva Server PRI-9M PCI,
Diva Server PRI-23M PCI, Diva Server PRI-30M PCI
- Diva Server PRI 2.0 PCI: Diva Server PRI-0M PCI, Diva Server PRI-4M PCI
Diva Server PRI-8M PCI, Diva Server PRI-30M 2.0 PCI
- Diva Server Voice PRI PCI: Diva Server Voice PRI-4M PCI,
Diva Server Voice PRI-8M PCI, Diva Server Voice PRI-30M PCI
T1 server adapters:
- Diva Server T1/PRI PCI: Diva Server T1/PRI PCI, Diva Server T1/PRI-4M PCI,
Diva Server T1/PRI-8M PCI, Diva Server T1/PRI-24M PCI
ISDN intelligent and passive adapters:
- Diva PCI: Diva PCI 2.01, Diva PCI 2.02
- Diva Pro PCI, Diva Pro PC Card (only Suse 7.1, kernel 2.4.0)
- Diva CT

Diva Server for Linux supports the installation of up to 7 Eicon Diva
adapters in one computer.

--------------------------------------------------------------------------------
System Requirements
--------------------------------------------------------------------------------
The system requirements for Diva Server for Linux are as follows:
- A PC/AT-compatible computer (80486 or higher processor with 32 MB RAM)
- An installed Linux system (for Diva Pro PC Card Suse 7.1, kernel 2.4.0
required)
- At least 40 MB of free space on the drive on which your Linux system is
installed
- An installed Eicon Diva adapter.

--------------------------------------------------------------------------------
Installation and Configuration
--------------------------------------------------------------------------------
The following steps provide an overview of the installation and configuration
procedure for Diva Server for Linux:

1. Install your Diva adapter and cable. (Refer to the printed guide that came
with your adapter).
2. Install your Diva Server for Linux software package. See Software
Installation using RPM below.
3. Configure the Diva Server for Linux software using the cfg_divas.sh
configuration wizard located in the /usr/lib/eicon/divas directory. For
further information, see Configuring Diva Server for Linux below.
4. Configure the Diva Server for Linux Serial Devices. For further
information, see Configuring the Diva Server TTY Serial ports.
5. Confirm the operation of your adapter. For further information, see Testing
adapter functionality and connectivity.

--------------------------------------------------------------------------------
Software Installation using RPM
--------------------------------------------------------------------------------
To install the Diva Server for Linux software, follow these steps:

1. Ensure that you are logged in as 'root' user (or use 'su')
2. Run the following command to extract the files from the RPM:
'rpm -i divas4linux_a_b_cc_dd_ee-ff-xxx.yy-z.i386.rpm'
- Where a_b_cc_dd is the kernel version that the RPM is intended for
(e.g. 2_2_12_20 for kernel 2.2.20 or 2_2_16 for kernel 2.2.16).
- Where ee is the distribution that the RPM is intended for (e.g. RH for
Red Hat or SuSE for SuSE).
- Where ff is the kernel configuration feature (for example SMP, i686, ...)
- Where xxx.yy-z is the revision of the RPM (e.g 100.21-1).

--------------------------------------------------------------------------------
Files included in the RPM package
--------------------------------------------------------------------------------
The following files are included in the RPM:

- Device driver for active PCI adapters (divas.o, divadidd.o, diva_idi.o)
- CAPI2.0 interface (divacapi.o, kernelcapi.o, capi.o)
- TTY (COM port) interface (Divatty.o)
- Utility used to download protocol code to active adapters, to configure and
to start adapters, to read and translate messages from the adapter's XLOG
interface, to create core dump of the adapter memory, to control the adapter
via the management interface and to read and translate messages from the
adapter's MLOG interface (divactrl).
- Protocol code for Diva PRI adapters (all *.pm, *.pm2 files and *.bin files)
- Protocol code for Diva BRI adapters (all *.sm, *.sm.4 files and *.bin files)
- Protocol code for Diva 4BRI adapters (all *.qm?, *.2q? files, *.bit files and
*.bin files)
- Utility that allows to test the TTY interface, monitor link quality and
adapter performance and to test the hardware (tty_test).
This utility uses the TTY interface.
- ISDN file server, client, and remote management application that uses
the ACOPY protocol and allows to transfer files, create, remove, or list
directories and execute commands on a remote station (acopy2).
This utility uses the CAPI2.0 interface.
- Fax server or client that allows to transfer, receive, and poll fax documents
in text and SFF formats with various transmission speeds and various
ECM/compression settings.
This utility uses the CAPI2.0 interface.
- Diva configuration wizard used to detect the hardware and to automatically
create the configuration script (menu driven tools, includes the files
cfg_divas.sh cfg_pri.sh and cfg_bri.sh).
The Diva configuration wizard is started by executing the
'/usr/lib/eicon/divas/cfg_divas.sh' shell script.
- Shell script used by RPM to create or delete the symbolic links that enable
the 'Diva Server for Linux' drivers to be started automatically
at system startup (cfg_util.sh).
- Dummy Diva configuration file. This file is used to generate warnings if
the user forgets to configure divas4linux after installation (divas_cfg.rc).
This file is overwritten by the Diva configuration wizard, once the
configuration procedure is invoked.
- Shell script used to capture information about your system, hardware, or
installation if you have problems to install, configure, or start
divas4linux (divas_sys_info.sh).
This shell script generates a file named 'report.txt'. You can examine and
modify this shell script if it registers information (e.g. phone numbers
etc.) that you do not want to pass on to Eicon. If you change the script,
please send us your modified version together with the 'report.txt' file.
- Shell script used to stop and unload Diva drivers (divas_stop.rc).
- 'xlog' shell script that contains 'divactrl load -ReadXlog $*' and can be
used to read XLOG traces from the card.
- 'mlog' shell script that contains 'divactrl mlog $*' and can be used to read
MLOG traces from the card.
- 'mantool' shell script that contains 'divactrl mantool $*' and can be used
for management interface access.
- 'divaload' shell script that contains 'divactrl load $*' and can be used
to control the adapter.
- Card services configuration file for Diva PCMCIA adapters (diva.conf)
- Card services interface driver for Diva PCMCIA adapters (diva_cs.o)

================================================================================
CONFIGURING DIVA SERVER FOR LINUX
================================================================================

The 'cfg_divas.sh' script (located in the 'usr/lib/eicon/divas' directory) is a
setup wizard that detects all installed Diva Server adapters and walks you
through a series of questions to configure the ISDN settings for the installed
adapter(s).

The setup wizard generates the 'divas_cfg.rc' file (located in the
'usr/lib/eicon/divas' directory) that is used to start all adapters and
interface drivers at system startup or to start the adapters manually.

The setup wizard creates all necessary device nodes in the /dev directory:
- capi20: used to access the CAPI2.0 interface
- ttyds01...ttyds[n] - used to access the Diva TTY interface; [n] is the number
of B-channels of all installed adapters.

The available configuration options for Diva Server PRI adapters are described
below. For information on configuring Diva Server BRI or 4BRI adapters, refer to
the section Configuring Diva Server BRI and 4BRI adapters. For information on
configuring Diva Client adapters, see the section Configuring Diva Client adapters.

--------------------------------------------------------------------------------
Physical and logical adapter number
--------------------------------------------------------------------------------
Every Diva adapter that is installed in the system is a 'physical' adapter.
Every physical adapter contains one or more ISDN interfaces. Each of
these ISDN interfaces is represented in the system by a 'logical' adapter.
Example: Three Physical Diva adapters are installed in the system,
a Diva Server BRI, a Diva Server PRI, and a Diva Server 4BRI. The Diva
Server BRI and Diva Server PRI will add one logical adapter each.
The Diva Server 4BRI will add four logical adapters to the system.
If one physical adapter contains multiple logical adapters, a continuous
block of adapter numbers is allocated to these adapters. The first logical
adapter is the 'master' adapter. This adapter is responsible for the hardware
resources of the physical adapter and for loading, starting, and stopping
all logical adapters provided by the physical adapter. In all other aspects
(functionality, configuration, selected protocol, debug buffers and features)
all logical adapters are fully independent from the location of their physical
adapters: on different physical adapters or on the same physical adapter.

--------------------------------------------------------------------------------
'/proc' file system
--------------------------------------------------------------------------------
After being started, the DIDD (divadidd.o) driver creates the
'/proc/net/eicon' directory in the proc file system and the 'divadidd' file
in this directory. You can read this file (for example by executing
'cat divadidd') to get version information of this driver.
After being started, the XDI driver (divas.o) creates the 'divas' file in the
'/proc/net/eicon' directory. You can read this file (for example by
executing 'cat divas') to get version information of the XDI driver.
A subdirectory named 'adapterXXX' (XXX is the logical adapter number) is
created in the '/proc/net/eicon' directory for every logical adapter
present in the system.
Each 'adapterXXX' directory contains the following files:
info - You can read this file ('cat info') to get information
on the adapter:
adapter name, serial number, amount of channels supported by
the adapter, hardware resources assigned to the
adapter, adapter state (possible adapter states:
ready : ready to download and start firmware or fpga
active : operating
trapped : firmware problem, core dump should be generated,
unknown : hardware problem,
slave : slave adapter of a Diva adapter that supports
multiple logical adapters)
group_optimization - You can read this file ('cat group_optimization') to
get the current state of this feature (on/off - 1/0).
You can write '1' to this file to turn this feature on
('echo 1 > group_optimization').
You can write '0' to this file to turn this feature off
('echo 0 > group_optimization').
dynamic_l1_down - You can read this file ('cat dynamic_l1_down') to
get the current state of this feature (on/off - 1/0).
You can write '1' to this file to turn this feature on
('echo 1 > dynamic_l1_down').
You can write '0' in this file to turn this feature off
('echo 0 > dynamic_l1_down').

--------------------------------------------------------------------------------
CONFIGURING DIVA SERVER PRI ADAPTERS
--------------------------------------------------------------------------------

To configure the settings for your Diva Server PRI adapter, follow these steps:

NOTE: Depending on which type of adapter or D-channel protocol (switch type) is
currently being configured, your list of options will vary. The Diva
Server PRI adapter will offer more choices than would be found for a Diva
Server BRI adapter, for instance.

1. Change to the /usr/lib/eicon/divas directory and run the following command:

./cfg_divas.sh

You are presented with the wizard's main screen 'DIVA ISDN ADAPTER
CONFIGURATION WIZARD', stating how many adapters were automatically
detected. Select whether you want to start configuration now:

Start Configuration (Y/N):

Type 'N' or 'n' to exit the wizard.
Type 'Y' or 'y' to proceed.

The next series of screens will be presented for each and every Diva
Server PRI adapter found in your system. The following questions and
their possible choices are listed below, in the order they are
presented in the wizard.

2. At first, you are prompted to specify the operation mode of your Diva
Server PRI adapter.

PLEASE SELECT OPERATION MODE FOR ADAPTER 1 - PRI

1 - E1/T1 TE mode operation with D-channel
Normal operating mode for the Diva Server adapter when attaching to an
ISDN network.
2 - E1/T1 NT mode operation with D-channel
Your Diva Server PRI adapter can emulate an ISDN network, allowing
back-to-back operation with another Diva Server PRI adapter. This
requires a special back-to-back cable configuration and is only
available for Diva Server PRI adapters.
3 - Permanent connection, TE <--> TE mode (structured line)
Leased line operation for LAN to LAN connections with 2 or 1.5 Mbps
over a structured E1 or T1 line.
4 - Permanent connection, NT <--> TE mode (unstructured line), TE side
Leased line operation for LAN to LAN connections with 2 or 1.5 Mbps
over an unstructured E1 or T1 line, TE side.
5 - Permanent connection, NT <--> TE mode (unstructured line), NT side
Leased line operation for LAN to LAN connections with 2 or 1.5 Mbps
over an unstructured E1 or T1 line, NT side.

NOTE: Typical usage for selection 1 and 2 is: RAS server, fax server,
unified messaging server, wireless access server, WAP server,
VoIP (media gateway), PABX or link between two PABXs. Typical
usage for selection 3 to 5 is: LAN to LAN coupling (E1: 2Mbps
or T1: 1.5 Mbps).

Type the number of your selection and press ENTER.

3. You are now prompted to select your ISDN switch type (D-channel
protocol), as provided by your ISDN service provider:

PLEASE SELECT D-CHANNEL PROTOCOL (SWITCH TYPE)

1 - 1TR6 Germany, old protocol for PABX
2 - ETSI DSS1, Europe, Germany
3 - FRANC VN3, France, old protocol for PABX
4 - BELG NET3, Belgium, old protocol for PABX
5 - SWED DSS1 with CRC4 off, Sweden, Benelux
6 - NI NI1, NI2, North America, National ISDN
7 - 5ESS 5ESS, North America, AT&T
8 - JAPAN Japan, INS-NET64
9 - ATEL ATEL, Australia, old TPH1962
10 - ITALY DSS1, Italy
11 - TWAN DSS1, Taiwan
12 - AUSTRAL Australia, Microlink, TPH1962, On Ramp ETSI
13 - 4ESS_SDN 4ESS Software Defined Network
14 - 4ESS_SDS 4ESS Switched Digital Service
15 - 4ESS_LDS 4ESS Long Distance Service
16 - 4ESS_MGC 4ESS Megacom
17 - 4ESS_MGI 4ESS Megacom International
18 - HONGKONG Hong Kong
19 - RBSCAS Robbed Bit Signaling, CAS
20 - QSIG QSIG, Intra PABX link protocol

Type the number of your selection and press ENTER.

NOTE: If you selected the RBSCAS switch type, see the
section 'Advanced configuration for RBSCAS'.

--------------------------------------------------------------------------------
Advanced configuration - Diva Server PRI adapters
--------------------------------------------------------------------------------
At this point, you have configured the basic settings required to operate
the adapter. Because ISDN switch configurations vary, your provisioning may
require customizing. The following menu choices provide advanced configuration
features:

1. At first, you are asked if you want to configure advanced parameters:

DO YOU WISH TO CONFIGURE ADVANCED PARAMETERS ?

Type 'N' or 'n' to exit the wizard or proceed to configure the next
adapter. You are then prompted to specify if you want to use CAPI
group optimization for your adapter (see step 9).
Type 'Y' or 'y' to configure advanced features.

2. You are prompted to 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.

SELECT NT2 (DIRECT DIAL IN, DIRECT INWARD DIALING) MODE

Type 'N' or 'n' to skip this feature.
Type 'Y' or 'y' to accept NT2 mode.

NOTE: This option is not available if you have selected a North American
switch type.

If you select 'Y' you need to enter the direct inward dialing number
length:

PLEASE ENTER DIRECT INWARD DIALING NUMBER LENGTH

Enter a value between 0 and 20 (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 PABX systems).

3. You are asked to specify the layer 1 framing type.

PLEASE SELECT LAYER 1 OPTIONS

0 - NATIONAL DEFAULT (dependent on selected D-channel protocol)
1 - doubleframing (NO CRC4)
2 - multiframing (CRC4)
3 - autodetection

Type the number of your selection and press ENTER.

4. You are prompted to specify the law type to use to transmit analog data
on your line.

PLEASE SELECT LAW OPTIONS

0 - NATIONAL DEFAULT (dependent on selected D-channel protocol)
1 - force A-Law
2 - force u-Law

The 'National Default' setting automatically sets the correct law for the
selected switch type. You need to change this setting only if a PBX
requires a special law type that does not correspond to the law type
used by the switch type.

Type the number of your selection and press ENTER.

5. You are asked to specify whether you want to set your Diva Server adapter
to high impedance state.

Set adapter to high impedance state until first user application requests
interface activation.
ATTENTION: Please select Yes only if you have configured your PABX for this
operation (e.g. Hunt Group).

Type 'N' or 'n' to skip this feature.
Type 'Y' or 'y' to accept high impedance state.

NOTE: Select 'Yes' only if your PABX switch is configured for this.
Otherwise, indicate 'No'.

When you activate the high-impedance state option, dynamic layer 1
management (dynamic_l1_down) is also activated. Dynamic layer 1
management effects the following behaviour of your Diva Server adapter:
If the Diva adapter is used inside of a 'Hunt Group', it is useful that
no calls are delivered to the Diva adapter until the application running on top
of this adapter gets ready. To achieve this, dynamic layer 1 management is used:
Layer 1 of the Diva Server adapter is switched to High Impedance state until the
first application sends listen to the adapter. In this way, the PABX that manages
the Hunt Group will not deliver calls to the adapter (i.e. PABX will consider line
as not connected to terminal equipment).
After the Diva Server adapter receives the first listen from an application (also
application is ready to receive calls) it switches to normal operation mode.
This signals to the PABX that the adapter was attached to the port
and calls can be routed to this port now.
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 which indicates to the PABX
that the port is no longer available. In this way, no calls will be routed to a
port that is not able to accept these calls and no calls will be lost.

6. You are prompted to specify whether you are using a full E1/T1 line
(i.e. 30/23 B-channels) or whether you ordered a fractional line.

DO YOU USE A FRACTIONAL E1/T1 LINE ?

Type 'N' or 'n' to skip this feature.
Type 'Y' or 'y' to accept fractional PRI operation.

If you select 'Y' you must also specify the value of the total
number of active channels, i.e. if your subscription is for 5
B-channels, then you must specify '5' in this configuration.
If you specify a value higher than your subscription, then you
may experience errors indicating that the channel is unavailable
when placing an outbound call.

PLEASE ENTER THE HIGHEST AVAILABLE CHANNEL

Please enter a number [1...30].

7. You are asked to 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 unless your service provider
specifies a different TEI for your connections.

DO YOU USE STANDARD TEI ? (YES)

Type 'Y' or 'y' to skip this feature (default TEI=0).
Type 'N' or 'n' to specify a different TEI value (between 1-63).

If you select 'N' you must enter your TEI value:

PLEASE ENTER TEI VALUE [0...63]

8. You are prompted to specify if local tones should be generated.

GENERATE LOCAL TONES (ALERT/BUSY) IN B-CHANNEL IN
CASE TONES ARE NOT PROVIDED BY ISDN EQUIPMENT ?

Type 'Y' or 'y' to let your adapter generate in-band alert or
busy tones that signal to the remote station if an application
is ready to accept a call or if it is busy etc.

9. Specify if you want to use group optimization for your adapter.

DO YOU WISH TO TURN CAPI GROUP OPTIMIZATION ON THIS
ADAPTER 'ON'?

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
(i.e. one idle application in each group that matches the incoming call
will receive the indication about an incoming call) instead of a per
application basis (i.e. 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 application registers
multiple CAPI applications that use the same listen parameters.

Type 'Y' or 'y' to turn group optimization on.
Type 'N' or 'n' to skip this feature.

10. This concludes the configuration of this Diva Server PRI adapter:

DIVA ADAPTER CONFIGURATION COMPLETE
Startup script file:/usr/lib/eicon/divas/divas_cfg.rc
...
...
View generated configuration file (Y/N):

Type 'Y' or 'y' to view the generated configuration file.
Type 'N' or 'n' to step to the next adapter for configuration. If there
are no other adapters installed, the wizard will exit at this point. Go
to Loading the Diva Server Modules.

--------------------------------------------------------------------------------
Advanced configuration for RBSCAS
--------------------------------------------------------------------------------
1. At first , you are prompted to specify the RX Digit Timeout.

RX DIGIT TIMEOUT, SECONDS

Specify 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.

2. You are then prompted to specify how call collisions are to
be resolved if both ends of a line simultaneously attempt to
initiate a call.

GLARE-RESOLVING PARTY

No - When a call collision occurs, your server will not abort
its call attempt to resolve the collision but wil wait for the
other party to do so. It will then start sending address
digits.
Yes - When a call collision occurs, 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.

If your Diva Server adapter is operated in one of the TE modes,
you should leave the default setting 'Yes'. If it is operated in NT
mode, you should change the setting to 'No'.

3. Specify which bearer capability should be included with the
call that is signaled to the application.

SIGNAL CALLS TO APPLICATION AS

A - Voice/analog (3.1 kHz audio): Select this value if your application
handles voice calls, fax group III calls, and analog modem calls.
D - Data/digital (56 kbps rate adaptation HDLC): Select this
value if your application handles digital calls, e.g. digital RAS.

4. You are then prompted to specify the answer timeout.

ANSWER TIMEOUT, SECONDS

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.

5. Specify the trunk mode that your adapter should use.

TRUNK MODE

1 - WinkStart (default)
2 - LoopStart
3 - GroundStart

The trunk mode that you set here must correspond to the trunk mode that
your switch uses.

NOTE: The trunk modes are defined in the TIA/EIA-464 specification.
WinkStart is also defined in AT&T TR41458.

6. Specify the dial type that your adapter should use.

DIAL TYPE

1 - Pulse
2 - DTMF (Dual-Tone Multifrequency Signaling, default)
3 - MF (Multifrequency Signaling)

The dial type that you select here must correspond to the dial type
that your switch uses. Most analog telephones use dual-tone
multifrequency signaling.
Type the number of your selection and press ENTER.

7. Since the RBSCAS switch type always uses direct inward dialing,
you need to specify the direct inward dialing number length.

PLEASE ENTER DIRECT INWARD DIALING NUMBER LENGTH

8. You are prompted to specify the law type to use to transmit analog data
on your line.

PLEASE SELECT LAW OPTIONS

0 - NATIONAL DEFAULT (dependent on selected D-channel protocol)
1 - force A-Law
2 - force u-Law

Type the number of your selection and press ENTER.

8. You are asked to specify whether you want to set your Diva Server adapter
to high impedance state.

Type 'N' or 'n' to skip this feature.
Type 'Y' or 'y' to accept high impedance state.

NOTE: Select 'Yes' only if your PABX switch is configured for this.
Otherwise, indicate 'No'.

9. You are prompted to specify whether you are using a full E1/T1 line
(i.e. 30/23 B-channels) or whether you ordered a fractional line.

DO YOU USE A FRACTIONAL E1/T1 LINE ?

Type 'N' or 'n' to skip this feature.
Type 'Y' or 'y' to accept fractional PRI operation.

PLEASE ENTER THE HIGHEST AVAILABLE CHANNEL

Please enter a number [1...30].

10. You are prompted to specify if local tones should be generated.

GENERATE LOCAL TONES (ALERT/BUSY) IN B-CHANNEL IN
CASE TONES ARE NOT PROVIDED BY ISDN EQUIPMENT ?

Type 'Y' or 'y' to let your adapter generate in-band alert or
busy tones that signal to the remote station if an application
is ready to accept a call or if it is busy etc.

11. Specify if you want to use group optimization for your adapter.

DO YOU WISH TO TURN CAPI GROUP OPTIMIZATION ON THIS
ADAPTER 'ON'?

Type 'Y' or 'y' to turn group optimization on.
Type 'N' or 'n' to skip this feature.

12. This concludes the configuration of this Diva Server PRI adapter:

DIVA ADAPTER CONFIGURATION COMPLETE
Startup script file:/usr/lib/eicon/divas/divas_cfg.rc
...
...
View generated configuration file (Y/N):

--------------------------------------------------------------------------------
CONFIGURING DIVA SERVER BRI AND 4BRI ADAPTERS
--------------------------------------------------------------------------------

To configure the settings for your Diva Server adapter, follow these steps:

NOTE: Depending on which type of adapter is currently being configured, your
list of options will vary. The Diva Server PRI adapter will offer more
choices than would be found for a Diva Server BRI adapter, for instance.

1. Change to the /usr/lib/eicon/divas directory and run the following command:

./cfg_divas.sh

You are presented with the wizard's main screen 'DIVA ISDN ADAPTER
CONFIGURATION WIZARD', stating how many adapters were automatically detected.
Select whether you want to start configuration now:

Start Configuration (Y/N):

Type 'N' or 'n' to exit the wizard.
Type 'Y' or 'y' to proceed.

The next series of screens will be presented for Diva Server BRI adapters
found in your system. The following questions and their possible choices
are listed below, in the order they are presented in the wizard:

2. If you have installed a Diva Server 4BRI-8M adapter, you need to specify
whether you want to configure each port individually.

DO YOU WISH TO USE A DIFFERENT CONFIGURATION FOR EACH
PORT OF THE DIVA SERVER 4BRI-8M PCI ADAPTER WITH SERIAL
NUMBER XXXX?

Type 'Y' or 'y' if you want to create individual configurations. The wizard
will then walk you through the following options for each port.
Type 'N' or 'n' if you want to configure all four ports with identical
parameters. The wizard will then walk you through the following options
only once.

3. At first, you are prompted to specify the operation mode of your Diva
Server BRI adapter.

PLEASE SELECT OPERATION MODE FOR ADAPTER 1 - BRI

1 - S0 TE mode operation with D-channel
Normal operating mode for the Diva Server adapter when attaching to an
ISDN network. Typical usage is: RAS server, fax server, unified
messaging server, wireless access server, WAP server, VoIP (media
gateway), PABX or link between two PABXs.
2 - S0 TE mode operation, permanent connection
LAN to LAN coupling using a leased line.

Type the number of your selection and press ENTER.

NOTE: If you select 'S0 TE mode operation, permanent connection', all
all advanced parameters are set automatically and cannot be modified
manually.

4. You are now prompted to select your ISDN switch type (D-channel protocol),
as provided by your ISDN service provider.

PLEASE SELECT D-CHANNEL PROTOCOL (SWITCH TYPE)

1 - 1TR6 Germany, old protocol for PABX
2 - ETSI DSS1, Europe, Germany
3 - FRANC VN3, France, old protocol for PABX
4 - BELG NET3, Belgium, old protocol for PABX
5 - NI NI1, NI2, North America, National ISDN
6 - 5ESS 5ESS, North America, AT&T
7 - JAPAN Japan, INS-NET64
8 - ATEL ATEL, Australia, old TPH1962
9 - US North America, Auto Detect
10 - ITALY DSS1, Italy
11 - TWAN DSS1, Taiwan
12 - AUSTRAL Australia, Microlink (TPH1962), On Ramp ETSI
13 - HONGKONG Hong Kong
14 - QSIG, Intra PABX link protocol
15 - EWSD Siemens, National ISDN EWSD
16 - 5ESS_NI 5ESS switch National ISDN Lucent

Type the number of your selection and press ENTER.

NOTE: If you select the NI-1 protocol, you must enter the Service Profile
ID (SPID) values as well. These are supplied by your ISDN Service
provider. The SPID values must be entered or your line will not be
properly activated. If you select the 5ESS protocol, some regions
in the United States may also require SPIDs. If you use Auto-SPID
do not set SPID values here. You can change the SPID settings
at any time by means of the management interface utility 'mantool'
without restarting the adapter.

--------------------------------------------------------------------------------
Advanced configuration - Diva Server BRI and 4BRI adapters
--------------------------------------------------------------------------------
At this point, you have configured the basic settings required to operate
the adapter. Because ISDN switch configurations vary, your provisioning may
require customizing. The following menu choices provide advanced configuration
features:

1. At first, you are asked if you want to configure advanced parameters:

DO YOU WISH TO CONFIGURE ADVANCED PARAMETERS ?

Type 'N' or 'n' to exit the wizard or proceed to configure the next adapter.
You are then prompted to specify if you want to use CAPI
group optimization for your adapter (see step 9).

Type 'Y' or 'y' to configure advanced features.

2. You are asked to specify whether you want to use the V.6
protocol code.

DO YOU WISH TO USE V.6 PROTOCOL CODE ?

Leave the default setting 'No'.

3. You are prompted to 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.

SELECT NT2 (DIRECT DIAL IN, DIRECT INWARD DIALING) MODE ?

Type 'N' or 'n' to skip this feature.
Type 'Y' or 'y' to accept NT2 mode.

NOTE: This option is not available if you have selected a North American
switch type.

If you select 'Y' you need to enter the direct inward dialing number
length:

PLEASE ENTER DIRECT INWARD DIALING NUMBER LENGTH

Enter a value between 0 and 20 (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 PABX systems).

4. You are asked to select the D-channel layer 2 connection mode for your
configuration.

PLEASE SELECT D-CHANNEL LAYER 2 ACTIVATION POLICY

0 - 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.
1 - 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 NT side.
2 - Always active (default)
The D-channel layer 2 connection is activated as soon as the ISDN
protocol is loaded and is kept active afterwards.
3 - Always active, mode 2 (rarely used)
The D-channel layer 2 connection is always active. This setting is
used only for very rare configurations.

Type the number of your selection and press ENTER.

5. You are prompted to specify the law type to use to transmit analog data
on your line.

PLEASE SELECT LAW OPTIONS

0 - NATIONAL DEFAULT (dependent on selected D-channel protocol)
1 - force A-Law
2 - force u-Law

Type the number of your selection and press ENTER.

6. You are prompted to specify the type of ISDN interface to which your Diva
Server adapter is connected.

PLEASE SELECT S0 INTERFACE MODE

1 - Point to Multipoint
Allows multiple terminal devices (TEs) to be attached to the BRI line.
2 - Point to Point
Only one TE can be attached to the BRI line. The TEI value must be
set on the next screen.

- If you select the point to point interface mode you are prompted to enter
the TEI value. The TEI value specifies the Terminal Endpoint Identifier
that is assigned to the ISDN line. Leave the standard value unless your
service provider specifies a different TEI for your connections.

DO YOU USE STANDARD TEI ? (YES)

Type 'Y' or 'y' to skip this feature (default TEI=0).
Type 'N' or 'n' to specify a different TEI value (between 1-63).

If you select 'N' you must enter your TEI value:

PLEASE ENTER TEI VALUE [0...63]

- If you select the point-to-point interface mode, you are also
prompted to specify if local tones should be generated.

GENERATE LOCAL TONES (ALERT/BUSY) IN B-CHANNEL IN
CASE TONES ARE NOT PROVIDED BY ISDN EQUIPMENT ?

Type 'Y' or 'y' to let your adapter generate in-band alert or
busy tones that signal to the remote station if an application
is ready to accept a call or if it is busy etc.

7. Specify if you want to use group optimization for your adapter.

DO YOU WISH TO TURN CAPI GROUP OPTIMIZATION ON THIS
ADAPTER 'ON'?

Type 'Y' or 'y' to turn group optimization on.
Type 'N' or 'n' to skip this feature.

8. This concludes the configuration of this Diva Server BRI adapter:

DIVA ADAPTER CONFIGURATION COMPLETE
Startup script file:/usr/lib/eicon/divas/divas_cfg.rc
...
...
View generated configuration file (Y/N):

Type 'Y' or 'y' to view the generated configuration file.
Type 'N' or 'n' to step to the next adapter for configuration. If
there are no other adapters installed, the wizard will exit at this
point. Go to Loading the Diva Server Modules.

--------------------------------------------------------------------------------
CONFIGURING DIVA CLIENT ADAPTERS
--------------------------------------------------------------------------------
To configure the settings for your Diva Client adapter, follow these steps:

1. Change to the /usr/lib/eicon/divas directory and run the following command:

./cfg_divas.sh

You are presented with the wizard's main screen 'DIVA ISDN ADAPTER
CONFIGURATION WIZARD', stating how many adapters were automatically detected.

Note: If the setup wizard does not detect any installed Diva ISDN adapter, it will ask
you if you use a PCMCIA adapter. Type 'Y' or 'y' if you want install the Diva Pro
PC Card. Otherwise, shutdown your computer, install your Diva adapter and
then start the setup wizard again.

Select whether you want to start configuration now:

Start Configuration (Y/N):

Type 'N' or 'n' to exit the wizard.
Type 'Y' or 'y' to proceed.

The next series of screens will be presented for each and every Diva
Client adapter found in your system. The following questions and their possible
choices are listed below, in the order they are presented in the wizard:

2. At first, you are prompted to specify the operation mode of your Diva
Client adapter.

PLEASE SELECT OPERATION MODE FOR ADAPTER 1 - XXX

1 - S0 TE mode operation with D-channel
Normal operating mode for the Diva Client adapter when attaching to an
ISDN network. Typical usage is: RAS server, fax server, unified
messaging server, wireless access server, WAP server, VoIP (media
gateway), PABX or link between two PABXs.
2 - S0 TE mode operation, permanent connection
LAN to LAN coupling using a leased line.

Type the number of your selection and press ENTER.

NOTE: If you select 'S0 TE mode operation, permanent connection', all
advanced parameters are set automatically and cannot be modified
manually.

3. You are now prompted to select your ISDN switch type (D-channel protocol),
as provided by your ISDN service provider.

PLEASE SELECT D-CHANNEL PROTOCOL (SWITCH TYPE)

2 - ETSI DSS1, Europe, Germany
3 - FRANC VN3, France, old protocol for PABX
4 - BELG NET3, Belgium, old protocol for PABX
5 - NI NI1, NI2, North America, National ISDN
6 - 5ESS 5ESS, North America, AT&T
7 - JAPAN Japan, INS-NET64
8 - ATEL ATEL, Australia, old TPH1962
9 - US North America, Auto Detect
10 - ITALY DSS1, Italy
11 - TWAN DSS1, Taiwan
12 - AUSTRAL Australia, Microlink (TPH1962), On Ramp ETSI
13 - HONGKONG Hong Kong

Type the number of your selection and press ENTER.

--------------------------------------------------------------------------------
Advanced configuration - Diva Client adapters
--------------------------------------------------------------------------------
At this point, you have configured the basic settings required to operate
the adapter. Because ISDN switch configurations vary, your provisioning may
require customizing. The following menu choices provide advanced configuration
features:

4. At first, you are asked if you want to configure advanced parameters:

DO YOU WISH TO CONFIGURE ADVANCED PARAMETERS ?

Type 'N' or 'n' to exit the wizard or proceed to configure the next adapter.
Type 'Y' or 'y' to configure advanced features.

5. You are prompted to 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.

SELECT NT2 (DIRECT DIAL IN, DIRECT INWARD DIALING) MODE ?

Type 'N' or 'n' to skip this feature.
Type 'Y' or 'y' to accept NT2 mode.

NOTE: This option is not available if you have selected a North American
switch type.

If you select 'Y' you need to enter the direct inward dialing number
length:

PLEASE ENTER DIRECT INWARD DIALING NUMBER LENGTH

6. You are asked to select the D-channel layer 2 connection mode for your
configuration.

PLEASE SELECT D-CHANNEL LAYER 2 ACTIVATION POLICY

Type the number of your selection and press ENTER.

7. You are prompted to specify the law type to use to transmit analog data
on your line.

PLEASE SELECT LAW OPTIONS

0 - NATIONAL DEFAULT (dependent on selected D-channel protocol)
1 - force A-Law
2 - force u-Law

Type the number of your selection and press ENTER.

8. You are prompted to specify the type of ISDN interface to which your Diva
Client adapter is connected.

PLEASE SELECT S0 INTERFACE MODE

If you select the point to point interface mode you are prompted to enter
the TEI value. The TEI value specifies the Terminal Endpoint Identifier
that is assigned to the ISDN line. Leave the standard value unless your
service provider specifies a different TEI for your connections.

DO YOU USE STANDARD TEI ? (YES)

Type 'Y' or 'y' to skip this feature (default TEI=0).
Type 'N' or 'n' to specify a different TEI value (between 1-63).

If you select 'N' you must enter your TEI value:

PLEASE ENTER TEI VALUE [0...63]

10. This concludes the configuration of this Diva Client adapter.
The setup wizard generates the divas_cfg.rc file that is used
to start the interface drivers.
If you have installed a Diva Pro PC Card and the setup wizard
detects obsolete 'Diva Server for Linux' drivers in the 'lib/modules'
directory tree, it renames and moves these drivers to the 'lib/modules'
directory. It also updates the card services configuration database.

DIVA ADAPTER CONFIGURATION COMPLETE
Startup script file:/usr/lib/eicon/divas/divas_cfg.rc
...
...
View generated configuration file (Y/N):

Type 'Y' or 'y' to view the generated configuration file.
Type 'N' or 'n' to step to the next adapter for configuration. If
there are no other adapters installed, the wizard will exit at this
point. Go to Loading the Diva modules.

--------------------------------------------------------------------------------
Loading the Diva modules
--------------------------------------------------------------------------------
During the installation and at the conclusion of the configuration, the
'divas_cfg.rc' script is automatically generated. This script is used to
load protocol, CAPI and TTY interfaces.
On system startup, the Diva Server adapters will be started by symbolic links
named S03DIVAS4LINUX and created as part of the installation process.
These links are located in the /etc/rc.d/rc2.d, /etc/rc.d/rc3.d,
/etc/rc.d/rc5.d directories for Red Hat and in the /sbin/init.d/rc2.d,
/sbin/init.d/rc3.d, /sbin/init.de/rc5.d directories for SuSE.
(If you wish to remove these links, please execute:
'sh /usr/lib/eicon/divas/cfg_util.sh 2'.
If you wish restore these links, please execute:
'sh /usr/lib/eicon/divas/cfg_util.sh 1').
If you have changed the configuration or wish to restart/stop the Diva Server
adapters without restart of your system, you can use the script 'divas_stop.rc'
to stop Diva adapters and unload Diva drivers and you can run the
'/usr/lib/eicon/divas/divas_cfg.rc' script to load the Diva drivers and start the
Diva adapters.

If you wish to restart only one specific Diva adapter, you can do it
without unloading the drivers by executing the command
'./divactrl load -StopCard -c XXX',
where XXX is logical adapter number. In case of adapters that support multiple
interfaces (for example 4BRI) , the adapter number should be the number of the
master adapter.
After the adapter was stopped, you can load and start it again without affecting
other adapters (in case of adapters that support multiple interfaces, all
logical adapters that belong to the same physical adapter are affected).

If you have installed a Diva Pro PC Card , the card access driver (diva_cs.o)
is automatically loaded or unloaded on insertion or removal of the PCMCIA
adapter or on power management events.
The CAPI and TTY interface are permanently loaded and fully independent
from the state of the PCMCIA adapter, i.e. they do not lose their settings
and state when the PCMCIA adapter is removed. From their point of view,
the adapter removal looks like the removal of the ISDN cable. Thanks to
this feature, the same applications that are used with other Diva
adapters can be used with the Diva Pro PC Card without any
modifications. For example, a standard PPP daemon can be used for
Internet access via the Diva TTY interface. For applications that
require a notification on the state of the PCMCIA adapter, the
'cardstate' event with two states (inserted, removed) is provided
in the management interface that is part of the protocol driver.

--------------------------------------------------------------------------------
Manual adapter configuration
--------------------------------------------------------------------------------
If you cannot use the Diva configuration wizard or or you need to create
you own adapter configuration or startup procedure, you have to perform
the following steps to load drivers and start the Eicon Diva adapter:

1. Login as 'root' (or use 'su').
2. Change the working directory to '/usr/lib/eicon/divas'
('cd /usr/lib/eicon/divas').
2. Load the DIDD module ('insmod ./divadidd.o').
3. Load the XDI module ('insmod ./divas.o')
4. Load the User Mode IDI module, if necessary ('insmod ./diva_idi.o').
5. Start every available Eicon Diva adapter by the 'divactrl' utility.
Please call './divactrl load' to get help and full list of available options.
6. Set 'group optimization' and 'dynamic_l1_down' options, if necessary
(by default these features are turned off).
7. Load CAPI, if necessary
('insmod ./kernelcapi.o && insmod ./divacapi.o && insmod ./capi.o').
8. Load the Diva Server TTY module, if necessary ('insmod ./Divatty.o').

--------------------------------------------------------------------------------
Special configuration features
--------------------------------------------------------------------------------
Eicon Diva adapters provide numerous configuration options part of which
are only used in special applications.
These configuration options are not covered by the Diva configuration wizard.
To get a full list of configuration options, you should change to the
'/usr/lib/eicon/divas' directory and execute './divactrl load'.
You can apply special configuration options by modifying your adapter's
startup script 'divas_cfg.rc'. In this case, you have to specify special
configuration options in the command line of the 'divactrl' adapter load utility
like all other options.
Special configuration options can be changed during run time without adapter
restart via the management interface (for example by means of the
'divactrl mantool' management interface acces utility).

-------------------------------------------------------------------------------
TESTING ADAPTER FUNCTIONALITY AND CONNECTIVITY
-------------------------------------------------------------------------------
The following procedures allow you to determine if the adapter and the ISDN
service is working properly. After configurating and loading the drivers, it
is recommended that you use one or all of the following methods to test with.

--------------------------------------------------------------------------------
TTY test
--------------------------------------------------------------------------------
This test allows you to test adapter and Diva TTY interface functionality and
link integrity using various bearer protocols supported by your adapter .
The 'tty_test' utility is located in the '/usr/lib/eicon/divas' directory.
On the server side, please call: './tty_test 1 s auto'
On the client side, please call: './tty_test 2 [myISDNnumber] x75'
The transfer rate will appear in real time, updated every time 64 Kbytes of
data have been transferred.
NOTE: Many other options (e.g. bearer protocol, packet size, rate adaptation)
are available for TTY test. Please call './tty_test' for a full list or
refer to the section 'tty_test Utility' in this document.

--------------------------------------------------------------------------------
Acopy2 ISDN File Server
--------------------------------------------------------------------------------
This test allows you to test adapter and CAPI2.0 interface functionality and
link integrity using the X.75 bearer protocol.
The ACOPY2' utility is located in the '/usr/lib/eicon/divas' directory.
On the server side, please call:
'./acopy2 -cX -serve /p2048'
- where 2048 is the packet size for optimum
results
- where X is the ISDN adapter number that will
receive the call
On the client side, please call:
'./acopy2 -cY -n[myISDNnumber]:file2 file1 /p2048
- where 2048 is the packet size for optimum
results
- where Y is the ISDN adapter number that will
issue the call
ACOPY2 will transfer file2 from the remote system to file1 on the local system.
The call will be issued over the ISDN adapter Y. Once the transfer is finished
you will see the transfer rate indicated.

NOTE: Many other options (e.g. packet size, CPN, SubAddress, etc.) and commands
(e.g. receive file, send file, transfer directory list etc.)
are available. Please call './acopy2' for a full list.

--------------------------------------------------------------------------------
AFAX2 Fax Server
--------------------------------------------------------------------------------
This test allows you to test adapter and CAPI2.0 interface functionality and
link integrity using the Fax G3 bearer protocol.
The AFAX2 utility is located in the '/usr/lib/eicon/divas' directory.
On the server side, please call: './afax2 -serve -cX'
- where X is the ISDN adapter number
that will receive the call.
On the client side, please call: './afax2 file.[sff,txt] myISDNnumber -cY'
- where Y is the ISDN adapter number
that will issue the call.
AFAX2 will transmit the text file 'file.txt' or SFF file 'file.sff' as fax
document to the fax server. The received document will be saved in file
'RCV.SFF'.

NOTE: Many other options (e.g. packet size, transmission speed, ECM,
compression, fax ID, headline, etc.) and commands (e.g. poll etc.)
are available. Please call './afax2' for a full list.

--------------------------------------------------------------------------------
CONFIGURING THE DIVA SERVER TTY SERIAL PORTS
--------------------------------------------------------------------------------
The configuration of each TTYDSxx port is accomplished through the use of an
extensive list of AT commands. The following is a comprehensive list of all
AT commands that can be used:

AT Commands
--------------------------------------------------------------------------------
AT A - ANSWER. Accepts an incoming call that has been
indicated by a "RING". (If the S0 register is set
to zero, TTY indicates a RING until the call is
answered by the ATA command or released.)

AT D[T|P][number] - DIAL. Dials the given number.
Dial tone (T) or dial pulse (P) are ignored.
[Number] can have the following format:
Calling Party No.[| Subaddress][^56k][+iYYYY | +p=btx]
YYYY - Eicon-specific +I command (please read below).

AT E[0|1] - Echo mode. In echo mode, all commands sent to the
modem are echoed back to the terminal.
0 - Echo mode OFF. In command mode, the modem does
not reflect the data that it received from the
application back to the application.
1 - Echo mode ON. In command mode, the modem reflects
all data that it received from the application
back to the application.

AT I[N] - INFO. Returns the modem identification string.
N : integer [0 ... 9]

AT H[0] - HANGUP. Disconnects the line.

AT O[1] - ONLINE. Switches the modem from command mode to
data mode.

AT Q[0|1] - QUIET. In quiet mode the modem driver does not
return result codes for the commands.
0 - Returns result codes.
1 - Suppresses result codes.

AT V[0|1] - VERBAL Mode. In verbal mode the modem driver returns
result codes in plain text. Otherwise it returns
numeric result codes.
0 - Numeric result codes.
1 - Plain text result codes.

AT L[N], N[N],
M[N], Y[N] - Commands accepted for compatibility reasons.
N : any integer

AT X[0...4] - Result code reporting options. Sets normal or
extended result code reporting.
0 - Enables mimimum information only (plain CONNECT
in case of successful connection establishment,
NO CARRIER in case of dialing/answer error).
4 - Enables full information (all result codes are
reported).

AT Z[0...15] - Soft reset. Drops the connection if the modem is
in ESCAPE mode. Resets the modem and restores the
selected pre-defined modem configuration profile.

AT S[0...254]=? - Displays the value of the selected S-register.
AT S[0...254]=[0...255] - Sets the value of the selected S-register.
Currently only registers 0 and 2 are implemented.
Writing to all other registers is accepted.

S-register 0 controls the auto answer functionality.
0 - Disables auto answer. Incoming calls are
answered with an ALERT message and indicated
by RING messages (every 4 sec). The user can
investigate the call parameters, select the
appropriate profile/settings and accept the
call by the 'ATA' command.
1...254 - Enables auto answer. Incoming calls are
indicated by a RING and accepted
automatically.
255 - Ignores all incoming calls.

S-register 2 controls Escape Character.
S2 holds the value of the ASCII character used as
the escape character. The default value corresponds
to an ASCII '+' (43 decimal).
A value of 127 disabled the escape sequence process,
i.e., no escape character will be recognized.
Range: 0 ... 255
Default: 43 ('+')

S-register 27 is Bit Mapper register
Bit | Value | Result
----+-------+---------------------------------
0 | 1 | Reserved
----+-------+---------------------------------
1 | 2 | Reserved
----+-------+---------------------------------
2 | 4 | Reserved
----+-------+---------------------------------
3 | 8 | Disable 2100Hz answer tone
----+-------+---------------------------------
4 | 16 | Reserved
----+-------+---------------------------------
5 | 32 | Reserved
----+-------+---------------------------------
6 | 64 | Reserved
----+-------+---------------------------------
7 | 128 | Reserved
----+-------+---------------------------------

--------------------------------------------------------------------------------
AT\ Commands
--------------------------------------------------------------------------------
AT \V[0|1|2] - CONNECT message format.
0 - Plain CONNECT message without any connection
parameters.
1 - Full CONNECT message including connection
parameters (modulation, compression, transmit/
receive rate).
2 - Full CONNECT message in multiline format:
CONNECT TX/RX
CARRIER
PROTOCOL
COMPRESSION

AT \T[0...65535] - Inactivity timeout (sec.).
TTY releases the connection if there was no data
traffic on the interface for the time interval
specified here.

AT \D[N] - Debug level. Reserved for use by Eicon Networks.

AT \N[0..5] - Error correction control
0,1 - Turn error correction and
data compression off
2,3,4 - Turn error correction on
5 - Force error correction. Modem disconnects
if error correction can not be made

--------------------------------------------------------------------------------
AT% Commands
--------------------------------------------------------------------------------
AT %C[0..2] - Data compression control
0 - Turn data compression off
1,2,3, - Turn data compression on

--------------------------------------------------------------------------------
AT# Commands
--------------------------------------------------------------------------------
AT #CID=? - Displays CID (Caller ID) setting.
The short form of this command is 'CID?'.

AT #CID=[0...7] - Sets CID mode. The TTY indicates the origination (CID)
and destination (DAD) number in the RING and/or CONNECT
message. This enables a server application for example
to forward incoming calls directly to their
destination.
0 - no CID indication
1 - CID indication in RING message
2 - CID indication in CONNECT message
3 - CID indication in RING and in CONNECT messages
5 - CID and DAD indication in RING message
6 - CID and DAD indication in CONNECT message
7 - CID and DAD indication in RING and in CONNECT
messages

CID (or Calling Party Number) is indicated as:
RING CID: [number]
CONNECT ... CID: [number]
If a national call is indicated, '0' is inserted
in front of the number.
If an international call is indicated, '00' is
inserted in front of the number.
DAD (Destination Address) is indicated as:
RING DAD: [number]
CONNECT ... DAD: [number]

--------------------------------------------------------------------------------
AT& Commands
--------------------------------------------------------------------------------
AT &C[N] - Accepted for comaptibility reasons.
N : any integer

AT &G[0...2] - Guard Tone options.
0 - Turn Guard Tone off (default)
1 - Turn 550Hz Guard Tone on
2 - Turn 1800Hz Guard Tone on

AT &D[0...3] - Data Terminal Ready (DTR) options.
AT &Q[0...3] - Communication options.
Data Terminal Ready options (DTR options) and
Communication options (COM options) determine the
behavior of the virtual modem when DTR switches from
ON to OFF in accordance with the following table:

&D0 &D1 &D2 &D3
&Q0 N B C D
&Q1 A B C D
&Q2 C C C D
&Q3 C C C D

Actions:
A - If the modem is online, it hangs up and responds
with OK.
B - If the modem is online, it switches to command mode
(as if an ESCAPE sequence was detected) and sends
OK.
C - If the modem is online, it hangs up and responds
with OK.
D - If the modem is online, it hangs up and the current
profile defaults are restored.
N - No action is taken, the DTR drop is ignored.

AT &K[0...6] - Terminal flow control options. Defines the flow control
mechanism.
0 - Disables flow control.
1 - Enables RTS/CTS local+remote flow control
(obsolete).
2 - Enables XON/XOFF flow control (obsolete).
3 - Enables RTS/CTS local+remote flow control.
4 - Enables XON/XOFF flow control.
5 - Enables transparent XON/XOFF flow control.
6 - Enables both XON/XOFF & RTS/CTS flow control
(voice).

AT &V - Displays the current configuration, the last number that
has been dialed (last DIAL to), and the calling party
number of the last incoming call (last RING from).

AT &V1 - Displays current settings and settings of all available
profiles.

AT &F[1...15] - Resets the modem and restores the selected pre-defined
modem configuration profile.
AT&F sets factory defaults for current profile.

--------------------------------------------------------------------------------
AT+ Commands
Eicon-specific commands which may come either as part of a normal AT-command
or as part of a called party number
--------------------------------------------------------------------------------
AT +iA[number] - Accepted address.
Incoming calls are only accepted if the called party
number equals the phone number configured here.
If a subaddress (SUB) needs to be entered, it must be
separated from the rest of the number by a vertical
character [|] (also called the pipe symbol).
Addresses are compared backwards. So, if you set
accepted address to 12, all called party numbers that
end with 12, e.g. 12, 812, 384012, match the configured
address.
If you use this AT-command in sequence (in one line)
with other AT-commands, it should either be the last
command or it should be followed by a semi-colon ';'.
Example:
The AT-command sequence AT&F14, AT#CID=7, ATS0=1,
AT+IA12 can be written as:
AT&F14#CID=7S0=1+IA12 or AT&F14+IA12;#CID=7S0=1

AT +iO[number] - Origination address.
This number is placed as the origination address.
If a subaddress (SUB) needs to be entered, it must be
separated from the rest of the number by a vertical
character [|] (also called the pipe symbol).
If you use this AT-command in sequence (in one line)
with other AT-commands, it should either be the last
command or it should be followed by a semi-colon ';'.
Example:
The AT-command sequence AT&F1, ATE1, ATV1, AT\V1,
AT+IO384100, ATD384012 can be written as:
AT&F1E1V1\V1D384012+IO384100 or
AT&F1E1V1+IO384100;\V1D384012

AT +iB[2...9] - B-channel data adaptation rate, if supported by used
bearer protocol (for example V.110).
2 - 1200 bps
3 - 2400 bps
4 - 4800 bps
5 - 9600 bps
6 - 19200 bps
7 - 38400 bps
8 - 48000 bps
9 - 56000 bps

AT +iC[0|1] - Determines whether the modem stays in command mode
after call setup.
0 - Stays in command mode.
1 - Switches to data mode.

AT +iD[0...255] - Delay for AT-command response (msec).
0 - AT-command response is sent immediately.
1...255 - AT-command response is delayed.

AT +iF[0...5] - RNA Framing. Determines if the ASYNC/SYNC conversion
module is inserted on top of OSI Layer 3 and which
mode this module assumes.
0 - No framing check (pass data transparently).
1 - Force synchronous conversation (PPP).
2 - Force asynchronous conversation (PPP).
3 - Force synchronous conversation (RAS).
4 - Force asynchronous conversation (RAS).
5 - Detects required conversation by analyzing incoming
data packets.

AT +iGXXX - RNA patches. Controls the behavior of the ASYNC/SYNC
PPP conversion module.
XXX - Bit Mask. The bits have the following meaning:
Bit 7 - Pass LCP (default is track).
Bit 6 - Keep TX ACCM (default is delete).
Bit 5 - Keep RX ACCM (default is add).
Bit 4 - Force patch of IPCP.
Bit 3 - Pass IPCP (default is track).
Bit 2 - Reserved, should be zero.
Bit 1 - Reserved, should be zero.
Bit 0 - Reserved, should be zero.

Note on ASYNC/SYNC conversion module:
In the beginning we must escape every control character
when we explode a sync frame cause this is the initial
state for PPP over asyncronous lines (expected by RNA).
Thus 0xffffffff is set as the initial receive ACCM.
To prevent the overhead of escaping every control
character if the peer does not send an ACCM with its
configure request, we add a null ACCM to such a request
by default.
For asynchronous frames from RNA we can assume that
such frames will never contain spurious unescaped
control characters. Thus, 0x00000000 is set as the
initial transmit ACCM.
Because some routers (for example Cisco and NetGW)
reject an ACCM on synchronous links we remove (but
remember) the ACCM from outgoing configure requests
by default.

AT +iL[N] - Maximum data frame length.
N - integer 0 ... 2048
0 - Defaults to the maximum frame supported by the
adapter.

AT +iM[1...6] - Working mode.
1 - Normal operation mode. TTY does not try to preserve
the protocol data unit boundaries (streaming). This
mode fully emulates the behavior of a 'classic'
modem or terminal adapter connected via a serial
interface.
2 - Fax mode. TTY switches to this mode as soon as a
FAX CLASS 1 or FAX CLASS 2 command is detected.
3 - Voice mode (bit-transparent access to B-channel
data).
4 - RNA mode. TTY operates in framing mode, investigates
protocol data units and provides ASYNC/SYNC
conversion if necessary.
5 - BTX over ISDN mode.
6 - Frame mode. The TTY preserves the frame boundaries
of the ISDN data frames. Unfortunately, the Linux
TTY interface will stream the data again.

AT +iNXXX - Numbering plane identifiers for destination/origination
address.
XXX can have 2 formats:
Number between 0 ... 127 - Specifies the numbering plane
identifier for the
destination address only. The
numbering plane identifier of
the origination address is
set to 127.
Number 1/Number 2 - Specifies the identifiers for
the destination address
(number 1) and the
origination address
(number 2). Both numbers
should be in the range of
0 ... 127.

AT +iP[1...12] - Specifies the protocol stack used to transfer bearer
data.
1 - L1 - HDLC, L2 - X75SLP and V.42bis data compression
autodetection in case of incoming connection,
L3 - transparent
2 - L1 - V.110 synchronous mode,
L2 and L3 - transparent
3 - L1 - V.110 asynchronous mode,
L2 and L3 - transparent
4 - L1 - analog modem (synchronous mode),
L2 - V.42+V.42bis autodetect, L3 - transparent
5 - L1 - analog modem with full negotiation,
L2 - V.42+V.42bis autodetect, L3 - transparent
6 - L1 - HDLC, L2 - V.120, L3 - TA
7 - L1 - Fax, L2 - transparent,
L3 - T.30 with ECM, T.6, MR, MMR, polling
8 - L1, L2 and L3 - transparent
9 - L1 - HDLC, L2 and L3 - transparent
10 - L1 - HDLC, L2 - X75SLP, L3 - BTX
11 - external device 0
12 - L1 - HDLC, L2 - X.75SLP and data compression
autodetection in accordance with V.42bis,
L3 - transparent

AT +iSXXX - Service Indicator/Additional Service Indicator.
Every TTY profile has its own Service Indicator/
Additional Service Indicator to tell the remote site
which kind of connection the user wants to establish
for outgoing calls and to filter incoming calls. The
command affects the Low-Layer Capabilities (LLC) element
on the SETUP message.
You can overwrite default values by the AT+ISXXX command
if necessary.
XXX can have two formats:
Number between 1 ... 7 - Sets the Service Indicator to
the provided value. The
Additional Service
Indicator is set to zero.
Number 1/Number 2 - Number 1: Service Indicator. It
should be in the range
of 1 ... 7.
Number 2: Additional Service
Indicator.
It should be in the range
of 0 ... 255.
1/1 ISDN Voice call 3,1 kHz
1/2 Analog Voice call
1/3 ISDN Voice call 7 kHz
2/1 Fax Group 2
2/2 Fax Group 3
2/3 Data over modem
connection
2/4 BTX over modem connection
7/0 64000 bps Data
7/170 56000 bps Data
7/197 V.110 Rate Adaptation

At +iT[0...255] - ISDN trace options. Reserved for use by Eicon.

AT +iH[0|1] - Erases/sets slow application workarounds.
0 - Erases workarounds. Equivalent to AT command:
AT+IW=0+IX=0+IY=0+iZ0
1 - Sets workarounds. Equivalent to AT command:
AT+IW=1+IX=81+IY=8+iZ80

AT +iW[Val] - Defers receive notifications to 'Val' bytes/millisecond.
Val should be in the range of 0 ... 64000.

AT +iX[Val] - Respects read block size and defers receive
notifications. Val should be in the
range of 0 ... 64000.

AT +iY[Val] - Defers transmission to 'Val' bytes/millisecond.
Val should be in the range of 0 ... 8.

AT +iZ[Val] - Splits large frames into 'Val' byte segments.
Val should be in the range of 0 ... 2048.

AT +iU=<BC>
AT +iU=<BC/LLC> - Sometimes the Service Indicator and
Additional Service Indicator is not flexible enough
to indicate all necessary information in
bearer capabilities (BC) and low-layer capabilities (LLC)
that the user wants to provide for an outgoing call.
In this case the user can set these values directly.
For example, to indicate a V.110 call with 38400 bps
and the appropiate flow control option, the user can
enter the command: AT+IU=<8890214d00bb> to specify
the BC value.
The provided BC and LLC values are used without any
verification (except max. length of information
element) to create the SETUP message sent over the
D-channel. This allows the use of proprietary BC/LLC
values not yet covered by standards.

AT +iI - Reserved.

AT +iE - Select global TTY mode.
This command is used on brocken ISDN links that
provide wrong call type information over the
signalling channel.
If operating on like channels it is necessary to
enforce TTY driver to handle all incoming calls in
specific way independent of the signalled call type.
This command affects all virtual tty interfaces exposed
by Diva TTY driver and can be changed only by driver
unload or other +IE command.

Currently this feature is implemented for China PIAFS
links (where it additional activates China specific
extensions to PIAFS protocol):
AT&F16+IE=piafs32k - China 32K PIAFS link
AT&F17+IE=piafs64k - China 32K PIAFS link
AT&F18+IE=piafs - China variable speed PIAFS link

AT+IE=none - Put all tty interfaces back
in 'default' mode (i.e. signalling
information will be used to
determine the call type).

AT +iQ=[N] - Sometimes it is necessary to bind outgoing call to
specific adapter (by default first available adapter
is selected). This command allows to bind TTY interface
to specified adapter by specification of
adapter number (N):
oX - bind TTY to adapter X for all outgoing calls
iX - bind TTY to adapter X for all incoming calls
aX - bind TTY to adapter X for all calls
o0 - erase TTY binding for outgoing calls
i0 - erase TTY binding for incomming calls
a0 - erase TTY bindings for incoming and outgoing calls
? - display current bindings

AT +MF=Data Bits,Parity,Stop Bits
- Set UART framing parameters
Data Bits:
8 - 8 data bits
7 - 7 data bits
5 - 5 data bits
Parity:
N - none
O - odd
E - even
S - space
M - mark
Stop Bits:
1 - one stop bit
2 - two stop bits

The transmission rate is defived from actual
selected Rx/Tx transmission speed (+MS command).

Example:
AT+MF=8,N,1 - select 8 databits, no parity and
one stop bit.

AT +MF? - Report current selected framing
AT +MF=? - Report list of supported parameters

AT +MS=Modulation,Automode,Min Rx,Max Rx,Min Tx,Max Tx
- Set modulation and transmission speed
Modulation:
V90, V90D - V.90, Central Office (Digital) Modem
(33600 Rx, 56000 Tx)
V90A - V.90, Analog Modem (56000 Rx, 33600 Tx)
V34 - V.34 (33600 Bps) Analog Modem
V32b - V.32 bis (14400 Bps) Alalog Modem
V32 - V.32 (9600 Bps) Alalog Modem
V22b - V.22 bis (2400 Bps) Alalog Modem
V22 - V.22 (1200 Bps) Alalog Modem
V23 - V.23 (1200/75 or 75/1200 Bps) Alalog Modem
B212A - Bell 212 (1200 Bps) Analog modem
B103 - Bell 103 (300 Bps) Analog modem
Automode:
Is an optional parameter that enables or disables
automatic modulation negotiation using V.8 bis/V.8 or
V.32 bis Annex A.
0 - Automode disabled
1 - Automode enabled
Min Rx:
Is an optional parameter which specifies the lowest rate
at which the modem can receive during a connection.
This value is decimal coded, in units of bps.
Max Rx:
Is an optional parameter which specifies the highest
rate at which the modem can receive during a connection.
This value is decimal coded, in units of bps.
Min Tx:
Is an optional parameter which specifies the lowest rate
at which the modem can transmit during a connection.
This value is decimal coded, in units of bps.
Max Tx:
Is an optional parameter which specifies the highest
rate at which the modem can transmit
during a connection.
This value is decimal coded, in units of bps.

Rx Transmission rates for V.90a (Bps),
Tx Transmission rates for V.90 (Bps):
56000,54666,53333,52000,50666,49333,48000,46666,45333,
44000,42666,41333,37333,33333
Tx Transmission rates for V.90a (Bps),
Rx Transmission rates for V.90 (Bps),
Transmission rates for V.34 (Bps):
33600,31200,28800,26400,24000,21600,19200,16800,14400,
12000,9600,7200,4800,2400
Transmission rates for V.32b (Bps):
14400,12000,9600,7200,4800
Transmission rates for V.32 (Bps):
9600,4800
Transmission rates for V.22 bis (Bps):
2400, 1200
Transmission rate for V.22 (Bps):
1200
Transmission rate for V.23 (Bps):
1200
Transmission rate for V.21 (Bps):
1200
Transmission rate for B212A (Bps):
1200
Transmission rate for B103 (Bps):
300

Example:
AT+MS=V90a - select V.90, automode enabled,
max transmission rate
AT+MS=V22b,0 - select V.22 bis, automode disabled,
max transmission rate
AT+MS=V22b,0,1200,1200,1200,1200
- select V.22 bis,automode disables,
transmission rate set to 1200 Bps

AT +MS? - Report current selected modulation and transmission speed
AT +MS=? - Report list of supported parameters

--------------------------------------------------------------------------------
Fax Commands (excerpt of complete list)

Eicon Diva Server TTY supports FAX CLASS 1 and FAX CLASS 2 command set.
--------------------------------------------------------------------------------
AT +FCLASS? - Queries the configured modem class.
0 = Data mode
1 = EIA class 1
2 = EIA class 2

AT +FCLASS=? - Displays all supported modem classes.

AT +FCLASS=[N]- Configures the modem for modem class [N].

AT +FMFR? - Returns the name of the modem manufacturer.

AT +FMDL? - Returns the name of the modem model.

AT +FREV? - Returns the product version.

--------------------------------------------------------------------------------
Supported TTY Profiles
--------------------------------------------------------------------------------
You can always display all available profiles by the 'AT&V1' command.
The best way to view the settings of a profile is to select this profile by the
'AT&F[Profile Number]' command and then issue the 'AT&V' command.
Follow the description of most important profiles, that can be selected by
'AT&F[Profile]' or 'AT&Z[Profile]' commands.
Some of these profiles are selected automatically, as soon as the appropriate
AT command is detected (Fax).

PROFILE 14: Autodetection of B-channel protocol.
For incoming calls you can use autodetection of the
B-Channel protocol. In this mode the TTY processes as follows:
STEP 1: Analysis of BC/LLC if present.
If enough information is given in BC/LLC, the appropriate
protocol is selected.
STEP 2: If not enough information is given in BC/LLC, the first
frame that is received over the B-channel is analyzed and
the appropriate protocol is selected.
The following protocols can be autodetected in this way:
HDLC/Transparent/Transparent
HDLC/X.75/Transparent
HDLC/X.75 with V.42bis data compression/Transparent
HDLC/V.120/Transparent
HDLC/V.120 with V.42bis data compression/Transparent
V.110/Transparent/Transparent
Analog Modem with full negotiation (up to V.90 central
office) / V.42+V.42bis or V.42 or Transparent - buffered
mode/Transparent
PIAFS/PIAFS/Transparent
STEP 3: B-channel data is analyzed and the ASYNC/SYNC PPP
conversion module is inserted if necessary.

PROFILE 1: X.75/Transparent/Transparent protocol stack.
Data compression in accordance with V.42bis is detected
automatically for incoming calls.

PROFILE 2: V.110 synchronous mode.

PROFILE 3: V.110 asynchronous mode.

PROFILE 4: Synchronous modem with V.42/V.42bis.

PROFILE 5: Asynchronous modem with full negotiation and V.42/V.42bis.

PROFILE 6: V.120, 64000 bps.

PROFILE 7: V.120, 56000 bps.

PROFILE 8: Bit transparent access to B-channel data.
Note: By default, this profile does not switch to data mode
after the connection was established.

PROFILE 9: This profile can be used to select the
HDLC/Transparent/Transparent protocol stack, that is widely used
for PPP connections.
Note: This profile switches to numeric mode (atv0) by default.

PROFILE 10: Same as PROFILE 9, but with 56000 bps.

PROFILE 11: BTX.

PROFILE 12: BTX.

PROFILE 15: X.75 with data compression in accordance with V.42bis.
This profile should be used for outgoing calls if you wish to use
data compression in accordance with V.42bis. If the opposite side
does not support data compression, the connection will be
established without data compression.

PROFILE 16: PIAFS with 32KBit/Sec

PROFILE 17: PIAFS with 64LBit/Sec

PROFILE 18: PIAFS with 64LBit/Sec, transfer rate autodetect

--------------------------------------------------------------------------------
'ESCAPE' Sequence (+++)
--------------------------------------------------------------------------------
You can switch from ONLINE mode (data transfer mode) to ESCAPE mode
(command mode with the connection established in the background) by means of
the ESCAPE sequence.
The ESCAPE sequence includes the following procedure:
1. No data sent to TTY for 2 seconds.
2. Three '+' characters are sent. The time interval that passes between
two '+' characters should not exceed 1 sec.
3. No data sent to TTY for 2 seconds.
4. TTY switches to ESCAPE mode and sends OK response (format of
response depends on ATV and ATQ commands).

You can switch from ESCAPE back to ONLINE mode if you issue the 'ATO' command.
You can drop the connection and return to COMMAND mode if you issue the ATH
command.
In ESCAPE mode you can read the S-registers, view the modem profile, and change
port timeout and TTY interface related values, but you cannot issue DIAL and
ANSWER commands.

--------------------------------------------------------------------------------
AT command responses
--------------------------------------------------------------------------------
MEANING | DIRECT FORM | NUMERIC FORM
--------------------------------------------------------------------------------
Command accepted | OK | 0
--------------------------------------------------------------------------------
CONNECT 300 bps | CONNECT, CONNECT 300 | 1
--------------------------------------------------------------------------------
Ring indication | RING | 2
--------------------------------------------------------------------------------
Carrier lost, | |
switched back | NO CARRIER | 3
to command mode | |
--------------------------------------------------------------------------------
Invalid command, | |
command was not | ERROR | 4
accepted | |
--------------------------------------------------------------------------------
CONNECT 1200 bps | CONNECT, CONNECT 1200 | 5
--------------------------------------------------------------------------------
Dial attempt failed | |
(L1 error, L2 error,| NO DIALTONE | 6
no free B-channel) | |
--------------------------------------------------------------------------------
Opposite side has | |
rejected the call | BUSY | 7
or busy | |
--------------------------------------------------------------------------------
No equipment on | |
opposite side has | NO ANSWER | 8
answered the call | |
--------------------------------------------------------------------------------
Successful connect | CONNECT, CONNECT + speed and| 9
to opposite side | norm. Depends on AT\V |
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
TTY control interface (/dev/ttydsctrl and ttydsctrl utility)
--------------------------------------------------------------------------------

Eicon Diva TTY driver allows control of state of TTY interfaces through
additional device node with MAJOR 8 and MINOR 0.
Default installation creates this device node with name '/dev/ttydsctrl'.

The command are formated as ASCII strings and have following format:
N:command_string, where:
N - decimal number, selects TTY interfrace
command_string - command to be issued on the TTY interface

All commands can be issued via "write" or "ioctl" system call.
The return value of system call (success or failed) is used to indicate the
result of the operation.
In order to issue command via "IOCTL" interface user should write command
including terminating zero in one buffer with length of 64 bytes.
IOCTL command will receive output (if any) in the same bufer, and ioctl command
will return amount of bytes stored in the buffer.
"ttydsctrl" utility can be used to access Eicon Diva TTY control interface via
"ioctl" system call.

This interface allows:
1. check if selected TTY interface is opened
Used command string: 'open'
If interface is opened operation will return 'success'
If interface is not opened operation will return 'failed'
2. check if selected TTY interface is online
Used command string: 'dcd'
If interface is online (i.e. not in command mode) this operation will
return 'success'
If interface is offline or not opened operation will return 'failed'
3. Issue 'HANGUP' command to the selected TTY interface.
If interface is online, then the result of this command same,
as issued ATH command.
Used command string: 'h'
If command was successful this command will return 'success'
If command failed (TTY interface not opened by application) this command
will return 'success'
3. Issue 'HANGUP+RESET' command to the selected TTY interface.
If interface is online, then the result of this command same,
as issued ATZ command.
Used command string: 'z' or 'zX', where X is decimal number of the
Eicon Diva TTY profile
If command was successful this command will return 'success'
If command failed (TTY interface not opened by application or invalid
profile number) this command will return 'failed'
4. Issue AT command sequence to selected TTY interface.
This command can be issued only if modem is offline.
Used command string: any valid command string
If command was successful this command will return 'success'
If command failed (TTY interface not opened by application, invalid
command or TTY interface is online) this command will return 'failed'
5. In case "ioctl" interface is used (IOCTL command code 0x3701) then
additional "status" message can be issued in orger to obtain modem state
(online/offline) and parameters of current/last connections (used protocol,
transmission speed). The output is stored in the same buffer that was used
to pass command to Eicon Diva TTY interface as zero terminated ASCII string
including terminating zero.

All descriebed above operations happens fully hidden from application that
really owned the selected TTY interface.

Example: Use "ttydsctrl" application to retrieve status of TTY interface 2
(MINOR 2, device node /dev/ttyds2)
./ttydsctrl -c 2 -status
if [ $(($?)) -ne 0 ]
then
echo "Operation failed, TTY 2 not opened by application ?"
fi

Example: Use "ttydsctrl" application to issue "AT&F5+MS=V22B,0;S0=1;+MF=7,e,1"
AT command to TTY interface 1 (MINOR 1, device node /dev/ttyds01)
./ttydsctrl -c 1 -command "AT&F5+MS=V22B,0;S0=1;+MF=7,e,1"
if [ $(($?)) -ne 0 ]
then
echo "AT Command failed. TTY 1 not opened by application ?"
echo "Or invalid AT command ?"
echo "Or TTY interace is online ?"
else
echo "Modem hangup+reset OK, TTY will not accept any calls more"
echo "and profile settings was changed to 5 (Analog Modem)"
fi

The fact that all commands are build as ascii strings and can be issued via
'write' system call allow to use 'echo' command (attention return code is
not always valid for some kernels/distrubutions, plese use "ttydsctrl" if you
will get problems):

Example: Check if TTY interface 10 (MINOR 10, device node /dev/ttyds10) is
opened.

echo "10:open" > /dev/ttydsctrl
if [ $(($?)) -ne 0 ]
then
echo "Interface is closed"
else
echo "Interface is opened"
fi

Example: Check if TTY interface 2 (MINOR 2, device node /dev/ttyds02) is
online.

echo "2:dcd" > /dev/ttydsctrl
if [ $(($?)) -ne 0 ]
then
echo "Interface is online"
else
echo "Interface is offline (command mode)"
fi

Example: Hang up TTY interface 120 (MINOR 120, device node /dev/ttyds120)

echo "120:h" > /dev/ttydsctrl
if [ $(($?)) -ne 0 ]
then
echo "Hangup failed. TTY 120 not opened by application ?"
else
echo "Modem hangup OK"
fi

Example: Hang up and reset TTY interface 1 (MINOR 1, device node /dev/ttyds01)

echo "1:z" > /dev/ttydsctrl
if [ $(($?)) -ne 0 ]
then
echo "Hangup+Reset failed. TTY 1 not opened by application ?"
else
echo "Modem hangup+reset OK, TTY will not accept any calls more"
echo "and original profile settings are recovered"
fi

Example: Hang up and reset TTY interface 1 (MINOR 1, device node /dev/ttyds01)
to profile 5 (Analog Modem)

echo "1:z5" > /dev/ttydsctrl
if [ $(($?)) -ne 0 ]
then
echo "Hangup+Reset failed. TTY 1 not opened by application ?"
echo "Or invalid profile number selected ?"
else
echo "Modem hangup+reset OK, TTY will not accept any calls more"
echo "and profile settings was changed to 5 (Analog Modem)"
fi

Example: Issue "AT&F5+MS=V22B,0;S0=1;+MF=7,e,1" AT command to TTY interface 1
(MINOR 1, device node /dev/ttyds01)

echo "1:at&f5+ms=v22b,0;S0=1;+mf=7,e,1" > /dev/ttydsctrl
if [ $(($?)) -ne 0 ]
then
echo "AT Command failed. TTY 1 not opened by application ?"
echo "Or invalid AT command ?"
echo "Or TTY interace is online ?"
else
echo "Modem hangup+reset OK, TTY will not accept any calls more"
echo "and profile settings was changed to 5 (Analog Modem)"
fi

--------------------------------------------------------------------------------
Setting up a Linux PPP (RAS) Server
--------------------------------------------------------------------------------
Due to fact that Diva Server TTY provides ASYNC/SYNC conversion any PPP
software can be used.
For information on how to set up a Linux PPP Server refer to the documentation
provided with your Linux system. Go to the /usr/doc/howto directory and open
the manuals man pppd or man mgetty.

--------------------------------------------------------------------------------
Uninstalling Diva Server for Linux
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Unloading the Diva Server modules
--------------------------------------------------------------------------------
The unloading of the Diva Driver modules can be accomplished simply by
executing the 'divas_stop.rc' script, located with the Diva files in the
'/usr/lib/eicon/divas' directory.
If you wish to stop and unload Diva drivers manually, then you have to proceed
as described below:

NOTE: You must be logged-in as root or call 'su'.
1. Login as 'root' (or use 'su')
2. If you have started any tools that access the CAPI or Diva Server TTY
interfaces, please stop these tools so that these interfaces are not in use.
3. If you have modified /etc/inittab or /etc/ttys to start getty/mgetty/ppp on
one of Diva TTY interfaces, please remove these entries from these files and
call 'kill -HUP 1' (or kill appropriate processes manually).
4. Check that Divastty, capi and divacapi modules are not busy (call 'lsmod' to
check it).
5. Execute: 'rmmod capi && rmmod divacapi && rmmod kernelcapi' to tunload
CAPI drivers
6. Execute: 'rmmod Divatty' to unload Diva Server TTY drivers
7. Execute: 'rmmod diva_idi && rmmod divas && rmmod divadidd' to stop and
unload XDI drivers

--------------------------------------------------------------------------------
Uninstalling the Diva Server Package
--------------------------------------------------------------------------------
In order to uninstall the Diva Server for Linux package, please login
as 'root' (or use 'su') and execute:
'rpm -i divas4linux_a_b_cc_dd_ee-ff-xxx.yy-z',
where 'divas4linux_a_b_cc_dd_ee-ff-xxx.yy-z' is name of installed rpm package
without '.i386.rpm' extension. For example if you have installed package
'divas4linux_2_2_16-101.2-1.i386.rpm' then you should execute
'rpm -e divas4linux_2_2_16-101.2-1' in order to uninstall this package.

NOTE1: contained in the RPM package pre-uninstall script will stop and unload
all drivers by means of '/usr/lib/eicon/divas/divas_stop.rc' and remove
symbolic links used to start Diva drivers on system startup.
In case 'divas_stop.rc' configuration script will detect that drivers
still in use (some application/driver still access one of interfaces) and
can't be stopped then uninstalling process will be abouted before any
changes was applied.
NOTE2: In case you not know that for applications/drivers access interfaces
of Diva drivers or you can't stop these applications, please execute
'sh /usr/lib/eicon/divas/cfg/cfg_util.sh 2' (this will remove symbolic
links: S03DIVA4LINUX from the '/etc/rc.d/rc...d or /sbin.init.d/rc...d
directories) and reboot your system.
After reboot drivers will not be loaded more by system start and can be
uninstalled. You can identify applications/drivers that accessed Diva
drivers by error messages on console and in 'var/log/messages' file.
NOTE3: If you do not know the name of installed RPM package,
please execute: 'rpm -q -a | grep divas4linux' in order to get
package name from database maintained by RPM.

You can manually remove the Diva Server for Linux files from you system,
but this is not recommended, as it will leave the package entry in the RPM
database and may cause problems reinstalling the package.
One of reason's for manual removal is if RPM database was corrupted/destroyed.
In order to uninstall Diva Server package manually, please proceed as described
below:
1. Login as root (or use 'su')
2. Change working directory to '/usr/lib/eicon/divas'
('cd /usr/lib/eicon/divas')
3. Execute: 'sh ./cfg_util.sh 2'
4. Execute: './divas/divas_stop.rc'. If 'divas_stop.rc' will fain to stop and
unload the drivers, then please proceed as desctibed in NOTE1 and NOTE2
above.
5. Change working directory to '/usr/lib/eicon'
('cd /usr/lib/eicon')
6. Remove the files: rm -rf '/usr/lib/eicon/divas'
7. Remove doc files: rm -rf /usr/doc/packages/divas4linux*

--------------------------------------------------------------------------------
Troubleshooting
--------------------------------------------------------------------------------
The trace utility 'divactrl' can help you analyze problems if you
have trouble with connections or functionality.
'divactrl' provides the following capabilities for adapter tracing and
debugging:
1. Access to the adapter's XLOG interface. The XLOG interface is a
low level debug interface that should be used if other debug
capabilities (via the management interface) fail.
2. Access to the adapter memory that allows to create a 'core' dump of
the adapter. It can be used in case of problems with loading or starting
the adapter or if the adapter state changed to 'trapped'. 'core' image can
be used by Eicon for post mortem debugging and problem analysis.
3. Access to the 'Trace' directory in the adapter management interface (MLOG).
Tracing and debugging capabilities via the management interface allow you
to access B- and D-channel data and Layer 1 interface events and to debug
or trace messages generated by the Diva adapter.

--------------------------------------------------------------------------------
XLOG Trace and Debug Utility
--------------------------------------------------------------------------------
The XLOG trace and debug utility provides access to the adapter's XLOG
interface. The XLOG interface is a low level debug interface that should be
used if other debug capabilities (via the management interface) fail or cannot
be used for other reasons. The following information is accessible via the
XLOG interface:
- D-channel traces
- B-channel traces (first 24 bytes)
- Layer 1 interface events
- Layer 2 events
- Debug information

You can access this information via:
'./divactrl load -c X -ReadXlog': Read XLOG information from
adapter 'X', decode it and print it
to standard output.
'./divactrl load -c X -ReadXlog -File Y.txt' : Read XLOG information from
adapter 'X', decode it and write it
to file Y.txt.
'./divactrl load -c X -FlushXlog': Read XLOG information from
adapter 'X', decode it and print it
to standard output. Exit after
no more XLOG messages are available.
'./divactrl load -c X -FlushXlog -File Y.txt': Read XLOG information from
adapter 'X', decode it and write it
to file Y.txt. Exit after no more XLOG
messages are available.

--------------------------------------------------------------------------------
Core Dump Generation Utility
--------------------------------------------------------------------------------
In case the adapter state is changed to 'trapped' and you cannot access the
adapter's debug or trace information via XLOG (i.e. adapter firmware problem
has taken place), you can create a core dump of the adapter memory. This file
can be used by Eicon to extract debug information and analyze the adapter
state. To generate a core dump of the Diva adapter 'X' and store it to file
core.bin, execute: './divactrl load -c X -CoreDump -File core.bin'

--------------------------------------------------------------------------------
MLOG Trace and Debug Utility
--------------------------------------------------------------------------------
The MLOG trace and debug utility provides access to the 'Trace' directory
of the adapter's management interface that provides the following tracing,
debugging, and diagnostic information:
- D-channel traces
- B-channel traces
- Layer 1 interface events
- Layer 2 events
- Debug information

MLOG is able to control wich kinds of events should be traced. For example,
you can turn specific log events ON or OFF or specify a maximum length of
B-channel data, that should be logged. MLOG provides notifications in case of
MLOG trace buffer overflow. Multiple instances of the MLOG application (up to 5)
can run at the same time, independently of one another and each with its
own set of parameters.
To start MLOG, please execute: './divactrl mlog [parameters]'

The following tables list the parameters that can be used with MLOG:

- Control of output
Command line switches
------------------------------------------------------------------------------
-o - Output formatted and converted log stream to STDOUT and control
messages to STDERR. Normally, MLOG writes its output to the
MLOGXXX.txt file. XXX is the selected adapter number (1 by
default). This command cannot be used together with the '-w' command
and overwrites the '-w' command.
-wXXX - Write formatted and converted log stream to a ring buffer with
maximum size of XXX KB. Range 128KB < XXX < 257 MB. Smaller values
than 128KB will be set to 128KB. Ring buffer will be created as
4 files: MLOG.0, MLOG.1, MLOG.2 and MLOG.3. The information can be
recovered from the ring buffer by means of the '-r' command line
option. The '-w' command cannot be used together with the
'-o' command. The '-o' command overwrites the '-w' command.
-rXXX - Recover information from the ring buffer and write it to file XXX.

- Adapter selection
Command line switches
------------------------------------------------------------------------------
-c XXX - Select adapter number XXX.

- Control of B-channel trace
Command line switches
------------------------------------------------------------------------------
-b - Turn B-channel trace off.
-lXXX - Set maximum B-channel data trace length to XXX. If the entire
B-channel data packet is longer than XXX, then only the first
XXX bytes are written to the log interface.
#XXX - Select B-channel. Allows tracing of B-channel data only for
B-channels specified in the XXX. XXX is a 32-bit hex value. If
bit N is set then tracing of appropriate B-channel is allowed.
Example: 0x03 returns trace for B-channel 1 and B-channel 2

- Event Control
Command line switches
------------------------------------------------------------------------------
-s - Turn debug events from B-channel protocol code off.
-d - Turn D-channel traces off.
-t - Turn IDI interface traces off.

- Help
Command line switches
------------------------------------------------------------------------------
-? - Display help screen in readable (paged) form.

You can control events generated by MLOG at run time by the following commands:

- Help
Command line switches
------------------------------------------------------------------------------
? - Display help screen.

- Control
Command line switches
------------------------------------------------------------------------------
q - Stop tracing and exit MLOG.

- Control of B-channel trace
Command line switches
------------------------------------------------------------------------------
b - Turn B-channel trace off.
f - Set maximum B-channel data trace length. If the entire B-channel
data packet is longer than requested, only the first bytes are
written to the log interface.
# - Select B-channel trace mask. Allow trace of B-channel data only
for B-channels specified in the mask. Trace mask is a 32-bit hex
value. If bit N is set then tracing of the corresponding B-channel
is allowed.
Example: 0x03 returns trace for B-channel 1 and B-channel 2.

- Event control
Command line switches
------------------------------------------------------------------------------
s - Enable/disable (toggle) trace events from protocol code.
d - Enable/disable (toggle) D-channel traces.

--------------------------------------------------------------------------------
DCHANNEL trace and d-channel health monitoring utility
--------------------------------------------------------------------------------

'divactrl' package contains D-channel trace tools that allows to capture
D-channel messages and monitor Layer1/Llayer2 state of the isdn interface on
selected adapter, and operates in two modes: trace mode and monitor mode.

In trace mode 'D-channel' monitor operates like one ISDN analyse/trace tool.
This output can be traced for different events in order to create own
monitoring tools.
To start D-channel monitoring tool in trace mode please execute:

divactrl dchannel -c XXX [optional parameters]

where:
XXX - Logical adapter number to trace, mandatory

Started without optional parameters D-channel monitoring tool captures
all messages received or sent over D-channel (inclusive Layer 2 header) and
writes hex dump of these mesages as ASCII characters to standard output.
Example:
DTRC: 02 01 01 01
DTRC: 00 01 00 02 08 01 82 0D 18 01 89

Following optional parameters can be used to change type of destination of
output:
-xlog : use Eicon Networks 'xlog' format for output of D-channel
messages. This format uses header D-[R,X](Y), where 'R' is
used for received messages, 'X' is used for sent messages
and Y is the message length inclusive Layer 2 header.
Example:
D-R(004) 02 01 01 01
D-X(011) 00 01 00 02 08 01 82 0D 18 01 89

-syslog : Redirect output to system log file. Every record in system
log will receive header that contains logical adapter number,
card name and card serial number.
-dmonitor : This options allows output of additional trace information
that contains:
- Layer 3 messages as seen by internal state machine
(as hex dump, without Layer 2 header) and in decoded,
human readeable form, Layer3, Layers 2 and Layer 1
state events in human readeable form.
Example:
SIG-X(004) 08 01 82 01
Q.931 CR82 ALERT
SIG-x(007) 08 01 82 0D 18 01 89
Q.931 CR82 SETUP_ACK
Channel Id 89
SIG-R(004) 08 01 02 0F
Q.931 CR02 CONN_ACK
SIG-R(008) 08 01 81 5A 08 02 80 D8
Q.931 CR81 REL_COM
Cause 80 d8 'Incompatible destination'
EVENT: Call failed in State 'Call initiated'
Q.931 CR81 REL_COM
Cause 80 d8 'Incompatible destination'
L1_DOWN
SIG-EVENT FFFF 08
ACTIVATION_REQ
L1_DOWN
SIG-EVENT FFFF 08
ACTIVATION_REQ
L1_UP
SIG-EVENT FFFA 00

-Silent : Do not print messages to starndard output or standard error.
Exit silent in case of error and report error by return code
only

-Debug : Print additional information that can help to determine cause
of failure. This option is ignored if 'Silent' option was
invoked.

In monitor mode D-chnallel monitor runs in the background as daemon, and
reports status changes of Layer 2 and(or) Layer 2 to user application, that is
invoked by every change.
To start D-channel monitoring tool in monitor mode please execute:

divactrl dchannel -c XXX -monitor YYY [optional parameters]

where:
XXX - Logical adapter number to trace, mandatory
YYY - User application to be executed if state of Layer 1 or Layer 2 changes.
This application is called with three parameters:
1 - Logical adapter number
2 - Layer, that state changes (1 for Layer 1, and 2 for layer 2)
3 - State after change (1 - UP, 0 - DOWN)
In case D-channel monitor fails to start application, or application
exits with error, then D-channel monitor will report fauilure to
system log.

Following optional parameters can be used to change type of destination of
output:
-l1off : Do not monitor changes in the state of Layer 1
-l2off : Do not monitor changes in the state of Layer 2. This can be
necessary for BRI interface, in case Layers 2 is controlled
by NT side or is established 'on Demand'.
-syslog : Redirect output to system log file. Every record in system
log will receive header that contains logical adapter number,
card name and card serial number.
-dmonitor : This options allows output of additional trace information
to system log (please see example above).

You can safe terminate D-channel monitor by TERM or HUP signal.

--------------------------------------------------------------------------------
Trouble-shooting Procedure
--------------------------------------------------------------------------------
The trouble-shooting section is divided into two sections. The first section
guides you through some tests that you can perform to try and correct the
problem. Failing this, the second section outlines the steps to take to properly
report the problem to Customer Support at Eicon Networks.

--------------------------------------------------------------------------------
Test Procedure
--------------------------------------------------------------------------------
If you have any problems loading divas4linux driver modules, (you don't see the
divadidd, divas, diva_idi, kernelcapi, divacapi, capi, or Divatty modules listed
when you execute the 'lsmod' command) or if your machine crashes after you have
loaded drivers, please execute the following sequence of commands manually:

NOTE: Execution of 'sh /usr/lib/eicon/divas/cfg_util.sh 2' removes the symbolic
links that load divas4linux at system start and execution of
'sh /usr/lib/eicon/divas/cfg_util.sh 1' will create these links again.

1. Login as 'root' (us use 'su')
2. Change working directory to '/usr/lib/eicon/divas'
('cd /usr/lib/eicon/divas').
3. Execute 'sh ./cfg_util.sh 2'.
4. Reboot your machine and login again as root (or use 'su').
5. Change working directory to '/usr/lib/eicon/divas'
('cd /usr/lib/eicon/divas').
6. Execute 'sync && insmod -f ./divadidd.o >> report.txt 2>&1 && sync'
7. Execute 'insmod -f ./diva_idi.o >> report.txt 2>&1 && sync'
8. Execute 'insmod -f ./divas.o >> report.txt 2>&1 && sync'
9. Execute 'insmod -f ./kernelcapi.o >> report.txt 2>&1 && sync'
10. Execute 'insmod -f ./divacapi.o >> report.txt 2>&1 && sync'
11. Execute 'insmod -f ./capi.o >> report.txt 2>&1 && sync'
12. Execute './divactrl load -Debug YYYYYY -c X >> report.txt 2>&1 && sync'
Where YYYYYY are the parameters that you use to start this adapter
(for example -f ETSI).
Where X is Diva Server adapter number.
You can repeat this step for all Diva Server adapters installed in the system.
13. Execute 'insmod -f ./Divatty.o 2>&1 >> report.txt && sync'.
14. Run lsmod again and verify that the modules are now loaded or read the
report.txt file to determine the cause if a module was not loaded.

--------------------------------------------------------------------------------
Customer Support procedure
--------------------------------------------------------------------------------
If the above procedure does not give the desired results, follow the
reporting procedure below:

1. An exact problem description. A step-by-step description of your actions,
the result that you expected, and the actual results that you received.
2. Adapter type and serial number of the adapters installed in your machine.
3. Purpose of the adapter and the application being used.
4. The information captured in file 'report.txt' by running the script
'divas_sys_info.sh' located in directory '/usr/lib/eicon/divas'.
5. Send this to Eicon's customer support for analysis.

--------------------------------------------------------------------------------
'tty_test' Utility
--------------------------------------------------------------------------------
The 'tty_test' utility contains a test server, a test client, and a small
terminal application. The test client calls the test server. When the
connection is established, the client starts to generate test frames
and to transmit these frames to the test server. The test server loops
all received data back to the transmitter (client). The test client verifies
all received frames based on sequence number and check sum, and
generates link statistics. The 'tty_test' utility is located in the
'/usr/lib/eicon/divas' directory.

--------------------------------------------------------------------------------
'tty_test' in Server Mode
--------------------------------------------------------------------------------
The test server can be started with the following commands:

'./tty_test tty_nr s protocol [-lframe_length -srate]'

This command starts a test server on your console. You can see all messages
from the tty interface and all link statistics generated by the receiving
side.

'./tty_test tty_nr sv protocol [-lframe_length -srate]&'

This command starts a test server in the background. In this mode, the test
server detaches from your console and does not show any output on your
console. To get information about the test server started in the background,
use the ps x command. To safely stop the test server running in the
background, use the HUP signal ('kill -HUP process_number' or
'killall -HUP tty_test').

--------------------------------------------------------------------------------
Parameters for the 'tty_test' in Server Mode
--------------------------------------------------------------------------------
tty_nr - Mandatory. Diva TTY number that should be used by this test
server. It should range between 1 and N, where N is the number
of B-channels of all Diva ISDN adapters installed in the
system.
protocol - Mandatory. Selects the B-channel protocol. The following
options are available:
- auto - Automatic detection of the B-channel protocol stack.
The 'auto'-detection protocol functions as follows:
1. If present, the BC/LLC element is analyzed. If
the analysis provides enough information, the
appropriate protocol is selected.
2. If analyzing the BC/LLC element does not provide
sufficient information, the first frame received
over the B-channel is analyzed and then the
protocol is selected.
The following protocols can be auto detected:
- HDLC/Transparent/Transparent
This protocol stack is widely used by RAS.
- HDLC/X.75/Transparent
- HDLC/X.75 with V.42bis data compression/
Transparent
- HDLC/V.120/Transparent
- HDLC/V.120 with V.42bis data compression/
Transparent
- V.110/Transparent/Transparent
- Analog modem with full negotiation (up to
V.90 central Office)/V.42+V.42bis or V.42 or
Transparent - buffered mode/Transparent
This protocol stack is widely used by RAS.
- x75 - HDLC/X.75/Transparent
This protocol stack provides reliable data transfer.
V.42bis compression is detected automatically.
- x75v42 - HDLC/X.75 with V.42bis data compression/
Transparent.
This protocol is not used on the server side because 'x75'
automatically detects X.75 with V.42bis.
- V.120 - HDLC/V.120/Transparent
V.120 with V.42bis is possible.
- V110 - V.110/Transparent/Transparent
- mdm - Modem with full negotiation/V.42+V.42bis/Transparent

-lframe_length - Optional. Length of the test frame. It is normally not used
by the test server but it should be provided if the '-s'
option follows.
-srate - Optional. Speed adaptation rate. This parameter should be
indicated if the v110 B-channel protocol is used without
auto detection. It should range between 2 and 8 (5-9600,
9-56000). If this option is selected, the '-l' option
should also be used.

--------------------------------------------------------------------------------
'tty_test' in Client Mode
--------------------------------------------------------------------------------
The 'tty_test' client can be started with the following commands:

'./tty_test tty_nr CPN protocol [-lframe_length -srate] [-aat_command] [-y]
[-mpackets]'

This command starts a test client on your console.

'./tty_test tty_nr CPN protocol [-lframe_length -srate] [-aat_command]
[-mpackets] -x&'

This command starts a test client in the background. In this mode, the test
client detaches from your console and does not show any output on your
console. It generates a file named 'log.tty_nr' in its working directory.
The test client reports its link statistics to this file. You can monitor the
link statistics by the command 'strings log.* | more'.

Please note that TTY_TEST updates the log files after 64 KBytes of data
have been transferred. Also, please be patient if you use the v110 protocol
with 9600 Bps.

To get information about the test client started in the background, type:

ps ax | grep tty_test

To safely stop the test client running in the background, use the 'HUP'
signal ('kill -HUP process_number' or 'killall -HUP tty_test'). The 'tty_test'
utility understands the commands HUP, TERM, ABRT and INT. All these signals
terminate the 'tty_test' utility.

--------------------------------------------------------------------------------
Parameters for 'tty_test' in Client Mode
--------------------------------------------------------------------------------
- tty_nr - Mandatory. Diva TTY number that should be used by this test
client. It should range between 1 and N, where N is the
number of the B-channels of all Diva ISDN adapters that are
installed in the system.
- CPN - Mandatory. Called Party Number (any number can be used in
back-to-back mode).
- protocol - Mandatory. Selects the B-channel protocol. The following
options are available:
- hdlc - HDLC/Transparent/Transparent. This protocol stack
is widely used by RAS.
- x75 - HDLC/X.75/Transparent. This protocol stack provides
reliable data transfer.
- x75v42 - HDLC/X.75 with V.42bis data compression/
Transparent.
Same as x75, but V.42bis data compression is used if it is
supported by the other side.
- v120 - HDLC/V.120/Transparent This protocol stack provides
reliable data transfer.
- v110 - V.110/Transparent/Transparent
- mdm - Modem with full negotiation/V.42+V.42bis/Transparent

NOTES:
- The protocol stack notation is L1/L2/L3. However, the real
structure of Diva protocol stack is:
L1/L2/L3/AUTO_ASYNC2SYNC.
AUTO_ASYNC2SYNC is the ASYNC/SYNC conversion module that is
inserted automatically (as result of the analysis of the
first frames transferred over the link).
- ASYNC/SYNC conversion is provided automatically
if necessary.
-lframe_length - Optional. Test Frame Length. It is required if the -s option
follows. Default setting is 512 bytes.
-srate - Optional. Speed adaptation rate. It should be indicated if the
v110 B-channel protocol is used without auto detection. It
should range between 2 and 9 (5-9600, 7-38400). If this option
is selected, the '-l' option should be used.
-aat_command - Optional. Allows to provide additional AT command strings used
for client initialization.
-y - Optional. Do not display any messages except call progress and
data transfer status.
-mpackets - Optional. Exits after 'packets' data packets were sent.
Displays the transfer status on the screen (standard out) and
prints it to the log.tty_nr file. Error messages generated at
dial time are additionally written to syslog. If the data
packets have been successfully transferred, exit status is 20.
Any other exit status indicates an error. This option allows
you to create scripts that provide tests for multiple calls
with different protocols.

Examples:
- Start the test server at tty number 10. Use protocol auto detection:
'./tty_test 10 s auto'

- Start the test server at tty number 21. Use the V.110 protocol with 9600 Bps.
The test server should run in the background:
'./tty_test 21 sv v110 -l2048 -s5&'

- Start the test client at tty 1. Use the X.75 protocol. The called party number
is 800. The test frame length is 514 bytes:
'./tty_test 1 800 x75 -l514'

- Start the test client at tty 1. Use the V.110 protocol.
The called party number is 800. The test frame length is 128 bytes.
The rate adaptation speed is 9600 Bps. The rate adaptation should be
indicated in the bearer capabilities (BC). The test client should run
in the background:
'./tty_test 1 800 v110 -l128 -s5 -a+iu="<8890214800bb>" -x&'

NOTE: The AT+IU=<BC[/LLC]> command can be used to specify BCs (and low-layer
capabilities (LLC)) used for an outgoing call.
To specify BC only, use: AT+IU=<BC>
To specify BC and LLC, use: AT+IU=<BC/LLC>
BC and LLC should be specified in clear text as hex digits without
length digit.

- Start 30 test server and 30 test client sessions using this sample shell
script. It uses B-channel protocol auto-detection on the server side and
V.110 with 9600 Bps at the client side.

#! /bin/sh
#This 'n_cons' value will start 30 server and 30 client sessions
n_cons=30
# remove old log files
rm -f log.*
while [ $((n_cons)) -ge 1 ]
do
echo "Start $(($n_cons+30)) -> $((n_cons))"
./tty_test $((n_cons)) sv auto&
sleep 1
./tty_test $(($n_cons+30)) 800 v110 -l512 -a+ib5+iu="<8890214800bb>" -x&
sleep 1
n_cons=$(($n_cons-1))
done
#
# Please note that TTY_TEST updates log files after 64 KBytes
# of data has been transferred. Also, please be patient if you
# use v110 with 9600 Bps.
# To view TTY_TEST processes, type 'ps x'.
# To view the log files, use 'cat log.* | more'.
# --------------------------------------------------------------
# END OF SCRIPT
# --------------------------------------------------------------

--------------------------------------------------------------------------------
'tty_test' in Terminal Mode
--------------------------------------------------------------------------------
'tty_test' includes a simple and easy to use terminal mode.
To start TTY_TEST in terminal mode, type:

'./tty_test tty_nr t'

--------------------------------------------------------------------------------
Parameters for 'tty_test' in Terminal Mode
--------------------------------------------------------------------------------
- tty_nr - Mandatory. Diva TTY number that should be used by this test
server. It should range between 1 and N, where N is the
sum of all B-channels of the Diva ISDN adapters installed in
the system.

In terminal mode, all characters that you type on your console are sent to TTY,
once you press ENTER.

Normally, <CR> is forwarded to TTY. If you wish to strip <CR> from your input
(for example to test the +++ escape operation), enter <RETURN>r<RETURN>.
TTY_TEST will enter the 'no CR' mode and will remove <CR> from your input before
data is written to TTY. You can switch back to 'normal' operation by entering
<RETURN>R<RETURN>. If you are in 'no CR' mode, <RETURN>r<RETURN> will write
a <CR> to TTY.

In terminal mode, you can view the content of the virtual Modem Status Register
if you enter <RETURN>show msr<RETURN>. This will issue TIOCMGET ioctl on the
tty interface and print its output to the terminal.

You can set or clear the DTR line in the virtual Line Control Register (LCR).
If you enter <RETURN>DTR+<RETURN>, the DTR line will be set. If you enter
<RETURN>DTR-<RETURN>, the DTR line will be cleared (TIOCMBIS and TIOCMBIC
ioctl codes).

To quit the 'tty_test' terminal mode, enter <RETURN>q<RETURN>.

--------------------------------------------------------------------------------
Selection of different TTY interfaces
--------------------------------------------------------------------------------
'tty_test' has been developed to test and control the Diva Server TTY interface.
It always tries to open the /dev/ttyds[01 .... ] device node. With other
operating systems, the name of the Diva Server TTY interface may be different.
For example /dev/term/eicon/00/[0 ..... ] on UnixWare. You can still use
TTY_test without any changes if you create a symbolic link:
'ln -s your_real_tty_interface_device_node /dev/ttydsXXX'

Eicon Networks provides the source code of the 'tty_test' utility. If you use
'tty_test' or change the source code to create your own version of
the 'tty_test' application, note that the source files are supplied for the
exclusive use with Eicon Networks' range of Diva adapters.

--------------------------------------------------------------------------------
Building a back-to-back cable for PRI adapters
--------------------------------------------------------------------------------
NT mode of the PRI card is fully featured and allows you to create PABX, Media
Gateways and all other kinds of products that require NT capability. In other
words, you can create an ISDN switch with NT mode.
You can build your own back-to-back cable by using the unfinished cable supplied
with your Diva Server PRI card and terminating it according to
the diagram below:

Diva PRI Card Diva PRI Card
1 ---------------------------------------------4
2 -------------------------------------------- 5
3 not used
4 -------------------------------------------- 1
5 -------------------------------------------- 2
6 not used
7 not used
8 not used

NOTE: To make the back-to-back connection work between two PRI adapters, one
adapter must be configured as an NT (Network Termination), while the
other must be configured as a TE (Terminal Endpoint). Please refer to
the section Configuring Diva Server PRI adapters for details.
Plugging in this cable, plus loading the Diva Server for Linux drivers
and configuring the adapters should result in layer 1 and layer 2 being
active.
You can verify the layer activity either by checking the LEDs on both
adapters (for a description of the LED functions refer to the printed
guide that came with your Diva Server adapter) or by executing
./mantool -rState. Both LEDs should be lit or both layer states should
be ON.

--------------------------------------------------------------------------------
Management Interface
--------------------------------------------------------------------------------
The management interface can be used to control adapter configuration at run time
without reloading or restarting the Diva adapter or can be used as a source of
information and events that can be used for SNMP MIB, as source of SNMP traps,
and to create other management applications.
The management interface is located on the adapter. It is structured like a virtual file
space, containing directories and variables. Each directory and variable is identified
by its path and name. A path contains directory names followed by a specific variable
or subdirectory that is separated by a backslash '\'.
Variables can have the following functions:
- variable: standard variable that can be read or written
- function: variable that can be executed and does not provide any value
- event: variable that can be read and used as source of events that will
be generated when the state (value) of this variable changes

You can use the 'divactrl' utility in 'mantool' mode
('/usr/lib/eicon/divas/divactrl mantool') to access (read/write) management
interface variables. By means of 'divactrl mantool' you can turn on 'Line'
events in 'State\B[1...N]' management directories (where 'N' is the number of
B-channels supported by the adapter) and receive notifications from these events.
In this way 'divactrl mantool' operates as an accounting tool. In the
'divactrl mlog' mode ('/usr/lib/eicon/divas/divactrl mlog') 'divactrl' uses the
'Trace' management interface directory and the events/variables located in this
directory to receive information from layer 1 interface state changes,
SPID state changes, received and sent D-channel messages and
data received/sent over active B-channels.
The source code of 'divactrl' is freely available as part of the 'divactrl' package
and can be used as example for access to the management interface.

The following tables describe the content of the management interface directories
and use the following symbols to describe variable types:
MI_DIR - Directory
MI_HINT - Unsigned integer with hexadecimal representation, variable
length
MI_UINT - Unsigned integer, variable length
MI_ASCIIZ - ASCII string, zero terminated
MI_ASCII - ASCII string, counted
MI_BOOLEAN - Boolean value
MI_BITFLD - Unsigned integer, representation as bit field, variable length
MI_EXECUTE - Variable represents executable function

and their attributes:
RO - Read only
W - Writable
EVENT - Variable can be used to generate event (notification)

--------------------------------------------------------------------------------
Path:\
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
MIF Version MI_HINT RO Version number of Management
interface
Build MI_ASCIIZ RO Name and build number of
protocol file.
Events down MI_UINT EVENT Any variable's event tracing
is paused until internal
resources are re-available.
Config MI_DIR State machines, selected
protocols and their
parameters.
Statistics MI_DIR Statistics counters etc.
State MI_DIR State machines, selected
protocols.
Trace MI_DIR Trace functions (every
application instance will
receive an individual copy of
this directory).

--------------------------------------------------------------------------------
Path:\Config
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Dchannel MI_DIR Select used D-channel protocol
(switch type) on demand.
Layer 2 MI_DIR Select layer 2 parameters on
demand.
Layer 1 MI_DIR Select layer 1 parameters on
demand (PRI only).
Modem MI_DIR Analog modem parameters.
Fax MI_DIR Fax parameters.
Robbed Bit MI_DIR Robbed Bit Signaling protocol
options.
Version MI_UINT Protocol version.
DID-Length MI_UINT W When this variable is set, the
incoming digits of the called
number are collected until
their length corresponds to
the given DID-Length. Only
then, the call is forwarded to
the application.
Ringertone MI_BOOLEAN W Selects whether in-band tones
(busy/alert) are generated in
the B-channel when they are
not provided by the ISDN
equipment.
Redial-Timeout MI_UINT W Sets the time in seconds after
which redialing is no longer
possible.
QSIGDialect MI_UINT W Selects the QSIG version
to be used. Possible
values are:
0: Autodetection
1: ECMA-QSIG
2: ETSI-SS
3: ISOV2-QSIG
4: CornetNQ
NT MI_BOOLEAN W Select NT or TE operation
mode. Can be written only
for NT-capable adapters.
PRI MI_BOOLEAN RO PRI or BRI adapter.
GlobalCRs MI_BOOLEAN W Turn processing of D-channel
messages with global call
reference on/off.
NoOrderCheck MI_BOOLEAN W Turn order check of
information elements in
D-channel message on/off.
NT-2 MI_BOOLEAN W Turn NT 2 (Direct Inward
Dialing) mode on/off.
LoopBack MI_BOOLEAN W Turn loop back on physical
interface on/off.
CardType MI_UINT RO Diva adapter type.
SerialNumber MI_UINT RO Serial number of adapter.
BoardRevision MI_UINT RO Hardware revision of adapter.
SubFunction MI_UINT RO Sub-function.
DSPState MI_BITFLD RO Bit field to identify presence
of DSPs.
SPID-# MI_DIR D-channel link configuration.

--------------------------------------------------------------------------------
Path:\Config\US-EKTS
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
CACH MI_UINT W Sets the number of call
Appearances references from which on CACH
(Call Appearance Call Handling)
needs to be activated.
Key BeginConf MI_HINT W Sets the key value that
activates the begin conference
feature.
Key DropConf MI_HINT W Sets the key value that
activates the drop conference
feature.
Key MI_HINT W Sets the key value that
CallTransfer activates the call transfer
feature.

--------------------------------------------------------------------------------
Path:\Config\Dchannel
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Name MI_ASCIIZ RO Name of currently active
D-channel protocol.
Protocol MI_EXECUTE Execute this function to
names that select appropriate protocol.
can be
selected
Protocol MI_UINT W Active protocol number.
Writing a number to this
variable will select the
appropriate protocol.
Release MI_ASCIIZ RO Build time/date of protocol
image.

--------------------------------------------------------------------------------
Path:\Config\Layer2
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Stable L2 MI_ASCIIZ RO Name of currently active
layer 2 activation strategy.
On demand (0) MI_EXECUTE Select 'on demand' activation
strategy, i.e. layer 2 is
disconnected after last active
connection was cleared.
Send No Disc (1) MI_EXECUTE Select 'no disc' activation
strategy, i.e. layer 2 is
disconnected only if requested
by NT side.
Permanent (2) MI_EXECUTE Select 'permanent' activation
strategy, i.e. adapter will
try to keep layer 2 always
active.
L2 MI_UINT W Number of currently active
layer 2 activation strategy.
Writing to this variable will
change the layer 2 activation
strategy without reset of
D-channel protocol state, i.e.
state will be changed later
after last active connection
was cleared.

--------------------------------------------------------------------------------
Path:\Config\Layer1
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Current name MI_ASCIIZ RO Name of used layer 1 framing
type.
Current MI_UINT W Number of used layer 1 framing
type, can be written to select
new layer 1 framing type.
Auto CRC4 MI_EXECUTE RO Selects auto detection of
layer 1 framing type.
CRC4 MI_EXECUTE RO Selects CRC4.
No CRC4 MI_EXECUTE RO Selects double framing

--------------------------------------------------------------------------------
Path:\Config\Robbed Bit
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Options MI_BITFLD W Represents the settings
for the following parameters
(starting from the 2 least
significant bits):
- Glare-resolving party -
indicates how a call
collision is resolved:
00 - No: Your server waits
for the remote site to
return to on-hook status
and then starts sending
address digits.
01 - Yes: Your server
returns to on-hook status
and waits for dial digits
from the remote site.
- Trunk type - indicates which
trunk type is used.
00 - Wink Start
01 - Loop Start
10 - Ground Start
- Dial type - indicates which
dial type is used.
00 - Pulse dialing
01 - DTMF (Dual Tone
MultiFrequency)
10 - MF (MultiFrequency)
- Direct Inward Dialing (pulse
dialing only) - indicates if
incoming dialed digits are
collected and forwarded to
the application or if the
call is accepted as soon as
the destination party
indicates off-hook status.
Answerdelay MI_UINT W Sets the time (in seconds)
after which the adapter hangs
up if the remote site does not
answer a call.
Digittimeout MI_UINT W Sets the time (in seconds) that
may pass between incoming
dialed digits. If this time
interval is exceeded, the
called number is assumed to be
complete and the call is
forwarded to the application.
Bearer Cap MI_UINT W Sets the bearer capability
that is to be included with
the incoming call that is
signaled to the application.
Possible values are:
- 4 - Analog/voice (3.1 kHz)
- 8 - Digital/data
Debug MI_BITFLD W Sets the debug mask that is to
be used for Robbed Bit
Signaling.

--------------------------------------------------------------------------------
Path:\Config\SPID-#
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Automatic TEI MI_BOOLEAN RO Automatic TEI assignment
enabled.
TEI MI_UINT RO Fixed TEI value.
SPID MI_ASCII W SPID number string.
Number MI_ASCII W Origination address string.
Sub-Adr MI_ASCII W Origination sub-address
string.

--------------------------------------------------------------------------------
Path:\Statistics
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Outgoing Calls MI_DIR Statistic information for
outgoing calls.
Incoming Calls MI_DIR Statistic information for
incoming calls.
D-Layer2 MI_DIR Sum of D-channel layer 2
statistics.
B-Layer2 MI_DIR Sum of B-channel layer 2
statistics.
Charges MI_UINT EVENT Sum of charge units.
Clear Values MI_EXECUTE Reset all values in this
directory and all
subdirectories.

--------------------------------------------------------------------------------
Path:\Statistics\Outgoing Calls
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Calls MI_UINT EVENT Number of requested calls.
Connected MI_UINT EVENT Number of successful calls.
User busy MI_UINT RO Number of refused calls by
cause.
No Answer MI_UINT RO Number of refused calls by
cause.
Wrong Number MI_UINT RO Number of refused calls by
cause.
Call rejected MI_UINT RO Number of refused calls by
cause.
Other failures MI_UINT RO Number of refused calls by
cause.
Clear values MI_EXECUTE Reset all values in this
directory.

--------------------------------------------------------------------------------
Path:\Statistics\Incoming Calls
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Calls MI_UINT EVENT Number of incoming calls.
Connected MI_UINT EVENT Number of accepted calls.
User busy MI_UINT RO Number of refused calls by
cause.
Call rejected MI_UINT RO Number of refused calls by
cause.
Wrong number MI_UINT RO Number of refused calls by
cause.
Incompatible MI_UINT RO Number of refused calls by
destination cause.
Out of order MI_UINT RO Number of refused calls by
cause.
Ignored MI_UINT RO Number of refused calls by
cause.
Clear values MI_EXECUTE Reset all values above.

--------------------------------------------------------------------------------
Path:\Statistics\(B)D-Layer2
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
X-Frames MI_UINT RO Number of frames sent.
X-Bytes MI_UINT RO Number of bytes sent.
X-Errors MI_UINT RO Number of detected transmit
errors.
R-Frames MI_UINT RO Number of received frames.
R-Bytes MI_UINT RO Number of received bytes.
R-Errors MI_UINT RO Number of detected receive
errors.

--------------------------------------------------------------------------------
Path:\State
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Layer1 MI_ASCIIZ EVENT State of layer 1.
Layer2 No# MI_SPID_STATE EVENT State of D-channel link
number #.
CODEC # MI_DIR Adjustment and states of
CODEC number # (this directory
is present only with CTI-
capable adapters equipped with
audio codec).
B# MI_DIR State of B-channel number #.

--------------------------------------------------------------------------------
Path:\State\CODEC # (CTI-capable adapters only)
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
Mic Volume Hdset MI_UINT W Volume of head/handset
Range: 0...8 microphone 1.
Spk Volume HdSet MI_UINT W Volume of head/handset
Range: 0...9 speaker 1.
Mic Volume HFree MI_UINT W Volume of hands-free (ext)
Range: 0...8 microphone.
Spk Volume HFree MI_UINT W Volume of speaker in
Range: 0...12 handsfree mode.
Spk Volume LoudH MI_UINT W Volume of speaker in
Range: 0...12 loudhearing mode.
Transmit Volume MI_UINT W Gain adjustment of transmit
Range: 0...51 path1(micro).
Receiver Volume MI_UINT W Gain adjustment of receive
Range: 0...51 path1(spk).
Sidetone Gain MI_UINT W Hand/Headset 1 sidetone gain
Range: 0...51 adjustment.
Ring Volume Ext MI_UINT W Volume of external ringer
Range: 0...12 (ext. speaker).
Ring Melody MI_UINT W Selection of predefined ringer
Range: 0...9 melodies.
IntrTone Volume MI_UINT W Volume 1 of intrusion tone
Range: 0...10 melody.
IntrTone Melody MI_UINT W Selection of actual intrusion
Range: 0...9 tone melody.
Muting on/off MI_UINT W Switches the microphone 1 off.
Range: 0...1
HdSet 1 Status MI_ASCIIZ EVENT Plug state / hook state of
hand/headset 1. Strings:
'Unplugged', 'Operating',
'Hook ON'. A handset can be
Operating or Hook ON, a
headset can be Operating or
Unplugged.
Ext Mic Status MI_ASCIIZ EVENT Plug state of the external
microphone. Strings:
'Unplugged', 'Operating'
HdSet 2 Status MI_ASCIIZ EVENT Plug state / hook state of
hand/headset 2. Strings see
HdSet1 Status.
Switch Status MI_ASCIIZ EVENT Telephone chip (codec)
operating mode. Strings:
'Off', 'Head/HandSet ON',
'External Mic/Spk ON',
'Alerting External Speaker',
'Alerting Head/Handset'. The
Alerting Head/Handset is
active if an intrusion tone
is used to ring a call.
Switch Hdset/Ext MI_EXECUTE Toggles between hands-free
and headset.
Mic Vol 2 HdSet MI_UINT W Volume of head/handset
Range: 0...8 microphone 2.
Spk Vol 2 HdSet MI_UINT W Volume of head/handset
Range: 0...9 speaker 2.
Transmit Vol 2 MI_UINT W Gain adjustment of transmit
Range: 0...51 path2 (micro).
Receiver Vol 2 MI_UINT W Gain adjustment of receive
Range 0...51 path2 (spk)
Sidetone Gain 2 MI_UINT W Hand/Headset 2 sidetone gain
Range: 0...51 adjustment.
IntrTone Vol 2 MI_UINT W Volume 2 of intrusion tone
Range 0...10 melody.
Muting 2 on/off MI_UINT W Switches microphone 2 off
Range: 0...1

--------------------------------------------------------------------------------
Path:\State\B#
--------------------------------------------------------------------------------
This directory contains the currently used values, or last used values if the
B-channel is inactive.

Name Type Attribute Comment
==== ==== ========= =======
Framing MI_ASCIIZ RO Used layer 1 protocol.
Line MI_ASCIIZ EVENT Line state (idle, connected
in/out).
Layer2 MI_ASCIIZ RO Used layer 2 protocol.
Layer3 MI_ASCIIZ RO Used layer 3 protocol.
Line type MI_ASCIIZ RO Dialup/leased.
Remote Address MI_ASCII RO
Remote Subaddr MI_ASCII RO
Local Address MI_ASCII RO
Local Subaddr MI_ASCII RO
BC MI_NUMBER RO Bearer Capability.
HLC MI_NUMBER RO High Layer Compatibility.
LLC MI_NUMBER RO Low Layer Compatibility.
Charges MI_UINT EVENT Sum of line-related charges.
Call Reference MI_HINT RO Last used value.
Last Disc Cause MI_HINT RO Last used value.
User ID MI_ASCII RO Last owner that claimed this
channel, if any.
Clear Call MI_EXECUTE Send DISCONNECT for channel
B#.

--------------------------------------------------------------------------------
Path:\Trace
--------------------------------------------------------------------------------
Name Type Attribute Comment
==== ==== ========= =======
B-Ch# Enable MI_BITFLD W Bit field to enable specific
B-channels.
Debug Level MI_HINT W Upper limit of debug events to
log.
D-HW Txt Mask MI_BITFLD W D-channel hardware trace mask.
B-HW Txt Mask MI_BITFLD W B-channel hardware trace mask.
Misc Txt Mask MI_BITFLD W Trace mask for miscellaneous
use.
Event Enable MI_BITFLD W Bit field to enable specific
trace events.
Max Log Length MI_UINT W Maximum number of data bytes in
trace.
Log Buffer MI_TRACE EVENT Trace information: L1,
D-channel, B-channel
and debug information.

For further information, see the manual for the 'divactrl mantool' (can be
received if you execute '/usr/lib/eicon/divas/divactrl mantool' without any
parameter).

--------------------------------------------------------------------------------
Features
--------------------------------------------------------------------------------
Each of Eicon's Diva Server adapters provides different features and
capabilities with Diva Server for Linux. The table below outlines the feature
set of Eicon Diva Server adapters.
However, all features may not be available on all the supported interfaces.
The interfaces supported by Eicon Diva Server adapters are as follows:
- IDI ISDN Direct Interface
Supports all features and capabilities of Eicon ISDN adapters.
- COM Port
For applications that require communications via a standard PC communications
port.
- CAPI 2.0
Common ISDN Application Programming Interface. A standard interface for
applications to interact with ISDN adapters.

--------------------------------------------------------------------------------
Features via interface | IDI | COM Port | CAPI 2.0
| | (TTY) |
--------------------------------------------------------------------------------
B-channel related features:
--------------------------------------------------------------------------------
Transparent HDLC, 64/56 kbps | X | X | X
--------------------------------------------------------------------------------
Transparent (Voice) | | |
(8 bit 8 kHz A-Law, | X | X | X
8 bit 8 kHz u-Law) | | |
--------------------------------------------------------------------------------
X.75 64/56 kbps | X | X | X
--------------------------------------------------------------------------------
T.70/T.90 (T-Online) | X | X | X
--------------------------------------------------------------------------------
V.110 (GSM) 1) | X | X | X
--------------------------------------------------------------------------------
V.120 64/56 kbps (CompuServe) | X | X | X
--------------------------------------------------------------------------------
V.120/V.42bis | X | | X
--------------------------------------------------------------------------------
V.34+, V.90 analog modem 1) | X | X | X
--------------------------------------------------------------------------------
V.42, V.42bis 1) | X | X | X
--------------------------------------------------------------------------------
X.75/V.42bis | X | | X
--------------------------------------------------------------------------------
Change of B-channel protocol | X | | X
during a call | | |
--------------------------------------------------------------------------------
LAPD/B | X | | X
--------------------------------------------------------------------------------
X.25, X.31, ISO 8208 in the B-channel | X | | X
--------------------------------------------------------------------------------
Fax Group 4 (incl. T.90/ISO8208 and | X | | X
module mode detection) | | |
--------------------------------------------------------------------------------
T.30 Fax Group 3 (analog), Class 1 | X | X | X
and 2 1) | | |
--------------------------------------------------------------------------------
B-channel protocol detection | | X |
--------------------------------------------------------------------------------
Async/sync conversion | | X |
--------------------------------------------------------------------------------
Fax with Error Correction Mode (ECM) 1)| | |
Fax with MR (D2 coding) 1) | X | X | X
Fax with MMR (T.6 coding) 1) | | |
--------------------------------------------------------------------------------
Fax 14.4 kbps 1) | X | X | X
--------------------------------------------------------------------------------
Fax tone detection 1) | X | | X
--------------------------------------------------------------------------------
Reversal of fax direction 1) | X | | X
--------------------------------------------------------------------------------
Fax polling / fax on demand 1) | X | X | X
--------------------------------------------------------------------------------
Speed and feature indication | X | | X
(polling and ECM) 1) | | |
--------------------------------------------------------------------------------
New fax header line 1) | X | | X
--------------------------------------------------------------------------------
DTMF tone detection and transmission 1)| X | | X
--------------------------------------------------------------------------------
Line Interconnect (switch loops, | X | | X
digital mixer, multi conference) 1) | | |
--------------------------------------------------------------------------------
Media mode (unknown, interactive | X | |
voice, automated voice) 1) | | |
--------------------------------------------------------------------------------
Supplementary Services:
--------------------------------------------------------------------------------
MSN (multiple subscriber number) 2) | X | X | X
--------------------------------------------------------------------------------
DDI (direct dialing-in) 2) | X | | X
--------------------------------------------------------------------------------
SUB (sub-addressing) 2) | X | X | X
--------------------------------------------------------------------------------
CLIP (calling line identification | X | X | X
presentation) 2) | | |
--------------------------------------------------------------------------------
CLIR (calling line identification | X | | X
restriction) 2) | | |
--------------------------------------------------------------------------------
COLP (connected line identification | X | | X
presentation) 2) | | |
--------------------------------------------------------------------------------
COLR (connected line identification | X | | X
restriction) 2) | | |
--------------------------------------------------------------------------------
KEY (keypad protocol) 2) | X | | X
--------------------------------------------------------------------------------
TP (terminal portability) 2) | X | | X
--------------------------------------------------------------------------------
Call forwarding unconditional | X | | X
--------------------------------------------------------------------------------
Call forwarding busy | X | | X
--------------------------------------------------------------------------------
Call forwarding no reply | X | | X
--------------------------------------------------------------------------------
Call deflection | X | | X
--------------------------------------------------------------------------------
CW (call waiting) 2) | X | | X
--------------------------------------------------------------------------------
HOLD (hold and retrieve a call) 2) | X | | X
--------------------------------------------------------------------------------
ECT (explicit call transfer) | X | | X
--------------------------------------------------------------------------------
AoC (advice of charge) 2) | X | | X
--------------------------------------------------------------------------------
3rd party conference | X | | X
--------------------------------------------------------------------------------
User-to-user signaling 2) | X | | X
--------------------------------------------------------------------------------
Voice over Packet:
--------------------------------------------------------------------------------
VoIP 3) | X | | X
--------------------------------------------------------------------------------
Others:
--------------------------------------------------------------------------------
Transparent D-channel | X | | X
--------------------------------------------------------------------------------
X.25/D-channel including AO/DI support | X | | X
--------------------------------------------------------------------------------

1) Features are not available with the Diva Server PRI adapter without modules
or the Diva Server PRI 2.0 adapter without additional DSPs.
2) Supplementary services are protocol-type independent.
3) Feature is only available with VoIP-enabled Diva Server adapters.
Feature includes Echo Cancellation, Voice Compression,
Tone generation/recognition and RTP/UDP/IP packet handling.

NOTE: Depending on the switch type and PBX not all supplementary services might
be available.

--------------------------------------------------------------------------------
Diva Client adapters' features
--------------------------------------------------------------------------------

Features via interface | IDI | COM Port | CAPI 2.0
| | (TTY) |
--------------------------------------------------------------------------------
B-channel related features:
--------------------------------------------------------------------------------
Transparent HDLC, 64/56 kbps | X | X | X
--------------------------------------------------------------------------------
Transparent (Voice) | | |
(8 bit 8 kHz A-Law, | X | X | X
8 bit 8 kHz u-Law) | | |
--------------------------------------------------------------------------------
X.75 64/56 kbps | X | X | X
--------------------------------------------------------------------------------
T.70/T.90 (T-Online) | X | X | X
--------------------------------------------------------------------------------
V.110 (GSM) 1) | X | X | X
--------------------------------------------------------------------------------
V.120 64/56 kbps (CompuServe) | X | X | X
--------------------------------------------------------------------------------
V.120/V.42bis | X | | X
--------------------------------------------------------------------------------
V.34+, V.90 analog modem 1) | X | X | X
--------------------------------------------------------------------------------
V.42, V.42bis 1) | X | X | X
--------------------------------------------------------------------------------
X.75/V.42bis | X | | X
--------------------------------------------------------------------------------
Change of B-channel protocol | X | | X
during a call | | |
--------------------------------------------------------------------------------
LAPD/B | X | | X
--------------------------------------------------------------------------------
X.25, X.31, ISO 8208 in the B-channel | X | | X
--------------------------------------------------------------------------------
Fax Group 4 (incl. T.90/ISO8208 and | X | | X
module mode detection) | | |
--------------------------------------------------------------------------------
T.30 Fax Group 3 (analog), Class 1 | X | X | X
and 2 1) | | |
--------------------------------------------------------------------------------
B-channel protocol detection | | X |
--------------------------------------------------------------------------------
Async/sync conversion | | X |
--------------------------------------------------------------------------------
Fax with Error Correction Mode (ECM) 1)| | |
Fax with MR (D2 coding) 1) | X | X | X
Fax with MMR (T.6 coding) 1) | | |
--------------------------------------------------------------------------------
Fax 14.4 kbps 1) | X | X | X
--------------------------------------------------------------------------------
Fax tone detection 1) | X | | X
--------------------------------------------------------------------------------
Reversal of fax direction 1) | X | | X
--------------------------------------------------------------------------------
Fax polling / fax on demand 1) | X | X | X

--------------------------------------------------------------------------------
Speed and feature indication | X | | X
(polling and ECM) 1) | | |
--------------------------------------------------------------------------------
New fax header line 1) | X | | X
--------------------------------------------------------------------------------
DTMF tone detection and transmission 1)| X | | X
--------------------------------------------------------------------------------
Line Interconnect (switch loops, | X | | X
digital mixer, multi conference) 1) | | |
--------------------------------------------------------------------------------
Media mode (unknown, interactive | X | |
voice, automated voice) 1) | | |
--------------------------------------------------------------------------------
Supplementary Services:
--------------------------------------------------------------------------------
MSN (multiple subscriber number) 2) | X | X | X
--------------------------------------------------------------------------------
DDI (direct dialing-in) 2) | X | | X
--------------------------------------------------------------------------------
SUB (sub-addressing) 2) | X | X | X
--------------------------------------------------------------------------------
CLIP (calling line identification | X | X | X
presentation) 2) | | |
--------------------------------------------------------------------------------
CLIR (calling line identification | X | | X
restriction) 2) | | |
--------------------------------------------------------------------------------
COLP (connected line identification | X | | X
presentation) 2) | | |
--------------------------------------------------------------------------------
COLR (connected line identification | X | | X
restriction) 2) | | |
--------------------------------------------------------------------------------
KEY (keypad protocol) 2) | X | | X
--------------------------------------------------------------------------------
TP (terminal portability) 2) | X | | X
--------------------------------------------------------------------------------
Call forwarding unconditional | X | | X
--------------------------------------------------------------------------------
Call forwarding busy | X | | X
--------------------------------------------------------------------------------
Call forwarding no reply | X | | X
--------------------------------------------------------------------------------
Call deflection | X | | X
--------------------------------------------------------------------------------
CW (call waiting) 2) | X | | X
--------------------------------------------------------------------------------
HOLD (hold and retrieve a call) 2) | X | | X
--------------------------------------------------------------------------------
ECT (explicit call transfer) | X | | X
--------------------------------------------------------------------------------
AoC (advice of charge) 2) | X | | X
--------------------------------------------------------------------------------
3rd party conference | X | | X
--------------------------------------------------------------------------------
User-to-user signaling 2) | X | | X
--------------------------------------------------------------------------------
Voice over Packet:
--------------------------------------------------------------------------------
VoIP 3) | X | | X
--------------------------------------------------------------------------------
Others:
--------------------------------------------------------------------------------
Transparent D-channel | X | | X
--------------------------------------------------------------------------------
X.25/D-channel including AO/DI support | X | | X
--------------------------------------------------------------------------------