OutDial Database Setup (for
VoiceGuide v6 only)
VoiceGuide
Dialer will by default use an internal database to store the
details of all the outbound calls which are to be made. This is
sufficient for most applications as the internal database can
easily handle having up to about 100,000 queued calls at any one
time.
The internal
database in version 7 of VoiceGuide is VistaDB (www.vistadb.net). The internal
database in version 5 and version 6 of VoiceGuide is MS
Access.
In some
circumstances use of another database is preferred and this section
we'll describe how another database engine can be
used.
All that is
required for VoiceGuide dialer to look in another database for any
queued outgoing calls is to:
- Create a
table CallQue in the new database of choice, modeling it's the
tables schema on the table CallQue in OutDialQue.mdb
- Specify the
connection string to the new database in VG.INI,
section [VGDialer], entry DbConnectString_ADO.
- Optionally
set the FindCallDAO_SqlPrefix and FindCallDAO_SqlSuffix fields in VG.INI (in
section [VGDialer] )
An example
CallQue table schema if the new database is created in MS SQL
Server would be:
An example
DbConnectString_ADO entry for a MS SQL Server based OutDialQue
would be:
[VGDialer]
DbConnectString_ADO=Provider=SQLOLEDB;Server=DBSERV1;UID=vg;PWD=vg;Database=OurOutDialQue
Modifying SQL
It is possible
to modify the SQL command issued by VoiceGuide to the database when
retrieving the outgoing calls. The prefix and suffix of the SQL can
be modified using the VG.INI entries below:
[VGDialer]
FindCall_ADO_SqlPrefix_LowVol=
FindCall_ADO_SqlSuffix_LowVol=
FindCall_MSAccess_SqlPrefix_LowVol=
FindCall_MSAccess_SqlSuffix_LowVol=
FindCall_ADO_SqlPrefix_HighVol=
FindCall_ADO_SqlSuffix_HighVol=
FindCall_MSAccess_SqlPrefix_HighVol=
FindCall_MSAccess_SqlSuffix_HighVol=
Leaving the
above entries blank will result in default SQL statements used
which work with MSAccess, MSSQLServer, etc..
For MySQL
based OutDialQue the following entries would need to be modified,
as MySQL uses different SQL syntax:
FindCall_ADO_SqlPrefix_HighVol=SELECT
FindCall_ADO_SqlSuffix_HighVol=LIMIT 1
Other Notes
- To determine
what the valid database entries are it's recommended to use the
Telephone Number Loader to load new outbound calls into
OutDialQue.mdb and use the entries inserted by Telephone Number
Loader as an example of what the entries in the secondary
OutDialQue database should look like in order for them to be
correctly read in by VoiceGuide.:
- By default, specifying a
secondary OutDialQue database source does not stop VG from
continually querying OutDialQue.mdb for new entries. The new
database is just another database that VG will retrieve call
information from.
- VoiceGuide uses ADO layer to
connect to the secondary OutDialQue database (ADO.NET in version
7).
- One previous post covering the
migration to MS SQL Server can be found here: http://voiceguide.com/forums/index.php?showtopic=2696
