added AST_VDauto_dial_FILL.pl script to ADMIN_keepalive_ALL.pl script as option 7. Also, added to install and docs

git-svn-id: svn://192.168.202.10@399 3d104415-ff17-0410-8863-d5cf3c621b8a

docs/BALANCE_FILL_PROCESS.txt

@@ -2,13 +2,21 @@ VICIDIAL Dialing-out Balance FILL proces flow                        2006-11-20
 
 ** FULL VICIDIAL BALANCE DIALING FUNCTIONALITY WAS ADDED IN THE 2.0.2 RELEASE **
 
-This will outline the process I have thought through in my head for a process to allow for dialing-out only servers and for lines on one VICIDIAL server to be utilized when another dialing server does not have enough lines to meet it's dial level for the number of agents that are on the server.
+This will outline the process I have thought through in my head for a way to allow for dialing-out only servers and for dialing-out-trunk-lines on one VICIDIAL server to be utilized when another dialing server does not have enough lines to meet it's dial level for the number of agents that are on the server.
+
+This process is made much more complicated by the addition of the new campaign-reserved-trunks feature for servers, meaning that you need to check on the trunk reservations and their settngs before being able to place any calls.
+
+This script(AST_VDauto_dial_FILL.pl) will be a constantly running script that needs to only be run on one server in a VICIDIAL cluster of servers. 
+
+This script will be started up and monitored by the ADMIN_keepalive_ALL.pl script.
+
+This script is not needed on a single-server or single-VICIDIAL/Asterisk server setup.
 
 
 
-MySQL changes:
+MySQL database changes needed for this new feature:(already in upgrade_2.0.2.sql file)
 ALTER TABLE vicidial_auto_calls MODIFY call_type ENUM('IN','OUT','OUTBALANCE') default 'OUT';
-Added OUTBALANCE to keep track of the calls that were originated by the Balance FILL process.
+- Added OUTBALANCE to keep track of the calls that were originated by the Balance FILL process.
 
 
 
@@ -28,6 +36,7 @@ Process Flow of the AST_VDauto_dial_FILL.pl script:
 			- Loop through these servers
 				- Calculate the available trunks for this campaign per server
 				- Calculate the number of trunks to dial for this server for this campaign
-
+				- Select leads from the hopper and dial 
+				  (this step is identical to normal AST_VDauto_dial.pl script)
 
 

docs/LOAD_BALANCING.txt

@@ -8,6 +8,9 @@ The primary reason to do load balancing, or clustering of multiple VICIDIAL serv
 
 Another reason for load balancing is the ability to use cheaper hardware on the server side. It is much cheaper and more fault-tolerant to buy four P4 2.0GHz 1U servers for $800 a piece than it is to buy a single 4U quad Xeon 3.2GHz server. The four 1U servers will have more total capacity, can be easily scaled and if one fails you've only lost 25% of capacity instead of everything. This philosophy has serverd our call center very well over the last two years.
 
+As of release 2.0.2, a new script(AST_VDauto_dial_FILL.pl) allows for dial-out-only(no agents on the server) VICIDIAL servers as well as balance dialing where a server with available trunk lines can dial lines for another server that does not have enough lines to dial for it's dial_level. AST_VDauto_dial_FILL.pl script is only for multi-server systems and is started from new ADMIN_keepalive_ALL.pl script with option 7 in astguiclient.conf.
+
+
 
 How do I set up load balancing on my two server VICIDIAL setup?
 
@@ -21,8 +24,8 @@ NOTE: In a multi-server setup you may want to have your database and web server
 	- AST_cleanup_agent_log.pl
 	- ADMIN_adjust_GMTnow_on_leads.pl
 	- AST_DB_optimize.pl
-	- ADMIN_keepalive_AST_VDadapt.pl
 	- AST_VDadapt.pl
+	- AST_VDauto_dial_FILL.pl
 
 
 2. The two servers need to be registered to each other as IAX2 friends:
@@ -131,6 +134,6 @@ If you have any questions or problems please post to the astguiclient-users list
 - AST_cleanup_agent_log.pl
 - ADMIN_adjust_GMTnow_on_leads.pl
 - AST_DB_optimize.pl
-- ADMIN_keepalive_AST_VDadapt.pl
 - AST_VDadapt.pl
+- AST_VDauto_dial_FILL.pl