Re: [hylafax-users] RECV FAX: Failed to properly detect high-spee d data carrier.

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Donald, Adam wrote:

> I am also using MT5634ZPX-PCI-V.92 Internal Modem(s), and getting similar
> errors.
>
> Hans, are you using firmware v 1.32i?
>
> Lee, I see that you mention a problem with v.17 in this thread.
> You may recall from a previous thread, "Re: [hylafax-users] Is DID required
> for this application?", that I was having trouble with v.17 with the MT5634
> as the sender.  While this issue that Hans has brought up deals with
> receiving, do you think that it is related to the v.17 issue that you
> mentioned in that previous thread?
>
> FC 3
> Hylafax 4.2.1
> LT V.92 1.0 MT5634ZPX-PCI-U Internal Data/Fax/Voice Modem Version 1.32i
> ...
> Mar 03 15:51:28.27: [16747]: RECV send PPR (partial page request)
> Mar 03 15:51:28.27: [16747]: RECV sent fourth PPR
> Mar 03 15:51:28.27: [16747]: <-- [9:AT+FRH=3\r]
> Mar 03 15:51:28.36: [16747]: --> [7:CONNECT]
> Mar 03 15:51:29.54: [16747]: --> [2:OK]
> Mar 03 15:51:29.54: [16747]: RECV recv CTC (continue to correct)
> Mar 03 15:51:29.54: [16747]: <-- [9:AT+FRS=7\r]
> Mar 03 15:51:29.71: [16747]: --> [2:OK]
> Mar 03 15:51:29.71: [16747]: <-- [9:AT+FTH=3\r]
> Mar 03 15:51:30.68: [16747]: --> [7:CONNECT]
> Mar 03 15:51:30.68: [16747]: <-- data [3]
> Mar 03 15:51:30.68: [16747]: <-- data [2]
> Mar 03 15:51:31.07: [16747]: --> [2:OK]
> Mar 03 15:51:31.07: [16747]: RECV send CTR (confirm continue to correct)
> Mar 03 15:51:31.07: [16747]: <-- [11:AT+FRM=121\r]
> Mar 03 15:51:33.41: [16747]: --> [8:+FCERROR]
> Mar 03 15:51:33.41: [16747]: <-- [11:AT+FRM=121\r]
> Mar 03 15:51:33.63: [16747]: --> [8:+FCERROR]
>  

Adam,

There are many different possible, valid, reasons why this (+FCERROR 
after CTC/CTR) would happen under "normal" circumstances, and I think 
that I commented on them earlier in this thread.

The fact that others are seeing similar logs when using the same modem 
as you may not necessarily be indicative of anything - because it may be 
normal.

That said, it still could be something with the modems themselves.  It 
could also be that HylaFAX could do something better here.  But, really, 
in order to answer those questions, you'd need to be able to reliably 
reproduce this particular error.  So if you can do that, then we can try 
to figure out what the problem may be.  Otherwise, we pretty much have 
to just assume that it's normal.

That said, the presense of CTC/CTR indicates a *really* bad connection.  
And, rather than trying to hunt down the reason for +FCERROR, the first 
thing that I would do would be to try to figure out why the connection 
is so bad.

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*