[cisco-voip] Unity Connection 8 Auto Attendant exclusion

[Brian Palmer]

Thanks so much for the response Anthony.  Given that these guys have two IVR’s I would of expected an auto attendant within CVP or UCCX which would allow this to all work much easier with far less work.  I am considering all options but the less complex the better.   I truly dislike having to do PT/CSS trickery with a system that was setup entirely by another reseller as it requires a lot of time looking into the system.




Thank you,
Brian Palmer
bpalmer at ctipath.com<mailto:bpalmer at ctipath.com>
Deployment Engineer
CtiPath Communications
Ph. (919) 590-9297

From: Anthony Holloway [mailto:avholloway+cisco-voip at gmail.com]
Sent: Thursday, February 5, 2015 2:48 PM
To: Brian Palmer; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unity Connection 8 Auto Attendant exclusion

Within CUC there is only one way to specify a Transfer Rule for a subscriber, so I don't think you're going to get the differentiated services you want from within CUC so simply.

There are many options to consider, sure, to include prefix routing, PT/CSS tricks, etc.

And if you are considering all options, no matter how complex, then have a look at the CURRI API and the divert parameter:
The divert routing directive instructs Unified CM to redirect the call to another destination.

The divert directive has the following sub-elements:

•<destination> number | voicemail</destination>—This sub-element is mandatory for the divert directive. This sub-element specifies the destination to which the call is diverted. The destination can be a number routable in Unified CM, such as a directory number, a hunt pilot, or a route pattern. The destination can also be the string voicemail. If voicemail is specified as the destination, Unified CM will redirect the call to the voice mail box of the original called party. The call will be released if the original called party does not have a voicemail box.

•<reason>chaperone</reason>—this sub-element specifies the reason for the call diversion. Chaperone indicates the destination is a chaperone line or a hunt list of chaperone lines. When this reason is included, the destination device will be enabled for chaperone features.For more information on chaperone feature, refer the Cisco Unified Communications Manager Features and Services Guide, release 8.0(1).

•<modify callingNumber=number calledNumber=number callingName=name calledName=name/> —This sub-element specifies that the calling/called numbers and names are modified with the numbers and names provided. The web service overwrites the calling and called party transformation that is configured for the trigger point. Unified CM changes the calling/called numbers and names to the numbers and names that are provided in the directive. If the number is not included in the directive, the configuration for the route pattern or trigger point applies.

•<resetCallHistory> resetLastHop | resetAllHops </resetCallHistory>—this sub-element specifies the method to reset call history. The following options are available:
oresetLastHop: erase the last called party number from the call history.
oresetAllHops: erase all previous called party numbers from the call history.

Source: https://developer.cisco.com/site/curri/develop-and-test/documentation/latest-version/index.gsp

Here's a cool use case from that same developer site, which you may like:

Delegate(s) – Send calls to my Exchange delegate when my Calendar shows "Out-Of-Office"

So, in a way, if you solve this one problem with CURRI, then you get CURRI introduced in to the environment, where it can then be used for all kinds of cool advanced routing features that you previously didn't have before.

On Thu Feb 05 2015 at 12:50:09 PM Brian Palmer <bpalmer at ctipath.com<mailto:bpalmer at ctipath.com>> wrote:
I have a CEO that wants anybody using the directory lookup from unity connection(last name, first name) to find him to be directed to his secretary while also allowing anybody that knows his direct extension to still be able to get him directly.

This is for a UCCX 8 environment that also has CVP standalone.  He is on extension mobility.  This environment is LDAP synchronized and part of me is just thinking we can change the telephone number in the AD as I think that is the information that is being looked up to find him via the LDAP enabled CUCM.  That way if somebody looks him up they get the number for the secretary and anybody he has given the number to can still get direct access.  Those are my thoughts on doing this does anybody else have any good suggestions on how to get this directory lookup to provide the secretarys number instead of the CEO?





Thank you,
Brian Palmer
bpalmer at ctipath.com<mailto:bpalmer at ctipath.com>
Deployment Engineer
CtiPath Communications
Ph. (919) 590-9297

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20150205/b01866c9/attachment.html>