Jump to content


< Back to Forum


 

Verifying Entered Number Using Vbscript Always Takes "fail" Pa


  • Please log in to reply

#1 iTime 13 November 2015 - 08:22 AM

Hello,

 

After we upgraded to V7.5, we encounter a problem on number format verification.

In the script, we check if the provided PIN length is between 3 and 5 using VBScript in "Verify Entered Number," then return "verify_passed" or "verify_failed" otherwise.

But the script takes "fail" path even if the format is correct.

 

We could see that the result was returned as "Verify_Passed" but the log shows "....Verify_Pass} not found" then goes (back) to "PlayPasswordExpired" module and loops between those two module.

The paths we set on this "GetNewPassword" module is, so upon success, "GetNewPasswordConfirm" module should play.

 

Was there changes between V7.4 and 7.5?

 

Thanks.

on {success} goto [GetNewPasswordConfirm]
on {fail} goto [PlayPasswordExpired]
 

 

 

134042.631  23   3   1 rem   Run_ResultReturn [verify_passed] 13

134042.631  23   3   1       q_scr +     cmdRun_ResultReturn 0 
134042.631   6   3   1       q_scr run   cmdRun_ResultReturn sCode=[] iActionID=0, crn=0 [0|0|0|0|0][verify_passed|||||] 00:00:00 max:1|00:00:00.0005000
134042.631   6   3   1       q_scr +     evScriptEvent 9221 EV_MODGETNBRS_VERIFY_PASS
134042.631   6   3   1       q_scr run   evScriptEvent sCode=[EV_MODGETNBRS_VERIFY_PASS] iActionID=0, crn=0 [0|0|0|0|0][|||||] 00:00:00 max:1|00:00:00.0005000
134042.631   6   3   1       se    EV_MODGETNBRS_VERIFY_PASS 9221  0|0|0  || LineState=LS_RUN_WAITTILLFINISHED
134042.631   6   3   1       LsRunWaitTillFinished EV_MODGETNBRS_VERIFY_PASS lCode2Str=EV_UNKNOWN_9221
134042.631   6   3   1       path {EV_MODGETNBRS_VERIFY_PASS} not found
134043.199   8   3   1 timer EV_TIMEOUT_CHECKONSTATE

 



#2 SupportTeam 13 November 2015 - 01:17 PM

The version below fixes the number script verification issue which you encountered. Please update system to this version:

 

[old link removed]

 

Please post traces as before if you still encounter any problems.

 

 

To change from one release of VoiceGuide v7 to another:

1. Stop VoiceGuide Service and exit all VoiceGuide programs. (eg Script Designer, Voicemail Manager, etc) and all other programs.

2. Run the VoiceGuide install and install into same directory as existing installation. (Do NOT uninstall the previous VoiceGuide installation).

3. Start  VoiceGuide service.

 

Running a VoiceGuide install over the top of an existing install will NOT overwrite existing configuration or license files (Config.xml, ConfigLine.xml, VG.INI, VmBoxList.xml, etc) and will not remove any of users script or sound files, and will not remove any log files etc



#3 iTime 17 November 2015 - 02:49 AM

I can confirm that the issue has been fixed with the patch.

Thanks for the prompt action.