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

[Thilo Hille <thilo.hille@xxxxxxxxx>]

Hi Bodo,
thanks for your posting. Here are some further information:

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.

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.faxCAPI21
prw-rw-rw- 1 uucp uucp 0 2005-07-19 17:43 FIFO.faxCAPI22
prw-rw-rw- 1 uucp uucp 0 2005-07-19 17:43 FIFO.faxCAPI31
prw-rw-rw- 1 uucp uucp 0 2005-07-19 17:43 FIFO.faxCAPI32
prw-rw-rw- 1 uucp uucp 0 2005-07-19 17:43 FIFO.faxCAPI41
prw-rw-rw- 1 uucp uucp 0 2005-07-19 17:43 FIFO.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.faxCAPI21 ->
config.faxCAPI
lrwxrwxrwx 1 uucp uucp 14 2005-07-19 15:20 config.faxCAPI22 ->
config.faxCAPI
lrwxrwxrwx 1 uucp uucp 14 2005-07-19 15:20 config.faxCAPI31 ->
config.faxCAPI
lrwxrwxrwx 1 uucp uucp 14 2005-07-19 15:20 config.faxCAPI32 ->
config.faxCAPI
lrwxrwxrwx 1 uucp uucp 14 2005-07-19 15:20 config.faxCAPI41 ->
config.faxCAPI
lrwxrwxrwx 1 uucp uucp 14 2005-07-19 15:20 config.faxCAPI42 ->
config.faxCAPI

in etc/config.faxCAPI we have definitions for the following devices:
faxCAPI11
faxCAPI12
faxCAPI21
faxCAPI22
faxCAPI31
faxCAPI32
faxCAPI41
faxCAPI42

Modemcapabilities are:
FaxQueuer[3118]: MODEM faxCAPI: READY, capabilities Pc87fcf01
FaxQueuer[3118]: MODEM faxCAPI11: READY, capabilities P3c7dffff:ff
... the 7 other are just the same than faxCAPI11.

output from faxstat -i: (msn anonymized with **)
HylaFAX version 4.2.1 built Thu Mar 17 22:28:14 UTC 2005 for
i686-pc-linux-gnu


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|faxCAPI21|(+49.**):|Running and idle
Modem|faxCAPI22|(+49.**):|Running and idle
Modem|faxCAPI31|(+49.**):|Running and idle
Modem|faxCAPI32|(+49.**):|Running and idle
Modem|faxCAPI41|(+49.**):|Running and idle
Modem|faxCAPI42|(+49.**):|Running and idle

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

another thing i noticed: if sending faxes faxstat didnt shows the status
for all modems "running and idle". when receiving faxes it shows
"Answering the phone" in the appropriate modem line.

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 guess you are right and capi4hylafax is what to look after. :(

Regards

Thilo

Bodo Meissner wrote:

> Am 2005.07.19 17:05 schrieb(en) Thilo Hille:
>
>> Hi,
>> i have a eicon dial diva4 bri card working with hylafax HylaFAX
>> Version 4.2.1 (debian sarge) and capi4hylafax (c2faxsend/c2faxrecv).
>
>
> Hello Thilo,
>
> what are the exact version numbers?
> (see "dpkg -s hylafax-server" and "dpkg -s capi4hylafax")
>
>> Sending and receiving faxes works quite well as long as there are
>> free Modems.
>> If a fax gets queued when all channels are busy c2faxsend fails with
>> reason 0x34A2 (No circuit / channel available).
>
>
> How many B channels do you have?
> How many devices are defined in config.faxCAPI
>
>> Hylafax now requeues the fax for immediatelly retry.
>
>
> What is the return code of c2faxsend?
> You should find it in syslog if tracing is set high enough.
>
> I think the retry should be delayed
>
>> A split second later the fax gets dequeued with the note "REJECT: Too
>> many attempts to dial: 12, max 12 ". Sometimes it dials 4 or 6 times
>> before the job is delayed as expected.
>
>
> c2faxsend has a bug, it increments the counter twice. So if you see 4
> or 6 it should be 2 or 3 instead and 12 really means 6 tries.
>
>> Isnt hylafax expected to dial when there are free modems only? How
>> does Hylafax check if a modem is in use? I realized c2faxrcvd does
>> not create lockfiles like /var/lock/LCK..faxCAPI31.
>
>
> Hylafax and Capi4hylafax communicate through FIFO files.
> Obviously capi4hylafax tells Hylafax that it has free devices.
>
>> Is it possible to limit the channels hylafax uses for outgoing calls?
>
>
> You could reduce the number of device definitions in config.faxCAPI.
>
>
> 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*
>
>
>


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