HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] Some users don't get all scan lines



Lee Howard wrote:

> On 2003.08.21 16:12 Michael Evans wrote:
>
>> Hi,
>>
>> I installed HylaFAX on a SuSE 7.3 box, with a Zoom V.90 Model 2920
>
> ....
>
>> Aug 21 11:03:09.50: [15606]: SEND training at v.17 14400 bit/s
>> Aug 21 11:03:09.50: [15606]: <-- [9:AT+FTH=3\r]
>> Aug 21 11:03:10.36: [15606]: --> [7:CONNECT]
>> Aug 21 11:03:10.36: [15606]: <-- data [23]
>> Aug 21 11:03:10.36: [15606]: <-- data [2]
>> Aug 21 11:03:10.37: [15606]: --> [7:CONNECT]
>> Aug 21 11:03:10.37: [15606]: <-- data [6]
>> Aug 21 11:03:10.37: [15606]: <-- data [2]
>> Aug 21 11:03:11.46: [15606]: --> [2:OK]
>> Aug 21 11:03:11.46: [15606]: DELAY 75 ms
>> Aug 21 11:03:11.54: [15606]: <-- [11:AT+FTM=145\r]
>> Aug 21 11:03:11.55: [15606]: --> [7:CONNECT]
>> Aug 21 11:03:11.55: [15606]: <-- data [1024]
>> Aug 21 11:03:11.55: [15606]: <-- data [1024]
>> Aug 21 11:03:11.55: [15606]: <-- data [652]
>> Aug 21 11:03:11.55: [15606]: <-- data [2]
>> Aug 21 11:03:14.68: [15606]: --> [2:OK]
>> Aug 21 11:03:14.68: [15606]: <-- [9:AT+FRH=3\r]
>> Aug 21 11:03:14.80: [15606]: --> [7:CONNECT]
>> Aug 21 11:03:16.07: [15606]: --> [2:OK]
>> Aug 21 11:03:16.07: [15606]: DELAY 1500 ms
>> Aug 21 11:03:17.57: [15606]: SEND training at v.17 12000 bit/s
>
>
> Class1TMConnectDelay: 400 will help this.
>
> See: http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=419
>
>> - faxaddmodem doesn't specifically recognize the Zoom 2920, so it 
>> uses the generic "class1" config file. However, I noticed in 4.1.7's 
>> /config directory several "lucent" files, one of which lists the Zoom 
>> 2920 model. (Per Zoom's docs, it uses the "Lucent Venus" chipset.) I 
>> copied / overwrote those entries in the "lucent" config file to the 
>> active config file.
>
>
> Good.  The lucent config is what you should be using.  The problem 
> with faxaddmodem is a long-going awk battle relating to how we should 
> or shouldn't handle conflicting configs.  We thought we improved it 
> again, but ended up just breaking it.
>
> Lee.

Lee,

Thanks for the pointer to the patch. I patched the source files from 
4.1.7, then re-did ./configure, make, and make install, as well as 
faxsetup. I also checked the modem config file to make sure it had the 
Class1TMConnectDelay: 400 parameter, which it did.

However, this didn't fix the problem. The faxes sent to the HP machine 
are just as chopped up as before, with the same RTN errors recorded in 
the log file. I tried increasing the Class1TMConnectDelay from 400 to 
1000, with no effect. I also tried, once again, changing the flow 
control scheme from rtscts to xonxoff, but again with no effect. The 
faxes sent to the Brother machine are perfect, but those sent to the HP 
machine fail every time.

I would throw up my hands and blame it on a crummy phone line, except 
for the fact that the Brother machine itself can send a fax to the HP 
flawlessly. (I've tried hooking up the Brother's phone line to the modem 
in the Hylafax machine, but that didn't help either.)

So somehow, the Brother fax machine is able to figure out something 
about proper communication with the HP machine that the Hylafax / Zoom 
modem combination, as far as any configuration I can come up with, 
cannot.  It's not that I intend to send zillions of faxes to the HP 
machine, it's just that we have no control over what machinery our 
regular fax recipients have, and if the HP has this problem, what other 
types of machines do as well?

Is it time to yank the Zoom 2920 modem and get a Multitech, or is there 
something else I can try?

Thanks,

Michael Evans



____________________ 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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*




Project hosted by iFAX Solutions