Menu using Access ports - different routing for 0 vs no response 1

[fonchick]

Good Morning,

I hope you all can help. I am working on an issue where I have created a menu in Symposium and there has been a request to route when a caller presses 0 differently than when a caller doesn't press anything. I had originally scripted it

so that where menu_choice_cv equals
value 1: ROUTE CALL 1234
value 2: ROUTE CALL 1235
value 3: ROUTE CALL 1236
value 4: ROUTE CALL 1237
value 5: ROUTE CALL 1238
value 6: ROUTE CALL 1239
value 7: ROUTE CALL 1240
value 8: ROUTE CALL 1241
value 9: ROUTE CALL 1242
value 0: ROUTE CALL 1243
DEFAULT: ROUTE CALL 1244
END WHERE

However, whenever I didn't press any option, it was going to the value 0: routing to 1243 instead of 1244...Any suggestions?

 

[Sympology]

You know I've never tried 0 !
Maybe you could get around it by using a script varible with an entry of 0 (integer, string?)
Bit of guess work here as I've never tried it.

Stu..

Oh course I'll come back at lunchtime. When is it? Oh thats a shame, so's mine.

 

[sandyml]

Change the default value for your variable menu_choice_cv to 1244. Looks like you will find that it is currently set at 1243.

 

[fonchick]

Thank you Stu and Sandy!

We have menu_choice_cv used in all of our menus and the default value is 0. However, in all of our menus prior to playing the menu, I have assign 0 to menu_choice_cv (thinking that I needed a nul value so it could assign the value that the caller imputs to that value)...If I assign a bogus value such as 99 to the menu_choice, then I am able to follow my default value and my 0 out...

Now, my script states

assign 99 to menu_shoice_cv and then my menu plays. After testing if a caller doesn't imput anything, then the caller gets the default routing...if the caller imputs 0 then then get routed to the VALUE 0 location.

I learn something everyday!

Thanks!

 

[Sympology]

LOMAO !

Just had a user complaining that Option 0 wasn't working! The script has been active for 6 months and they've only just spotted the fault. Guess how I fixed it (Hint see above)!

Stu..

Only the truly stupid believe they know everything.
Stu.. 2004

 

[sandyml]

Well, ya know the old Will Rogers saying: "It ain't the things you don't know what gets ya into trouble. It's the things ya know fer sure what ain't so!

 

[Jeff325]

Have you tried assigning a value other than 0 to the Call variable prior to this portion of the script?

 

[fonchick]

Jeff,

i had not tried assigning 0 to the call variable prior to this menu. We use this call variable for all our menus throughout Symposium and the default value in our script variable is 0. We have so many menus that to ensure that the call is not carrying any value in the variable, we always put assign 0 to menu_choice_cv prior to playing a menu and collecting digits. With this excercise, I have learned if my default value is different than my 0 value, then I need to assign a bogus number such as 99 to ensure that it will work...

fonchick

 

[Jeff325]

Call Variables are script specific - the call receives a copy it as it enters the script and uses that information until told otherwise - you are only allowed a few Call Variables because they can be reused at will in different scripts.