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

Added cm_phonesearch.agi script for phone number searching and redirection from a Call Menu

Browse Source 
git-svn-id: svn://192.168.202.10@2657 3d104415-ff17-0410-8863-d5cf3c621b8a
This commit is contained in:
mattf
2017-01-13 21:53:15 +00:00
parent 4e7c2d6b24
commit 4ebe87b629
9 changed files with 446 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CROSS_CLUSTER_COMMUNICATION.txt
+14 -1
View File
@@ -1,4 +1,4 @@
CROSS-CLUSTER COMMUNICATION 2011-05-27
CROSS-CLUSTER COMMUNICATION Started: 2011-05-27 Updated: 2017-01-01
!!!!! THIS FEATURE DOES NOT EXIST, THIS IS FOR PLANNING PURPOSES ONLY !!!!!
@@ -100,3 +100,16 @@ cluster_server_status:
- 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
--------------------------------
SIMPLER ALTERNATIVE OPTION:
--------------------------------
Below is a description of a more simple option, which is to send lead data from one cluster to another as the lead is sent over.
- A call to be sent from one cluster to another should leave its callerIDname as the Caller Code, the 20-character code that includes the lead_id
- This call will go into an internal DID on the other cluster through an IAX trunk between the two
- At the DID, the call will get sent to a Call Menu where the call will go through an AGI script
- That AGI script will look up the lead_id on the originating system using the Non-Agent API and credentials set in a Settings Container
- If there is a match, then the AGI script will gather the default lead information, insert the information into the new system and change the callerIDname with the new system's lead_id included
- The call will then go to an In-Group with that lead_id set so it can then go on to an agent
docs/LIMESURVEY.txt
+1 -1
View File
@@ -1,4 +1,4 @@
LIME SURVEY and ViciDial
LIME SURVEY and ViciDial Started: 2009-09-08
We've been asked about Lime Survey(http://www.limesurvey.org) integration with ViciDial several times so here is a little summary of how you install it as well as how you can get it to work with Vicidial.
docs/PERFORMANCE_TESTING.txt
+2 -2
View File
@@ -3,9 +3,9 @@ PERFORMANCE TESTING OF A VICIDIAL SERVER 2008-03-31
OVERVIEW:
This document goes over the setup of a VICIDIAL/Asterisk server that you are testing, and the control Asterisk server that will be taking the calls from the serer being tested.
This document goes over the setup of a VICIDIAL/Asterisk server that you are testing, and the control Asterisk server that will be taking the calls from the server being tested.
It is very difficult to realistically performance test a VICIDIAL server not in production because of the random-ness of call center operations.
It is very difficult to realistically performance test a VICIDIAL server not in production because of the randomness of call center operations.
How this process works is that multiple remote agents are activated and calls are placed from the server being tested to a control server that will take those calls and send various signals and play various audio files so that the randomness of outbound dialing is simulated.