Re: [hylafax-users] Problems Receiving fax from some fax machines.

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2004.07.29 20:00 Daniel Whimpey wrote:

> I am running Fedora Core 1 and HylaFAX version 4.1.8 on a US Robotics
> 56k
> Flash. I would like to run Class 2.0 if I can

Why?  In HylaFAX 4.1.8 there are just as many features in Class 1 as 
with Class 2.0 and there are much less bugs with HylaFAX's Class 1 than 
with USR's Class 2.0.

> but it is not important.

It is important to use Class 1 with USRs if you want somewhat reliable 
faxing.

> This
> Problem is occurring in both classes and more so on Class 2.0.  Class
> 1 is a
> little more compatible but not perfect.
>
> Here is a log of one of the faxes that fail. But it may not be the
> only
> problem. It's like the modem sometimes tries to answer in data mode
> and then
> other times it just seems to retrain till it dies. Also I have noticed
> when
> I have the speaker of the modem on some fax machines don't respond to
> the
> initial train.

If by "initial train" you mean the receiver's first iteration of the 
NSF/CSI/DIS signals and if the sender is sending/listening for the 
ANSam signal (V.34-Fax/V.8 hanshaking) then this will happen.  It's 
nothing to worry about unless it causes a problem.

> Jul 30 10:45:39.43: [ 9121]: SESSION BEGIN 000000132 61031300361829
> Jul 30 10:45:39.43: [ 9121]: HylaFAX (tm) Version 4.1.8
> Jul 30 10:45:39.43: [ 9121]: <-- [22:AT+FCLASS=1&H1&I0&R2A\r]

You don't seem to be using the default configuration prototype file.  
Did you run faxaddmodem and modify the result?   Did faxaddmodem pick 
the config/usr-xon file as a prototype?

> Jul 30 10:45:44.74: [ 9121]: --> [7:CONNECT]
> Jul 30 10:45:44.74: [ 9121]: ANSWER: FAX CONNECTION  DEVICE
> '/dev/ttyS0'
> Jul 30 10:45:44.74: [ 9121]: RECV FAX: begin
> Jul 30 10:45:44.79: [ 9121]: --> [7:CONNECT]
> Jul 30 10:45:46.72: [ 9121]: --> [2:OK]
> Jul 30 10:45:46.72: [ 9121]: <-- [9:AT+FRH=3\r]
> Jul 30 10:45:47.38: [ 9121]: --> [7:CONNECT]
> Jul 30 10:45:48.61: [ 9121]: --> [2:OK]
> Jul 30 10:45:48.61: [ 9121]: REMOTE TSI "61 2 97924750"
> Jul 30 10:45:48.61: [ 9121]: <-- [9:AT+FRH=3\r]
> Jul 30 10:45:48.64: [ 9121]: --> [7:CONNECT]
> Jul 30 10:45:48.88: [ 9121]: --> [2:OK]
> Jul 30 10:45:48.88: [ 9121]: REMOTE wants 12000 bit/s
> Jul 30 10:45:48.88: [ 9121]: REMOTE wants page width 1728 pixels in
> 215 mm
> Jul 30 10:45:48.88: [ 9121]: REMOTE wants unlimited page length
> Jul 30 10:45:48.88: [ 9121]: REMOTE wants 3.85 line/mm
> Jul 30 10:45:48.88: [ 9121]: REMOTE wants 2-D MR
> Jul 30 10:45:48.88: [ 9121]: RECV training at v.17 12000 bit/s
> Jul 30 10:45:48.88: [ 9121]: <-- [11:AT+FRM=121\r]
> Jul 30 10:45:50.59: [ 9121]: --> [7:CONNECT]
> Jul 30 10:45:52.97: [ 9121]: --> [10:NO CARRIER]
> Jul 30 10:45:52.97: [ 9121]: MODEM No carrier
> Jul 30 10:45:52.97: [ 9121]: RECV: TCF 2269 bytes, 1% non-zero, 2228
> zero-run
> Jul 30 10:46:22.97: [ 9121]: MODEM <Empty line>
> Jul 30 10:46:22.97: [ 9121]: DELAY 75 ms
> Jul 30 10:46:23.05: [ 9121]: TRAINING succeeded
> Jul 30 10:46:23.05: [ 9121]: <-- [9:AT+FTH=3\r]
> Jul 30 10:46:23.26: [ 9121]: --> [7:CONNECT]
> Jul 30 10:46:24.43: [ 9121]: --> [2:OK]
> Jul 30 10:46:24.43: [ 9121]: <-- [11:AT+FRM=122\r]
> Jul 30 10:46:31.45: [ 9121]: --> [2:OK]

"OK" is not an appropriate response to the AT+FRM=122 command.  It 
should respond with CONNECT, ERROR, or +FCERROR.  In any case, this 
"OK" is now going to mess up HylaFAX, since it is unexpected.  I think 
that HylaFAX 4.2.0 will handle this error better than 4.1.8 will...

In any case, the USR modem screwed up (not surprisingly), so HylaFAX 
can't do much about that.  But, if you revert to the default config 
file and try 4.2.0 you're at least going to start from something that 
has worked for others and contains all of the fixes made by others.

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*