OK, I got it, but I went way in over my head to get there. I'm not going to share my scripts on this, as I'd rather you were the architect of your own DB's demise. Be sure you have good backups before you do this. I'm sure TAC will chime in that this is a very bad idea, and I'm positively sure it will be hosed in the 8.0 upgrade...
A couple of the fields pull from and in turn increment in the ConfigSeed table. There are a couple of stored procedures (and a bunch of sub-procedures) that do a lot of the intelligence and validation for you. Adding records using the stored procedures seem to take care of some backend stuff that breaks when you do it manually. Note that the only way to execute a stored procedure in a script, even when it updates the database, is through a read step.
Here is a rough sketch of the steps:
1. Create a new system DSN to the db_CRA and connect to it through the DB subsystem
2. Config up your Outbound subsystem and setup your Call Back campaign, skills, etc
3. Import a contact and go look at the DialingList table to get your campaignID
4. Make sure your Outbound campaign works properly and previews the call to your agent
5. You'll create a script to gather the number from your caller and validate it however you want (look for other posts from me, somebody shared some nice Java w/ me to pull this off recently)
6. Create your callback script
a. First query the ConfigSeed table to find out the NextDialingListID (actually tells you the last contact)
b. Increment this NextDialingListID by one, you'll use it as the dialingListID in the DialingList table and write back the incremented value to your ConfigSeed
c. Pull the current time and date and put it into the same format you see in your DialingList table
d. Put in a read step and execute the following SQL, you will of course fill in values w/ variables, where I have done it manually to execute the SQL: EXEC wrapperCreateDialingList '', '12', '1', '5', '', '', 'James', 'Bond', '2085551212', '', '', '102', '0', '102', '0', '102', '0', '', '', '1', '', '', '', '', '', '', '', '', '', '1' (You can look at the stored procedure to get an understanding of these variables, I'll paste them w/ my comments below.)
e. Put in a read step and execute the updateConfigSeed wrapper to update the NextDialingListID to your updated value (UPDATE ConfigSeed ID = $dialingListID WHERE tableName = 'NextDialingListID')
7. Outbound call should preview to your agent, assuming your campaign is enabled and your stars are aligned
Here is the first part of the main stored procedure and my comments on the variables to pass.
CREATE PROC wrapperCreateDialingList(
@recordID int OUT, /*Automatically filled from ConfigSeed w/ Wrapper call below */
@dialingListID int , /*????You have to increment this from the last record somehow, don't see how it's done in SQL, can easily do w/ a query of last record and increment, but want to know how this is done*/
@profileID int , /* 1 */
@campaignID int , /* 5 for my test, but this will statically map to your campaign of choice, create your campaign, add a contact, then look at the table to get this value*/
@createDateTime datetime OUT, /* Automatically filled in procedure */
@accountNumber nvarchar (25) , /* null */
@firstName nvarchar (50) , /* SEND IT IN A VAR*/
@lastName nvarchar (50) , /* SEND IT IN A VAR*/
@phone01 varchar (28) , /* SEND IT IN A VAR */
@phone02 varchar (28) , /* null */
@phone03 varchar (28) , /* null */
@gmtZonePhone01 smallint , /* 102 for MST */
@dstPhone01 bit , /* 0 = dst*/
@gmtZonePhone02 smallint , /* 102 for MST*/
@dstPhone02 bit , /* 0 = dst*/
@gmtZonePhone03 smallint , /* 102 for MST*/
@dstPhone03 bit , /* 0 = dst*/
@callbackNumber varchar (28) , /* null */
@callbackDateTime datetime , /*manually populate this w/ current date/time */
@callStatus smallint , /* 1 Always */
@callResult smallint , /* null */
@callResult01 smallint , /* null */
@callResult02 smallint , /* null */
@callResult03 smallint , /* null */
@lastNumberDialed smallint , /* null */
@callsMadeToPhone01 smallint , /* null */
@callsMadeToPhone02 smallint , /* null */
@callsMadeToPhone03 smallint , /* null */
@privateData image , /* null */
@numcds int /*Always 1 on single server environ. I think this is in place for DB replication in a cluster?*/
Good luck. And don't blame me if your server starts smoking.
Please rate this if it helps you.
Thanks,
Joshua
