Re: [hylafax-users] Frequent transmission breakdowns HF4.1 und HF4.1b3

[Lee Howard <faxguy@deanox.com>]

At 11:49 PM 7/17/01 +0200, Peter Bauer wrote:
....
>Any idea what I can look for to trace back the problem? Here is a
>typical transmisson log:
....
>Jul 17 22:47:53.37: [ 5961]: SEND end page
>Jul 17 22:48:29.07: [ 5961]: --> [2:OK]
>Jul 17 22:48:29.07: [ 5961]: DELAY 95 ms

This delay is now known as Class1SendEOPDelay in CVS, and according to T.30
should only be 75 ms, but for empirical experience it has been hard-coded
to 95 ms in 4.1-release.  In my experience, this is still too little, and
Class1SendEOPDelay has a default in CVS of 200 ms.

>Jul 17 22:48:29.17: [ 5961]: SEND send EOP (no more pages or documents)
>Jul 17 22:48:29.17: [ 5961]: <-- [9:AT+FTH=3\r]
>Jul 17 22:48:29.20: [ 5961]: --> [7:CONNECT]
>Jul 17 22:48:29.20: [ 5961]: <-- data [3]
>Jul 17 22:48:29.20: [ 5961]: <-- data [2]
>Jul 17 22:48:30.47: [ 5961]: --> [2:OK]
>Jul 17 22:48:30.47: [ 5961]: <-- [9:AT+FRH=3\r]
>Jul 17 22:48:33.58: [ 5961]: --> [0:]
>Jul 17 22:48:33.58: [ 5961]: MODEM <Empty line>

Exactly the behavior I experienced before Class1SendEOPDelay, execpt yours
seems to be much more tragic than mine, since in my case the retries
succeeded.  I'd recommend trying CVS, or applying the last patch on:

http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=152

....
>Even stranger: since the image is quite complex, it looks for me as if the
>"SEND send EOP" is being transmitted too soon. There must be more data to
>send

I doubt it.

....
>Also strange: when I fax another document to myself, the fax machine
>displays an transmission error, but does not hang up. Then, hylafax
>resends the page, fails again, and the cycle starts again (up to 
>three times).

Could you send the log to this, please?

Lee.



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