Re: Hylafax 6.0 No response to PPS repeated 3 times Ubuntu Jaunty.

Sean Murdock wrote:

> Nov 23 14:32:28.69: [26147]: SEND send PPS (partial page signal)
> Nov 23 14:32:28.69: [26147]: SEND send MPS (more pages, same document)
> Nov 23 14:32:28.69: [26147]: <-- [9:AT+FRH=3\r]
> Nov 23 14:32:29.17: [26147]: --> [10:NO CARRIER]
> Nov 23 14:32:29.17: [26147]: MODEM No carrier
> Nov 23 14:32:29.17: [26147]: <-- [9:AT+FTH=3\r]
> Nov 23 14:32:29.37: [26147]: --> [7:CONNECT]
> Nov 23 14:32:29.37: [26147]: <-- data [7]
> Nov 23 14:32:29.37: [26147]: <-- data [2]
> Nov 23 14:32:30.65: [26147]: --> [2:OK]
> Nov 23 14:32:30.65: [26147]: SEND send PPS (partial page signal)
> Nov 23 14:32:30.65: [26147]: SEND send MPS (more pages, same document)
> Nov 23 14:32:30.65: [26147]: <-- [9:AT+FRH=3\r]
> Nov 23 14:32:31.21: [26147]: --> [10:NO CARRIER]
> Nov 23 14:32:31.21: [26147]: MODEM No carrier
> Nov 23 14:32:31.21: [26147]: <-- [9:AT+FTH=3\r]
> Nov 23 14:32:31.41: [26147]: --> [7:CONNECT]
> Nov 23 14:32:31.41: [26147]: <-- data [7]
> Nov 23 14:32:31.41: [26147]: <-- data [2]
> Nov 23 14:32:32.69: [26147]: --> [2:OK]
> Nov 23 14:32:32.69: [26147]: SEND send PPS (partial page signal)
> Nov 23 14:32:32.69: [26147]: SEND send MPS (more pages, same document)
> Nov 23 14:32:32.69: [26147]: <-- [9:AT+FRH=3\r]
> Nov 23 14:32:33.17: [26147]: --> [10:NO CARRIER]

You'll get a different behavior with HylaFAX+ 5.3.0.  I'm not entirely 
sure of how many Class 1 protocol modifications were ported from 
HylaFAX+ to hylafax.org code between 4.4.4 and 6.0.x, so I'm not sure if 
6.0.0 will or won't give you anything different.  Hopefully it would.

Whether or not you could actually get the fax through with HylaFAX+ 
5.3.0, however, is uncertain without testing.

The repeated AT+FRH=3 followed immediately by NO CARRIER is an 
indication that there is some kind of carrier (or possibly just some 
kind of noise) on the line, but that it is *not* the expected V.21 HDLC.

So something is wrong - maybe there is another fax machine sending a fax 
on the same line at the same time?

The only possible way for HylaFAX to recover at this point is to 
continue to repeat AT+FRH=3 in hopes that eventually a V.21 HDLC carrier 
is detected so that a re-sync can occur... repeating at least until NO 
CARRIER is received like this so many times that a timeout expires.  
Alternatively, AT+FRS=9 could be used before then retransmitting 
PPS-MPS... and this approach may have a different outcome than the 
AT+FRH=3 looping.

In sending I think that the latter approach is probably the 
most-appropriate, but since there is some sort of carrier on the line it 
likely is a lost cause anyway.  Most likely something is wrong beyond 
HylaFAX's control.

Thanks,

Lee.


____________________ HylaFAX(tm) Developers Mailing List ____________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe [email protected] < /dev/null