Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Call Handler Transfer Confusion

Status
Not open for further replies.

MitelInMyBlood

Technical User
Apr 14, 2005
1,990
US
UCXN 8.0.2

I'm struggling between what appears to be otherwise good documentation and a UCXN system that doesn't appear to work the way the docs says it does, specifically with call handler transfers

Documentation suggests a System CH can directly transfer to any valid system DN, regardless whether a mailbox user or not. In practice this seems only true in the case where caller input is accepted. If I try to configure a CH with a std, closed or temp. schedule I see an "extension" field in the transfer rules which seems to have no effect. Taking this a step further, if I 'edit' the transfer rule (i.e., say the Alternate rule) - I have it set to enabled with the 'transfer action' set to transfer calls to a valid (on-system) DN but it still doesn't perform the transfer. Calls to this CH instead hear a default system greeting that the <mailbox name> is not available & get prompted to leave their message at the tone. This is a brand new "test" call handler & I've not configured anything deeper than trying to figure out why it doesn't work as expected.

Thanks for any tips.


Original MUG/NAMU Charter Member
 
Figured it out...

I guess I once again gave the documentation too much credit ;)
- - this was not documented - -

Seems "the key" to accomplishing what I wanted to do was to go a step further down into the Edit Greetings menu (even though the intent was and still is to have no greeting)

Within the "edit greetings" menu under the Alternate greeting (since I had previously selected the Alternate transfer rule) it is necessary for the alternate greeting to be enabled, then set the caller to hear nothing. Next, in the "After Greeting" field you must place a tic mark to select "call handler" and then select the same call handler as the one you're configuring. Then below this you place a tic mark in the "attempt transfer" field.

Now it all works as desired.

For reference I had two pieces of documentation I was working with, neither of which mentioned this last (required) step to perform a call transfer without caller input. The docs were: Chapter 6 System Admin Guide for CUXN and Chapter 8 in "Cisco Unity Connection" by David Schulz (Cisco Press) (First printing June 2011). Schulz's book is fairly thorough. I'm a little surprised he missed this.



Original MUG/NAMU Charter Member
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top