HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: hylafax and mgetty



-----BEGIN PGP SIGNED MESSAGE-----

On Fri, 16 Jul 1999, Torsten Mueller wrote:

> hello,
> my modem is a multitech 2834zdxg
> 
> my problem: sometimes if there is an incoming fax, faxgetty tries to
> start
> mgetty (why this ?) and mgetty tries to get the fax .
> then i get a message from mgetty like this:

You neglected to mention your HylaFAX version, your mgetty version,
your operating system, or your local configuration (such as the
$SPOOLDIR/etc/setup.cache created when you installed HylaFAX).

faxgetty should be answering the line, and should be the *only* job
left running on the line. That should fall through to call a data
getty or voice getty if it is not a fax call....

> 1. Why tries mgetty to process the incoming call and not faxgetty ?

Can't tell: take a look at your setup.cache for clues.

> 2. How can i "disable" mgetty, so that all incoming calls are handled by
> faxgetty ?

Delete it, and make sure no jobs are left running on other names for
the same serial line (say, faxgetty is on /dev/modem, mgetty is
accidentally left on /dev/ttyS0 or /dev/cua0 and they are linked to
each other)

> 3. What about this file /tmp/FAXnd8f0.01 ? it seems not to be a valid
> bitmap, tiff, ps file.

Can't tell.

> 4. Is it o.k. to use this config file, as it is for Multi-Tech MT1432,
> MT224BA, and MT1932ZDX modems ?


> 
> # Configuration for a Multi-Tech MT1432, MT224BA, and MT1932ZDX modems.
> #
> # MT1432 firmware rev 0307 I or newer
> # MT132BG rev 0109A
> # MT1932ZDX rev 0109H
> #
> # Note that MT1432 modems come in several varieties:
> #
> # MT1432BA uses Rockwell data pump
> # MT1432BA/A uses AT&T data pump
> # MT1432BG MT1432BA tweaked for German FCC
> # MT1432MK (for UK?)
> #
> # The modem has been tried with both XON/XOFF and RTS/CTS flow
> # control; this configuration is for hardware flow control.


> # Modem-related stuff: should reflect modem command interface
> # and hardware connection/cabling (e.g. flow control).
> #
> ModemType:  Class2  # use class 2 interface
> ModemRate:  38400  # lock rate for DCE-DTE communication
> ModemFlowControl: rtscts  # default
> ModemHardFlowCmd: AT&E4  # hardware flow control
> ModemSoftFlowCmd: AT&E5  # software flow control
> ModemSetupDTRCmd: AT&D3  # setup so DTR drop resets modem
> ModemSetupDCDCmd: AT&C1  # setup so DCD reflects carrier (or not)
> ModemSetupAACmd: AT+FAA=1 # enable adaptive-answer in class 2
> ModemDialCmd:  ATX3DT%s  # T for tone dialing, @ for silence
> #
> Class2RecvDataTrigger: "\022"  # character sent to modem to start recv

I don't see any obvious problems: you may want to play with ModemSetupAACmd,
since different modems have to be in Class 0 or Class 1 or whatever
to do adaptive-answer.

			Nico Kadel-Garcia
			Senior Engineer, CIRL 
			Mass. Eye and Ear Infirmary
			raoul@cirl.meei.harvard.edu

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBN4+Sdz/+ItycgIJRAQHnvwP/UdImXJqLPJDrecu4mnDuvLSoGwScp5FU
AW152/JeHFoIsDuo/GclbWevNXve8LSsWf1jIUWtrtMbHvuzPizSq+wKYcRtyCN6
vPKywcdITh7j6tEemhlouVugXecf5SJDIUbJq/4S1gc4V273hjc5eEwL2VJssG1R
niV/gIBm5rg=
=RpQw
-----END PGP SIGNATURE-----




Project hosted by iFAX Solutions