System requirements

The following requirements have to be met for the installation of the Dialogic^® Diva^® System Release software:

• A PC-compatible computer (pentium processor or higher with at least 500 MHz and 128 MB RAM). For Dialogic^® Blue^TM Telephony Boards see notes below. Verify specific requirements for your Dialogic^® Diva^® Media Board at the Dialogic web site www.dialogic.com.
• An installed Linux system
• At least 80 MB of free space on the drive on which your Linux system is installed
• An installed Diva Media Board, Dialogic^® Blue^TM Telephony Board, or valid licenses for the Dialogic^® Diva^® softIP for SIP Software

Notes for Dialogic^® Blue^TM Telephony Boards:

• To operate at least one Dialogic^® Blue^TM OneSpan-24/30-S-LP Telephony Board, you need a 2GHz XEON Core processor. With this processor type you need 24% processor performance using one core of a 2 GHz XEON processor.
• Up to two Dialogic^® Blue^TM Telephony Boards are tested in a system. Since the hardware of the Telephony Boards is a passive design, the features of the boards are executed on the CPU of the PC host. Therefore, the number of supported boards depends on the speed of the host CPU and the performance need of the application.
• If you use a 128ms Echo Canceller, the processor performance consumption increases to approximately 44% using one core of a 2GHz XEON processor.

Dialogic® Diva® Media Boards and Dialogic® Blue(TM) Telephony Boards

This chapter lists the supported boards and switch types and it gives an overview of the Dialogic^® Diva^® softIP for SIP software and its features.

Supported Boards

The Dialogic^® Diva^® System Release Software supports the following and Dialogic^® Diva^® Media Boards and Dialogic^® Blue^TM Telephony Boards

Dialogic Diva Media Boards

A maximum of eight Diva Analog, BRI, 4BRI, PRI, V-2PRI, four Diva V-4PRI, or two Diva V-8PRI Media Boards are supported in one computer. Diva Media Boards with DSPs can also function as resource board for the Diva softIP software. See Using Dialogic® Diva® Media Boards as DSP Resource Board with the Dialogic® Diva® softIP Software for more information. For more information about the Diva softIP software module, see Dialogic® Diva® softIP for SIP Software.

Dialogic^® Diva^® BRI Media Boards

Dialogic^® Diva^® PRI Media Boards

Dialogic^® Diva^® multiport V-PRI Media Boards

Note: "HS" stands for the half size and "FS" for the full size board format.

Dialogic^® Diva^® Analog Media Boards

Dialogic® Diva® softIP for SIP software (virtual media board for IP)

• virtual Diva softIP v2.2 board

Dialogic^® Blue^TM Telephony Boards

The Dialogic^® Diva^® System Release Software supports the following Dialogic^® Blue^TM Telephony Boards (A maximum of two Telephony Boards are supported in one computer. See also System requirements):

• Dialogic^® Blue^TM OneSpan-24/30-S-LP Telephony Board

Note: "S" stands for Software and "LP" stands for "Low Profile" board format.

Dialogic® Diva® softIP for SIP Software

With the licensed-based Dialogic^® Diva^® softIP for SIP software module, the Diva System Release software offers a middleware that enables existing voice Media Board in that it provides functions such as voice and fax transmission, DTMF tones and supplementary services as well as conferencing between ISDN and fax applications to be fully integrated into Voice over IP networks using any standard Ethernet adapter. Technically speaking, the Diva softIP software is comparable to a Diva Media Board in that it provides functions such as voice and fax transmission, DTMF tones and supplementary services as well as conferencing between ISDN and VoIP connections, as shown in the graphic.

If the Diva softIP software and a Diva Media Board are combined in one system, they can concurrently be connected to TDM and IP systems and they can serve as basis for PSTN-IP gateway applications. See also Using Dialogic® Diva® Media Boards as DSP Resource Board with the Dialogic® Diva® softIP Software.

To use the Diva softIP software, you need to purchase the required number of licenses with your Dialogic^® Diva^® Media Board vendor and activate them in the Dialogic^® Diva^® Configuration Manager. See License activation for more information. There are two types of licences: Telephony (for voice applications) and Telephony+Fax (for voice and T.38 fax applications).

Features

General features

• On 64-bit systems up to approximately 480 channels with host-based low bit-rate modems and approximately 600 channels voice (depends purely on the host performance) are supported. Host-based low bit-rate modems licenses are included in regular softIP voice licenses.
• Support for various V.23 modems without the need of purchasing a license when Dialogic^® Diva^® softIP software is used as standalone product:
• Support for the following virtualized environment: VMware^® ESX 3.5
• IP only configuration, software only (Host Media Processing)
• Support for mixed installation, i.e., Dialogic^® Diva^® hardware and Diva softIP software in one PC
• Support for up to 120 channels
• Basic Call origination, termination, and Supplementary Services
• Diva API (SDK) support
• TAPI support
• CAPI 2.0 support
• TTY driver support
• Mapping between phone numbers and SIP URLs
• Licensing per PC fingerprint or USB dongle
• Support for M-Board (The M-Board abstracts the underlying Diva Media Board based channel segmentation into one media board towards the application interfaces (APIs), e.g., from 4 x 30 channels to 1 x 120 channels.)
• Automatic Resource Management using the M-Board
  • Calls that are initiated without the need to allocate hardware DSP resources (e.g., voice) are preferably routed via the Diva softIP software.
  • The call characteristic may change during a call and therefore require a switchover from the Diva softIP board to the Diva Media Board or vice versa. In this case, the M-Board reroutes internally the call using the required resources.
• Internal Service CAPI interface

VoIP/CAPI/Diva API (Diva SDK) support

• Calling Party Number (inbound/outbound calls), including International Numbering Plan according to E.164 mapped to "+"
• Called Party Number (inbound/outbound calls), including International Numbering Plan according to E.164 mapped to "+"
• Redirecting Number, SIP Diversion Header (according draft-levy-sip-diversion-06.txt) mapped to Redirecting Number including International Numbering Plan according to E.164 mapped to "+"
• B-channel protocols, 64 kbps bit-transparent, Transparent, T.30*
• Fax support (T.30)*, MH, MR, MMR, ECM
• DTMF recognition and generation (inband and out of band according to RFC 2833)
• Line Interconnect
• Conferencing using Line Interconnect

  Note: Line Interconnect is not available for the Diva softIP software grouped in an M-Board.

• Call Transfer without consultation call (also known as Blind Transfer, Call Deflection, or Single Step Call Transfer in active state).
• Explicit Call Transfer with consultation call with primary call on hold.

Explicit Call Transfer with consultation call with primary call not on hold.

TAPI support

• Line Interconnect
• Conferencing

VoIP Call Control

• Session Initiation Protocol (SIP) according to RFC 3261
• Further SIP Methods: NOTIFY (RFC 3265), REFER (RFC 3515), SUBSCRIBE (RFC 3265), REGISTER (RFC 3261) with Digest Authentication, OPTIONS (RFC 3261)
• Session Description Protocol (SDP) according to RFC 2327
• SIP side Call Transfer (known as ECT) as transfer target (C-party) and as call initiator (A-party).
• Support of the SIP Register feature including HTTP Digest Authentication. This scheme is using a simple challenge/response mechanism and a shared secret between the two servers.
• SIP Diversion Header (according draft-levy-sip-diversion-06.txt)
• Proxy Authentication 407, Invite Authentication
• Proxy and Registrar address can be configured differently. REGISTER request can be sent to Registrar and INVITE to Proxy.
• SIP Signaling Proxy support if a Registrar is behind a Proxy
• Support of the SIP side Explicit Call Transfer
• Allow to have the port numbers (SIP and Media) configurable (also as a range of port numbers).

For more information about Proxy and Registrar configuration, see the Dialogic^® Diva^® softIP Online Help file.

Fax services

• T.38* for real-time fax over IP
• T.30* Fax Group 3 using T.38, up to 33.6 kbps (SuperG3 Fax).

  Note: The availability of the line speed depends also on the gateway or the remote IP Fax terminal.

• For more information about fax modes, see Using Dialogic® Diva® Media Boards as DSP Resource Board with the Dialogic® Diva® softIP Software
• Fax* compression MH, MR, MMR
• Error Correction Mode (ECM)*

* Based on T.38 without own Soft Fax stack, feature depends on VoIP Gateway/Terminal.

Media Streaming

• PSTN standard codec, G.711, 64 kbps a-law / µ-law
• RTP/G.711 Clear Channel Fax to CAPI/SDK SFF Fax (incl. all existing T.30 and error correction features)

Tone handling

• Inband DTMF generation and detection (clear channel)
• DTMF generation and detection via RTP event (RFC 2833)
• Basic call origination and termination

Supplementary Services support

• Numbering Services (Called Party Number, Calling Party Number, Redirecting Number supporting also International E.164 format)

Call HolCall Hold/Retrieve

• Call Transfer without consultation call, in active call state (also known as Blind Transfer/Call Deflection in active state or Single Step Call Transfer).
• SIP side Call Transfer (known as ECT) as transfer target (C-party) and as call initiator (A-party).
• Conference using Line Interconnect (see VoIP / CAPI 2.0 support above)
• Message Waiting Activation/Deactivation (to activate/deactivate MWI lamps on remote phones, e.g., connected via a gateway or on IP phones)d/Retrieve

Supported VoIP and FoIP software

Dialogic^® Diva^® softIP for SIP software (virtual media board for IP)

• virtual Diva softIP v2.2 board

Using Diva Media Boards as DSP Resource Board with the Diva softIP Software

All Diva Media Boards with DSPs, except Dialogic^® Diva^® PRI/E1/T1-8 PCI Media Boards, can be used as conventional TDM boards and/or as DSP resource board. In the resource board mode, the external interfaces are disabled and the Diva Media Board functions only in combination with the Diva softIP software and thus provides functions to voice, clear channel fax and clear channel modem connections. Clear channel fax can be used by PSTN-IP gateways that do not support T.38 fax so that the fax signal is transmitted in clear channel mode.

If the Diva softIP software is used together with the Diva Media Board as resource board, clear channel fax is used for fax transmission. If the Diva softIP software is used as stand-alone product, T.38 Fax is used.

If Diva Media Boards with DSPs and the Diva softIP software are installed in the same system, calls that are initiated without the need to allocate hardware DSP resources (e.g. voice) are preferably routed via the Diva softIP software. If all available channels of the Diva softIP software are used and no channels of the Diva Media Board are reserved for DSP usage, the remaining DSP-enabled channels of the Diva Media Board are also used for non DSP-related calls.

During a call, the call characteristic may change and may require a switchover from the Diva softIP board to the Diva Media Board or vice versa. In this case, the Combined Board internally reroutes the call using the required resources. To enable the switchover, you need to combine both boards in the Board Configuration page.

How to combine a Diva Media Board and the Diva softIP board

1. In the Board Configuration page, click the Diva Media Board or the line of a Diva Multiport Media Board you want to combine.
2. Next to Interface Mode/Resource Board, select Resourceboard mode and click Save.
3. Once the Diva Media Board is used as DSP Resource Board, the line of the softIP board is no longer shown in the Board Configuration page and an (R) is added to the name of Diva board.
4. To configure the softIP board, click the drop down menu next to the resource board and select softIP Configuration.

   

Supported switch types

Dialogic^® Diva^® Media Boards currently support the following switch types:

Public line ISDN protocols

USA PRI and BRI

• 5ESS Custom (AT&T)
• 5ESS Ni Avaya (Lucent)
• DMS 100 (Nortel)
• EWSD (Siemens)

USA T.1/PRI

• 4ESS
• T.1 RBS

EMEA PRI and BRI

• 1TR6 (legacy Germany and old PBXs)
• ETSI Australia variant (On Ramp ETSI)
• ETSI China variant
• ETSI (Europe, Africa)
• ETSI Hong Kong variant
• ETSI Japan variant
• ETSI New Zealand variant
• ETSI Taiwan variant
• INS-Net 64 / 1500 (Japan)
• VN4 (legacy France, old PBXs)
• VN6 (current France)

R2 CAS (E.1 only)

• Argentina
• Brazil
• China
• India
• Indonesia
• Korea
• Mexico
• Philippines
• Thailand
• Venezuela

Line Side E.1

• Australian P2
• Ericsson
• Melcas
• NEC
• Nortel

PBX protocols

• Generic QSIG T.1 and E.1

  Note: The Generic QSIG switch type can be used for the majority of PBXs

• ETSI

  Note: Many European PBXs use the regular ETSI protocol (PRI and BRI).

Specific major PBX types

• Alcatel 4200
• Alcatel 4400
• Alcatel 4410
• ASCOM Ascotel 2020
• ASCOM Ascotel 2030
• ASCOM Ascotel 2050
• ASCOM Ascotel 2060
• DeTeWe OpenCOM 1000
• Ericsson MD110/BP250
• GPT Realitis iSDX
• Lucent Definity
• Matracom 6500
• Nortel opt11 Rev23
• Nortel Meridian
• Siemens Hicom 150
• Siemens Hicom 300
• Siemens Hipath 3000
• Siemens Hipath 4000
• Tenovis QSig

Carrier Grade

• SS7

POTS

• Worldwide POTS

License activation

After you have installed your Dialogic^® Diva^® product, you might need to generate a license file and activate it in the web interface to unlock the required functionality in the product. To do so, you need the Proof of Purchase Code (PPC) delivered with your product and the Device Unique ID (DUID) of the installed product. See below for more information about the PPC and DUID.

For the Dialogic^® Diva^® System Release LIN software, licenses are available as free 30-day test licenses. For the Dialogic^® Diva^® softIP for SIP software a free test license for two channels (voice and fax) is available on the Dialogic web site www.dialogic.com. If you use the Diva softIP software in a virtualized environment, see also Licensing the Dialogic® Diva® softIP Software in virtualized environments.

Note: You can purchase the license with your Dialogic^® Diva^® Media Board vendor.

You need to generate a license file if you have installed one of the following products and purchased a license for one of the following functionalities:

Device Unique ID (DUID)

The DUID binds the installed Dialogic^® Diva^® product to your PC (PC fingerprint).

To get the DUID:

1. Open the Dialogic^® Diva^® web interface and click License Management.
2. The DUIDs of the installed Diva products are displayed.
3. To use your DUID for generating a license, select it, right-click it, and select Copy.
4. If you need to do web activation using another computer, open an editor, paste the DUID, and save the file.

See To register your PPC and DUID for information about generating a license.

Proof of Purchase Code (PPC)

When you purchase the license, you will receive a PPC either in printed form or via email. By registering this PPC, you represent and warrant that you lawfully purchased the license.

To register your PPC and DUID

1. Open the following web site: www.dialogic.com/activate
2. Enter your PPC and click Check.

   

3. If your PPC is valid, the following web site will open:

   

4. Paste your Device Unique ID (DUID) that you copied from the Diva web interface and enter your email address to which the license file should be sent.
5. Click Activate to generate the license file that will be sent to the email address you have entered.
6. Save the license file and activate it. For more information, see To activate the license.

To activate the license

The date set in the system settings of your computer must be correct. Otherwise, you cannot add your license file.

1. Open the Dialogic^® Diva^® web interface and click License Management on the lower left side of the interface.
2. Go to the product for which you want to activate the license and click Browse next to Upload <product> license file.
3. Go to the directory where you saved the license key file, select it, and click Open.
4. Click Upload to activate the license file.
5. The license file is shown for each product under Installed license files.

Now, the functionality is unlocked for the feature set you acquired with your license.

Licensing the Dialogic® Diva® softIP Software in virtualized environments

In virtualized environments the Diva softIP software license is bound to your system with the PC fingerprint only. The WIBU-Key USB dongle cannot be used for licensing purposes, because an access to the USB is not supported by virtualized environments. The license is bound to several hardware components of the PC, including the MAC address. Each virtual machine (VM) has its own MAC address; therefore, a separate license is required for each active VM with the Diva softIP software installed. Separate licenses are also needed for environments with parallel services, e.g., VM 1 operates a fax server using the Diva softIP software and VM 2 operates an IVR system using the Diva softIP software. Also, since the Diva softIP software license is bound to the hardware components as well, the Diva softIP software license will become invalid if you move the VM to another hardware platform.

You should assign a fixed MAC address to avoid that it changes, e.g., after copying the virturalized environment to a different place, or after restarting or reconfiguring the PC, otherwise the Diva softIP software license will become invalid.

If two VMs are used for failover only and are not active at the same time, the same MAC address may be assigned to both VMs, the active VM and the passive failover VM. In this case, the Diva softIP software license can be installed on both VMs, but you need to make sure that only one of the VMs is active, otherwise it may cause a MAC address conflict and the network communication may be interrupted.

Installation and Configuration

Notes:

• If you upgrade from the Dialogic^® Diva^® System Release software v8.3, the existing configuration cannot be used due to structural changes. A backup of the configuration is stored under divas_cfg.rc.8.3.
• The Dialogic^® Diva^® softIP Software is installed together with the Diva System Release software package.
• The Diva softIP software cannot be used on a Terminal Server.

The following steps provide an overview of the installation and configuration procedure for the Diva System Release software:

1. Install your Dialogic^® Diva^® Media Board and connect it to the network. For further information on the hardware installation, refer to the Dialogic^® Diva^® Media Board Installation Guide that came with your Diva Media Board.
2. Install the Diva System Release software package. For further information, see Software installation.
3. Configure the Diva System Release software using the Config Configuration Wizard located in the /usr/lib/opendiva/divas directory. For further information, see Configuring the Dialogic® Diva® System Release Software.
4. Confirm the operation of your Diva Media Board. For further information, see Testing the Dialogic® Diva® Media Board functionality and connectivity.
5. Configure the Diva System Release software TTY devices. For further information, see Configuring the Dialogic® Diva® TTY ports.

Software installation

The Dialogic^® Diva^® System Release software can be installed on a wide range of Linux distributions.

The software consists of an integrated installer, providing automatic detection of the presence and type of the system package manager:

• On RPM-based systems, the packages are automatically installed using rpm.
• On Debian-based systems, the packages are automatically converted to a .deb-format and installed using dpkg.

To install the software, follow these steps:

1. Ensure that you are logged in as "root" user (or use "su -").
2. Run the following command in a terminal window to start the installation: sh <download path>/Diva4Linux_installer_<nnn>.bin
   • Where <download path> is the path where you stored the downloaded installer package, and <nnn> is the software version and build number.
   • Using the command line switch -t <path>, you can specify the temporary working directory for the installer. The default is /tmp/divas.
3. Follow the instructions on the screen. The installer will search for previous versions of the software and allow uninstallation prior to installing the packaged versions. The configuration files and licenses will be retained.
4. Move into the source directory where the files have been extracted to: cd /usr/lib/opendiva/divas/src
5. Start the build process: ./Build

Files included in the package

The following files are included in the package:

• Device driver for active Dialogic^® Diva^® Media Boards (divas.[k]o, divadidd.[k]o, diva_idi.[k]o)
• CAPI 2.0 interface (divacapi.[k]o, kernelcapi.[k]o, capi.[k]o)
• Dialogic^® Diva^® TTY (COM port) interface (Divatty.[k]o)
• Dialogic^® Diva^® SDK runtime library (libDivas.a, libDivas.so)
• The divactrl utility is used to download the protocol code of active Diva Media Boards, to configure, and to start Diva Media Boards, to read and translate messages from the board's XLOG interface, to create a core dump of the board's memory, to control the board via the management interface and to read and translate messages from the board's MLOG interface (divactrl).
• Protocol code for Dialogic^® Diva^® PRI Media Boards and Dialogic^® Diva^® Multi-PRI Media Boards (*.pm, *.pm2, *.qpm files and *.bin files)
• Protocol code for Dialogic^® Diva^® BRI Media Boards (*.sm, *.sm.4, *.2q0 files, *.bit files and *.bin files)
• Protocol code for Dialogic^® Diva^® 4BRI Media Boards (*.qm?, *.2q? files, *.bit files and *.bin files)
• The tty_test utility allows you to test the TTY interface, to monitor link quality and Dialogic^® Diva^® Media Board 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 you to transfer files, create, remove, or list directories and execute commands on a remote station (acopy2). This utility uses the CAPI 2.0 interface.
• A fax application that allows you to transfer and poll fax documents in text and SFF formats with various transmission speeds and various ECM/compression settings (testfax). This utility uses the CAPI 2.0 interface.
• Dialogic^® Diva^® Configuration Wizard detects the hardware and automatically creates the configuration script (menu driven tools, includes the files Config, Start, Stop, Config.dlg, cfg_util.sh and others). The Diva Configuration Wizard is started by executing the Config shell script.
• Shell script used by RPM to create or delete the symbolic links that enable the Dialogic^® Diva^® System Release software drivers to be started automatically at system startup (cfg_util.sh) and to enable/disable the configuration web server.
• Dummy Dialogic^® Diva^® configuration file. This file is used to generate warnings if the user forgets to configure the Diva System Release software after installation (divas_cfg.rc). This file is overwritten by the Diva Configuration Wizard once the configuration procedure is invoked.
• Shell script to capture information about your system, hardware, or installation if you have problems to install, configure, or start the Diva System Release software (Support). 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 that you do not want to pass on to the Dialogic Customer Support. If you change the script, please send us the modified version together with the report.txt file.
• Trace shell script that can be used to read driver and Diva Media Board traces for debug purposes.
• Shell script stops and unloads Dialogic^® Diva^® drivers (divas_stop.rc).
• xlog that contains divactrl load -ReadXlog $* and can be used to read XLOG traces from the Diva Media Board.
• mlog shell script that contains divactrl mlog $* and can be used to read MLOG traces from the Diva Media Board.
• 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 Diva Media Board.
• divalogd call journal/monitor application. The call journal created by this utility can be used for accounting purposes and for controlling the quality of service (every call record is stored together with information about the connection quality).
• divasnmpx SNMP extension agent providing interface and call statistics. Supports AgentX protocol and trap generation.
• Documentation (*.txt and *.html files) extracted to the /usr/doc/packages directory.

Configuring the Dialogic® Diva® System Release Software

The Config script (located in the /usr/lib/opendiva/divas directory) is a setup wizard that detects the installed Dialogic^® Diva^® Media Boards and additional applications.

The setup wizard generates the divas_cfg.rc file (located in the /usr/lib/eicon/divas directory) that is used to start the Diva Media Boards, interface drivers, and additional software at system startup or to start the components manually. You can use the script /usr/lib/opendiva/divas/Start to load and /usr/lib/opendiva/divas/Stop to unload the software manually.

The setup wizard creates the necessary device nodes in the /dev directory:

• /dev/capi20 is used to access the CAPI 2.0 interface
• /dev/ttyds01 ... /dev/ttyds<n> is used to access the Dialogic^® Diva^® TTY interface, where <n> is the sum of B-channels of the installed Diva Media Boards.

You can either use the Config script or the web-based Dialogic^® Diva^® Configuration Wizard to configure the settings for your Diva Media Boards. The following description of configuration options is based on the web-based Diva Configuration Wizard. It is structured as follows:

• Post installation settings: Steps to be performed immediately after the installation.
• System and Diva Media Board configuration: Configuration of the major parts of the product that depend on the type of your application and the switch type that the Diva board is using. Configuration of application and switch type-dependent parameters that allow you to increase the performance of the system or access switch-specific services. Configuration of number ranges, peers, protocol-specific settings and startup options.
• Control and monitoring: Control Diva Media Board configuration, status and performance data.
• Maintenance: Initiate trace process, create, view, and download trace files.

Post installation settings

The Dialogic^® Diva^® System Release software installs and configures the Dialogic^® Diva^® WEB Configuration Wizard that allows you to access and configure the Diva System Release software via an HTTP browser.

The installation procedure sets up the port 10005 for HTTP access and 10006 for HTTPS access.

If you do not want to use the Dialogic^® Diva^® WEB Configuration Wizard, you can disable it with the command: cd /usr/lib/opendiva/divas && sh cfg_util.sh 4. To re-activate the Diva WEB Configuration Wizard, use the command cd /usr/lib/opendiva/divas && sh cfg_util.sh 5.

To access the Diva WEB Configuration Wizard you need to edit the /usr/lib/opendiva/divas/httpd/login/login file and configure your password.

Note that the "login" file must meet the following requirements, otherwise the password will be ignored:

• The file must be owned by root.
• Permissions must be 600 or 400.
• The password must be located in the first line of the file, contain printable characters only and consist of not less than 7 characters.

System and Dialogic® Diva® Media Board configuration

The system and Diva Media Board configuration is divided in two parts:

• System configuration to configure the type of application, the system startup mode, and global parameters.
• Board configuration to configure parameters of the installed Diva Media Boards in accordance with the information required by the service provider or the PBX to which the Diva Media Board is connected.

System configuration

Online help is available for any system configuration option. To open the online help for a specific parameter, click the parameter and a window with the help text pops up.

1. In the system configuration, select the applications and activate the interfaces that meet your requirements. For example, if you want to set up a fax polling server that is based on the TTY interface, select TTY interface and fax/voice support for TTY.
2. Depending on the selected application scenario, you can set FAX CLASS 2 options like ECM, compression, etc. For further information, see the online help or Intelligent FAX CLASS 2 processing.
3. The system configuration also allows you to specify startup options for your Dialogic^® Diva^® Media Boards. If you plan to clone your system configuration on other computers, disable the verification of the serial numbers. If you want to view debug or trace messages that are issued during the Diva Media Board configuration, enable Debug code for microcode load. For further information on these parameters, see the online help.
4. To write detailed call log records to the /var/log/divalog.../var/log/divalog.N file, activate the call history. The call log records can be used for accounting and for generating different statistics.
5. Specify if the divasnmpx SNMP extension agent should be started during driver load.
6. Specify if the driver load should be forced even if the driver's kernel version does not completely match your Linux kernel version. Note that you cannot force a driver load if your Linux system uses kernel checksums.
7. Specify if the Dialogic^® Diva^® drivers should be loaded automatically on system startup.

At the end of the system configuration, the Dialogic^® Diva^® WEB Configuration Wizard will prompt you to restart the Diva drivers if necessary. To restart the Diva drivers, go to System control, where you can stop and start the drivers.

Note: Some of the changes, for example, Start driver on system boot or Debug mode for microcode load do not affect the state of the currently running drivers and change only the driver behavior at system or Dialogic^® Diva^® Media Board start. The Dialogic^® Diva^® WEB Configuration Wizard ignores changes of these parameters and does not prompt you to restart the Diva Media Board drivers.

Board configuration

Context-specific online help is available for most configuration options. To open the online help for a specific parameter, click the parameter and a window with the help text pops up.

The Board configuration allows you to configure the Dialogic^® Diva^® Media Boards that are installed in your system as required by your service provider or by the PBX to which the Diva Media Boards are connected.

To start the configuration of a Diva Media Board, select its "board" icon in the Diva Media Board list. The basic configuration parameters are displayed.

1. Specify the D-channel protocol (switch type) as provided by your service provider.
2. Specify if you want to operate your board as terminal equipment (TE) or as network termination (NT). Normally, Diva Media Boards are operated as terminal equipment.
3. Specify whether you are using a direct dial in (DDI) interface. A direct dial in interface provides you with an ISDN line with a basic phone number that is able to accept any extension digits and to pass them to the ISDN applications. If you select Yes, also specify the direct dial in number length.

   Note: This option is not available for all D-channel protocols. A better control of incoming called party numbers is available using the Call Routing Configuration.

4. Specify the layer 1 framing type. The National default setting automatically sets the correct layer 1 framing type for the selected switch type. Change this setting only if you are using your Diva Media Board in a non-standard environment.
5. Specify the voice companding type that is used to transmit analog data on your line. The National default setting automatically sets the correct voice coding for the selected switch. You need to change this setting only if the voice coding required by your PBX does not correspond to the coding of the switch.

Depending on the installed board and the selected D-channel protocol, you might need to configure various advanced parameters. To do so, set View extended configuration to Yes and modify the advanced parameters as required. For further information on advanced parameters, see the online help topic of the respective parameter.

When the board configuration is complete, the Dialogic^® Diva^® WEB Configuration Wizard stores the parameters list, generates a startup shell script and tries to update the modified parameters via the management interface. If updating via the management interface is not possible, for example, the board is not running or the configuration parameter is not supported by the management interface, the Diva WEB Configuration Wizard prompts you to restart the board.

To restart the board, you can either:

• select in the Board configuration main page Start hardware from the dropdown menu next to the Diva Media Board, or
• set in System configuration page the option Start driver on system boot to Yes, which allows for starting or restarting the Diva Media Boards at once.

Note: Restarting the Dialogic^® Diva^® Media Board clears the active connections of this board.

Control and Monitoring

If you select the Hardware status/management icon, you will gain access to the:

• current status of the Dialogic^® Diva^® Media Board, which allows you to view hardware-related settings and to control the state of the Diva Media Board.
• Diva board startup log, which allows you to view the board's configuration as seen by the selected Diva Media Board.
• "XLOG" trace snapshot, which allows you to receive a small snapshot of the board traces for the trace ring buffer, located in the Diva Media Board memory.
• Line monitor, which allows you to view the status of active connections on the selected board and to clear these connections, if necessary.
• Management interface browser, which allows you to walk through the board management interface and view or modify management interface variables or execute management interface functions.
• Management interface browser, which allows you to walk through the Dialogic^® Diva^® TTY driver management interface and view or modify management interface variables or execute management interface functions (Port Manager).
• Management interface browser, which allows you to walk through the Dialogic^® Diva^® CAPI driver management interface and view or modify management interface variables or execute management interface functions.
• Report based on the information from the board management interface that provides an overview over the Diva Media Board's link status, link quality and over the call-related statistics.

Maintenance

The Dialogic^® Diva^® WEB Configuration Wizard provides access to the following maintenance functions:

• System environment allows for viewing hardware-related settings of the host system.
• Trace/Debug allows for creating debug and trace files of the Dialogic^® Diva^® Media Board or the system.
• Support/Troubleshooting allows for capturing information required for the support request in case of installation problems.
• System messages allows for viewing the latest system messages (dmesg).
• View trace file allows for decoding, viewing, and filtering debug and trace files.
• View call history allows for viewing the latest call history file.
• View statistics allows for generating and viewing statistics, based on the call history files.

System environment

The system environment browser allows for viewing information about the:

• Kernel version
• CPU(s)
• PCI bus configuration
• I/O memory configuration
• I/O port configuration
• DMA configuration
• Interrupt configuration
• APM configuration
• Loaded modules
• Installed devices
• Memory usage

Trace/Debug

The Dialogic^® Diva^® Trace Wizard allows for selecting various trace profiles and thus enables you to trace everything or to suppress unnecessary information in certain scenarios. Detailed information on the various trace profiles is given in the online help. To display the online help for a profile, click its name.

The Diva Trace Wizard also allows you to set the size of the trace ring buffer - a binary file where the trace information is stored - and to start the trace process in the background.

After the trace process is started, you can leave the Diva Trace Wizard or close your HTML browser without affecting the running trace process.

While the trace process is running (and after the trace process is stopped), you can decode, filter, and view the content of the trace ring buffer file with the trace file browser (View trace file).

To stop a running trace process, enter the Diva Trace Wizard again; the Diva Trace Wizard will remember that the trace process is still running, and stop it. After stopping the trace process, you can download the compressed binary trace file.

Support/Troubleshooting

If you should experience any problems after the installation of the Dialogic^® Diva^® System Release software, for example, no Dialogic^® Diva^® Media Boards can be detected, use the Dialogic^® Diva^® Support Wizard to capture and download in compressed form the information that is required to process your support request. Select one of the following options:

• Capture the necessary information about your system (kernel version, PCI-bus configuration, system configuration files).
• Capture the necessary information about your system (kernel version, PCI-bus configuration, system configuration files) and a binary image of the installed kernel and related modules. With this option, the Dialogic Customer Support can reproduce your environment if this should be necessary to process your support request. Select this option only if requested by the Dialogic Customer Support.

System messages

The system log viewer allows you to view the latest kernel messages. You can use this information to control the load and operation of Dialogic^® Diva^® drivers and to check your system for unexpected errors, driver failures, or exceptions ("Oops").

View trace file

The trace file browser allows for decoding, filtering, and browsing the trace file without downloading this file to your machine and without stopping the trace process.

The trace file viewer displays a list of the Dialogic^® Diva^® debug and trace sources information contained in the trace file and it allows you to select the sources of information that you want to view, decode, and display.

The trace viewer highlights messages in the trace information window by the following colors:

• Yellow - highlights messages related to initial call establishment
• Green - highlights messages related to the call establishment progress and completion
• Red - highlights messages related to the call disconnect procedure

To get detailed decoded information on trace and debug messages, click the "highlighted" links in the trace information window.

View call history

The call history (call journal/log) is stored as a sequence of files named divalog,divalog.1...divalog.N, where N is the integer number in the /var/log directory. The divalog.N file contains the oldest trace information while the divalog file contains the latest (current) information about the call activities.

You can use the call history viewer to decode the divalog file (call time, duration, type, speed) and view this information without downloading the call history file to your local machine.

To download call history files, click Download. You will receive a text file that displays the various components of the call history information separated by commas. The first line of the file contains the description of the components.

View statistics

The Dialogic^® Diva^® Statistics Viewer analyzes the call history files found in the /var/log directory and creates various statistics based on these files. The statistics show the total number of calls related to various periods of time, the ratio of incoming and outgoing calls, the ratio of call types, call duration charts, a peak board load chart, etc.

The statistic information is presented in a graphical format (jpeg) and can be used to analyze the system load and reliability.

If you want to create your own statistics, download the call history files in the call history viewer and apply your own spread-sheet application.

Loading the Dialogic® 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 Dialogic^® Diva^® Media Boards will be started by symbolic links named "S03DIVAS4LINUX" and "S06DIVAS4LINUX_NETWORK". These links are created as part of the installation process and are located in the runlevels 2, 3, and 5 of the following directories (system and version dependent): /etc/rc.d/ directories for Red Hat, in the /sbin/init.d/ or /etc/init.d/ directories for SuSE and in the /etc/rcX.d/ directories for Debian and others.

• If you wish to remove these links, execute: sh /usr/lib/opendiva/divas/cfg_util.sh 2. If you wish to restore these links, execute: sh /usr/lib/opendiva/divas/cfg_util.sh 1.
• If you have changed the configuration or wish to stop or restart the Diva Media Boards without restarting your system, you can use the /usr/lib/opendiva/divas/Stop script to stop the Diva Media Board and unload the Dialogic^® Diva^® drivers.
• You can run the /usr/lib/opendiva/divas/Start script to load the Diva drivers and start the Diva Media Boards.
• If you wish to restart only one specific Diva Media Board, you can do so without unloading the drivers by executing the /usr/lib/opendiva/divas/divas_cfg.rc restart <x> command, where <x> is the logical board number.
• If boards support multiple interfaces (e.g., 4BRI), the board number should be the number of the master board. After the board was stopped, you can load and start it again without affecting other boards.
• If boards support multiple interfaces, the logical boards that belong to the same physical board are affected.
• An updated configuration can be written to the drivers by executing the /usr/lib/opendiva/divas/divas_cfg.rc restart -1 command.

Dialogic® Diva® Media Board information

To interpret the Diva Media Board, driver, and trace data the following information is necessary:

• Physical and logical Dialogic® Diva® Media Board number
• "/proc" file system

Physical and logical Dialogic® Diva® Media Board number

Every Dialogic^® Diva^® Media Board that is installed in the system is a "physical" board. Every physical board contains one or more ISDN or analog interfaces. Each interface is represented in the system by a "logical" board. Example: Three physical Diva Media Boards are installed in the system: a Dialogic^® Diva^® BRI Media Board, a Dialogic^® Diva^® PRI Media Board, and a Dialogic^® Diva^® 4BRI Media Board. The Diva BRI Media Board and the Diva PRI Media Board add one logical board each. The Diva 4BRI Media Boards adds four logical boards to the system. If one physical board contains multiple logical boards, a continuous block of board numbers is allocated to these boards. The first logical Diva Media Board is the "master" board. This board is responsible for the hardware resources of the physical board and for loading, starting, and stopping the logical boards provided by the physical board. In the other aspects (functionality, configuration, selected protocol, debug buffers, and features), the logical boards are independent from the location of their physical boards: on different physical boards or on the same physical board.

"/proc" file system

After being started, the DIDD (divadidd.[k]o) driver creates the directory /proc/net/isdn/eicon for kernel 2.4.x and the directory /proc/net/eicon for kernel 2.5.x and higher in the proc file system. You can read the file divadidd in this directory (for example by executing cat divadidd) to get version information on the DIDD driver.

After being started, the XDI driver (divas.[k]o) creates the file divas in the /proc/net/[isdn/]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 Dialogic^® Diva^® Media Board number) is created in the directory /proc/net/[isdn/]eicon for every logical Diva Media Board present in the system.

Each adapter<no> directory contains the following files:

Global fax configuration options

Global fax configuration options allow for overwriting parameters passed by the fax application to the Dialogic^® Diva^® Media Board and to control parameters running on the Diva Media Board's T.30 protocols. This provides a high level of flexibility, especially if the fax application does not provide the required parameters.

Fax configuration options

Special configuration features

Dialogic^® Diva^® Media Boards provide numerous configuration options part of which are only used in special applications. These configuration options are not covered by the Dialogic^® Diva^® Configuration Wizard.

To get a full list of configuration options, execute /usr/lib/opendiv/divas/divactrl load.

You can apply special configuration options by modifying your Diva Media Board's startup script /usr/lib/opendiva/divas/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 /usr/lib/opendiva/divas/divactrl board load utility.

Special configuration options can be changed during run time without restarting the board via the management interface, for example, with the /usr/lib/opendiva/divas/divactrl mantool management interface access utility.

Testing the Dialogic® Diva® Media Board functionality and connectivity

The following procedures will help you to verify if the Dialogic^® Diva^® Media Board and the service are working properly. After configuring and loading the drivers, it is recommended that you use one or more of the following methods for testing:

• TTY Test
• ACOPY2 file server
• Testfax

TTY Test

This test allows you to test the Dialogic^® Diva^® Media Board and Dialogic^® Diva^® TTY interface functionality and link integrity using various bearer protocols supported by your Diva Media Board.

The /usr/lib/opendiva/divas/tty_test utility is located in the /usr/lib/opendiva/divas directory. On the server side, type: /usr/lib/opendiva/divas/tty_test 1 s auto. On the client side, type: /usr/lib/opendiva/divas/tty_test 2 <ISDNnumber> x75. The transfer rate will appear in real time and be 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 /usr/lib/opendiva/divas/tty_test for a full list or refer to the section tty_test utility in this document.

ACOPY2 file server

This tool allows you to test the Dialogic^® Diva^® Media Board and CAPI 2.0 interface functionality and link integrity using the X.75/T.70NL bearer protocol. The acopy2 utility is located in the /usr/lib/opendiva/divas directory.

Note: Many other options, e.g., packet size, CPN, SubAddress, and commands are available. Type /usr/lib/opendiva/divas/acopy2 for a full list.

On the server side, type: /usr/lib/opendiva/divas/acopy2 -c<X> -serve /p2048, where 2048 is the packet size for beneficial results and <X> is the CAPI board number that will receive the call.

On the client side, type: /usr/lib/opendiva/divas/acopy2 -c<Y> - n<ISDNnumber>:file2 file1 /p2048, where 2048 is the packet size for beneficial results and <Y> is the CAPI board number that will issue the call.

Testfax

This tool allows you to test Dialogic^® Diva^® Media Board and CAPI 2.0 interface functionality and link integrity using the Fax G3 bearer protocol.

The TESTFAX utility is located in the /usr/lib/opendiva/divas directory.

On the server side, type: /usr/lib/opendiva/divas/testfax -serve -c<X>, where <X> is the CAPI board number that will receive the call.

Note: Many other options, e.g., packet size, transmission speed, ECM, SEP/SUB/PWD, compression, fax ID, headline, and commands, are available. Call /usr/lib/opendiva/divas/testfax for a full list.

On the client side, type: /usr/lib/opendiva/divas/testfax file.sff|file.txt <ISDNnumber> -c<Y>, where <Y> is the CAPI board number that will issue the call.

TESTFAX will transmit the file.txt text file or the file.sff SFF file as fax document. The received document will be saved in the rcv.sff file.

Verifying the operating mode of the Dialogic® Blue(TM) Telephony Boards

Dialogic^® Blue^TM Telephony Boards can be started in kernel or user mode. Normally, they are started in kernel mode. If the kernel mode fails, they are started in user mode. There are 3 possibilities to verify the mode of your Telephony Board:

• the web interface,
• the mantool command line utility
• a third party tool

The web interface

To verify in which mode your Telephony Board is running, either:

1. Click System control (driver start/stop) on the left hand side of the web interface.
2. The Last operation log shows you in which mode the driver was started.

or:

1. Click Board monitor on the left hand side of the web interface.
2. Click the management interface icon of the M-Board, to which the Telephony Board belongs.
3. Go to Status\XDI\A1\UserMode.

   A value of 0 indicates that the board is running in kernel mode.

   A value of 1 indicates that it is running in user mode.

The mantool command line utility

When using the mantool, the following message shows you whether the board was loaded in user mode:

--------bol-[Status\XDI\A1\UserMode .....] = TRUE

If the board was loaded in kernel mode, the following message appears:

--------bol-[Status\XDI\A1\UserMode .....] = FALSE

See Management interface access and monitoring utility for more information on the mantool.

A third party tool

You may also check the modus with tools like telnet or putty.

To see whether the board is stared in kernel mode, enter:

# lsmod | grep DivasL

and the following message appears:

DivasL               1973792  0

divadidd               68684  9 divacapi,diva_mtpx,diva_idi,DivasL,divas

To see whether the board is running in user mode enter:

# ps | grep DivasL

and the following message should appear:

root      8962     1  0 09:26 ?        00:00:00 /usr/lib/eicon/divas/DivasL

Configuring the Dialogic® Diva® TTY ports

The /dev/ttydsxx ports must be configured by AT commands (parameters enclosed in square brackets are optional. Variables are enclosed in angle brackets).

AT-command set

The following commands are supported by the Dialogic^® Diva^® System Release software:

• AT commands
• AT\ commands
• AT% commands
• AT# commands
• AT& commands
• AT$ commands
• AT+ commands
• Class Fax1 and class Fax2 AT commands
• AT+FTD. Set current time and date
• AT+FPH. Page header generation

AT commands

AT\ commands

AT% commands

AT# commands

Notes:
[a] CID (Calling Party Number) is indicated as: RING CID: <number>
[b] CID (Calling Party Number) is indicated as: CONNECT ... CID: <number>
[c] Indicated as: RING CID: <number> DAD: <number>
[d] Indicated as: CONNECT ... CID: <number> DAD: <number>
[e] Indicated as: RING;<number>
[f] Indicated as: RING;<number>;<number>

AT& commands

Notes:
[a] No action is taken, the DTR drop is ignored.
[b] If the modem is online, it hangs up and responds with OK.
[c] If the modem is online, it switches to command mode (as if an ESCAPE sequence was detected) and sends OK.
[d] If the modem is online, it hangs up and responds with OK.
[e] If the modem is online, it hangs up and the current profile defaults are restored.

AT$ commands

Notes:
[a] CID (Calling Party Number) is indicated as: RING CID: <number>
[b] CID (Calling Party Number) is indicated as: CONNECT ... CID: <number>
[c] Indicated as: RING CID: <number> DAD: <number>
[d] Indicated as: CONNECT ... CID: <number> DAD: <number>
[e] Indicated as: RING;<number>
[f] Indicated as: RING;<number>;<number>

AT+ commands

Notes:
[a] "AT+" commands are Dialogic^® Diva^®-specific commands which may be used either as part of a normal AT command or as part of a called party number.
[b] 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 ";". For 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
[c] 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).
[d] If supported by used bearer protocol (for example V.110).
[e] Determines if the ASYNC/SYNC conversion module is inserted on top of OSI Layer 3 and which mode this module assumes. See ASYNC/SYNC conversion module for details.
[f] Commonly used values are: 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. See Call parameter (BC/LLC) selection for details.

Fax class 1 and Fax class 2 AT commands

The following list is an excerpt of the complete list.

AT+FTD. Set current time and date

The AT+FTD command is used to set the current date and time. The current time and date should be set before each fax transmit session. The syntax of the command is: AT+FTD=year,month,hour,minute,second,zone,dtsdelta

AT+FPH. Page header generation

The AT+FPH command is used to enable automatic generation of a Fax page header. There are three allowable formats for the syntax of this command:

1. AT+FPH=mode,"left"
2. AT+FPH=mode,"left'middle'right"
3. AT+FPH=mode,"left'right"

AT+FPH command parameters

An escape sequence is a % followed by an optional width, which may include a leading left-justification signifier, and then by the escape character itself. It is of the form %[numbers][-]character. The dash (-) denotes left justification. When the dash is absent, right justification is used. If the width specification starts with a zero and the escape sequence is expanded, the value will be left-padded with zeroes. Otherwise, it will be left-padded with spaces.

Recognized escape sequences

Supported TTY profiles

You can use the AT&F[<profile>] and ATZ[<profile>] commands to select a TTY profile.

Supported TTY profiles

Notes:
[a] By default, this profile does not switch to data mode after the connection was established.
[b] This profile switches to numeric mode (ATV0) and "echo off" (ATE0) by default.
[c] You can use the AT+iE command to activate the CHINA PIAFS protocol extension.

Incoming RAS call type autodetection

For incoming calls, you can use autodetection of the B-channel protocol. The call autodetection procedure detects the call type, uses the right framing and ASYNC/SYNC conversion module if necessary in order to present the data to the RAS PPP application like it comes from an analog modem (ASYNC PPP framing). This allows you to use a standard RAS application that serves the incoming calls on the same port, independent from the call type.

In autodetection mode, the TTY proceeds as follows:

1. It analyzes the BC/LLC if present. If enough information is given in BC/LLC, the appropriate protocol is selected.
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.
3. B-channel data is analyzed and the ASYNC/SYNC PPP conversion module is inserted if necessary.

The following protocols can be autodetected in this way:

1. HDLC/Transparent/Transparent
2. HDLC/X.75/Transparent
3. HDLC/X.75 with V.42bis data compression/Transparent
4. HDLC/V.120/Transparent
5. HDLC/V.120 with V.42bis data compression/Transparent
6. V.110/Transparent/Transparent
7. Analog Modem with full negotiation (up to V.90 central office)/V.42+V.42bis or V.42 or Transparent - buffered mode/Transparent
8. PIAFS/PIAFS/Transparent

If the Dialogic^® Diva^® Media Board is operated on broken ISDN links that provide wrong call-type information over the signaling channel, it might be necessary to force the Dialogic^® Diva^® TTY driver to handle the incoming calls in a specific way independent of the signaled call type. This functionality is provided by the AT+iE command that affects the virtual TTY interfaces exposed by the Diva TTY driver and can be changed only by unloading the driver or issuing another AT+IE command. See AT-command set for more information on the commands.

ASYNC/SYNC conversion module

The ASYNC/SYNC conversion module is inserted on top of OSI layer 3 and is used for automatic framing type detection and conversion. Together with the B-channel autodetection, this module enables automatic discrimination of the incoming call type and thus allows to set up a RAS server that is able to accept digital, analog, wireless, and PIAFS calls on the same number by a standard ASYNC PPP application. See Incoming RAS call type autodetection for more information.

The ASYNC/SYNC conversion module is controlled by the AT+iF and AT+iG commands. If you select modem profile 14 (AT&F14 or ATZ14), correct values will be set for most applications and B-channel protocol detection will be enabled. See AT-command set for more information.

At the beginning, the ASYNC/SYNC conversion module escapes every control character when it explodes a sync frame because this is the initial state for PPP over asyncronous lines (expected by RNA). Thus 0xffffffff is set as the initial receive ACCM. If the peer does not send an ACCM with its configuration request, a null ACCM added to such a request by default, to prevent the overhead of escaping every control character.

The ASYNC/SYNC conversion module assumes that such frames will never contain unescaped control characters for asynchronous RNA frames. Thus, 0x00000000 is set like the initial transmit ACCM. Because some routers (for example Cisco and NetGW) reject an ACCM on synchronous links, the ASYNC/SYNC PPP conversion module removes (but remembers) the ACCM from outgoing configuration requests by default.

Intelligent fax class 2 processing

The fax class 2 AT-command set provides an easy way to access fax-related functionality.

If you use fax class 2 for fax document processing, you need to be aware of the following problems, that might occur:

• It is necessary to maintain a constant data stream between the application and the fax class 2 device. Any interruption in this data stream will affect the quality of the fax document.
• It is necessary to deal with various low-level T.30 protocol settings like scan line time, compression, error correction, etc.
• Not every application or device supports the command-set features provided by fax class 2. This limits the functionality and may require modification of the existing application.
• The usage of fax document compression forces you to deal with compressed data (reception), or to be able to generate compressed data stream on demand, or to provide documents in different compression formats (transmission).
• The "classic" fax class 2 application is unable to deal with transmission speeds higher than 14400 bps. To be able use V.34 fax transmission speeds of up to 33600 bps, the application needs to be modified.

This section explains how the Dialogic^® Diva^® Media Board can overcome these drawbacks and allows you to use the fax class 2 AT-command set to process fax documents with a comparable level of reliability and flexibility as a sophisticated high-level fax API.

Reliable data transfer between application and Dialogic® Diva® Media Board

Dialogic^® Diva^® Media Boards provide a high-performance block-oriented IDI (ISDN Direct Interface) between the board hardware and the host CPU. The data transfer is performed via a BUS master DMA. This enables a reliable data transfer between the host CPU and the Diva Media Board memory that is not affected by the host CPU load. At the same time, using the BUS master DMA reduces the host CPU load.

The Dialogic^® Diva^® TTY interface does not perform data processing. It is only used to forward the data stream between the application and the IDI interface, i.e., the virtual or emulated TTY interface. The entire data processing is performed on the RISC CPU of the Diva Media Board. The reliability of the data stream is ensured by the board hardware through buffering (up to 64 Kbytes for every channel) and block-oriented data transfer (blocks of up to 2 Kbytes) via the BUS master DMA.

Automatic T.30 protocol parameter adjustment

The FAX CLASS 2 application can ignore low-level T.30 protocol settings. The T.30 protocol stack that runs on the RISC CPU of the Dialogic^® Diva^® Media Board is able to perform the required adjustment of transmission parameters to provide reliable and fast document transmission without requiring application intervention.

You can overrule the automatic T.30 protocol parameter adjustment with FAX CLASS 2 commands. If your application does not support the appropriate command set or the required features are not part of the FAX CLASS 2 command set, you can use Global fax configuration options or Global Dialogic® Diva® TTY configuration options to overrule the automatic parameter adjustment.

Support for SEP/SUB/PWD

SEP/SUB/PWD commands are used to address the document recipient and to select or protect the polled document.

The Dialogic^® Diva^® Media Board's support for SEP/SUB/PWD is transparent to the application. The appropriate features can be activated via Global Dialogic® Diva® TTY configuration options without any application intervention. The received SEP/SUB/PWD frames are delivered to the application via "+FSA:", "+FPA:", and "+FPW:" indications.

ECM (Error Correction Mode) support

You can control ECM support via the FAX CLASS 2 AT-command set or via Global Dialogic® Diva® TTY configuration options.

If you use global Diva TTY configuration options to enable ECM support, the Dialogic^® Diva^® Media Board will use ECM mode for document transfer, if supported by the opposite side.

Diva Media Boards use their internal memory to store document data. They retrieve data for ECM re-transmissions from this internal buffer (up to 64 Kbytes for every channel). This reduces the host CPU load and increases the reliability of the fax transmission.

Document compression support

Dialogic^® Diva^® Media Boards use MR, MMR, T.6 fax document compression. In order to reduce transmission time, Diva Media Boards select the best compression algorithm supported by the opposite side. The Diva Media Board's RISC CPU is used to re-compress 1D-coded page data from the application to the format requested by the opposite side (transmission) and to convert received data to 1D-coded page data that is sent to the application (reception).

The re-compression process is handled internally by the board's RISC CPU and happens fully transparent to the application that deals only with 1D (MH) coded data.

You can adjust the compression-related T.30 protocol settings via Global fax configuration options.

V.34 (33600 bps) fax support

The V.34 fax support can be activated via Global Dialogic® Diva® TTY configuration options. If the Dialogic^® Diva^® Media Board is able to establish a connection with a transmission speed higher than 14400 bps (V.34), it handles this transparent to the application. In order to avoid incompatibility with FAX CLASS 2 applications, the Diva Media Board never indicates transmission speeds higher than 14400 bps to the application. This means that transmission speeds higher than 14400 bps are mapped to 14400 bps.

You can use the "divalogd" accounting utility that uses the Diva Media Board Management interface to get information on the real transmission speed and the used compression algorithm.

Global Dialogic® Diva® TTY configuration options

Global Dialogic^® Diva^® TTY configuration options allow you to overwrite the parameters passed by the application and to control parameters running on the Dialogic^® Diva^® Media Board's fax protocols. This provides a high level of flexibility, especially if the application does not provide the required parameters.

TTY configuration options

Call parameter (BC/LLC) selection

Every profile has its own service/additional service indicator that enables the appropriate selection of Bearer Capabilities (BC) and Low-Layer Compatibility elements for the SETUP message. These indicators are used to filter incoming calls and to tell the remote site which kind of connection the user wants to establish for outgoing calls.

To change these default values for outgoing calls, use the AT commands AT+iS (specify service/add service indicator) or AT+iU (specify BC/LLC values). See AT-command set for more information on the AT commands.

TTY "channel pool" mode

By default, the Dialogic^® Diva^® TTY interface operates in "channel pool" mode. It presents the available Dialogic^® Diva^® Media Boards as one board to the user application. This board owns the channels provided by the real Diva Media Boards.

This feature hides the call distribution details from the application and allows creation of servers such as RAS.

You can use the AT+iQ command to control this behavior and to bind specific Diva TTY interfaces to specific Diva Media Boards. See AT-command set for more information.

Note: It is possible to bind specific Dialogic^® Diva^® TTY interfaces to specific Dialogic^® Diva^® Media Boards. But it is not possible to bind specific Diva TTY interfaces to specific B-channel numbers due to the fact that B-channel resources are automatically assigned by the active signaling protocol.

Handling of incoming calls

Incoming calls are handled in the following sequence of operations:

1. The Dialogic^® Diva^® Media Board receives a call.
2. The Diva Media Board uses the active signaling protocol to select the B-channel that will be used for this call.
3. The Diva Media Board delivers the call to the Dialogic^® Diva^® TTY driver.
4. The Diva TTY driver delivers the call to the first application that matches the call type and is ready to receive incoming calls (ATS). See AT-command set for more information on the ATS commands.

Handling of outgoing calls

Outgoing calls are handled in the following sequence of operations:

1. The user application issues a call on an arbitrary Dialogic^® Diva^® TTY interface.
2. The Diva TTY interface transfers the call request to the first Dialogic^® Diva^® Media Board that is able to handle this call type and owns free B-channel resources.
3. The Diva Media Board uses the active signaling protocol to select the B-channel that will be used for this call.

"ESCAPE" sequence (+++)

The ESCAPE sequence enables you to switch from ONLINE mode (data transfer mode) to ESCAPE mode (command mode with the connection established in the background).

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 second.
3. No data is sent to TTY for 2 seconds.
4. TTY switches to ESCAPE mode and sends OK response. The response format depends on the ATV and ATQ commands. See AT-command set for more information on these commands.

To switch from ESCAPE back to ONLINE mode, issue the ATO command. To drop the connection and return to COMMAND mode, 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.

To change the ESCAPE character or to disable or enable the ESCAPE sequence, use the S2 S-register.

AT-command responses

Depending on the response code format that is selected by the ATV command, the result code can be delivered as plain text message (direct form) or as numeric code.

The format of the plain text CONNECT command response can be controlled by the AT\V command.

Command responses

See AT-command set for more information on these commands.

If you select the numeric response format (ATV0), CONNECT will be indicated in numeric form in accordance with the numeric CONNECT responses as described in the table below.

Numeric CONNECT responses

How to set up a dial-in server

This section describes step-by-step how to set up a dial-in server using mgetty and pppd applications.

The dial-in server is built using the mgetty and pppd utilities. mgetty is responsible for TTY interface initialization and call answering. pppd provides a method for transmitting datagrams over point-to-point links and is responsible for link control, authentication, and for network protocol configuration.

The Dialogic^® Diva^® TTY interface is set in auto-detection mode. In this mode, the TTY driver will detect the type of the used protocol and PPP framing and will convert it to ASYNC PPP. This allows the calls to be served by pppd in the same way.

Setting up a "ppp" dial-in server

To set up a dial-in server, proceed as described below:

1. Make sure that the mgetty+sendfax package is installed on your system.
2. Change the context of the /etc/mgetty+sendfax/mgetty.config file as follows:

   # set the global debug level to "4" (default from policy.h) #debug 9 # access the modem(s) with 38400 bps speed 38400 # This is 33600 only #init-chat "" AT&F14;S0=0;E0;\\V1#CID=1;+ms=v34,1 OK init-chat "" AT&F14+IF5+IM4;S0=0;E0;\\V1#CID=1 OK data-only y blocking no toggle-dtr no modem-type data modem-check-time 0 autobauding no answer-chat-timeout 180

3. Change the context of the /etc/mgetty+sendfax/login.config file as follows:

   # Automatic PPP startup on reception of LCP configuration request (AutoPPP). # mgetty has to be compiled with "-DAUTO_PPP" for this to work. /AutoPPP/ - a_ppp /usr/sbin/pppd modem # # Disable login sessions # * - - /bin/false @

4. Add the following lines to the /etc/inittab file, one for every Diva TTY interface that you plan to use for your dial-in server.

   SXX:2345:respawn:/usr/sbin/mgetty ttydsXX

   "XX" is the Dialogic^® Diva^® TTY device number (01, 02, etc.). For example, if one Dialogic^® Diva^® BRI Media Board with 2 channels is installed in the system, you should add two entries:

   S01:2345:respawn:/usr/sbin/mgetty ttyds01 S02:2345:respawn:/usr/sbin/mgetty ttyds02

5. Make sure that the ppp package is installed on your system.
6. Change the context of the /etc/ppp/options file as follows:

   # # Common options for TTY interfaces # lock # # Debug # #debug 9 #kdebug 9 # modem noipx noccp nodeflate nobsdcomp asyncmap 00000000 lcp-echo-interval 10 lcp-echo-failure 5 # # Set the local system name # user roadrunner # # Provide address of your DNS server # ms-dns 192.168.212.130 nodefaultroute proxyarp netmask 255.255.255.255 auth # # Two following lines will disable CHAP and allow PAP # #require-pap #refuse-chap # # The following option disables the identification via "clear text" # user name and password transmission and # enable CHAP and derivates # refuse-pap +chap +chapms +chapms-v2 # # Allows to set idle link timeout # #idle 900

7. In case you plan to use the PAP authentication protocol, create the file /etc/ppp/pap-secrets:

   # Secrets for authentication using PAP # client server secret IP addresses test1 * pwdtest1 * test2 * pwdtest2 *

   In case you plan to use the CHAP authentication protocol, create the file /etc/ppp/chap-secrets:

   # Secrets for authentication using CHAP # client server secret IP addresses test1 * pwdtest1 * test2 * pwdtest2 *

8. Create for every ttydsxx interface that you use for the dial-in server (i.e. where mgetty was started) one /etc/ppp/options.ttydsxx file that contains the IP addresses for local and remote ends of the PPP link. In this example, the configuration file /etc/ppp/options.ttyds01 contains:

   # # Options that differ for every TTY interface (i.e. IP address) # # LOCAL IP:REMOTE_IP 192.168.212.240:192.168.212.241

9. Optionally, you can use dynamic IP address assignment. Please refer to "pppd" documentation for details.
10. If you plan to allow access from the router to your network, it is necessary to allow IP forwarding: echo 1 > /proc/sys/net/ipv4/ip_forward.
11. Execute "kill -HUP 1" to start mgetty processes (this command will inform "init" process about changes in the /etc/inittab file).

Now, the dial-in server is running. You can use name/password pairs "test1/pwdtest1" and "test2/pwdtest2" and CHAP/MS- CHAP protocol to gain access to the system.

How to set up a dial-in callback server

A dial-in callback server allows you to gain access to your system using the callback procedure.

The callback procedure allows you to establish the connection, invoke the authentication procedure and provide phone number where the dial-in server will call you back.

The description for setting up a dial-in callback server is based on How to set up a dial-in server and provides only changes.

General Description

The mgetty utility is responsible for the initialization of the TTY interface and for the answering of the incoming calls. Once the call establishment is complete, mgetty will start the modified pppd utility pppd.callback. The pppd.callback will establish the PPP link, invoke the authentication procedure and obtain callback parameters. Finally, pppd.callback will disconnect the link and execute the user-provided application (script) that will issue the call back.

Setting up a dial-in callback server

1. Set up the dial-in server using How to set up a dial-in server. Finally, follow the described procedure below to configure a dial-in callback server.
2. Install the changed ppp.callback ppp application in the /usr/sbin directory.
3. Change the context of the /etc/mgetty+sendfax/login.config file as follows (it uses now the changed ppp application ppp.callback):

   # Automatic PPP startup on receipt of LCP configure request (AutoPPP). # mgetty has to be compiled with "-DAUTO_PPP" for this to work. /AutoPPP/ - a_ppp /usr/sbin/pppd modem # # Disable login sessions # * - - /bin/false @

4. Change the context of the /etc/ppp/options file as follows:

   # # Common options for TTY interfaces # # # Debug # #debug 9 #kdebug 9 # # # Allow callback operation and set-up callback script # callback 211 callbackscript /etc/ppp/callback.sh modem noipx noccp nodeflate nobsdcomp asyncmap 00000000 lcp-echo-interval 10 lcp-echo-failure 5 # # Set the local system name # user roadrunner # # Provide the address of your DNS server # ms-dns 192.168.212.130 nodefaultroute proxyarp netmask 255.255.255.255 auth # # The two following lines will disable CHAP and allow PAP # #require-pap #refuse-chap # # the following option disables the identification via "clear text" # user name and password transmission and # enable CHAP and derivates # refuse-pap +chap +chapms +chapms-v2 # # Allows to set idle link timeout # #idle 900

   Note: The "lock" option was removed and two new parameters were added: "callback", which activates callback and provides default callback number, and "callbackscript", which provides the name of a callback application.

5. Create a callback script /etc/ppp/callback.sh as follows:

   #! /bin/sh set -e # Parameter 1 - Callback Address # Parameter 2 - TTY device name # Parameter 3 - peer auth name if [ $(($#)) -lt $((3)) ] then logger -i -t callback.sh Parameter missing > /dev/null 2>&1 exit 1 fi mantool="/usr/lib/eicon/divas/divactrl mantool -b -Exclusive -WDog -c 1001" # # Read the callback parameters from the management interface # phone=$1 tty_dev=$2 tty_nr=$2 name=$3 # parameter is passed as "/dev/ttydsXX" tty_nr=$(($(echo ${tty_nr} | sed -e "s/^.*ttyds//" -))) if [ $((tty_nr)) -lt $((1)) ] then logger -i -t callback.sh Invalid tty name $1 > /dev/null 2>&1 exit 1 fi # # Set up the dial script file name # dial=/etc/ppp/diva_dial.$((tty_nr)) tty_nr=$(($tty_nr-1)) dir_start=$(($tty_nr/50)) dir_start=$(($dir_start*50)) dir_start=$(($dir_start)) dir_end=$(($dir_start+50)) offset=$(($tty_nr-$dir_start)) offset=$(($offset+1)) atinit=$(${mantool} -rTTY\\TTY$(($dir_start+1))-$((dir_end))\\T$((offset))\\AtInit | sed -e "/^$/d" - | sed -e "s/^.* = //" -) protocol=$(${mantool} -rTTY\\TTY$(($dir_start+1))-$((dir_end))\\T$((offset))\\ProtocolName | sed -e "/^$/d" - | sed -e "s/^.* = //" -) txspeed=$(${mantool} -rTTY\\TTY$(($dir_start+1))-$((dir_end))\\T$((offset))\\TxSpeed | sed -e "/^$/d" - | sed -e "s/^.* = //" -) if [ -z "$atinit" ] then atinit="AT&F9" fi atinit="${atinit}E1V1" # # Check for V.110 (GSM) callback and set the connection parameters # baud="" if [ "$protocol" = "V.110" ] then if [ $((txspeed)) -eq $((38400)) ] then baud="+ib7+iu=<8890214d00bb>" else # Use 9600Bps as default bit rate baud="+ib5+iu=<8890214800bb>" fi fi if [ ! -z "$baud" ] then atinit="${atinit}${baud}" fi # # Create the dial script now # echo "#! /bin/sh" > ${dial} echo "" >> ${dial} echo "chat -S -V -t 90 ABORT BUSY ABORT NO REPORT CONNECT '' \"${atinit}\" OK ATD${phone} CONNECT " >> ${dial} chmod 700 ${dial} logger -i -t callback.sh "Callback(${phone},${tty_dev},\"${atinit}\"${name})" > /dev/null 2>&1 # # Start PPP # /usr/sbin/pppd.callback ${tty_dev} 115200 connect ${dial} modem user $user nocallback nodetach exit $(($?))

6. Change the permissions of callback.sh file to "executable".
7. The callback script receives the callback number, the Dialogic^® Diva^® TTY device name and the peer name from the command line, i.e., from pppd.callback instance that was responsible for the callback procedure and retrieves the information about used bearer protocol and framing from the management interface of Dialogic^® Diva^® TTY driver. Finally, "callback.sh" uses the available information to construct dial script and to issue the callback.

How to set up a simple fax polling server (mgetty)

The mgetty+sendfax package contains mgetty, a daemon that allows processing of incoming fax polling requests.

To set up a simple fax polling server, proceed as described below:

1. Make sure that the mgetty+sendfax package is installed on your system.
2. Change the context of the /etc/mgetty+sendfax/mgetty.config file as follows:

   # Select your preferred debug level here. # The current global debug level is "4" (default from policy.h). debug 4 # Set any interface. The exact value is not important # because the Dialogic® Diva® TTY interface is virtual. speed 38400 init-chat "" AT?F;S0=0;E0;\\V1#CID=1 OK # # Set your FAX ID in the following line # fax-id 0123456789 blocking no toggle-dtr no modem-check-time 0 answer-chat-timeout 180 fax-only Y modem-type cls2

3. Add the following line to the /etc/inittab file, one for every Dialogic^® Diva^® TTY interface that you plan to use for faxes.

   SXX:235:respawn:/usr/sbin/mgetty -S polling ttydsXX

   "polling" is the name of the fax document to be polled (in G3 format). Optionally, it can be a text file that contains the list of the fax document files (one file name per line). In this case, the files should be in G3 format and will be transmitted as consecutive pages of the same fax document.

   "XX" is the Dialogic^® Diva^® TTY device number (01, 02, etc.). For example, if one Dialogic^® Diva^® BRI Media Board with 2 channels is installed in the system, you should add two entries:

   S01:2345:respawn:/usr/sbin/mgetty -S polling ttyds01 S02:2345:respawn:/usr/sbin/mgetty -S polling ttyds02

4. Issue kill -HUP 1 to start mgetty.

Uninstallation of the Dialogic® Diva® System Release Software

Before you can uninstall the Dialogic^® Diva^® System Release software, you need to unload the Dialogic^® Diva^® driver modules.

Unloading the Dialogic^® Diva^® driver modules:

The Diva driver modules can be unloaded simply by executing: /usr/lib/opendiva/divas/Stop

If you wish to stop and unload the Diva drivers modules manually, proceed as described below:

1. Login as "root" (or use su -).
2. If you have started any tools that access the CAPI or Dialogic^® Diva^® 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.
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 the CAPI drivers.
6. Execute rmmod Divatty to unload the Dialogic^® Diva^® TTY drivers.
7. Execute rmmod diva_idi && rmmod divas && rmmod divadidd to stop and unload the XDI drivers.

Uninstalling the Dialogic^® Diva^® System Release Software

To uninstall the Diva System Release software package, login as "root" (or use su -) and execute:

• For the Debian package: dpkg -r xxx.deb, where xxx is the Debian package name.
• For the RPM package: 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.

Notes:

• The pre-uninstall script contained in the rpm package stops and unloads the drivers by means of /usr/lib/opendiva/divas/divas_stop.rc. It also removes the symbolic links used to start the Dialogic^® 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.
  
• If you do not know which applications or drivers access interfaces of Dialogic^® Diva^® drivers or you cannot stop these applications, proceed as follows:
  
  - Execute sh /usr/lib/opendiva/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.
  
• If you do not know the name of the installed RPM package, execute rpm -q -a | grep divas4linux to get the package name from the database maintained by RPM.

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.

You can manually remove the Diva System Release software 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. To uninstall the Diva System Release package manually, proceed as described below:

1. Login as root (or use su).
2. Change the working directory to /usr/lib/opendiva/divas (cd /usr/lib/opendiva/divas).
3. Execute: sh ./cfg_util.sh 2.
4. Execute: ./divas_stop.rc.
5. Execute rm -rf /usr/lib/eicon/divas.
6. Execute rm -rf /usr/doc/packages/divas4linux*.

Notes:

• The pre-uninstall script contained in the rpm package stops and unloads the drivers by means of /usr/lib/opendiva/divas/divas_stop.rc. It also removes the symbolic links used to start the Dialogic^® 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.
• If you do not know which applications or drivers access interfaces of Dialogic^® Diva^® drivers or you cannot stop these applications, proceed as follows:
  
  - Execute sh /usr/lib/opendiva/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.

Management Interface

The management interface can be used to control the Dialogic^® Diva^® Media Board configuration at run time without reloading or restarting the Diva Media Board. It can also be used as source of information and events for an SNMP interface, call statistics and accounting utilities, or other management applications.

The management interface is located on the Diva Media Board (or in the device driver). 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:

"divalogd" accounting utility

The divalogd accounting utility uses the sources of information contained in the management interface and maintains a detailed call log journal. Based on the information from divalogd, you can provide accounting services and control the quality of the provided services.

divalogd stores the call log to the file /var/log/divalog. On every daemon/system restart, the logfiles are rotated: /var/log/divalog is renamed to /var/log/divalog.1, etc. Up to 10 log files are stored.

"divalogd" parameters

Note: There is a similarly named shellscript divalog, which can be used to retrieve trace information.

Management interface access and monitoring utility

The divactrl package contains the mantool utility that allows you to access (read, write or execute) directories and variables of the management interface. It also allows you to turn on events and receive notifications from these events when the corresponding state of the variable changes.

This utility can be used to capture additional statistics or create ISDN firewall services with its own system of events.

Note: Based on the information from the management interface it is possible to clear calls that meet specific criteria, e.g., calling party number, fax ID, and fax polling address.

To start the mantool utility, type: /usr/lib/opendiva/divas/divactrl mantool -c <x> <parameters>"[<path>]

Where <x> is the logical Dialogic^® Diva^® Media Board number, <parameters> specify the action to be taken, and <path> is the path to the directory or variable in the management interface that you want to access.

Notes:

• The "-w" parameter can only be used with variables that have the "W" attribute.
• 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 mantool from scripts, i.e., not interactively, add the "-b" option to turn the interactive mode off.
  

The following parameters can be used with the mantool utility:

Management interface structure

The management interface is structured like a virtual file space, containing directories with variables. The set of operations that is valid for each variable depends on the variable type and attributes.

Management interface variable types

Management interface variable attributes

Dialogic® Diva® Media Board management interface

The Dialogic® Diva® Media Board management interface is located on the Dialogic^® Diva^® Media Board. 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 "\".

Management interface root directory

Management interface info directory

Management interface statistics\Outgoing calls directory

Management interface statistics\incoming calls directory

Management interface statistics\B/D-Layer1/2 directory

Management interface trace directory

Dialogic® Diva® TTY management interface directory (Port Manager)

The Dialogic® Diva® TTY driver management interface is located in the TTY device driver. 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 "\". TTY driver management interface is accessible via logical Dialogic^® Diva^® Media Board number 1001. The TTY driver provides only one management entity, and cannot be accessed by multiple applications simultaneously. For this reason, the user should perform access in "exclusive" mode (divactrl mantool -Exclusive -c 1001 -r). In exclusive mode, divactrl mantool will use the file lock to synchronize the access to the management interface fully transparent to the caller.

You can use the management interface of the Dialogic^® Diva^® TTY driver to obtain information about the Diva TTY driver, to change the configuration of the TTY driver and to view and to control the state of the Dialogic^® Diva^® TTY interfaces.

Dialogic® Diva® TTY driver configuration directory

The "GlobalOptions" management interface directory allows to change the values of the configuration parameters that affect the TTY interfaces (global configuration parameters). The values of these parameters are passed to the TTY driver module at load time. Using the management interface, allows for changing the values of parameters at run time.

GlobalOptions

TTY Call filter directory

The "CallFilter" management interface directory allows for configuration of the call filters. The call filter allows for processing of the calls with a specific Calling Party Number with a preconfigured protocol, instead of using the protocol auto-detection procedure. This can be necessary for callers with non-standard behavior, that does not allow reliable detection of the bearer protocol.

CallFilter directory

Every call filter consists of two entries: Calling Party Number and protocol to be used. The numbers are compared from behind, i.e., 123 with math 123, 77123, 721999123, ... .

Call Filter entry

TTY Port Manager directory

The "TTY" management interface directory allows you to control the state of the available TTY interfaces (TTY ports). Moreover, it is possible to issue one "DTR drop" to the TTY interface that will clear the connection and re-initialize the selected TTY interface.

Applications can use the context of this directory to retrieve the information about the last processed call (detected protocol, bit rate, calling party number, ...) and use this information for example for call-back.

Port Manager

Port Status

Dialogic® Diva® CAPI management interface directory

The CAPI driver management interface is located in the CAPI device driver. 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 "\". The CAPI driver management interface is accessible via logical board number 1000, i.e., divactrl mantool -Exclusive -c 1000 -r. The CAPI driver provides only one management entity and cannot be accessed by multiple applications simultaneously. For this reason, the user should perform access in "exclusive" mode (divactrl mantool -Exclusive -c 1001 -r). In exclusive mode, the divactrl mantool will use file lock to synchronize the access to the management interface in a fully transparent way to the caller.

You can use the Management interface of the CAPI driver to obtain information about CAPI boards, applications, and PLCIs or to change the configuration of the CAPI driver.

Dialogic® Diva® SNMP Extension Agent

Using the AgentX protocol Diva SNMPX extends an existing snmp master agent to provide runtime data of installed Dialogic^® Diva^® Media Boards. It provides call and line statistics as well as status and errors. Supported OIDs include the MIB-II ifTable (RFC 1213/2233), which is standard in the known SNMP-management applications as well as subsets of DS1-MIB (RFC2495), ISDN-MIB (RFC2127) and DIALCONTROL-MIB (RFC2128) and interface/channel state traps (RFC2233).

Requirements

• Net-SNMP v5.0.6 or higher

SNMP agents are included in most Linux distributions. Most distributors bundle the UCD-SNMP or Net-SNMP packages. The required version is Net-SNMP v5.0.6 or higher. To check your version use the command snmpd -v and upgrade if necessary. It is vital that AgentX is fully supported by this master agent.

To download the newest version of Net-SNMP, browse the Net-SNMP Project Homepage

Configuration of the SNMP master agent

To configure and secure the SNMP master agent correctly, read the corresponding documentation and FAQ. For the impatient, a quickstart is provided here:

Configure the SNMP master agent as follows:

1. The system wide snmpd configuration file can reside in arbitrary locations. Most commonly you can find it in /usr/[local/]share/snmp/snmpd.conf or /etc/snmpd.conf. It can be created and modified by using the command snmpconf -i, which presents a configuration menu for most of the possible options. To get a basically working (and insecure) configuration, you have to configure at least the following items:

   - Access Control: Create a SNMPv1/v2c read-only community, enter a community string, an IP range and a starting OID. For testing purposes, use e.g., "mycomm, (no restriction), (no restriction)".

   - Agent Operating Mode

   - "Should the agent operate as a master agent or not?": Enter "agentx".

   - "IP address and port number": Specify the listening address and port, e.g., localhost:161

2. Start the SNMP master agent (or restart if it is already running).
3. Issue the command snmpwalk -c mycomm localhost interfaces. This will walk the interfaces MIB tree. You should (at least) see data for the loopback- and ethernet interfaces. If you get a timeout, check the above configuration. If you still have no success, delete the configuration file and start from the beginning. Dialogic cannot provide support for this part of the configuration, but there are resources on the internet, such as the Net-SNMP Project Homepage.

Activation of Dialogic® Diva® SNMP support

You can activate Diva SNMP support using the WEB-based System configuration or using the console-based Config application.

You can activate the Diva SNMP extension manually with the following command: /usr/lib/opendiva/divas/divasnmpx. If there is a master SNMP agent running, divasnmpx attaches to its AgentX socket /var/agentx/master. On failure, it retries to open the socket every 10 seconds. This also applies during shutdown/restart of the SNMP master agent: Dialogic^® Diva^® SNMPX automatically reattaches to the master socket as soon as it is available again.

Diva SNMPX automatically detects the start of new Dialogic^® Diva^® Media Boards and the shutdown of existing Diva Media Boards and uses interface state traps to indicate these events to the management application.

Command line options:

Reference: Supported OIDs

This section provides information about supported MIBs, OIDs, and traps by Dialogic^® Diva^® SNMPX and about the relationship between supported OIDs and Dialogic^® Diva^® Media Board management interface variables.

OIDs provided by Diva SNMPX

After installation, the MIB files for the ISDN-, DIAL-CONTROL-, and DS1-MIB can be found in directory /usr/lib/opendiva/divas/mibs. These definitions can be imported in any management application to decode the OIDs reported by divasnmpx. For net-snmp simply copy these files to the standard MIB path (usually /usr/local/share/snmp/mibs) and tell the snmp command line tools to use them by exporting/setting the environment variable "MIBS" with the names of the appropriate MIBs (or simply the keyword ALL). E.g. export MIBS=ALL.

Troubleshooting

The troubleshooting section is divided into two sections. The first section deals with general installation problems that can occur, and outlines the steps to take to report the problems, if they do occur, to the Dialogic Customer Support. The second section deals with test tools that allow you to verify board configuration and to investigate connectivity problems, should they occur.

Support procedure

If you have any problems loading the Dialogic^® Diva^® System Release software 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 computer crashes or freezes after you have loaded the drivers, use the Dialogic^® Diva^® Support Wizard. To start the Diva Support Wizard, execute /usr/lib/opendiva/divas/Support. The Diva Support Wizard allows you to select a problem profile and guides you through the maintenance process.

If you observe a total system failure and the Diva Support Wizard is not able to proceed until the end, then restart the Diva Support Wizard and select problem profile number 5. In this mode, the Diva Support Wizard captures system information that allows the Dialogic Customer Support personnel to replicate your system environment. For this operation, your system should have at least 50 MB of free disk space.

The Diva Support Wizard will create a report file and inform you about the location and the name of the file. Add this file together with a detailed problem description to your support request.

Dialogic® Diva® Trace Wizard

If application problems occur, for example, you cannot connect to a specific number, the application returns an error, the application does not receive notifications of incoming calls, or any other failure at the application layer, Dialogic^® Diva^® Media Board and driver debug traces are required to analyze the problem.

To create the required driver trace files, execute the following command: /usr/lib/opendiva/divas/Trace, select the appropriate trace profile and activate the trace daemon.

To stop the Diva Trace Wizard, execute /usr/lib/opendiva/divas/Trace again and select Stop trace daemon and compress trace file. The Diva Trace Wizard will inform you about the location of the trace file.

You can use /usr/lib/opendiva/divas/divactrl ditrace -i ditrace.bin >tracefile.txt to convert the binary trace file into a text file.

D-channel trace and health monitoring utility

The divactrl package contains a D-channel trace tool that allows you to capture D-channel messages and monitor the layer 1 and layer 2 states of the ISDN interface on the selected Dialogic^® Diva^® Media Board. It operates in two modes: trace mode and monitor mode. In trace mode, the D-channel monitor serves as ISDN diagnostic or trace tool. Its output can be traced for different events allowing you to create your own monitoring tools.

D-channel trace mode

To start the D-channel monitoring tool in trace mode, execute: divactrl dchannel -c <x> [<parameters>], where: <x> is the logical Dialogic^® Diva^® Media Board number to be traced.

Started without optional parameters, the D-channel monitoring tool captures the 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.

The following optional parameters can be used to change the destination type of the output:

Example for a D-channel trace output

D-channel monitor mode

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 if the status changes.

To start the D-channel monitoring tool in monitor mode, execute: divactrl dchannel -c <x> -monitor <y> [<parameters>]

D-channel monitor mandatory parameters

Notes:
[a] The dchannel_monitor shell script is provided as example and can be used to notify the system administrator (root account) about the link state via email.
[b] 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.

D-channel monitor optional parameters

Dialogic® Diva® Media Board health monitoring utility

The Dialogic^® Diva^® Media Board health monitor contained in the divactrl package allows you to control the operating status of the Dialogic^® Diva^® Media Board. This utility uses the Dialogic^® Diva^® XLOG interface to control that the board remains in the operating (active) state.

Note: Whenever Dialogic^® Diva^® Media Board health monitor is running, the XLOG interface is busy and cannot be used by other utilities.

To start the board health monitor, execute: divactrl load -c X -CardMonitor - File Y, where <X> is the Diva Media Board number to be monitored and <Y> is the file provided by the user to be executed in case of board failure.

If the board fails, the Diva Media Board health monitor will write the appropriate information to the system log and exit. Optionally, it can execute a user provided application. The sample shell script card_monitor can be used to notify the system administrator via email.

You can modify card_monitor or create your own script or application that restarts the failed board and the board monitor. You can restart the Diva Media Board fully transparent to applications and without unloading the interface drivers - the active connections will receive a DISCONNECT.

XLOG trace and debug utility

The XLOG trace and debug utility provides access to the Dialogic^® Diva^® Media Board'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.

XLOG trace mode

The following trace 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 using the following commands:

Core dump generation mode

If the Dialogic^® Diva^® Media Board state is changed to trapped and you cannot access the Diva Media Board's debug or trace information via XLOG, i.e., board firmware problem, you can create a core dump of the board memory. This file can be used by the Dialogic Customer Support to extract debug information and analyze the board's state.

Note: To find out the state of a logical board <x>, execute: /usr/lib/opendiva/divas/divactrl load -c <x> -CardState.

To generate a core dump of the Diva Media Board <x> and store it to the file core.bin, execute: /usr/lib/opendiva/divas/divactrl load -c <x> - CoreDump -File core.bin.

Note: Execute this command after the Dialogic^® Diva^® Media Board is in a trapped state.

tty_test utility

The tty_test utility contains a test server, a test client, and a small terminal application. The test client calls the test server. When the connection is established, the client starts to generate test frames and to transmit these frames to the test server. The test server loops the received data back to the transmitter (client). The test client verifies the 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:

Parameters for the tty_test in server mode

tty_test in client mode

The test client can be started with the following commands:

Note: The tty_test updates the log files after 64 KBytes of data have been transferred. Therefore, please be patient if you use, e.g., 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. These commands terminate the tty_test utility.

Parameters for the tty_test in client mode

Example 2. Start tty_test server with protocol auto-detection

To start the test server at TTY number 10 and use protocol auto-detection, execute: tty_test 10 s auto.

Example 3. Start the test server using the V.110 protocol

To start the test server at TTY number 21 using the V.110 protocol with 9600 bps in the background, execute: tty_test 21 sv v110 -l2048 -s5&

Example 4. Start the test client using the X.75 protocol and specify the frame length

To start the test client at TTY 1 using the X.75 protocol, the called party number 800, and a test frame length of 514 bytes, execute: tty_test 1 800 x75 -l514.

Example 5. Start the test client using the V.110 protocol

To start the test client at TTY 1 running in the background using the V.110 protocol, called party number 800, a test frame length of 128 bytes, a rate adaptation speed of 9600 bps, and rate adaptation indication in the , execute: tty_test 1 800 v110 -l128 -s5 -a+iu="<8890214800bb>" -x&

Example 6. Start 30 test server and 30 test client sessions

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.

tty_test in terminal mode

tty_test includes a simple and easy to use terminal mode. To start tty_test in terminal mode, execute: /usr/lib/opendiva/divas/tty_test <tty_nr> t

Parameters for the tty_test in terminal mode

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 Dialogic^® Diva^® TTY interface. It tries to open the /dev/ttyds[01 .... ] device node. With other operating systems, the name of the Diva TTY interface may be different. 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.

Web Interface

You can use the Dialogic^® Diva^® web interface, accessible at port 10005 or 10006, to gain access to the Dialogic^® Diva^® Media Board and system configuration, management interfaces of the Diva Media Boards and drivers, generate statistics and reports, invoke troubleshooting procedures, create/view trace files and view/control the status of the hardware.

To access the Diva web interface you need a web browser with Java Script support. For instance, to access the Diva web interface at local host, type in the address window of you browser: http://127.0.0.1:10005 or https://127.0.0.1:10006.

The Dialogic^® Diva^® HTTP server is designed to run as a daemon in the background. The default port 10005 is used for the HTTP protocol, whereas the default port 10006 is used in conjunction with the HTTPS protocol.

WEB server configuration

The Dialogic^® Diva^® HTTP server (diva_httpd) is started on system boot time and during installation.

The product installation procedure adds the startup script diva_httpd.rc to the system startup scripts. The diva_httpd daemon can also be <started/stopped/status queried> manually by the "diva_httpd.rc start/stop/status" command as usually required by the system startup procedure.

To disable the automatic start of the diva_httpd daemon on system startup and thus, disable the Diva HTTP server, you can execute cd /usr/lib/opendiva/divas && sh ./cfg_util.sh 4.

Before you can access the Diva HTTP server you need to set a password in the /usr/lib/opendiva/divas/httpd/login/login file. The valid password should contain not less than seven characters and being accessible only by "root".

Login procedure

After the first access to the Dialogic^® Diva^® HTTP server, the login page appears:

After a successful login, the Diva HTTP server verifies the "Java Script" functionality. If the WEB browser cannot provide the requested functionality, a WEB page appears informing you about the cause of the failure.

If your browser provides the requested features, the Diva HTTP server forwards you to the Main page.

The server will automatically log you off after 15 minutes of inactivity.

You can log off using the following link:

Context sensitive help

Most configuration parameters and commands, accessible via the Dialogic^® Diva^® WEB server, are exposed as HTML links (HTML links are underlined and the mouse cursor changes its form if you move it over the link). If you click the link, a page appears with help for this parameter. For instance, if you click

the following help window appears:

Dialogic home page

Click the Dialogic symbol to access the Dialogic home page.

Reference Guides

Click Reference Guides in the upper right corner to open the drop-down menu with the list of the available documentation. Click the reference guide you want to consult and it will open in a separate window.

Main page

After the successful Login procedure, the Dialogic^® Diva^® WEB server presents you the main page:

Configuration

Board/softIP configuration

If you click Board configuration on the left side, the following page opens.

This page allows you to:

• create/change the configuration of the Dialogic^® Diva^® Media Boards or the Diva softIP board. To do so, either click the highlighted name of the board or select Configuration or softIP Configuration from the drop down menu next to the board name to open the Board Configuration - Detail page. For more information, see the description below the screen.

  Note: The option softIP Configuration is only available in the drop down menu if the softIP and a Diva Media Board are used in Resource board mode. For more general information, see Using Dialogic® Diva® Media Boards as DSP Resource Board with the Dialogic® Diva® softIP Software. For information about how to combine both boards see further below.
  To open the softIP configuration when used as standalone product, you need to click the highlighted name of the softIP line to configure.

• identify a Diva Media Board. To do so, select Identify on from drop down menu next to the board name. With this option activated, the LEDs of the Diva Media Board are set to blink so that you can simply identify the board for connecting it to the correct cable.
• restart the selected Diva Media Board if necessary, e.g., after the configuration of certain parameters. To do so, select Restart hardware or Restart softIP stack from the drop down menu next to the board name.
• disable the selected Diva Media Board if necessary. To do so, select Disable hardware and the Diva Media Board is unloaded from the system and layer 1 gets disconnected.
• add a Diva Media Board to an M-Board. The benefits of the M-Board are described in the General features section. To so so, select Add to M-Board <x>, where <x> stands for the M-Board Number to which you want to add the board.

  Note: If you join a softIP board and a Diva Media Board to an M-Board, the Diva Media Board is not used as DSP Resource Board but keeps functioning as conventional TDM board.

• remove a Diva Media Board from the M-Board. To do so, select Remove from M-Board.

When you select Configuration or click the name of the Diva Media Board, the Board Configuration - Detail page opens and you may configure the basic and extend parameters of the Diva board. To see the extended parameters, select Yes next to View Extended Configuration.

Among others, the Board Configuration - Detail allows you to combine a Diva Media Board and a Diva softIP board to use the Diva Media Board as DSP resource board. To do so, select Resourceboard mode next to Interface Mode/Resource Board and click Save.

Note: Once the line of the Diva softIP board is combined with the Diva Media Board, the softIP board is no longer shown in the Board Configuration page and an (R) is added at the end of the name of Diva board. To configure the softIP board, click the drop down menu next to the resource board and select softIP Configuration.

As soon as the configuration process is complete, click Save to update the Diva Media Board configuration. The Diva Media Board configuration utility tries to update the changed configuration parameters on demand, i.e., without a board restart. If the changed parameters cannot be updated in this way, the Dialogic^® Diva^® WEB server will ask you to restart the Diva Media Board.

Clock configuration

This feature is only available on specific Dialogic^® Diva^® xBRI and V-xPRI Media Boards. Clock synchronization may be necessary, if one port of the Diva multiport Media Board is connected directly to the ISDN line and the other ports are connected to the PBX, so that the clocks of the ports may drift. With the clock synchronization, the ports configured as NT are synchronized with the TE ports on the same Diva Media Board.

To synchronize the ports, you have two options:

• You can synchronize the configured NT ports to one selected TE port. If you use this mode, either port 1 or 3 needs to be configured as TE. Select one of the TE ports under NT-ClockSync.
• In a specific monitoring configuration, NT port 2 is synchronized with TE port 1 and NT port 4 is synchronized with TE port 3. In this configuration, port 2 and 4 must be NT and port 1 and 3 must be TE. If you use such a configuration, select Monitor Mode under NT-ClockSync.

System configuration

If you click System configuration on the left hand side, a page opens that allows you to configure global system parameters that affect the installed boards and device drivers, to optimize the configuration of your system, such as Fax-, RAS-, or Voice server, to select the applications and interface drivers to be loaded (CAPI, TTY), and to control misc. system services (accounting, etc.).

Note: The activation of the SIP-PSTN gateway (Dialogic^® Diva^® SIPcontrol^TM software), the SIP enabled CAPI (Dialogic^® Diva^® softIP software), the DSI SS7 for Diva support (Dialogic^® DSI SS7 for Diva^® Media Boards), or specific features on the Dialogic^® Diva^® Media Boards require a valid license. See License activation for more information.

Call Routing configuration

This page allows you to configure number ranges, different targets (CAPI/DSAPI vs. TTY), and different kinds of call distributions. You may configure the call routing for each controller. Note that if the first rule for a called party number matches, the remaining rules for the same number are ignored.

Note: If you select to configure the call routing, the parameter Direct Dial In (NT2) is automatically set to Yes.

To configure the call routing options:

1. Select Advanced from the dropdown menu and click Save. A page appears confirming that the selection was saved.
2. Click Call Routing configuration again and the Advanced configuration menu appears.

   

3. Click Edit to configure the necessary settings.

   

4. Use the wildcard character "*" if any Called Party Number should be matched. You can also enter a single number or a range of numbers.
5. Select the controller to be used for the call routing. If you select Any and you may create a common call routing for all installed controllers.
6. Under Call Distribution, select how the call should be handled. If you select Broadcast, the call is routed to the running applications on all interfaces. If you select Forward to, you need to enter the number to which the call should be routed and you need to select an interface.
7. For more information, see the online help for each parameter.

CHAN_CAPI configuration

The Dialogic^® Diva^® System Release is compatible with the CHAN_CAPI Asterisk interfaces. The CHAN_CAPI is a specific use case to provide CAPI-based ISDN hardware support. It establishes the connection between the PBX software and ISDN hardware, which provides a CAPI 2.0 compatible interface.

During the installation of the Diva System Release LIN software, the installation process detects automatically if Asterisk is installed and if the header files to build the CHAL_CAPI driver are available.  

If Asterisk is installed, the user will be asked if the CHAN_CAPI driver should be build. After confirmation, the build process automatically detects the installed Asterisk version and creates and installs the required CHAN_CAPI driver. 

If Asterisk is not installed, the documentation for using Asterisk with Diva is available in the web configuration. Asterisk may be installed or updated after the Diva System Release is installed. In this case, the build process for the Diva System Release can be started again and will create and install the CHAN_CAPI driver.

The CHAN_CAPI configuration generates a capi.conf Asterisk configuration file and modifies the modules.conf and makes the available options visible. You need to write your own extension.conf. Consult the examples in the internet for reference. For Diva-specific commands, see the README, README.media, README.Diva.fax, and README.Diva.qsig files.

Notes:

• If a new capi.conf is generated, the old version is saved as capi.conf.saved_by_diva.
• The DTMF parameters are set to 80ms Tone/Gap Duration and are detected by the DSP if the capi.conf is configured via the WEB configuration interface.
• MF and other tones can be detected. See the readme.media file for more information.
• If you use Asterisk 1.6, do not activate RTP support.

To open the online help for a specific parameter, click the parameter and a window with the help text will pop up.

System

System control (driver start/stop)

If you click System control (driver start/stop) the following page opens, where you can start and stop Dialogic^® Diva^® drivers. The Dialogic^® Diva^® WEB server will detect the current state of the drivers and will open the appropriate page. Moreover, this page allows you to view the log file of the last driver start/stop configuration procedure.

Note for Dialogic^® Blue^TM Telephony Boards:

Dialogic^® Blue^TM Telephony Boards can be started in kernel mode or user mode. Normally, they are started in kernel mode. If the kernel mode fails, they are started in user mode. The Last operation log in the web interface will show you in which mode the driver was started. For more information see also, Verifying the operating mode of the Dialogic® Blue(TM) Telephony Boards.

You can also verify the modus under Board monitor of the web interface. To do so:

1. Click Board monitor on the left hand side of the web interface.
2. Click the management interface icon of the M-Board, the Telephony Board belongs to.
3. Go to Status\XDI\A1\UserMode. A value of 0 indicates that the board is running in kernel mode. A value of 1 indicates that it is running in user mode.

System environment

This page allows you to get important information about your system (kernel version, PCI hardware configuration, system resources, etc.). Most of the information is retrieved from the /proc file system.

System messages

This page allows you to view the last 200 messages from the kernel ring buffer. This is equivalent to the command dmesg > msg.txt && tail -n 200 msg.txt.

Backup and restore

If you need to create a backup of your configuration, you can do so with the backup and restore functionality.

To create the backup file:

1. Click Create backup file.
2. After the backup file is created, you have the option to save the file.

   If you click Download backup file button, a window opens giving you the options to either open the file or to save the file. Choose one option and click OK.

   

To restore the backup file:

1. Next to Upload backup file, click Browse.
2. Go to the directory where you stored the file and click Open.
3. Click Upload.
4. After the upload has finished successfully, restart the drivers as described in System control (driver start/stop).

   

Status

Board monitor

If you click Board monitor on the left hand side, the following page opens, which allows you to check the current status and the configuration of the installed Dialogic^® Diva^® Media Boards, to read internal board trace buffers (XLOG) and to gain access to the Management interface of Diva Media Boards and drivers:

Management interface browser

You can navigate through the Management interface of the selected Dialogic^® Diva^® Media Board or driver using the management interface browser:

The management interface is available for:

• Dialogic® Diva® Media Boards
• the Dialogic® Diva® TTY driver
• the CAPI driver

Dialogic® Diva® Media Board management interface

If you click the icon below Mgnt in the Available Diva Board section, the management interface browser opens. The management interface browser allows you to navigate through the management interface directories, read, write, and execute management interface variables using the buttons under Operation.

CAPI driver management interface

If you click the icon below Mgnt for the CAPI driver in the Available System Release driver section, the management interface browser opens. The management interface browser allows you to navigate through the management interface directories, read, write, and execute management interface variables using the buttons under Operation.

Dialogic® Diva® TTY driver management interface

If you click the icon below Mgnt for the TTY driver in the Available System Release driver section, the management interface browser opens. The management interface browser allows you to navigate through the management interface directories, read, write, and execute management interface variables using the buttons under Operation.

View call history

This page allows you to view the last segment (up to 10000 calls) of the call record that is stored in the /var/log/divalog file. This file contains the information about call time, duration, call parameters, e.g., calling/called party numbers, used protocol, transmission speed, remote fax station id, or fax features.

The record file of the call is stored in ASCII format and can be downloaded to a local machine. To receive more details on the format of the call record file, read about the"divalogd" accounting utility.

View statistics

This page allows you to perform statistical analysis of the call record (call journal) files. The result of the analysis is presented as sequence of pie- and chart- diagrams (stored as JPEG files).

View report

This page allows you to view the state and the cumulative statistics for the active Dialogic^® Diva^® Media Boards. If you click the board icon below Details, the information listed here is displayed. The information contained in the report originates from the management interface of the Diva Media Boards.

• Link status (Layer 1 state, Layer 1 alarms, Layer 2 state).
• Total amount of Layer1/Layer2 frames/bytes transferred over the D-channel.
• Total amount of Layer1/Layer2 errors detected in the D-channel frames.
• Total amount of Layer1/Layer2 frames/bytes transferred over the B-channels.
• Total amount of Layer1/Layer2 errors detected in the B-channel frames.
• Total amount of calls.
• Total amount of successful calls.
• Total amount of failed calls, sorted by cause (User Busy, Incompatible destination, etc.).
• Total amount of successful modem calls.
• Total amount of failed modem calls, sorted by cause (Not a modem device, etc.).
• Total amount of successful fax calls.
• Total amount of failed fax calls, sorted by cause (Not a fax device, Forced by application, etc.).

Debugging

Support/Troubleshooting

In case of a problem, you can use this page to capture relevant information for your support request:

You can invoke the support procedure in two modes: The first mode captures the most important information about your system in one text file, whereas the second mode captures system environment information (kernel image, modules, configuration files) that allows the Dialogic Customer Support personnel to reproduce your environment locally. Finally, you can download the report file as compressed archive.

Trace/Debug

This page allows you to select the trace profile and level, to set trace ring buffer size and to activate the background trace process:

Once the trace process (ditrace) is running, you can issue one test call or stop the trace process and retrieve compressed trace file.

At any time, you can view the context of the trace ring buffer file (even if the trace process is still running) using the trace file viewer. See View trace file for more information.

View trace file

This page allows you to decode and to view a trace file. You can filter the trace file to view only specific sources of information:

Finally, you can view or download the decoded trace file:

Orange and green trace messages deal with the call establishment.

Red trace messages deal with the call release.

D-channel analyzer

Some of the messages are displayed as HTML links (underlined). You can receive more information about messages if you activate the link:

AudioTap analyzer

The blue trace messages (and HTML links) deal with AudioTap data. Audio taps are the audio data samples on the input (output) of the analog modem and fax DSP code combined with control information from the DSP code (events, EYE patterns). You can click the silver HTML link to start the Audio Tap Analyser that includes numerous tools.

Control panel

Digital oscilloscope (view timing diagram)

Digital spectral analyzer

EYE pattern diagram

WAV file download

Moreover, it is possible to download an Audio Tap file in "WAV" file format.

View recovered debug/trace buffer

This page allows you to view or download the decoded trace file.

The internal debug/trace buffer of Dialogic^® Diva^® MAINT driver is saved to /var/log/maint.bin file every time system was rebooted or received kernel panic at time Diva MAINT driver (diva_mnt) was loaded and at least one Dialogic^® Diva^® PRI Media Board was present in the system and was in the active state.

View board recovered trace buffer

Product Features

Each Dialogic^® Diva^® Media Board provides different features and capabilities with the Dialogic^® Diva^® System Release software. The table below outlines the feature set of the Diva Media Boards.

Supported interfaces

The services provided by the Dialogic^® Diva^® Media Boards are accessible via system interfaces. The features may not be available on every supported interface. The interfaces supported by Diva Media Boards are as follows:

Supported interfaces

The features list of Dialogic^® Diva^® BRI and PRI Media Boards is divided in:

• Features of Dialogic® Diva® BRI and PRI Media Boards via interface
• Supplementary services of Dialogic® Diva® BRI and PRI Media Boards via interface
• Supplementary services of Dialogic® Diva® BRI and PRI Media Boards per switch

To view the Features of Dialogic® Diva® Analog Media Boards click this link.

Features of Dialogic® Diva® BRI and PRI Media Boards via interface

The following features are available with the Diva ISDN Media Boards: