Re: flexfax: SEND FAILED: Remote is not T.4 compatible ????????

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

> Aug 26 15:13:16.53: [  862]: DIAL 00190512776
> Aug 26 15:13:16.53: [  862]: <-- [17:ATDP00190512776@\r]
> Aug 26 15:13:46.03: [  862]: --> [7:CONNECT]
> Aug 26 15:13:47.37: [  862]: --> [2:OK]
> Aug 26 15:13:47.37: [  862]: REMOTE CSI "0"
> Aug 26 15:13:47.37: [  862]: <-- [9:AT+FRH=3\r]
> Aug 26 15:13:47.39: [  862]: --> [7:CONNECT]
> Aug 26 15:13:47.67: [  862]: --> [2:OK]
> Aug 26 15:13:47.67: [  862]: Remote is not T.4 compatible
> Aug 26 15:13:47.67: [  862]: SEND FAILED: Remote is not T.4 compatible

Either you haven't got a sufficient trace level (you definitely need
the 0x00002 bit set in the session tracing flags, and may need the
0x00040 bit set as well) or the modem is returning
empty Phase B protocol frames.  You might want to experiment with the
receive bit order (ModemFrameFillOrder).

This is the code that generates the error:

                case FCF_DIS:
                    if ((dis&DIS_T4RCVR) == 0) {
                        emsg = "Remote is not T.4 compatible";
                        protoTrace(emsg);
                        return (send_failed);

and I think the T4 Receiver bit is zero because the whole of the message
is zero, because no message has been recognized, and possibly none 
received.