Receiving fax with mgetty

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

On Wed, Oct 27, 1999 at 06:47:30AM +0200, Volker Englisch wrote:
> Well, first of all I have to admit that I wonder what language was
> the right one to use in this de.* newsgroup, for most articles seem to
> be written in English. So I'll try to write in English, too, being
> curious about the things that will happen...

English is fine, thank you (the reason is that the newsgroup is gatewayed
to the mgetty mailing list, with about 500 readers all over the world -
most speak English, hardly anyone speaks German...)

> Does anyone have experience with receiving fax by means of mgetty? 

Um, yea :-) - most of us.

> In general, sending faxes works fine here, they are prepared using
> faxspool and sent out using faxrunq once per night. The modem ist an
> elder one, 14400 bps max., that ran with a DOS system formerly and
> showed that is was able to send and receive fax documents. Actually the
> OS is (Debian) Linux, but it is still the same modem (and the same
> cable!) between the modem and the machine.

Good...

> When a fax call comes in, the modem goes offhook and sends the typical
> fax answer tones. But after a few seconds of handshake the connection
> terminates, and the follwing e-mail is sent to the root user:

Let's look into the mgetty log...

> 10/22 17:38:19 yS0  mgetty: experimental test release 1.1.14-Apr02
> 10/22 17:38:19 yS0  check for lockfiles
> 10/22 17:38:19 yS0  locking the line
> 10/22 17:38:20 yS0  WARNING: DSR is off - modem turned off or bad cable?

This is not a problem (just for the records).

> 10/22 17:38:20 yS0  lowering DTR to reset Modem
> 10/22 17:38:20 yS0  send: \d\d\d+++\d\d\dAT&F2L1[0d]
> 10/22 17:38:23 yS0  waiting for ``OK'' ** found **
> 10/22 17:38:24 yS0  mdm_send: 'ATI'
> 10/22 17:38:24 yS0  unknown numerical modem id 242
> 10/22 17:38:24 yS0  mdm_send: 'AT+FCLASS=2.0' -> ERROR
> 10/22 17:38:24 yS0  mdm_send: 'AT+FCLASS=2' -> OK
> 10/22 17:38:24 yS0  mdm_send: 'AT+FAA=0;+FCR=1' -> OK
> 10/22 17:38:25 yS0  mdm_send: 'AT+FBOR=0' -> OK
> 10/22 17:38:25 yS0  mdm_send: 'AT+FLID="+49 8382 23014"' -> OK
> 10/22 17:38:25 yS0  mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
> 10/22 17:38:26 yS0  waiting...
> 10/22 17:38:28 ##### failed dev=ttyS0, pid=361, got signal 15, exiting

Hmmm.  This is pretty weird, and I don't think this is the actual log file
showing the incoming call - 2 seconds after going into "waiting for an
incoming call" state, someone/something kill'ed mgetty with a "SIGTERM".

It should show something like "waiting for RING", and then "ATA", etc.

[..]
> For test purposes, I omitted the keyword "switchbd" and re-initialized
> mgetty, but there was no different behaviour then. Any idea what's
> going wrong?  

Not really.  The log file is weird, as it doesn't even show the incoming
call.

> I also can't understand the reason for the warning about DSR being off
> - the same modem and cable is used for UUCP and works fine, even with a
> higher bps rate between the modem and computer. Btw., the computer is a
> i386, with a 16550A serial chip.

The DSR warning means "if there is a problem later on, like AT -> timeout,
it could mean that the modem is switched off, or the cable fell of" - to
ease remote debugging.

In your case, it just means "everything works, but the modem is set to 
have DSR off while not connected".  AT&S<0 or 1> changes that behaviour.

But it's definitely not related to the problem.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de