Waiting for ring... xx seconds
Posted: Mon Dec 30, 2013 7:24 am
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.
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.