vicidial.org

Hi i have a scratch install vicidial 2.2 it was running weeks now, but suddenly stop dialing without any notice or log errors on the asterisk CLI.

Its just when agent login they successfully enter conference and then when they click resume button on the agent interface nothing happens, no sign of dialing logs on asterisk CLI, auto dialing is not running but when we do manual dialing we can have our calls. the dial ratio is 3.0

any idea..

VERSION: 2.2.0-234
BUILD: 100116-0718
Asterisk 1.4.27-vici

Code: Select all

screen -list

when was the last time you rebooted? (A lot of "Scratch" installers believe that their system is impervious to error and will never be in need of rebooting ... and then it crashes unexpectedly ...and they don't think to reboot!)

is your hard drive full? (which can cause mysql to crash a table in your database, rendering your mysql incapable of responding properly, and often no calls are generated as a result of no questions being answered)

For what it's worth I am having this same issue. Auto-dialing worked fine, but after I upgraded to 2.2 just a couple days ago, auto-dialing stopped working. The auto_dial script is running as well as all the other necessary scripts. The hopper has leads in it. Manual dialing works great (my agents are doing that now). I am running vicidialNOW - followed the upgrade directions on his site.

I tried some of the recommendations in the FAQ but those seem to be a little outdated (I think), and aside from that they didn't help.

This is what shows up when I run screen -list

Code: Select all

[root@vicidial ~]# screen -list
There are screens on:
   3959.ASTlisten   (Detached)
   3020.ASTfastlog   (Detached)
   3962.ASTVDauto   (Detached)
   3956.ASTsend   (Detached)
   2852.asterisk   (Detached)
   3976.ASTVDremote   (Detached)
   2847.astshell20100514184044   (Detached)
   32119.ASTVDadapt   (Detached)
   3953.ASTupdate   (Detached)
9 Sockets in /var/run/screen/S-root.

I don't think anything is missing. Correct me if I'm wrong.


edit: I'm running asterisk 1.2.30.2, the one that vicidialnow has by default.

did you run the mysql scripts during the upgrade? (you may want to list the commands issued during the upgrade, there are only a few ...) and did you verify "success" during issuing each command?

have you cleared the hopper to see if it will repopulate?

have you looked at the asterisk cli to see if there is any activity?

have you checked /var/log/astguiclient logs to see if there are problems with the logic (deciding when to dial and how many lines, etc)?

williamconley wrote:did you run the mysql scripts during the upgrade? (you may want to list the commands issued during the upgrade, there are only a few ...) and did you verify "success" during issuing each command?

Yes. I ran the mysql upgrade script and it did quite a bit, no errors.

have you cleared the hopper to see if it will repopulate?

Yes, and it does re-populate.

have you looked at the asterisk cli to see if there is any activity?

There is no activity to speak of when its set to auto-dial, other than activity from people logging in and such.

have you checked /var/log/astguiclient logs to see if there are problems with the logic (deciding when to dial and how many lines, etc)?

I've attempted to sift through a few of the logs but I'm not seeing anything that jumps out at me as abnormal, but I'm not a vicidial expert either.

This is what the auto_dial log looks like:

Code: Select all

2010-05-19 11:57:57|SERVER CALLS PER SECOND MAXIMUM SET TO: 60 |16.6666666666667||
2010-05-19 11:57:57|LIVE AGENTS LOGGED IN: 0   ACTIVE CALLS: 17|
2010-05-19 11:57:57| : agents:  (READY: 0)    dial_level: 0|
2010-05-19 11:57:57| : Calls to place: 0 (0 - 0 [0 + 0]) 17 |
2010-05-19 11:57:57|CAMPAIGN DIFFERENTIAL: 0   0   (0 - 0)|
2010-05-19 11:57:57|LOCAL TRUNK SHORTAGE: 0|0  (17 - 60)|
2010-05-19 11:57:57| : CALLING|
2010-05-19 11:57:57||     dead call vac XFERd do nothing|425778|3082800204|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|425916|3362877422|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|425932|3184479392|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|425942|9377898493|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426155|11172009200450|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426303|3166853914|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|425615|3108151954|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|425745|7024883529|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|425861|6262339168|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426298|6618331746|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426504|8453927219|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426517|3344142605|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426518|9852497593|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426520|7043014471|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426521|4802467499|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426523|8015625264|XFER||
2010-05-19 11:57:57||     dead call vac XFERd do nothing|426524|7063993199|XFER||

It updates every few seconds. Active calls = 17 and I have about 20 agents, but it says live agents logged in = 0.... even though they are definitely logged in and manual-dialing. Could that be related? Auto_dial script thinks no live agents are logged in? The real-time summaries and such are quite aware of who is logged in and who is placing calls though.

what version did you upgrade FROM and TO?

williamconley wrote:what version did you upgrade FROM and TO?

I upgraded from Vicidial 2.0.5.1rc1 to 2.2.0 rc8

I upgraded via SVN per instructions on vicidialnow.org

edit: I'm actually at revision 1436 of SVN if that narrows it down. I don't know if that IS rc8 or if perhaps I accidentally downloaded an unstable version....

and you DID reboot after the upgrade?

williamconley wrote:and you DID reboot after the upgrade?

Yes, I did, even though the directions didnt specify that. I am pretty paranoid as it is.


As you can see, this is very perplexing.

are there entries in your live agents table after your agents log on?

williamconley wrote:are there entries in your live agents table after your agents log on?

Yes. Also the version on the admin page says VERSION: 2.2.1-237
BUILD: 100510-2015, dunno if that helps.

verify that all your scripts are the correct version. somewhere it's asking the wrong question or getting the wrong answer.

williamconley wrote:verify that all your scripts are the correct version. somewhere it's asking the wrong question or getting the wrong answer.

All scripts where updated/last-modified on May 13th at 2:19 PM, which is when I did the upgrade. Including the .pm files and other ancillary stuff.


This is frustrating :\

I really dont want to re-install from scratch because it's in production but it looks like i might have to.

why from scratch? you don't like the .iso installs?

williamconley wrote:why from scratch? you don't like the .iso installs?

Well I mean I installed from VicidialNOW iso but I'll have to do it again and lose our production configuration

Although someone did just inform me via PM that doing a scratch install fixed this very problem I am experiencing, so perhaps i should go that route anyway.

Also, is it safe to upgrade to the latest Asterisk 1.4.x version? I'm seeing evidence around the forums that seems to indicate that it is.

1.4 is cool.

.iso install of VicidialNOW, Vicibox, Vicibox Redux are all good right now.

VicidialNOW installs Asterisk 1.2 and Vicidial 2.0.5 on CentOS with a pretty agent screen, but if you are experiencing issues with this on CentOS you may want to look at changing.

Vicibox installs on Asterisk 1.2 and Vicidial 2.0.5 Ubuntu and is considered the present "official" latest stable, arguably at least (2.2.0 seems stable now).

Vicibox Redux installs Asterisk 1.4 and Vicidial (version based on installation choices) on OpenSuse. Unfortunately, if I recall, you are limited in your SVN choices (cool that it has SVN, but i think if you choose SVN you end up with 2.4 which is not considered that stable just yet). On the other hand I think the latest one will put 2.2.0 on if you say no to SVN.

On any of them you should be able to do an immediate SVN/SQL upgrade and upgrade to the Asterisk 1.4-vici version to be "latest".

With Redux you can choose the 2.2 branch of SVN if you don't want to run SVN trunk(which is stable with more features)