Re: [hylafax-users] Problem Ring detected without successful handshake

[Lee Howard <faxguy@deanox.com>]

At 06:39 PM 4/17/01 -0500, Scott Rasco wrote:
>Running Hylafax 4.1 Beta 3-1 / Libtiff 3.5.5-2 on RedHat 6.2
>
>Problem with “Ring detected without successful handshake” for some incoming
>faxes.  I am using an Intel 144/144i internal faxmodem set for class 1. As
>you can see, the faxaddmodem script recognizes my modem as a 400e, and seems
>to work with most faxes.  I did have a problem with some incoming faxes
>where I would get a MaxConsecutiveBadLines errors, but by setting it to ‘0’
>seems to have covered that problem.  Can you provide any suggestions or
>comments?

>Sample Log file as follows:
>
>Apr 11 14:38:55.26: [  652]: SESSION BEGIN 00000323 19726416295
>Apr 11 14:38:55.26: [  652]: <-- [13:AT+FCLASS=1A\r]
>Apr 11 14:39:01.04: [  652]: --> [7:CONNECT]
>Apr 11 14:39:01.04: [  652]: ANSWER: FAX CONNECTION
>Apr 11 14:39:01.05: [  652]: RECV FAX: begin
>Apr 11 14:39:01.06: [  652]: <-- data [23]
>Apr 11 14:39:01.06: [  652]: <-- data [2]
>Apr 11 14:39:02.61: [  652]: --> [7:CONNECT]
>Apr 11 14:39:02.61: [  652]: <-- data [10]
>Apr 11 14:39:02.62: [  652]: <-- data [2]
>Apr 11 14:39:03.03: [  652]: --> [2:OK]
>Apr 11 14:39:03.03: [  652]: <-- [9:AT+FRH=3\r]
>Apr 11 14:39:06.13: [  652]: --> [0:]
>Apr 11 14:39:06.13: [  652]: MODEM <Empty line>
>Apr 11 14:39:06.14: [  652]: <-- data [1]
>Apr 11 14:39:06.33: [  652]: MODEM <Timeout>

3.1 seconds between +FRH=3 and a null response... Ahem.  I'm very familiar
with this problem, and I don't know how to resolve it, unfortunately.  I
*can* say that you're not alone with this.  At the moment, the best guess
that I can give you is that you're looking at a modem firmware problem.
Interestingly, this firmware problem spans makes and models - I can get
this to reaccur on USR modems with one particular fax sender.

Essentially what is happening is that the modem is sending +FRH=3 (forgive
me for not looking this up to check, but I think that it means that the
modem's ready to receive data from the remote) and if there is a carrier,
the modem should respond with CONNECT, and if not, the modem should respond
with ERROR.  I don't think that the modem is requiring any response from
the remote on this other than a carrier signal, necessarily.  But, as you
can see, instead of responding with CONNECT or ERROR the modem response
times out at 3.1 seconds (very consistent timeout period throughout many
modems) and you get a null response back... and HylaFAX tries it over
again.  Unfortunately, HylaFAX tries it over again at consistent intervals,
but I think the problem is hardware related.

I think it's hardware related because I can use the same modem with the
same remote system (when I can get 100% failure) with different fax
software, and the problem is the same.

Try a different modem.

Lee.

>Apr 11 14:39:06.33: [  652]: DELAY 1500 ms
>Apr 11 14:39:07.83: [  652]: <-- [9:AT+FTH=3\r]
>Apr 11 14:39:07.83: [  652]: --> [10:NO CARRIER]
>Apr 11 14:39:07.84: [  652]: DELAY 1500 ms
>Apr 11 14:39:09.33: [  652]: <-- [9:AT+FTH=3\r]
>Apr 11 14:39:09.33: [  652]: --> [7:CONNECT]
>Apr 11 14:39:09.34: [  652]: <-- data [23]
>Apr 11 14:39:09.34: [  652]: <-- data [2]
>Apr 11 14:39:10.35: [  652]: --> [7:CONNECT]
>Apr 11 14:39:10.35: [  652]: <-- data [10]
>Apr 11 14:39:10.36: [  652]: <-- data [2]
>Apr 11 14:39:10.78: [  652]: --> [2:OK]
>Apr 11 14:39:10.78: [  652]: <-- [9:AT+FRH=3\r]
>Apr 11 14:39:13.88: [  652]: --> [0:]
>Apr 11 14:39:13.88: [  652]: MODEM <Empty line>
>Apr 11 14:39:13.89: [  652]: <-- data [1]
>Apr 11 14:39:14.08: [  652]: MODEM <Timeout>
>Apr 11 14:39:14.08: [  652]: RECV FAX: No answer (T.30 T1 timeout)
>Apr 11 14:39:14.09: [  652]: RECV FAX: end
>Apr 11 14:39:14.09: [  652]: <-- [14:ATH+FCLASS=0A\r]
>Apr 11 14:39:14.75: [  652]: --> [10:NO CARRIER]
>Apr 11 14:39:14.76: [  652]: ANSWER: Ring detected without successful
>handshake
>Apr 11 14:39:14.76: [  652]: SESSION END




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