Project

General

Profile

Actions

Feature #4237

closed

Understanding how the system works with certain table and fields

Added by Nicolas Payette about 7 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Features
Target version:
-
Start date:
02/28/2017
Due date:
% Done:

0%

Estimated time:

Description

With GAD we did an integration with our sub-system to make the campaigns dynamically feeded every minutes or so.

Doing so, we are inserting directly to database.

1. We have an issue: we have some rows in our database , we want to insert them into `asterisk`.`vicidial_list` then insert in to `asterisk`.`vicidial_hopper` but with high priority for users to call them first,
It works very well, But I don’t know how and under which conditions all the priorities reset and again returns to 0 or 1.
Question : which procedure reset the hopper and under which conditions?
Question : what is the best way to manage call priorities with direct database?

2. We have a features to force a lead in to vicidial_hopper table with high priority to call as soon as we press next call and also want to make it stick to a specific agent. To do it, we insert a row in vicidial_hopper with status “QUEUE” and the “Agent” but when we click next call the agent will not receive the call. How can we force the callback?
Question : what we have to do to get the specific calls in Hopper as a next call for a specfic agent.

3. What is the different between statuses “NEW”, “READY” in `vicidial_list`?
4. What is status ‘NP’ and under which condition it sets?

Actions #1

Updated by Wittie Manansala over 5 years ago

  • Status changed from New to Rejected

Please use the forums. This issue tracker is for GOautodial development purposes only.

Actions

Also available in: Atom PDF

Go to top