<font size=2 face="sans-serif">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?</font>
<br><font size=2 face="sans-serif"><br>
<br>
Steve Siltman<br>
Assurant Corporate Technology<br>
Senior Network Engineer - Cisco CCVP<br>
Work: 651-361-4752<br>
Cell: 651-336-5563<br>
steve.siltman@assurant.com</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Pat Hayes <pat-cv@wcyv.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">steve.siltman@assurant.com</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">lelio@uoguelph.ca,
"cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">07/12/2010 07:41 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [cisco-voip]
Unity 5.x with Multiple Call Manager Clusters</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">pat@wcyv.com</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>It sounds like you have multiple callmanager clusters
defined under<br>
the same integration. When there are multiple clusters defined for the<br>
same integration, Unity doesn't know which one your user is on so it<br>
dials the MWIs and such out on each integration until one is<br>
successful.<br>
<br>
Starting with Unity 4.2(1), Unity supports multiple skinny<br>
integrations. If you create a separate integration for each of your<br>
callmanager clusters (rather than multiple clusters under the same),<br>
then you can assign users to a specific cluster and their MWIs and<br>
notifications will only be dialed out on the appropriate<br>
integration/cluster.<br>
<br>
On Mon, Jul 12, 2010 at 4:20 PM, <steve.siltman@assurant.com>
wrote:<br>
> Wondering if this is true for message notification too. An outbound
dial to<br>
> notify the user that a message exists could use any cluster? I
don't think<br>
> I like where this is going.<br>
><br>
><br>
> Steve<br>
><br>
><br>
><br>
> From: lelio@uoguelph.ca<br>
> To: "steve.siltman@assurant.com"
<steve.siltman@assurant.com><br>
> Cc: "cisco-voip@puck.nether.net"
<cisco-voip@puck.nether.net><br>
> Date: 07/12/2010 03:15 PM<br>
> Subject: Re: [cisco-voip] Unity 5.x with
Multiple Call Manager<br>
> Clusters<br>
> ________________________________<br>
><br>
><br>
> I belive this is working by design, or at least with Unity 4.x it
is.<br>
> There's no way to tell Unity on which cluster the phone is registered.
With<br>
> Connection v7, you select the phone system the subscriber belongs
to in the<br>
> first config screen. Not sure if they added this option in Unity and/or
in<br>
> what version they did.<br>
><br>
> …<br>
> Don't look at me, my iPod maid that spilling mistake.<br>
><br>
> On 2010-07-12, at 4:08 PM, steve.siltman@assurant.com wrote:<br>
><br>
> I've got a cheesy question.<br>
><br>
> While looking at the ports I see that when the MWI is set or cancelled,
it<br>
> is sent to each cluster rather than the cluster where the phone resides.<br>
> It's the same everytime, I see MWI set to extension 28950 on
port 120 and<br>
> right when its finished it sends the same to Port 144. I have
3 different<br>
> clusters connected to this Unity pair. Did I miss a routing
configuration<br>
> screen somewhere?<br>
><br>
> It's not causing an issue but it bothers me. Wasted port usage.<br>
><br>
> Thanks,<br>
><br>
> Steve This e-mail message and all attachments transmitted with it
may<br>
> contain legally privileged and/or confidential information intended
solely<br>
> for the use of the addressee(s). If the reader of this message is
not the<br>
> intended recipient, you are hereby notified that any reading, dissemination,<br>
> distribution, copying, forwarding or other use of this message or
its<br>
> attachments is strictly prohibited. If you have received this message
in<br>
> error, please notify the sender immediately and delete this message
and all<br>
> copies and backups thereof. Thank you.<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> </font></tt><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"><tt><font size=2>https://puck.nether.net/mailman/listinfo/cisco-voip</font></tt></a><tt><font size=2><br>
> This e-mail message and all attachments transmitted with it may contain<br>
> legally privileged and/or confidential information intended solely
for the<br>
> use of the addressee(s). If the reader of this message is not the
intended<br>
> recipient, you are hereby notified that any reading, dissemination,<br>
> distribution, copying, forwarding or other use of this message or
its<br>
> attachments is strictly prohibited. If you have received this message
in<br>
> error, please notify the sender immediately and delete this message
and all<br>
> copies and backups thereof. Thank you.<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> </font></tt><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"><tt><font size=2>https://puck.nether.net/mailman/listinfo/cisco-voip</font></tt></a><tt><font size=2><br>
><br>
><br>
</font></tt>
<br>
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.