Hylafax Mailing List Archives

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

[hylafax-users] Bad TIF files created on some faxes



Lately it seems that half the faxes I receive (HylaFax v4.2.1, on Linux) are bad.

A bad fax generates a non-zero-length TIF file which is invalid. 
(Several different graphics applications tell me that the file is corrupted.)
When I look at the log files I see statements like the ones below.
The bad faxes all have "RECV received frame number" log entries and the
good faxes do not.

I'm using a FM56-ITU/2 modem (http://english.aopen.com.tw/products/modem/fm56itu2.htm),
and have been for several years.

Can anyone advise me on what to do to fix this problem?

Thanks.

---------------------

Jun 01 08:58:12.51: [ 1739]: SESSION BEGIN 000000357 13178772031
Jun 01 08:58:12.51: [ 1739]: HylaFAX (tm) Version 4.2.1
Jun 01 08:58:12.51: [ 1739]: <-- [4:ATA\r]
Jun 01 08:58:18.57: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:18.58: [ 1739]: ANSWER: FAX CONNECTION  DEVICE '/dev/fax'
Jun 01 08:58:18.58: [ 1739]: RECV FAX: begin
Jun 01 08:58:18.60: [ 1739]: <-- data [32]
Jun 01 08:58:18.60: [ 1739]: <-- data [2]
Jun 01 08:58:20.50: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:20.50: [ 1739]: <-- data [23]
Jun 01 08:58:20.50: [ 1739]: <-- data [2]
Jun 01 08:58:21.33: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:21.33: [ 1739]: <-- data [10]
Jun 01 08:58:21.33: [ 1739]: <-- data [2]
Jun 01 08:58:21.90: [ 1739]: --> [2:OK]
Jun 01 08:58:21.90: [ 1739]: <-- [9:AT+FRH=3\r]
Jun 01 08:58:22.40: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:23.85: [ 1739]: --> [2:OK]
Jun 01 08:58:23.85: [ 1739]: REMOTE TSI "7032693092"
Jun 01 08:58:23.85: [ 1739]: <-- [9:AT+FRH=3\r]
Jun 01 08:58:23.86: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:24.16: [ 1739]: --> [2:OK]
Jun 01 08:58:24.16: [ 1739]: REMOTE wants 14400 bit/s
Jun 01 08:58:24.16: [ 1739]: REMOTE wants A4 page width (215 mm)
Jun 01 08:58:24.16: [ 1739]: REMOTE wants unlimited page length
Jun 01 08:58:24.16: [ 1739]: REMOTE wants 3.85 line/mm
Jun 01 08:58:24.16: [ 1739]: REMOTE wants 1-D MH
Jun 01 08:58:24.16: [ 1739]: REMOTE wants T.30 Annex A, 256-byte ECM
Jun 01 08:58:24.16: [ 1739]: RECV training at v.17 14400 bit/s
Jun 01 08:58:24.16: [ 1739]: <-- [11:AT+FRM=145\r]
Jun 01 08:58:25.90: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:27.44: [ 1739]: RECV: TCF 2747 bytes, 1% non-zero, 2697 zero-run
Jun 01 08:58:27.45: [ 1739]: --> [10:NO CARRIER]
Jun 01 08:58:27.45: [ 1739]: DELAY 75 ms
Jun 01 08:58:27.53: [ 1739]: TRAINING succeeded
Jun 01 08:58:27.53: [ 1739]: <-- [9:AT+FTH=3\r]
Jun 01 08:58:27.58: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:27.58: [ 1739]: <-- data [3]
Jun 01 08:58:27.58: [ 1739]: <-- data [2]
Jun 01 08:58:28.90: [ 1739]: --> [2:OK]
Jun 01 08:58:28.90: [ 1739]: <-- [11:AT+FRM=146\r]
Jun 01 08:58:29.77: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:30.46: [ 1739]: RECV received frame number 0
Jun 01 08:58:30.61: [ 1739]: RECV received frame number 1
Jun 01 08:58:30.77: [ 1739]: RECV received frame number 2
Jun 01 08:58:30.93: [ 1739]: RECV received frame number 3
Jun 01 08:58:31.08: [ 1739]: RECV received frame number 4
Jun 01 08:58:31.16: [ 1739]: RECV received frame number 5
Jun 01 08:58:31.31: [ 1739]: RECV received frame number 6
Jun 01 08:58:31.47: [ 1739]: RECV received frame number 7
Jun 01 08:58:31.61: [ 1739]: RECV received frame number 8
Jun 01 08:58:31.76: [ 1739]: RECV received frame number 9
Jun 01 08:58:31.92: [ 1739]: RECV received frame number 10
Jun 01 08:58:32.07: [ 1739]: RECV received frame number 11
Jun 01 08:58:32.22: [ 1739]: RECV received frame number 12
Jun 01 08:58:32.38: [ 1739]: RECV received frame number 13
Jun 01 08:58:32.53: [ 1739]: RECV received frame number 14
Jun 01 08:58:32.68: [ 1739]: RECV received frame number 15
Jun 01 08:58:32.82: [ 1739]: RECV received frame number 16
Jun 01 08:58:32.98: [ 1739]: RECV received frame number 17
Jun 01 08:58:33.13: [ 1739]: RECV received frame number 18
Jun 01 08:58:33.28: [ 1739]: RECV received frame number 19
Jun 01 08:58:33.44: [ 1739]: RECV received frame number 20
Jun 01 08:58:33.59: [ 1739]: RECV received frame number 21
Jun 01 08:58:33.75: [ 1739]: RECV received frame number 22
Jun 01 08:58:33.83: [ 1739]: RECV received frame number 23
Jun 01 08:58:33.98: [ 1739]: RECV received frame number 24
Jun 01 08:58:34.14: [ 1739]: RECV received frame number 25
Jun 01 08:58:34.28: [ 1739]: RECV received frame number 26
Jun 01 08:58:34.44: [ 1739]: RECV received frame number 27
Jun 01 08:58:34.60: [ 1739]: RECV received frame number 28
Jun 01 08:58:34.76: [ 1739]: RECV received frame number 29
Jun 01 08:58:34.91: [ 1739]: RECV received frame number 30
Jun 01 08:58:35.06: [ 1739]: RECV received frame number 31
Jun 01 08:58:35.21: [ 1739]: RECV received frame number 32
Jun 01 08:58:35.36: [ 1739]: RECV received frame number 33
Jun 01 08:58:35.52: [ 1739]: RECV received frame number 34
Jun 01 08:58:35.66: [ 1739]: RECV received frame number 35
Jun 01 08:58:35.80: [ 1739]: RECV received frame number 36
Jun 01 08:58:35.95: [ 1739]: RECV received frame number 37
Jun 01 08:58:36.09: [ 1739]: RECV received frame number 38
Jun 01 08:58:36.25: [ 1739]: RECV received frame number 39
Jun 01 08:58:36.41: [ 1739]: RECV received frame number 40
Jun 01 08:58:36.73: [ 1739]: RECV received frame number 41
Jun 01 08:58:37.37: [ 1739]: RECV received frame number 42
Jun 01 08:58:38.09: [ 1739]: RECV received frame number 43
Jun 01 08:58:38.69: [ 1739]: RECV received frame number 44
Jun 01 08:58:39.37: [ 1739]: RECV received frame number 45
Jun 01 08:58:40.12: [ 1739]: RECV received frame number 46
Jun 01 08:58:40.72: [ 1739]: RECV received frame number 47
Jun 01 08:58:40.72: [ 1739]: RECV received RCP frame
Jun 01 08:58:40.85: [ 1739]: --> [10:NO CARRIER]
Jun 01 08:58:40.85: [ 1739]: <-- [9:AT+FRH=3\r]
Jun 01 08:58:41.21: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:42.10: [ 1739]: --> [2:OK]
Jun 01 08:58:42.10: [ 1739]: RECV recv PPS (partial page signal)
Jun 01 08:58:42.10: [ 1739]: RECV recv EOP (no more pages or documents)
Jun 01 08:58:42.10: [ 1739]: RECV received 48 frames of block 1 of page 1
Jun 01 08:58:42.18: [ 1739]: RECV: 12288 bytes of data, 1047 total lines
Jun 01 08:58:42.18: [ 1739]: <-- [9:AT+FRS=7\r]
Jun 01 08:58:42.31: [ 1739]: --> [2:OK]
Jun 01 08:58:42.31: [ 1739]: <-- [9:AT+FTH=3\r]
Jun 01 08:58:42.36: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:42.36: [ 1739]: <-- data [3]
Jun 01 08:58:42.36: [ 1739]: <-- data [2]
Jun 01 08:58:43.68: [ 1739]: --> [2:OK]
Jun 01 08:58:43.68: [ 1739]: RECV send MCF (message confirmation)
Jun 01 08:58:43.68: [ 1739]: RECV FAX (000000357): from 7032693092, page 1 in 0:16, INF, 3.85 line/mm, 1-D MH, 14400 bit/s
Jun 01 08:58:43.69: [ 1739]: RECV FAX (000000357): recvq/fax000000357.tif from 7032693092, route to <unspecified>, 1 pages in 0:25
Jun 01 08:58:43.69: [ 1739]: <-- [9:AT+FRH=3\r]
Jun 01 08:58:44.12: [ 1739]: --> [7:CONNECT]
Jun 01 08:58:45.04: [ 1739]: --> [2:OK]
Jun 01 08:58:45.04: [ 1739]: RECV FAX: bin/faxrcvd "recvq/fax000000357.tif" "fax" "000000357" "" "" ""
Jun 01 08:58:45.04: [ 1739]: RECV FAX: end
Jun 01 08:58:45.04: [ 1739]: SESSION END


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



Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services