[cisco-voip] call handler won't transfer

[Jared Olson]

In the Unity Tools Depot you can use the ATManager (Audio Text Manager) to see the call handlers setup in an nice interface.  This might help to see if something is misconfigured or if Unity is simply unable to handle all the routing based on the current config.  Then again, I don't have Unity 4.0(5) I have 4.0(3) so there may be some changes I'm not familiar with.

Jared

>>> "Rossella Mariotti-Jones" <rossella at chemeketa.edu> 04/20/06 04:58PM >>>
We are using CallManager 4.1(2)es63 and Unity 4.0(5) and we are trying
to set up hotdials or ringdowns where a user is transferred to a message
prompt as soon as he/she picks up the phone. The message will give the
user 3 options, i.e.: "for HR press 1, for Accounts Payable press 2, for
Media press 3". We have a CTI route point with a DN that forwards all
calls to voicemail. Then in Unity we have a Call routing that sends the
forwarded calls to a call handler. In this call handler we set up the 3
caller inputs, at each caller input the call is transferred to another
call handler which then transfers it to the extension or outside phone#
(this is the option: Yes, ring a subscriber at this extension under Call
Transfer). The problem is that the process always skips the call
transfer piece. Even if we eliminate the second tier of call handlers
Unity doesn't dial out and the call transfer piece is skipped. We're
thinking that maybe there is a setting that we need to turn on for Unity
to be able to dial out. Does anybody have any ideas? Thanks in advance.

 

 

--

Rossella Mariotti-Jones rossella at chemeketa.edu 

Chemeketa Community College, Information Technology

503-589-7775