efax.1

使用efax的fax工具程序

.TH EFAX 1 "April 1994" ""  ""
.UC 1
.\" $Id: efax.1,v 1.4 1993/11/20 17:34:59 edc Exp edc $
.SH NAME
efax \- send/receive faxes using Class 1 or 2 fax modems
.SH SYNOPSIS

.B efax
[
\fIoptions\fP
]
[
\fB-r\fP \fIpat\fP
|
\fB-t\fP \fInum\fP \fIfile\fP...
|
\fB-p\fP \fInum\fP \fIpat\fR
]

.SH OPTIONS

Where \fIoptions\fP are:

.TP 9 
.B -d \fIdev\fP 
use the fax modem connected to device \fIdev\fP.  The default is
\fB/dev/fax\fP.  

.\" If \fIdev\fP is \fB\`-'\fP efax uses the standard input.

.TP 9 
.B -o \fIopt\fP 
use option \fIopt\fP to accommodate a non-standard fax modem
protocol.  See the MODEM REQUIREMENTS section below for more
details.  The \fIopt\fPions are:

.TP 9
.B 
    1
Use Class 1 fax modem commands.  The modem must suport Class 1
commands.  The default is to use Class 2 commands.

.\" .TP 9
.\" .B 
.\"    0
.\" Use Class 2.0 fax modem commands (untested).

.TP 9
.B 
    a
use software adaptive answer method.  If the first attempt to
answer the call does not result in a data connection within 15
seconds the phone is hung up temporarily and answered again in
fax mode (see "Accepting both fax and data calls" below).

.TP 9
.B 
    e 
ignore errors in modem initialization commands.

.TP 9
.B 
    r
reverse bit order during data reception.  Most Class 2 modems
require this option.

.TP 9
.B 
    x
send XON (DC1) instead of DC2 to start data reception.  Applies
to Class 2 only.

.TP 9
.B 
    z
delay an additional 100 milliseconds before each modem
initialization or reset command.  The initial delay is 100
ms. For example, -ozzz produces a 400 ms delay.


.TP 9
.B -i \fIstr\fP
send the command \fBAT\fP\fIstr\fP to the modem to initialize it.
Multiple \fB-i\fP may options be used.

.TP 9
.B -z \fIstr\fP
send the command \fBAT\fP\fIstr\fP to the modem to reset it when
done.  Multiple \fB-z\fP may options be used.

.TP 9
.B -c \fIcaps\fP
set the local capabilities to \fIcaps\fP.  See the section on
capabilities below for the format and meaning of \fIcaps\fP.  The
default is 1,3,0,2,0,0,0,0.  
For Class 2 operation this option must appear after the modem
initialization (-i) option that enables fax mode.

.TP 9
.B -l \fIid\fP
set the local identification string to \fIid\fP.  \fIid\fP should
be the local telephone number in international format (for
example "[phone]").  This is passed to the remote fax
machine.  Some fax machines may not accept characters other than
numbers, space, and '+'.  For Class 2 operation this option must
appear after the modem initialization (-i) option that enables
fax mode.

.TP 9
.B -h \fIhdr\fP
put string `hdr' at the top of each page.  The first %d in `hdr'
is replaced by the page number, the second is replaced by the
number of pages.

.TP 9
.B -f \fIfnt\fP
use font file \fIfnt\fP for generating the header.  The default
is a built-in 8x16 font.  See efix(1) for the font file format.

.TP 9
.B -v \fIstrng\fP
select types of messages to be printed.  Each \fIlower-case\fP
letter in \fIstrng\fP enables one type of message:

.RS 12
.B
e - 
errors
.br
.B
w - 
warnings
.br
.B
i - 
session progress information
.br
.B
n - 
capability negotiation information
.br
.B
c - 
modem (AT) commands and responses
.br
.B
h - 
HDLC frame data (Class 1 only)
.br
.B
m - 
modem output
.br
.B
a - 
program arguments
.br
.B
r -
reception error details

.RE

.RS 9
The default is "ewin".
.RE

.TP 9
.B -x \fIlkf\fP
use UUCP-style lock file \fIlkf\fP to lock the modem device
before opening it.  If the device is locked, efax checks every 15
seconds until it is free.  Up to 16 -x options may be used if
there are several names for the same device.  A `#' prefix on the
file name creates an HDB-style (text) lock file.

.TP 9
.B -s
remove lock file(s) after initializing the modem.  This allows
outgoing calls when efax is waiting for an incoming call.  If
efax detects modem activity it will attempt to re-lock the
device.  If the modem is now locked by another program efax will
exit and return 1 (``busy'').  Normally a new efax process is
then started by init(8). The new process waits until the line
becomes free.

.TP 9
.B -w
wait for an OK or CONNECT prompt instead of issuing an answer
(\fBATA\fP) command to receive a fax.  Use this option when the
modem is set to auto-answer (using S0=\fIn\fP) or if another
program has already answered the call.

.TP 9
.B -g \fIcmd\fP
if a \fBCONNECT\fP (or \fBDATA\fP) response indicates a data
call, the shell \fB/bin/sh\fP is exec(2)'ed with \fIcmd\fP as its
command.  \fIcmd\fP is a printf(3) format that may contain up to
6 %d escapes which are replaced by the baud rate following the
most recent \fBCONNECT\fP message. \fIcmd\fP typically exec's
getty(8).

.TP 9
.B -q \fIn\fP
ask for page retransmission if more than \fIn\fP errors per page
are detected.  Default is 10.

.SH COMMANDS

.TP 9
.B -r \fIpat\fP
answer phone and receive a fax.  Each fax page is stored in a
separate file.  The file name is created using \fIpat\fP as a
strftime(3) format string.  A page number of the form .001, .002, ...  
is appended to the file name.  If \fIpat\fP is blank (""), a
default string of "%m%d%H%M%S" is used.  If a file already
exists, efax terminates with an error message.

.TP 9
.B -t \fInum file\fP...
dial telephone number \fInum\fP and send the fax image files
\fIfile\fP....  The telephone number \fInum\fP is a string that
may contain any dial modifiers that the modem supports, for
example, a T prefix for tone dialing or commas for delays.

.TP 9
.B -p \fInum pat\fP...
dial telephone number \fInum\fP and receive any pages available
to be polled. \fInum\fP and \fIpat\fP are as above.  Only
implemented for Class 1 modems.

.SH FAX FILE FORMATS

Each page is stored in a separate file.  The images are coded
according to the ITU-T (CCITT) Group 3 fax standard, T.4.  The
EXAMPLES section below shows how efix or the Ghostscript and the
PBM utilities can be used to create and print these files.

.SH OPERATING SYSTEM REQUIREMENTS

The operating system must provide short response times to avoid
protocol timeouts.  For Class 2 modems the delay should not
exceed 1 or 2 seconds.

When using Class 1 modems the program must respond to certain
events within 55 milliseconds.  Longer delays may cause the fax
protocol to fail in certain places (between DCS and TCF or
between RTC and MPS).  Class 1 modems should therefore not be
used on systems that cannot guarantee that the program will
respond to incoming data in less than 55 milliseconds.  In
particular, intelligent serial cards or terminal servers may
introduce enough delay to cause problems with Class 1 operation.

The operating system must also provide sufficient low-level
buffering to allow uninterrupted transfer of data from the modem
to a disk file at the selected baud rate, typically 9600 bps.
Since the fax protocol does not provide end-to-end flow control
the effectiveness of flow control while receiving is limited by
the size of the modem's buffer. This can be less than 100 bytes.
Efax does not use flow control during reception.

.SH MODEM REQUIREMENTS

"Group" describes the protocol used to send faxes over the
telephone network.  Efax suports the universal Group 3 standard.
The "Class" is the protocol used between a computer and a fax
modem.  Efax supports Class 1 and 2 (but not 2.0) fax modems.

.\" Class 2.0 support is untested.

Almost all Class 2 modems reverse the bit order (MSB to LSB) on
receive.  This will cause errors when trying to display or print
the received files.  The \fB-or\fP option should be specified
when receiving faxes using these modems.

All fax modems except AT&T models use XON/XOFF flow control by
default.  This type of flow control adds very little overhead in
fax mode. Most modems have unreliable hardware (RTS/CTS) flow
control in fax mode.  Therefore efax only supports XON/XOFF flow
control.

While some modems have serial buffers of about 1k bytes, many
inexpensive modems have buffers of about one hundred bytes and
are thus more likely to suffer overruns when receiving data.

Some modems may need a delay between commands of more than the
default value used by efax (100 milliseconds).  If the delay is
too short, commands may not echo properly, may time out, or may
give inconsistent responses.  Use one or more \fB-oz\fP options
to increase the delay between modem initialization commands.

By default efax sends DC2 to start the data flow from the modem
when receiving faxes from Class 2 modems.  A few older modems
require XON instead.  Use of DC2 would cause the modem to give an
error message and/or the program to time out.  The \fB-ox\fP
option should be used in this case.

A few older Class 2 modems (e.g. some Intel models) don't send
DC2 or XON to start the data flow to the modem when sending
faxes.  After waiting 2 seconds efax will print a warning and
start sending anyways.

Some inexpensive "9600 bps" fax modems only \fItransmit\fP at
9600 bps and reception is limited to 4800 bps.

The following Class 1 modems have been reported to work with efax:
AT&T DataPort,
.\" Andrea Gozzi <[e-mail]>, v0.6, SCO 3.2.0, (Class 1)
Cardinal Digital Fax Modem (14400),
.\" [e-mail], v0.6, linux 1.0, downloading fax144c.car
Digicom Scout+,
.\" [e-mail], v 0.6, Linux 1.1.12
QuickComm Spirit II,
.\" [e-mail], v 0.6, Linux 1.1.12
Smartlink 9614AV-Modem,
.\" [e-mail], v0.6, Linux 1.1.15
Supra Faxmodem 144LC,
.\" [e-mail], v0.6, Consensys (ie., Unixware) 4.2
USR Courier V.32bis Terbo,
.\" [e-mail], v0.6, SunOS 4.1.3
USR Sportster,
.\" satyr![e-mail] (Kayvan Sylvan), v0.6, Linux (?)
Zoom AFC 2.400,
.\" [e-mail] (Utz-Uwe Haus), v0.6, Linux
Zoom VFX14.4V.
.\" [e-mail] (me!), v0.6, Linux

The following Class 2 modems have been reported to work with efax:
14k4 Amigo Communion fax/modem,
.\" [e-mail], efax0.5
askey modem type 1414VQE,
.\" [e-mail], efax06?, Linux?
AT&T DataPort,
.\" [e-mail] (Class 2)
ATT/Paradyne,
.\" [e-mail]
AT&T Paradyne PCMCIA,
.\" [e-mail] (Juha Heinanen)
Boca modem,
.\" ?
BOCA M1440E, 
.\" v0.6a, SunOS 4.1.1, Linux 1.0.9
.\" [e-mail]
Crosslink 9614FH faxmodem,
.\" ?
FuryCard DNE 5005,
.\" a PCMCIA Class 3 faxmodem
.\" [e-mail]
GVC 14.4k internal,
.\" [e-mail], 0.6a w/ stty fax patch, Linux kernel 1.1.59
Intel 14.4 fax modem,
.\" ([e-mail])
Megahertz 14.4,
,\" [e-mail]
Microcom DeskPorte FAST ES 28.8,
.\" Skip Montanaro ([e-mail]), 0.6a, Linux
Motorola UDS FasTalk II,
.\" Raj Mathur ([e-mail]), 0.6a, Linux 1.1.48
MultiTech 1432MU,
.\"[e-mail]
Practical Peripherals PM14400FXMT,
.\" (DEC Alpha AXP 3000/500 running OSF/1 V1.3)
Supra V32bis,
.\" [e-mail], v0.5b, SysV R4.2
.\" tbucks![e-mail]
.\" (ROCKWELL)
.\" [e-mail] (Alec Muffett), Linux 1.1.51, 
.\"  Supra FAXModem v.32bis
Telebit Worldblazer,
.\" blurfl![e-mail]
.\" Telebit Worldblazer with ROM version LA7.02. (requires -or)
.\" (my configuration required hardware flow control)
.\" [e-mail], v 0.6, Version LA7.05C.  
Twincom 144/DFi,