Fax data can be stored in one of the following formats. Support for file storage formats varies by product; see Section 2.4. Key Product Features on page 8.
Fax data stored in raw, unformatted files contains only a single page of fax data per file. A description of the data, such as width, resolution and encoding scheme is specified in the DF_IOTT structure.
Raw MH encoded data is recorded by the fax library with a fill order of Least Significant Bit (LSB) first and may not have EOL (End Of Line) sequences byte aligned.
Raw MMR encoded data is also recorded by the fax library with a fill order of Least Significant Bit (LSB) first. There is no zero fill, EOL (End Of Line) sequences or byte alignment for MMR stored files.
Raw, unformatted files for transmission are treated as a byte stream of compressed fax data with the width, resolution and encoding scheme of the stored data specified in the fields of the DF_IOTT structure.
For transmission, raw MH encoded data must include EOL (End Of Line) flags, but may or may not contain RTC (Return To Control) sequences. RTC sequences are inserted by the firmware at the end of Phase C (message transmission) if the raw data does not contain them.
TIFF/F refers to Tagged Image File Format meeting Class F specifications.
A TIFF/F file stores MH or MMR encoded data with additional header information and tags. Information such as the starting page number, page count and data type is specified in the DF_IOTT structure. Incoming fax data stored in TIFF/F format is written by the fax library with tags specified in Appendix A. TIFF/F files that include all mandatory tags (or subset) with valid values are accepted for transmission.
During transmission, ASCII text files are converted to an encoded fax image. A description of the data, such as width, resolution and encoding scheme, is specified in the DF_IOTT structure. You can define additional attributes using the DF_ASCIIDATA structure.
To set fonts for use in ASCII to fax conversion, see Chapter 6. Specifying Fonts in ASCII to Fax Conversion.
Click here to contact Dialogic Customer EngineeringCopyright 2002, Intel Corporation