[cisco-voip] Unity Connection Partitions and SS

Lelio Fulgenzi lelio at uoguelph.ca
Tue Sep 1 09:31:45 EDT 2009


wow. that's really too bad. not scalable especially with a finite number of ports. What if I had an office building with 200 tennants? 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Chris Lewis" <Chris.Lewis at magnetar.com> 
To: "Michael Back" <Michael.Back at nisd.net> 
Cc: cisco-voip at puck.nether.net 
Sent: Tuesday, September 1, 2009 8:18:01 AM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] Unity Connection Partitions and SS 

All, 

What I ended up doing was to have a separate Phone System for each of my 
sites even though they are within the same UCM Cluster. 

The drawback with this is that I have had to split up my ports to 
balance them out across the Phone Systems. 

I have the same number to access Unity from all sites but as users here 
are aware of the inter-office dialling digits this removes any issues 
of attempting to log on to the wrong "System" 

So far it seems fine but I do not like the fact I have had to split the 
ports up as I may have to juggle with it in the future depending on 
specific usage at various office. This is a solution which TAC and I 
came up with after many conversations. 

Thanks for the help 

Chris 

-----Original Message----- 
From: Michael Back [mailto:Michael.Back at nisd.net] 
Sent: 19 August 2009 17:35 
To: Lewis, Chris 
Cc: cisco-voip at puck.nether.net 
Subject: RE: [cisco-voip] Unity Connection Partitions and SS 

When I looked into partitions and ss, I knew we would have problems if 
someone from site A was at site B for some reason and wanted to access 
their voice mail. I am sure Unity would need some special routing for 
that to work properly or maybe a dedicated extension for each site to 
get messages remotely. So essentially, we could have cleaned up UCM but 
we would have added complications to Connection. I am curious to see 
what you come up with though... 

MB 

>>> "Lewis, Chris" <Chris.Lewis at magnetar.com> 8/19/2009 10:49 AM >>> 
Ah OK. 

I have that for Unity currently but want to remove the 3 digit codes 
we 
use and the masks on the VM Profiles. 

Thanks for the into though. I am pushing TAC for more so will let you 
guys know how it goes. 

Thanks 

Chris 

-----Original Message----- 
From: Michael Back [mailto:Michael.Back at nisd.net] 
Sent: 19 August 2009 16:46 
To: Lewis, Chris; Pat Hayes 
Cc: cisco-voip at puck.nether.net 
Subject: RE: [cisco-voip] Unity Connection Partitions and SS 

Our sites all have a three digit code, for example 001, and we 
duplicate 
all 31XX extensions. For site 001 I create a voice mail profile that 
will be used only by phones with in the 31XX range. The voice mail 
box 
mask for the voice mail profile is set to add the three digit site 
code. 
So the mask for my 001 site would be 001XXXX. In Connection, all my 
overlapping DNs are seven digits. So at site 001, extension 3101 
would 
be extension 0013101 in Unity. Everything is in the same partition on 
each cluster. We have been doing it this way far awhile and have had 
no 
problems. For 4 sites, this should be fairly easy to set up. You can 
probably use bulk edit to prepend any site code you like in Unity, and 
use BAT to change the extension voice mail profiles in UCM. 

Hope this helps, 
>>> "Lewis, Chris" <Chris.Lewis at magnetar.com> 8/19/2009 8:55 AM >>> 
Would you mind explaining how you did this please? 

Thanks 

Chris 

-----Original Message----- 
From: Michael Back [mailto:Michael.Back at nisd.net] 
Sent: 19 August 2009 14:53 
To: Lewis, Chris; Pat Hayes 
Cc: cisco-voip at puck.nether.net 
Subject: Re: [cisco-voip] Unity Connection Partitions and SS 

If you are trying to set up a true multi-tenant system then partitions 
and ss will probably be necessary. If you are just trying to work out 
a 
solution for the overlapping DNs then you don't need to worry about 
the 
partitions and ss. We have more than 100 sites with overlapping DNs 
and 
do not use partitions or ss. I considered it when we started 
implementing Connection 7, but it seemed more trouble than it was 
worth. 

MB 

Mike Back 
VoIP Systems Administrator 
Northside ISD 
(210) 397-7737 
michael.back at nisd.net 

>>> "Lewis, Chris" <Chris.Lewis at magnetar.com> 8/19/2009 4:37 AM >>> 
Hi Pat, 

Sorry for the delay, I have been away. 

I agree with what you are saying and this does work for different 
Phone 
Systems. The issue with when using the Voice Ports. I have set up 
forwarding rules on for the voice ports but when you set it up with 
more 
that one Port for the Routing Rule the call does not get forwarded to 
the Specific Mailbox. 

Chris 

-----Original Message----- 
From: pat at wcyv.com [mailto:pat at wcyv.com] On Behalf Of Pat Hayes 
Sent: 07 August 2009 16:29 
To: Lewis, Chris 
Cc: lelio at uoguelph.ca; cisco-voip at puck.nether.net 
Subject: Re: [cisco-voip] Unity Connection Partitions and SS 

For a true multi-tenant install like this, you need to route by port 
or phonesystem. For example, create a separate phone system (and 
associated ports) for each site, point your pilots to line groups 
containing just those ports, and setup forwarding routing rules with 
the appropriate SS for each site. 

On Fri, Aug 7, 2009 at 10:12 AM, Lewis, 
Chris<Chris.Lewis at magnetar.com> 
wrote: 
> It shows the dialled number rather than the pilot number. 
> 
> Tac are stumped btw. :-) 
> 
> ________________________________ 
> From: Lelio Fulgenzi 
> To: Lewis, Chris 
> Cc: cisco-voip at puck.nether.net 
> Sent: Fri Aug 07 09:02:03 2009 
> Subject: Re: [cisco-voip] Unity Connection Partitions and SS 
> What does the remote port status monitor say? It should tell you the 
dialed 
> pilot number. I haven't tried it my self (the forwarding rule 
config) 
but it 
> seems like that would be the way. 
> 
> It might be TAC time. 
> 
> 
> --- 
> Lelio Fulgenzi, B.A. 
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 
2W1 
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
> 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
> "Bad grammar makes me [sic]" - Tshirt 
> 
> 
> ----- Original Message ----- 
> From: "Chris Lewis" <Chris.Lewis at magnetar.com> 
> To: lelio at uoguelph.ca 
> Cc: cisco-voip at puck.nether.net 
> Sent: Friday, August 7, 2009 9:56:01 AM GMT -05:00 US/Canada Eastern 
> Subject: Re: [cisco-voip] Unity Connection Partitions and SS 
> 
> Tried it. 
> 
> That works for direct routing - ie sign in - but for forward routing 
it 
> doesn't work. 
> 
> ________________________________ 
> From: Lelio Fulgenzi 
> To: Lewis, Chris 
> Cc: cisco-voip at puck.nether.net 
> Sent: Fri Aug 07 08:49:14 2009 
> Subject: Re: [cisco-voip] Unity Connection Partitions and SS 
> 
> your forward routing rules allow you to set a calling search space 
based on 
> the pilot you have forwarded to. it's the dialed number. not the 
best 
> terminology, it should say "forwarded target" or something like 
that. 
> 
> try that out if you haven't already, or let us know if you have. 
> 
> 
> --- 
> Lelio Fulgenzi, B.A. 
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 
2W1 
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
> 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
> "Bad grammar makes me [sic]" - Tshirt 
> 
> 
> ----- Original Message ----- 
> From: "Chris Lewis" <Chris.Lewis at magnetar.com> 
> To: cisco-voip at puck.nether.net 
> Sent: Friday, August 7, 2009 3:11:53 AM GMT -05:00 US/Canada Eastern 
> Subject: [cisco-voip] Unity Connection Partitions and SS 
> 
> Has anyone set up UC utilising Partitions and SS? 
> 
> 
> 
> I am trying to do the following: 
> 
> 
> 
> 4 separate sites with overlapping DNs. 
> 
> 
> 
> I have setup UC with separate Partitions and SS. Added DNs to their 
> respective Partitions. Set up Direct Routing Rules to allow the DN 
to dial 
> UC - I have separate Pilot Numbers as per Cisco docs. 
> 
> 
> 
> The issue is when you try to dial the DN and have it forwarded to 
vmail. 
> These use forward routing rules and due to the CallerID not being 
recognised 
> as Vmail ID (IE Pilot number) they fail. 
> 
> 
> 
> Has anyone successfully managed to get this sort of scenario 
working? 
> 
> 
> 
> Thanks 
> 
> 
> 
> Chris 
> 
> The information contained in this message and its attachments 
> is intended only for the private and confidential use of the 
> intended recipient(s). If you are not the intended recipient 
> (or have received this e-mail in error) please notify the 
> sender immediately and destroy this e-mail. Any unauthorized 
> copying, disclosure or distribution of the material in this e- 
> mail is strictly prohibited. 
> 
> _______________________________________________ cisco-voip mailing 
list 
> cisco-voip at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-voip 
> 
> The information contained in this message and its attachments 
> is intended only for the private and confidential use of the 
> intended recipient(s). If you are not the intended recipient 
> (or have received this e-mail in error) please notify the 
> sender immediately and destroy this e-mail. Any unauthorized 
> copying, disclosure or distribution of the material in this e- 
> mail is strictly prohibited. 
> 
> The information contained in this message and its attachments 
> is intended only for the private and confidential use of the 
> intended recipient(s). If you are not the intended recipient 
> (or have received this e-mail in error) please notify the 
> sender immediately and destroy this e-mail. Any unauthorized 
> copying, disclosure or distribution of the material in this e- 
> mail is strictly prohibited. 
> 
> _______________________________________________ 
> cisco-voip mailing list 
> cisco-voip at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-voip 
> 
> 

The information contained in this message and its attachments 
is intended only for the private and confidential use of the 
intended recipient(s). If you are not the intended recipient 
(or have received this e-mail in error) please notify the 
sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e- 
mail is strictly prohibited. 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 


The information contained in this message and its attachments 
is intended only for the private and confidential use of the 
intended recipient(s). If you are not the intended recipient 
(or have received this e-mail in error) please notify the 
sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e- 
mail is strictly prohibited. 


The information contained in this message and its attachments 
is intended only for the private and confidential use of the 
intended recipient(s). If you are not the intended recipient 
(or have received this e-mail in error) please notify the 
sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e- 
mail is strictly prohibited. 


The information contained in this message and its attachments 
is intended only for the private and confidential use of the 
intended recipient(s). If you are not the intended recipient 
(or have received this e-mail in error) please notify the 
sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e- 
mail is strictly prohibited. 
_______________________________________________ 
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/20090901/65008ce9/attachment.html>


More information about the cisco-voip mailing list