Re: [hylafax-users] Failed to detect high-speed data carrier

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Ismail OZATAY wrote:
> Feb 04 13:44:48.44: [ 2069]: TRAINING succeeded
> Feb 04 13:44:48.45: [ 2069]: <-- [9:AT+FTH=3\r]
> Feb 04 13:44:49.32: [ 2069]: --> [7:CONNECT]
> Feb 04 13:44:49.32: [ 2069]: <-- data [3]
> Feb 04 13:44:49.32: [ 2069]: <-- data [2]
> Feb 04 13:44:49.64: [ 2069]: --> [2:OK]
> Feb 04 13:44:49.64: [ 2069]: <-- [10:AT+FRM=96\r]
> Feb 04 13:44:52.41: [ 2069]: --> [7:CONNECT]
> Feb 04 13:44:53.05: [ 2069]: RECV assumed RCP frame with block end
> Feb 04 13:44:53.05: [ 2069]: --> [10:NO CARRIER]
> Feb 04 13:44:53.05: [ 2069]: <-- [9:AT+FRH=3\r]
> Feb 04 13:44:53.20: [ 2069]: --> [7:CONNECT]
> Feb 04 13:44:54.94: [ 2069]: --> [2:OK]
> Feb 04 13:44:54.94: [ 2069]: RECV recv TSI (sender id)
> Feb 04 13:44:54.94: [ 2069]: REMOTE TSI "985966466"
> Feb 04 13:44:54.94: [ 2069]: RECV recv TSI (sender id)

It seems like the sender did not get your CFR signal.

> Feb 04 13:44:54.94: [ 2069]: <-- [9:AT+FRH=3\r]
> Feb 04 13:44:54.95: [ 2069]: --> [7:CONNECT]
> Feb 04 13:44:55.32: [ 2069]: --> [2:OK]
> Feb 04 13:44:55.32: [ 2069]: REMOTE wants 9600 bit/s
> Feb 04 13:44:55.32: [ 2069]: REMOTE wants A4 page width (215 mm)
> Feb 04 13:44:55.32: [ 2069]: REMOTE wants unlimited page length
> Feb 04 13:44:55.32: [ 2069]: REMOTE wants 3.85 line/mm
> Feb 04 13:44:55.32: [ 2069]: REMOTE wants 2-D MMR
> Feb 04 13:44:55.32: [ 2069]: REMOTE wants T.30 Annex A, 256-byte ECM
> Feb 04 13:44:55.32: [ 2069]: RECV recv DCS (command signal)
> Feb 04 13:44:55.32: [ 2069]: RECV training at v.29 9600 bit/s
> Feb 04 13:44:55.32: [ 2069]: <-- [10:AT+FRM=96\r]
> Feb 04 13:44:55.49: [ 2069]: --> [8:+FCERROR]
> Feb 04 13:44:55.49: [ 2069]: <-- [10:AT+FRM=96\r]
> Feb 04 13:44:56.01: [ 2069]: --> [7:CONNECT]
> Feb 04 13:44:56.01: [ 2069]: RECV: TCF 0 bytes, 0% non-zero, 0 zero-run
> Feb 04 13:44:56.01: [ 2069]: RECV: reject TCF (zero run too short, min 
> 1200)
> Feb 04 13:44:56.01: [ 2069]: --> [10:NO CARRIER]

... and then you have this kind of thing play out a couple of times.  My 
guess is that the modem is misbehaving here (the +FCERROR seems to 
indicate that the previous OK came too soon before the sender's DCS 
carrier dropped - followed by a CONNECT that seems to be erronious).

So the modem firmware could be buggy or the line audio quality could be bad.

You could possibly try:

 Class1TCFRecvHackCmd: AT+FRS=1

... but I don't have much hope for that solving 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*