Re: [hylafax-users] T.30 T2 timeout, expected signal not received

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Mike Warfe wrote:

In your log everything is going fine until...

> May 11 10:22:33.95: [ 3657]: RECV received frame number 20
> May 11 10:22:34.18: [ 3657]: RECV received frame number 21
> May 11 10:22:34.18: [ 3657]: RECV frame FCS check failed
> May 11 10:22:34.18: [ 3657]: HDLC frame not byte-oriented.  Trailing 
> byte: 0
> May 11 10:22:34.19: [ 3657]: Bad HDLC terminating flag received.
> May 11 10:22:34.19: [ 3657]: HDLC frame with bad address field 0x91
> May 11 10:22:34.19: [ 3657]: RECV assumed RCP frame with block end
> May 11 10:22:34.19: [ 3657]: --> [10:NO CARRIER]


... there is an unexpected termination of Phase C at 10:22:34.19.  This 
could have happened for several reasons.  Among the more common reasons 
are issues related to the audio quality and deliberate remote disconnection.

> May 11 10:22:34.19: [ 3657]: <-- [9:AT+FRH=3\r]
> May 11 10:22:38.73: [ 3657]: --> [7:CONNECT]
> May 11 10:22:38.90: [ 3657]: --> [5:ERROR]


This indicates that the sender was still there at 10:22:38.73 making 
some kind of noises, at least, or maybe just the "click" of a hangup.  
(Depending on how the modem works internally the CONNECT may even 
indicate that V.21 HDLC was, indeed, detected.)  However the ERROR 
indicates that either no valid HDLC signal was received before the 
carrier dropped or that the sender's transmission was corrupt somehow.

> May 11 10:22:38.90: [ 3657]: MODEM Command error
> May 11 10:22:38.90: [ 3657]: FCS error
> May 11 10:22:38.90: [ 3657]: DELAY 70 ms
> May 11 10:22:38.97: [ 3657]: <-- [9:AT+FTH=3\r]
> May 11 10:22:39.16: [ 3657]: --> [7:CONNECT]
> May 11 10:22:40.34: [ 3657]: --> [2:OK]
> May 11 10:22:40.34: [ 3657]: RECV send CRP (command repeat)


This is our attempt to tell the sender that we didn't get any valid 
message signal just before.

> May 11 10:22:40.34: [ 3657]: <-- [9:AT+FRH=3\r]
> May 11 10:22:42.67: [ 3657]: --> [10:NO CARRIER]


And this indicates that there is no carrier - the caller has almost 
certainly hung up.

So that's the interpretation of the log.  Hopefully it can help you 
discover what happened.  In most cases this just indicates that the 
sender aborted (like, with the "stop" button on the fax machine).  If it 
wasn't that, then there is some troubleshooting to perform.

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*