Mailing List Archive: Cisco: VOIP

CMM with two CUCM clusters and MGCP

Index | Next | Previous | View Threaded

rade239 at gmail

Aug 8, 2012, 3:17 PM

Post #1 of 13 (911 views)
Permalink

CMM with two CUCM clusters and MGCP

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

pav.ccie at gmail

Aug 8, 2012, 3:29 PM

Post #2 of 13 (899 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

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> 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
> https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

rade239 at gmail

Aug 8, 2012, 3:38 PM

Post #3 of 13 (899 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

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> 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> 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
> > https://puck.nether.net/mailman/listinfo/cisco-voip
>

--
Ratko

lelio at uoguelph

Aug 8, 2012, 3:38 PM

Post #4 of 13 (901 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

I just checked, and 6.1 does not have CFUR. If it did, I would have went with your suggestion. Since it doesn't, I would suggest preparing the new cluster to ensure that: (a) all phones that have not yet been migrated have CFUR set to route them to the old cluster, and (b) any non-phone DN that has not yet been migrated can be reached via route patterns. You can use an intercluster trunk for this. If you have enough spare PRIs, register some to the new cluster. Then during a maintenance window you cant temporarily move a PRI over to the new system and test.

I'm not entirely sure how CMMs are configured and whether the entire blade is looked at as an IOS device or the modules. You may or may not be able to have separate PRI port registered to different clusters.

Once testing is done, you can simply move your PRIs over. Your migration process will have to remove the CFUR on each phone that is moved over.

Of course, there are many ways to complete this migration. Take what others say and pick the best that suits your environment. Feel free to post a migration summary, people may have additional comments.

Lelio

---
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)

----- Original Message -----
From: "Pavan" <pav.ccie [at] gmail>
To: "Ratko Dodevski" <rade239 [at] gmail>
Cc: cisco-voip [at] puck
Sent: Wednesday, 8 August, 2012 6:29:03 PM
Subject: Re: [cisco-voip] CMM with two CUCM clusters and MGCP

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> 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
> https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

rade239 at gmail

Aug 8, 2012, 3:38 PM

Post #5 of 13 (899 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

btw, what is cfur ???

On Thu, Aug 9, 2012 at 12:38 AM, Ratko Dodevski <rade239 [at] gmail> 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> 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> 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
>> > https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
>
>
> --
> Ratko
>

--
Ratko

lelio at uoguelph

Aug 8, 2012, 3:40 PM

Post #6 of 13 (900 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

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)

----- Original Message -----
From: "Ratko Dodevski" <rade239 [at] gmail>
To: "Pavan" <pav.ccie [at] gmail>
Cc: cisco-voip [at] puck
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 > 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 > 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 > 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
> https://puck.nether.net/mailman/listinfo/cisco-voip

--
Ratko

--
Ratko

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

rade239 at gmail

Aug 8, 2012, 3:48 PM

Post #7 of 13 (903 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

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> 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>
> *To: *"Pavan" <pav.ccie [at] gmail>
> *Cc: *cisco-voip [at] puck
> *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> 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> 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> 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
>>> > https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
>>
>>
>> --
>> Ratko
>>
>
>
>
> --
> Ratko
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

--
Ratko

lelio at uoguelph

Aug 8, 2012, 4:00 PM

Post #8 of 13 (902 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

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)

----- Original Message -----
From: "Ratko Dodevski" <rade239 [at] gmail>
To: "Lelio Fulgenzi" <lelio [at] uoguelph>
Cc: cisco-voip [at] puck, "Pavan" <pav.ccie [at] gmail>
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 > 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 >
To: "Pavan" < pav.ccie [at] gmail >
Cc: cisco-voip [at] puck
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 > 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 > 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 > 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
> https://puck.nether.net/mailman/listinfo/cisco-voip

--
Ratko

--
Ratko

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

--
Ratko

rade239 at gmail

Aug 8, 2012, 4:15 PM

Post #9 of 13 (910 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

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> 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>
> *To: *"Lelio Fulgenzi" <lelio [at] uoguelph>
> *Cc: *cisco-voip [at] puck, "Pavan" <pav.ccie [at] gmail>
> *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> 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>
>> *To: *"Pavan" <pav.ccie [at] gmail>
>> *Cc: *cisco-voip [at] puck
>> *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>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> 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> 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
>>>> > https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>
>>>
>>>
>>>
>>> --
>>> Ratko
>>>
>>
>>
>>
>> --
>> Ratko
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip [at] puck
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
>
>
> --
> Ratko
>

--
Ratko

rade239 at gmail

Aug 8, 2012, 5:04 PM

Post #10 of 13 (895 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

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> 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> 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>
>> *To: *"Lelio Fulgenzi" <lelio [at] uoguelph>
>> *Cc: *cisco-voip [at] puck, "Pavan" <pav.ccie [at] gmail>
>> *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>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>
>>> *To: *"Pavan" <pav.ccie [at] gmail>
>>> *Cc: *cisco-voip [at] puck
>>> *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>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> 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> 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
>>>>> > https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ratko
>>>>
>>>
>>>
>>>
>>> --
>>> Ratko
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip [at] puck
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
>>
>>
>> --
>> Ratko
>>
>
>
>
> --
> Ratko
>

--
Ratko

lelio at uoguelph

Aug 8, 2012, 5:18 PM

Post #11 of 13 (890 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

i'm pretty sure that on pre-v7, any phone that is configured has an active DN. if the phone is not registered, the forwarding settings take place. if no forwarding takes place it will ring error tone. a DN is more accurate than a wildcard route pattern.

an alternative to moving DNs into other partitions is to modify the DN from the DN search panel and uncheck the active checkbox. this is how i would do it in v7, not sure if v6 has something similar.

---
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)

----- Original Message -----
From: "Ratko Dodevski" <rade239 [at] gmail>
To: "Lelio Fulgenzi" <lelio [at] uoguelph>
Cc: cisco-voip [at] puck, "Pavan" <pav.ccie [at] gmail>
Sent: Wednesday, 8 August, 2012 8:04:46 PM
Subject: Re: [cisco-voip] CMM with two CUCM clusters and MGCP

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 > 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 > 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 >
To: "Lelio Fulgenzi" < lelio [at] uoguelph >
Cc: cisco-voip [at] puck , "Pavan" < pav.ccie [at] gmail >
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 > 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 >
To: "Pavan" < pav.ccie [at] gmail >
Cc: cisco-voip [at] puck
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 > 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 > 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 > 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
> https://puck.nether.net/mailman/listinfo/cisco-voip

--
Ratko

--
Ratko

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

--
Ratko

--
Ratko

--
Ratko

rade239 at gmail

Aug 8, 2012, 5:23 PM

Post #12 of 13 (890 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

I also have CM v6.1 in our production and just saw that there is CFUR field
on the device. Good thing is that we have CM6.1 for production and 8.6 for
test (exacly the same as the customer :) ).

Regards

--
Ratko

lelio at uoguelph

Aug 8, 2012, 5:47 PM

Post #13 of 13 (890 views)
Permalink

Re: CMM with two CUCM clusters and MGCP [In reply to]

checking the release notes, it looks like this was made available in 6.0(1)

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_0_1/cucm-rel_note-601a.html#wp45126

the document i checked earlier, 6.1 DN configuration guide, did not have the call forward unregistered parameter, that's why i said this.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmcfg/b03dn.html#wp1281526

but since you've found it. you're great.

---
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)

----- Original Message -----
From: "Ratko Dodevski" <rade239 [at] gmail>
To: "Lelio Fulgenzi" <lelio [at] uoguelph>
Cc: cisco-voip [at] puck, "Pavan" <pav.ccie [at] gmail>
Sent: Wednesday, 8 August, 2012 8:23:33 PM
Subject: Re: [cisco-voip] CMM with two CUCM clusters and MGCP

I also have CM v6.1 in our production and just saw that there is CFUR field on the device. Good thing is that we have CM6.1 for production and 8.6 for test (exacly the same as the customer :) ).

Regards

-- Ratko

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads