[cisco-voip] Multiple CM Clusters - 1 Unity system

[Pat Hayes]

With Unity 4.2(1) and later you can create multiple skinny
integrations (rather than a single skinny integration with multiple
clusters) and assign users to a specific one. This will limit MWI
dialouts to the appropriate cluster.

You can also come at this from the CUCM side if you have a relatively
consistent dial plan across clusters. Inter-cluster trunks will
support MWI as well as original called party info. If you're going to
have an ICT anyways, you might not even need to go to the trouble of
the two separate integrations.

On Fri, Mar 26, 2010 at 11:17 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> The only issue is the TSP. I believe you can only have one TSP loaded at a
> time. The latest TSP will work better with v7 and should be supported with
> v4.
>
> Unless things have changed, your biggest issue with an integration like this
> is MWI (and MWI refresh). AFAIK, Unity can not assign an integration to a
> subscriber (like Connection can), so MWIs go out all ports. If you only have
> a few ports on the v4 system, and MWI refresh will take longer.
>
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it.
>                               - LFJ (with apologies to Mr. Popeil)
>
>
> ----- Original Message -----
> From: "Micah Bennett" <mbennett at als-xtn.com>
> To: "Matt Slaga (US)" <Matt.Slaga at us.didata.com>, "cisco-voip list"
> <cisco-voip at puck.nether.net>
> Sent: Friday, March 26, 2010 11:10:34 AM GMT -05:00 US/Canada Eastern
> Subject: Re: [cisco-voip] Multiple CM Clusters - 1 Unity system
>
> Does the unity server care what versions of call manager it talks to?
>
>
>
> The main cluster with 99% of the users is 7.x.
>
>
>
> The second cluster is only staying in service to server our Call Centers
> until they are migrated to Avaya.  I only have a few users staying on that
> system that have voicemail.  That CM cluster is 4.2(3).
>
>
>
> A few ports for the smaller system should be plenty.
>
>
>
> Micah Bennett
>
> ________________________________
>
> From: Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
> Sent: Friday, March 26, 2010 9:55 AM
> To: Micah Bennett; cisco-voip list
> Subject: RE: Multiple CM Clusters - 1 Unity system
>
>
>
> It is absolutely possible, however you have to carve out the Unity ports
> between the systems, as they cannot be shared.  I.e, if you have 32 ports
> and 4 systems, you could do 8 ports per system.  You also have to configure
> each UCM cluster in the Unity TSP .
>
>
>
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Micah Bennett
> Sent: Friday, March 26, 2010 10:51 AM
> To: cisco-voip list
> Subject: [cisco-voip] Multiple CM Clusters - 1 Unity system
>
>
>
> Is it possible for multiple CM Clusters (different Versions) to point to one
> common Unity Server.
>
>
>
> Micah Bennett
> Telecommunications Admin
> Active Outdoors
>
>
>
> ________________________________
>
> Disclaimer: This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the designated
> addressee(s) named above only. If you are not the intended addressee, you
> are hereby notified that you have received this communication in error and
> that any use or reproduction of this email or its contents is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify us immediately by replying to this message and deleting
> it from your computer. Thank you.
>
> _______________________________________________ cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>