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

Added the ability for internal chats to have more than one agent participant

Browse Source 
Fix for rare parked call hangup issue

git-svn-id: svn://192.168.202.10@2648 3d104415-ff17-0410-8863-d5cf3c621b8a
This commit is contained in:
mattf
2016-12-17 14:13:08 +00:00
parent 1fe21df24d
commit b87a7806ee
16 changed files with 612 additions and 125 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CELLPHONE_USA_TCPA_FCC_COMPLIANCE.txt
+8
View File
@@ -101,3 +101,11 @@ PREFIX_SFTP_server => sftp.dncscrub.com
PREFIX_SFTP_user => DEMOVICIDIAL
PREFIX_SFTP_pass => sampLepass
PREFIX_SFTP_port => 22
Changing DB schema back to allow auto-dialing:
UPDATE system_settings SET disable_auto_dial='0';
ALTER TABLE vicidial_campaigns MODIFY dial_method ENUM('MANUAL','RATIO','ADAPT_HARD_LIMIT','ADAPT_TAPERED','ADAPT_AVERAGE','INBOUND_MAN') default 'MANUAL';
ALTER TABLE vicidial_campaigns MODIFY auto_dial_level VARCHAR(6) default '0';
docs/CHAT_MESSAGING.txt
+3 -1
View File
@@ -1,4 +1,4 @@
CHAT MESSAGING Started 2014-05-01 Updated 2016-03-05
CHAT MESSAGING Started 2014-05-01 Updated 2016-12-17
After over 18 months of development, the Chat Messaging system for Vicidial was added to svn/trunk on December 13th, 2015(svn revision 2428). Our Chat messaging allows for customers to chat with agents from websites, as well as allowing managers to chat with agents and agents to chat with other agents all within their existing agent screen.
@@ -10,6 +10,8 @@ UPDATE 2015-12-19: We added several security enhancements related to the chat fu
UPDATE 2016-03-05: We added the ability to transfer a customer chat to another chat group or agent.
UPDATE 2016-12-17: We added the ability for agents to add more agents to their internal chat sessions, so multiple agents can be chatting together in the same session at one time.
AGENT CHAT INTERFACE INSTRUCTIONS:
docs/OUTBOUND_OPTIMIZATIONS.txt
+3 -1
View File
@@ -28,12 +28,14 @@ In our first three rounds of live testing, we have seen the following results:
- Calls that never resolved in over 30 seconds made up from 5-10% of total Answered calls
- The Asterisk 11 server had a lower rate of LRERR calls, and faster overall routing compared to 1.4 and 1.8 servers
Some conclusions based upon these round of live testing:
Some conclusions based upon more rounds of live testing:
- Allowing more than 1 second for channel resolution increased delayed resolution calls being routed by about 30%, although this is still only 1-2% of total Answered calls
- Using different carriers at different times can greatly affect the rate of LRERRs, from less than 1% to over 30%
- If a call does not resolve within 3 seconds post-Answer, there is very little chance it will ever resolve, although we did have some calls resolve at 25+ seconds
- Asterisk 11 appears to be more successful at forcing resolutions, and routing calls faster, when compared to earlier branches of Asterisk
- The quality of your telco carrier, and the state of that telco network, is a big factor in the LRERR rate for post-answer calls
- The speed of your database is a much larger factor in the speed of the routing of outbound VDAD calls post-Answer
- The loadavg of the dialer will be LARGELY affected by use of the BETA AGI script(loadavg over 20.00 on quad-core), although it does not seem to affect functionality