$rv[Pathapp] And The Trailing "\"

[iTime]

 

 

$RV[PathApp] is not a VoiceGuide system RV, are you sure that your script doesnot creae this $RV itself?

 

 

The code below is from "C:\Program Files (x86)\VoiceGuide\Scripts\Pickup Line And Record\StartRec.vbs" that are installed with VG as a sample script (,thus it is not an RV created by us):

As you can see, there is no "\" between the provided RV and "Scripts....", which will break with this version of VG.

 

 

set vg = CreateObject("VoiceGuide.CommandLink")

vg.Line_Pickup 0, "$RV[PathApp]Scripts\Pickup Line And Record\Pickup Line And Record.vgs"

'we have now started recording on the 1st device controlled by VG.

'now lets show a box which allows user to stop recording:

msgbox "Recording now..." & vbCrLf & "Press OK to stop.", vbOKOnly + vbInformation , "VG Call Recorder"

 

There is another example in "C:\Program Files (x86)\VoiceGuide\System\vm\vm_ftp.vbs", which is not made by us either. This script also uses [PathApp] RV, and does not include "\" before "log\...." either.

 

Set ftpcmds = fso.OpenTextFile(InFile, ForWriting, True)

'OutFile : stores FTP responses

'OutFile = fso.GetSpecialFolder(TemporaryFolder) & "\" & fso.GetTempName

OutFile = "$RV[PathDataVm]" & "vm_ftp_ret_$RV_MM$RV_DD$RV_HH$RV_NN$RV_SS_$RV_LINEID.txt"

OutFile_SaveLog = "$RV[PathApp]" & "log\$RV_MM$RV_DDftp.txt"

 

So, your fix to call a defined vbs upon "OnNotAnswered" correctly, but when executing the vbs, it break because the path defined inside that vbs file to set a path to an inclusive fails.

Please see attached file and the VBS file. I assure you it has been working fine before this patch.

 

 

For the tts issue, I added another set of log, which shows the call gets stuck on "PlayCallOutGreetings."

I waited about 55 seconds and hung up because it does not proceed after "tts generate start..."

I can see 0 byte of wav file ("tts_3_1.wav" in this example) is created in "temp" folder, but the process does not proceed further.

 

Thanks.

 

VGLog_VBSPath.zip

VGLog_TTSIssue.zip

[SupportTeam]

This version should fix the TTS issue:

 

[old link removed]

 

 

The $RV[PathApp] in v7.5 does not have trailing "\", and it looks like its been like this for a while. From which version of VoiceGuide are you upgrading from?

 

BTW. here is trace excerpt from your post in 2013: http://voiceguide.com/forums/index.php?showtopic=10388

 

vgEngine posted on that topic shows that on your system in 2013 the path RVs were already defined as:

 

125211.903 6 3 1 rvns add PathApp|C:\Program Files (x86)\VoiceGuide
125211.903 6 3 1 rvns add PathVoiceGuide|C:\Program Files (x86)\VoiceGuide
125211.904 6 3 1 rvns add ScriptPath|C:\Program Files (x86)\VoiceGuide\Scripts\IntelliTime\
125211.904 6 3 1 rvns add ScriptsPath|C:\Program Files (x86)\VoiceGuide\Scripts\IntelliTime\
125211.904 6 3 1 rvns add PathScript|C:\Program Files (x86)\VoiceGuide\Scripts\IntelliTime

 

 

 

The examples that you refer to will need to be modified to reflect that PathApp does not have "\". (those examples are quite old - they were inherited from v6).

[iTime]

From which version of VoiceGuide are you upgrading from?

 

It is to be upgraded from same 7.5 version. Please see the screen shot below.

 

 

And I can assure you this vbs file in question is currently running fine without trailing "\" on other 7.5 instances.

Please see the following screen capture I got from one of the customers who are using the 7.5 version before this fix: It DOES have "\" at the end of the value for "$RV[PathApp]".

 

 

 

The next screen shot is a compiled file from the server with your current fix: You can see the value does not have "\"

 

Please note that I added the comment in the code:

 

"Generating the script path is different from those scripts inside VGS files"

 

This is in order to remember that the result variable returned different values (with or without "\" according to the location where it is called.)

This VBS file (that executes upon "NoAnswered" case) is stored in "C:\Program Files (x86)\VoiceGuide\Scripts\IntelliTime\VbsExecutable", which is a sub folder of the place where all the vgs files are stored.

 

So it seems, if this RV is referred from VGS files, it returns without "\", but if this RV is referred from another folder (i.e. sub folder), it returns with "\".

Now with this new version you have provided, it seems the RV returns the path without "\" regardless of where is it called.

 

Let me know whether you will keep this new behavior or not so that we can decide to change our script accordingly, but please note you did change the behavior of the returned result.

 

BTW, this new patch has fixed the TTS issue.

Thanks.

 

 

 

 

[SupportTeam]

And I can assure you this vbs file in question is currently running fine without trailing "\" on other 7.5 instances.

 

Please post vgEngine traces from those other systems. Please ensure the vgEngine trace captures the VoiceGuide service startup.

 

 

the result variable returned different values (with or without "\" according to the location where it is called.)

 

Please post vgEngine traces that capture both cases. Please ensure the vgEngine trace captures the VoiceGuide service startup.

 

Please .ZIP up trace files before posting.

[iTime]

Well, the other instance is the customer's production environment so we are not able to run the test cases freely as requested.

 

Instead, I included the log and the temp file that was generated several days ago, and the original VBS file with the current folder structure.

Since the log (3/6/2016) did not include service startup, I restarted the service to capture this information.

This is all I can provide regarding the path issue.

 

Please let me know if it is good to use the latest fix file so that we can provide it to the customer.

 

Again, thank you very much for your prompt help.

 

 

 

 

IVR_Ch.zip

[SupportTeam]

Looks like right now once the call is answered the $RV[PathApp] is set to value that does not have the trailing "\". This is for both incoming and outgoing calls. The time the $RV[PathApp] is assigned can be seen in vgEngine trace file.

 

But before the call is answered the $RV[PathApp] has a value that does have the trailing "\".

 

So right now if an outgoing call is never answered then the "OnNotAnswered" and "OnRetriesEnd" scripts will have $RV[PathApp]replaced with a directory path expression that does have the trailing "\".

 

The convention adopted in VoiceGuide is that the path related variables should not have a trailing "\". The software will be modified to change the "before the call is answered" $RV[PathApp] value to not have the trailing "\" - matching the value of the $RV[PathApp] is set to after call is answered.

[SupportTeam]

In this version the $RV[PathApp] does not have the trailing "\", even before the call is answered. So "OnNotAnswered" and "OnRetriesEnd" scripts will have $RV[PathApp]replaced with a directory path expression that does not have the trailing "\".

 

[old link removed]

 

 

 

The standard used by VoiceGuide is that VoiceGuide shall not include trailing "\" in system $RVs that specify path expressions.

[iTime]

OK, I will change our code for the path values.

BTW, the provided recent patch does not work: VG stops as soon as it tries to start. And I see the following error from the Windows Event Viewer (Attached screen shot)

No log files have been generated either.

 

 

I restored the previous one (VoiceGuide_7.5.1_160309_hsdw.exe) for now, but it will be much appreciated if you can provide the stable patch as soon as possible (our customer's waiting)

 

Thank you.

 

 

[iTime]

OK, this works fine for catching up "abruptly disconnected" call to trigger associated VBS with the "pathApp" change as you announced: no TTS or functionality issue of the application either.

 

Thanks.

[SupportTeam]

OK, thanks for letting us know these issues are now resolved.