Re: [hylafax-users] Problem from one specific location to hylafax

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Ben Hodgens wrote:
> Jun 07 15:24:44.57: [ 1118]: SESSION BEGIN 000386389 XXXXXXXXXX
> Jun 07 15:24:44.57: [ 1118]: HylaFAX (tm) Version 4.3.2
> Jun 07 15:24:44.57: [ 1118]: <-- [4:ATA\r]
> Jun 07 15:24:50.65: [ 1118]: --> [7:CONNECT]
> Jun 07 15:24:50.65: [ 1118]: ANSWER: FAX CONNECTION DEVICE '/dev/cuaU9'
> Jun 07 15:24:50.65: [ 1118]: RECV FAX: begin
> Jun 07 15:24:50.66: [ 1118]: <-- data [32]
> Jun 07 15:24:50.66: [ 1118]: <-- data [2]
> Jun 07 15:24:50.68: [ 1118]: --> [7:CONNECT]
> Jun 07 15:24:50.68: [ 1118]: <-- data [23]
> Jun 07 15:24:50.68: [ 1118]: <-- data [2]
> Jun 07 15:24:50.71: [ 1118]: --> [7:CONNECT]
> Jun 07 15:24:50.71: [ 1118]: <-- data [13]
> Jun 07 15:24:50.71: [ 1118]: <-- data [2]
> Jun 07 15:24:52.91: [ 1118]: --> [2:OK]
> Jun 07 15:24:52.91: [ 1118]: <-- [9:AT+FRH=3\r]
> Jun 07 15:24:53.71: [ 1118]: --> [7:CONNECT]
> Jun 07 15:24:55.16: [ 1118]: --> [2:OK]
> Jun 07 15:24:55.16: [ 1118]: REMOTE wants 14400 bit/s
> Jun 07 15:24:55.16: [ 1118]: REMOTE wants A4 page width (215 mm)
> Jun 07 15:24:55.16: [ 1118]: REMOTE wants unlimited page length
> Jun 07 15:24:55.16: [ 1118]: REMOTE wants 7.7 line/mm
> Jun 07 15:24:55.16: [ 1118]: REMOTE wants 2-D MMR
> Jun 07 15:24:55.16: [ 1118]: REMOTE wants T.30 Annex A, 256-byte ECM
> Jun 07 15:24:55.16: [ 1118]: RECV training at v.17 14400 bit/s
> Jun 07 15:24:55.16: [ 1118]: <-- [11:AT+FRM=145\r]
> Jun 07 15:24:55.22: [ 1118]: --> [8:+FCERROR]
> Jun 07 15:24:55.22: [ 1118]: <-- [11:AT+FRM=145\r]
> Jun 07 15:24:55.29: [ 1118]: --> [8:+FCERROR]
> Jun 07 15:24:55.29: [ 1118]: <-- [9:AT+FRH=3\r]
> Jun 07 15:24:55.75: [ 1118]: --> [7:CONNECT]
> Jun 07 15:24:58.39: [ 1118]: --> [10:NO CARRIER]
> Jun 07 15:24:58.39: [ 1118]: MODEM No carrier
>   

This is in part a problem with the modem firmware.  What's probably 
happening in the modem firmware is that the OK following the previous 
AT+FRH=3 comes *before* the V.21 HDLC carrier drops.  And in a situation 
like this where the sender may leave the V.21 carrier going for some 
time after the last HDLC frame is transmitted you'll find that your 
modem will respond with +FCERROR to the AT+FRM=n attempt to receive the 
TCF signal.

A long time ago I developed a workaround for this kind of modem 
oversight (the modem really shouldn't report OK after AT+FRH=3 and an 
HDLC frame was received with the "last frame" indication).  In your 
modem config file put:

*Class1TCFRecvHackCmd: AT+FRS=1*

> Jun 07 15:24:58.39: [ 1118]: <-- [9:AT+FRS=7\r]
> Jun 07 15:24:58.47: [ 1118]: --> [2:OK]
> Jun 07 15:24:58.47: [ 1118]: <-- [9:AT+FTH=3\r]
> Jun 07 15:24:59.34: [ 1118]: --> [7:CONNECT]
> Jun 07 15:24:59.34: [ 1118]: <-- data [3]
> Jun 07 15:24:59.34: [ 1118]: <-- data [2]
> Jun 07 15:24:59.66: [ 1118]: --> [2:OK]
> Jun 07 15:24:59.66: [ 1118]: RECV send CRP (command repeat)
> Jun 07 15:24:59.66: [ 1118]: <-- [9:AT+FRH=3\r]
> Jun 07 15:24:59.95: [ 1118]: --> [7:CONNECT]
> Jun 07 15:25:01.40: [ 1118]: --> [2:OK]
> Jun 07 15:25:01.40: [ 1118]: REMOTE wants 14400 bit/s
> Jun 07 15:25:01.40: [ 1118]: REMOTE wants A4 page width (215 mm)
> Jun 07 15:25:01.40: [ 1118]: REMOTE wants unlimited page length
> Jun 07 15:25:01.40: [ 1118]: REMOTE wants 7.7 line/mm
> Jun 07 15:25:01.40: [ 1118]: REMOTE wants 2-D MMR
> Jun 07 15:25:01.40: [ 1118]: REMOTE wants T.30 Annex A, 256-byte ECM
> Jun 07 15:25:01.40: [ 1118]: RECV training at v.17 14400 bit/s
> Jun 07 15:25:01.40: [ 1118]: <-- [11:AT+FRM=145\r]
> Jun 07 15:25:01.46: [ 1118]: --> [8:+FCERROR]
> Jun 07 15:25:01.46: [ 1118]: <-- [11:AT+FRM=145\r]
> Jun 07 15:25:01.52: [ 1118]: --> [8:+FCERROR]
> Jun 07 15:25:01.52: [ 1118]: <-- [9:AT+FRH=3\r]
> Jun 07 15:25:01.98: [ 1118]: --> [7:CONNECT]
> Jun 07 15:25:04.62: [ 1118]: --> [10:NO CARRIER]
> Jun 07 15:25:04.62: [ 1118]: MODEM No carrier
>   

The problem just repeats itself.  Unfortunately, the sender very blindly 
attempts the same modulation.

> Jun 07 15:25:04.62: [ 1118]: <-- [9:AT+FRS=7\r]
> Jun 07 15:25:04.70: [ 1118]: --> [2:OK]
> Jun 07 15:25:04.70: [ 1118]: <-- [9:AT+FTH=3\r]
> Jun 07 15:25:05.57: [ 1118]: --> [7:CONNECT]
> Jun 07 15:25:05.57: [ 1118]: <-- data [3]
> Jun 07 15:25:05.57: [ 1118]: <-- data [2]
> Jun 07 15:25:05.88: [ 1118]: --> [2:OK]
> Jun 07 15:25:05.88: [ 1118]: RECV send CRP (command repeat)
> Jun 07 15:25:05.88: [ 1118]: <-- [9:AT+FRH=3\r]
> Jun 07 15:25:06.19: [ 1118]: --> [7:CONNECT]
> Jun 07 15:25:07.63: [ 1118]: --> [2:OK]
> Jun 07 15:25:07.63: [ 1118]: REMOTE wants 14400 bit/s
> Jun 07 15:25:07.63: [ 1118]: REMOTE wants A4 page width (215 mm)
> Jun 07 15:25:07.63: [ 1118]: REMOTE wants unlimited page length
> Jun 07 15:25:07.63: [ 1118]: REMOTE wants 7.7 line/mm
> Jun 07 15:25:07.63: [ 1118]: REMOTE wants 2-D MMR
> Jun 07 15:25:07.63: [ 1118]: REMOTE wants T.30 Annex A, 256-byte ECM
> Jun 07 15:25:07.63: [ 1118]: RECV training at v.17 14400 bit/s
> Jun 07 15:25:07.63: [ 1118]: <-- [11:AT+FRM=145\r]
> Jun 07 15:25:07.69: [ 1118]: --> [8:+FCERROR]
> Jun 07 15:25:07.69: [ 1118]: <-- [11:AT+FRM=145\r]
> Jun 07 15:25:07.75: [ 1118]: --> [8:+FCERROR]
> Jun 07 15:25:07.75: [ 1118]: <-- [9:AT+FRH=3\r]
> Jun 07 15:25:08.21: [ 1118]: --> [7:CONNECT]
> Jun 07 15:25:10.85: [ 1118]: --> [10:NO CARRIER]
> Jun 07 15:25:10.85: [ 1118]: MODEM No carrier
> Jun 07 15:25:10.85: [ 1118]: <-- [9:AT+FRS=7\r]
> Jun 07 15:25:10.93: [ 1118]: --> [2:OK]
> Jun 07 15:25:10.93: [ 1118]: <-- [9:AT+FTH=3\r]
> Jun 07 15:25:11.80: [ 1118]: --> [7:CONNECT]
> Jun 07 15:25:11.80: [ 1118]: <-- data [3]
> Jun 07 15:25:11.80: [ 1118]: <-- data [2]
> Jun 07 15:25:12.12: [ 1118]: --> [2:OK]
> Jun 07 15:25:12.12: [ 1118]: RECV send CRP (command repeat)
> Jun 07 15:25:12.12: [ 1118]: <-- [9:AT+FRH=3\r]
> Jun 07 15:25:12.41: [ 1118]: --> [7:CONNECT]
> Jun 07 15:25:13.59: [ 1118]: --> [2:OK]
> Jun 07 15:25:13.59: [ 1118]: RECV FAX: RSPREC error/got DCN
> Jun 07 15:25:13.59: [ 1118]: RECV FAX: end
> Jun 07 15:25:13.59: [ 1118]: SESSION END
>
> Might there be a hylafax setting somewhere I can set (either globally or
> specifically for certain senders) which might help this users' faxes
> through? What might be causing the problem?

Try the "hack" config option I pointed out.  If that doesn't do it, then 
possibly a different modem type won't exhibit the problem.

Thanks,

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*