2 class1 global – FaxBack NET SatisFAXtion 8.7 (Including R3) - Manual User Manual

Page 202

4 – Appendices

NET SatisFAXtion 8.7 Manual

202

fax_driver_name [string]: Device name that will override the key name that is
used for the fax device name. This needs to match a key or fax_device_name
from the driver specified by fax_driver_name. This would really only need to be
different when using the device# key name ordering option of ICANFax. For-
mat: One of the following values:

BOS_MAN
BT_MAN
CLASS1
CLASS2
GAMMAFAX
IP_FAX
PLUGIN_FAX_W32
SATISFAX

mode [string]: Sets whether this device sends, receives, both, or neither. This
setting must be present. When the application specifies "*" for "first available"
device when sending a message, devices set to

FAX_OUT

only have higher priori-

ty than devices set to

FAX_IN

FAX_OUT

. This is to prevent devices that are set

to both send and receive from sending a message, thus being unavailable for re-
ceives, when a device set to only send is available. This is a device specific set-
ting, but you can set the default for all devices by specifying this under the
global ICANFax section. Format: Comma separated list of

FAX_IN

and

FAX_OUT

, or

disabled

. Default:

FAX_IN, FAX_OUT

4.2.1.2

Class1 Global

frs_20_timeout_msecs [dword 0–65535]: How many milliseconds to wait
for

AT+FRS=20

to complete. This only applies if the

software_frs_20_msecs =

. Default:

500

fts_8_timeout_msecs [dword 0–65535]: How many milliseconds to wait for

AT+FTS=8

to complete. Default:

500

no_frame_checksum [boolean]: If

true

then modem will not return CRC

checksums in receive T30 frames. There was once a modem (AT&T Paradyne?)
that would not report the 2 CRC bytes for received T.30 frames (

at+frh=3

This lack of CRC bytes could cause the driver grief in knowing how much data
to actually process in the frame (i.e. receive CSI would lose 2 chars because the
driver assumes the last 2 bytes are CRC bytes). Default:

false

pause_before_frh_msecs [dword 0–65535]: Some modems would not be
able to understand the

AT+FRH=3

command if a slight pause is not inserted fol-

lowing a previous response or command. Since this is usually a very small delay,
this was previously implemented in 16 bit as a software timing loop because
one clock tick (54ms) was too long to wait. NT has a min of 10ms clock inter-
rupt timing, so this may cause problems and the driver may need to be modified
to use a software delay timing loop. Default:

receive_frame_response_timeout_msecs [dword 0–65535]: How long to
wait for modem response (

+FCERROR

NO CARRIER

...) after receiving a

DLE/ETX terminated frame. Default:

3000