Vg Is Timing Out On A Long Running Query

[gwatkins]

I have a VB script that runs for about 5 seconds that executes a stored procedure. If I take out the stored procedure call, it will complete normally. Is there a way to tell VG to wait for X seconds before actually trying to timeout. I already have a timeout path that waits for 7 seconds. However, I think that VG is transferring out of the script before the 7 seconds is up. Any help would be greatly appreciated.

 

Thanks

Garry

 

[SupportTeam]

If you have a timeout path specified, then VoiceGuide will wait the amount of time specified in the timeout path before continuing.

 

If you think that you are seeing the VBScript module timing out earlier then it should then please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

Then restart VG and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces and the VoiceGuide script used.

 

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

[gwatkins]

Sorry, I did not have the log files and scripts with me last night when I posted it. I have attached them now.

 

Thanks

RemotePunchInOut.zip

0629vgm.zip

[SupportTeam]

Trace shows the [Punch In DB] module starting at 10:17:38 :

 

101738.11 1 state [Punch In DB] Running VB Script...

 

The started VBScript continues to run without returning any results to VoiceGuide and VoiceGuide then times out 7 seconds later at 10:17:45 and goes to the module pointed to by the Timeout path :

 

101745.72 1 event EV_TIMEOUT_CHECKONSTATE, iCode=9007 state=1501

...

101745.72 1 next module is [DB FAILURE] (idx=9)

 

So it's functioning as expected. If you want to give the VBScript more time to run before timing out on it then you should increase the timeout value...