[cisco-voip] Unity Auto Attendant question

[Brian Meade]

The AA is probably listed as the redirecting number coming back to CUCM.
When it gets forwarded back to voicemail, Unity Connection sees 2
redirecting numbers and by default Unity Connection checks the first
redirecting number to determine where to send the call.  You can override
this behavior by checking "Use Last (Rather than First) Redirecting Number
for Routing Incoming Call" under System Settings->Advanced->Conversations.

The other option you have would be to un-check "Redirecting Diversion
Header Delivery - Inbound" on the CUC SIP trunk then save and reset.  I
can't think of a reason you would want to preserve the Redirecting Number
from Unity Connection so that should work as well.

On Tue, Aug 11, 2015 at 5:26 PM, Aaron Banks <amichaelbanks at hotmail.com>
wrote:

> I've built a simple auto attendant which the staff forwards to after
> hours: 1-staff directory; 0 for general mailbox.  0 works.  When I press 1
> (which is a voice enabled directory), say the person's name, I am
> redirected to their extension, but I never get to their mailbox.  The call
> is redirected back to the auto attendant.  This is a call initiated from
> outside of the organization.  If I call the auto attendant inside, same
> result.  If I have someone physically perform a transfer to the auto
> attendant, it works.  I get the extension and eventually hit the mailbox.
>
> I have gone as far as call forwarding someone's phone directly to
> voicemail, in additional to call forwarding to a cell phone, and if no
> physical transfer is performed, I hear the auto attendant again.  I've
> changed the CSS to be wide open with no success.
>
> If no call forwarding is done on the main phone (ie it rings until the AA
> answers) - same.  Without a person physically transferring to the AA, the
> caller will hear the AA over and over again.
>
> I've rebuilt both the call handler and the directory handler.  I have
> turned of the voice enabled option in favor of dial by name.  Same result.
>
> The version CUCM/CUC 10.5.2.12900-14.  I should mention that the
> connection between CUCM and CUC is a SIP trunk.  Could this be a bug (in my
> head)?
>
> TIA if you have an additional ideas.
>
>
> Aaron
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150811/7059042d/attachment.html>