Disabling a CUCM server from registering any CIPC clients

I want to make a Call Manager unavailable for CIPC registration. What services would I need
to shut down so that any CIPC that attempts to connect goes to the secondary in its
configured list of CUCM servers?
amigan_99Network EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ken BooneNetwork ConsultantCommented:
So le me get this straight... you have 2 CUCM servers and you want to force the CIPC clients to register to CUCM #2 and not #1 is that correct?
amigan_99Network EngineerAuthor Commented:
I am trying to decomm a subscriber and for some reason there are clients still registering to it.
I could turn the dern thing off. But if there's some drama I want to be able to re-activate quickly.
So the idea is to just turn off the service and force these CIPC clients to hit what's configured
secondary (or ternary) in their local CIPC config. I've been trying forever to get IT to get all
these updated but now this has gone on too long and need to nudge things along. Make sense?
Ken BooneNetwork ConsultantCommented:
So what you can do is this... set up a new CUCM group and leave the CUCM that you don't want the CIPC clients to register to out of the new group.  Then you can do one of two things depending on your setup.  If you have  a device pool that is dedicated just to the CIPC clients, then simply change the CUCM group that is in that device pool to the new CUCM group.  Rest the device pool and you should be good.  If you the device pool that the CIPC clients are on is a device pool that is used by other devices, then create a new device pool exactly like the existing device pool, except use the new group.  Then go back to the CIPC clients and change their device pool.  Reset the devices and you should be good to go.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ken BooneNetwork ConsultantCommented:
Email stated this was inactive and suggested to select the best solution and close the case.  I provided a solution, but have heard any updates on this.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IP Telephony

From novice to tech pro — start learning today.