Waiting for ring... xx seconds

[techbob]

Hi, I'm new here.

First off, I followed the installation instructions (scratch) based on striker24x7's instruction on his blogspot account. And while the instructions were for a CentOS system, I adapted accordingly for a Debian system. I was able to track down why an admin account wasn't able to view/create campaigns despite allowing access to the db. Despite this, I've hit a wall on the following issue:

1. When an agent does a manual dial (by clicking the manual dial link; inputting the phone to call; [I called my phone and was able to confirm audio is being passed between the two] and clicking the dial link) -- the call rings and gets answered on the other end, but on the vicidial agent page it doesn't reflect that status and displays "waiting for ring... xx secs" and then because the status is still ringing when the time reaches the <dial time out> I set in campaign settings as expected the warning message "dial timed out" appears -- this, despite both ends being able to talk with each other.

I did the screen -list command and made sure all the perl scripts were running (there were 11), recreated the DB, checked the permissions for the DB's cron user. I checked the carrier and modified the dial options to have the ff: atTor -- and still the same issue.

EDIT:

I'm guessing it could be with the AGI, but I can't be sure. I could set the timeout to something like 10 minutes, but the FORCE_ALL recording action doesn't take effect as the agent page still thinks the call is ringing.

[williamconley]

Often this is related to the carrier dialplan in use. If your manual dial calls go through a different dialplan than your autodial calls, the agi or hangup lines may be missing. These two lines are required for all Vicidial controlled calls. The order is "agi/dial/hangup" all three required. If you have any test carriers from the stock install, they should all have all three of these lines. While the exten may vary widely, the three function calls do not. Also, in the dial command the "o" switch is required.

So: show command line interface for the failing calls.

Also: Why scratch install instead of .iso install? If this is your first Vicidial system you could spend weeks (stupid amounts of man-hours) getting something to work that could have been handled in a quick iso install in under an hour with configuration. A good idea is to use a Virtual server for a practice install with the .iso at Vicibox.com which will net you a FUNCTIONAL dialer capable of only a single agent. But then you have a great comparison tool for whatever other system you may deem necessary to build.

Also, for scratch installs where you MUST start from a Stock OS in a hosted environment, CentOS is actually a better idea as Gardo's Goautodial 3.0 can be installed much easier from a stock CentOS install than a scratch install on any other system.

Then we have the similarity between debian and ubuntu (same family) which makes it often a better idea to use the ubuntu install instructions for vicidial on a debian system than converting a centos set.

But seriously: iso install from Vicibox.com is the most reasonable installation method for your first install unless you Can't.