Re: [hylafax-users] various receive errors with hylafax 4.2.0

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2004.12.03 14:00 marthter wrote:

> The system is the same as described earlier in this thread:
> Red Hat Linux release 9 (Linux 2.4.20-8)
> hylafax-4.2.0 from .tar.gz plus last patch from 
> http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=543
> ati0 TP560 Data/Fax/Voice 56K Modem
>
> Receiving from a certain sender, I had repeated problems today (6 
> attempts, ending up with 3 different error results).
>
> RSPREC error/got DCN
> No answer (T.30 T1 timeout)  (how can it complain about no answer 
> when this is on the receiving side!?)
> RSPREC error/got DCN
> T.30 T2 timeout, expected page not received
> No answer (T.30 T1 timeout)
> No answer (T.30 T1 timeout)
>
> In the 4th one, the one that got the furthest, it e-mailed the PDF, 
> but it was zero size.  I didn't get a chance to look in received 
> directory to see if the tiff was also zero size, though that seems 
> likely given the "begin page" and "end page" were only 2/100 of a 
> second apart.
>
> Lee, can you do your babelfish magic from faxish to english?  Is this 
> noisy lines or something else I might have more control over?

> Dec 03 15:33:52.80: [ 3455]: SESSION BEGIN 000000563 14164252922
> Dec 03 15:33:52.80: [ 3455]: HylaFAX (tm) Version 4.2.0
> Dec 03 15:33:52.84: [ 3455]: <-- [4:ATA\r]
> Dec 03 15:34:00.25: [ 3455]: --> [7:CONNECT]
> Dec 03 15:34:00.26: [ 3455]: ANSWER: FAX CONNECTION  DEVICE
> '/dev/ttyS1'
> Dec 03 15:34:00.27: [ 3455]: RECV FAX: begin
> Dec 03 15:34:00.39: [ 3455]: <-- data [32]
> Dec 03 15:34:00.39: [ 3455]: <-- data [2]
> Dec 03 15:34:00.42: [ 3455]: --> [7:CONNECT]
> Dec 03 15:34:00.42: [ 3455]: <-- data [23]
> Dec 03 15:34:00.42: [ 3455]: <-- data [2]
> Dec 03 15:34:00.45: [ 3455]: --> [7:CONNECT]
> Dec 03 15:34:00.45: [ 3455]: <-- data [10]
> Dec 03 15:34:00.45: [ 3455]: <-- data [2]
> Dec 03 15:34:03.00: [ 3455]: --> [0:]
> Dec 03 15:34:03.00: [ 3455]: MODEM <Empty line>

Notice that's still 2550 ms from the data transmission to the timeout.  
Are you sure the patch was applied properly?  It should be 7550 ms 
before it times out.

> Dec 03 15:39:46.15: [ 3455]: <-- [9:AT+FTH=3\r]
> Dec 03 15:39:46.15: [ 3455]: --> [7:CONNECT]
> Dec 03 15:39:46.15: [ 3455]: <-- data [32]
> Dec 03 15:39:46.15: [ 3455]: <-- data [2]
> Dec 03 15:39:46.19: [ 3455]: --> [7:CONNECT]
> Dec 03 15:39:46.19: [ 3455]: <-- data [23]
> Dec 03 15:39:46.19: [ 3455]: <-- data [2]
> Dec 03 15:39:46.22: [ 3455]: --> [7:CONNECT]
> Dec 03 15:39:46.22: [ 3455]: <-- data [10]
> Dec 03 15:39:46.22: [ 3455]: <-- data [2]
> Dec 03 15:39:48.71: [ 3455]: --> [2:OK]
> Dec 03 15:39:48.71: [ 3455]: <-- [9:AT+FRH=3\r]
> Dec 03 15:39:49.56: [ 3455]: --> [7:CONNECT]
> Dec 03 15:39:51.46: [ 3455]: --> [2:OK]

You see, in this case it worked because the OK came before 2550 ms 
(2490 ms).

Lee.

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*