vicidial.org

Hi everyone,

We're experiencing an issue in predictive mode (adapt_hard_limit) and (ratio).

Let's say i have a 2500 leads campaign, i run it until the end of the list. And when i take a look at my leads, there is about 10% of leads still showing as NEW... like i run all trough it, and when it's done, it either skipped lead, or just didnt call the lead.

Anyone experimenting that?

The only workaround i found is to reset the lead, so the new go back in the hopper.

That can happen if the call to that lead failed for some reason. For example, if VICIdial got back congestion on that call, it's going to show as NEW still since it never did anything with it. To know for sure, search the /var/log/astguiclient/screenlog.0 file for the Dial() event for the phone number of one of those NEW leads.

Another possibility I just remembered is a bug in VICidial versions prior to 2.4-324a, build 110707-1402. Before that, having an abnormally high dial-timeout can cause the issue too.

Thank you very much!

I'll look at the logs,

Cheers!

xatomicx wrote:Hi everyone,

We're experiencing an issue in predictive mode (adapt_hard_limit) and (ratio).

Let's say i have a 2500 leads campaign, i run it until the end of the list. And when i take a look at my leads, there is about 10% of leads still showing as NEW... like i run all trough it, and when it's done, it either skipped lead, or just didnt call the lead.

Anyone experimenting that?

The only workaround i found is to reset the lead, so the new go back in the hopper.

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Test with one next time through. Set the campaign to 1:1 dialing (ratio) and set the hopper to ONE. And watch the asterisk CLI as it dials through those "missed" leads again. You may find out what happened ...

4) Be sure you are not overloading the server. Watch "htop" and be sure your load average never exceeds your core count. Ideally is should rarely get past 1/2 of your core count ... so if you have 8 cores, it should not go past 4.0 for more than a few seconds every now and again, but certainly not past 8.0 ever.

Thank you!

Yes i am new, and i am also a simple employee and not the technician who installed Vicidial, so in terms of version of things, models of that... i can probably grab some of these infos, but my knowledge is limited compare to all of you guys.

Anyway we found out that those "NEW" are basically out of service numbers, and vicidial somehow can't identify them and automatically code them.

I'll keep in mind to get these info next time i ask a question

Add this to one of your carriers (or create a "generic/default" carrier for this entry):

exten=> s,1,AGI(agi://127.0.0.1:4577/call_log)
exten=> s,n,NoOp(No Dial Pattern Matches This Extension)
exten=> s,n,Hangup