Dialogic® Diva® System Release 9.0LIN Service Update 1 Reference Guide May 2009 206-324-10 www.dialogic.
Contents Dialogic® Diva® System Release 9.0LIN SU 1 Reference Guide 4 Syntax used throughout the guide ................................................................... 4 Copyright and Legal Notice 5 Software License Agreement 7 About the Dialogic® Diva® System Release Software 11 Features .................................................................................................... General features .........................................................................................
Call parameter (BC/LLC) selection ................................................................. TTY "channel pool" mode ............................................................................. "ESCAPE" sequence (+++) ........................................................................... AT-command responses ............................................................................... How to set up a dial-in server .......................................................................
Use of the Dialogic® Diva® System Release Software in a Customized Environment 168 Base drivers .............................................................................................. 168 Dialogic® Diva® TTY driver .........................................................................
Dialogic® Diva® System Release 9.0LIN SU 1 Reference Guide This guide provides a detailed description of how to install and configure the Dialogic® Diva® System Release software, and how to troubleshoot your ISDN connection, if necessary. This guide covers the following subject matter: • The Diva System Release software features, supported hardware, and system requirements. • Installation and configuration of the Diva System Release software with Dialogic® Diva® PRI, BRI, and Analog Media Boards.
Copyright and Legal Notice Copyright © 1993 - 2009 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation at the address provided below. All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Corporation or its subsidiaries ("Dialogic").
This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present or future effects such usage might have, including without limitation effects on your products, your business, or your intellectual property rights.
Software License Agreement This is an Agreement between you, the Company, and your Affiliates (referred to in some instances as "You" and in other instances as "Company") and all Your Authorized Users and Dialogic Corporation ("Dialogic"). YOU SHOULD CAREFULLY READ THE SOFTWARE LICENSE AGREEMENT ("AGREEMENT") ON THIS SEALED PACKAGE BEFORE OPENING THE PACKAGE. BY OPENING THE PACKAGE, YOU ACCEPT THE TERMS AND CONDITIONS OF THIS AGREEMENT.
• You may distribute the Program in object code only and only as part of, or integrated by You into, a computer system that (i) contains a Dialogic hardware product, (ii) includes a substantial amount of other software and/or hardware manufactured or marketed by You and (iii) is marketed and sublicensed to an end user for the end user's own internal use in the regular course of business (a "Licensed System"); • Each end user to whom a Licensed System is distributed must agree to license terms with respec
Limited Warranty Dialogic solely warrants the media on which the Program is furnished to You to be free from defects in materials and workmanship under normal use for a period of ninety (90) days from the date of purchase by You as evidenced by a copy of Your receipt. If such a defect appears within the warranty period, You may return the defective media to Dialogic for replacement without charge provided Dialogic, in good faith, determines that it was defective in materials or workmanship.
Miscellaneous You acknowledge that You have read this Agreement, that You understand it, and that You agree to be bound by its terms and conditions, and You further agree that this is the complete and exclusive statement of the Agreement between the Dialogic and You ("the Parties"), which supersedes and merges all prior proposals, understandings and all other agreements, oral and written, between the Parties relating to the Program.
About the Dialogic® Diva® System Release Software The Dialogic® Diva® System Release software enables you to use your Dialogic® Diva® Media Board and the Dialogic® Diva® softIP for SIP Software module with Linux, such as to provide analog, digital, and fax modem emulation over TTY, a CAPI 2.0 interface for ISDN-based applications, an ISDN Direct Interface (IDI) for access to the management interface, and B- and D-channel tracing utilities.
• Use any available channel command • Conferencing • Q.SIG • README.media and README.Diva.
• RAS connection to a Linux-based RAS server from digital, analog, and mobile networks with only one telephone number • LAN-to-LAN connection with a transfer rate of 64/56 kbps or 128/112 kbps for Dialogic® Diva® BRI Media Boards, 2 (E1) or 1.5 (T1) Mbps for Dialogic® Diva® PRI Media Boards, and 56 kbps for Dialogic® Diva® Analog Media Boards • Fax, voice, or unified messaging server • Support for B-channel protocols: HDLC, X.75, X.75 with V.42bis, V.120, V.120 with V.42bis, ISO8208, T.70/T.
The Combined Board is named M-Board in the web interface. • With the Internal Call Transfer, an application can forward a call to another application. It is possible for application manufacturers and developers to detect the characteristic of a call (Fax, Voice, Modem, etc) and forward the call to another, compatible application. This is required if a solution is splitted into multiple single applications. This feature is especially relevant for application developers.
Fax and voice features • Fax Class 1 and 2 • Fax and voice support via CAPI • Fax sub-addressing (SUB), polled document selection (SEL), password (PWD), non-standard facility frames (NSF) • Fax compression (MH, MR 2D coding, MMR T.6 coding) and error-correction mode (ECM) • SFF and plain text (ASCII) support • Fax connections up to 33.6 kbps (V.
• Transcoding • MCU functionality (conference, mixer, interconnection) • Real time protocol (RTP) processing on the Dialogic® Diva® Media Board's RISC CPU • Dynamic anti-jitter buffer processing on the Diva Media Board's RISC CPU • Comfort noise generation (CNG) • Voice activity detection (VAD) • DTMF/MF tone processing (in band, out of band) • Enhanced tone processing (e.g., 390 Hz for VoIP answering machine, country-specific tones) Q.SIG features • Basic call (64 kbps unrestricted, 3.
Dialogic® Diva® TTY driver The Dialogic® Diva® ISDN serial driver provides access to analog, digital, fax (FAX CLASS 1 and FAX CLASS 2 with ECM, compression, and polling support), V.110, B-channel protocol detection, caller ID, and voice capabilities of the Dialogic® Diva® Media Boards by providing a standard serial driver interface.
License-based features For the following features you need to purchase a license: License-based features for Dialogic® Diva® Media Boards, except the Dialogic® Diva® 2FX, PRI/E1/T1CTI, and PRI/E1/T1-8 Media Board Support for G.729 incl. Annex A and Annex B voice codec License-based features for Dialogic® Diva® V-2PRI and V-4PRI Media Boards • Support for RTAudio voice codec with default bit rates: 24 kbps for 16 kHz and 8.
3. Data modem support, up to V.90 • Modem modulations POS up to V.90 (Client and Server side) • V.21, V.23, V.22, V.22bis, Bell 103, Bell 212A, V.32, V.32bis, V.34, V.90, including error correction MNP, V.42, SDLC and compressions V.42bis, MNP 5 • POS modulations V.22 FC, V.22bis FC, V.29 FC • Text telephone modem: V.18, V.21, Bell 103, V.23, EDT, Baudot 45, Baudot 47, Baudot 50, DTMF • Extended modulations V.23 half duplex, V.23 on hook (SMSC mode), V.
• • 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 Dialogic® Diva® API (Diva SDK) support • IP only configuration, Host-Media Processing, software only • TDM/IP hybrid configuration, mixed with Diva Media Boards VoIP / CAPI 2.
• 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.
• For more information about fax modes, see Using Dialogic® Diva® Media Boards as DSP Resource Board with the Dialogic® Diva® softIP Software on page 22 • 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.
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). Verify specific requirements for your Dialogic® Diva® Media Board at the Dialogic web site www.dialogic.com http://www.dialogic.com.
Supported Dialogic® Diva® Media Boards The Dialogic® Diva® System Release Software supports the following Dialogic® Diva® Media Boards (maximum of eight Diva Analog, BRI, 4BRI, PRI, V-2PRI or four Diva V-4PRI Media Boards in one computer): Dialogic® Diva® BRI Media Boards • Diva BRI-CTI PCI v2 • Diva UM-BRI-2 PCI v2 • Diva BRI-2FX PCI v2 • Diva UM-BRI-2 PCIe v2 • Diva BRI-2M PCI v2 • Diva UM-4BRI-8 PCI v2 • Diva BRI-2M PCIe v2 • Diva UM-4BRI-8 PCIe v2 • Diva 4BRI-8M PCI v2 • Diva 4BRI-8M
• Diva V-4PRI/T1-96 PCIe HS v1 • Diva V-4PRI/E1-120 PCIe HS v1 Note: "HS" stands for half size. Dialogic® Diva® Analog Media Boards • Diva Analog-2 PCI v1 • Diva UM-Analog-4 PCI v1 • Diva Analog-2 PCIe v1 • Diva UM-Analog-4 PCIe v1 • Diva Analog-4 PCI v1 • Diva UM-Analog-8 PCI v1 • Diva Analog-4 PCIe v1 • Diva UM-Analog-8 PCIe v1 • Diva Analog-8 PCI v1 • Diva Analog-8 PCIe v1 Dialogic® Diva® softIP for SIP software (virtual media board for IP) • virtual Diva softIP v2.
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.
• Melcas • NEC • Nortel PBX protocols • Generic Q.SIG T.1 and E.1 Note: The Generic Q.SIG switch type can be used for the majority of PBXs • ETSI Note: Many European PBXs use the regular ETSI protocol (PRI and BRI).
Installation and Configuration Notes: • If you want to install the Dialogic Host Media Processing software on top of the Diva System Release software, go to Dialogic® HMP Software and Dialogic® Diva® System Release LIN Software. • 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.
• Where is the path where you stored the downloaded installer package, and is the software version and build number. • Using the command line switch -t , 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.
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.
• Documentation (*.txt and *.html files) extracted to the /usr/doc/packages directory.
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.
and bound the licenses to the Diva Media Board. • With the Diva V-4PRI PCIe HS Media Board, data modem support and fax support are available via licenses but not on all channels. 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.
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 on page 36.
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 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.
Post installation settings The Dialogic® Diva® System Release software installs and configures the Dialogic® Diva® WEB Configuration Wizard (lightweight HTTP server, started via xinetd) that allows you to access and configure the Diva System Release software via an HTTP browser. The installation procedure selects a free TCP port number between 10005 ... 10050, modifies your /etc/services and xinetd configuration files, and restarts the currently active xinetd application.
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...
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.
Maintenance The Dialogic® Diva® WEB Configuration Wizard provides access to the following maintenance functions: • System environment on page 40 allows for viewing hardware-related settings of the host system. • Trace/Debug on page 41 allows for creating debug and trace files of the Dialogic® Diva® Media Board or the system. • Support/Troubleshooting on page 41 allows for capturing information required for the support request in case of installation problems.
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.
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.
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.
"/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.
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 Option Description Fax speed limit Allows to limit the transmission speed.
a lower transfer speed. This setting allows for disabling fallback. 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.
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.
On the client side, type: /usr/lib/opendiva/divas/testfax file.sff|file.txt -c, where 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. 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 command Description AT A ANSWER. Accepts an incoming call that has been indicated by a "RING".
AT V[] Modem response (result code) format 0 Numeric result codes. 1 Plain text result codes (verbal mode, default). AT L Command accepted for compatibility reasons. AT N Command accepted for compatibility reasons. AT M Command accepted for compatibility reasons. AT Y Command accepted for compatibility reasons.
ATS7= Default value is set to zero (e.g., modem will use protocol-specific default value). Modem mode: time to wait for carrier. Sets the time in seconds that the modem will wait for a carrier before hanging up. is a range from 0 to 255 seconds. Fax mode: time to wait for connect. Sets the time in seconds that fax will wait for connection before hanging up. Suggested value is 200 seconds. Values less than 10 seconds are ignored.
7 128 Reserved Bit Value Result 0 1 Use reverse SDLC establishment (SNRM sent by answerer and not by caller). Mandatory for POS. 1 2 Poll on each SDLC frame. Required by some POS terminals. ATS91= ATS92= SDLC Address A (default 0x30) ATS128 S-register 128 is a read-only register. Reading this register allows to retrieve information on the current (last) incoming call. It returns a message in the following format: ;;.
ATS254= Bit Value Result 0 1 Allows to reject incoming call using ATH, ATZ commands or using DTR drop procedure. 1 2 Activate TIES (Time Independent Escape Sequence). The TIES procedure switches to command mode if "+++AT" (where represents hex digit 0x0D) sequence is detected in the data stream after a 20 ms pause and is followed by a 40 ms pause. ATS1001= Second origination address. This number is placed as the second origination address.
failure, connect in transparent mode. 3 Try to establish error correction; try to detect error correction (any supported). In case of failure, connect in transparent mode. 4 Force V.42 error correction. Disconnect in case of failure. 5 Force MNP error correction. Disconnect in case of failure. 6 Force V.42 or MNP error correction. Disconnect in case of failure. 7 Try to establish V.42 error correction; try to detect V.42 error correction. In case of failure, connect in transparent mode.
AT# commands AT command Description AT #CID=? Displays CID (Caller ID) setting. The short form of this command is "CID?". AT #CID= Sets CID mode. The TTY indicates the origination (CID) and destination (DAD) number in the RING and/or CONNECT message. This enables a server application for example to forward incoming calls directly to their destination.
Notes: [a] CID (Calling Party Number) is indicated as: RING CID: [b] CID (Calling Party Number) is indicated as: CONNECT ... CID: [c] Indicated as: RING CID: DAD: [d] Indicated as: CONNECT ... CID: DAD: [e] Indicated as: RING; [f] Indicated as: RING;; AT& commands AT command Description AT &C[] Accepted for compatibility reasons. : any integer AT &G[] Guard tone options 0 Turns guard tone off (default).
4 Enables XON/XOFF flow control. 5 Enables transparent XON/XOFF flow control. 6 Enables both XON/XOFF and RTS/CTS flow control (voice). AT &V Displays the current configuration, the last number that has been dialed (last DIAL to), and the calling party number of the last incoming call (last RING from). AT &V1 Displays current settings and settings of the available profiles. AT &F[] Resets the modem and restores the selected predefined modem configuration profile.
9 Use an mgetty friendly format for CID indication in RING message [e] 14 HylaFax friendly format RING CID: XXX[/YYY] DAD: HHH[/ZZZ] RING 15 Use an mgetty friendly format for CID and DAD [a] indication in RING message [f] Notes: [a] CID (Calling Party Number) is indicated as: RING CID: [b] CID (Calling Party Number) is indicated as: CONNECT ... CID: [c] Indicated as: RING CID: DAD: [d] Indicated as: CONNECT ...
AT +iC[] AT +iD AT +iF AT +iG Determines whether the modem stays in command mode after call setup. 0 Stays in command mode. 1 Switches to data mode. Delay for AT-command response (ms). 0 AT-command response is sent immediately. 1 ... 255 AT-command response is delayed. RNA Framing. [e] 0 No framing check (pass data transparently). 1 Force synchronous conversation (PPP). 2 Force asynchronous conversation (PPP). 3 Force synchronous conversation (RAS).
Maximum data frame length. should be in the range of 0 ... 2048. 0 defaults to the maximum frame length supported by the Dialogic® Diva® Media Board. AT +iL AT +iM AT +iN AT +iP Working mode 1 Normal operation mode. TTY does not try to preserve the protocol data unit boundaries (streaming). This mode fully emulates the behavior of a "classic" modem or terminal adapter connected via a serial interface. 2 Fax mode.
AT +iS 7 L1 - Fax, L2 - transparent, L3 - T.30 with ECM, T.6, MR, MMR, polling 8 L1, L2, and L3 - transparent 9 L1 - HDLC, L2, and L3 - transparent 10 L1 - HDLC, L2 - X.75SLP, L3 - BTX 11 external device 0 12 L1 - HDLC, L2 - X.75SLP and data compression autodetection in accordance with V.42bis, L3 - transparent Format Service Indicator/Additional Service Indicator Number Sets the Service Indicator to the provided value. The Additional Service Indicator is set to zero.
AT +iW Defers receive notifications to bytes/millisecond. should be in the range of 0 ... 64000. AT +iX Respects read block size and defers receive notifications. should be in the range of 0 ... 64000. AT +iY Defers transmission to bytes/millisecond. should be in the range of 0 ... 8. AT +iZ Splits large frames into byte segments. should be in the range of 0 ... 2048.
AT +iK= i0 Erase TTY binding for incoming calls a0 Erase TTY bindings for incoming and outgoing calls ? Display current bindings String Binding. See TTY "channel pool" mode on page 74 for details.
Note: This command must be used in conjunction with the AT+iQ command to first set the controller number that the tty interface is bound to AT +MF=, Data bits: 8,7,5. Parity: N (none), O (odd), E (even), S (space), M (mark). Stop bits: 1, 2. The transmission rate is derived from the currently selected Rx/Tx transmission speed (+MS command). Example: AT+MF=8,N,1 - select 8 data bits, no parity and one stop bit. AT +MF? Returns currently selected framing.
Fax class 1 and Fax class 2 AT commands The following list is an excerpt of the complete list. Command Description AT +FCLASS? Queries the configured modem class. AT +FCLASS=? Displays the supported modem classes. AT +FCLASS= Configures the modem for modem class . 0 - Data mode, 1 - EIA class 1, 2 - EIA class 2 AT +FMFR? Returns the name of the modem manufacturer. AT +FMDL? Returns the name of the modem model. AT +FREV? Returns the product version.
AT+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 command parameters Parameter Description mode Reserved. Should be set to 1. string The string defines the page header itself. Only ASCII printable characters are allowed in the string (0x20 thru 0x7e). Escape sequences that are introduced with the percent (%) character are allowed. The string can be partitioned into one, two, or three parts by using single quote characters (') in the command expression.
Supported TTY profiles You can use the AT&F[] and ATZ[] commands to select a TTY profile. Supported TTY profiles Profile Description 14 Autodetection of B-channel protocol. See Incoming RAS call type autodetection on page 69 for details. 1 X.75/Transparent/Transparent protocol stack. Data compression in accordance with V.42bis is detected automatically for incoming calls. 2 V.110 synchronous mode. 3 V.110 asynchronous mode. 4 Synchronous modem with V.42/V.42bis.
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 on page 70 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.
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 on page 69 for more information.
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.
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 on page 73. 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.
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 "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.
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 on page 49 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.
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.
9600 13 19200 14 38400 15 48000 16 56000 17 64000 18 11111 19 75 20 110 21 150 22 300 23 600 24 2400 26 4800 27 7200 28 9600 29 12000 30 14400 31 16800 32 19200 33 21600 34 24000 35 26400 36 28800 37 31200 38 33600 39 36000 40 77
38400 41 40800 42 43200 43 45600 44 48000 45 50400 46 52800 47 55200 48 56000 49 57600 50 60000 51 62400 52 64000 53 28000 54 29333 55 30666 56 32000 57 33333 58 34666 59 37333 60 38666 61 40000 62 41333 63 42666 64 44000 65 45333 66 46666 67 78
49333 68 50666 69 52000 70 53333 71 54666 72 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.
/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.).
#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.
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 on page 79 and provides only changes.
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.
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.
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.
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).
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__- where divas4linux__- is the name of the installed rpm package without the .i386.rpm extension.
• 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.
"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.
• 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: Parameters Description -r Reads the content of management interface directory or variable specified in . -w Sets the value of the management interface variable specified in . -e Executes the management interface function specified in . -m Monitors incoming/outgoing calls (line activity).
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.
Dialogic® Diva® Media Board management interface The Dialogic® Diva® Media Board management interface on page 133 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 "\".
ProtocolBuild MI_ASCIIZ RO XXX DSPCodeBuild MI_ASCIIZ RO XXX PRI MI_BOOLEA N RO Dialogic® Diva® PRI Media Board or Dialogic® Diva® BRI Media Board Channels MI_UINT RO Number of channels AnalogChanne ls MI_UINT RO Number of channels with modem capability PCIDMA MI_BOOLEA N RO Successfull test of PCI DMA capability IndentifyStart MI_EXECUT E RO Start Diva Media Board identification procedure DSPState MI_BITFLD RO Bit field to identify presence of DSPs Management interface stati
Management interface statistics\incoming calls directory Name Type Attribute Description Calls MI_UINT EVENT Number of incoming calls Connected MI_UINT EVENT Number of accepted calls User busy MI_UINT RO Number of calls refused because the user was busy Call rejected MI_UINT RO Number of calls refused because they were rejected Wrong number MI_UINT RO Number of calls refused because an invalid number was dialed Incompatible Destination MI_UINT RO Number of calls refused because th
Debug Level MI_HINT W Upper limit of debug events to log D-HW Txt Mask MI_BITFLD W D-channel hardware trace mask B-HW Txt Mask MI_BITFLD W B-channel hardware trace mask Misc Txt Mask MI_BITFLD W Trace mask for various use Event Enable MI_BITFLD W Bit field to enable specific trace events Max Log Length MI_UINT W Maximum number of data bytes in trace Log Buffer MI_TRACE EVENT Trace information: L1, D-channel, B-channel and debug information Dialogic® Diva® TTY management interface
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.
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.
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 reinitialize 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.
TE Dialogic® Diva® CAPI management interface directory The CAPI driver management interface on page 134 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.
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.
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.
ifType The type of the interface according to IANA: PRI, BRI, ISDN ifMTU Since the concept of MTU is not applicable on Diva interfaces, they return 0. ifSpeed The maximum interface speed in bps ifAdminStatus Always up ifOperStatus The current operating status of the interface ifInBytes, ifInPackets, ifInErrors, ifOutBytes, ifOutPackets, ifOutErrors For boards, the added values of the D- and B-channel interface counters are returned.
ISDN-MIB DIALCONTROL-MIB transmission.isdnMib.isdn MibObjects.isdnBearerGro up.isdnBearerTable.isdnB earerEntry B-channels isdnBearerChannelType dialup or leased isdnBearerOperStatus idle, active, unknown isdnBearerChannelIndex Index of B-channel per Diva Media Board isdnBearerPeerAddress Remote address isdnBearerPeerSubAddres s Remote sub address isdnBearerCallOrigin Answer or originate isdnBearerInfoType Info type as per Q.
DIALCONTROL-MIB (RFC2128) DIALCONTROL-MIB transmission.dialControlM ib.dialControlMibObjects.c allHistory callHistoryTableMaxLengt h The maximum number of entries in the callHistoryTable (read/write). callHistoryRetainTimer The minimum amount of time in minutes that a callHistoryEntry will be maintained before being deleted. transmission.dialControlM ib.dialControlMibObjects.c allHistory.callHistoryTable .
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.
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 [], where: 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.
Q.931 CR81 REL_COM Cause 80 d8 "Incompatible destination" EVENT: Call failed in State "Call initiated" Q.
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 -monitor [] D-channel monitor mandatory parameters Param eter Description x The logical board number to be traced.
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.
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: Command Description divactrl load -c ReadXlog Reads XLOG information from board , decodes it, and prints it to standard output. divactrl load -c ReadXlog -File .
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.
mdm Modem with full negotiation/V.42+V.42bis/Transparent. l Optional Length of the test frame. It is normally not used by the test server but it should be provided if the -s option follows -s Optional Speed adaptation rate. This parameter should be indicated if the v110 Bchannel protocol is used without auto detection. It should range between 2 and 9 (5-9600, 9-56000).
tty_test in client mode The test client can be started with the following commands: Command Description tty_test [l -s] [a] [-y] [-m] This command starts a test client on your console. tty_test [l -s] [a] [-mpackets] -x& This command starts a test client in the background. In this mode, the test client detaches from your console and does not display any output.
l Optional Length of the test frame. It is normally not used by the test server but it should be provided if the -s option follows. -s Optional Speed adaptation rate. This parameter should be indicated if the v110 B-channel protocol is used without auto detection. It should range between 2 and 9 (5-9600, 9-56000). If this option is selected, the -l option should also be used. a Optional Allows to provide additional AT-command strings used for client initialization.
#! /bin/sh #This "n_cons" value will start 30 server and 30 client sessions n_cons=30 # remove old log files rm -f log.* while [ $((n_cons)) -ge 1 ] do echo "Start $(($n_cons+30)) -> $((n_cons))" /usr/lib/opendiva/divas/tty_test $((n_cons)) sv auto& sleep 1 /usr/lib/opendiva/divas/tty_test $(($n_cons+30)) 800 v110 -l512 -a+ib5+iu="<8890214800bb>" -x& sleep 1 n_cons=$(($n_cons-1)) done # # Note that tty_test updates log files after 64 KBytes # of data have been transferred.
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 t Parameters for the tty_test in terminal mode Parameter Level Description tty_test Mandatory Dialogic® Diva® TTY number that should be used by this test. It should range between 1 and N, where N is the sum of B-channels of the Dialogic® Diva® Media Boards installed in the system. Normally, is forwarded to TTY.
Web interface You can use the Dialogic® Diva® web interface, accessible at port 10005, to gain access to 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.
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 on page 121. The server will automatically log you off after 15 minutes of inactivity.
the following help window appears: Dialogic home page Click the Dialogic symbol to access the Dialogic home page. Reference Guide 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 on page 118, the Dialogic® Diva® WEB server presents you the main page: 121
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.
Board configuration If you click Board configuration on the left side, the following page opens, which allows you to create/change the configuration of the Dialogic® Diva® Media Boards, to restart or disable the selected Diva Media Board if necessary, and to start the Diva Media Board identification process.
Use the Restart symbol to restart. In the drop-down menu on the right of the Diva Media Board description you can select different options: • Select Configuration to start the configuration of the selected Diva Media Board and a screen similar to the one shown below is displayed. • When you select Identify on, 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.
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.
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.).
Call routing configuration This page allows you to configure the call routing by automatically configuring the Direct Inward Dialing (DID) length and a special number for Dialogic® Diva® Media Boards where DID is activated in the Board configuration on page 123. To allow a more sophisticated routing configuration with the possibility to configure number ranges, different targets (CAPI/DSAPI vs. TTY), and configure different kinds of call distributions, you can select an Advanced configuration method.
Simple configuration method The Simple configuration method uses only the Diva Media Board internal configuration Direct Inward Dialing (DID) to allow the collection of a specific number of digits and the DID special number, which allows to configure a special number with less digits, e.g., for a receptionist.
Under Use DID Length, you can either select the length of the DID number or the use of a special number. The latter lets you configure a number with less digits, in many companies needed for the receptionist. If you select this option, you need to enter the number in Use Special Number. Advanced configuration method The Advanced configuration method allows for routing calls to a certain application, e.g., to a fax application.
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. 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.
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 on page 88 of Diva Media Boards and drivers: 131
Management interface browser You can navigate through the Management interface on page 88 of the selected Dialogic® Diva® Media Board or driver using the management interface browser: The management interface is available for: • Dialogic® Diva® Media Boards see "Dialogic® Diva® Media Board management interface" on page 133 • the Dialogic® Diva® TTY driver see "Dialogic® Diva® TTY driver management interface" on page 135 • the CAPI driver see "CAPI driver management interface" on page 134 132
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.
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.
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: 137
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 on page 141 for more information.
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.
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.
View trace file This page allows you to decode and to view a trace file.
Finally, you can view or download the decoded trace file: 142
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).
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 146
Digital oscilloscope (view timing diagram) 147
Digital spectral analyzer 148
EYE pattern diagram WAV file download Moreover, it is possible to download an Audio Tap file in "WAV" file format.
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.
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).
152
153
154
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.
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.
Product Features Supported interfaces 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. The services provided by the Dialogic® Diva® Media Boards are accessible via system interfaces. The features may not be available on every supported interface.
Features of Dialogic® Diva® BRI and PRI Media Boards via interface The following features are available with the Diva ISDN Media Boards: Feature IDI TTY CAPI 2.0 / Dialogic® Diva® API Transparent HDLC, 64/56[d] kbps • • • Transparent (Voice) (8 bit 8 kHz A- Law/u-Law) • • • X.75 64/56[d] kbps • • • X.75/V.42bis • • • T.70/T.90 (T-Online) [g] • • • V.110 (GSM) [a] [g] • • • V.120 64/56 kbps (CompuServe) • • • V.120/V.42bis • • • Digital (Central Office) V.
FAX CLASS 1, 2 [a] [g] • Fax with Error Correction Mode (ECM) [a] [g] • • • Fax with MR (D2 coding) [a] [g] • • • Fax with MMR (T.6 coding) [a] [g] • • • Fax 33.6 kbps with MMR (T.6 coding) [a] [g] • • • Fax 14.4 kbps [a] [g] [h] • • • Fax 33.6 kbps (V.34) [a] [g] [h] • • • Fax T.38 (up to 33.
Dynamic anti-jitter buffer [a] [d] • VoIP processing [a] • Transparent D-channel • • X.25/D-channel including AO/DI support • • Notes: [a] These features are not available with Dialogic® Diva® PRI/E1/T1-CTI Media Boards. [b] PIAFS support is not available with Dialogic® Diva® BRI-2FX Media Boards. [c] Including T.90/ISO8208 and module mode detection. [d] These features are not available with the Dialogic® Diva® BRI-2FX Media Board. [e] CAPI 2.0 (Dialogic® Diva® API) supports X.
Supplementary services of Dialogic® Diva® BRI and PRI Media Boards via interface For an overview of supplementary services supported by the different switch types, see Supplementary services of Dialogic® Diva® BRI and PRI Media Boards per switch on page 163. Supplementary Service IDI TTY CAPI 2.
User-to-user signaling • • 162
Supplementary services of Dialogic® Diva® BRI and PRI Media Boards per switch The Dialogic® Diva® System Release software supports basic call services for the available switch types. In addition to this, it offers supplementary services for the following switch types: • Euro-ISDN (ETSI) BRI and PRI • 5ESS Custom (AT&T) • 5ESS NI (Lucent/Avaya) • DMS 100 (Nortel) • Q.SIG Q.SIG support is available for the derivatives ETSI-SS, ECMA-QSIG, and ETSI- QSIG. Thus, the Q.
Call forwarding busy • Call forwarding no reply • Call deflection • CW (call waiting) • HOLD (hold and retrieve a call) • [b] ECT (explicit call transfer) • • • [c] • • • [d] • Path replacement • Single-step call transfer (over CAPI deflection) • AoC (advice of charge) • • • Three-party conference • • Large conference • • Drop conference • • User-to-user signaling • • • Name identification services • [e] Generic functional procedures (basis for supplementary services
Notes: [a] In a Q.SIG environment, the feature is also called "Simple Dialog". [b] HOLD is not a standard supplementary service for Euro-ISDN PRI, nevertheless some PBXs support call hold and retrieve. [c] HOLD is not defined in Q.SIG but corresponding procedures are available. [d] Call transfer is only possible if path replacement works for one sub-PBX. [e] Presented by switch. [f] Presented by the network.
Voice and speech features • G.711 coding (a-law, µ-law selectable) • DTMF detection and generation • DTMF clamping and filtering • Generic tone detection and generation • Pulse tone detection • Full-duplex voice, "barge-in" • Voice activity detection • Silence detection • Human talker detection • Fax signal detection • G.168 echo cancellation, up to 128 ms tail length • Recording Automatic Gain Control (ACG) • Pitch control • Audio tap Voice over IP support • G.
Fax • Support for Fax class 1 and 2 • Support for Fax Group 3, T.30 • V.17, V.29, V.27ter, V.21, V.34 Modulation • Up to 33.600 bps with each channel (send and receive) • Fax compression MH, MR, MMR • Error Correction Mode (ECM) • Reversal of fax direction • Fax password • Fax sub addressing • New fax header line • Page formats: ISO A4, B4, A3 • Standard, fine, super-fine and ultra-fine resolution • Color fax (JPEG-Format) Data modem features • V.21, V.22, V.
Use of the Dialogic® Diva® System Release Software in a Customized Environment Once the .bin files (binary files) are installed, the modules still have to be translated for the running kernel. Base drivers The following drivers are available as source code under GPL license: • divadidd.[k]o • divas.[k]o • diva_mnt.[k]o • diva_idi.[k]o • kernelcapi.[k]o • divacapi.[k]o • capi.[k]o They can be compiled for a specific kernel using the source level package.
Dialogic® Diva® TTY driver The Dialogic® Diva® TTY driver is provided only in binary form, and can only be recompiled for your own kernel using the source level package. This section describes the usage of this driver with customized kernels if the aforementioned method is not applicable. The Dialogic® Diva® TTY interface relies on a limited amount of exposed kernel services.
• Note that the kernel configuration options can change the layout of these structures. • Now you can compare the settings of these configuration options of your customized kernel and the kernel that the Diva TTY driver was compiled for. You can use include/linux/autoconf.h files for this purpose. • Use include/linux/autoconf.h to compare the configuration options that can affect the CPU model.
