Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Newbie:facsimile not received
Hi Lee,
This happens to all senders. I followed the installation and
configuration of Hylafax to the letter. If it would help clarify the
issue, there are two types of errors that I get, first is the one I
mentioned, and second is listed below
Sender:
Pages: 1
Quality: Fine
Page: 1728 by 215
Received: 2006:01:31 19:08:41
TimeToRecv: 2:13
SignalRate: 9600 bit/s
DataFormat: 2-D MR
ErrCorrect: No
ReceivedOn: ttyS2
The full document was not received because:
COMREC error
---- Transcript of session follows ----
Jan 31 19:08:19.79: [ 2336]: SESSION BEGIN 000000012 6329149999
Jan 31 19:08:19.79: [ 2336]: HylaFAX (tm) Version 4.2.5
Jan 31 19:08:19.79: [ 2336]: <-- [19:AT+FCC=,,,,,,,,0;A\r]
Jan 31 19:08:37.34: [ 2336]: --> [4:+FCO]
Jan 31 19:08:37.34: [ 2336]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS2'
Jan 31 19:08:37.34: [ 2336]: RECV FAX: begin
Jan 31 19:08:37.39: [ 2336]: --> [27:+FTI:" "]
Jan 31 19:08:37.39: [ 2336]: REMOTE TSI ""
Jan 31 19:08:37.71: [ 2336]: --> [20:+FCS:1,3,0,2,1,0,0,0]
Jan 31 19:08:37.71: [ 2336]: REMOTE wants 9600 bit/s
Jan 31 19:08:37.71: [ 2336]: REMOTE wants A4 page width (215 mm)
Jan 31 19:08:37.71: [ 2336]: REMOTE wants unlimited page length
Jan 31 19:08:37.71: [ 2336]: REMOTE wants 7.7 line/mm
Jan 31 19:08:37.71: [ 2336]: REMOTE wants 2-D MR
Jan 31 19:08:37.72: [ 2336]: --> [2:OK]
Jan 31 19:08:37.72: [ 2336]: <-- [7:AT+FDR\r]
Jan 31 19:08:41.68: [ 2336]: --> [7:CONNECT]
Jan 31 19:08:41.68: [ 2336]: RECV: begin page
Jan 31 19:08:41.68: [ 2336]: RECV: send trigger 022
Jan 31 19:08:41.68: [ 2336]: Copy quality checking performed by modem
Jan 31 19:09:39.03: [ 2336]: RECV: 32711 bytes of data, 677 total lines
Jan 31 19:10:36.08: [ 2336]: RECV: 32710 bytes of data, 1099 total lines
Jan 31 19:10:50.36: [ 2336]: RECV: 8316 bytes of data, 1666 total lines
Jan 31 19:10:50.41: [ 2336]: --> [24:+FPS:2,1662,357,21,42903]
Jan 31 19:10:50.68: [ 2336]: --> [6:+FET:2]
Jan 31 19:10:50.68: [ 2336]: RECV recv EOP (no more pages or documents)
Jan 31 19:10:50.69: [ 2336]: --> [2:OK]
Jan 31 19:10:50.69: [ 2336]: RECV send RTN (retrain negative)
Jan 31 19:10:50.69: [ 2336]: <-- [7:AT+FDR\r]
Jan 31 19:10:53.83: [ 2336]: --> [7:+FHS:72]
Jan 31 19:10:53.83: [ 2336]: REMOTE HANGUP: COMREC error (code 72)
Jan 31 19:10:53.83: [ 2336]: RECV keeping unconfirmed page
Jan 31 19:10:53.83: [ 2336]: RECV FAX (000000012): from , page 1 in 2:13, INF, 7.7 line/mm, 2-D MR, 9600 bit/s
Jan 31 19:10:53.83: [ 2336]: RECV FAX (000000012): recvq/fax000000008.tif from , route to <unspecified>, 1 pages in 2:16
Jan 31 19:10:53.83: [ 2336]: RECV FAX: COMREC error
Jan 31 19:10:53.83: [ 2336]: RECV FAX (000000012): session with terminated abnormally: COMREC error
Jan 31 19:10:53.83: [ 2336]: RECV FAX: bin/faxrcvd "recvq/fax000000008.tif" "ttyS2" "000000012" "COMREC error"
Jan 31 19:10:53.84: [ 2336]: RECV FAX: end
Jan 31 19:10:53.84: [ 2336]: SESSION END
Lee Howard wrote:
Pinoy Bug wrote:
Feb 03 16:54:53.20: [ 2333]: <-- [10:AT+FRM=96\r]
Feb 03 16:54:53.60: [ 2333]: --> [7:CONNECT]
Feb 03 16:54:53.60: [ 2333]: RECV: begin page
Feb 03 16:57:20.21: [ 2333]: RECV: Missing EOL after 5 seconds
Feb 03 16:57:20.21: [ 2333]: RECV: end page
Feb 03 16:57:22.21: [ 2333]: MODEM <Timeout>
Feb 03 16:57:24.21: [ 2333]: MODEM <Empty line>
Feb 03 16:57:26.22: [ 2333]: MODEM <Empty line>
Feb 03 16:57:26.42: [ 2333]: MODEM <Timeout>
Feb 03 16:57:26.42: [ 2333]: RECV FAX (000000021):
recvq/fax000000017.tif from , route to <unspecified>, 0 pages in 2:43
Feb 03 16:57:26.42: [ 2333]: RECV FAX: T.30 T2 timeout, expected page
not received
Feb 03 16:57:26.42: [ 2333]: <-- [9:AT+FTH=3\r]
Feb 03 16:57:27.49: [ 2333]: --> [7:CONNECT]
Feb 03 16:57:27.98: [ 2333]: --> [2:OK]
Does this happen with all fax senders or only a few select ones? If
the latter, what are the fax senders?
The log says that it went to find the V.29 9600 bps carrier, found it
0.4 s later, but for over 2 minutes no real image data was received at
all from the sender. Then HylaFAX attempted to abort the reception
(forcing the modem back into command mode), and found the modem to be
in command-mode already.
So, the sender could be doing something bizarre, but the modem also
appears to be doing something bizarre.
If this is being caused by a unique sender, then the problem may be
limited. However, it would appear that any fix is going to have to
come from MultiTech... unless there's some configuration or
installation change that can be made on your end.
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*