[cisco-voip] CMM with two CUCM clusters and MGCP

Wed Aug 8 20:04:46 EDT 2012

I've done some tests in my lab and I've managed to get CSS and partitions
right so if device is note registered on new CM it forwards to the old CM.
Maybe I can use this on the other side to, if it's not registered on the
old CM forward to new CM... This way users first search for that DN in the
cluster where they are registered, and if the device they look for is not
registered, call is forwarded to the other CM. Sounds to me like it can
work.

Regards
Ratko

On Thu, Aug 9, 2012 at 1:15 AM, Ratko Dodevski <rade239 at gmail.com> wrote:

> It's a bit complicated but it seems like doable. I need to have a good
> look into it.
>
> Thanks Lelio
>
> Regards
>
>
> On Thu, Aug 9, 2012 at 1:00 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
>> 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:
>>
>>
>>    - on cluster A, create a route pattern 2XXX that sends calls to the
>>    new cluster over the inter cluster trunk
>>    - as you migrate phones from cluster A to cluster B, on cluster A,
>>    move their DN to a non-reachable partition
>>    - 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.
>>    - phones on cluster B that have not been migrated will have a CFUR
>>    destination of *772XXX
>>
>> you'll have to ensure CSS and partitions are set properly so calls can be
>> made properly.
>>
>>
>> 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.
>>
>> ---
>> Lelio Fulgenzi, B.A.
>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>> (519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> Cooking with unix is easy. You just sed it and forget it.
>>                               - LFJ (with apologies to Mr. Popeil)
>>
>>
>> ------------------------------
>> *From: *"Ratko Dodevski" <rade239 at gmail.com>
>> *To: *"Lelio Fulgenzi" <lelio at uoguelph.ca>
>> *Cc: *cisco-voip at puck.nether.net, "Pavan" <pav.ccie at gmail.com>
>> *Sent: *Wednesday, 8 August, 2012 6:48:20 PM
>>
>> *Subject: *Re: [cisco-voip] CMM with two CUCM clusters and MGCP
>>
>> 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?
>>
>> On Thu, Aug 9, 2012 at 12:40 AM, Lelio Fulgenzi <lelio at uoguelph.ca>wrote:
>>
>>> call forward unregistered. very very handy for stuff like this.
>>>
>>> ---
>>> Lelio Fulgenzi, B.A.
>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>>> (519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> Cooking with unix is easy. You just sed it and forget it.
>>>                               - LFJ (with apologies to Mr. Popeil)
>>>
>>>
>>> ------------------------------
>>> *From: *"Ratko Dodevski" <rade239 at gmail.com>
>>> *To: *"Pavan" <pav.ccie at gmail.com>
>>> *Cc: *cisco-voip at puck.nether.net
>>> *Sent: *Wednesday, 8 August, 2012 6:38:49 PM
>>>
>>> *Subject: *Re: [cisco-voip] CMM with two CUCM clusters and MGCP
>>>
>>> btw, what is  cfur  ???
>>>
>>> On Thu, Aug 9, 2012 at 12:38 AM, Ratko Dodevski <rade239 at gmail.com>wrote:
>>>
>>>> Thanks for your replay 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.
>>>>
>>>> Regards
>>>>
>>>> On Thu, Aug 9, 2012 at 12:29 AM, Pavan <pav.ccie at gmail.com> wrote:
>>>>
>>>>> I would keep the CMM registered to the old ccm and route calls to it
>>>>> from the new ccm back to the old ccm.
>>>>> 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.
>>>>>
>>>>> Curious if others have a better idea !
>>>>>
>>>>> -Pavan
>>>>>
>>>>> On Aug 8, 2012, at 17:17, Ratko Dodevski <rade239 at gmail.com> wrote:
>>>>>
>>>>> > 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...
>>>>> >
>>>>> > Thanks and regards
>>>>> >
>>>>> > --
>>>>> > Ratko
>>>>> > _______________________________________________
>>>>> > cisco-voip mailing list
>>>>> > cisco-voip at puck.nether.net
>>>>> > https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ratko
>>>>
>>>
>>>
>>>
>>> --
>>> Ratko
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
>>
>>
>> --
>> Ratko
>>
>
>
>
> --
> Ratko
>

-- 
Ratko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120809/a0e1b08c/attachment.html>