Re: flexfax: sendpage problems continued

[Matthias.Apitz@SOFTCON.de]

Mike Pistone wrote:
    
    Here is what I get with the IXO debugging
    
    It looks like the ATH0 line right after CONNECT 1200 is the problem.
    Why is the program hanging up?
    Just for the record,  I can send pages just fine with this modem from
    Windows 95 software so it is not the modem....

BTW: If a modem returns garbage or noice and the Windows 95
sw is designed to eat up the garbage for that specific modem
this does not mean that the modem isn't the problem.
And if your Windows 95 software runs fine with that modem it
would be nice to see a log file/trace *how* this software
handles the problem below.
    
    ANY HELP?  Please??

See below.
    
    Nov 24 18:34:11.20: [10165]: SESSION BEGIN 00001282 18006116532
    Nov 24 18:34:11.20: [10165]: MODEM set DTR OFF
    Nov 24 18:34:13.81: [10165]: MODEM set DTR ON
    Nov 24 18:34:13.81: [10165]: MODEM set baud rate: 19200 baud,input 	flow
    XON/XOFF, output flow XON/XOFF
    Nov 24 18:34:13.81: [10165]: MODEM flush i/o
    Nov 24 18:34:13.81: [10165]: <-- [15:ATE0V1Q0S0=0H0\r]
    Nov 24 18:34:13.82: [10165]: --> [2:OK]
    Nov 24 18:34:13.82: [10165]: <-- [21:ATS8=2S7=60&K4&D2&C1\r]
    Nov 24 18:34:13.84: [10165]: --> [2:OK]
    Nov 24 18:34:13.84: [10165]: <-- [5:ATM0\r]
    Nov 24 18:34:13.85: [10165]: --> [2:OK]
    Nov 24 18:34:13.85: [10165]: MODEM set parity: 7 bits, even parity
    Nov 24 18:34:13.85: [10165]: MODEM input buffering enabled
    Nov 24 18:34:13.92: [10165]: <-- [12:AT+FCLASS=0\r]
    Nov 24 18:34:14.03: [10165]: --> [2:OK]
    Nov 24 18:34:14.03: [10165]: <-- [28:ATE0B0S37=5N0W2&Q0F4M1L1\N1\r]
    Nov 24 18:34:14.15: [10165]: --> [2:OK]
    Nov 24 18:34:14.15: [10165]: <-- [17:ATDT18006116532@\r]
    Nov 24 18:34:29.11: [10165]: --> [12:CARRIER 1200]

HylFAX's pagesend(1M) dials and your modem returns "CARRIER 1200".
It should return "CONNECT" or "CONNECT 1200" or something like
that. The response "CARRIER...." is treated as a failure.

If you can't switch the message off (check your modem manual)
there are now two opportunities. Check (e.g. with a terminal
program) whether or not the "CARRIER...." message is followed
by a "CONNECT" message. In this case you could add the eating
up of the garbage to ClassModem::isNoise() in faxd/ClassModem.c++
The other opportunity is to use another modem for HylaFAX.

	matthias

    Nov 24 18:34:29.11: [10165]: <-- [5:ATH0\r]
    Nov 24 18:34:34.11: [10165]: MODEM TIMEOUT: reading line from modem
    Nov 24 18:34:34.11: [10165]: MODEM <Timeout>
    Nov 24 18:34:34.11: [10165]: MODEM input buffering enabled
    Nov 24 18:34:34.12: [10165]: MODEM set DTR OFF
    Nov 24 18:34:34.12: [10165]: SESSION END
    
    -------------------------------------------------------------
    Mike Pistone                            pistone@eurekanet.com
    Systems/Network Administrator                 ph 614.593-5052
    Eureka Networks, Ltd.                         fx 614.594-3632