Debian Bug report logs - #309684
hylafax-server: MaxConcurrentCalls not being respected

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: John Goerzen <jgoerzen@complete.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: hylafax-server: MaxConcurrentCalls not being respected

Date: Wed, 18 May 2005 15:06:14 -0500

Package: hylafax-server
Version: 1:4.2.1-5
Severity: normal

This bug also appeared after our pugrade from 4.1.x.

According to the docs, MaxConcurrentCalls defaults to 1.  This is as we want
it.  We have two outgoing FAX lines.

This setting doesn't seem to be getting respected anymore.  We're seeing a
number of situations where one line calls a particular FAX number, and the
other line then tries to call it also to deliver a different document.  The
second line gets a busy signal, of course.

In 4.1.x, the second line wouldn't even attempt to dial a number that the
first line was already working with, and that's the behavior we want.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: LANG=C, LC_CTYPE=C

Versions of packages hylafax-server depends on:
ii  debconf          1.4.30.5                Debian configuration management sy
ii  gs               8.01-5                  Transitional package
ii  gs-gpl [gs]      8.01-5                  The GPL Ghostscript PostScript int
ii  hylafax-client   1:4.2.1-5               Flexible client/server fax softwar
ii  libc6            2.3.2.ds1-16            GNU C Library: Shared libraries an
ii  libgcc1          1:3.4.1-4sarge1         GCC support library
ii  libpam0g         0.76-22                 Pluggable Authentication Modules l
ii  libstdc++5       1:3.3.4-6sarge1.2       The GNU Standard C++ Library v3
ii  libtiff-tools    3.7.2-2                 TIFF manipulation and conversion t
ii  libtiff4         3.7.2-2                 Tag Image File Format (TIFF) libra
ii  mailx            1:8.1.2-0.20040524cvs-1 A simple mail user agent
ii  mawk [awk]       1.3.3-11                a pattern scanning and text proces
ii  mime-codecs      7.18-9                  Fast Quoted-Printable and BASE64 M
ii  psmisc           21.5-1                  Utilities that use the proc filesy
ii  sed              4.1.2-1                 The GNU sed stream editor
ii  zlib1g           1:1.2.1.1-7             compression library - runtime

-- debconf information excluded

Message #10 received at 309684@bugs.debian.org (full text, mbox, reply):

From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>

To: 309684@bugs.debian.org, 309684-submitter@bugs.debian.org

Subject: Re: Bug#309684: hylafax-server: MaxConcurrentCalls not being respected

Date: Fri, 20 May 2005 16:32:54 +0200

Il giorno mer, 18-05-2005 alle 15:06 -0500, John Goerzen ha scritto:
> Package: hylafax-server
> Version: 1:4.2.1-5
> Severity: normal
> 
> This bug also appeared after our pugrade from 4.1.x.
> 
> According to the docs, MaxConcurrentCalls defaults to 1.  This is as we want
> it.  We have two outgoing FAX lines.

Thanks for reporting the problem, I am going to work on it tomorrow.

Bye,
Giuseppe

Message #18 received at 309684@bugs.debian.org (full text, mbox, reply):

From: Giuseppe Sacco <eppesuig@debian.org>

To: 309684-submitter@bugs.debian.org, 309684@bugs.debian.org

Subject: Re: Bug#309684: hylafax-server: MaxConcurrentCalls not being respected

Date: Sun, 22 May 2005 18:31:24 +0200

Il giorno mer, 18-05-2005 alle 15:06 -0500, John Goerzen ha scritto:
> Package: hylafax-server
> Version: 1:4.2.1-5
> Severity: normal
> 
> This bug also appeared after our pugrade from 4.1.x.
> 
> According to the docs, MaxConcurrentCalls defaults to 1.  This is as we want
> it.  We have two outgoing FAX lines.
> 
> This setting doesn't seem to be getting respected anymore.  We're seeing a
> number of situations where one line calls a particular FAX number, and the
> other line then tries to call it also to deliver a different document.  The
> second line gets a busy signal, of course.
[...]

I cannot reproduce the problem with 4.2.1-6, since I have a problem on
the second modem :-) Please patient a little bit.

In the meantime, could you plese use DestControl files and see if this
work as expected (this might be a workaround)?

Please note that you may have a line in "destctrls" file that will match
every destinations, as in:

.* MaxConcurrentCalls = 1

Thanks,
Giuseppe

Message #26 received at 309684@bugs.debian.org (full text, mbox, reply):

From: John Goerzen <jgoerzen@complete.org>

To: Giuseppe Sacco <eppesuig@debian.org>, 309684-quiet@bugs.debian.org

Cc: 309684-submitter@bugs.debian.org, 309684@bugs.debian.org

Subject: Re: Bug#309684: hylafax-server: MaxConcurrentCalls not being respected

Date: Mon, 23 May 2005 11:36:48 -0500

On Sun, May 22, 2005 at 06:31:24PM +0200, Giuseppe Sacco wrote:
> I cannot reproduce the problem with 4.2.1-6, since I have a problem on
> the second modem :-) Please patient a little bit.
> 
> In the meantime, could you plese use DestControl files and see if this
> work as expected (this might be a workaround)?

Will do.  I'm away from the office for another week, so this may take a
little bit too, but I'll let you know.

-- John

> 
> Please note that you may have a line in "destctrls" file that will match
> every destinations, as in:
> 
> .* MaxConcurrentCalls = 1
> 
> Thanks,
> Giuseppe
> 
> 
> 

-- 
John Goerzen
Author, Foundations of Python Network Programming
http://www.amazon.com/exec/obidos/tg/detail/-/1590593715

Message #39 received at 309684@bugs.debian.org (full text, mbox, reply):

From: Giuseppe Sacco <eppesuig@debian.org>

To: 309684-submitter@bugs.debian.org

Cc: 309684@bugs.debian.org

Subject: Re: Bug#309684: hylafax-server: MaxConcurrentCalls not being respected

Date: Wed, 04 Jan 2006 11:54:19 +0100

Il giorno lun, 23/05/2005 alle 11.36 -0500, John Goerzen ha scritto:
> On Sun, May 22, 2005 at 06:31:24PM +0200, Giuseppe Sacco wrote:
> > I cannot reproduce the problem with 4.2.1-6, since I have a problem on
> > the second modem :-) Please patient a little bit.
> > 
> > In the meantime, could you plese use DestControl files and see if this
> > work as expected (this might be a workaround)?
> 
> Will do.  I'm away from the office for another week, so this may take a
> little bit too, but I'll let you know.

Hu John,
did you check if this fix the problem? From that time I also uloaded a
few new versions of hylafax. Did you have this problem with any of them?

Bye,
Giuseppe

P.S. If I do no get a reply in some weeks I think I will close this bug
report.

Message #49 received at 309684-quiet@bugs.debian.org (full text, mbox, reply):

From: Giuseppe Sacco <eppesuig@debian.org>

To: 309684-quiet@bugs.debian.org, John Goerzen <jgoerzen@complete.org>

Subject: Bug#309684: hylafax-server: MaxConcurrentCalls not being respected

Date: Fri, 23 Jun 2006 22:35:22 +0200

Mr Goerzen,
did you find any time to check if this problem is fixed with hylafax
4.3.0 or if the workaround I suggested you works?

Thanks,
Giuseppe Sacco

Message #54 received at 309684@bugs.debian.org (full text, mbox, reply):

From: Lee Howard <faxguy@howardsilvan.com>

To: 309684@bugs.debian.org

Subject: MaxConcurrent calls not working

Date: Fri, 23 Jun 2006 16:55:52 -0700

MaxConcurrentCalls works for me.

Are you sure that you're not noticing the effects of batching and 
misinterpreting them?

Lee.

Message #59 received at 309684-done@bugs.debian.org (full text, mbox, reply):

From: Giuseppe Sacco <eppesuig@debian.org>

To: 309684-done@bugs.debian.org

Subject: Re: Bug#309684: hylafax-server: MaxConcurrentCalls not being respected

Date: Sun, 10 Dec 2006 09:20:40 +0100

Version: 2:4.3.1.-3
Package: hylafax-server

Hi John,

Il giorno mer, 18/05/2005 alle 15.06 -0500, John Goerzen ha scritto:
> Package: hylafax-server
> Version: 1:4.2.1-5
> Severity: normal
> 
> This bug also appeared after our pugrade from 4.1.x.
> 
> According to the docs, MaxConcurrentCalls defaults to 1.  This is as we want
> it.  We have two outgoing FAX lines.
> 
> This setting doesn't seem to be getting respected anymore.  We're seeing a
> number of situations where one line calls a particular FAX number, and the
> other line then tries to call it also to deliver a different document.  The
> second line gets a busy signal, of course.
> 
> In 4.1.x, the second line wouldn't even attempt to dial a number that the
> first line was already working with, and that's the behavior we want.

I have been waiting for a reply on this bug report since more than one
year, and I do think that this has been solved many months ago, so I am
closing this report.

Thanks for your report,
Giuseppe Sacco

Send a report that this bug log contains spam.