Outdial_new.xml Not Loading Correctly

[Guest ooper]

Hello,

I can't get the OutDial_New.xml file to load properly into the Access database. I created the file using this example in the help file:

 

<OutDialEntry>

<PhoneNumber>5553328</PhoneNumber>

<CallTime>6:30 AM, 24 Aug 04</CallTime>

<OnAnswer>d:\scripts\todays_specials.vgs</OnAnswer>

<OnAnswerMachine>d:\scripts\todays_specials_AM.vgs</OnAnswerMachine>

<RV>[ClientID]{123456}[PriceWidget]{125}[PriceDelivery]{7.50}</RV>

</OutDialEntry>

 

and only changed "Aug 04" to "Aug 06". I then saved it in VoiceGuide\data, and it loaded into OutDialQue.mdb like this:

 

ID 154

PhoneNumber 5553328

ActivateTime 912300000

DayTimeStart 0

DayTimeStop 2359

DaysCallAllowed MoTuWeThFrSaSu

LineSelection ,,

Priority 0

AnnounceMessage d:\scripts\todays_specials.vgs

Script d:\scripts\todays_specials_AM.vgs

OnAnswerMachine

RV [ClientID]{123456}[PriceWidget]{125}[PriceDelivery]{7.50}

AnswerTimeout 60

CallRetriesLeft 2

DelayBetweenRetries 5

OnNotConnected none

EscalationCalls none

 

What is going on? The ActivateTime should be 608240630. I'm not sure why LineSelection has two commas in it either.

 

Any ideas? I'm using a registered version of VG - version 5.2.5012 Enterprise.

 

Thanks,

Brian Barnett

[Harry L. Roberts]

You Said:

 

What is going on? The ActivateTime should be 608240630. I'm not sure why LineSelection has two commas in it either.

 

You are correct. The ActivateTime should reflect the date/time that you entered.

 

The problem is that the Help File has incorrectly indicated the proper format for the date/time.

 

You need to remove the comma from your date/time and everything should work fine.

 

Give it a try. It doesn't matter if the time or the day comes first you just need to have a space between the date and the time. No Commas.

 

Like this:

 

20 Aug 2006 6:30

 

or

 

6:30 20 Aug 2006

 

The Help File needs to be updated to reflect the proper format to specify the date/time.

 

I'm not sure why the commas appear in the line selection. It must be so that the program knows to select any available line. If you specify a specific line or lines they will appear in this field. They will also start with a leading comma and end in a comma.

[Guest ooper]

Thanks. That fixed it. A followup question:

 

Can you have more than one call in the OutDial_New.xml file? I want to load up a bunch of calls in one xml file, but I'm not sure how to make it work. What should the root element be named?

 

I generated a file like this, dropped it in the data folder, but the entries were not added to the Access db.

 

<?xml version="1.0" encoding="UTF-8"?>

<rootElem>

<OutDialEntry>

...

</OutDialEntry>

<OutDialEntry>

...

</OutDialEntry>

<OutDialEntry>

...

</OutDialEntry>

<OutDialEntry>

...

</OutDialEntry>

</rootElem>

[Harry L. Roberts]

Trying leaving this off

 

<?xml version="1.0" encoding="UTF-8"?>

<rootElem>

 

 

</rootElem>

 

But keep everything else the same.

[Guest ooper]

I removed the parts you suggested, but it still did not work. The (invalid) xml file gets processed (because I see it disappear), but nothing gets added to the CallQue table.

[SupportTeam]

The (invalid) xml file gets processed (because I see it disappear), but nothing gets added to the CallQue table.

Could you please post a copy of VoiceGuide's Debug Printout which captures the problem, this will allow us to see what happened.

 

When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - any log information will then appear in this window. You must open the trace window before making the call.

You can enable the automatic saving of the logs to files in \log\ directory as well.

 

When posting traces/scripts please .ZIP them up and post them as attachements.

[Harry L. Roberts]

Try this file.

 

Just place it in your data directory.

 

It works fine on my system. It should also work on yours.

 

You could post your OutDial_New.xml file for us to look at.

OutDial_New.xml

[Guest ooper]

I think I figured it out. The Voice Guide code that loads data into the CallQue table from the OutDial_New.xml file has a bug in it, or at least a shortcoming. It does not properly handle apostrophe's that may exist in the xml element content. I suspect the sql insert is choking on it.

 

I had an apostrophe in the <RV> element like this:

 

<RV>[textMessage]{It's 6 o'clock}</RV>

 

When I removed the apostrophes, everything worked fine. I will properly escape the apostrophe's prior to putting them in the xml file so that the sql insert command doesn't choke as a work-around.

 

A word to the wise... Before putting content in the elements, make sure to check for xml reserved characters and either properly escape them or remove them. The reserved characters are: ><& -- escaped as > < and &

 

Brian Barnett

 

PS. It does load the data fine with my added <rootElem> too.