The sequence of DTMF tones that an originating Cisco Unity
location sends to the receiving location begins with # (pound) and includes a
second tone that distinguishes the type of handoff (sign-in, transfer, or live
reply). By default, the Unity Connection opening greeting and other call
handlers are configured to ignore any additional caller input following a #
key. In such a configuration, all cross-server handoffs fail.
You have a couple of options for changing the behavior on a
Unity Connection receiving location so that cross-server handoffs are performed
successfully:
-
Change the opening greeting (or other existing call handler that
receive the cross-server handoff calls based on your routing rule
configuration) to allow additional input.
-
Create a new call handler and direct-call routing rule
specifically to handle cross-server calls. The direct call routing rule should
route calls to the new call handler based on criteria that apply to
cross-server calls—the calling number of any originating Cisco Unity location,
for example, or the cross-server dial string that the originating locations
dial to reach the receiving location. (If you do not want other calls to match
the routing rule, select criteria that are unique to cross-server calls.)
Do the following procedure on each Unity Connection receiving
location to configure the opening greeting or other call handler to allow
additional input after the # key, and, optionally, to create a new direct-call
routing rule.