Re: flexfax: Phase Errors

[David Woolley <david@djwhome.demon.co.uk>]

I think these error messages should changed to something like:

Phase A:  Whilst connect to remote machine.
Phase B:  Whilst negotiating transmission parameters.
Phase C:  Whilst sending/receiving the image of the page.
Phase D:  Whilst confirming page reception.

as too many people seem to thing that the problem is that a Phase has
happened (even though these are obviously the descriptions in the
standards)!

Note there does seem to be a Hylafax problem in that it has failed to
shut down after the remote machine has abandoned in response to RTN.
However the immediate causes look like a mix of misconfiguration and
faulty lines/modems.

> Feb 24 16:32:41.06: [  367]: --> [2:OK]
> Feb 24 16:32:41.07: [  367]: <-- [7:AT+FDR\r]
> Feb 24 16:32:42.55: [  367]: --> [5:+FCFR]
> Feb 24 16:32:49.33: [  367]: --> [8:+FHNG:70]

Looks like the modem failed to receive the high speed carrier for the
image phase in spite of successfully negotiating reception.

....
> Feb 24 16:02:58.14: [  367]: --> [2:OK]
> Feb 24 16:02:58.14: [  367]: <-- [7:AT+FDR\r]
> Feb 24 16:02:58.29: [  367]: --> [5:+FCFR]
> Feb 24 16:03:00.60: [  367]: --> [7:CONNECT]

Got the high speed carrier.

> Feb 24 16:03:00.60: [  367]: RECV: begin page
> Feb 24 16:03:00.60: [  367]: RECV: send trigger 021

Sent a probably wrong proceed code - see other articles - Rockwell
based modems and all modems with configuration files in the Hylafax
source tree expect 022, not 021.

> Feb 24 16:03:29.13: [  367]: RECV: 225 total lines, 225 bad lines, 0
> consecutive bad lines

Received 225 lines of rubbish.

> Feb 24 16:03:30.40: [  367]: --> [16:+FPTS:1,2142,0,0]

But modem reports that there should have been 2142 lines.

> Feb 24 16:03:30.40: [  367]: --> [6:+FET:2]
> Feb 24 16:03:30.40: [  367]: RECV recv EOP (no more pages or documents)

Remote indicates it has no more pages to send.

> Feb 24 16:03:30.40: [  367]: --> [2:OK]
> Feb 24 16:03:30.41: [  367]: RECV: REJECT page quality, 0% good lines (95%
> required)
> Feb 24 16:03:30.41: [  367]: RECV send RTN (retrain negative)

Quite reasonably told the other end it had received rubbish and asked
for a retransmission.

> Feb 24 16:03:30.41: [  367]: <-- [10:AT+FPTS=2\r]
> Feb 24 16:03:33.48: [  367]: --> [9:+FHNG:100]
> Feb 24 16:03:33.48: [  367]: REMOTE HANGUP: Unspecified Phase D error (code
> 100)

The other end gave up, probably because resending would need manual
intervention to reposition the page, or because it has violated the protocol
and hung up before confirming tranmsission.

> Feb 24 16:03:33.48: [  367]: --> [2:OK]
> Feb 24 16:03:33.48: [  367]: <-- [7:AT+FDR\r]

This is where there may be a problem with Hylafax - it looks like it
is trying to receive the next page even though the sender appears
to have gone away.

> Feb 24 16:06:33.48: [  367]: REMOTE HANGUP: Unspecified Phase C error,
> including too much delay between TCF and +FDR command (code 90)

Three minutes later it realises that the other end is no longer talking,
and gives up itself.