HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: [hylafax-users] race condition
Moritz Winterberg wrote:
Feb 14 10:33:07.35: [ 3910]: SESSION BEGIN 000291023
Feb 14 10:33:07.35: [ 3910]: HylaFAX (tm) Version 5.1.4
Feb 14 10:33:07.35: [ 3910]: CallID: '216697xxx' '08051983xxx'
Feb 14 10:33:07.35: [ 3910]: <-- [4:ATA\r]
Feb 14 10:33:07.35: [ 3910]: --> [16:CID: 06861934xxx]
Feb 14 10:33:07.35: [ 3910]: --> [14:DAD: 476435xxx]
Feb 14 10:33:07.35: [ 3910]: --> [4:RING]
Feb 14 10:33:19.98: [ 3910]: --> [5:+FCON]
RingsBeforeAnswer: 3
CIDNumber: "DAD: "
CIDName: "CID: "
You're answering a call based on the RINGs. And that could be part of
the problem. I would recommend at least changing those three
configuration items to be:
RingsBeforeAnswer: 0
CallIDPattern: "CID: "
CallIDPattern: "DAD: "
CallIDAnswerLength: 9
However, there could be a possibility that the first call is
disconnecting just after it presents Caller*ID and then the second call
comes through immediately thereafter, just as the modem does ATA. In my
opinion this is really a problem that the modem is causing by not
busying-out the channel/line for at least a few seconds before accepting
another call on the same channel. So, I'd suggest bringing that up with
Eicon.
However, you may be able to work-around the issue by configuring
Asterisk or the Diva server to allocate channels and/or modems in a
"round-robin" fashion rather than always landing on the same
channels/modems.
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*