[cisco-voip] Calling search spaces and paritions

[Matthew Loraditch]

Dane,
If 191-194 are your voice mail ports then yes their CSS needs to be able to access your internal DNs to be able to transfer calls to extensions from Unity.
-Matthew

From: Dane Newman [mailto:dane.newman at gmail.com]
Sent: Sunday, October 11, 2009 2:41 AM
To: Matthew Loraditch
Cc: cisco-voip
Subject: Re: [cisco-voip] Calling search spaces and paritions

I am also trying to update the css on the lines 191 192 193 194 to be something that can reach the internal numbers the AA needs to tranfer too and it's giving me the same error Update failed. DeviceFailureDN is set only for Directory Numbers.  I need to update the css of 191 192 193 194 to something that can reach the internal numbers the AA needs to tranfer too right?
On Sun, Oct 11, 2009 at 2:34 AM, Dane Newman <dane.newman at gmail.com<mailto:dane.newman at gmail.com>> wrote:
Matt,

Thank you so much for taking the time to answer some questions.

I have it setup with an fxo on a 2801 plar to 190 which is my hunt pilot for my voicemail.  This pilot includes ext 191 192 193 194.  I put extention 190 in a partition reachable from the css assigned to the gateway.  But when I try to assign 191 192 193 194 from any other partiton but the "no partition" I get the following error.

Update failed. DeviceFailureDN is set only for Directory Numbers

When I call into my fxo line it plar me to my AA fine.  It plays my recorded greeting and I then hit an extention of a phone of a phone number with voicemail and instead of ringing the phone it just puts me into there voicemail and if I hit an extention without voicemail it just says this number cannot be reached and tranfers be to the start of the AA greeting again.  I have also made sure in unity connection that * was not checked to be blocked in my restriction tables

Once again thanks so much for your time and assistance Matt.




On Sat, Oct 10, 2009 at 10:49 PM, Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>> wrote:
The partitions and such in Unity are fairly new and have to do with some new features, I believe, called logical partitioning . For a normal setup you shouldn't have to touch them. As to what people can dial from your AAs that is dealt with in the restriction tables in Unity. Normally you can only dial extensions associated to mailboxes and Call Handlers. Anything else is disallowed by default. You could also restrict what people could dial by the CSS assigned your voicemail ports in CUCM.
HTH
-Matthew

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Dane Newman
Sent: Saturday, October 10, 2009 11:42 AM
To: cisco-voip
Subject: Re: [cisco-voip] Calling search spaces and paritions

I set up calling search spaces and partitions in cucm but I also see there's options in unity connection to also do it.  I would have hoped unity connection and cucm could share a single cucm and unity connection calling search space and partition configuration?  are both the settings locally significant?  how do I set it up so When users call into my auto attendant from any number outside they are allowed to be tranfered to certain numbers and not others?



On Sat, Oct 10, 2009 at 11:33 AM, Dane Newman <dane.newman at gmail.com<mailto:dane.newman at gmail.com>> wrote:
Hello All,

I have a lab system that I am testing setting up calling search spaces and paritions with in CUCM 7 and unity connection 7.  I created a few partitions and put my route patterns and internal extentions into.  I also put the hunt pilot number for my unity connection auto attendant in.  Now when Someone calls in it's not tranfering them to auto attendant.  Is there something on the unity connection side I need to configure that I am missing?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091011/fb87e9c3/attachment.html>