http://bugs.hylafax.org/show_bug.cgi?id=919
Summary: Incomplete or half page
Product: HylaFAX
Version: 4.4.1
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: faxrcvd
AssignedTo: [email protected]
ReportedBy: [email protected]
Hello
Few our our clients are facing issue like when they receive faxes they are
incomplete or half page or getting 1 or 2 page and then 3rd one half and then
faxes got interrupted, is there any resolution you can give to this issue ?
Here is one of the log file (I can provide more if wanted)
Sep 14 11:29:18.18: [ 2929]: SESSION BEGIN 000030775 14082645222
Sep 14 11:29:18.18: [ 2929]: HylaFAX (tm) Version 4.4.1
Sep 14 11:29:18.18: [ 2929]: <-- [4:ATA\r]
Sep 14 11:29:29.26: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:29.26: [ 2929]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS5'
Sep 14 11:29:29.26: [ 2929]: RECV FAX: begin
Sep 14 11:29:29.26: [ 2929]: <-- data [32]
Sep 14 11:29:29.26: [ 2929]: <-- data [2]
Sep 14 11:29:29.27: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:29.27: [ 2929]: <-- data [23]
Sep 14 11:29:29.27: [ 2929]: <-- data [2]
Sep 14 11:29:29.27: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:29.27: [ 2929]: <-- data [13]
Sep 14 11:29:29.27: [ 2929]: <-- data [2]
Sep 14 11:29:31.57: [ 2929]: --> [2:OK]
Sep 14 11:29:31.57: [ 2929]: <-- [9:AT+FRH=3\r]
Sep 14 11:29:31.94: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:33.67: [ 2929]: --> [2:OK]
Sep 14 11:29:33.67: [ 2929]: REMOTE TSI "AT&T/CVS Pharmacy"
Sep 14 11:29:33.67: [ 2929]: RECV recv TSI (sender id)
Sep 14 11:29:33.67: [ 2929]: <-- [9:AT+FRH=3\r]
Sep 14 11:29:33.68: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:33.98: [ 2929]: --> [2:OK]
Sep 14 11:29:33.98: [ 2929]: REMOTE wants 14400 bit/s
Sep 14 11:29:33.98: [ 2929]: REMOTE wants A4 page width (215 mm)
Sep 14 11:29:33.98: [ 2929]: REMOTE wants unlimited page length
Sep 14 11:29:33.98: [ 2929]: REMOTE wants 3.85 line/mm
Sep 14 11:29:33.98: [ 2929]: REMOTE wants 2-D MMR
Sep 14 11:29:33.98: [ 2929]: REMOTE wants T.30 Annex A, 256-byte ECM
Sep 14 11:29:33.98: [ 2929]: RECV recv DCS (command signal)
Sep 14 11:29:33.98: [ 2929]: RECV training at v.17 14400 bit/s
Sep 14 11:29:33.98: [ 2929]: <-- [11:AT+FRM=145\r]
Sep 14 11:29:35.76: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:37.29: [ 2929]: RECV: TCF 2736 bytes, 0% non-zero, 2712 zero-run
Sep 14 11:29:37.29: [ 2929]: --> [10:NO CARRIER]
Sep 14 11:29:37.29: [ 2929]: <-- [9:AT+FRS=7\r]
Sep 14 11:29:37.36: [ 2929]: --> [2:OK]
Sep 14 11:29:37.36: [ 2929]: TRAINING succeeded
Sep 14 11:29:37.36: [ 2929]: <-- [9:AT+FTH=3\r]
Sep 14 11:29:38.32: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:38.32: [ 2929]: <-- data [3]
Sep 14 11:29:38.32: [ 2929]: <-- data [2]
Sep 14 11:29:38.71: [ 2929]: --> [2:OK]
Sep 14 11:29:38.71: [ 2929]: <-- [11:AT+FRM=146\r]
Sep 14 11:29:40.14: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:40.49: [ 2929]: RECV received frame number 0
Sep 14 11:29:40.71: [ 2929]: RECV received frame number 1
Sep 14 11:29:40.85: [ 2929]: RECV received frame number 2
Sep 14 11:29:40.99: [ 2929]: RECV received frame number 3
Sep 14 11:29:41.13: [ 2929]: RECV received frame number 4
Sep 14 11:29:41.27: [ 2929]: RECV received frame number 5
Sep 14 11:29:41.42: [ 2929]: RECV received frame number 6
Sep 14 11:29:41.56: [ 2929]: RECV received frame number 7
Sep 14 11:29:41.70: [ 2929]: RECV received frame number 8
Sep 14 11:29:41.91: [ 2929]: RECV received frame number 9
Sep 14 11:29:42.06: [ 2929]: RECV received frame number 10
Sep 14 11:29:42.20: [ 2929]: RECV received frame number 11
Sep 14 11:29:42.34: [ 2929]: RECV received frame number 12
Sep 14 11:29:42.48: [ 2929]: RECV received frame number 13
Sep 14 11:29:42.63: [ 2929]: RECV received frame number 14
Sep 14 11:29:42.77: [ 2929]: RECV received frame number 15
Sep 14 11:29:42.91: [ 2929]: RECV received frame number 16
Sep 14 11:29:43.05: [ 2929]: RECV received frame number 17
Sep 14 11:29:43.19: [ 2929]: RECV received frame number 18
Sep 14 11:29:43.34: [ 2929]: RECV received frame number 19
Sep 14 11:29:43.55: [ 2929]: RECV received frame number 20
Sep 14 11:29:43.69: [ 2929]: RECV received frame number 21
Sep 14 11:29:43.84: [ 2929]: RECV received frame number 22
Sep 14 11:29:43.98: [ 2929]: RECV received frame number 23
Sep 14 11:29:44.12: [ 2929]: RECV received frame number 24
Sep 14 11:29:44.26: [ 2929]: RECV received frame number 25
Sep 14 11:29:44.40: [ 2929]: RECV received frame number 26
Sep 14 11:29:44.55: [ 2929]: RECV received frame number 27
Sep 14 11:29:44.69: [ 2929]: RECV received frame number 28
Sep 14 11:29:44.83: [ 2929]: RECV received frame number 29
Sep 14 11:29:45.04: [ 2929]: RECV received frame number 30
Sep 14 11:29:45.19: [ 2929]: RECV received frame number 31
Sep 14 11:29:45.33: [ 2929]: RECV received frame number 32
Sep 14 11:29:45.47: [ 2929]: RECV received frame number 33
Sep 14 11:29:45.61: [ 2929]: RECV received frame number 34
Sep 14 11:29:45.76: [ 2929]: RECV received frame number 35
Sep 14 11:29:45.90: [ 2929]: RECV received frame number 36
Sep 14 11:29:46.04: [ 2929]: RECV received frame number 37
Sep 14 11:29:46.18: [ 2929]: RECV received frame number 38
Sep 14 11:29:46.39: [ 2929]: RECV received frame number 39
Sep 14 11:29:46.54: [ 2929]: RECV received frame number 40
Sep 14 11:29:46.68: [ 2929]: RECV received frame number 41
Sep 14 11:29:46.82: [ 2929]: RECV received frame number 42
Sep 14 11:29:46.96: [ 2929]: RECV received frame number 43
Sep 14 11:29:47.11: [ 2929]: RECV received frame number 44
Sep 14 11:29:47.25: [ 2929]: RECV received frame number 45
Sep 14 11:29:47.39: [ 2929]: RECV received frame number 46
Sep 14 11:29:47.53: [ 2929]: RECV received frame number 47
Sep 14 11:29:47.68: [ 2929]: RECV received frame number 48
Sep 14 11:29:47.89: [ 2929]: RECV received frame number 49
Sep 14 11:29:48.03: [ 2929]: RECV received frame number 50
Sep 14 11:29:48.17: [ 2929]: RECV received frame number 51
Sep 14 11:29:48.31: [ 2929]: RECV received frame number 52
Sep 14 11:29:48.46: [ 2929]: RECV received frame number 53
Sep 14 11:29:48.60: [ 2929]: RECV received frame number 54
Sep 14 11:29:48.74: [ 2929]: RECV received frame number 55
Sep 14 11:29:48.88: [ 2929]: RECV received frame number 56
Sep 14 11:29:48.95: [ 2929]: RECV received frame number 57
Sep 14 11:29:48.95: [ 2929]: RECV received RCP frame
Sep 14 11:29:48.96: [ 2929]: --> [10:NO CARRIER]
Sep 14 11:29:48.96: [ 2929]: <-- [9:AT+FRH=3\r]
Sep 14 11:29:49.08: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:50.31: [ 2929]: --> [2:OK]
Sep 14 11:29:50.31: [ 2929]: RECV recv PPS (partial page signal)
Sep 14 11:29:50.31: [ 2929]: RECV recv EOP (no more pages or documents)
Sep 14 11:29:50.31: [ 2929]: RECV received 58 frames of block 1 of page 1
Sep 14 11:29:50.36: [ 2929]: RECV: 14848 bytes of data, 1077 total lines
Sep 14 11:29:50.36: [ 2929]: <-- [9:AT+FRS=7\r]
Sep 14 11:29:50.50: [ 2929]: --> [2:OK]
Sep 14 11:29:50.50: [ 2929]: <-- [9:AT+FTH=3\r]
Sep 14 11:29:51.46: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:51.46: [ 2929]: <-- data [3]
Sep 14 11:29:51.46: [ 2929]: <-- data [2]
Sep 14 11:29:51.85: [ 2929]: --> [2:OK]
Sep 14 11:29:51.85: [ 2929]: RECV send MCF (message confirmation)
Sep 14 11:29:51.85: [ 2929]: RECV FAX (000030775): from AT&T/CVS Pharmacy, page
1 in 0:21, INF, 3.85 line/mm, 2-D MMR, 14400 bit/s
Sep 14 11:29:51.85: [ 2929]: <-- [9:AT+FRH=3\r]
Sep 14 11:29:51.85: [ 2929]: RECV FAX (000030775): recvq/fax000011018.tif from
AT&T/CVS Pharmacy, route to <unspecified>, 1 pages in 0:22
Sep 14 11:29:52.24: [ 2929]: --> [7:CONNECT]
Sep 14 11:29:53.44: [ 2929]: --> [2:OK]
Sep 14 11:29:53.44: [ 2929]: RECV recv DCN (disconnect)
Sep 14 11:29:53.44: [ 2929]: RECV FAX: bin/faxrcvd "recvq/fax000011018.tif"
"ttyS5" "000030775" ""
Sep 14 11:29:53.44: [ 2929]: RECV FAX: end
Sep 14 11:29:53.44: [ 2929]: SESSION END
Thanks in advance as I am new to HylaFAX power
--
Configure bugmail: http://bugs.hylafax.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
____________________ HylaFAX(tm) Developers Mailing List ____________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe [email protected] < /dev/null
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.