Re: [hylafax-users] Hardcoded quality settings. Why?

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Aivils Stoss wrote:

> 	I use hylafax several years. It typicaly receives around 35000 pages per 
> mount . Normal hylafax drop to many pages because of poor voice network 
> quality (VOIP included). I solve the problem when i recompile faxgetty with
> another quality settings. Here is a patch, a bit obsolete:
> diff -Nurp hylafax-4.1.8/faxd/ModemConfig.c++ 
> hylafax-4.1.8-chg/faxd/ModemConfig.c++
> --- hylafax-4.1.8/faxd/ModemConfig.c++	2003-03-26 06:41:55.000000000 +0200
> +++ hylafax-4.1.8-chg/faxd/ModemConfig.c++	2004-03-08 12:13:01.000000000 +0200
> @@ -176,8 +176,8 @@ static struct {
>     u_int		 def;
> } numbers[] = {
> { "ringtimeout",		&ModemConfig::ringTimeout,	     6000 },
> -{ "percentgoodlines",		&ModemConfig::percentGoodLines,	     95 },
> -{ "maxconsecutivebadlines",	&ModemConfig::maxConsecutiveBadLines,5 },
> +{ "percentgoodlines",		&ModemConfig::percentGoodLines,	     5 },
> +{ "maxconsecutivebadlines",	&ModemConfig::maxConsecutiveBadLines,200 },
> { "modemresetdelay",		&ModemConfig::resetDelay,	     2600 },
> { "modemdtrdropdelay",		&ModemConfig::dtrDropDelay,	     75 },
> { "modembaudratedelay",		&ModemConfig::baudRateDelay,	     10 },
>
> Unfortunately i cannot think up try , who show me how many pages are realy 
> droped. Is a good think try out another quality settings? I afraid i will 
> destroy that stupid document workflow when i change the settings.
> I worry about additional 75000 pages per month which are planed in the 2007.
>
> Hylafax 4.1.8 in use.

You didn't need to change the code to modify PercentGoodLines or 
MaxConsecutiveBadLines.  Those are both configurable.  You merely 
changed the defaults.

As for the values that they were changed to... 5% good lines on a fax 
page with the max number of consecutive bad lines being 200 (an inch!) 
is quite extreme measures.  The original defaults should be adequate for 
the vast majority of implementations - with tolerances increasing only 
slightly for places with poor phone line quality.

Faxing over internet-run VoIP channels is not extremely good for 
reliability.

Upgrading to any 4.2 version or later will get you ECM, and that will 
probably help out immensely.

I have done a fair amount of work in HylaFAX+ to be able to get the 
Class 1 driver to tolerate most of the chaos created by faxing on VoIP 
channels... and I would expect that your best chance for success will be 
with it.

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*