2 class1 global – FaxBack NET SatisFAXtion 8.6 - Manual User Manual

Page 208

4 – Appendices

NET SatisFAXtion 8.6 Manual

208

setting, 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

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 = 0

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

following 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
interrupt 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

receive_v34_image_modulation_timeout_msecs [dword 0–65535]:
How long to wait without receiving any image data before canceling the
reception of image data when doing v.34 fax receive. This is quite different than
the

receive_image_modulation_timeout_msecs

because the modem is

responsible for removing flags and bit stuffing and it may be that the sending
unit can add up to 35 seconds of flags between ECM frames so as to allow for
send flow control. It is valid and has been witnessed that the class1 driver might
not receive any data for several seconds due to the sender scanning latency.
Default:

35000

send_frame_response_timeout_msecs [dword 0–65535]: How long to
wait for modem response after sending frame data. Default:

software_frs_20_msecs [dword 0–65535]: How long to wait when switching
the modulation from receive to transmit. If this is set to 0, then

AT+FRS=20

will be

used. Default:

300

star t_receive_image_timeout_msecs [dword 0–65535]: How long to wait
for modem response after sending

AT+FRM=

command to start receive

training/image data. Default:

3000

star t_send_image_timeout_msecs [dword 0–65535]: How long to wait for
modem response after sending

AT+FRM=

command to start send

training/image data. Default:

3000

t1_seconds [dword 0–65535]: T.30 T1 timer. Default: