Re: Receiving works --- almost

[Matthias.Apitz@SOFTCON.de (Matthias Apitz)]

Stefan Pettersson wrote:
    
    When I receive a fax from most fax machines I get the page ok and my modem
    disconnects. But the sending fax machine indicates "Tx error".
    If I lift the phone and listen (in my end) I hear the fax machine still trying
    to talk.
    
    Sending fax works perfectly.

Sorry for the delay -- but I wanted to check this against the
class2 spec; you've hit a bug in the driver; see below;
    
    
    OS: Linux 2.0.27 (Slackware)
    The Software: v4.0pl1 (binary dist)
    Modem: Microcom DeskPorte 33.6S class 2
    Chip: MODEM ROCKWELL AC/V34/V1.510-V34_DS
    
    
    Jan 24 12:34:04.95: [  341]: SESSION BEGIN 00000080 4658914585
    Jan 24 12:34:04.95: [  341]: <-- [4:ATA\r]
    Jan 24 12:34:13.65: [  341]: --> [5:+FCON]
    Jan 24 12:34:13.75: [  341]: ANSWER: FAX CONNECTION
    Jan 24 12:34:13.75: [  341]: RECV FAX: begin
    Jan 24 12:34:15.34: [  341]: --> [29:+FTSI: "       +46 570 10070"]
    Jan 24 12:34:15.34: [  341]: REMOTE TSI "+46 570 10070"
    Jan 24 12:34:15.64: [  341]: --> [22:+FDCS: 0,3,0,2,1,0,0,0]
    Jan 24 12:34:15.64: [  341]: REMOTE wants 9600 bit/s
    Jan 24 12:34:15.64: [  341]: REMOTE wants page width 1728 pixels in 215 mm
    Jan 24 12:34:15.64: [  341]: REMOTE wants unlimited page length 
    Jan 24 12:34:15.64: [  341]: REMOTE wants 3.85 line/mm
    Jan 24 12:34:15.64: [  341]: REMOTE wants 2-D MR
    Jan 24 12:34:15.75: [  341]: --> [2:OK]
    Jan 24 12:34:15.75: [  341]: <-- [7:AT+FDR\r]
    Jan 24 12:34:17.56: [  341]: --> [5:+FCFR]
    Jan 24 12:34:20.13: [  341]: --> [22:+FDCS: 0,3,0,2,1,0,0,0]
    Jan 24 12:34:20.13: [  341]: REMOTE wants 9600 bit/s
    Jan 24 12:34:20.13: [  341]: REMOTE wants page width 1728 pixels in 215 mm
    Jan 24 12:34:20.13: [  341]: REMOTE wants unlimited page length 
    Jan 24 12:34:20.13: [  341]: REMOTE wants 3.85 line/mm
    Jan 24 12:34:20.13: [  341]: REMOTE wants 2-D MR
    Jan 24 12:34:20.13: [  341]: --> [7:CONNECT]
    Jan 24 12:34:20.13: [  341]: RECV: begin page
    Jan 24 12:34:20.13: [  341]: RECV: send trigger 022
    Jan 24 12:34:20.13: [  341]: <-- data [1]
    Jan 24 12:34:40.88: [  341]: RECV: 1146 total lines, 0 bad lines, 0 consecutive 
    bad lines
    Jan 24 12:34:40.93: [  341]: --> [17:+FPTS: 2,2219,0,0]
    Jan 24 12:34:42.19: [  341]: --> [7:+FET: 2]
    Jan 24 12:34:42.19: [  341]: RECV recv EOP (no more pages or documents)
    Jan 24 12:34:42.30: [  341]: --> [2:OK]
    Jan 24 12:34:42.30: [  341]: RECV send MCF (message confirmation)
    Jan 24 12:34:42.30: [  341]: RECV FAX (00000080): from +46 570 10070, page 1 in 
    0:27, INF, 3.85 line/mm, 2-D MR
    Jan 24 12:34:42.31: [  341]: RECV FAX (00000080): recvq/fax00036.tif from +46 57
    0 10070, route to <unspecified>, 1 pages in 0:2
    9
    Jan 24 12:34:42.31: [  341]: <-- [7:AT+FDR\r]
    Jan 24 12:34:46.21: [  341]: --> [29:+FTSI: "       +46 570 10070"]
    Jan 24 12:34:46.21: [  341]: RECV FAX: bin/faxrcvd "recvq/fax00036.tif" "modem" 
    "00000080" ""
    Jan 24 12:34:54.88: [  341]: RECV FAX: end
    Jan 24 12:34:54.88: [  341]: SESSION END

the modem says "+FPTS: 2,2219,0,0" which means the page isn't
good (from the point of view of the modem), ends phase C and reports
the post-message command value as "+FET: 2" -- EOP;
it is now in phase D and waiting for "AT+FDR" command;
    
HylaFAX just ignores the PPR value of the modem 'cuze it
does its own quality checking and sets its internal ppr-value
to 1;

if we're now issuing the "AT+FDR" the modem releases not an
MCF (Message Confirmation), it releases an RTN frame;

the bug is that we don't care about the modems status of the
page;

a workaround could be disabling the copy quality checking of the
server if the modem is able to do that; see PersentGoodLines
and Class2CQCmd / Class2CQQueryCmd in config(4F);

	matthias