Added Callback Days Limit campaign option to allow scheduled callbacks to be scheduled only a set number of days from today.
git-svn-id: svn://192.168.202.10@1670 3d104415-ff17-0410-8863-d5cf3c621b8a
This commit is contained in:
@@ -9,9 +9,10 @@ with each other to send various types of information between them. The overall
|
||||
goal is to allow for many clusters to talk to each other.
|
||||
|
||||
Some of the types of communication that we would like to achieve are:
|
||||
- Setup of telco trunks(SIP/IAX) allowing for 1-way or 2-way calling
|
||||
- Setup of crossover trunks(SIP/IAX) allowing for 1-way or 2-way calling
|
||||
- Allowing lookup of lead information while transferring between clusters
|
||||
- Allow transmission of number of calls in queue and agents available
|
||||
- Allow transmission of number of calls in queue, agents available and other stats
|
||||
- Allow routing of calls to another cluster based upon total daily call percentage, drop rate, number of waiting calls or number of waiting agents
|
||||
|
||||
|
||||
|
||||
@@ -34,6 +35,7 @@ This will require a new Admin subsection for cluster configuration:
|
||||
- cluster_api_user
|
||||
- cluster_api_pass
|
||||
- cluster_api_permissions - lead_lookup, user_lookup, ingroup_lookup, etc...
|
||||
- cluster_user_group - used to define the campaigns/ingroups cluster is allowed to get info on
|
||||
- <readonly auto-updated> cluster_dst, cluster_tz, cluster_local_gmt_now
|
||||
|
||||
There will be new options added to Servers:
|
||||
@@ -50,6 +52,12 @@ There will be a new table added to link lead_ids on clusters:
|
||||
- call_date
|
||||
- caller_code
|
||||
|
||||
New table to keep track of the active in-groups and campaigns on other clusters
|
||||
- group_id
|
||||
- name
|
||||
- type - INGROUP, CAMPAIGN
|
||||
- cluster_id
|
||||
|
||||
Some tables will have a "cluster_id" field added to them to show where the call came from
|
||||
- vicidial_auto_calls
|
||||
- vicidial_campaign_stats
|
||||
@@ -70,11 +78,15 @@ lead_notes_lookup:
|
||||
|
||||
ingroup_status:
|
||||
- REQUIRES: cluster_id, group_id
|
||||
- RETURNS: number of agents waiting/incall/paused/total, number of calls waiting, calls today, drops today, drop %
|
||||
- RETURNS: status, after hours, number of agents waiting/incall/paused/total, number of calls waiting, calls today, drops today, drop %
|
||||
|
||||
campaign_status:
|
||||
- REQUIRES: cluster_id, campaign_id
|
||||
- RETURNS: number of agents waiting/incall/paused/total, number of calls waiting, calls today, drops today, dialable leads, drop %
|
||||
- RETURNS: status, number of agents waiting/incall/paused/total, number of calls waiting, calls today, drops today, dialable leads, drop %
|
||||
|
||||
ingroup_campaign_list:
|
||||
- REQUIRES: cluster_id
|
||||
- RETURNS: ID and name of all active campaigns and in-groups on the cluster
|
||||
|
||||
cluster_server_status:
|
||||
- REQUIRES: cluster_id
|
||||
@@ -86,5 +98,5 @@ cluster_server_status:
|
||||
CALL FLOW AND TRUNK CHANGES:
|
||||
--------------------------------
|
||||
|
||||
- IAX/SIP trunks would be added between every server on every active cluster(depending on direction settings)
|
||||
- IAX/SIP crossover trunks would be added between every server on every active cluster(depending on direction settings)
|
||||
- dialplan context would be added for each foreign cluster to route calls with proper cluster_id flag allowing for lookups of lead information
|
||||
|
||||
Reference in New Issue
Block a user