[cisco-voip] 1 Unity Connection with 2 CM clusters

[Ted Nugent]

yep and as long as you have the users assigned to that phone system when you
migrate them over to CUCM7 and MWI is working on outbound dialing for those
ports then you should be fine. In case its not clear, you need to point the
users in CUC to the CUCM7 integration or they will still try and push MWi
and outdialing out the 4.x cluster. obviously you still need to have
licensed ports to consider as well but i don't think CUC will allow you to
make more ports then licensed but i have not tested that in CUC... only on
unity.

On Sun, May 30, 2010 at 11:58 PM, <lelio at uoguelph.ca> wrote:

> Basically, yes.  The MWIs should go out based on the phone system the MWI
> config is set to use.
>
> …
> Don't look at me, my iPod made that spilling mistake.
>
> On 2010-05-30, at 10:26 PM, Sandy Lee <Sandy.Lee at dti.ulaval.ca> wrote:
>
>  Ok, just to make sure I understand it correctly. When you say a dual
> integration, you mean create a new phone system in CUC for the CUCM 7
> cluster and that’s it ? Because that’s what I did first, but MWI stopped
> working for my CUCM 4.1 cluster users.
>
>
>
> What I forgot to say, is that we already have a dual integration for our
> legacy pbx, which is achieved with TIMGs, but that shouldn’t affect anything
> right ? So CUC will now have 3 phone systems to manage.
>
>
>
> Thanks and regards.
>
> Sandy
>
> *From:* Ted Nugent [mailto:tednugent73 at gmail.com]
> *Sent:* Friday, May 28, 2010 8:15 PM
> *To:* Sandy Lee
> *Cc:* Ryan Ratliff; <cisco-voip at puck.nether.net>cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] 1 Unity Connection with 2 CM clusters
>
>
>
> I would seriously consider just doing the dual integration and make sure
> your bulk assigning the users to the new system in CUC as you migrate them
> over to the new cluster. I just did this for a client about 3 month ago and
> it want flawlessly.
>
>
>
> My $0.02
>
> Ted
>
> On Fri, May 28, 2010 at 3:53 PM, Sandy Lee < <Sandy.Lee at dti.ulaval.ca>
> Sandy.Lee at dti.ulaval.ca> wrote:
>
> I have an ICT between the 2 clusters, but it’s not a QSIG one. I will try
> it with this protocol on.
>
>
>
> Thanks.
>
>
>
> Sandy.
>
>
>
> *From:* Ryan Ratliff [mailto: <rratliff at cisco.com>rratliff at cisco.com]
> *Sent:* Friday, May 28, 2010 11:12 AM
> *To:* Sandy Lee
> *Cc:* <cisco-voip at puck.nether.net>cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] 1 Unity Connection with 2 CM clusters
>
>
>
> You can either use a dual integration (if UC can do this) or set up a qsig
> tunneled ICT between the two CUCM clusters.  Have a route pattern pointing
> to that trunk for the numbers that exist on the other cluster and MWIs will
> be passed between.
>
>
>
> -Ryan
>
>
>
> On May 28, 2010, at 9:37 AM, Sandy Lee wrote:
>
>
>
> Hi,
>
>
>
> We’re migrating from CUCM 4.1(3) to UCM 7.1(3) with a new server migration
> approach. We have a Unity Connection 7.1(3) that is already SCCP integrated
> with the CUCM 4.1(3).
>
>
>
> My question is how do I deal with my 4.1(3) cluster for the MWIs to
> continue working? In the lab, I configured the SIP integration for the UCM
> 7.1(3) and it worked just fine, but MWIs stopped working for the 4.1(3)
> guys.
>
>
>
> In the doc, it says that I need to do a translation pattern, but there’s no
> example. Did anyone of you went through this and could give me an example?
>
>
>
> Any help would be appreciated.
>
>
>
> Thanks and regards.
>
>
>
> Sandy.
>
> _______________________________________________
> cisco-voip mailing list
>  <cisco-voip at puck.nether.net>cisco-voip at puck.nether.net
>  <https://puck.nether.net/mailman/listinfo/cisco-voip>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
>  <cisco-voip at puck.nether.net>cisco-voip at puck.nether.net
>  <https://puck.nether.net/mailman/listinfo/cisco-voip>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100531/469021e3/attachment.html>