Page 1 of 1

list dial problem

PostPosted: Tue Jul 13, 2010 8:43 am
by issam123
Hello
We remarks that after a dial of a list some leads have always new status and the agent is vdad the number of calls for this status is 1.
why predictive dont dial this leads.
we use vicidial 2.0.5 and 3 asterisk 1.4 and one 1.2
thanks

PostPosted: Tue Jul 13, 2010 9:00 am
by mcargile
This is either caused by an error in your dial plan, or your are having an issue with Local channels not resolving on Vicidial. In either case this is really a support question and I am going to move this into our support forum.

PostPosted: Wed Jul 14, 2010 5:39 am
by issam123
thanks for your response,
how can I do to solve this problem and if I upgrade vicidial to 2.2.0, can this help
THANKS

PostPosted: Wed Jul 14, 2010 7:39 am
by mcargile
If you have errors in your dialplan, the best thing to do is use the stock dialplan that comes with Vicidial and use the web based configuration. If you are having Local channels not resolving, this can be far more difficult to figure out. The three things to check first are your firewall settings, and that your carrier is not what is known as Comfort Noise, and load on the server.

Make sure your firewall is configured correctly to handle VoIP traffic, and that it is fast enough to handle the volume of VoIP traffic you are doing.

Comfort Noise is basically when the carrier detects that the person you have calls is not talking, they do not send audio packets to you. This saves on bandwidth for them. The problem is that Local channel resolution happens during audio processing, so if there is no audio to process, the channels will not resolve.

Lastly if your dialers are over loaded, you can have issues with Local channels as well. I have seen customers who have decided that if a single quad core processor supports around 25 agents, then a dual quad core must support 50 agents. When you look at just the load average on these systems, the load looks to be within acceptable means, until you look at the cpu idle percentage which can fall well below 60%. Vicidial pushes asterisk so hard that it needs a lot more than just processing power, it needs IO through put, and memory access. Unfortunately these do not double when you just double the number of processing cores. Turn on the server performance logging and check what the graphs in the reports are showing.