Dialing Via Xml

[jewillis]

 

When using XML (below) to load numbers, the script immediately plays when the call is answered. It does not wait to determine if it is a live answer. If I use the call loader, or add a row to the database, the script waits until it determines they type of answer.

 

Why the difference?

 

Logs attached

 

 

<OutDialEntry>

<PhoneNumber>18187314522</PhoneNumber>

<OnAnswerLive>C:\VGScripts\outbound\SendMessageWav.vgs</OnAnswerLive>

<OnAnswerMachine>C:\VGScripts\outbound\SendMessageWav.vgs</OnAnswerMachine>

<RetriesLeft>1</RetriesLeft>

<RetriesDelay>1</RetriesDelay>

<RV>[MessageWav]{1.wav,2.wav,3.wav}</RV>

</OutDialEntry>

vg_logs.zip

[jewillis]

Correction

 

It palys immediatley when loaded by XML AND loaded via database. Only waits for response when using call loader

 

 

[SupportTeam]

Trace shows two outbound calls being made.

 

When call was loaded from the OutDial_New.xml file the AnsweringMachine script was not read in. Please post the OutDial_New.xml used and we can then see why the AnsweringMachine script setting was not read in. Having the AnsweringMachine script set to nothing/blank in turn results in VoiceGuide not enabling answering machine detection on the outgoing call.

 

200913.672 4 0 OutDial load from [C:\Program Files\VoiceGuide\data\OutDial_New.xml]

200913.672 4 DialListLoadFileXML ReadAllText call

200913.672 4 0 LocalVistaDb_Insert ExecuteNonQuery call

200913.734 4 0 LocalVistaDb_Insert ExecuteNonQuery returned

200913.734 4 0 OutDial input file : loaded 1 entries from C:\Program Files\VoiceGuide\data\OutDial_New.xml

200913.734 4 OutDial input file deleted : C:\Program Files\VoiceGuide\data\OutDial_New.xml

200913.765 10 dial DbProcessQueue_Callback_DoWorkFindCall_LocalVistaDB found some rows. sTaskTimestamp=200913.734

200913.765 10 dial strScriptAnswerMachine=, strOnAnswerFax=

200913.765 10 0 dial FindCallQueryCompleted some calls found (any lineid search) ID=321 ,strLineSelection=, source=[Local...], sTaskTimestamp=200913.734

200913.781 10 dial DbProcessQueue_Callback_DoWorkFindCall_LocalVistaDB found some rows. sTaskTimestamp=200913.765

200913.781 10 iDailyDialWindowStart=0 HH=0 MM=0

200913.781 10 iDailyDialWindowStop=2359 HH=23 MM=59

200913.781 10 dial strScriptAnswerMachine=, strOnAnswerFax=

200913.781 10 dial callque update id=321 nextActivateTime=10/1/2008 8:10:13 PM, retriesLeft=0, iRelatedPortNumber=1

200913.812 10 dial callque update id=321 nextActivateTime=10/1/2008 8:10:13 PM, retriesLeft=0, iRelatedPortNumber=1 : completed ok

200913.812 10 dial StartOutgoingCall call. port=1

200913.812 10 2 dial StartOutgoingCall start tel[xxxxx] live[C:\VGScripts\outbound\SendMessageWav.vgs] am[] fax[] rv[[MessageWav]{1.wav,2.wav,3.wav}] CampaignName[] options[] ID=321

200913.812 10 2 dial making call tel[xxxxx] live[C:\VGScripts\outbound\SendMessageWav.vgs] am[] fax[] OnHangup[] rv[] options=[]

200913.812 10 2 answering machine detection: disabling as digital line (strDlgcDevName_Network=dtiB1T1) and strDialoutOnAnswerMachine blank or 'ignore' ()

200913.812 10 2 answering machine detection disabled

 

 

On the second call VoiceGuide reads the call from the local database (loaded in using call loader?). The answering machine detection was enabled, and about 1.3 seconds after the call was answered (telephone handset picked up) the Dialogic card informed VoiceGuide that it believes that a live person answered the call. VoiceGuide then started the 'live human answer' script. 1.3 seconds is a pretty average time for person answering call to say 'Hello" and the Dialogic card to report on it so this call looks fine.

 

There did not seem to be an example of the call loaded directly into the external Dialer database available in the traces. Please provide a trace showing this example and we can then comment on it.

[SupportTeam]

We have confirmed that there is a bug with XML file read function which results in the Answering Machine option (<OnAnswerMachine> tag contents) not being read in. Currently the OnAnswerMachine will be left blank when reading XML input - which in turn will result in the error which you seeing.

This bug affects only XML file input. Entries loaded using all other methods (including loading directly into the dialer database) would not be affected by this bug.

The following v7.0.7 contains a fix for this bug: [old link removed]

The fix will be included in all future releases of v7.

Please note that v7.0.7 of VoiceGuide has introduced changes to the dialer database structure. Notes on new table structure and how to work with them can be found here: http://www.voiceguide.com/vghelp/source/ht...rnal_config.htm

[jewillis]

thanks - works great now. I was unaware of the new database structure and was using a pre 7.0.7 and that was the issue for the db load

 

Jeff