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

Fix for Cross-Cluster phones where phone_type has "trunk" in it

Browse Source 
Added user_call_log archiving when over 1000000 records
Added new options to Fronter/Closer report

git-svn-id: svn://192.168.202.10@2801 3d104415-ff17-0410-8863-d5cf3c621b8a
This commit is contained in:
mattf
2017-08-10 01:52:06 +00:00
parent a0dc2e73a3
commit 388a291658
9 changed files with 145 additions and 68 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CROSS_CLUSTER_COMMUNICATION.txt
+2 -2
View File
@@ -1,4 +1,4 @@
CROSS-CLUSTER COMMUNICATION Started: 2011-05-27 Updated: 2017-06-09
CROSS-CLUSTER COMMUNICATION Started: 2011-05-27 Updated: 2017-08-09
--------------------------------
@@ -11,7 +11,7 @@ Below is a description of a simple cross-cluster option, which is to send lead d
- This call will go through an IAX trunk between the two systems into an internal DID on the destination cluster
Set up an IAX "carrier" on the originating cluster and an IAX "phone" on the destination cluster to link the two together.
(Note: the phone entry on the destination cluster must have the Outbound CallerID and Fullname fields blank)
(Note: the phone entry on the destination cluster must have the Outbound CallerID and Fullname fields blank, and the Phone Type must have "trunk" in it)
The destination phone entry needs to use "trunkinbound" as it's phone and exten context
- Agent on the originating cluster will do a blind-transfer or dial-with-customer to a custom dialplan number that goes to the destination cluster