How to Disallow New Registrations to OLD CM 1

[thar27]

Hi all

We just cut fro 5.2 to CM 7. They're both still up but we'd like to disallow new registrations to the old CM 5. Is there a way to do that without taking the system offline?

Thanks!

 

[wpetilli]

Assuming you mean registration to the PE.. you can either disable the PROCR IP-interface or from that same screen disable h.323 registrations and/or h.248. Either way you'll have to disable the ip-interface to make the changes.

 

[kyle555]

If you're migrating slow, maybe change security codes of stations moved to cm7. Or, if you're moving ip ranges at a time, make a network region with no connection to any other regions with dsp's. CM won't let a phone register if it can't get dialtone/dsp. Maybe have a blacklist of subnets as you move over.

 

[kyle555]

Actually...just had a idea. Crazy enough it might work. If you did the network blacklist thing above and made that network region have as a 'survivable gk' in page 2 the IP of procr of CM7, then cm5 should refuse to have the phone register but might actually pop the survivable list to the phone to push them over to CM7 on their own. Gutsy and unproven, but it could be fun to try.

 

[thar27]

We did disable nr-registration on the network regions currently in the old system.
However, that "kicked" the currently registered users off the old system...but not necessarily disallowed new registrations.

We wanted it to be a more "soft" process.. but it didn't look like that could be an option.

 

[thar27]

Sorry.. we were at the 11th hour and curious for a quick fix! We thought the vendor would have provided the solution but they had no idea.. so we had to figure it out on our own. I'm gonna note that for when I'm not so spent and work it through.

Thanks kyle!

 

[kyle555]

Well, if you're asking in the middle of a migration, be careful wtv you do!

Otherwise, disable NR reg will kick them off the core cm. If that were remote branch 3, in NR3 with a gateway and LSP, all disabling reg on NR3 would do is kick NR3 into LSP mode.

Depending on your architecture and how you're trying to migrate, making those NRs disconnected from all dsps in 5.2 will guarantee a reboot provided no GWs are active in LSP mode.

Or, you can probably feed up a station import with ASA to change the security codes of a bunch of phones in 5.2, reset ip-phones and specify a subnet or extn range to force a reboot, new 46xx to point em to CM7 and do it that way.

Couldn't tell ya what makes most sense for you, but mixing and matching a few strategies should get you out of the woods.

Are you slowly migrating, like just the sales Dept in site 1 on voice vlan 1 need to go to 7 but everyone else there stays on 5.2?

 

[kyle555]

In restrospect, wtv you do, try not to mess with the pws. Can't remember h323, but I know as soon as sip phones get a 'invalid pw', they drop extn and pw and you have to enter manually. Try to avoid invalid passwords as a means to kick phones off

 

[mattKnight]

I'd consider doing it at the network level.
Alterms your voice vlann routin to drop traffic directed to your old cm

Something like

IP route <ip of old procr> 255.255.255.255 null

Of course deponds on your network layout...

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.