--------------------------------------------------------------------------------
Diva Server for Linux - Reference Guide
--------------------------------------------------------------------------------
Third Edition (February 2002) 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.
This distribution contains programs the are licensed under GNU General Public
License (GPL). Those programs are copyrighted by their respective owners and
distributed under the terms of the GNU General Public License included in this
package. If you have not received a copy of such license you may obtain it by
writing to the Free Software Foundation, Inc., 59 Temple Place, Suite 330,
Boston, MA 02111-1307 USA.
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 2000-2002 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 guide
Structure of this guide
Syntax of this guide
About Diva Server for Linux
Features
Supported hardware
System Requirements
Installation and Configuration
Software installation using RPM
Configuring Diva Server for Linux
Loading the Diva modules
Manual adapter configuration
Special configuration features
Testing adapter functionality and connectivity
Configuring the Diva Server TTY Serial Ports
AT commands
Supported TTY profiles
ESCAPE sequence
AT command responses
TTY control interface
Setting up a Linux PPP (RAS) server
Uninstalling Diva Server for Linux
Unloading the Diva modules
Uninstalling the Diva package
Troubleshooting
Troubleshooting procedure
TTY_Test utility
Trace and debug utilities
Management Interface
Mantool management interface access and monitoring utility
Management interface structure
Features
Supplementary Services
--------------------------------------------------------------------------------
CHAPTER 1: ABOUT THIS GUIDE
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
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.
Loading Diva Server modules: Eicon ISDN Serial Driver (analog, fax,
V.110 and V.120 capabilities) and CAPI support.
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.
--------------------------------------------------------------------------------
Syntax of this guide
--------------------------------------------------------------------------------
The following syntax is used throughout the guide:
Syntax Description
------ -----------
<Variable> Variables that must be entered are enclosed in angle brackets.
Variables may consist of numbers or other characters strings.
[Opt] Optional entries are enclosed in square brackets. They may
consist of variables (e.g. <number>) and characters strings.
a1|a2 Alternative entries are separated by a vertical line (pipe
character).
--------------------------------------------------------------------------------
CHAPTER 2: ABOUT DIVA SERVER FOR LINUX
--------------------------------------------------------------------------------
Diva Server for Linux enables you to use your Eicon Diva 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 utilities.
--------------------------------------------------------------------------------
General 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, 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),
PIAFS 1.0 and 2.1
- 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
- Automatic synchronous/asynchronous conversion
- Automatic detection of incoming call type (Generic modem only)
- Support for all known D-channel protocols (switch types)
- Support for Q-Sig protocol
- 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 kbps lines (e.g. USA)
- Support for fractional lines
- Automatic detection of Eicon Diva adapters during configuration
- Diva configuration wizard for easy adapter configuration
- Up to 210 B-channels can be used simultaneously (up to 7 Diva Server PRI
adapters in a system)
- Eicon ISDN Serial driver (modem emulation) provides a rich AT-command set and
supports Fax Class 1 and Fax Class 2 AT-commands
- 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 2D coding, 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
- Reversal of fax direction
- Dynamic switching of B-channel protocols
- DTMF transmission and detection
- Cross-board switching via interline connect (DSP-based monitor, bridge, and
mixer for voice connections: supports multiline conference calls)
- Page formats: ISO A4, ISO B4, ISO A3
- Standard, fine and ultra-fine resolution
- Echo cancellation
- Real time protocol (RTP)
- Dynamic anti-jitter buffering
- Comfort noise generation (CNG)
- Voice activity detection (VAD)
--------------------------------------------------------------------------------
Q-Sig features
--------------------------------------------------------------------------------
- Basic call
- Redirected number
- Connected name
- Advice of charge (AoC)
--------------------------------------------------------------------------------
Eicon ISDN Serial driver
--------------------------------------------------------------------------------
The Eicon ISDN Serial driver provides access to the analog, digital, fax, V.110,
B-channel protocol detection, caller ID, and voice capabilities of Diva adapters
by providing a standard serial driver interface. This allows Diva 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
IP (Internet Protocol) over PPP (Point-to-Point Protocl) connections.
- As a fax server or gateway, in combination 3rd-party fax software that works
with fax modems.
- As a WAP (Wireless Application Protocol) gateway or WAP application server,
using the V.110 protocol (or combined with RAS server).
--------------------------------------------------------------------------------
CAPI 2.0 support
--------------------------------------------------------------------------------
The CAPI 2.0 (Common ISDN Application Programming Interface) driver allows
CAPI-based applications to be used with Diva adapters and provides
a mechanism for 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.
Supplementary services supported by the CAPI 2.0 driver:
- Number identification services: MSN, DDI, SUB, CLIP, CLIR, COLP, COLR, KEY
- Call offering services: TP, CFU, CFB, CFNR, call deflection
- Call completion services: CW, HOLD, ECT
- Charging services: AoC
- Three-party conference
- Others: User-to-user signaling
- Hunt-group support
NOTE: The availability of supplementary services depends on your switch and
PBX.
--------------------------------------------------------------------------------
Supported hardware
--------------------------------------------------------------------------------
Diva Server for Linux supports the following Eicon Diva adapters:
ISDN BRI adapters:
- Diva Server 2FX
- Diva Server BRI-2M PCI
- Diva Server BRI-2M 2.0 PCI
- Diva Server 4BRI-8M PCI
- Diva Server 4BRI-8M 2.0 PCI
ISDN PRI 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
T1 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
Diva Server for Linux supports the installation of up to 7 Eicon Diva Server
adapters in one computer.
--------------------------------------------------------------------------------
System requirements
--------------------------------------------------------------------------------
The following requirements have to be met for the installation of Diva Server
for Linux :
- A PC/AT-compatible computer (80486 or higher processor with 32 MB RAM)
- An installed Linux system
- At least 40 MB of free space on the drive on which your Linux system is
installed
- An installed Eicon Diva adapter.
--------------------------------------------------------------------------------
CHAPTER 3: 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. Confirm the operation of your adapter. For further information, see Testing
adapter functionality and connectivity.
5. Configure the Diva Server for Linux Serial Devices. For further
information, see Configuring the Diva Server TTY Serial ports.
--------------------------------------------------------------------------------
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,
etc.)
- 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)
- CAPI 2.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 CAPI 2.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 CAPI 2.0 interface.
- Diva configuration wizard used to detect the hardware and to automatically
create the configuration script (menu driven tools, includes the files
Config, Start, Stop, 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' or 'Config' 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 Diva Server for Linux 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
Diva Server for Linux (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 the 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 adapter.
- MLOG shell script that contains 'divactrl mlog $*' and can be used to read
MLOG traces from the adapter.
- 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.
- Documentation (all *.txt and *.pdf files) extracted to 'usr/doc/packages'.
--------------------------------------------------------------------------------
CONFIGURING DIVA SERVER FOR LINUX
--------------------------------------------------------------------------------
The './Config' script (located in the 'usr/lib/eicon/divas' directory) is a
setup wizard that detects all installed Diva adapters and guides you
through a series of menus 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.
You can use the 'usr/lib/eicon/divas/Start' script to load the adapters
manually. You can use the 'usr/lib/eicon/divas/Stop' script to unload the
adapters manually.
The setup wizard creates all necessary device nodes in the /dev directory:
- capi20: used to access the CAPI 2.0 interface
- ttyds01...ttyds<n> - used to access the Diva TTY interface; <n> is the sum
of B-channels of all installed adapters.
The available configuration options depend on the installed Diva adapter:
- Configuration options for Diva Server PRI adapters are described in the
section 'Configuring Diva Server PRI adapters'.
- For information on configuring Diva Server 2FX, BRI, or 4BRI adapters, refer
to the section 'Configuring Diva Server BRI and 4BRI 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 ISDN interface
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 add one logical adapter each.
The Diva Server 4BRI adds 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 on the DIDD 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 on the XDI driver.
A subdirectory named 'adapter<no>' (<no> is the logical adapter number) is
created in the '/proc/net/eicon' directory for every logical adapter
present in the system.
Each 'adapter<no>' 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 are:
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:
1. Change to the /usr/lib/eicon/divas directory and run the following command:
./Config
The 'Diva ISDN Adapter Configuration Wizard' is opened.
Check if your kernel supports dialog-based wizards and if your terminal
uses the required settings.
Type 'Y' or 'y' to use the dialog-based configuration wizard.
Type 'N' or 'n' to use the console-based configuration wizard.
The following description of configuration options is based on the dialog-
based configuration wizard.
2. Specify the interface to be activated.
Please select interfaces to activate
1 - TTY interface (RAS server)
2 - TTY interface (Fax/Voice server)
3 - CAPI2.0 interface (Fax/Voice server, VoIP Gateway)
4 - CAPI2.0 and TTY interfaces (Universal system)
Type the number of the interface that meets your requirements. Press the
Space bar to activate your selection. Select the 'OK' button and press
ENTER to continue.
3. Select the Diva adapter that you want to configure. Press the Space
bar to activate your selection. Select the 'OK' button and press ENTER.
If you want to exit the configuration with standard settings for your
Diva adapter, select 'Save Configuration and Exit'.
4. The configuration wizard displays an overview of the hardware settings of
the selected Diva Server adapter.
Press ENTER to continue.
5. Select whether you want to operate your Diva Server adapter as terminal
equipment (TE) or as network termination (NT)
Please select interface mode (TE/NT)
0 - Terminal equipment (TE) mode, default
1 - Network terminator (NT) mode
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
Normally, Diva Server adapters are operated as terminal equipment. As
terminal equipment they derive their timing from the signal received
from the NT, e.g. PSTN or PBX, and use this derived timing to
synchronize their transmitted signal.
If you use the Diva Server adapter as network termination, it generates
the timing from which the terminal equipment derives its timing and
synchronization.
Using the Diva Server adapter as NT might be useful in the following
scenarios:
- Diva Server adapters in network termination mode serve as master
in PBX networks that use the Q-Sig protocol. This is the main field
of application.
- Two Diva Server adapters are operated back-to-back. Back-to-back
operation allows to install network-independent test scenarios for
trade shows and to run stress and long-time tests for application
software.
- Diva Server adapters are used as test or measuring device by running
test scripts with third-party software that supports network emulation.
For information on properly connecting Diva Server adapters acting as an
NT to the respective TE, see the printed guide that came with your
adapter.
6. Select your ISDN switch type (D-channel protocol), as provided by your
ISDN service provider:
Please select D-channel protocol
1 - 1TR6 Germany, old protocol for PABX
2 - ETSI DSS1, Europe, Germany
3 - QSIG QSIG, Intra PABX link protocol
4 - T1QSIG QSIG for T1 trunk, Intra PABX link protocol
5 - FRANC VN3, France, old protocol for PABX
6 - BELG NET3, Belgium, old protocol for PABX
7 - SWED DSS1 with CRC4 off, Sweden, Benelux
8 - NI NI1, NI2, North America, National ISDN
9 - 5ESS 5ESS, North America, AT&T
10 - JAPAN Japan, INS-NET64
11 - ATEL ATEL, Australia, old TPH1962
12 - ITALY DSS1, Italy
13 - TWAN DSS1, Taiwan
14 - AUSTRAL Australia, Microlink, TPH1962, On Ramp ETSI
15 - 4ESS_SDN 4ESS Software Defined Network
16 - 4ESS_SDS 4ESS Switched Digital Service
17 - 4ESS_LDS 4ESS Long Distance Service
18 - 4ESS_MGC 4ESS Megacom
19 - 4ESS_MGI 4ESS Megacom International
20 - HONGKONG Hong Kong
21 - RBSCAS Robbed Bit Signaling, CAS
Select the required D-channel protocol. Press the Space bar to activate
the selection. Select the 'OK' button and press ENTER.
7. The following configuration steps depend on the selected switch type:
- If you selected the RBSCAS switch type, see the section 'RBSCAS-specific
settings'.
- If you selected the QSIG or T1QSIG switch type, see the section 'Q-Sig-
specific settings'.
- If you selected any other switch type, see the section 'Advanced
configuration Diva Server PRI adapters'.
--------------------------------------------------------------------------------
RBSCAS-specific settings
--------------------------------------------------------------------------------
1. Specify the trunk mode that your adapter should use.
Please select RBS trunk mode
1 - Wink Start (default)
2 - Loop Start
3 - Ground Start
The trunk mode must correspond to the trunk mode of your switch.
NOTE: The trunk modes are defined in the TIA/EIA-464 specification.
WinkStart is also defined in AT&T TR41458.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
2. Specify the dial type that your adapter should use.
Please select RBS trunk dialing mode
1 - Pulse Dialing
2 - DTMF Dialing (Dual-Tone Multifrequency Signaling, default)
3 - MF Dialing (Multifrequency Signaling)
The dial type must correspond to the dial type of your switch. Most analog
telephones use dual-tone multifrequency signaling.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
3. Specify which bearer capability should be included with the
call that is signaled to the application.
Signal incoming calls as
A - Voice/analog (default)
D - Data/digital
Select 'Voice/analog' if your application handles voice calls, fax
group 3 calls, and analog modem calls. Select 'Data/digital' if your
application handles digital calls, e.g. digital RAS.
Select the required option. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
4. Specify how call collisions are to be resolved if both ends of a line
simultaneously attempt to initiate a call.
Please select RBS glare-resolving party
0 - No (default in NT mode)
1 - Yes (default in TE mode)
If you select 'No', your server will not abort its call attempt to
resolve the call collision but will wait for the other party to do so.
It will then start sending address digits.
If you select 'Yes', your server will stop dialing and return to on-hook
status. It will prepare to receive address digits and the call attempt
from the other end of the line can be completed.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
5. Specify the received digit timeout.
Please select RBS received digit timeout
Select the time interval, in seconds, that may pass between
the incoming dialed digits. If the specified interval is exceeded,
the dialed number is assumed to be complete and the call is
forwarded to the application.
The default setting is 10 seconds.
Select the required time interval. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
6. Specify the answer timeout.
Please select RBS answer timeout
Specify the time interval, in seconds, after which the adapter hangs
up if the remote station does not answer a call.
Default setting is 120 seconds.
Select the required time interval. Press the Space bar to activate the
selection. Select the 'OK' button 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 select direct inward dialing number length
Select a value between 0 and 20. This value specifies the number of
digits that are used to determine the called party number. Commonly,
the number length is set to '4' to match the length of telephone
extensions generated by PBX systems.
8. Continue with step 3 of the section 'Advanced configuration - Diva Server
PRI adapters'.
--------------------------------------------------------------------------------
Q-Sig-specific settings
--------------------------------------------------------------------------------
1. Specify the Q-Sig dialect.
Please select QSig protocol dialect
0 - Autodetect
1 - ECMA-QSIG (older QSig dialect)
2 - ISOV2-QSIG (currently used QSig dialect)
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
2. Specify the channel identifier format.
Please select QSIG protocol channel identifier (CHI)
0 - Timeslots (default)
1 - Logical channels
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
3. Continue with the section 'Advanced configuration - Diva Server PRI
adapters'.
--------------------------------------------------------------------------------
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. 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.
Please select NT-2 (Direct Dial In, Direct Inward Dialing) mode
0 - No
1 - Yes
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
NOTE: This option is not available if you have selected a North American
switch type.
If you select 'Yes', you need to enter the direct inward dialing number
length:
Please select direct inward dialing number length
Select a value between 0 and 20. This value specifies the number of digits
that are used to determine the called party number. Commonly, the number
length is set to '4' to match the length of telephone extensions generated
by PBX systems.
2. Specify the layer 1 framing type.
Please select layer 1 framing
0 - National default (dependent on selected D-channel protocol)
1 - Doubleframing (NO CRC4)
2 - Multiframing (CRC4)
3 - Autodetection
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
3. Specify the voice companding type that is used to transmit analog data
on your line.
Please select voice companding 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 voice
coding for the selected switch type. You need to change this
setting only if the voice coding required by your PBX does not
correspond to the coding of the switch type.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
4. Specify whether your PBX is configured for hunt group operation.
Please configure hunt group operation mode
0 - Standard operation (default)
1 - Hunt group operation (only PABX in H.G. mode)
When you select hunt group operation, dynamic layer 1 management
(dynamic_l1_down) is activated. Dynamic layer 1 management effects the
following behaviour of your Diva Server adapter:
Layer 1 of the Diva Server adapter is switched to high-impedance state
until the application sends a LISTEN request to it.
As long as the Diva Server adapter is in high-impedance state, the PBX
that manages the Hunt Group considers the line of the Diva Server adapter
as not being connected and thus, does not deliver calls to it.
When the Diva Server adapter receives the first LISTEN request from an
application, i.e. the application is ready to receive calls, it switches
to normal operation mode. The PBX is signalled that the adapter is
attached to the port and that calls can be routed to this port. If the
application removes all LISTEN requests from the Diva Server adapter
(application terminated or application failure), the Diva Server adapter
switches back to high-impedance state. Thus, the port is no longer
available to the PBX. This mechanism ensures that no calls are lost.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
5. Specify whether you are using a full E1/T1 line (i.e. 30/23/24 B-channels)
or whether you ordered a fractional line.
Please configure trunk operation mode
0 - Standard operation (default)
1 - Fractional line operation
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
If you have selected 'Fractional line operation', you must also specify
the lowest available channel that is assigned to your fractional line.
Your ISDN service provider can supply the required information.
Please select lowest available channel (fraction start)
Type the number of your lowest channel. Press the Space bar to activate
the selection. Select the 'OK' button and press ENTER.
6. 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.
Please select TEI value
0 - Use standard TEI (TEI 0, default)
1 - Use custom TEI
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
If you have selected 'Use custom TEI' you must enter your TEI value:
Please select TEI value [0...63]
Select your specific TEI value. Press the Space bar to
activate the selection. Select the 'OK' button and press ENTER.
7. Specify the source of local tones.
Please select source of local tones (BUSY/ALERTING)
0 - Tones provided by ISDN equipment (default)
1 - Tones provided by Diva adapter
Normally, local tones are generated by the ISDN equipment. If the ISDN
equipment is not able to generate in-band alert or busy tones, the Diva
adapter can generate these tones to signal to the remote station if an
application is ready to accept a call or if it is busy etc.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
8. Specify if you want to use group optimization for your adapter.
Please configure CAPI call distribution policy (group optimization)
0 - Off (broadcast incoming call to all applications)
1 - On (distribute calls on a per group basis)
Group optimization allows the adapter to create application groups
depending on the LISTEN parameters that the application passes to
the adapter. Every incoming call will be distributed on a per group
basis instead of a per application basis. Thus, only one idle
application in each group and not every idle application that matches
the incoming call will receive the indication about an incoming call.
This feature is useful if you start multiple instances of the same
application (for example multiple instances of a fax server or voice
gateway application) or if your CAPI registers multiple CAPI
applications that use the same LISTEN parameters.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
9. Set the fax speed limit for your adapter.
Please configure global fax options - fax speed limit
0 - No fax speed limit (default)
1 - Limit to 14400 bps
2 - Limit to 9600 bps
3 - Limit to 4800 bps
4 - Limit to 2400 bps
Normally, you do not need to limit the fax speed because the Diva
Server adapter automatically negotiates the appropriate speed.
Type the number of your selection. Press the Space bar to activate
the selection. Select the 'OK' button and press ENTER.
10. Adjust fax options for the T.30 protocol.
Please configure global fax options - T.30 protocol
0 - Disable fine resolution
1 - Disable error correction mode (ECM)
2 - Use ECM frame length of 64 bytes
3 - Disable 2D fax document compression
4 - Disable T6 fax document compression
5 - Disable uncompressed T6 fax document lines
6 - Refuse incoming polling requests
7 - Hide 'total pages' information in fax message
8 - Hide 'headline' information in fax message
9 - Hide 'page info' information in fax message
10 - Disable fallback to lower speed on failure
Activate the options according to your requirements. Select each
option and press the Space bar. When you are done, select the
'OK' button and press ENTER.
11. This concludes the configuration of the Diva Server PRI adapter.
If you have installed several adapters in your system, you can
configure the next adapter.
If the configuration of all adapters is complete, save your
configuration and exit the configuration wizard. Continue with
the section 'Loading the Diva modules'.
--------------------------------------------------------------------------------
Configuring Diva Server 2FX, BRI, and 4BRI Adapters
--------------------------------------------------------------------------------
To configure the settings for your Diva Server 2FX, BRI, or 4BRI adapter,
follow these steps:
1. Change to the /usr/lib/eicon/divas directory and run the following command:
./Config
The 'Diva ISDN Adapter Configuration Wizard' is opened.
Check if your kernel supports dialog-based wizards and if your terminal
uses the required settings.
Type 'Y' or 'y' to use the dialog-based configuration wizard.
Type 'N' or 'n' to use the console-based configuration wizard.
The following description of configuration options is based on the dialog-
based configuration wizard.
2. Specify the interface to be activated.
Please select interfaces to activate
1 - TTY interface (RAS server)
2 - TTY interface (Fax/Voice server)
3 - CAPI2.0 interface (Fax/Voice server, VoIP Gateway)
4 - CAPI2.0 and TTY interfaces (Universal system)
Type the number of the interface that meets your requirements. Press the
Space bar to activate your selection. Select the 'OK' button and press
ENTER to continue.
3. Select the Diva adapter that you want to configure. Press the Space
bar to activate your selection. Select the 'OK' button and press ENTER.
NOTE: If you have installed a Diva Server 4BRI-8M adapter you need to
configure each port of the adapter individually.
4. The configuration wizard displays an overview of the hardware settings of
the selected Diva Server adapter.
Press ENTER to continue.
5. Select whether you want to operate your Diva Server adapter as terminal
equipment (TE) or as network termination (NT).
NOTE: This option is only available for Diva Server BRI-2M 2.0 and Diva
Server 4BRI-8M 2.0 adapters.
Please select interface mode (TE/NT)
0 - Terminal equipment (TE) mode, default
1 - Network terminator (NT) mode
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
Normally, Diva Server adapters are operated as terminal equipment. As
terminal equipment they derive their timing from the signal received
from the NT, e.g. PSTN or PBX, and use this derived timing to
synchronize their transmitted signal.
If you use the Diva Server adapter as network termination, it generates
the timing from which the terminal equipment derives its timing and
synchronization.
Using the Diva Server adapter as NT might be useful in the following
scenarios:
- Diva Server adapters in network termination mode serve as master
in PBX networks that use the Q-Sig protocol. This is the main field
of application.
- Two Diva Server adapters are operated back-to-back. Back-to-back
operation allows to install network-independent test scenarios for
trade shows and to run stress and long-time tests for application
software.
- Diva Server adapters are used as test or measuring device by running
test scripts with third-party software that supports network emulation.
For information on properly connecting Diva Server adapters acting as an
NT to the respective TE, see the printed guide that came with your
adapter.
6. Select your ISDN switch type (D-channel protocol), as provided by your
ISDN service provider.
Please select D-channel protocol
1 - 1TR6 Germany, old protocol for PABX
2 - ETSI DSS1, Europe, Germany
3 - QSIG, Intra PABX link protocol
4 - FRANC VN3, France, old protocol for PABX
5 - BELG NET3, Belgium, old protocol for PABX
6 - NI NI1, NI2, North America, National ISDN
7 - 5ESS 5ESS, North America, AT&T
8 - JAPAN Japan, INS-NET64
9 - ITALY DSS1, Italy
10 - TWAN DSS1, Taiwan
11 - AUSTRAL Australia, Microlink (TPH1962), On Ramp ETSI
12 - HONGKONG Hong Kong
13 - EWSD Siemens, National ISDN EWSD
14 - 5ESS_NI, 5ESS switch National ISDN Lucent
Select the required D-channel protocol. Press the Space bar to activate
the selection. Select the 'OK' button and press ENTER.
NOTES:
- If you select the NI, EWSD Siemens, or 5ESS_NI protocol, you must
enter the Service Profile ID (SPID) values to properly activate your
line. The SPID values are supplied by your ISDN Service
provider. 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 with the management interface utility 'mantool'
without restarting the adapter.
- If you select the QSIG protocol, you need to configure specific
settings for this protocol. See the section 'Q-Sig-specific settings'.
7. See the section 'Advanced configuration - Diva Server BRI and 4BRI
adapters' to continue.
--------------------------------------------------------------------------------
Q-Sig-specific settings
--------------------------------------------------------------------------------
1. Specify the Q-Sig dialect that you are using.
Please select QSig protocol dialect
0 - Autodetect
1 - ECMA-QSIG (older QSig dialect)
2 - ISOV2-QSIG (currently used QSig dialect)
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
2. Specify the call reference and the channel identifier length.
Please select QSIG protocol call reference (CR) and channel identifier (CHI)
length
0 - CR and CHI 2 bytes long (default)
1 - CR 1 and CHI 2 bytes long
2 - CR 2 and CHI 1 byte long
3 - CR and CHI 1 byte long
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
For information on the configuration of all further settings, go to the section
'Advanced configuration - Diva Server 2FX, BRI, and 4BRI adapters'.
--------------------------------------------------------------------------------
Advanced configuration - Diva Server 2FX, 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. If you are using a Diva Server BRI-2M (rev. 1) adapter, specify for which
applications your adapter should be optimized.
Please select adapter profile
0 - No optimization (default)
1 - Optimized for fax/voice/unified messaging
2 - Optimized for RAS
If you use your adapter for RAS applications, select 'Optimized for RAS' to
take advantage of enhanced RAS features, such as V.90. If you implement fax,
voice, or unified-messaging applications, select 'Optimized for fax/voice/
unified messaging' to be able to use enhanced-unified messaging, fax, and
voice features.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
2. 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.
NOTE: This option is not available if you have selected a North American
switch type.
Please select NT-2 (Direct dial in, direct inward dialing) mode
0 - No
1 - Yes
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
If you select 'Yes', you need to enter the direct inward dialing number
length:
Please select direct inward dialing number length
Select a value between 0 and 20. This value defines the number of digits
that are used to determine the called party number. Commonly, the number
length is set to '4' to match the length of telephone extensions generated
by PBX systems.
3. Select the D-channel layer 2 connection mode for your configuration.
Please select D-channel layer 2 activation policy
0 - On Demand
1 - Deactivation only by NT side (default)
2 - Always active
If you select On Demand, the D-channel layer 2 connection is activated
to establish the B-channel data connection and is deactivated as soon as
the B-channel data connection releases.
If you leave the default setting Deactivation only by NT side, the
D-channel layer 2 connection is activated when a B-channel data connection
is established for the first time and is kept active afterwards until
disconnection is requested by the NT side.
The setting Always active effects that the D-channel layer 2 connection
is activated as soon as the ISDN protocol is loaded and is kept active
afterwards.
NOTE: The American protocols NI, 5ESS, EWSD Siemens, and 5ESS_NI require
the setting Always active.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
4. Specify the voice companding type that is used to transmit analog data
on your line.
Please select voice companding 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 voice
coding for the selected switch type. You need to change this
setting only if the voice coding required by your PBX does not
correspond to the coding of the switch type.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
5. Specify whether your PBX is configured for hunt group operation.
Please configure hunt group operation mode
0 - Standard operation (default)
1 - Hunt group operation (only PABX in H.G. mode)
When you select hunt group operation, dynamic layer 1 management
(dynamic_l1_down) is activated. Dynamic layer 1 management effects the
following behaviour of your Diva Server adapter:
Layer 1 of the Diva Server adapter is switched to high-impedance state
until the application sends a LISTEN request to it.
As long as the Diva Server adapter is in high-impedance state, the PBX
that manages the Hunt Group considers the line of the Diva Server adapter
as not being connected and thus, does not deliver calls to it.
When the Diva Server adapter receives the first LISTEN request from an
application, i.e. the application is ready to receive calls, it switches
to normal operation mode. The PBX is signalled that the adapter is
attached to the port and that calls can be routed to this port. If the
application removes all LISTEN requests from the Diva Server adapter
(application terminated or application failure), the Diva Server adapter
switches back to high-impedance state. Thus, the port is no longer
available to the PBX. This mechanism ensures that no calls are lost.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
6. Specify the type of ISDN interface to which your Diva Server adapter is
connected.
Please select trunk operation mode
1 - Point to Multipoint (default)
Allows multiple terminal devices (TEs) to be connected to the BRI
line.
2 - Point to Point (fixed TEI)
Only one TE can be connected to the BRI line. The TEI value must be
set and the source of local tones must be specified in the following
screens.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
- If you have selected the point-to-point interface, 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.
Please select TEI value
0 - Use standard TEI (TEI 0, default)
1 - Use custom TEI
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
If you have selected 'Use custom TEI', you must specify your TEI value:
Please select TEI value [0...63]
Select your specific TEI value. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
- If you have selected the point-to-point interface mode, you must also
specify the source of local tones.
Please select source of local tones (BUSY/ALERTING)
0 - Tones provided by ISDN equipment (default)
1 - Tones provided by Diva adapter
Normally, local tones are generated by the ISDN equipment. If the ISDN
equipment is not able to generate in-band alert or busy tones, the Diva
Server adapter can generate these tones to signal to the remote station
if an application is ready to accept a call or if it is busy etc.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
7. If you are using the 'NI', 'EWSD Siemens', or 'NI_5ESS' switch type and
ordered supplementary services, specify the number of call appearances
and the values of the 'Begin Conference', 'Drop Conference', and 'Call
Transfer' feature activators as specified by your service provider.
8. Specify if you want to use group optimization for your adapter.
Please configure CAPI call distribution policy (group optimization)
0 - Off (broadcast incoming call to all applications)
1 - On (distribute calls on a per group basis)
Group optimization enables the adapter to create application groups
depending on the LISTEN parameters that the application passes to
the adapter. Every incoming call is distributed on a per group
basis instead of a per application basis. Thus, only one idle
application in each group and not every idle application that matches
the incoming call receives the indication about an incoming call.
This feature is useful if you start multiple instances of the same
application (for example multiple instances of a fax server or voice
gateway application) or if your CAPI registers multiple CAPI
applications that use the same LISTEN parameters.
Type the number of your selection. Press the Space bar to activate the
selection. Select the 'OK' button and press ENTER.
9. Set the fax speed limit for your adapter.
Please configure global fax options - fax speed limit
0 - No fax speed limit (default)
1 - Limit to 14400 bps
2 - Limit to 9600 bps
3 - Limit to 4800 bps
4 - Limit to 2400 bps
Normally, you do not need to limit the fax speed because the Diva
Server adapter automatically negotiates the appropriate speed.
Type the number of your selection. Press the Space bar to activate
the selection. Select the 'OK' button and press ENTER.
10. Adjust fax options for the T.30 protocol.
Please configure global fax options - T.30 protocol
0 - Disable fine resolution
1 - Disable error correction mode (ECM)
2 - Use ECM frame length of 64 bytes
3 - Disable 2D fax document compression
4 - Disable T6 fax document compression
5 - Disable uncompressed T6 fax document lines
6 - Refuse incoming polling requests
7 - Hide 'total pages' information in fax message
8 - Hide 'headline' information in fax message
9 - Hide 'page info' information in fax message
10 - Disable fallback to lower speed on failure
Activate the options according to your requirements. Select each
option and press the Space bar. When you are done, select the
'OK' button and press ENTER.
11. This concludes the configuration of this Diva Server BRI adapter.
If you have installed several adapters in your system or you are
using a Diva Server 4BRI-8M, you can now configure the next adapter.
If the configuration of all adapters is complete, save your configuration
and exit the configuration wizard. Continue with the section 'Loading the
Diva Modules'.
--------------------------------------------------------------------------------
Loading the Diva Modules
--------------------------------------------------------------------------------
During installation and 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 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, execute:
'sh /usr/lib/eicon/divas/cfg_util.sh 2'.
If you wish restore these links, 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 restarting your system, you can use the script 'divas_stop.rc'
to stop Diva adapters and unload Diva drivers. 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 <x>',
where <x> is the logical adapter number. In case of adapters that support
multiple interfaces (e.g. 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 you need to create your own
adapter configuration or startup procedure, you have to perform the following
steps to load the 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.
Type './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, 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 as well as the standard options in the command line of
the Divactrl adapter load utility.
Special configuration options can be changed during run time without adapter
restart via the management interface (for example with the Divactrl Mantool
management interface access utility).
--------------------------------------------------------------------------------
Testing Adapter Functionality and Connectivity
--------------------------------------------------------------------------------
The following procedures will help you to verify if the adapter and the ISDN
service is working properly. After configuring 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, type: './tty_test 1 s auto'
On the client side, type: './tty_test 2 <ISDNnumber> 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 the TTY test. Type './tty_test' for a full list or refer to
the section 'TTY_Test Utility' in this document.
--------------------------------------------------------------------------------
ACOPY2 ISDN file server
--------------------------------------------------------------------------------
This tool 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, type:
'./acopy2 -c<X> -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, type:
'./acopy2 -c<Y> -n<ISDNnumber>: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. Type './acopy2' for a full list.
--------------------------------------------------------------------------------
AFAX2 fax server
--------------------------------------------------------------------------------
This tool allows you to test adapter and CAPI 2.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, type: './afax2 -serve -c<X>'
- where <X> is the ISDN adapter number that will
receive the call.
On the client side, type: './afax2 file.sff|file.txt <ISDNnumber> -c<Y>'
- where <Y> is the ISDN adapter number that will issue
the call.
AFAX2 will transmit the 'file.txt' text file or the 'file.sff' SFF file as fax
document to the fax server. The received document will be saved in the
'RCV.SFF' file.
NOTE: Many other options (e.g. packet size, transmission speed, ECM,
compression, fax ID, headline, etc.) and commands (e.g. polling etc.)
are available. Please call './afax2' for a full list.
--------------------------------------------------------------------------------
CHAPTER 4: CONFIGURING THE DIVA SERVER TTY SERIAL PORTS
--------------------------------------------------------------------------------
The TTYDSxx ports must be configured by AT commands (parameters enclosed in
square brackets are optional. Variables are enclosed in angle brackets). The
following AT-command set is supported:
--------------------------------------------------------------------------------
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:
<CalledPartyNumber>[| <Subaddress>][^56k][+i<y> |
+p=btx]
where <y> is the Eicon-specific +I command (see
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 ranging from 0 to 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] - VERBOSE 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<n> - Result code reporting options. Sets normal or
extended result code reporting.
n=0 Enables mimimum information only (plain CONNECT
in case of successful connection establishment,
NO CARRIER in case of dialing/answer error).
n=4 Enables full information (all result codes are
reported).
AT Z[<n>] - Soft reset. Drops the connection if the modem is
in ESCAPE mode. Resets the modem and restores the
selected pre-defined modem configuration profile <n>.
See AT&F below for the list of pre-defined modem
configuration profiles.
AT S<r>=? - Displays the value of the selected S-register <r>.
AT S<r>=<n> - Sets the value <n> of the selected S-register <r>.
Currently registers 0, 2, 7, 9, 10, 27, and 51
are implemented. Writing to all other registers
is accepted.
S-register 0 controls the auto answer functionality.
n=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
or settings and accept the call by the
'ATA' command.
0<n<255 Enables auto answer. Incoming calls are
indicated by a RING and accepted
automatically.
n=255 Ignores all incoming calls.
S-register 2 controls the Escape character:
S2 holds the value of the ASCII character used as the
escape character. The default value corresponds to an
ASCII '+' (43 decimal).
<n> is a range from 0 to 255.
n=127 Disables the escape sequence process, i.e.
no escape character will be recognized.
S-register 7 - Time to wait for carrier.
Sets the time in seconds that the modem will wait for
a carrier before hanging up.
<n> is a range from 0 to 255 seconds.
S-register 9 - Carrier Detect Response Time.
Sets the time in tenths of a second that a carrier
must be present before the modem considers it valid.
<n> is a range from 0 to 255 tenths of a second
This register is only implemented for
compatibility reasons. Write to this register
does not affect the Carrier Detect Response time.
S-register 10 - Delay between carrier loss and hang
up.
Sets the time in tenths of a second that the modem
waits before hanging up after a loss of carrier.
<n> is a range from 0 ... 255 tenths of a second
S-register 27 is a bit mapper register.
<n> is interpreted as a bit mask as follows:
Bit | Value | Result
----+-------+---------------------------------
0 | 1 | Reserved
----+-------+---------------------------------
1 | 2 | Reserved
----+-------+---------------------------------
2 | 4 | Reserved
----+-------+---------------------------------
3 | 8 | Disables 2100Hz answer tone
----+-------+---------------------------------
4 | 16 | Reserved
----+-------+---------------------------------
5 | 32 | Reserved
----+-------+---------------------------------
6 | 64 | Reserved
----+-------+---------------------------------
7 | 128 | Reserved
----+-------+---------------------------------
S-register 51 is a bit mapper register.
<n> is interpreted as a bit mask as follows:
Bit | Value | Result
----+-------+---------------------------------
0 | 1 | Disables error correction for
| | 1200Bps connections
----+-------+---------------------------------
1 | 2 | Disable error correction for
| | V.22bis connections
----+-------+---------------------------------
2 | 4 | Disable error correction for
| | V.32bis connections
----+-------+---------------------------------
3 | 8 | Reserved
----+-------+---------------------------------
4 | 16 | Reserved
----+-------+---------------------------------
5 | 32 | Reserved
----+-------+---------------------------------
6 | 64 | Reserved
----+-------+---------------------------------
7 | 128 | Reserved
----+-------+---------------------------------
S-register 128 is a read-only register.
Reading this register allows to retrieve
information on the current (last) incoming call.
It returns a message in the following format:
;<calling_party_number>;<destination_address>
If calling party or destination sub-addresses
are present, they are separated by '/' from the
called party number or the destination address.
For example, the calling party number 800,
calling party sub-address 900,
destination address 400,
destination sub-address 500 are presented as:
;800/900;400/500
--------------------------------------------------------------------------------
AT\ Commands
--------------------------------------------------------------------------------
AT \V[<n>] - CONNECT message format.
n=0 Plain CONNECT message without any connection
parameters.
n=1 Full CONNECT message including connection
parameters (modulation, compression, transmit/
receive rate).
n=2 Full CONNECT message in multi-line 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[<n>] - Error correction control
n=0|1 Turn error correction, error correction
detection and data compression off
(i.e. connect in transparent mode only).
n=2 Disable V.42 error correction and V.42
error correction detection (i.e. MNP only).
In case of failure, connect in transparent
mode.
n=3|4 Try to establish error correction, try to
detect error correction (any supported).
In case of failure, connect in transparent
mode.
n=5 Force error correction (any).
Disconnect in case of failure.
--------------------------------------------------------------------------------
AT% Commands
--------------------------------------------------------------------------------
AT %C[0|1] - Data compression control
0 - Turn data compression off
1 - Turn data compression on
--------------------------------------------------------------------------------
AT# Commands
--------------------------------------------------------------------------------
AT #CID=? - Displays CID (Caller ID) setting.
The short form of this command is 'CID?'.
AT #CID=<n> - 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.
n=0 No CID indication
n=1 CID indication in RING message
n=2 CID indication in CONNECT message
n=3 CID indication in RING and in CONNECT messages
n=5 CID and DAD indication in RING message
n=6 CID and DAD indication in CONNECT message
n=7 CID and DAD indication in RING and in CONNECT
messages
n=9 Use an 'mgetty' friendly format for CID
indication in RING message
n=15 Use an 'mgetty' friendly format for CID and
DAD indication in RING message
By default 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>
If the 'mgetty' friendly format is used, CID
is indicated as:
RING;CID
DAD (Destination Address) is indicated as:
RING;CID;DAD
If calling party or destination sub-addresses are
present, they are separated by '/' from the called
party number or the destination address.
For example, the calling party number 800,
calling party sub-address 900, destination
address 400, destination sub-Address 500 are
presented as:
RING CID: 800/900 DAD: 400/500
or
RING;800/900;400/500
--------------------------------------------------------------------------------
AT& Commands
--------------------------------------------------------------------------------
AT &C[<n>] - Accepted for comaptibility reasons.
<n> : any integer
AT &G[0...2] - Guard tone options.
0 - Turns guard tone off (default).
1 - Turns 550Hz guard tone on.
2 - Turns 1800Hz guard tone on.
AT &D[<n>] - Data Terminal Ready (DTR) options.
<n> ranges from 0 to 3.
See AT&Q command below.
AT &Q[<n>] - Communication options.
<n> ranges from 0 to 3.
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<n> - Terminal flow control options. Defines the flow
control mechanism.
n=0 Disables flow control.
n=1 Enables RTS/CTS local+remote flow control
(obsolete).
n=2 Enables XON/XOFF flow control (obsolete).
n=3 Enables RTS/CTS local+remote flow control.
n=4 Enables XON/XOFF flow control.
n=5 Enables transparent XON/XOFF flow control.
n=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[<n>] - Resets the modem and restores the selected
pre-defined modem configuration profile.
AT&F sets factory defaults for current profile.
The following pre-defined profiles are supported.
n=14 Autodetection of B-channel protocol
For incoming calls you can use
autodetection of the B-channel protocol.
In this mode the TTY proceeds 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.
n=1 X.75/Transparent/Transparent protocol stack.
Data compression in accordance with V.42bis
is detected automatically for incoming calls.
n=2 V.110 synchronous mode
n=3 V.110 asynchronous mode
n=4 Synchronous modem with V.42/V.42bis
n=5 Asynchronous modem with full negotiation and
V.42/V.42bis
n=6 V.120, 64 kbps
n=7 V.120, 56 kbps
n=8 Bit-transparent access to B-channel data
Note: By default, this profile does not switch
to data mode after the connection was
established.
n=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.
n=10 Same as PROFILE 9, but with 56000 bps
n=11 BTX
n=12 BTX
n=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.
n=16 PIAFS with 32 kbps
n=17 PIAFS with 64 kbps
n=18 PIAFS with 64 kbps, transfer rate autodetect
--------------------------------------------------------------------------------
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<n> - B-channel data adaptation rate, if supported by used
bearer protocol (for example V.110).
n=2 1200 bps
n=3 2400 bps
n=4 4800 bps
n=5 9600 bps
n=6 19200 bps
n=7 38400 bps
n=8 48000 bps
n=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<n> - Delay for AT-command response (msec).
n=0 AT-command response is sent immediately.
0<n<255 AT-command response is delayed.
AT +iF<n> - RNA Framing. Determines if the ASYNC/SYNC conversion
module is inserted on top of OSI Layer 3 and which
mode this module assumes.
n=0 No framing check (pass data transparently).
n=1 Force synchronous conversation (PPP).
n=2 Force asynchronous conversation (PPP).
n=3 Force synchronous conversation (RAS).
n=4 Force asynchronous conversation (RAS).
n=5 Detects required conversation by analyzing incoming
data packets.
AT +iG<n> - RNA patches. Controls the behavior of the ASYNC/SYNC
PPP conversion module.
<n> is interpreted as a bit mask as follows:
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 ranging from 0 to 2048
n=0 Defaults to the maximum frame supported by the
adapter.
AT +iM<n> - Working mode.
n=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.
n=2 Fax mode. TTY switches to this mode as soon as a
Fax CLASS 1 or Fax CLASS 2 command is detected.
n=3 Voice mode (bit-transparent access to B-channel
data).
n=4 RNA mode. TTY operates in framing mode,
investigates protocol data units, and provides
ASYNC/SYNC conversion if necessary.
n=5 BTX over ISDN mode.
n=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 +iN<xxx> - 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<n> - Specifies the protocol stack used to transfer bearer
data.
n=1 L1 - HDLC, L2 - X75SLP and V.42bis data
compression autodetection in case of incoming
connection, L3 - transparent
n=2 L1 - V.110 synchronous mode,
L2 and L3 - transparent
n=3 L1 - V.110 asynchronous mode,
L2 and L3 - transparent
n=4 L1 - analog modem (synchronous mode),
L2 - V.42+V.42bis autodetect, L3 - transparent
n=5 L1 - analog modem with full negotiation,
L2 - V.42+V.42bis autodetect, L3 - transparent
n=6 L1 - HDLC, L2 - V.120, L3 - TA
n=7 L1 - Fax, L2 - transparent,
L3 - T.30 with ECM, T.6, MR, MMR, polling
n=8 L1, L2 and L3 - transparent
n=9 L1 - HDLC, L2 and L3 - transparent
n=10 L1 - HDLC, L2 - X75SLP, L3 - BTX
n=11 external device 0
n=12 L1 - HDLC, L2 - X.75SLP and data compression
autodetection in accordance with V.42bis,
L3 - transparent
AT +iS<xxx> - 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 Compatibility (LLC)
element on the SETUP message.
You can overwrite default values by the AT+IS<xxx>
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 64 kbps Data
7/170 56 kbps Data
7/197 V.110 Rate Adaptation
At +iT<n> - ISDN trace options. Reserved for use by Eicon.
<n> ranges from 0 to 255.
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<n> - Defers receive notifications to <n> bytes/millisecond.
<n> should be in the range of 0 ... 64000.
AT +iX<n> - Respects read block size and defers receive
notifications. <n> should be in the
range of 0 ... 64000.
AT +iY<n> - Defers transmission to <n> bytes/millisecond.
<n> should be in the range of 0 ... 8.
AT +iZ<n> - Splits large frames into <n> byte segments.
<n> 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 compatibility
(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 - Selects global TTY mode.
This command is used on broken ISDN links that
provide wrong call-type information over the
signaling channel.
If operating on such channels, it is necessary to
enforce the TTY driver to handle all incoming calls
in a specific way independent of the signaled call
type. This command affects all virtual tty interfaces
exposed by the Diva TTY driver and can be changed
only by unloading the driver or issuing another
+IE command.
Currently this feature is implemented for China PIAFS
links (where it activates additional China-specific
extensions of the PIAFS protocol):
AT&F16+IE=piafs32k - China 32K PIAFS link
AT&F17+IE=piafs64k - China 64K PIAFS link
AT&F18+IE=piafs - China variable speed PIAFS link
AT+IE=none - Resets all tty interfaces to
to 'default' mode (i.e. signaling
information will be used to
determine the call type).
AT +iQ=<n> - Sometimes it is necessary to bind an outgoing call to a
specific adapter (by default, the first available adapter
is selected). This command allows you to bind the TTY
interface to a specific adapter by specifying the adapter
number (x):
n=ox Bind TTY to adapter X for all outgoing calls.
n=ix Bind TTY to adapter X for all incoming calls.
n=ax Bind TTY to adapter X for all calls.
n=o0 Erase TTY binding for outgoing calls.
n=i0 Erase TTY binding for incoming calls.
n=a0 Erase TTY bindings for incoming and outgoing calls.
n=? Display current bindings.
AT +MF=<data bits>, - Sets UART framing parameters
<parity>,<stop bits> Data Bits:
data bits=8 8 data bits
data bits=7 7 data bits
data bits=5 5 data bits
Parity:
parity=N none
parity=O odd
parity=E even
parity=S space
partiy=M mark
Stop Bits:
stop bits=1 one stop bit
stop bits=2 two stop bits
The transmission rate is derived from the actuallly
selected Rx/Tx transmission speed (+MS command).
Example:
AT+MF=8,N,1 - select 8 data bits, no parity and one
stop bit.
AT +MF? - Returns currently selected framing.
AT +MF=? - Returns list of supported parameters.
AT +MS? - Modulation Selection Query
The response to the query has the following format:
AT +MS: <mod>,<auto>,<min>,<max>,<min_rx>,<max_rx>
See Modulation Selection Set below for explanations
of the variables.
AT +MS=[<mod>] - Modulation Selection Set
[,[<auto>] Modulation Data Rate Range
[,[<min>] ---------- ---------------
[,[<max>] mod = B103: 300 bps
[,[<min_rx>] mod = B212A: 1200 bps
[,[<max_rx>]]]]]] mod = V21: 300 bps
mod = V22: 1200 bps
mod = V22B: 1200 - 2400 bps
mod = V23C: Tx:75 bps/Rx:1200 bps outgoing call
Tx:1200 bps/Rx:75 bps incoming call
mod = V32: 4800 - 9600 bps
mod = V32B: 4800 - 14400 bps
mod = V34: 2400 - 33600 bps
mod = V90: 28000 - 56000 bps download
(client <- server)
28000 - 32000 bps upload
(client -> server)
Try other modulations if the specified modulation
cannot be used.
auto = 0: Use only the specified modulation.
auto = 1: Try other modulations with lower data rates.
min = Minimum transmit data rate.
max = Maximum transmit data rate.
min_rx = Minimum receive data rate.
max_rx = Maximum receive data rate.
Only V90 modulation has different transmit/receive
rates. Rate = 0 means no minimum or maximum limitation.
Valid Rate Values (in bps):
75, 300, 600, 1200, 2400, 4800, 7200, 9600, 12000, 14400,
16800, 19200, 21600, 24000, 26400, 28000, 28800, 29333,
30667, 31200, 32000, 33600, 33400, 34667, 36000, 37333,
38000, 38667, 40000, 41333, 42000, 42667, 44000, 45333,
46000, 46667, 48000, 49333, 50000, 50667, 52000, 53333,
54000, 54667, 56000, 0
--------------------------------------------------------------------------------
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.
AT +FCLASS=? - Displays all supported modem classes.
AT +FCLASS=<n> - Configures the modem for modem class <n>.
n=0 Data mode
n=1 EIA class 1
n=2 EIA class 2
AT +FMFR? - Returns the name of the modem manufacturer.
AT +FMDL? - Returns the name of the modem model.
AT +FREV? - Returns the product version.
AT +FLPL=<n> - Control class 2 polling capability
n=0 - Normal operation
n=1 - Document available for polling
--------------------------------------------------------------------------------
'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 is 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 is 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)
--------------------------------------------------------------------------------
The Eicon Diva TTY driver allows to control the state of TTY interfaces through
an additional device node with MAJOR 8 and MINOR 0. This device node named
/dev/ttydsctrl is created during default installation.
Commands of the TTY control interface are used as ASCII strings and have the
following format:
<N>:<command_string>
where:
- <N> is the decimal number that selects the TTY interface.
- <command_string> is the command to be issued on the TTY interface.
All commands are issued via the write or ioctl system call. The return value
of this system call (success or failed) is used to indicate the result of the
operation.
In order to issue the command via the ioctl interface, you must write the
command into a buffer with a length of 64 bytes including the terminating zero.
The ioctl command will receive the output (if any) in the same buffer and
return the amount of bytes stored in the buffer.
The ttysctrl utility can be used to access the Eicon Diva TTY control
interface via the ioctl system call.
The TTY control interface allows:
- To check if the selected TTY interface is opened.
The used command string is 'open'.
If the interface is opened, the operation will return 'success'. If the
interface is not opened, the operation will return 'failed'.
- To check if the selected TTY interface is online.
The used command string is 'dcd'.
If the interface is online (i.e. not in command mode), the operation will
return 'success'. If the interface is offline or not opened, the operation
will return 'failed'.
- To issue a HANGUP command to the selected TTY interface. If the interface
is online, the result of this command is the same as for an ATH
command.
The used command string is 'h'.
If the command is successful, it will return 'success'. If it fails (TTY
interface not opened by application), 'failed' is returned.
- To issue a HANGUP+RESET command to the selected TTY interface. If the
interface is online, the result of this command is the same as for
an ATZ command.
The used command string is 'z' or 'z<x>', where <x> is the decimal number of
the Eicon Diva TTY profile.
If the command is successful, it will return 'success'. If it fails (TTY
interface not opened by application or invalid profile number), it will
return 'failed'.
- To issue an AT-command sequence to the selected TTY interface. This
command can only be issued if the modem is offline.
Any valid command string can be used.
If the command is successful, it will return 'success'. If it fails
(TTY interface not opened by application, invalid command, or TTY
interface is online), it will return 'failed'.
- To issue an additional 'status' message in order to obtain the modem
status (online/offline) and parameters of current or the last
connections (used protocol, transmission speed) if the ioctl interface
is used (IOCTL command code 0x3701). The output is stored in the same
buffer that was used to pass the command to the Eicon Diva TTY interface
as zero-terminated ASCII string including the terminating zero.
All operations described above happen fully hidden from the application
that owns the selected TTY interface.
Examples:
- Use the 'ttydsctrl' application to retrieve the 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
In case of success, this command returns the port status in the
following format:
DCD [ON|OFF] CID: <x>[/<y>] DAD: <z>[/<h>]
or
DCD [ON|OFF] CID: <x>[/<y>] DAD: <z>[/<h>] CONNECT <protocol>/[<opt>/]<speed>
where:
- <x> is the calling party number (if any)
- <y> is the calling party number sub-address (if any)
- <z> is the destination address (if any)
- <h> is the destination sub-address (if any)
- <protocol> is the currently (last) used protocol. It can be one of the
following protocols: MODEM, PIAFS, X75, V110, V120, FAX, G.711, HDLC,
BTX, X75V42
- <opt> are the protocol options (if any).
The options can be one of the following: DAP, RTP, VR1, VR2, FTR for
PIAFS protocol.
They can be any conbination of: V21, V23, V22, V22BIS, V32, V32BIS, V34,
BELL212A, BELL103, V90, and LAPM/V42BIS, LAPM, MNP5, MNP for analog
modem.
- <speed> is the current (last) connection speed in the format
TxSpeed/TXRxSpeed/RX for analog modem or a single number for all
other protocols.
- Use the 'ttydsctrl' application to issue the
'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 interface is online ?"
else
echo "Modem hangup+reset OK, TTY will not accept any more calls"
echo "and profile settings were changed to 5 (Analog Modem)"
fi
Since all commands are built as ASCII strings and issued via
the 'write' system call, the 'echo' command can be used.
NOTE: The return code is not valid for some kernels or
distributions. Use 'ttydsctrl' if you run into problems.
Examples:
- 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
- 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
- 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
- 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 more calls"
echo "and original profile settings are recovered"
fi
- 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 more calls"
echo "and profile settings were changed to 5 (Analog Modem)"
fi
- 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 interface is online?"
else
echo "Modem hangup+reset OK, TTY will not accept any more calls"
echo "and profile settings were 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.
--------------------------------------------------------------------------------
CHAPTER 5: UNINSTALLING DIVA SERVER FOR LINUX
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Unloading the Diva Server Modules
--------------------------------------------------------------------------------
The Diva Server driver modules can be unloaded simply by executing:
'./divas_stop.rc'
This script is located in the '/usr/lib/eicon/divas' directory.
If you wish to stop and unload Diva drivers manually, you have to proceed as
described below:
1. Login as 'root' (or use 'su')
2. If you have started any tools that access the CAPI or Diva Server TTY
interfaces, stop these tools to release the interfaces.
3. If you have modified /etc/inittab or /etc/ttys to start getty/mgetty/ppp
on one of the Diva TTY interfaces, remove these entries from these files
and execute 'kill -HUP 1' (or kill the appropriate processes manually).
4. Check that the Divastty, capi and divacapi modules are not busy (call
'lsmod' to check it).
5. Execute 'rmmod capi && rmmod divacapi && rmmod kernelcapi' to unload
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, login as 'root' (or
use 'su') and execute:
'rpm -e divas4linux_<a_b_cc_dd>_<ee>-<ff-xxx.yy-z>',
- where 'divas4linux_<a_b_cc_dd>_<ee>-<ff-xxx.yy-z>' is the name of the
installed rpm package without the '.i386.rpm' extension. For example, if you
have installed the package 'divas4linux_2_2_16-101.2-1.i386.rpm', execute
'rpm -e divas4linux_2_2_16-101.2-1' in order to uninstall this package.
NOTE1: The pre-uninstall script contained in the rpm package stops and
unloads all drivers by means of '/usr/lib/eicon/divas/divas_stop.rc'.
It also removes all symbolic links used to start the Diva drivers
on system startup. If the 'divas_stop.rc' configuration script detects
that drivers are still in use (an application or driver still accesses
one of the interfaces) and cannot be stopped, the uninstalling process
is aborted before any changes are applied.
NOTE2: If you do not know which applications or drivers access interfaces
of Diva drivers or you cannot stop these applications, execute
'sh /usr/lib/eicon/divas/cfg/cfg_util.sh 2'. This removes the
symbolic links S03DIVA4LINUX from the '/etc/rc.d/rc...d or
/sbin.init.d/rc...d directories. Restart your system.
The Diva drivers are not loaded on system startup and can be
uninstalled. You can identify the applications or drivers that
accessed Diva drivers by error messages on the console and in
the 'var/log/messages' file.
NOTE3: If you do not know the name of the installed RPM package,
execute: 'rpm -q -a | grep divas4linux' in order to get the
package name from the database maintained by RPM.
You can manually remove the Diva Server for Linux files from your system,
but this is not recommended as it will leave the package entry in the RPM
database and may cause problems reinstalling the package.
Manual removal might become necessary if your RPM database was corrupted or
destroyed.
In order to uninstall the 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' fails to stop and
unload the drivers, proceed as described 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*.
--------------------------------------------------------------------------------
CHAPTER 6: TROUBLESHOOTING
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Troubleshooting Procedure
--------------------------------------------------------------------------------
The troubleshooting section is divided into two sections. The first section
guides you through some tests that you can perform to try to 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 Diva Server for Linux driver modules, (you do
not 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 the drivers, execute the following sequence of commands
manually:
NOTE: Executing 'sh /usr/lib/eicon/divas/cfg_util.sh 2' removes the symbolic
links that load Diva Server for Linux at system start. Executing
'sh /usr/lib/eicon/divas/cfg_util.sh 1' re-creates these links.
1. Login as 'root' (us use 'su')
2. Change your 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 your 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 <parameters> -c <x> >> report.txt 2>&1 &&
sync'
- Where <parameters> are the parameters that you use to start this adapter
(for example -f ETSI).
- Where <x> is the Diva adapter number.
You can repeat this step for all Diva 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 provide the desired results, provide the
following information to Eicon's customer support for analysis:
- An exact problem description: a step-by-step description of your
actions, the result that you expected, and the actual results that you
received.
- Type and serial number of the adapters installed in your machine.
- Purpose of the adapter and the application being used.
- The information captured in the 'report.txt' file by running the
'divas_sys_info.sh' script that is located in the '/usr/lib/eicon/divas'
directory.
--------------------------------------------------------------------------------
TTY_TEST Utitlity
--------------------------------------------------------------------------------
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> [-l<frame_length> -s<rate>]'
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> [-l<frame_length> -s<rate>]&'
This command starts a test server in the background. In this mode, the test
server detaches from your console and does not display any output. 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.
- v120 - 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
NOTE: 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 automatically inserted if necessary (as a
result of the analysis of the first frames transferred
over the link).
-l<frame_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.
-s<rate> - 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> [-l<frame_length> -s<rate>]
[-a<at_command>] [-y] [-m<packets>]'
This command starts a test client on your console.
'./tty_test <tty_nr> <CPN> <protocol> [-l<frame_length> -s<rate>]
[-a<at_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 display any output. 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 V.110 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
NOTE: 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 if necessary (as result
of the analysis of the first frames transferred over
the link).
-l<frame_length> - Optional. Test frame length. It is required if the -s option
follows. Default setting is 512 bytes.
-s<rate> - 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.
-a<at_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.
-m<packets> - 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
compatibility (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 on 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 ENTER 'r' ENTER.
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 ENTER 'R' ENTER. If you are in 'no CR' mode, ENTER 'r' ENTER writes
a <CR> to TTY.
In terminal mode, you can view the content of the virtual Modem Status
Register if you enter ENTER 'show msr' ENTER. 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 ENTER 'DTR+' ENTER, the DTR line will be set. If you enter
ENTER 'DTR-' ENTER, the DTR line will be cleared (TIOCMBIS and TIOCMBIC
ioctl codes).
To quit the TTY_Test terminal mode, enter ENTER 'q' ENTER.
--------------------------------------------------------------------------------
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'
-------------------------------------------------------------------------------
Trace and Debug Utilities
-------------------------------------------------------------------------------
The Divactrl trace utility can help you analyze problems if you
have trouble with connections or functionality.
Divactrl provides the following capabilities for adapter tracing and
debugging:
- 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. See 'XLOG Trace and Debug
Utility'.
- 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 has changed to 'trapped'. The 'core'
image is useful for post mortem debugging and problem analysis.
See 'Core Dump Generation Utility'.
- 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. See 'MLOG Trace and Debug
Utility'.
- Access to the D-channel (dchannel) that allows you to trace D-channel
messages and to monitor layer 1 and layer 2 states of the ISDN interface on
your adapter. See 'D-channel Trace and D-channel Health Monitoring Utility'.
--------------------------------------------------------------------------------
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),
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'
NOTE: Execute this command after the adapter is in a 'trapped' state.
--------------------------------------------------------------------------------
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 which kinds of events should be traced. 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
MLOG<x>.txt file. <x> is the selected adapter number (1 by
default). This command cannot be used together with the '-w'
command and overwrites the '-w' command.
-w<n> - Write formatted and converted log stream to a ring buffer with
maximum size of <n> KB. The available range is 128KB < n < 257 MB.
Smaller values than 128KB are set to 128KB. The 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 with the '-r'
command line option. The '-w' command cannot be used together
with the '-o' command. The '-o' command overwrites the '-w'
command.
-r<y> - Recover information from the ring buffer and write it to file <y>.
- Adapter selection
Command line switches
------------------------------------------------------------------------------
-c <x> - Select adapter number <x>.
- Control of B-channel trace
Command line switches
------------------------------------------------------------------------------
-b - Turn B-channel trace off.
-l<n> - Set maximum B-channel data trace length to <n>. If the entire
B-channel data packet is longer than <n>, only the first <n>
bytes are written to the log interface.
#<b> - Select B-channel. Allows tracing of B-channel data only for
B-channels specified in <b>. <b> is a 32-bit hex value. If
bit <n> is set, tracing of the corresponding B-channel is allowed.
Example: 0x03 returns a trace for B-channel 1 and B-channel 2.
-A<b> - Select B-channel for audio tap processing. Allows recording of
transparent B-channel data only for B-channels specified in
<b>. <b> is a 32-bit hex value. If bit <n> is set then audio tap
processing of the corresponding B-channel is allowed.
Example: 0x03 turns audio tap processing for B-channel 1 and
B-channel 2 on.
Audio tap processing allows to receive a bit transparent Tx/Rx
data stream for analog connections (analog modem, fax G3).
The audio stream is forwarded to the application as sequence of
pairs of bytes Tx/Rx coded as G.711 in accordance with national
settings.
- 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
Run-time commands
------------------------------------------------------------------------------
? - Display help screen.
- Control
Run-time commands
------------------------------------------------------------------------------
q - Stop tracing and exit MLOG.
- Control of B-channel trace
Run-time commands
------------------------------------------------------------------------------
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 tracing of B-channel data only
for B-channels specified in the mask. The trace mask is a 32-bit
hex value. If bit <n> is set, tracing of the corresponding
B-channel is allowed.
Example: 0x03 returns a trace for B-channel 1 and B-channel 2.
A - Select audio tap processing mask. See '-A' command line switch
for more details.
- Event control
Run-time commands
------------------------------------------------------------------------------
s - Enable/disable (toggle) trace events from protocol code.
d - Enable/disable (toggle) D-channel traces.
--------------------------------------------------------------------------------
D-channel trace and D-channel health monitoring utility
--------------------------------------------------------------------------------
The Divactrl package contains a D-channel trace tool that allows you to
capture D-channel messages and monitor the layer1 and layer2 state of the ISDN
interface on the selected adapter. It operates in two modes, trace mode and
monitor mode.
In trace mode, the D-channel monitor serves as ISDN diagnose or trace
tool. Its output can be traced for different events allowing you to create
your own monitoring tools.
To start the D-channel monitoring tool in trace mode execute:
'divactrl dchannel -c <x> [<parameters>]'
where:
<x> is the logical adapter number to be traced. <x> is mandatory.
Started without optional parameters, the D-channel monitoring tool captures
all messages received or sent over the D-channel (including the layer 2 header)
and writes a hex dump of these messages as ASCII characters to the standard
output.
Example:
DTRC: 02 01 01 01
DTRC: 00 01 00 02 08 01 82 0D 18 01 89
The following optional parameters can be used to change the destination type of
the output:
Parameter Destination type of output
--------- --------------------------
-xlog Use Eicon Networks 'xlog' format for output of D-channel
messages. This format uses the header D-[R,X](<Y>), where 'R' is
used for received messages, 'X' is used for sent messages and Y
is the message length including the 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 the system log
receives a header that contains the logical adapter number, the
adapter name, and the adapters serial number.
-dmonitor This option allows you to output additional trace information
containing layer 3 messages as seen by the internal state machine
(as hex dump, without layer 2 header) and layer 3, layer 2, and
layer 1 state events in decoded plain text.
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 standard output or standard error. Exit
silently in case of error and report the error by return code
only.
-Debug Print additional information that can help determine the cause
of failure. This option is ignored if the Silent option is
enabled.
In monitor mode, the D-channel monitor runs in the background as daemon and
reports status changes of layer 1 and (or) layer 2 to the user applications
that are executed when the status changes.
To start the D-channel monitoring tool in monitor mode execute:
'divactrl dchannel -c <x> -monitor <y> [<parameters>]'
where:
- <x> is the logical adapter number to be traced. <x> is mandatory.
- <y> is the user application to be executed if the state of layer 1 or layer 2
changes.
This application is called with three parameters:
1 - Logical adapter number
2 - Layer, that changes its state (1 for layer 1, and 2 for layer 2)
3 - State after change (1 - UP, 0 - DOWN)
If the D-channel monitor fails to start the application or the application exits
with an error, the D-channel monitor will report the failure to the system log.
The following optional parameters can be used to change the destination type of
the output:
Parameter Destination type of output
--------- --------------------------
-l1off Do not monitor changes of the layer 1 status.
-l2off Do not monitor changes of the layer 2 status. This might be
necessary for BRI interfaces if layer 2 is controlled by the NT
side or is established 'on Demand'.
-syslog Redirect output to system log file. Every record in system log
will receive a header that contains the logical adapter number,
adapter name, and the adapters serial number.
-dmonitor This option allows you to output additional trace information to
the system log (please see the example above).
You can safely terminate the D-channel monitor using the TERM or HUP signal.
--------------------------------------------------------------------------------
CHAPTER 7: MANAGEMENT INTERFACE
--------------------------------------------------------------------------------
The management interface can be used to control adapter the configuration at
run time without reloading or restarting the Diva adapter. It can also be used
as source of information and events for an SNMP interface or 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 a directory name
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 a value
- event: variable that can be read and used as source of events which are
generated when the state (value) of this variable changes
To access the management interface, use the Mantool utility (see below).
--------------------------------------------------------------------------------
Mantool Management Interface Access and Monitoring Utility
--------------------------------------------------------------------------------
The Divactrl package contains the Mantool utility that allows you to access
(read or write) directories and variables of the management interface. It also
allows you to turn on events and receive notifications from these events when
the corresponding variable's state changes.
To start the Mantool utility, type:
'divactrl mantool -c <x> <parameters>"[<path>]"
where:
- <x> is the logical adapter number.
- <parameters> specify the action to be taken.
- <path> is the path to the directory or variable in the management interface
that you want to access.
The following parameters can be used with the Mantool utiliy:
Parameter Action
--------- ------
-r Reads the content of management interface directory
or variable specified in [path].
-w Sets the value of the management interface variable
specified in [path].
-e Executes the management interface function specified
in [path].
-m Monitors incoming/outgoing calls (line activity).
-a Monitors state changes of analog modem hardware
(Connection progress and reporting)
-g Monitors state changes of Fax G3 hardware
(Connection progress and status reporting)
NOTES:
- The '-w' parameter can only be used with variables that have the 'W'
attribute (see table below).
- The '-e' parameter can only be used with variables of the 'MI_EXECUTE'
type.
- '-m', '-a', and '-g' parameters can be used in combination.
- If you use the Divactrl Mantool from scripts (i.e. not interactively),
add the '-b' option to turn interactive mode off.
Examples:
- Read the content of the root directory of the management interface:
'divactrl mantool -c <x> -r'
- Read how many incoming calls were rejected because the user was busy:
'divactrl mantool -c <x> -r"State\\Incoming Calls\\User Busy"'
- Read directory that contains information about B-channel number 1
(active/idle, call type, call owner, ... ):
'divactrl mantool -c <x> -r"State\\B1"'
- Set value of 'NT-2' management interface variable to 1 to activate
NT-2 (direct inward dialing) mode:
'divactrl mantool -c <x> -w"Config\\NT-2=1"'
- Disconnect the call on B-channel number 1 by executing the clear call
function:
'divactrl mantool -c <x> -e"State\\B1\\Clear Call"'
--------------------------------------------------------------------------------
Management Interface Structure
--------------------------------------------------------------------------------
The following tables describe the content of the management interface
directories. They 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
the trace information).
--------------------------------------------------------------------------------
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
within which only a restricted
number of redial attempts
is possible. The possible
number of attempts is defined
by the 'Redial-Attempts'
variable. After the 'Redial-
Timeout' has expired, new
redial attempts may be made.
Redial-Attempts MI-UINT W Sets the number of redial
attempts that may be made within
the period defined in 'Redial-
Timeout'.
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. Only writeable
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 appearances (CACH = Call
Appearance Call Handling).
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 resetting the
D-channel protocol state, i.e.
state will be changed later
after last active connection
is 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 Selects auto detection of
layer 1 framing type.
CRC4 MI_EXECUTE Selects CRC4.
No CRC4 MI_EXECUTE 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 calls refused
because the user was busy.
No Answer MI_UINT RO Number of calls refused
because remote station did
not answer.
Wrong Number MI_UINT RO Number of calls refused
because invalid number was
dialed.
Call rejected MI_UINT RO Number of calls refused
because remote station
rejected the call.
Other failures MI_UINT RO Number of calls refused
because of other reasons than
the ones mentioned above.
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 calls refused
because the user was busy.
Call rejected MI_UINT RO Number of calls refused
because they were rejected.
Wrong number MI_UINT RO Number of calls refused
because an invalid number
was dialed.
Incompatible MI_UINT RO Number of calls refused
destination because the destination was
not compatible with the TE.
Out of order MI_UINT RO Number of calls refused
because destination was out
of order.
Ignored MI_UINT RO Number of calls refused
because the call was ignored.
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 only available 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
Range: 0...9 intrusion tone melody.
Muting on/off MI_UINT W Switches 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 utility (to
view the manual, execute '/usr/lib/eicon/divas/divactrl mantool' without any
parameter).
--------------------------------------------------------------------------------
Features
--------------------------------------------------------------------------------
Each of Eicon's Diva adapters provides different features and
capabilities with Diva Server for Linux. The table below outlines the feature
set of Eicon Diva adapters.
All features may not be available on all the supported interfaces.
The interfaces supported by Eicon Diva adapters are as follows:
- IDI ISDN Direct Interface
Supports all features and capabilities of Eicon ISDN adapters.
- COM Port (TTY interface)
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 | 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 | 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
--------------------------------------------------------------------------------
PIAFS 1.0 and 2.1 2) | X | X |
--------------------------------------------------------------------------------
Automatic call type and PPP frame type | | X |
detection | | |
--------------------------------------------------------------------------------
Async/sync conversion | | 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) | | |
--------------------------------------------------------------------------------
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 5) | X
--------------------------------------------------------------------------------
Speed and feature indication | X | | X
(polling and ECM) 1) | | |
--------------------------------------------------------------------------------
New fax header line 1) | X | | X
--------------------------------------------------------------------------------
Page formats: ISO A4, ISO B4, ISo A3 1)6) | X | | X
--------------------------------------------------------------------------------
Resolution: standard, fine, | X | | X
ultra-fine 1)6) | | |
--------------------------------------------------------------------------------
DTMF tone detection and transmission 1) | X | X | X
--------------------------------------------------------------------------------
Cross-board switching (via line | X | | X
interconnect) 1)6) | | |
--------------------------------------------------------------------------------
Media mode (unknown, interactive | X | |
voice, automated voice) 1) | | |
--------------------------------------------------------------------------------
Wave audio format (8 bit 8 kHz A-Law, | X | X |
8 bit 8 kHz u-Law, 8 bit 8 kHz PCM, | |(8 bit 8 kHz |
16 bit 8 kHz PCM) 1) | |A- u. u-Law) |
--------------------------------------------------------------------------------
Echo cancellation 1)6) | | | X
--------------------------------------------------------------------------------
Real time protocol (RTP) 1)6) | | | X
--------------------------------------------------------------------------------
Comfort noise generation (CNG) 1)6) | | | X
--------------------------------------------------------------------------------
Voice activity detection (VAD) 1)6) | | | X
--------------------------------------------------------------------------------
Dynamic anti-jitter buffer 1)6) | | | X
--------------------------------------------------------------------------------
Supplementary Services: 3)
--------------------------------------------------------------------------------
MSN (multiple subscriber number) | X | X | X
--------------------------------------------------------------------------------
DDI (direct dialing-in) | X | X | X
--------------------------------------------------------------------------------
SUB (sub-addressing) | X | | X
--------------------------------------------------------------------------------
CLIP (calling line identification | X | X | X
presentation) | | |
--------------------------------------------------------------------------------
CLIR (calling line identification | X | | X
restriction) | | |
--------------------------------------------------------------------------------
COLP (connected line identification | X | | X
presentation) | | |
--------------------------------------------------------------------------------
COLR (connected line identification | X | | X
restriction) | | |
--------------------------------------------------------------------------------
KEY (keypad protocol) | X | | X
--------------------------------------------------------------------------------
TP (terminal portability) | 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) | X | | X
--------------------------------------------------------------------------------
HOLD (hold and retrieve a call) | X | | X
--------------------------------------------------------------------------------
ECT (explicit call transfer) | X | | X
--------------------------------------------------------------------------------
AoC (advice of charge) | X | | X
--------------------------------------------------------------------------------
Three-party conference | X | | X
--------------------------------------------------------------------------------
Large conference 6) | X | | X
--------------------------------------------------------------------------------
User-to-user signaling | X | | X
--------------------------------------------------------------------------------
Voice over Packet:
--------------------------------------------------------------------------------
VoIP 4) | X | | X
--------------------------------------------------------------------------------
Others:
--------------------------------------------------------------------------------
Transparent D-channel | X | | X
--------------------------------------------------------------------------------
X.25/D-channel including AO/DI support | X | | X
--------------------------------------------------------------------------------
1) Features are not available with Diva Server PRI adapters without modules,
Diva Server PRI-0M adapters and Diva Server T1/PRI adapters without
additional DSPs.
2) PIAFS support is only available with Diva Server BRI-2M 2.0, 4BRI-8M 2.0,
and PRI 2.0. and T1/PRI adapters with additional DSPs.
3) For an overview on supplementary services support by the various switch
types, see the section 'Supplementary Services'.
4) Feature is only available with VoIP-enabled Diva Server adapters.
Feature includes Echo Cancellation, Voice Compression,
Tone generation and recognition and RTP, UDP, and IP packet handling.
5) The COM Port supports fax polling for Fax Class 1 only.
6) Features are not available with Diva Server BRI-2M (rev.1) adapters.
---------------------------------------------------------------------------------
Supplementary Services
---------------------------------------------------------------------------------
The Diva Server for Linux software supports basic call services for all
available switch types. In addition to this, it offers supplementary services
for the following switch types:
- Euro-ISDN (ETSI) BRI and PRI
- 5ESS Custom (AT&T)
- 5ESS NI (Lucent/Avaya)
- DMS 100 (Nortel)
- Q-Sig
Q-Sig support is available for the derivatives ETSI-SS, ECMA-QSIG, and
ETSI-QSIG. Thus, the Q-Sig switch type can be used with any PBX based on one
of these derivatives.
Q-Sig has been tested with a number of various switches, for example,
Hicom 150, Hicom 300, Lucent Definity, Alcatel 4200, Alcatel 4400, Ericsson
MD 110, Nortel Meridian, and Nortel M65xx.
The table below gives a detailed overview of the supplementary services
supported by the switch types listed above. The availability of supplementary
services also depends on your PBX. For detailed information on supplementary
services supported by your PBX, contact the PBX manufacturer.
--------------------------------------------------------------------------------
Supplementary services with switch | Euro-ISDN | Euro-ISDN | QSig | 5ESS Custom
type | (ETSI) PRI| (ETSI) BRI| | 5ESS NI
| | | | DMS 100
--------------------------------------------------------------------------------
MSN (multiple subscriber number) | X | X | X | X
| | | | (incoming)
--------------------------------------------------------------------------------
DDI (direct dialing-in) | X | X | X |
--------------------------------------------------------------------------------
SUB (sub-addressing) | X | X | X | X
--------------------------------------------------------------------------------
CLIP (calling line identification | X | X | X | X
presentation) | | | |
--------------------------------------------------------------------------------
CLIR (calling line identification | X | X | X | X
restriction) | | | |
--------------------------------------------------------------------------------
COLP (connected line identification| X | X | X | X
presentation) | | | |
--------------------------------------------------------------------------------
COLR (connected line identification| X | X | X | X
restriction) | | | |
--------------------------------------------------------------------------------
KEY (keypad protocol) | X | X | X | X
--------------------------------------------------------------------------------
AoC (advice of charge) | X | X | X |
--------------------------------------------------------------------------------
User-to-user signaling | X | X | X |
--------------------------------------------------------------------------------
TP (terminal portability) | | X | | X
--------------------------------------------------------------------------------
Call forwarding unconditional | | X | |
--------------------------------------------------------------------------------
Call forwarding busy | | X | |
--------------------------------------------------------------------------------
Call forwarding no reply | | X | |
--------------------------------------------------------------------------------
Call deflection | | X | |
--------------------------------------------------------------------------------
CW (call waiting) | | X | | X
--------------------------------------------------------------------------------
HOLD (hold and retrieve a call) | X 1) | X | X 2)| X 4)
--------------------------------------------------------------------------------
ECT (explicit call transfer) | | X | X 3)| X 4)
--------------------------------------------------------------------------------
Three-party conference | | X | | X 4)
--------------------------------------------------------------------------------
Large conference | | X 4) | | X 4)
--------------------------------------------------------------------------------
Drop conference | | X | | X 4)
--------------------------------------------------------------------------------
Name identification services | | | X | X
| | |pres. |presented
| | |by |by network
| | |switch |
--------------------------------------------------------------------------------
Escape message types | | | | X 4)
| | | |5ESS custom
| | | |only
--------------------------------------------------------------------------------
Call Appearance/Call Handling | | | | X 4)
(CACH) plus configuration | | | |
--------------------------------------------------------------------------------
Feature activators plus | | | | X 4)
configuration | | | |5ESS NI +
| | | |DMS 100 only
--------------------------------------------------------------------------------
Network display conversion/ | | | | X 4)
treatment | | | |
--------------------------------------------------------------------------------
Message waiting | | | | X 4)
--------------------------------------------------------------------------------
1) HOLD is not a standard supplementary service for Euro-ISDN PRI, nevertheless
some PBXs support call hold and retrieve.
2) HOLD is not defined in Q-Sig but corresponding procedures are available.
3) Call transfer is done via special Q-Sig mechanisms that allow call transfer
for one sub-PBX.
4) Features are not available with Diva Server BRI-2M (rev.1) adapters.
distrib
>
Mandriva
>
2008.1
>
x86_64
>
media
>
contrib-release
>
by-pkgid
>
6b126222df23e08323a5785d17bc56f0
>
files
>
8
