Re: faxrm failure

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

Maarten Boerlijst wrote:
    
    Hi again,
    
    Maybe this helps even further:
    
    Also after getting a no-answer for a send jod the modem sometimes goes waiting:
    
    email notifyer:
    
    Your facsimile job to 71279 was not sent because:
        No answer from remote
    
    The job will be retried at 09:19.
    
        ---- Transcript of session follows ----
    
    Feb 12 09:15:09.54: [14803]: SESSION BEGIN 00000051 44186571279
    Feb 12 09:15:09.55: [14803]: SEND FAX: JOB 32 DEST 71279 COMMID 00000051
    Feb 12 09:15:09.55: [14803]: DELAY 2600 ms
    Feb 12 09:15:12.15: [14803]: <-- [15:ATE0V1Q0S0=0H0\r]
    Feb 12 09:15:12.25: [14803]: --> [14:ATE0V1Q0S0=0H0]
                                         ^^^^^^^^^^^^^^

What is the reason for the ECHO-on mode of the modem? If faxgetty(1M)
was the last "user" of it it should be in ECHO-off; if faxsend(1M)
was the last it should be in ECHO-off too;

    Feb 12 09:15:12.26: [14803]: --> [2:OK]
    Feb 12 09:15:12.26: [14803]: <-- [21:ATS8=2S7=60&E4&D3&C1\r]
                                                       ^^^
ah, this is the answer: DTR-drop re-loads profile 0 later;

    Feb 12 09:15:12.32: [14803]: --> [2:OK]
    Feb 12 09:15:12.32: [14803]: <-- [12:AT+FCLASS=2\r]
    Feb 12 09:15:12.38: [14803]: --> [2:OK]
    Feb 12 09:15:12.38: [14803]: <-- [10:AT+FTBC=0\r]
    Feb 12 09:15:12.44: [14803]: --> [2:OK]
    Feb 12 09:15:12.44: [14803]: <-- [10:AT+FBOR=0\r]
    Feb 12 09:15:12.49: [14803]: --> [2:OK]
    Feb 12 09:15:12.49: [14803]: <-- [13:AT+FPHCTO=30\r]
    Feb 12 09:15:12.55: [14803]: --> [2:OK]
    Feb 12 09:15:12.55: [14803]: <-- [24:AT+FDCC=1,5,2,2,2,0,0,0\r]
    Feb 12 09:15:12.62: [14803]: --> [2:OK]
    Feb 12 09:15:12.62: [14803]: <-- [5:ATM0\r]
    Feb 12 09:15:12.67: [14803]: --> [2:OK]
    Feb 12 09:15:12.68: [14803]: <-- [12:AT+FCLASS=2\r]
    Feb 12 09:15:12.83: [14803]: --> [2:OK]
    Feb 12 09:15:12.83: [14803]: <-- [10:AT+FTBC=0\r]
    Feb 12 09:15:12.98: [14803]: --> [2:OK]
    Feb 12 09:15:12.98: [14803]: <-- [10:AT+FBOR=0\r]
    Feb 12 09:15:13.13: [14803]: --> [2:OK]
    Feb 12 09:15:13.13: [14803]: <-- [13:AT+FPHCTO=30\r]
    Feb 12 09:15:13.29: [14803]: --> [2:OK]
    Feb 12 09:15:13.29: [14803]: <-- [24:AT+FDCC=1,5,2,2,2,0,0,0\r]
    Feb 12 09:15:13.45: [14803]: --> [2:OK]
    Feb 12 09:15:13.45: [14803]: <-- [23:AT+FLID="NothingSetup"\r]
    Feb 12 09:15:13.61: [14803]: --> [2:OK]
    Feb 12 09:15:13.61: [14803]: DIAL 71279
    Feb 12 09:15:13.61: [14803]: <-- [11:ATDT71279@\r]
    Feb 12 09:16:09.83: [14803]: --> [9:NO ANSWER]
    Feb 12 09:16:09.83: [14803]: SEND FAILED: No answer from remote
    Feb 12 09:16:09.83: [14803]: <-- [5:ATH0\r]
    Feb 12 09:16:09.98: [14803]: --> [2:OK]
    Feb 12 09:16:09.98: [14803]: SESSION END
    
    Resulting in:
    >faxstat -s
    HylaFAX scheduler on turing.zoo.ox.ac.uk: Running
    Modem ttyf2 (271197): Waiting for modem to come ready
    
    JID  Pri S  Owner Number       Pages Dials     TTS Status
    32   124 S    mcb 71279         0:1   3:12   09:19 No answer from remote
    
    
    
    My modem manual syas that ATH0 should make the modem 'go on hook', i.e. hang
    up, but this seems to fail ...

Why do you think that it seems to fail?

I'm still not sure about it but maybe it helps (and if it helps
we should work-out the reason): try setting &D2 for ModemSetupDTRCmd;

	matthias