Re: [hylafax-users] COMREC invalid response received (expected PPS)

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Rafal Jankowski wrote:

> sie 12 14:41:11.04: [ 4277]: <-- [11:AT+FRM=146\r]
> sie 12 14:41:11.73: [ 4277]: --> [7:CONNECT]
> sie 12 14:41:12.08: [ 4277]: RECV received frame number 0
> sie 12 14:41:12.24: [ 4277]: RECV received frame number 1
> sie 12 14:41:13.02: [ 4277]: RECV received frame number 2
>  
....

> sie 12 14:41:32.45: [ 4277]: RECV received frame number 113
> sie 12 14:41:32.45: [ 4277]: RECV received frame number 114
> sie 12 14:41:32.45: [ 4277]: RECV received RCP frame
> sie 12 14:41:32.71: [ 4277]: --> [10:NO CARRIER]
>  

This is a perfect example of what you *should* see when receiving.

> sie 12 14:41:35.51: [ 4277]: <-- [11:AT+FRM=146\r]
> sie 12 14:41:36.19: [ 4277]: --> [7:CONNECT]
> sie 12 14:41:36.48: [ 4277]: HDLC frame not byte-oriented.  Trailing byte: 0
> sie 12 14:41:36.64: [ 4277]: HDLC frame not byte-oriented.  Trailing byte: 0xf8
> ....
> sie 12 14:41:59.18: [ 4277]: HDLC frame not byte-oriented.  Trailing byte: 0xf0
> sie 12 14:41:59.33: [ 4277]: Bad HDLC terminating flag received.
> sie 12 14:41:59.33: [ 4277]: HDLC frame not byte-oriented.  Trailing byte: 0
> sie 12 14:41:59.52: [ 4277]: RECV assumed RCP frame with block end
> sie 12 14:41:59.52: [ 4277]: --> [10:NO CARRIER]
>  

This is a perfect example of what you should *not* see when receiving.

I'd need to see your logging at a higher setting (to show the actual 
modem data) and try to parse through it to know for certain, but this is 
generally and indication that the sender's modulator, the receiver's 
modulator, or both are not in a usable state.  Generally they "come out 
of it" after a couple of attempts, but in this case it did not happen.  
My bet is on the USR modem being the culprit here.

> sie 12 14:42:44.62: [ 4277]: RECV recv CTC (continue to correct)
> sie 12 14:42:44.62: [ 4277]: <-- [9:AT+FRS=7\r]
> sie 12 14:42:44.78: [ 4277]: --> [2:OK]
> sie 12 14:42:44.78: [ 4277]: <-- [9:AT+FTH=3\r]
> sie 12 14:42:44.90: [ 4277]: --> [7:CONNECT]
> sie 12 14:42:46.11: [ 4277]: --> [2:OK]
> sie 12 14:42:46.11: [ 4277]: RECV send CTR (confirm continue to correct)
> sie 12 14:42:46.11: [ 4277]: <-- [11:AT+FRM=121\r]
> sie 12 14:42:47.99: [ 4277]: --> [7:CONNECT]
>  
....

> sie 12 14:42:50.55: [ 4277]: RECV recv DCN (disconnect)
>  

It's too bad the sender didn't drop down to V.29 before giving up (DCN) 
because that probably would have recovered things.

You *may* be able to work around your USR problems by disabling V.17.  
You do that with Class1RMQueryCmd.  Search the archives for examples.

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*