class2.txt

使用efax的fax工具程序

|   D              Originate a call                       |
|   A              Answer a call                          |
|   +FDT=          Data Transmission                      |
|   +FET=N         Transmit Page Punctuation              |
|   +FDR           Begin or Continue Phase C Receive Data |
|   +FK            Session Termination                    |
|---------------------------------------------------------|
|  CLASS 2 DCE RESPONSES                                  |
|---------------------------------------------------------|
|   +FCON          Facsimile Connection Response          |
|   +FDCS:         Report Current Session                 |
|   +FDIS:         Report Remote Identification           |
|   +FCFR          Indicate Confirmation to Receive       |
|   +FTSI:         Report the Transmit Station ID         |
|   +FCSI:         Report the Called Station ID           |
|   +FPTS:         Page Transfer Status                   |
|   +FET:          Post Page Message Response             |
|   +FHNG          Call Termination with Status           |
|---------------------------------------------------------|
|   CLASS 2 SESSION PARAMETERS                            |
|---------------------------------------------------------|
|   +FMFR?         Identify Manufacturer                  | 
|   +FMDL?         Identify Model                         |
|   +FREV?         Identify Revision                      |
|   +FDCC=         DCE Capabilities Parameters            |
|   +FDIS=         Current Sessions Parameters            |
|   +FDCS=         Current Session Results                |
|   +FLID=         Local ID String                        |
|   +FCR           Capability to Receive                  |
|   +FPTS=         Page Transfer Status                   |
|   +FAA           Adaptive Answer                        |
|   +FBUF?         Buffer Size (Read Only)                |
|   +FPHCTO        Phase C Time Out                       |
|   +FAXERR        Fax Error Value                        |
|   +FBOR          Phase C Data Bit Order                 |
|---------------------------------------------------------|

7.2 SERVICE CLASS 2 IDENTIFICATION AND SELECTION

The fax class 2 commands are summarized in Table 7-1.

Three commands report identification and selection information.  Each of 
these three commands cause the DCE to send a message to the DTE.  Each 
message is 20 bytes (ASCII encoded) followed by the terminating 
character (binary 0).

7.2.1 +FMFR?, REQUEST MANUFACTURER IDENTIFICAITION

The +FMFR? command caused the DCE to send a message identifying the DCE 
product manufacturer.  The default message is:

    ROCKWELL
    OK

7.2.2  +FMDL?, IDENTIFY PRODUCT MODEL

The +FMDL? command causes the DCE to send a message identifying the DCE 
product model.  The default message is:

   V.32AC
   OK

7.2.3  +FREV?, IDENTIFY PRODUCT REVISION

The +FREV? command causes the DCE to send a message identifying the DCE 
product model revision number.  The typical default message is:

    V0.200 TR14-JXXX-001
    OK

7.3  SERVICE CLASS 2 ACTION COMMANDS

These commands transfer data, and punctuate sessions.  They also release 
specific T.30 messages.  All action commands must be the last command on 
a command line.  This is indicated by the terminating <CR>.

All action commands initiate processes.  The modem will not accept other 
commands from the DTE until the modem issues a final result code  (e.g. 
OK, CONNECT).  The modem will abort the process if it receives any 
character before the final result code is issued.

7.3.1  ATD, ORIGINATE A CALL

Syntax:    ATD...<CR>

The DCE can support a DTE command to originate a call using the ATD 
command (See Table 4-2).

If this command is unsuccessful, the DCE reports an appropriate failure 
or error type result code such as NO CARRIER, NO DIALTONE or BUSY (see 
Table 4-7).

If this call is successful, the typical DCE response is:

   ATDnn.nn         (go off-hook, dial, get CED)
   +FCON            (DCE detects flags)
   [+FCSI:<remote ID string>]
   +FDCS:<T.30 subparameter string>
   OK

The DCE dials, detects call progress and generates the CNG tone.  Then 
it waits for a DIS frame.  On detection of the first Phase B preamble 
(V.21 ch. 2 modulated by 300 bit/s HDLC flags) it reports the "+FCON" 
message to the DTE.  The DCE then switches to 19.2K bps.

The DCE generates a DCS frame based on the received DIS frame and on the 
previously set +FDIS parameter.  A +FDT command from the DTE releases 
the DCE to transmit that DCS frame.

The DCE reports the initial received T.30 negotiation messages, 
including the DIS frame and the optional CSI ID string.  The +FDIS: 
report is followed by the OK final result code.

7.3.2  ATA, ANSWER A CALL

The DCE can support a DTE command to answer an incoming call using the 
ATA command (see Table 4-2).

The DTE may issue an Answer command in response to an incoming ring.

If the Answer command is unsuccessful, the DCE will report an 
appropriate failure or error type result code, such as NO CARRIER (see 
4-7)

MANUAL CALL ANSWER

If this call is successful, the typical DCE response (answer and 
receive) is:

  +FCON
  [+FTSI:<remote ID string>]
  +FDCS: <T.30 subparameter string>
  OK
  (DTE should issue +FDR command here)

On receipt of an Answer command from the DTE, the DCE answer and 
generates the CED tone.  The DCE then generates a DIS frame (derived 
from the +FDIS parameter) and hunts for the first T.30 negotiation 
frames.  On detection of the first Phase B preamble (V.21 ch 2 modulated 
by 300 bit/s HDLC flags), it reports the "+FCON" message to the DTE.

The DTE should report the initial received T.30 negotiation messages, 
including the DCS frame.  The +FCS: report will be followed by the OK 
final result code.

AUTOMATIC ANSWER

The modem provides for automatic answering of incoming calls.  If 
configured for automatic answer, the modem answers and incoming call in 
compliance with T.30 and reports the same messages as described for 
manual answer.

CONNECTIONS AS A DATA MODEM

If configured to do so by the +FAA parameter, the DCE will adaptively 
answer as a facsimile DCE or as a data DCE.  If the DCE answers as a 
facsimile DCE or as a data DCE.  If the DCE answers as a data DCE, it 
resets the +FCLASS parameter to 0 and issues the appropriate final 
result code (e.g. CONNECT or NO CARRIER) to the DTE.

7.3.3  +FDT, DATA TRANSMISSION

Syntax: +FDT<CR>

The +FDT command prefixes Phase C data transmission.  When the DCE is 
ready to accept Phase C data, it issues the negotiation responses and 
the CONNECT result code to the DTE.

In Phase B, the +FDT command releases the DCE to proceed with 
negotiation, and releases the DCS message to the remote station.  In 
Phase C, the +FDT command resumes transmission after the end of a prior 
transmit data stream.

INITIATE PAGE TRANSMISSION

Phase B DCE polled response:

  [+FCSI:<remote ID string>]                   ; If new CSI received
  [+FDIS:<subparameters from remote station>]  ; If new DIS received
  +FDCS:<T.30 subparameter string>
  CONNECT
  <XON>                                        ; When ready for data

After placing a call, or after finishing a document exchange, the DTE 
may command the DCE to re-enter T.30 Phase B to attempt to negotiate a 
document transmission.

CONTINUE A PAGE

   CONNECT
   <XON>

The DTE may issue more than one +FDT command for a given page, so that 
different files may be concatenated together.  These files must have the 
same format.

PHASE C DATA FRAMING

Phase C data must be presented to the DCE in stream mode.  The DCE 
expects Phase C data to follow until it detects <DLE><ETX> termination 
characters.  The DCE will filter the stream as described in Section 
7.1.2

The DCE will acknowledge the end of the data by returning the OK result 
code to the DTE.

If there is data underrun before the next +FDT or +FET= command, the DCE 
will zero-fill pad as per T.4 until the  Phase C timeout (+FPHCTO) is 
reached, or until more data is received.  The DCE appends an RTC pattern 
to the transmit data after an +FET= command is received from the DTE.

PHASE C DATA FORMAT

The Phase C data will be of the format specified by the negotiated T.30 
DCS frame.  The +FDCS <string> response is defined in section 7.4.2.  
The subparameter values are described in table 7.2.

The DCE will use the negotiated minimum Scan Time parameter from the DCS 
frame , and insert sufficient fill bits to pad each line to the minimum 
scan time.  This is reported in the +FDCS:ST subparameter.

If the DCE finds more than one consecutive EOL in Phase C data (e.g. 
RTC), it will send only one EOL.

Note 1:  Phase C data must conform to T.4 specifications

Note 2:  The DTE need not include a final RTC, since the DCE will append 
         an RTC in response to an FET= command

Note 3:  Some facsimile machines may treat two EOLs as an RTC

<CAN>, ESCAPE FROM TRANSMISSION

The DCE may request the DTE to halt Phase C transmission, by sending an 
cancel <CAN> character (024) to the DTE.  In this case, the DTE should 
terminate Phase C transmission, issue <CAN>, and wait for the OK 
response code from the DCE.

Table 7-2  T.30 Session Subparameter Codes

|-----------------------------------------------------------------|
|  Label |  Function     |  Value  |  Description                 |
|--------|---------------|---------|------------------------------|
|  VR    |  Vertical     |   0     |  Normal, 98 lpi              |
|        |  resolution   |   1     |  Fine, 196 lpi               |
|--------|---------------|---------|------------------------------|
|  BR    |  Bit Rate     |   0     |  2400 bit/s V.27 ter         |
|        |               |   1     |  4800 bit/s V.27 ter         |
|        |  (See note 1) |   2     |  7200 bit/s V.29 or v.17     |
|        |               |   3     |  9600 bit/s V.29 or v.17     |
|        |               | **4     |  12000 bit/s V.33 or v.17    |
|        |               | **5     |  14400 bit/s V.33 or v.17    |
|--------|---------------|---------|------------------------------|
|  WD    | Page Width    |   0     |  1728 pixels in 215 mm       |
|        |               |   1     |  2048 pixels in 255 mm       |
|        |               |   2     |  2432 pixels in 303 mm       |
|        |               |  *3     |  1216 pixels in 151 mm       |
|        |               |  *4     |   864 pixels in 107 mm       |
|--------|---------------|---------|------------------------------|
|  LN    |  Page Length  |   0     |  A4, 297 mm                  |
|        |               |  *1     |  B4, 364 mm                  |
|        |               |  *2     |  unlimited length            |
|--------|---------------|---------|------------------------------|
|  DF    |  Data         |   0     |  1-D modified Huffman        |
|        |  Compression  |   1     |  2-D modified Read           |
|        |  Format       |  *2     |  2-D uncompressed mode       |
|        |               |  *3     |  2-D modified Read           |
|--------|---------------|---------|------------------------------|
|  EC    |  Error        |   0     |  Disable ECM                 |
|        |  Correction   |  *1     |  Enable ECM,64 bytes/frame   |
|        |  (Annex       |  *2     |  Enable ECM,256 bytes/frame  |
|        |   A/T.30)     |         |                              |
|        |  (See Note 2) |         |                              |
|--------|---------------|---------|------------------------------|
|  BF    |  Binary File  |   0     |  Disable BFT                 |
|        |  Transfer     |  *1     |  Enable BFT                  |
|        |  (See Note 3) |         |                              |
|--------|---------------|---------|------------------------------|
|  ST    |  Scan Time/   |         |  VR=normal   VR=fine         |
|        |  Line         |   0     |    0 ms        0 ms          |
|        |               |   1     |    5 ms        5 ms          |
|        |               |   2     |    10 ms       5 ms          |
|        |               |   3     |    10 ms       10 ms         |
|        |               |   4     |    20 ms       10 ms         |
|        |               |   5     |    20 ms       20 ms         |
|        |               |   6     |    40 ms       20 ms         |
|        |               |   7     |    40 ms       40 ms         |
|--------|---------------|---------|------------------------------|
|  NOTES: 1: CCITT T.30 does not provide for the answering        |
|            station to specify all speeds exactly using the DIS  |
|            frame.  Implementation of some BR codes (e.g.code 2) |
|            by an answering DCE is manufacturer specific.        |
|                                                                 |
|                                                                 |
|         * =Not supported                                        |
|        ** =RC144AC only                                         |
|                                                                 |
|         2: ECM has been implemented in Supra's version 1.200C.  |
|            ECM transmit works correctly, and ECM receive works, |
|            but does not tell the transmitting machine that the  |
|            fax was received correctly.                          |
|                                                                 |
|        3:  BFT has been implemented in Supra's version 1.200C.  |
|            BFT transmit works correctly, and BFT receive works, |
|            but does not tell the transmitting machine that the  |
|            file was received correctly.                         |
|                                                                 |
|-----------------------------------------------------------------|


7.3.4  +FET=, TRANSMIT PAGE PUNCTUATION

Syntax:   +FET=<ppm>[,<pc>,<bc>,<fc>]

DCE response:
  +FPTS:<ppr>    ; when receive from remote OK

This command is used to punctuate page and document transmission after 
one or more +FDT commands.  This command generates T.30 Post Page 
Messages selected by the <ppm> code (Table 7-3)

The +FET=<ppm> command indicates that the current page is complete; no 
more data will be appended to it.  The value indicates if there are any 
additional pages are to be sent and, if so, whether there is a change in 
any of the document parameters.

The DTE can command the DCE to generate PRI-Q messages with the 
+FET=<ppm> command using ppm codes 4-6 (see Table 7-3)

This command must be sent within the time out specified by +FPHCTO after 
sending Phase C data, or else the DCE will end the page and document 
transmission.  If the Phase C timeout is reached, the DCE sends an EOP 
post page message and terminates the session

The remote facsimile station should respond to the post page message