It's a bit complicated but it seems like doable. I need to have a good look into it.<div><br></div><div>Thanks Lelio</div><div><br></div><div>Regards<br><br><div class="gmail_quote">On Thu, Aug 9, 2012 at 1:00 AM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:10pt;font-family:Verdana">you'll have to decide how to send calls back and forth from each cluster. your goal is probably to make it as simple for the users as possible. here's one option:<br>
<br><ul><li>on cluster A, create a route pattern 2XXX that sends calls to the new cluster over the inter cluster trunk</li><li>as you migrate phones from cluster A to cluster B, on cluster A, move their DN to a non-reachable partition</li>
<li>on cluster B, create a route pattern, *77.2XXX, that drops the *77 and sends the 2XXX over the intercluster trunk to the old cluster.</li><li>phones on cluster B that have not been migrated will have a CFUR destination of *772XXX</li>
</ul><p>you'll have to ensure CSS and partitions are set properly so calls can be made properly.</p><p><br></p><p>one thing to remember is to ensure that the CSS of the trunk does not have access to a partition that contains a route pattern that can send the call back to itself. this will help prevent loops.<br>
</p><div class="im"><span><br><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr><b>From: </b>"Ratko Dodevski" <<a href="mailto:rade239@gmail.com" target="_blank">rade239@gmail.com</a>><br>
</div><b>To: </b>"Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>><br><b>Cc: </b><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>, "Pavan" <<a href="mailto:pav.ccie@gmail.com" target="_blank">pav.ccie@gmail.com</a>><br>
<b>Sent: </b>Wednesday, 8 August, 2012 6:48:20 PM<div><div class="h5"><br><b>Subject: </b>Re: [cisco-voip] CMM with two CUCM clusters and MGCP<br><br>hmmm... CFUR might come in handy... so basically I just register CMM to the new CUCM cluster and then create 2XXX route pattern (this is the numbering plan) to the old CUCM cluster (using inter-cluster trunk) and each device to have CFUR to the same DN, right?<br>
<br><div class="gmail_quote">On Thu, Aug 9, 2012 at 12:40 AM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-size:10pt;font-family:Verdana">call forward unregistered. very very handy for stuff like this. <span><br><div><br><span></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br>
<span></span><br></div></span><br><hr><b>From: </b>"Ratko Dodevski" <<a href="mailto:rade239@gmail.com" target="_blank">rade239@gmail.com</a>><br><b>To: </b>"Pavan" <<a href="mailto:pav.ccie@gmail.com" target="_blank">pav.ccie@gmail.com</a>><br>
<b>Cc: </b><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Sent: </b>Wednesday, 8 August, 2012 6:38:49 PM<div><br><b>Subject: </b>Re: [cisco-voip] CMM with two CUCM clusters and MGCP<br>
<br></div><div><div>btw, what is
<span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">cfur </span> ???<br><br><div class="gmail_quote">On Thu, Aug 9, 2012 at 12:38 AM, Ratko Dodevski <span dir="ltr"><<a href="mailto:rade239@gmail.com" target="_blank">rade239@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for your replay <span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">Pavan. Yes this is one possible scenario but the migration of users is completely random so I cannot determine some pattern and to make those DNs to be routed to the new cluster. Plus, when the migration of the users is complete we need to shutdown old cucm so I then I would have to register the CMM modules on the new CUCM and this means some downtime and reconfigurations.</span><div>
<font color="#222222" face="arial, sans-serif"><br></font></div><div><font color="#222222" face="arial, sans-serif">Regards<br></font><div><div><br><div class="gmail_quote">On Thu, Aug 9, 2012 at 12:29 AM, Pavan <span dir="ltr"><<a href="mailto:pav.ccie@gmail.com" target="_blank">pav.ccie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would keep the CMM registered to the old ccm and route calls to it from the new ccm back to the old ccm.<br>
Inbound calls from cmm need to be routed to the new ccm from the old one based on some characteristic of your 150 user batch or by using cfur on old ucm.<br>
<br>
Curious if others have a better idea !<br>
<br>
-Pavan<br>
<div><div><br>
On Aug 8, 2012, at 17:17, Ratko Dodevski <<a href="mailto:rade239@gmail.com" target="_blank">rade239@gmail.com</a>> wrote:<br>
<br>
> Hi, I have a bit of a problem... I have a customer that migrates from CUCM 6.1 (two server cluster) to CUCM 8.6 (two VM cluster). They have two CMM line cards registered with the old CUCM cluster using MGCP. Now I have to do a migration of users/devices to the new cluster in several phases (150 users per phase) and they will be using the same numbering plan on both clusters. My problem is how to register the CMM modules on both clusters and how to manage the incoming calls when both clusters will have the same numbering plan...<br>
><br>
> Thanks and regards<br>
><br>
> --<br>
> Ratko<br>
</div></div>> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br>Ratko<br>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Ratko<br>
<br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Ratko<br>
</div></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Ratko<br>
</div>