[hylafax-users] HylaFAX getting stuck on bad transmissions

[Christopher Curtis <ccurtis@aet-usa.com>]

Hello,

I'm trying to troubleshoot some problems with an existing HylaFAX setup
that I'm not terribly familiar with (nor am I a HylaFAX whiz, either).
The website is being cantakerous so apologies beforehand if this is a FAQ
or has been answered before.

First, the system is Linux, kernel 2.2.14, a Slackware variant, and
HylaFAX is version 4.0pl2.  There is a single modem attached to the
system.

Everything is fine until a number of error conditions arise.  One problem
was that a phone number was invalid and the prerecorded error message
began playing before I had finished dialing the number manually.  I don't
know what logfile this session was stored in, however, so I can't provide
any specific tracing information.

The problem that occured this last time HylaFAX hung is this:

Apr 11 19:50:11.71: [26173]: --> [22:+FDIS: 1,5,0,2,1,0,0,0]
Apr 11 19:50:11.82: [26173]: --> [2:OK]
Apr 11 19:50:11.82: [26173]: REMOTE best rate 14400 bit/s
Apr 11 19:50:11.82: [26173]: REMOTE max page width 1728 pixels in 215 mm
Apr 11 19:50:11.82: [26173]: REMOTE max unlimited page length
Apr 11 19:50:11.82: [26173]: REMOTE best vres 7.7 line/mm
Apr 11 19:50:11.82: [26173]: REMOTE best format 2-D MR
Apr 11 19:50:11.82: [26173]: REMOTE best 0 ms/scanline
Apr 11 19:50:11.82: [26173]: USE 14400 bit/s
Apr 11 19:50:11.82: [26173]: USE 0 ms/scanline
Apr 11 19:50:11.82: [26173]: SEND file "docq/doc5871.ps;30"
Apr 11 19:50:11.82: [26173]: USE page width 1728 pixels in 215 mm
Apr 11 19:50:11.82: [26173]: USE unlimited page length
Apr 11 19:50:11.82: [26173]: USE 3.85 line/mm
Apr 11 19:50:11.82: [26173]: USE 1-D MR
Apr 11 19:50:11.82: [26173]: <-- [24:AT+FDIS=0,5,0,2,0,0,0,0\r]
Apr 11 19:50:11.94: [26173]: --> [2:OK]
Apr 11 19:50:11.94: [26173]: <-- [7:AT+FDT\r]
Apr 11 19:50:40.75: [26173]: --> [9:+FHNG: 50]
Apr 11 19:50:40.75: [26173]: REMOTE HANGUP: Unspecified Transmit Phase D
error, including +FPHCTO timeout between data and +FET command (code 50)
Apr 11 19:50:41.32: [26173]: --> [2:OK]
Apr 12 11:53:23.80: [26173]: ABORT: job abort requested
Apr 12 11:53:23.85: [26173]: --> [0:]
Apr 12 11:53:23.85: [26173]: MODEM <Empty line>
Apr 12 11:53:23.90: [26173]: SEND FAILED: Job aborted by user
Apr 12 11:53:23.90: [26173]: <-- [5:ATH0\r]
Apr 12 11:53:24.05: [26173]: --> [2:OK]
Apr 12 11:53:24.07: [26173]: SESSION END

Note the time change before the abort.  This is very unacceptable so I
need to do something quickly.  An interesting thing was that after I
faxrm'd the job, it didn't leave, and no others were being spooled.  I
found that 'faxq' was no longer running, so I typed 'faxq' and things
begin going smoothly again.

So, my questions:

Is this a hardware error, or software error (since faxq died)?  How would
I be able to tell?  My config.ttyS0 is for a 'Rockwell RC288DPi-based
Class 2 modem' but I have no way to verify this is accurate.  I assume it
is, however.

Is there a workaround?  IE, how can I say 'abort any job not completed
within 10 minutes of starting'.  Everything should be using the system
default values.

Here are some trace snippets from other aborted commands:

Mar 24 04:56:11.90: [16337]: <-- [24:AT+FDIS=0,5,0,2,0,0,0,1\r]
Mar 24 04:56:12.02: [16337]: --> [2:OK]
Mar 24 04:56:12.02: [16337]: <-- [7:AT+FDT\r]
Mar 24 04:56:50.25: [16337]: --> [9:+FHNG: 25]
Mar 24 04:56:50.25: [16337]: REMOTE HANGUP: DCS sent 3 times without response (code 25)
Mar 24 04:56:50.83: [16337]: --> [2:OK]
Apr 07 18:19:45.10: [16337]: ABORT: job abort requested


Apr 09 12:29:33.56: [13268]: REMOTE HANGUP: DCS sent 3 times without response (code 25)
Apr 09 12:29:34.14: [13268]: --> [2:OK]
Apr 10 11:57:48.10: [13268]: ABORT: job abort requested


Apr 10 12:00:06.49: [29431]: REMOTE HANGUP: DCS sent 3 times without response (code 25)
Apr 10 12:00:07.07: [29431]: --> [2:OK]
Apr 10 13:02:10.88: [29431]: ABORT: job abort requested


Apr 10 21:09:22.99: [16269]: REMOTE HANGUP: DCS sent 3 times without response (code 25)
Apr 10 21:09:23.57: [16269]: --> [2:OK]
Apr 11 10:26:57.34: [16269]: ABORT: job abort requested


Apr 11 14:53:55.83: [ 4957]: REMOTE HANGUP: DCS sent 3 times without response (code 25)
Apr 11 14:53:56.41: [ 4957]: --> [2:OK]
Apr 11 16:04:25.70: [ 4957]: ABORT: job abort requested


Apr 11 16:29:13.01: [11779]: REMOTE HANGUP: Unspecified Transmit Phase D
error, including +FPHCTO timeout between data and +FET command (code 50)
Apr 11 16:29:13.58: [11779]: --> [2:OK]
Apr 11 16:55:43.56: [11779]: ABORT: job abort requested


Apr 11 17:03:06.04: [14230]: REMOTE HANGUP: DCS sent 3 times without response (code 25)
Apr 11 17:03:06.62: [14230]: --> [2:OK]
Apr 11 17:16:30.36: [14230]: ABORT: job abort requested


Apr 11 19:50:40.75: [26173]: REMOTE HANGUP: Unspecified Transmit Phase D
error, including +FPHCTO timeout between data and +FET command (code 50)
Apr 11 19:50:41.32: [26173]: --> [2:OK]
Apr 12 11:53:23.80: [26173]: ABORT: job abort requested


Apr 12 12:11:36.63: [ 1998]: REMOTE HANGUP: DCS sent 3 times without response (code 25)
Apr 12 12:11:37.21: [ 1998]: --> [2:OK]
Apr 12 12:29:57.50: [ 1998]: ABORT: job abort requested


These errors are show up more often as the service is getting more widely
used, and thus making things worse for more people more often.  :(

Any help is appreciated.

Thanks,
Chris

PS - Please Cc: me since I'm not subscribed to the mailing list.



____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null