vicidial.org

Hi, we have Vicibox 1.0.0RC2 configured with 296 outbound campaigns and 296 lists. Each campaing have it's own list, one and only one. For example campaing 5063 uses list 5063.
In average we have about 30 campaigns running at the same time.
We have found that there are leads being called from a wrong campaing. We have about 460 call in that situation in less than a week, for explample from:
SELECT * FROM vicidial_log where campaign_id <> list_id

| 1248798357.4062 | 64648 | 2041 | 5063 | 2009-07-28 12:26:12 | 1248798372 | 1248798430 | 58 | WN | 1 | 56999872527 | 15763077 | AUTO | N | Solu_LaCalera | CALLER | NONE |

We don't understand how can this be posible. We've double checked campaigns and lists configuration and every thing seems to be right.

Ideas?

Thanks!
Javier
Pibix Telefonía IP - Chile

Do you ever switch agents from one campaign to another?

Do you allow for scheduled callbacks?

Do you do inbound at all?

Thanks Matt,

We never switch agents from one campaign to another.

We do allow scheduled callbacks.

We never accept inbound calls.


Javier

Not sure about the version you are using, but with scheduled callbacks they can follow the agent no matter the campaign they are currently in. There is an option to disable this in SVN trunk.

Thanks, I think thats not the situation in this case because agents work for campaign in a specific a geographic zone with lead for the same geographic zone, and now the system is making call for wrong geographic zones.

What is the vicidial.php version and build?

VERSION: 2.0.5-173
BUILD: 90320-0424

For something like this you really have to look at the logs and see how the lead went into the hopper, how it was dialed by the auto dial script, how it was handled by the ALL_outbound AGI script and how the agent interface handled it.

I've been looking the problem from diferent sides and I'm sure the leads went to the hopper in a wrong way. Can you tell me where can I check how the lead went to the hopper?

Thanks

Javier

Change the AST_VDhopper.pl script to run with the --dbdetail flag in your crontab.