Re: [hylafax-users] MaxCalls reached in a second

[Bodo Meissner <bodo@xxxxxxxxx>]

Am 2005.07.20 11:57 schrieb(en) Thilo Hille:

> Hylafax is version 1:4.2.1-5
> Capi4hylafax is version 1:01.02.03-11
> Capi4hylafax is from debian unstable as in the current sarge deb
> (1:01.02.03-10) has an unfixed Bug in c2faxsend with Eicon Diva cards.

Hello Thilo,

your versions should be new enough. I think the changes from Hylafax  
1:4.2.1-5 to 1:4.2.1-7 are not important.

> We have 8 B-Channels.

> FIFOs in /var/spool/hylafax/:
> prw------- 1 uucp uucp 0 2005-07-20 10:25 FIFO
> prw-rw-rw- 1 uucp uucp 0 2005-07-19 15:18 FIFO.faxCAPI
> prw-rw-rw- 1 uucp uucp 0 2005-07-19 17:43 FIFO.faxCAPI11
> prw-rw-rw- 1 uucp uucp 0 2005-07-20 09:17 FIFO.faxCAPI12
...
> prw-rw-rw- 1 uucp uucp 0 2005-07-19 17:43 FIFO.faxCAPI42

That means Hylafax uses 9 devices: faxCAPI, faxCAPI11, ... faxCAPI42

> in etc/ we have:
> --rw-r--r-- 1 uucp uucp 5071 2005-07-19 15:19 config.faxCAPI
> lrwxrwxrwx 1 uucp uucp 14 2005-07-19 17:42 config.faxCAPI11 ->
> config.faxCAPI
> lrwxrwxrwx 1 uucp uucp 14 2005-07-19 12:04 config.faxCAPI12 ->
> config.faxCAPI
...
> lrwxrwxrwx 1 uucp uucp 14 2005-07-19 15:20 config.faxCAPI42 ->
> config.faxCAPI

Same as above: 9 devices.

> in etc/config.faxCAPI we have definitions for the following devices:
> faxCAPI11
> faxCAPI12
...
> faxCAPI42

Hylafax uses 9 devices but you configured only 8 of them. Maybe device  
faxCAPI uses some default values.

> Modemcapabilities are:
> FaxQueuer[3118]: MODEM faxCAPI: READY, capabilities Pc87fcf01

I don't know why Hylafax shows this value.
The normal value as shown below for the other "modems" is a hard coded  
string in the source code of capi4hylafax. IMHO capi4hylafax cannot  
report this capability string.

> FaxQueuer[3118]: MODEM faxCAPI11: READY, capabilities P3c7dffff:ff

That is the normal value.

> ... the 7 other are just the same than faxCAPI11.
>
> output from faxstat -i: (msn anonymized with **)
...
> HylaFAX scheduler on cs1.ganter.local: Running
> Modem|faxCAPI|(+49.**):|Running and idle
> Modem|faxCAPI11|(+49.**):|Running and idle
> Modem|faxCAPI12|(+49.**):|Running and idle
...
> Modem|faxCAPI42|(+49.**):|Running and idle

Same as above: 9 devices.

> returncode of c2faxsend for 389 attempts was 0. two times it was
> 0x200.

0 is retry. I don't know what 0x200 means.

> Reducing the devicedefinitions in config.faxCAPI would leave me with
> less than 8 channels which are all verified with sendfax -h
> faxCAPI??@localhost ... and they are all working.

I think you should not reduce the number of definitions but change the  
device name to faxCAPI in one of them and remove the corresponding  
files. Your problem seems to be Hylafax thinks you have 9 devices while  
you have only 8 channels.


A different problem is: Why does Hylafax retry immediately?
Normally it should wait before retrying.

Please show the syslog output related to a situation when Hylafax  
retries immediately. There should be lines with "SEND INCOMPLETE".
(Set ServerTracing and SessionTracing to higher values if necessary.
I don't know what the different values mean, but I use 0x03FFFF for  
both ServerTracing and SessionTracing.)

Do this before changing the device definitions.


Bodo

____________________ 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*