VoiceGuide IVR Software Main Page
Jump to content

callrouting problem

Recommended Posts

Hello VoiceGuide Team, 

Unfortunately, we have an error in our call routing process. Directly at the beginning after the greeting, a PIN should be requested, unfortunately no input time is waited here, so a second process is started immediately. In the second run, an input is then waited for... as it should be.
 
Unfortunately, we can't find the error here and would like to kindly ask if you might see something we don't.
 
I have attached the script once.

Wachobjekt.vgs

Share this post


Link to post

Can you please post the VgEngine file capturing the incoming call. We can the see what has happened on the call and advise.

Most likely the issue here is that you have "Do not wait for VBScript to complete" option selected in the previously executed "CheckRufnummer" module, but that module's VBScript is also calling the "Run_ResultReturn" API.

The "Run_ResultReturn" API tells VoiceGuide's callflow executing engine to take a specific path out of the current module. So if that current module happens to be "PINEingabe" when the VBScript started by the "CheckRufnummer" module completes, then a path out of that "PINEingabe" module will be taken as the effect of that "Run_ResultReturn" API call...

 

Resolution would be to change the "CheckRufnummer" module's setting to be "Wait until VBScript completes" (or remove the "Run_ResultReturn" API call).

Changing that module's setting to be "Wait until VBScript completes" looks to be the right thing to do, as that module is querying a database, and we can see that you have specified the following path to be taken in case the database query is taking too long:

on {timeout 5} goto [DB-Fehler]

and above timeout path will only be in force while the callflow is in that module.

Share this post


Link to post

Hello VoiceGuide Team,

Attached you will find the vgEngine file and the call events, in which several incoming calls should be visible.

If you could briefly confirm, based on these, whether the issue can indeed be resolved by changing the settings of the “Check Rufnummer” module to “Wait until VBScript completes”, I would test this and provide feedback.

Many thanks in advance!

0129_1546_vgEngine.txt

0129_CallEvents.txt

Share this post


Link to post

Trace confirms that "Run_ResultReturn" call from module [CheckRufnummer] is whats causing VoiceGuide to exit [PINEingabe] and take "success" path to module [PINVergleich].

154711.507   17   3   1     1 state [CheckRufnummer] RunScript (no wait) | 
154711.508   17   3   1     1       modvbs QueueUserWorkItem vbScript
154711.508   17   3   1     1       modvbs check for success path
154711.508   17   3   1     1       find_next_vgm module=[AnzahlPINVersuche] (trigger={SUCCESS})
154711.508   17   3   1     1 t     timer clear force=False(RunModule_begin)
154711.508   17   3   1     1       RunModule start Evaluate, [AnzahlPINVersuche], vgm=10, previous_vgm=2
154711.508   17   3   1     1 state [AnzahlPINVersuche] Evaluate [0] | 
...
154711.509   17   3   1     1       RunModule start Get Numbers, [PINEingabe], vgm=60, previous_vgm=10
154711.509   17   3   1     1 state [PINEingabe] Number Input | 
154711.510   17   3   1     1       PrepareAndPlayWavAndTts start iModuleIdx=60, iPlayFileIdx=1, bMakeTtsFile=True, sSoundFileIs=
154711.510   17   3   1     1       rv    replace start [$RV[ScriptPath]\WOAnsagePINEingabe.wav]
154711.510   17   3   1     1       rv    replace end   [C:\INSOCAM\\WOAnsagePINEingabe.wav]
154711.510   17   3   1     1       PrepareAndPlayWavAndTTS sPlayFile=C:\INSOCAM\\WOAnsagePINEingabe.wav
154711.511   17   3   1     1 state [PINEingabe] Playing wav (C:\INSOCAM\\WOAnsagePINEingabe.wav) | 
154711.511   17   3   1     1       PlayStartOrFireEventFinished strSndFile: C:\INSOCAM\\WOAnsagePINEingabe.wav
...
154711.514   12   3   1     1 task  scr Run_VBS vgm=2, file=, RunUsingClearScript=True
154711.514   12   3   1     1 state [CheckRufnummer] Run Script vbs, onhold= | 
154711.514   12   3   1     1       rv    replace start - not logging - input length is >1000
...
154711.518   12   3   1     1       scr   ClearScript VBS engine used
154711.519   12   3   1     1       scr   ClearScript VBS new VBScriptEngine completed
154711.519   12   3   1     1       scr   ClearScript VBS AddHostObject vg completed
154711.519   12   3   1     1       scr   .Execute call
154711.544    3               api   vgServices_CommandLink started
154711.547    3   3   1     1 api   RvSet RV_ErkannteNummer, 491703480746
154711.547    3   3   1     1       rv    add   RV_ErkannteNummer|491703480746
154711.548    3   3   1     1 api   RvSet RV_OTID, 31759
154711.548    3   3   1     1       rv    add   RV_OTID|31759
154711.548    3   3   1     1 api   RvSet RV_VLID, 46417
154711.548    3   3   1     1       rv    add   RV_VLID|46417
154711.549    3   3   1     1 api   Run_ResultReturn success
154711.549    3   3   1     1       q_scr +     cmdRun_ResultReturn lcode=0 scode=[]
154711.549   17   3   1     1       q_scr run   cmdRun_ResultReturn 0  action_id=0, crn=0 [0|0|0|0|0][success|||||] 00:00:00 max:1|0,4942
154711.549   12   3   1     1       scr   dispose call
154711.550   12   3   1     1       scr   sModuleType=Run VB Script
154711.550   12   3   1     1       scr   .Execute returned. iRunWait=0
154711.550   12   3   1     1       scr   wait=0. exiting thread
154711.551   17   3   1     1       Run_ResultReturn_InqScr keyword return -  iRunWait_VgmIdx not set
154711.552   17   3   1     1       rv    add   PINEingabe_ResultReturn|success
154711.552   17   3   1     1       path {success} found (at offset 70)
154711.552   17   3   1     1       find_next_vgm module=[PINVergleich] (trigger={success})
154711.552   17   3   1     1       Run_ResultReturn_InqScr state: .iRunWait_VgmIdx=-1, iVgmIdx=60
154711.552   17   3   1     1 t     timer clear force=False(RunModule_begin)
154711.552   17   3   1     1       RunModule start Run VB Script, [PINVergleich], vgm=11, previous_vgm=60
154711.552   17   3   1     1 state [PINVergleich] RunScript | 

 

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
×