VoiceGuide IVR Software Main Page
Jump to content

Vg7 Does Not Generate Vbs File In Temp Folder

Recommended Posts

Hello support team,

 

I have just installed VG7 with HMP driver on Windows2008 R2 and while testing, I found out VG does not process an incoming call from the first module.

 

If you see the log, "CheckTaskType" module is supposed to parse and generate a vbs file in "Temp" folder and usually records it to the log, "script will be ran from file: C:\Program Files (x86)\VoiceGuide\temp\vbs_xx_1.vbs", like the lines below:

 


rv dbg rv_retrieve did not find [isBroadcasting] (....

script will be ran from file: C:\Program Files (x86)\VoiceGuide\temp\vbs_xx_1.vbs.....

 

 

However, the log shows "runscr waiting. wait=1..." (without "Script will be ran...." part) then hangs up the call.

Would it be a permission problem? I designated an application user to start VG service and that account is in Administrators group.

Or something else?

 

Thanks for your help in advance.

 

 

Logs.zip

Share this post


Link to post

Trace shows that the VBScript in module CheckTaskType was started and ran and functions RvSet IsMoveAutoNotify and RvSet TTSSpeed were called from that VBScript.

 

When VBScript finishes the 'next' module is not set, and no 'success' was returned, so VoiceGuide takes a fail path from that module (and if Fail path is not defined then VoiceGuide will hangup - which is what happens here)

 

To determine what is happening in the script we would recommend adding some Admin_TracelogAdd() function calls into your script. You can see how the script progresses.

 

Please see: http://www.voiceguide.com/vghelp/source/html/com_admin_tracelogadd.htm

 

v7.4.2 uses a different way to execute the VBScript/JavaScript modules - this is why the vgEngine trace looks a bit different. You should see that VBScripts/JavaScripts run a lot faster in v7.4.2 then in previous VoiceGuide versions.

 

Will check whether the actual "VoiceGuide\temp\vbs_xx_1.vbs" files are still created - they do not need to be created but maybe their creation can be enabled for debugging purposes.

 

NB. v7.4.1 can still be downloaded from [old link removed] if required.

190753.988   4   3   1       runscr start - ClearScriptV8
190753.988   4   3   1       runscrunscr new VBScriptEngine call
190754.032   4   3   1       runscrunscr new engine created
190754.033   4   3   1 state [CheckTaskType] RunScript, wait=1
190754.045   4   3   1       rv    replace start (strlen>500)
190754.056   4               rv    dbg   rv_retrieve did not find [UserID] ( 55 73 65 72 49 44)
190754.056   4               rv    dbg   rv_retrieve did not find [AutoNotifyCallID] ( 41 75 74 6f 4e 6f 74 69 66 79 43 61 6c 6c 49 44)
190754.057   4               rv    dbg   rv_retrieve did not find [AutoNotifyMoveNotificationCallID] ( 41 75 74 6f 4e 6f 74 69 66 79 4d 6f 76 65 4e 6f 74 69 66 69 63 61 74 69 6f 6e 43 61 6c 6c 49 44)
190754.057   4               rv    dbg   rv_retrieve did not find [IsHiring] ( 49 73 48 69 72 69 6e 67)
190754.057   4               rv    dbg   rv_retrieve did not find [IsBroadcasting] ( 49 73 42 72 6f 61 64 63 61 73 74 69 6e 67)
190754.057   4   3   1       runscr waiting. wait=1
190754.060   4   3   1       moh file not specified
190754.060   4   3   1       runscr .Execute call
190754.080  16               remoting link constructor activated: vgServices_CommandLink
190754.086  16   3   1 rem   RvSet IsMoveAutoNotify, false
190754.088  16   3   1       rv    add   IsMoveAutoNotify|false
190754.092  16   3   1 rem   RvSet TTSSpeed,
190754.092  16   3   1       rv    add   TTSSpeed|
190754.093   4   3   1       runscr .Execute returned. iRunWait=1
190754.093   4   3   1       runscr RunWait_1 script completed
190754.094   4   3   1       runscr RunWait_1 taking fail path as script completed and no next module set
190754.102   4   3   1       HangupCall (RunModule_Script_AfterScriptStarted_1) crn_in=0, L1=Connected, L2=Running_Normal, lPlayId=0, lRecId=0

Share this post


Link to post

Looks like current v7.4.2 does not create the "VoiceGuide\temp\vbs_xx_1.vbs" files as it is unnecessary to create them.

 

Future versions will have option to have these files created for debugging purposes. To enable this option you will need to edit VG.INI file, adding this entry to the [moduleRunScript] section:

 

SaveToFile=1

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×