HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] The tif images doesn't exist in the recvq directory



Thank you for your good answer Lee! I'm using Hylafax 4.4.3 with USR Sportster external modem. Can you answer one more question? Which modem is supposed to be better?

-----Message d'origine-----
De : Lee Howard [mailto:lee.howard@xxxxxxxxxxxx] 
Envoyé : 3 décembre, 2008 21:09
À : Marcelo Godois Tavares
Cc : Hylafax Users
Objet : Re: [hylafax-users] The tif images doesn't exist in the recvq directory

Marcelo Godois Tavares wrote:
>
> Dec 02 12:51:27.94: [ 6619]: <-- [11:AT+FRM=146\r]
>
> Dec 02 12:51:34.94: [ 6619]: MODEM TIMEOUT: reading line from modem
>
> Dec 02 12:51:34.94: [ 6619]: <-- data [1]
>
> Dec 02 12:51:35.14: [ 6619]: MODEM TIMEOUT: reading line from modem
>
> Dec 02 12:51:35.14: [ 6619]: MODEM <Timeout>
>
> Dec 02 12:51:35.14: [ 6619]: <-- [9:AT+FRH=3\r]
>
> Dec 02 12:51:37.99: [ 6619]: --> [7:CONNECT]
>
> Dec 02 12:51:40.27: [ 6619]: --> [15:14 63 F6 96 93 2A 03 D9 1E 22 CC 
> A1 00 10 03]
>
> Dec 02 12:51:40.27: [ 6619]: --> [5:ERROR]
>

These are both a series of modem errors.  First the modem's V.17 
demodulator isn't compatible with the signal.  Second, the modem's V.21 
HDLC function is also less than perfect.  So with +FRH=146 it won't 
detect the signal, but with +FRH=3 it mistakenly thinks that it's V.21 HDLC.

> Dec 02 12:51:41.71: [ 6619]: <-- [9:AT+FRH=3\r]
>
> Dec 02 12:51:47.85: [ 6619]: --> [7:CONNECT]
>
> Dec 02 12:51:57.85: [ 6619]: --> [16:52 C3 F0 47 B1 47 A1 A6 41 1B 38 
> 1E C5 DD EA 00]
>
> Dec 02 12:51:57.85: [ 6619]: MODEM TIMEOUT: receiving HDLC frame data
>
> Dec 02 12:51:57.85: [ 6619]: <-- data [1]
>
> Dec 02 12:51:57.85: [ 6619]: --> [2:OK]
>

Again, it's a fun modem.  :-)

> Dec 02 12:51:59.27: [ 6619]: RECV FAX (000001548): session with 
> ENTERPRISE terminated abnormally: Failed to properly detect high-speed 
> data carrier.
>
> Dec 02 12:51:59.27: [ 6619]: RECV FAX: bin/faxrcvd 
> "recvq/fax000001618.tif" "ttyS1" "000001548" "Failed to properly 
> detect high-speed data carrier."
>

HylaFAX always opens a TIFF file, but in this case the file may be 
closed and removed because no data was received.  Your faxrcvd should be 
capable of handling this condition.

> Dec 02 15:39:35.45: [ 6619]: <-- [11:AT+FRM=146\r]
>
> Dec 02 15:39:36.23: [ 6619]: --> [7:CONNECT]
>
> Dec 02 15:39:36.23: [ 6619]: MODEM input buffering enabled
>
> Dec 02 15:39:36.23: [ 6619]: MODEM set XON/XOFF/FLUSH: input ignored, 
> output generated
>
> Dec 02 15:39:36.23: [ 6619]: RECV: begin page
>
> Dec 02 15:40:10.55: [ 6619]: RECV/CQ: Bad 1D pixel count, row 2198, 
> got 0, expected 1728
>
> Dec 02 15:40:10.55: [ 6619]: RECV/CQ: Bad 1D pixel count, row 2199, 
> got 0, expected 1728
>
> Dec 02 15:40:10.55: [ 6619]: RECV/CQ: Bad 1D pixel count, row 2200, 
> got 0, expected 1728
>
> Dec 02 15:40:10.55: [ 6619]: RECV/CQ: Bad 1D pixel count, row 2201, 
> got 0, expected 1728
>
> Dec 02 15:40:10.69: [ 6619]: RECV/CQ: Adjusting for RTC found at row 2198
>
> Dec 02 15:40:10.69: [ 6619]: RECV: 2198 total lines, 0 bad lines, 0 
> consecutive bad lines
>
> Dec 02 15:40:10.69: [ 6619]: RECV: end page
>
> Dec 02 15:40:10.69: [ 6619]: --> [10:NO CARRIER]
>
> Dec 02 15:40:10.69: [ 6619]: <-- [9:AT+FRH=3\r]
>
> Dec 02 15:40:11.09: [ 6619]: --> [7:CONNECT]
>
> Dec 02 15:40:11.93: [ 6619]: --> HDLC<5:FF C8 F2 AC A0>
>
> Dec 02 15:40:11.93: [ 6619]: --> [2:OK]
>
> Dec 02 15:40:11.93: [ 6619]: RECV recv MPS (more pages, same document)
>

Okay, good.  Page 1.

> Dec 02 15:40:11.93: [ 6619]: DELAY 70 ms
>
> Dec 02 15:40:12.00: [ 6619]: <-- [9:AT+FTH=3\r]
>
> Dec 02 15:40:42.00: [ 6619]: MODEM TIMEOUT: reading line from modem
>
> Dec 02 15:40:42.00: [ 6619]: MODEM <Timeout>
>

Um, but here the modem botches things.  It's the  same modem.  Is this, 
by chance, a USR modem?

> Dec 02 15:40:42.02: [ 6619]: RECV FAX (000001622): 
> recvq/fax000001698.tif from 0q      62-555-3153, route to 
> <unspecified>, 0 pages in 1:17
>

Hrmm... this is interesting because it would appear that HylaFAX *lost* 
the page that was just received... although the receipt was not 
confirmed to the sender.

You must have SaveUnconfirmedPages set to "no" in your modem config 
file... or there is a bug in your version of HylaFAX.  I just tested 
this exact scenario with HylaFAX+ 5.2.7 and the page was saved as expected.

Thanks,

Lee.

-- 
*Lee Howard*
*Mainpine, Inc. Software Development Lead*
Tel: +1 866 363 6680 ext 805 | Fax: +1 360 462 8160
lee.howard@xxxxxxxxxxxx | www.mainpine.com


____________________ 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*




Project hosted by iFAX Solutions