Dialogic® Diva® System Release 8.5LIN Reference Guide www.dialogic.
Contents Dialogic® Diva® System Release LIN Reference Guide 3 Syntax used throughout the guide........................................................................................ 3 Copyright and Legal Disclaimer 4 Software License Agreement 5 About the Dialogic® Diva® System Release Software 9 Features ............................................................................................................................. 9 System requirements................................................
Management interface 73 "divalogd" accounting utility ............................................................................................... 73 Management interface access and monitoring utility ............................................................ 74 Management interface structure ......................................................................................... 75 Dialogic® Diva® SNMPX extension agent 83 Requirements .............................................................
Dialogic® Diva® System Release LIN 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 Disclaimer Copyright © 1993 - 2008 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation. 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").
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.
• Each end user to whom a Licensed System is distributed must agree to license terms with respect to the Program that are at least as protective of Dialogic's rights in the Program as those set forth in this Agreement; • You shall receive one (1) Program master disk, and shall be solely responsible for copying the Program into the Licensed Systems and for warranting the physical media on which it is copied • You may make one (1) copy of the documentation accompanying the Program, provided that all copy
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 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. Additional software provides integrated support for the SIP and SS7 protocols.
General features The Dialogic® Diva® System Release software offers the following features: • RAS connection to a Linux-based RAS server from digital, analog, and mobile networks with only one telephone number • LAN-to-LAN connection with a transfer rate of 64/56 kbps or 128/112 kbps for Dialogic® Diva® BRI Media Boards, 2 (E1) or 1.
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.
Q.SIG features • Basic call (64 kbps unrestricted, 3.1 kHz audio and speech bearer services) ECMA 142/143 • Line identification presentation ECMA-148 • Name identification presentation ECMA-163/164 • Generic functional procedures ECMA-165 • Call deflection (call rerouting) ECMA-173/174 • Call transfer ECMA-177/178 (only with working path replacement) • Path replacement ECMA 175/176 • Advice of charge ECMA-211/212 (incl.
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.
Licensable features For the following features you need to purchase a license: Licensable features for the Dialogic® Diva® Media Boards, except the Dialogic® Diva® 2FX Media Board Support for G.729 incl. Annex A and Annex B voice codec Licensable 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.8 kbps for 8 kHz • Support for AMR-NB voice codec • Support for G.729 incl.
- Extended modulations V.23 half duplex, V.23 on hook (SMSC mode), V.23 off hook, Bell 202 (POS), Telenot 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.
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.
Files included in the package The following files are included in the package: 17
• 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.
After you have installed your Dialogic® Diva® product, you might need to generate a license and activate it in the web interface to unlock the required functionality in the product. You need to generate a license if you have installed one of the following products and purchased a license for one of the following functionalities: Product Functionality Dialogic® Diva® System Release LIN • Dialogic® Diva® softIP for SIP v2.2 software • Dialogic® Diva® SIPcontrolTM v1.
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: http://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 on page 22.
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.
Maintenance The Dialogic® Diva® WEB Configuration Wizard provides access to the following maintenance functions: • System environment on page 26 allows for viewing hardware-related settings of the host system. • Trace/Debug on page 27 allows for creating debug and trace files of the Dialogic® Diva® Media Board or the system. • Support/Troubleshooting on page 27 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 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. Normally, you do not need to limit the fax speed because the Diva Media Board automatically negotiates the appropriate speed. Disable fine resolution Disables the transmission of fax messages with high resolution. Disable Error Correction Mode (ECM) Disables the transmission of fax messages using ECM (Error Correction Mode).
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.
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 [5] utility is located in the /usr/lib/opendiva/divas directory. Many other options, e.g., packet size, CPN, SubAddress, and commands are available. Type /usr/lib/opendiva/divas/acopy2 for a full list.
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 I[] INFO. Returns the modem identification string. : integer ranging from 0 to 9 AT H[0] HANGUP. Disconnects the line. AT O[1] ONLINE. Switches the modem from command mode to data mode. AT Q[] Modem response mode AT V[] 0 Returns result codes (default) 1 Quiet mode. In quiet mode the modem driver does not return result codes for the commands. Modem response (result code) format 0 Numeric result codes. 1 Plain text result codes (verbal mode, default).
ATS2= ATS7= Description (0 ... 255) 127 Disables the escape sequence process, i.e. no escape character is recognized. 43 The default value of the ESCAPE character ("+"). 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.
ATS91= 4 16 Reserved 5 32 Reserved 6 64 Reserved 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. 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.
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.
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. 8 Try to establish MNP error correction; try to detect MNP error correction. In case of failure, connect in transparent mode. 10 Force SDLC error correction. Disconnect in case of failure. 11 Try to establish SDLC error correction.
Supported 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.
2 Turns 1800 Hz guard tone on. AT &D[] Data Terminal Ready (DTR) options. ranges from 0 to 3. See AT&Q command below. AT &Q[] Communication options. ranges from 0 to 3.
Supported AT$ commands AT command Description AT $F Controls Dialogic® Diva® FastSetup. 0 - Normal connection (default), 1 - FastSetup without answer/calling tone, 3 - FastSetup with answer tone. The AT+MS command can be used to control the allowed FastSetup modulations: AT+MS=V90a,1 - v.22 and v.22bis FastSetup, AT+MS=v22 - v.22 FastSetup, AT+MS=v22b,0 - v.22bis FastSetup. Supported AT+ commands AT command [a] [b] Description AT +iA Accepted address.
AT +iF AT +iG 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). 4 Force asynchronous conversation (RAS). 5 Detects required conversation by analyzing incoming data packets. Bit Value RNA patches. Controls the behavior of the ASYNC/SYNC PPP conversion module.
AT +iN AT +iP 4 RNA mode. TTY operates in framing mode, investigates protocol data units, and provides ASYNC/SYNC conversion if necessary. 5 BTX over ISDN mode. 6 Frame mode. The TTY preserves the frame boundaries of the ISDN data frames. Note that the Linux TTY interface will stream the data again. Format Numbering plan for destination/origination address and presentation/screening indicators for origination address.
AT +iS Format Service Indicator/Additional Service Indicator Number Sets the Service Indicator to the provided value. The Additional Service Indicator is set to zero. The number should be in the range 1 ... 7. Number1/N umber2 Number 1: Service Indicator. It should be in the range of 1 ... 7. Number 2: Additional Service Indicator. It should be in the range of 0 ... 255. [f] At +iT ISDN trace options. Reserved for use by Dialogic. ranges from 0 to 255.
AT +iQ= AT +iK= AT&F18+IE=piafs China variable speed PIAFS link AT+IE=none Resets the tty interfaces to "default" mode (i.e. signaling information will be used to determine the call type) String Binding. See TTY "channel pool" mode on page 58 for details.
AT +MF=, 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. AT +MF=? Returns list of supported parameters. AT +MS? Modulation Selection Query.
Supported Class Fax1 and class Fax2 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+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 Parameter Description year The current year. Range: 1970 to 65535 month The current month number. Range: 1 to 12. January is 1. day The current day of the month. Range: 1 to 31. hour The current hour. Range: 0 to 23. minute The current minute.
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 53 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 54 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 53 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 57. 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 [7].
"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.
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.
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 38400 41 40800 42 43200 43 45600 44 48000 45 62
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 49333 68 50666 69 52000 70 53333 71 54666 72 63
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.
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.
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 test1 test2 * * pwdtest1 pwdtest2 IP addresses * * 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 test1 test2 * * pwdtest1 pwdtest2 IP addresses * * 8. Create for every ttydsxx interface that you use for dial-in server (i.e.
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.
# # 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.
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.
#! /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/^.
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.
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.
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.
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 [11] with its own system of events.
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 directory The Dialogic® Diva® Media Board management interface on page 111 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 "\".
PRI MI_BOOLEAN RO Dialogic® Diva® PRI Media Board or Dialogic® Diva® BRI Media Board Channels MI_UINT RO Number of channels AnalogChannel s MI_UINT RO Number of channels with modem capability PCIDMA MI_BOOLEAN RO Successfull test of PCI DMA capability IndentifyStart MI_EXECUTE RO Start Diva Media Board identification procedure DSPState MI_BITFLD Bit field to identify presence of DSPs RO Management interface Statistics\Outgoing Calls directory Name Type Attribute Description Calls M
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 the destination was not compatible with the TE Out of Order MI_UINT RO Number of calls refused because destination was out of order Ignored MI_UINT RO Number of calls refused because the call was ignored Other failures MI_UINT RO Number of calls refused because
Log Buffer MI_TRACE EVENT Trace information: L1, D-channel, B-channel and debug information Dialogic® Diva® TTY management interface directory (Port Manager) The Dialogic® Diva® TTY driver management interface on page 113 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.
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 of 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.
Dialogic® Diva® CAPI management interface directory The CAPI driver management interface on page 112 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 adapter 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.
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 MIB-II (RFC 1213/2 233) Path MIB-II interfaces.ifTable.ifEntry. Description ifIndex Unique index of Dialogic® Diva® interfaces starting with ifIndexoffset + 1 (see option -oN).
ISDNMIB (RFC212 7) transmission.isdnMib.isdnMi bObjects.isdnSignalingGroup isdnSignalingGetIndex ISDNMIB ISDNMIB DIALCONTRO L-MIB Number of possible D-channels (equals number of installed Diva Media Boards) transmission.isdnMib.isdnMi Dialogic® Diva® BRI Media Boards bObjects.isdnBasicRateGrou p .isdnBasicRateTable.
DIALCONTRO L-MIB (RFC212 8) DIALCONTRO L-MIB callActiveIndex Unique index callActivePeerAddress Address of remote partner callActivePeerSubAddress Subaddress of remote partner callActivePeerId Always 0 (unknown) callActivePeerIfIndex Always 0 (unknown) callActiveLogicalIfIndex Index of entry in ifTable for the interface used by this call callActiveConnectTime 0 if the call was not connected, otherwise timeticks measured from start of divasnmpx.
callHistoryDisconnectTime Timeticks measured from start of divasnmpx. callHistoryCallOrigin Direction of call: Answer or originate. 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.
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.
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.
SIG-X(004) 08 01 82 01 Q.931 CR82 ALERT SIG-X(007) 08 01 82 0D 18 01 89 Q.931 CR82 SETUP_ACK Channel Id 89 SIG-R(004) 08 01 02 0F Q.931 CR02 CONN_ACK SIG-R(008) 08 01 81 5A 08 02 80 D8 Q.931 CR81 REL_COM Cause 80 d8 "Incompatible destination" EVENT: Call failed in State "Call initiated" Q.
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 Parameter 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 [16] to control that the board remains in the operating (active) state. 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.
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.
Optional l 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 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).
x75v42 HDLC/X.75 with V.42bis data compression/Transparent. This protocol is not used on the server side because x75 automatically detects X.75 with V.42bis. v120 HDLC/V.120/Transparent V.120 with V.42bis is possible. v110 V.110/Transparent/Transparent mdm Modem with full negotiation/V.42+V.42bis/Transparent.
Optional l 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 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 (59600, 9-56000). If this option is selected, the "-l" option should also be used. Optional Optional a 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.
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 on page 104. 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 102 the Dialogic® Diva® WEB server presents you the main page: 104
System control (driver start/stop) If you click System control (driver start/stop) the following page opens, where you can start and to stop Dialogic® Diva® drivers. The Dialogic® Diva® WEB server will detect the current state of the drivers and opens you 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 Indentify 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.
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 serve, 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® SIPcontrolTM 1.
Board monitor If you click Board monitor on the left hand side the following page opens, which allows you to control 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 73 of Diva Media Boards and drivers: 109
Management interface browser You can navigate through the Management interface on page 73 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 111 • the Dialogic® Diva® TTY driver see "Dialogic® Diva® TTY driver management interface" on page 113 • the CAPI driver see "CAPI driver management interface" on page 112 110
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.
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.
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 118 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.
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: 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 Digital oscilloscope (view timing diagram) 122
Digital spectral analyzer 123
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).
127
128
129
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 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.
Features of Dialogic® Diva® ISDN Media Boards via interface See the table on the next page for features available with the Diva ISDN Media Boards: 133
Feature IDI TTY CAPI 2.0 Transparent HDLC, 64/56 kbps • • • Transparent (Voice) (8 bit 8 kHz A- Law/u-Law) • • • X.75 • • • X.75/V.42bis • • • T.70/T.90 (T-Online) • • • V.110 (GSM) [a] • • • V.120 64/56 kbps (CompuServe) • • • V.120/V.42bis • • • Digital (Central Office) V.90 modem [a] • • • V.34+, V.90 analog modem [a] • • • SMS modem ETSI V1,V2 and auto-detection [a] • • • Dialogic® Diva® Fast Setup [a] • • • SDLC • • • V.42, V.
Fax 33.6 kbps with MMR (T.
Supplementary services of Dialogic® Diva® ISDN Media Boards via interface For an overview of supplementary services supported by the different switch types, see Supplementary services of Dialogic® Diva® ISDN Media Boards per switch on page 138.
Supplementary Service IDI TTY CAPI 2.
Supplementary services of Dialogic® Diva® ISDN Media Boards per switch The Dialogic® Diva® System Release software supports basic call services for the available switch types.
• Euro-ISDN (ETSI) BRI and PRI • 5ESS Custom (AT&T) • 5ESS NI (Lucent/Avaya) • DMS 100 (Nortel) • Q.SIG Q.SIG support is available for the derivatives ETSI-SS, ECMA-QSIG, and ETSI- QSIG. Thus, the Q.SIG switch type can be used with any PBX based on one of these derivatives. Q.SIG has been tested with a number of various switches, for example, Hicom 150, Hicom 300, Lucent Definity, Alcatel 4200, Alcatel 4400, Ericsson MD 110, Nortel Meridian, and Nortel M65xx.
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 in Q.SIG environment) • Common information • Redirected number translation from Q.SIG to Q.
Features of Dialogic® Diva® Analog Media Boards Dialogic® Diva® Analog Media Boards offer the following feature set: • Call control features on page 141 • Voice and speech features on page 142 • Voice over IP support on page 142 • Switching and Conferencing on page 142 • Fax on page 143 • Data modem features on page 143 Call control features • Pulse dialing • Tone (DTMF/MF) dialing • Busy tone detection • Ring back tone detection • Special Information Tone (SIT) detection • Fax/modem
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. 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.
• Change the configuration of your kernel now in order to meet the configuration of the kernel that the Diva TTY driver was compiled for and recompile your kernel. [1] The availability of supplementary services depends on your switch or PBX. [2] 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.
[9] 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.
[19] The stunnel is designed to work as SSL encryption wrapper between remote clients and local (xinetd-startable) or remove servers. The concept is to have non-SSL aware daemons running on your system. You can easily set them up to communicate with clients over secure SSL channels. [20] Drivers for SMP (Multi-processor) systems are compiled using the same symbol version information settings as set by the original kernel configuration.
