[cisco-voip] Unity 5.x with Multiple Call Manager Clusters

[steve.siltman at assurant.com]

This makes perfect sense.  Reading the documentation it sounded like this 
but I wasn't convinced.  I was too afraid to try this in production.  I'm 
going to do change this.. think its wise to change this on 5.x before 
jumping to Unity Connections or do it afterwards?


Steve Siltman
Assurant Corporate Technology
Senior Network Engineer - Cisco CCVP
Work: 651-361-4752
Cell: 651-336-5563
steve.siltman at assurant.com



From:   Pat Hayes <pat-cv at wcyv.com>
To:     steve.siltman at assurant.com
Cc:     lelio at uoguelph.ca, "cisco-voip at puck.nether.net" 
<cisco-voip at puck.nether.net>
Date:   07/12/2010 07:41 PM
Subject:        Re: [cisco-voip] Unity 5.x with Multiple Call Manager 
Clusters
Sent by:        pat at wcyv.com



It sounds like you have multiple callmanager clusters defined under
the same integration. When there are multiple clusters defined for the
same integration, Unity doesn't know which one your user is on so it
dials the MWIs and such out on each integration until one is
successful.

Starting with Unity 4.2(1), Unity supports multiple skinny
integrations. If you create a separate integration for each of your
callmanager clusters (rather than multiple clusters under the same),
then you can assign users to a specific cluster and their MWIs and
notifications will only be dialed out on the appropriate
integration/cluster.

On Mon, Jul 12, 2010 at 4:20 PM,  <steve.siltman at assurant.com> wrote:
> Wondering if this is true for message notification too.  An outbound 
dial to
> notify the user that a message exists could use any cluster?  I don't 
think
> I like where this is going.
>
>
> Steve
>
>
>
> From:        lelio at uoguelph.ca
> To:        "steve.siltman at assurant.com" <steve.siltman at assurant.com>
> Cc:        "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
> Date:        07/12/2010 03:15 PM
> Subject:        Re: [cisco-voip] Unity 5.x with Multiple Call Manager
> Clusters
> ________________________________
>
>
> I belive this is working by design, or at least with Unity 4.x it is.
> There's no way to tell Unity on which cluster the phone is registered. 
With
> Connection v7, you select the phone system the subscriber belongs to in 
the
> first config screen. Not sure if they added this option in Unity and/or 
in
> what version they did.
>
> ?
> Don't look at me, my iPod maid that spilling mistake.
>
> On 2010-07-12, at 4:08 PM, steve.siltman at assurant.com wrote:
>
> I've got a cheesy question.
>
> While looking at the ports I see that when the MWI is set or cancelled, 
it
> is sent to each cluster rather than the cluster where the phone resides.
>  It's the same everytime, I see MWI set to extension 28950 on port 120 
and
> right when its finished it sends the same to Port 144.  I have 3 
different
> clusters connected to this Unity pair.  Did I miss a routing 
configuration
> screen somewhere?
>
> It's not causing an issue but it bothers me.  Wasted port usage.
>
> Thanks,
>
> Steve This e-mail message and all attachments transmitted with it may
> contain legally privileged and/or confidential information intended 
solely
> for the use of the addressee(s). If the reader of this message is not 
the
> intended recipient, you are hereby notified that any reading, 
dissemination,
> distribution, copying, forwarding or other use of this message or its
> attachments is strictly prohibited. If you have received this message in
> error, please notify the sender immediately and delete this message and 
all
> copies and backups thereof. Thank you.
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> This e-mail message and all attachments transmitted with it may contain
> legally privileged and/or confidential information intended solely for 
the
> use of the addressee(s). If the reader of this message is not the 
intended
> recipient, you are hereby notified that any reading, dissemination,
> distribution, copying, forwarding or other use of this message or its
> attachments is strictly prohibited. If you have received this message in
> error, please notify the sender immediately and delete this message and 
all
> copies and backups thereof. Thank you.
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>



This e-mail message and all attachments transmitted with it may
contain legally privileged and/or confidential information intended
solely for the use of the addressee(s). If the reader of this
message is not the intended recipient, you are hereby notified that
any reading, dissemination, distribution, copying, forwarding or
other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please
notify the sender immediately and delete this message and all
copies and backups thereof. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100712/abd85cb6/attachment.html>