Execution Won't Follow Success Path

[Brian in Arnold-fornia]

Hello:

 

I purchased the 4-line professional license last week.

 

I am running VG 5.1.3305 on Windows 2K.

 

It says in your run command module that if a result file exists for that phone line after execution the success path will be followed. Below is the script from my VBS module. The purpose of this script is to stall the caller in a hold loop. If I click on the input box displayed on the screen, this script ends successfully and creates the run result file. The problem is that the success path isn't being followed.

 

VBS Script Below

 

inputBox("Click here to transfer")

 

filename="VGRUNRESULT_$RV_DEVICEID.TXT"

set fso=createobject("scripting.filesystemobject")

set ts=fso.opentextfile(filename, 2, TRUE)

ts.writeline("transfer call")

ts.close

 

set ts=nothing

set fso=nothing

 

'below is the script to use with the enterprise version

'set vg = CreateObject("VoiceGuide.CommandLink")

'vg.Run_ResultReturn $RV_LINEID, "success"

'set vg = Nothing

 

end of VBS script

 

trace from call

 

143328.73 5 [Attorney Loop] Running VB Script...

143328.80 5 RVreplace start (strlen>100)

143329.86 5 Run Script waiting... (shellid=1140, process=1456)

143329.96 5 [Attorney Loop] Playing (C:\VoicePrompts\AttorneyGreeting.wav,c:\voiceprompts\holdwannounce.wav)

143331.53 5 PlaySoundStart ok [C:\VoicePrompts\AttorneyGreeting.wav,c:\voiceprompts\holdwannounce.wav]

143332.51 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143332.62 5 task still running (shellid=1140, process=1456)

143333.73 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143333.99 5 task still running (shellid=1140, process=1456)

143335.11 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143335.21 5 task still running (shellid=1140, process=1456)

143336.32 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143336.43 5 task still running (shellid=1140, process=1456)

143337.54 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143337.65 5 task still running (shellid=1140, process=1456)

143338.76 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143338.87 5 task still running (shellid=1140, process=1456)

143339.98 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143340.09 5 task still running (shellid=1140, process=1456)

143341.20 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143341.31 5 task still running (shellid=1140, process=1456)

143342.43 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143342.55 5 task still running (shellid=1140, process=1456)

143343.66 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143343.77 5 task still running (shellid=1140, process=1456)

143344.91 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

143344.99 5 task completed (shellid=1140, process=1456)

143345.08 5 Found result file: VGRUNRESULT_5.TXT

143345.18 5 Run Result [transfer call, ]

143345.31 5 PlaySoundStop ok

143345.41 5 voicemail used: Builtin (vgp)

143345.49 0 LoadedVgs_Find C:\Voice Guide\system\vm\VmLm.vgp at idx=3

143345.57 0 LoadedVgs_Find C:\Voice Guide\system\vm\VmLm.vgp at idx=3

143345.70 5 [VmLmStart] Running VB Script...

143345.79 5 RVreplace start (strlen>100)

143346.04 5 Run Script waiting... (shellid=1524, process=1456)

143346.67 0 cl Vm_VmbConfig_Get 0002, DeleteAfterForward

 

...at this point it continues in the voicemail box

 

Here are the paths

 

on {success} goto [Transfer to Operator]

on {timeout 200} goto [Voicemail Box 0002]

on {fail} goto [Voicemail Box 0002]

 

====================

The module is set to "wait until VB script completes"

 

 

The result file was found, which is supposed to signal "success" regardless of its content. Isn't that right? It should be branching to the "Transfer to Operator" module. But it is going to "Voicemail Box 0002" instead.

 

As a footnote. The reason I am having to do this is because the professional license I purchased apparently doesn't support the "VoiceGuide.CommandLink" function which is what I was running on the demo. When I upgraded to the professional version I got an error messaging saying that the CommandLink function wasn't supported. I have to use the file method to "talk" to my script until I get authorization to spend the extra money on the enterprise version. I thought the CommandLink function was included in the professional version. Guess not.

 

Please assist.

[SupportTeam]

The result file was found, which is supposed to signal "success" regardless of its content. Isn't that right?

Content of the result file does matter. It is based on the content of the file that VoiceGuide will determine what path to take next. The Success path will be taken if Result Variables are returned:

The result file can be used to return results back to VoiceGuide. This file should contain the list of the Result Variables that you want VoiceGuide to read in, along with their values.

 

The syntax for the VGRUNRESULT_LineNumber.TXT file is:

 

[Result Variable Name]{Result Variable Value}

 

Multiple Result Variables can be specified. For Example, the following contents:

 

[RvName1]{Value1}[RvName2]{Value2}[RvName3]{Value3}[RvName4]{Value4}

Only if the Result Variables are specified correctly will the success path be taken.

If the old format is used:

SUCCESS|FAIL

Result Variable

 

Only one Result Variable can be specified.

Then the Success path will be taken only if SUCCESS or TRUE or YES is specified on the first line of the file...

 

I thought the CommandLink function was included in the professional version. Guess not.

The ActiveX Server functionality (COM Interface functions) is only available in the Enterprise version of VoiceGuide, feature list can be found at: http://www.voiceguide.com/vgFeatures.htm

[Brian in Arnold-fornia]

Putting the word "success" in the file worked.

 

Thanks.