Re: [hylafax-users] Empty pages

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Wolfgang Klein wrote:
> If I use Hylafax and Capi4hylafax then some (and only some!) recipients
> complain about incomplete faxes. Whenever I send faxes containing more
> than one page to those recipients, only the first page contains
> information. The second and following pages are empty except for the
> tag-line.
>   

I try to avoid commenting on CAPI4HylaFAX cases because I know next to 
nothing about it.  My understanding is that CAPI4HylaFAX development has 
essentially ceased.  Its developers never responded to my previous 
inquires to work in a more concerted approach.  It's quite possible that 
something in "recent" HylaFAX development has broken functionality with 
something in CAPI4HylaFAX, but I honestly don't know.

The problem sounds to me like CAPI4HylaFAX's faxsend doesn't like the 
image that was prepared by faxq... at least on pages after the first.

I believe that there is an Asterisk channel driver for CAPI.  It would 
be a bit of work, but I've heard of people setting up Asterisk and then 
IAXmodem to get their CAPI devices working in a better way.  (Thus 
faxsend and faxgetty are the "modern" versions that come with HylaFAX.)

> You know much more about faxes than I do, so I'd like to ask you what
> you think about this: could it be that those empty pages occur when the
> recipients are connected by VoIP, most probably without even knowing it?
> Could the explanation be that simple?
>   

It's a possibility.  However, if it's *always* cutting off right after 
the tag line, then I doubt it's the case.  If it were VoIP issues then 
the image would get cut off at seemingly random places on the page.

> I checked and double-checked every file that is involved in the process
> of sending faxes as far as I am able to: the generated tiff and
> postscript files are complete, there's nothing missing there, so the
> pages must get corrupted while actually being sent.
>   

Yes, either in the transmission of them over-the-wire or in the tagline 
imaging process that faxsend does.

> I also tried several versions and combinations of Hylafax and
> Capi4hylafax and they all show the described behaviour, so that should
> prove that neither of those two programs is buggy.
>   

I wouldn't make that conclusion so quickly.  I'm quite certain there are 
some bugs in both.  However, as HylaFAX isn't involved in the faxsend 
process in a CAPI4HylaFAX configuration then HylaFAX is not likely 
responsible.

> But, on the other hand, if I use Capisuite, which brings its own
> capisuitefax to send faxes, all page are sent correctly and contain
> every piece of information when they arrive.
>   

Which points more and more to the CAPI4HylaFAX faxsend program being 
culpable.

> So, either Capisuite can deal with buggy phone lines while Capi4hylafax
> can't, or there has to be a really nasty big bug in my system which only
> makes itself noticed when I use Capi4hylafax.
>
> Do you (or any one else) have any idea what might be wrong?

My bet is on a CAPI4HylaFAX that is surfacing due to some kind of 
configuration that is somewhat unique on your system while somewhat 
uncommon on other CAPI4HylaFAX systems.

Thanks,

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*