PE> handle class 2 faxes. So, can you tell me whether this means I
PE> can use Binkley by itself to receive faxes? BFN. Paul.
LE> Yes. You need to find which keyword sets the connect message Bink
LE> recognizes as fax. It might default to +FCON or /FAX, you need to change it
It defaults to +FCO. With BTPE 4.00 it now needs an exact match,
so that isn't good enough. So I whacked the following stuff into
binkley.cfg:
Answer AT+FAA=1;+FCR=1;+FSW=1;A|
Faxindir c:\faxindir
ModemIgnore RINGING
ModemIgnore RING RESPONSE
ModemRinging RING
ModemConnect CONNECT
ModemIgnore RRING
ModemRetry BUSY
ModemFailure VOICE
ModemFailure ERROR
ModemFailure OK
ModemFailure NO CARRIER
ModemIncoming NO DIAL
ModemIgnore DIALING
ModemFailure NO ANSWER
ModemIgnore DIAL TONE
ModemFax +FCO
ModemFax +FCON
and it received fax + data fine!
LE> to +FCON if it's /FAX. Apart from that you MAY find a problem waiting for
LE> is >you if your DTE rate 19200bps. While you're debugging and testing etc,
LE> run with DTE=19200. Only
LE> once you're sure it works, increase DTE.
The Binkley documentation said that it defaults to operating at 19200
unless you use faxbaud. I found no such evidence in the source code,
so I assume it operated at 57600. Worked fine, regardless!
Any suggestions on what I should do with the *.FAX files? I can use
a program called MAKEFAX which will convert them into something viewable
by ZFAX or Quicklink II. I am attempting to track down a copy of ZFAX.
I have an old copy of Quicklink II, which doesn't appear to support
that. BFN. Paul.
@EOT:
---
* Origin: X (3:711/934.9)
|