ViciDial/agc_2-X
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added 'logtable' SIP action, added sip actions to auto-dial calls

Browse Source 
git-svn-id: svn://192.168.202.10@3134 3d104415-ff17-0410-8863-d5cf3c621b8a
This commit is contained in:
mattf
2019-09-26 05:02:28 +00:00
parent cca82b554c
commit 9b78364691
8 changed files with 303 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/SIP_EVENT_LOGGING.txt
+28 -5
View File
@@ -1,4 +1,4 @@
SIP EVENT LOGGING DOC Started: 2019-05-30 Updated: 2019-07-30
SIP EVENT LOGGING DOC Started: 2019-05-30 Updated: 2019-09-25
!!!! THIS IS AN EXPERIMENTAL FEATURE, PLEASE READ ALL IMPORTANT NOTES !!!!
@@ -15,6 +15,9 @@ For phase 2 of this project, we added some basic reporting(AST_SIP_event_report.
ADDED 2019-07-24: The new campaign "SIP Event Actions" settings will allow you to define specific actions to happen depending on what is in the SIP Event Log for each call. Initially this feature will only affect manual dial agent screen calls, for example, allowing you to automatically hang up manual dial calls that take less than one seccond from the dial event to the answer. See the "Campaign SIP Event Actions" section below for more information.
ADDED 2019-09-25: The ability to log to vicidial_sip_action_log table. Also added auto-dial call SIP Action execution.
IMPORTANT VICIDIAL VERSION NOTE!!!
@@ -97,7 +100,10 @@ Campaign SIP Event Actions:
This is designed to be a set of features that will allow for flexible configuration of different actions that are to be taken on calls based upon their SIP event logs.
The first action of this feature to be enabled is the ability to set agent screen manual dial calls to be hung up if certain criteria are met, for example, less than 1 second from dial to answer.
The first action of this feature to be enabled is the ability to set agent screen manual dial calls and auto-dialed calls to be hung up if certain criteria are met, for example, less than 1 second from dial to answer.
The second action to be enabled is the ability to log to a special vicidial_sip_action_log table when certain criteria are met.
This set of features is configured using a Settings Container of the "SIP_EVENT_ACTIONS" type, which you define in the Campaign Detail screen "SIP Event Actions" setting.
@@ -107,7 +113,7 @@ Example SIP_EVENT_ACTIONS Settings Container:
; agent screen actions
AGENT_SCREEN_ACTIONS_START
invite_to_final => 0.0,1.0,hangup-dispo-message,FAS,Auto Hangup and Dispo of False Answer Call
invite_to_final => 0.0,1.0,hangup-dispo-message-logtable,FAS,Auto Hangup and Dispo of False Answer Call
AGENT_SCREEN_ACTIONS_FINISH
@@ -115,13 +121,18 @@ AGENT_SCREEN_ACTIONS_FINISH
Settings within agent screen actions:
1. time range start - a number with 1-6 decimal places
2. time range finish - a number with 1-6 decimal places
3. agent screen action taken - any combination of the following: 'hangup', 'dispo', 'message' separated by dashes
4. If 'dispo' is included in #3, then this is the dispo set
3. agent screen action taken - any combination of the following: 'hangup', 'dispo', 'message', 'logtable' separated by dashes
4. If 'dispo' is included in #3, then this is the dispo set. If 'logtable' is used, then this is the result logged
5. If 'message' is included in #3, then this is the message sent to the agent
If you include a message, it will be displayed on the agent's screen for 4 seconds then it will automatically disappear.
If you use 'logtable', a record will be inserted into the vicidial_sip_action_log table.
For auto-dialed calls, if 'hangup' is used, then 'dispo' will be assumed, even if no tdefined
@@ -202,6 +213,18 @@ index(caller_code)
CREATE TABLE vicidial_log_extended_sip_archive LIKE vicidial_log_extended_sip;
CREATE UNIQUE INDEX vlesa on vicidial_log_extended_sip_archive (caller_code,call_date);
CREATE TABLE vicidial_sip_action_log (
call_date DATETIME(6),
caller_code VARCHAR(30) NOT NULL,
lead_id INT(9) UNSIGNED,
phone_number VARCHAR(18),
user VARCHAR(20),
result VARCHAR(40),
index(call_date),
index(caller_code),
index(result)
) ENGINE=MyISAM;
MariaDB [asterisk]> SELECT * FROM vicidial_sip_event_log limit 10;
+--------------+----------------------+---------------------+----------------+-------------------+------------------------------------------------------+----------------------------+-----------+