LTympanick Report post Posted 01/17/2007 07:54 AM Created Get Numbers module with following inputs: 4 Minimum entered number length 4 Maximum entered number length 2 Retries 2 Seconds - Pause time between replays Have a sound file to play when not enough digits detected Paths appear as follows: on {success} goto [Look Up Extension] on {fail} goto [Perform Final Updates] We could bypass the Get Extension module due to caller id so I create [Look Up Extension] as a separate module rather than as a verify script in this one. Therefore, no verify script. When I execute the attached script (Get Extension is the module in question) Assume it branches to it: Enter a 2-digit extension - not enough digits detected message plays and it prompts us again - ok Enter a 2 digit extension again - not enough digits detected plays again and then goes to [Perform Final Updates] I thought I would get at least 3 shots at it, the initial prompt & 2 retries...not happening??? If I don't enter anything, it correctly plays the prompt 3 times and if i enter it correctly on the 3rd prompt, i get success. No timeout path specified because that appears to override the interdigit delay specified in the vg.ini file. Any explanation? Share this post Link to post
SupportTeam Report post Posted 01/17/2007 07:56 AM Please post the script used and a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened. Enable logging by setting the log levels to 10 in VG.INI as per below: [Log] VoiceGuide=10 Then restart VG and make a test call which demonstrates the problem. Trace files will be created in VG's \log\ subdirectory. Please post the traces and the VoiceGuide script used. When posting traces/scripts please .ZIP them up and post them as attachments. Share this post Link to post
LTympanick Report post Posted 01/18/2007 01:11 AM Here's the script & here's the log. Please note: I have no timeout path defined here because the number of seconds specified in that appears to impact the seconds between replays and that's not what I want to happen. The inter-digit timeout should not impact seconds between replays. With no input at all from the caller, one simply wants the prompt to replay again in "seconds between replay" seconds. With an interdigit timeout, meaning some input was entered but not enough, I want my error message to play (not enough digits were dected) and then immediately replay the prompt. It shouldn't delay, in this case, by the seconds between replay param, which is seemingly what is happening. With enough digits entered, it should return success and take the appropriate path which it appears to do just fine. Otherwise, it should continue to prompt for the input until # of retries is exhausted and then produce fail. In this case, it appears to be cutting me short by 1 when not enough digits detected. Thanks. Inbound.vgs 0117vgm.txt Share this post Link to post
SupportTeam Report post Posted 01/18/2007 10:40 AM Thanks for posting the trace capturing the problem and script. All appears as expected in this trace. I think the confusion here is that you expect that the file "Enter 4-digit extension.wav" will be played if caller enters some digits but not the full number. This is not as per design. The ‘Entered number was not correct length’ message will be played in this case (if specified). (That message is "Not enough digits detected.wav" in your script). The delay between "Not enough digits detected.wav" and "Enter 4-digit extension.wav" is because script is waiting for caller to enter some data. Playing "Not enough digits detected.wav" is regarded as one of the replays. From: http://www.voiceguide.com/vghelp/html/modGetNumber.htm If the caller pressed at least one key and then uses the "#" key or if VoiceGuide times out awaiting next key press then the ‘Entered number was not correct length’ message will be played, and VoiceGuide will wait for the caller to enter the numbers again (if ‘Entered number was not correct length’ message is not specified then the then original ‘Ask caller to enter number’ message will be played). 193819.34 2 state [Get Extension] Playing (prompts\Enter 4-digit extension.wav) ... 193821.84 2 tw PlayEnd 2 200921 ... 193823.27 2 state [Get Extension] Number Input 56 ... 193826.53 2 timer fired EV_TIMEOUT_ENTERDATA 193826.53 2 state [Get Extension] Playing (prompts\Not enough digits detected.wav) ... 193829.05 2 tw PlayEnd 2 208109 ... 193831.23 2 timer fired EV_TIMEOUT_REPLAYMSG ... 193831.23 2 state [Get Extension] Playing (prompts\Enter 4-digit extension.wav) Share this post Link to post
LTympanick Report post Posted 01/19/2007 12:05 AM Ok, now I get it. My best bet is to have my "Not enough digits were detected" error message modified so that its says "Not enough digits were detected, please try again". I was confused because the main message would play again if I mixed a time-out scenario along with incorrect number of digits, and that would count as a retry. I agree, it appears to be fine the way it is. Thanks for the clarification. Share this post Link to post