Re: [hylafax-users] COMREC received DCN

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Giuseppe Sacco wrote:

> Nov 27 10:34:23.91: [30348]: <-- [11:AT+FRM=146\r]
> Nov 27 10:34:24.40: [30348]: --> [7:CONNECT]
> Nov 27 10:34:24.40: [30348]: MODEM input buffering enabled
> Nov 27 10:34:24.40: [30348]: MODEM set XON/XOFF/FLUSH: input ignored, output generated
> Nov 27 10:34:24.75: [30348]: RECV received frame number 0
> Nov 27 10:34:24.96: [30348]: RECV received frame number 1
> Nov 27 10:34:25.17: [30348]: RECV received frame number 2
> Nov 27 10:34:25.17: [30348]: RECV received RCP frame
> Nov 27 10:34:25.17: [30348]: MODEM set XON/XOFF/DRAIN: input ignored, output disabled
> Nov 27 10:34:25.17: [30348]: MODEM input buffering disabled
> Nov 27 10:34:25.23: [30348]: --> [10:NO CARRIER]
> Nov 27 10:34:25.23: [30348]: <-- [9:AT+FRH=3\r]
> Nov 27 10:34:25.86: [30348]: --> [7:CONNECT]
> Nov 27 10:34:26.77: [30348]: --> HDLC<5:FF C8 DF 59 6F>
> Nov 27 10:34:26.78: [30348]: --> [2:OK]
> Nov 27 10:34:26.78: [30348]: RECV recv DCN (disconnect)

The sender machine aborted the fax.  That's very clear.  I would assume 
that the sender would know why.  (Likely they pushed "stop".)

HylaFAX could employ some logic here in recognizing the send-abort and 
not trigger an error-like condition... but for now we get to just ignore 
most "COMREC received DCN" cases.  (I say "most" because in some cases 
it will not necessarily be send-abort.)

Lee.

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*