predictive dialer big problem

[kpanik]

Hi all

I've a vicidial server with asterisk whith kernel 2.6.17.9. Hardware: 3 GB RAM, 2 processor Xeon 3.2 Ghz, Te410P with 3 PRI active. I use Asterisk 1.2.12.1, zaptel 1.2.9.1 and libpri 1.2.3.

And a 1 server MySql with 3 GB RAM, 2 processor Xeon 3.2 Ghz.

I've a big problem on vicidial version 2.01.b2, With predictive dialer in modality ratio and other. The problem is when after some minutes, I see in the CLI various NOTICE whit this message:

NOTICE[10042]: app_dial.c:1056 dial_exec_full: Unable to create channel of type 'Zap' (cause 34 - Circuit/channel congestion)

would seem when in the mysql remain active some channel after hangup without it are close

suggestions ?

[gerski]

does your dialer working?

can you post your zaptel.conf and zapata.conf...

[mflorell]

What do you have your server "Max VICIDIAL trunks" value set to?

What dial level are you dialing at?

How many agents do you have calling?

[kpanik]

the my dialer working but when created the error up descript, some channels are congestion. At moment I noticed this problem when modify the tipology of predictive or the value of the predictive.

my zapata.conf

[channels]
language=it
;pridialplan=unknown
;prilocaldialplan=unknown
resetinterval=never
switchtype=euroisdn
pridialplan=local
prilocaldialplan=local
;internationalprefix=00
;nationalprefix=0
;usecallingpres=yes
;callprogress=no
progzone=it
;callwaitingcallerid=yes
echotraining=yes
echocancel=yes
;echocancelwhenbridged=yes
;overlapdial=yes
immediate=no
;callerid=asreceived
;rxgain=0.0
;txgain=0.0
priindication = outofband
;usecallerid=yes
;threewaycalling=yes
;transfer=yes
;canpark=yes
;cancallforward=yes
;callreturn=yes
;busydetect=yes
;busycount=3
answeronpolarityswitch=yes
hanguponpolarityswitch=yes

group=1
signalling=pri_cpe
;context=pri1
context=default
channel => 1-15
channel => 17-31
channel => 32-46
channel => 48-62
channel => 63-77
channel => 79-93
;channel => 94-108
;channel => 110-124

my zaptel.cong

span=1,0,0,ccs,hdb3,crc4,yellow
span=2,0,0,ccs,hdb3,crc4,yellow
span=3,0,0,ccs,hdb3,crc4,yellow

bchan=1-15, 17-31
dchan=16

bchan=32-46, 48-62
dchan=47

bchan=63-77, 79-93
dchan=78

loadzone=it
defaultzone=it

[kpanik]

What do you have your server "Max VICIDIAL trunks" value set to?

What dial level are you dialing at?

How many agents do you have calling?

I've 90 trunks, my dial level was 10, and i've 8 agent

[mflorell]

What is the loadavg on this server when the congest messages appear?

We have found on loaded servers that the zaptel drivers do not always release a zap trunk channel when Asterisk will report the channel as free. Sometimes it takes a few seconds. When you are dialing at a high rate, as you must be, Asterisk is running into this issue where zaptel reports the channel as on-hook when it is not available to be dialed.

The easiest thing to do is either add a Wait(3) or something like that to the "h" exten in priority on in the extensions.conf file, or simply lower the Max VICIDIAL trunks setting in your servers table.

[kpanik]

up this

exten => h,1,DeadAGI(call_log.agi,${EXTEN}) ; DeadAGI is new
exten => h,2,DeadAGI(VD_hangup.agi,PRI-----NODEBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})

or down ?

[mflorell]

Before those two lines, just change the priority on those two and add the Wait as priority 1.

[kpanik]

Thanks guys,

The system it would seem work fine !

In this days, we will make the other tests and we will make to know you the results!

I've a idea ... for improve the predictive ...

we would want that max dial level auto adjust, calculating the number of agent
logged in the campaingn, the number of the max vicidial trunks, and after


max vicidial trunks / number of the agent = result max dial level


Ex: max vicidial trunks = 90 / number of agent "10" logged on system = result max dial level = 9

naturally, the number of the agent is dynamic variable and this calculation it must be carried out
for every campaign.


what of thoughts ?

[mflorell]

That is where we are heading with the dial-only and agent-only option for servers when I get around to starting development of that.

The problem now is with multiple campaigns on multiple servers that is not really possible to auto-calculate maximum dial level.

We will hopefully be able to tackle that at the same time allowing for restriction of lines per campaign per server.