recvq(5) [linux man page]
RECVQ(5) File Formats Manual RECVQ(5) NAME
recvq/fax* - received facsimile document format DESCRIPTION
Facsimile received by HylaFAX are placed in the recvq subdirectory. Each facsimile document is stored as a single Class F Tagged Image File Format (TIFF) file. This format includes the following information: o page width and length o horizontal and vertical resolution o page orientation o phone number of the sender o date and time document was received o number of scanlines received with errors o maximum number of consecutive scanlines received with errors o whether or not bad scanlines were regenerated by the receiver o make and model of the modem used to receive the document o name of the host computer on which the document was received Image data is written using either CCITT T.4 or CCITT T.6 compression. By default data is written using the compression scheme/data format negotiated by the sender and receiver. However, if faxgetty(8) is configured to do copy quality checking then data is written using the compression scheme defined by the RecvDataFormat configuration parameter; see hylafax-config(5). A scanline that is regenerated by the receiver because of an error is typically just a copy of the previous good scanline. The files in the recvq directory are created with the protection mode specified in the server configuration file(s). By default, files are created with mode 0600 and owned by the fax user, which means that they are accessible only to the fax user. To print a facsimile on a POSTSCRIPT(R) printer, the fax2ps(1) program can be used. SEE ALSO
viewfax(1), faxview(1), fax2ps(1), faxgetty(8), libtiff(3), hylafax-config(5) October 3, 1995 RECVQ(5)
Check Out this Related Man Page
XFERFAXLOG(5) File Formats Manual XFERFAXLOG(5) NAME
xferfaxlog - HylaFAX activity log DESCRIPTION
The file etc/xferfaxlog contains information about inbound and outbound activities. The file contains one line per inbound or outbound call (except for facsimile documents retrieved by polling in which case multiple entries may be present for a single call). If the modem config setting LogCalls is set to true, then the file also contains one line per received call. Lines are fixed-format, tab-separated ASCII strings. Each record of a facsimile transmission is of the form: date SEND commid modem jobid jobtag sender ``dest-number'' ``CSI'' params #pages jobtime conntime ``reason'' <null> <null> <null> ``owner'' ``dcs'' A facsimile reception record is of the form: date RECV commid modem fax.tif <null> fax ``local-number'' ``TSI'' params #pages jobtime conntime ``reason'' ``CallID1'' ``CallID2'' ``CallID3...CallIDn'' <null> ``dcs'' Each inbound call record is of the form: date CALL commid modem <null> <null> fax ``local-number'' <null> 0 0 jobtime conntime ``reason'' ``CallID1'' ``CallID2'' ``Cal- lID3..CallIDn'' <null> ``dcs'' Each facsimile document retrieved by polling has a record of the form: date POLL commid modem jobid jobtag sender ``dest-number'' ``TSI'' params #pages jobtime conntime ``reason'' <null> <null> <null> An alphanumeric pager request has a record of the form: date PAGE commid modem jobid jobtag sender ``dest-number'' ``<null>'' 0 0 jobtime conntime ``reason'' <null> <null> ``owner'' The following describes the fields in the above records: date The date and time of the transaction in the format MM/DD/YY HH:MM , where MM is the numeric month, DD the numeric day, YY the last two digits of the year, and HH:MM is the time in 24-hour format. commid The communication identifier for the call. modem The device identifier for the modem that was used to do the send or receive. jobid The job number for outbound calls. jobtag The client-specified job tag for outbound calls. fax.tif The associated recvq fax TIFF file for the event. sender The sender/receiver's electronic mailing address (facsimile receptions are always attributed to the ``fax'' user). dest-number The phone number dialed for outgoing calls. TSI The Transmitter Subscriber Identification string (as received) for incoming calls. CSI The Caller Subscriber Identification string of the remote machine (as reported) for outgoing calls. local-number The local phone number on which the data was received. params The negotiated facsimile session parameters used for transferring data encoded as described below. #pages The total number of pages transferred. jobtime The duration of the session; in the format HH:MM:SS. This time includes setup overhead and any time spent cleaning up after a call. conntime The time spent on the phone; in the format HH:MM:SS. This should be the time used by the PTT to calculate usage charges. reason A string that indicates if any problem occurred during the session. CIDName The received CIDName value for the session. CIDNumber The received CIDNumber value for the session. owner The login name of the job owner. dcs The T.30 DCS string that was used in the facsimile communication. Note that fields may have embedded blanks. Session parameters are encoded as a decimal number that contains a packed set of Class 2 ses- sion parameter values. The format is: 2 bits for vertical resolution, 3 bits for signalling rate, 3 bits for page width, 2 bits for page length, 2 bits for data format, 1 bit for ECM use, 1 bit of BF use, and 3 bits for the min scanline time. The page counts are always inte- gral numbers. Partial pages that are to be retransmitted are not included in the page count. The simple ASCII format was designed to be easy to process with programs like awk(1). NOTES
The sender field does not necessarily represent the submitter's actual identity. For example, it reflects the value given by the send- fax(8) ``-f'' option. Be cautious that this field is not utilized for auditing if the fax user base is not trusted. BUGS
The date format will ``break'' in the year 2000. Information should be recorded on a per-page basis for facsimile communications. SEE ALSO
faxq(8) faxsend(8) faxgetty(8) June 5, 1996 XFERFAXLOG(5)