HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
[hylafax-users] Sending empty/blank pages
Hello,
I am having a problem that I can't find a solution to and I hope someone
on this list can help me:
When sending faxes with more than one page all pages after the first one
are empty when they reach their destination. Well, nearly empty: the
only thing all pages after the first one contain is the header line,
which states the sender, the date and the time.
I tried to trace this down, but I until now I haven't found any clues.
The log file states that all pages where sent:
Jun 25 23:07:41.30: [ 1659]: SESSION BEGIN 000000141 +49.5251.xxxxxx
Jun 25 23:07:41.30: [ 1659]: SEND FAX: JOB 141 DEST yyyyyy COMMID 000000188
Jun 25 23:07:41.30: [ 1659]: Try to connect to fax number yyyyy in
Hylafax mode on controller 1.
Jun 25 23:07:41.30: [ 1659]: Dial and starting transfer of TIFF-File
docq/doc141.ps;01 with fine resolution.
Jun 25 23:07:59.81: [ 1659]: Connection established.
Jun 25 23:07:59.81: [ 1659]: BaudRate = 14400
Jun 25 23:07:59.81: [ 1659]: Flags = HighRes, MR_compr, MMR_compr
Jun 25 23:08:07.88: [ 1659]: Page 1 was sent.
Jun 25 23:08:35.18: [ 1659]: Page 2 was sent. - Last Page!
Jun 25 23:08:35.19: [ 1659]: Fax file completely transfered to CAPI.
Jun 25 23:08:50.28: [ 1659]: Connection dropped with Reason 0x3400 (No
additional information).
This is true: when I send two pages, the recipient will receive two
pages, but only the first one will contain text.
The ps file which is created in the process and which is stored in docq/
is intact: it shows all pages and all text and pictures.
The problem first appeared sometime in the beginning this year. I am
sorry, but I can not tell any more precisely, because not every
recipient told me about it. But I know that until some time last year I
was able to send faxes that contained more than one page.
It doesn't matter if I send the fax via command line or via GUI like
kdeprintfax. It also doesn't matter which resolution I use.
I am using:
- KUbuntu 7.10
- Kernel 2.6.25.8
- Hylafax 5.2
- AVM B1 PCI
- capi4hylafax 01.03.00.99.svn.300-5
I also had an answer in a newsgroup from another person who has the same
problem. He uses:
- Suse Linux 8.2
- 2.4.20 Kernel
- HylaFAX version 4.1.5
- AVM B1 PCI
- B1PCI
So it it neither a bug in the distribution, nor in the kernel itself,
unless kernel 2.4 and 2.6 use the same broken code for the capi devices.
Does anyone have any idea or clue what could be causing this effect?
--
Wolfgang Klein, DE - Paderborn ,_,
PGP-Schlüssel per e-mail anfordern: (o,o) Request PGP key by e-mail:
"Bitte PGP-Schluessel senden" {' '} "Please send PGP key"
=====================================#=#==============================
____________________ 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*