Dialogic Voice Cards - Using Hylafax with Diva Media boards
- Nathaniel Halbrooks
- Kelli Higdon
NOTE
Whilst Dialogic can offer support on the Dialogic-specific parts of the installation, if your problem is more general, such as being unable to compile Hylafax, we recommend you contact the support forum for that particular package.
Follow the instructions below in order to carry out a basic configuration of a Diva Media Board with Hylafax.
Download the latest Diva System Release for Linux for your Diva Media board. This is available from the
Dialogic Diva System Release for Linux page.
Ensure that you do not have the ISDN4Linux driver or the HiSax driver installed. The Diva System Release has a TTY interface, so the CAPI4Hylafax package is also not required.
Follow
How to install Diva System Release for Linux.
Follow the
Configuration procedure. Make sure that as part of the configuration you specify that you want to use the TTY Interface.
After installing Hylafax, please use the following configuration file as a template for your scenario. Save this file as config.ttyds01, for example.
********************************************************************************************
# Config File for tty modem
# $Id: eicon-2,v 1.2 2004/03/05 02:29:32 lhoward Exp $
#
# prototype config file for the Diva ISDN Modem
#
#
#
CountryCode: 44
AreaCode: 1628
FAXNumber: 3842XX
LongDistancePrefix: 0
InternationalPrefix: 00
DialStringRules: "etc/dialrules"
ServerTracing: 0xfff
SessionTracing: 0xfff
RecvFileMode: 0600
LogFileMode: 0600
DeviceMode: 0600
RingsBeforeAnswer: 2
SpeakerVolume: off
#GettyArgs: "-h %l dx_%s"
GettyArgs: "-b -r -s %s %l"
LocalIdentifier: "HylaFax -Diva Server"
TagLineFont: etc/lutRS18.pcf
TagLineFormat: "From %%l|%c|Page %%P of %%T"
MaxRecvPages: 25
#
#
ModemType: Class2
ModemRate: 57600 # Diva Server supports V.34-fax
ModemFlowControl: rtscts
ModemNoFlowCmd: AT&K0
ModemSoftFlowCmd: AT&K4
ModemHardFlowCmd: AT&K3
Class2APQueryCmd: none
Class2SPLCmd: none
Class2TBCCmd: none
Class2ECMType: 2.0 # follows Class 2.0 spec, not Class 2
#Bind Modem to Controller 1
ModemResetCmds: AT#CID=14+iQ=a1
# Put the Destination Address in CIDNumber. We can the reject calls on the basis
# Of where we are sending them, instead of the Caller ID
CIDNumber: "DAD: "
CIDName: "CID: "
QualifyCID: etc/cid # CID access control list file
******************************************************************************************** |
The most important lines here are
RingsBeforeAnswer: 2
This allows enough time for the calling party number and called party number information to be passed to the Hylafax application.
ModemResetCmds: AT#CID=14+iQ=a1
This passes the called party number and calling party number in a format that Hylafax understands. The command +iQ=a1, binds the tty port to a Diva Media board (or to a controller where the board has more than one controller), which in this example is controller 1.
If you have multiple Diva Media Boards in your machine, or if you have a Diva 4BRI (which has 4 controllers), use the command +iQ=aN where N is the number of the card (or controller if you have a 4BRI) that you want to bind your tty port to.
In addition, if you have a Diva Analog board, use the command +iK=aM where M is the line number of the Diva Analog board that you want to bind your tty port to. 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. An example can be found here.
Note: Several other AT commands may be used in the ModemResetCmds string.