Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[hylafax-users] MaxRecvPages somewhat unexpected behaviour - bug ?
Had to send 116 pages; knew that the setting of MaxRecvPages: was 100.
So I put some stacks of originals onto the Xerox (transmitter): 30, 30,
28 and 28.
Somewhat unexpectedly, the reception was in four batches of 30,30,28 and
*12*.
One can argue that these make exactly 100, so yahoo!, but I'd argue that
MaxRecvPages is supposed to be per fax; not per remote number (or
whatever happened here).
The log of the last batch looks messed up: For batches 1-3 the log looks
like
recvq/fax00783.tif (ftp://server.mydomain.com:4559/recvq/fax00783.tif):
Sender: 0389261668
Pages: 30
Quality: Normal
Page: ISO A4
Received: 2004:05:31 17:47:56
TimeToRecv: 22:23
SignalRate: 14400 bit/s
DataFormat: 2-D MR
ReceivedOn: tty02
CommID: c00001024
whereas the last batch has a log like:
recvq/fax00786.tif (ftp://server.mydomain.com:4559/recvq/fax00786.tif):
Sender: 0389261668
Pages: 12
Quality: Normal
Page: ISO A4
Received: 2004:05:31 18:51:28
TimeToRecv: 7:22
SignalRate: 14400 bit/s
DataFormat: 2-D MR
ReceivedOn: tty02
The full document was not received because:
Maximum receive page count exceeded, job terminated
---- Transcript of session follows ----
May 31 17:47:42.54: [16847]: SESSION BEGIN
...
page 1 in 0:49, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
May 31 17:48:40.15: [16847]: <-- [7:AT+FDR\r]
...
page 30 in 0:46, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
May 31 18:10:56.96: [16847]: RECV FAX
...
May 31 18:11:14.73: [16847]: --> [22:+FDCS: 0,5,0,2,1,0,0,0]
May 31 18:11:14.73: [16847]: REMOTE wants 14400 bit/s
May 31 18:11:14.73: [16847]: REMOTE wants page width 1728 pixels in 215 mm
May 31 18:11:14.73: [16847]: REMOTE wants unlimited page length
May 31 18:11:14.73: [16847]: REMOTE wants 3.85 line/mm
May 31 18:11:14.74: [16847]: REMOTE wants 2-D MR
May 31 18:11:14.74: [16847]: --> [7:CONNECT]
...
page 1 in 0:53, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
May 31 18:11:49.57: [16847]: <-- [7:AT+FDR\r]
...
page 30 in 0:36, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
May 31 18:29:37.59: [16847]: RECV FAX
...
May 31 18:29:55.34: [16847]: REMOTE wants 14400 bit/s
May 31 18:29:55.34: [16847]: REMOTE wants page width 1728 pixels in 215 mm
May 31 18:29:55.34: [16847]: REMOTE wants unlimited page length
May 31 18:29:55.34: [16847]: REMOTE wants 3.85 line/mm
May 31 18:29:55.35: [16847]: REMOTE wants 2-D MR
May 31 18:29:55.35: [16847]: --> [7:CONNECT]
...
page 28 in 0:46, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
May 31 18:51:11.13: [16847]: RECV FAX
...
[and so on, until:)
...
page 1 in 0:51, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
May 31 18:52:02.90: [16847]: <-- [7:AT+FDR\r]
...
page 12 in 0:38, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
May 31 18:58:50.24: [16847]: RECV FAX (00001024): recvq/fax00786.tif from 0389261668, route to <unspecified>, 12 pages in 7:39
May 31 18:58:50.24: [16847]: RECV FAX: Maximum receive page count exceeded, job terminated
The last log suddenly contains *all the previous events* ! This of
course will explain the unexpected end. Please check the timestamps !
The log for the last batch starts 17:47 and finishes 18:58 and contains
all faxes sent earlier.
In its header, however, it identifies correctly
TimeToRecv: 7:22
, the correct time it needed to receive the 12 faxes. These 12 are also converted and dispatched properly.
My questions:
1. Must we perceive this to be a bug ?
2. Am I correct, the MaxRecvPages are per individual session ?
Thanks in advance !
____________________ 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*