CISCO UNITY CONNECTION 8.6 TWO DIGIT CALLER INPUT

[chris henderson]

Good day Guys ,

        i am having a bit of a challenge configuring  caller inputs in call handlers .

i already have options 1 thru 9 configured however i have an option 10 and 11 in the call handler MAIN_GREETING

i did a work around in restriction tables to allow option 10 and 11 with a translation patterns on call manager to the destination

but i also have another call handler SUB GREETING with option 10 and 11  is there a way to specify this

any assistance will be greatly appreciated .

[lindborg · Accepted solution]

So I assume you mean you created a call handler with an extension of 10 and 11 that you used and now the 10 and 11 are taken you can’t make your trick work a 2^nd time.

Couple things here… First, having 12 menu items in a single menu is not fantastic – if at all possible setup sub menus that limit the list to 6 or 7 max (lots of usability stories around maximum menu lengths and time on call vs. hanging up and such).  If that’s not possible and you simply must have multiple menus with 12 options each you have a couple options.

1. You can do the same trick but use partitions to separate the call handlers – this way you can have two call handlers with an extension of 10 or 11 in the directory and they wont conflict – make sure the handler that hosts the menu you are creating are in the same partitions as the appropriate “sub handlers”. 
2. You can use the “lock” option on the menu entry key to “string together” two call handlers with menu entries.  So on call handler “A” you have the “1” key set to locked and set to send to the greeting for call handler “B” – in your greeting for A you have “press 2 for x, press 3 for y…. press 10 for ZZ press 11 for YY press 12 for QQ”.  On call handler b you have keys 1, 2 and 3 set to what you want.  The 1 key pressed in A will immediately go to call handler B, throw the 1 away and then take the key they hit next for input - 0, 1 or 2 in this case.  You can have call handler b set to play a few seconds of silence and then go back to A’s greeting if the user doesn’t hit anything.  In this way you can effectively create a very large number of menu options.

Personally I don’t care for those solutions and would work on creating smaller menus… but that’s just me.

[Gustavo Moreschi]

Another thing that I tested, but it looks like is not possible to get rid of this " sorry"  message was increase " wait for additional digits 1000 milliseconds....I was able to have enough time to enter the second digits without hearing "sorry", but the system did not recognize as a valid option.

So the only way I'm able to enter 2 digits working is hearing "sorry" message when I enter the first digit..., but is not nice...

About option 1 not sure how to do that...if you could explain in more details, I appreciate!

Thanks!

[chris henderson]

thanks for the feed back here is an emample of the call flow

PSTN ----  CUC ----- AA

                        OPTION 1 - GO TO EXTENSION 1111

                         OPTION2- GO TO EXTENSION 2XXX

                        OPTION 3-........... ETC

                          ............

                         .............

                         OPTION 10 - GO TO EXTENSION 2020

                         OPTION 11 - GO TO EXTENSION 2021

HOW can i get option 10 and 11 to work .

because i also have another call handler with

                       OPTION 10 - GO TO EXTENSION  3000

[Gustavo Moreschi]

Hello Lindborg,

Thanks for your comment on this threat. You gave us another way to look into this. I have just one question though.

After I followed your second option. It works very well, except all the time when I choose press 1 follow by any other number, I'm hearing " Sorry..." right after when I press 1. Then when I enter the second digit, it works just perfect, but I was wondering if there is a way to remove/disable this audio "sorry" message from CUC 8.6 when we press 1.

Thank you!