vicidial.org

All of a Sudden , i see Calls stops dialing.

If I create a New Campaign Its works perfectly, without rebooting.


[root@go ~]# screen -ls
There are screens on:
3737.asterisk (Detached)
3935.ASTupdate (Detached)
3938.ASTsend (Detached)
3327.ASTVDadapt (Detached)
3944.ASTVDauto (Detached)
3330.ASTfastlog (Detached)
3947.ASTVDremote (Detached)
3302.goautodial_d (Detached)
3941.ASTlisten (Detached)
3732.astshell20111107091109 (Detached)
10 Sockets in /var/run/screen/S-root.


What can be the issue ?

Did you run out of leads?

No. Leads are there ..Its just asterisk stop dialing !!!

To be clear: Vicidial's Campaign shows a large number of leads available to be dialed in the Campaign Modify screen? And it's not dialing? And you have agents listed as "Ready"?

Do you have any OTHER campaigns running at the same time? (or "Active"?)

To be clear: Vicidial's Campaign shows a large number of leads available to be dialed in the Campaign Modify screen? And it's not dialing? And you have agents listed as "Ready"?

YES

Do you have any OTHER campaigns running at the same time? (or "Active"?)

No.

Dang.

Any Inbound calls active during this period?

Also: check the output of your agi screens/logs during this period. One of them will show you the "tally" for calculating "how many calls to dial" for each campaign. Either asterisk is broken (not responding to commands) or the link to asterisk is broken or the calculation is broken (so no command is being issued).

No Inbnd Calls.

check the output of your agi screens/logs during this period. One of them will show you the "tally" for calculating "how many calls to dial" for each campaig

How ?

screen -list

screen --help

use "screen" to view each of the screens that are running.

this same information is available in /var/log/astguiclient in the logs. but the "real-time" is in that screen. check them all, you'll be educated in what your system is doing, and one of them will show you a tally where it is calculating calls to make.

I get :

[root@go ~]# screen -list
There are screens on:
3726.astshell20111108202810 (Detached)
24911.pts-10.go (Attached)
3997.ASTupdate (Detached)
4006.ASTVDauto (Detached)
2077.ASTVDadapt (Detached)
4009.ASTVDremote (Detached)
3731.asterisk (Detached)
4003.ASTlisten (Detached)
3307.ASTfastlog (Detached)
4000.ASTsend (Detached)
3284.goautodial_d (Detached)
11 Sockets in /var/run/screen/S-root.

[root@go ~]#

now learn to use screen (screen --help) so you can view them and see what they have to say. you can also view most of this information in /var/log/astguiclient, but as I said it is not "real time" in the log files as it is when directly viewing the screens.

was there a solution to this in the end?? having the same issue.
agent ready
leads in hopper
stops dialling


move lists to a new campaign (an actual copy of the broken camp) and it works fine

1) Welcome to the Party!

2) Hints:

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) Check your asterisk CLI to see what happens when the calls stop (leave it running so you can scroll back when something bad happens ...). Often that tells the tale quite clearly.