vicidial DB structure

vicidial DB structure  http://viciwiki.com/index.php/Vicidial_Database_Structure

Force Agent Active status

Re: Force Agent Active status

by mflorell » Mon May 29, 2017 7:07 am

There are several related settings, but nothing that will force an agent to active. The reason for this is you could have an agent log in to their screen and leave, then run for hours with agent there. What you are describing would allow the agent screen to run with no interaction from call to call. This is a bad idea.

Here are the related campaign settings that are available as of the current svn/trunk revision:



Dead Call Max Seconds -If this is set to greater than 0, after a customer hangs up and the agent has not clicked on the Hangup Customer button in this number of seconds, the call will automatically be hung up, the status below will be set and the agent will be paused. Default is 0 for disabled. 

Dead Call Max Status -If Dead Call Max Seconds is enabled, this is the status set for the call when the agent dead call is not hung up past the number of seconds set above. Default is DCMX. 

Dead Call to Dispo Only -If Dead Call Max Seconds is set greater than 0, this option can be enabled if you want to send the agent to the dispo screen after a dead call without automatically dispositioning it. Default is DISABLED. 

Dispo Call Max Seconds -If this is set to greater than 0, and the agent has not selected a disposition status in this number of seconds, the call will automatically be set to the status below and the agent will be paused. Default is 0 for disabled. 

Dispo Call Max Status -If Dispo Call Max Seconds is enabled, this is the status set for the call when the agent has not selected a status past the number of seconds set above. Default is DISMX. 

Agent Pause Max Seconds -If this is set to greater than 0, and the agent has not gone out of PAUSED status in this number of seconds, the agent will automatically be logged out of the agent screen. Default is 0 for disabled. 

Agent Ready Max Seconds Logout -If this is set to greater than 0, and the agent has not gone out of READY or CLOSER status in this number of seconds, the agent will automatically be logged out of the agent screen. Default is 0 for disabled.

mflorell

Site Admin

 

Posts: 15752

Joined: Wed Jun 07, 2006 2:45 pm

Location: Florida

Callbacks not porting to other campaign

Re: Callbacks not porting to other campaign

by mflorell » Tue Feb 28, 2017 2:33 pm

There's a setting to change that in System Settings:

Agent Only Callback Campaign Lock -This option defines whether AGENTONLY callbacks are locked to the campaign that the agent originally created them under. Setting this to 1 means that the agent can only dial them from the campaign they were set under, 0 means that the agent can access them no matter what campaign they are logged into. Default is 1.

Limit the number of leads allocated to an agent per day

Is it possible to limit the number of new leads allocated to each agent per day?

Example:

I create a new campaign – Manual Dial
20 agents are assigned to the campaign
I load a list of 10,000 leads
Each agent must be allocated only 100 new leads per day
Once they have dialled their new lead allocation they still have access to their call-backs, no answers, referrals, etc.

by mflorell » Sat Oct 22, 2016 10:03 am

We just added a feature to do this a couple weeks ago. Make sure you upgrade to the latest svn/trunk version, then go to system settings and enable "New Leads Per List Limit"

vicidial on virtual machine

Re: Vicidial Database

by mflorell » Thu Jan 19, 2017 10:14 am

CAN it be virtualized? Yes. SHOULD it be virtualized? No.

Virtualization causes all sorts of problems with VICIdial because it's a Real-Time system, it's not a good idea at all, and we tell clients that all the time, yet new clients keep trying every month 

mflorell

Site Admin

 

Posts: 15417

Joined: Wed Jun 07, 2006 2:45 pm

Location: Florida

vicidial svn update

Re: Vicidial Update (SVN)

by mflorell » Wed Jan 11, 2017 5:37 pm

On each server, run the following:
- mkdir /usr/src/astguiclient
- cd /usr/src/astguiclient
- svn checkout svn://svn.eflo.net:3690/agc_2-X/trunk
- cd trunk
-

Although, you will also need to separately update the Database Schema, this is done using the sql upgrade files found in the "extras" directory depending on the version you are upgrading from.(this is basically the instructions from the UPGRADE document)
mysql
use asterisk
\. /path/from/root/extras/upgrade_2.8.sql
\. /path/from/root/extras/upgrade_2.10.sql
\. /path/from/root/extras/upgrade_2.12.sql
\. /path/from/root/extras/upgrade_2.14.sql
quit

 perl install.pl

Yes, you should always upgrade the database first. I'll make sure I edit my post above and add that note.

voicemail and reporting

Re: Change Voicemail Server (Reporting)

by mflorell » Wed Dec 28, 2016 8:15 pm

Yes, the voicemail server has to be a dialer.

Did you try forcing a rebuild of the conf files on your servers after you changed the voicemail server in System Settings?