new serial hw - new problem

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

At 06:22 PM 12/16/98 +0100, Gert Doering wrote:
>Hi,

Hi, and thanks for the quick reply.

> - your application seems to call "sendfax" with stderr redirected to
>   /dev/ttyr1A, which will cause its error messages to go to the modem
>   (that's the "RTN: page bad" stuff up there).  Bad idea, if you want
>   to redirect stderr, send it to /dev/null.

The application calling sendfax is faxrunqd.  Another oddity was that after
the failed fax, faxrunqd was hung.  I had to kill it to get it to start
processing the queue again.  Next failed fax, same thing.

>> 12/16 08:35:06 r1A   fax_wait_for: string 'AT+FDT'
>> 12/16 08:35:06 r1A    got:[0d][0a]+FHS:00[0d]
>> 12/16 08:35:07 r1A   fax_wait_for: string '+FHS:00'
>> 12/16 08:35:07 r1A  connection hangup: '+FHS:00'
>
>And finally, the modem refuses to properly retransmit the page after
>"ERROR", so there is something definitely wrong in its firmware.
>
>Does it always happen this way? Or was this a "freak incident"?  What
>firmware version do you use?

Actually, it was quite odd.  This was the first attempt at faxing after
installing the new hardware.  I sent the fax, and it failed 5 times in a
row.  I requeued it and it still failed (that was the log file I posted).
I changed the fax number in the JOB file to try sending it to a different
fax machine, and it *worked*.  I then sent a whole bunch of faxes to the
original machine (the one that was failing), and all of them went without
incident.

I don't know what the problem was, but it seems to have worked itself out.
FYI, now that I've got all the pieces in place, mgetty+sendfax, along with
a number of other little add-ons will be replacing a package called
"Faximum" as our production faxing system.  Thanks.
__
Devin Redlich
devin@pctc.com