It sounds like the * should direct the caller to the Goodbye Call Handler. This can be set in the subscriber's Caller Input section. Click on the * and then set the Action for "Say Goodbye". This same action can be set in a template before importing your users and assigning them to that template. If you have all of your users already defined, you could make this update via the Bulk Edit tool.
That's correct... caller input is only active while the greeting itself is playing (i.e. when outside callers are listening to that subscriber's greeting).
In 4.0(1) and later, the exit destination for subscribers is configurable - so when a subscriber hits "*" when they're at the top level subscriber menu (i.e. the one that says "you have X new messages... to hear new messages, press 1, to send a message...") it will go to whereever you indicate it should on a per user basis. You can set this value using BulkEdit if you like and, of course, also in the SA and the Audio Text Manager applications.
In 3.x and earlier, however, it's hard coded to send the subscriber back out to the opening greeting call handler created by the Unity setup and is not adjustable.
I've the same scenario with Unity 4.0(3)sr1. I've changed the caller input key * to action say goodbye, but when that subscriber hit the key * when he is at top level menu, it still goes to opening greeting call handler instead of goodbye? What could be wrong in my case?
Again, the caller input keys are only active when outside callers are listening to the subscriber's greeting... this is _not_ where we determine what to do when a subscriber hits * when they are in the subscriber conversation. They have nothing at all to do with one another.
There's an exit destination that can be set for each subscriber on the conversation page in the SA. This is where we pull the destination to send the subscriber when they exit their conversation by hitting *. You can change this per user in the SA or in bulk in the Bulk Edit utility.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...