vicidial.org

Hello,

I'm trying to set up a call on a GoAutodial server. The software versions for Vicidial are:

VERSION: 2.2.1-237
BUILD: 100510-2015
running on CentOs (GoAutoDial CE 2.0)

The problem I have is when creating an automated campaign. My goal is to set it up with no live agents (send them to a recording). What I have done so far is the following:

- Create a campaign, set dial to ratio 1.0
- Create a list and assign it to a campaign. I loaded some test numbers into that list (all of which point to an IP phone so I get all the calls)
- Create a remote agent. Set the extension to 85100116 which does point to a valid recording

After I start everything, calls start to dial and my phone rings. When I answer, call gets immediately disconnected (no sounds or anything in the line).

When I look at the Realtime report, I can see the remote agent logged in, but it never receives the call. I've gone through the agiout log but as far as I can tell the only thing the agi_VDAD_outbound does is to set the CallerID and then it ends, never sends the call to the remote agent.

Any ideas of that could I be doing wrong? Today I set a campaign exactly the same way (in another GoAutodial system) with positive results, which tells me that at least I could set it properly once.

Any pointer of where might the problem be would be greatly appreciated.

Regards,

you are trying to create your own version of a "Survey" campaign. Probably better if you just read the manual for how to set up a survey campaign and it will work very nicely.

FYI: Survey is available via changing the Campaign Exten to 8366 and can be edited (per the manual) by Campaign->Detail->Survey (the survey menu item is not available in the Basic campaign screen, but becomes available in the top menu after Detail is selected).

Dear William,

Thank you for your reply, but no, I wasn't trying to create a survey. I actually followed all the steps in the manager manual for doing this (just play a simple recorded message). I tried everything I could think of, but the problem turned out to be something which I think is totally unrelated to Vicidial.

Turns out that if the queuemetrics user cannot log into the queuemetrics database, Vicidial just doesn't continue processing the call (or at least the version I'm at). This seems very weird to me, since what I would expect from an error like this is that simply the process wont log into queuemetrics, but instead of that, the call doesn't get connected to the remote agent.

All I had to run was the following query:

grant all privileges on queuemetrics.* to queuemetrics@192.168.1.55 identified by 'javadude';

And that solved it. I just got lucky while running one of the debugs on the live agent cleaning, and that gave away that QM wasn't able to log in.

Regards,

True statement. the Queuemetrics link (and I believe the vTiger link) will STOP the process instead of putting an error in a log and "marching along".

I think because most who are actually using these features are expected to be capable of resolving those sorts of issues. And because noone paid to have backchecks put in. Just a guess, though. LOL

Excellent post-back, by the way. Welcome aboard!