Call Manager can suddenly not force reset or restart of any Cisco IP phones.

I have an office with a Cisco Call Manager Pub and Sub on version 6.1.2. While everything was working fine last week, suddenly I can now no longer make changes to lines on a phone or force a reset or restart of any phone while in Call Manager configuration.

Additionally, soft reset and hard reset of a phone doesn't pull any changed configuration. The net effect is that I now can't add any new phones, nor change the configuarion on any existing phone.

It's the middle of the work day, so I can try to schedule a reboot of the Pub and Sub later this evening, but I'm hoping someone here has seen this before and can recommend a simpler action.

Call Manager Publisher and Subscriber are both the Linux flavor, and both on version 6.1.2. All phones are the same standard 7961 model, nothing fancy. I've done no recent upgrades or firmware additions. DHCP
LVL 3
skpruettAsked:
Who is Participating?
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.

bkepfordCommented:
I would check your services in the Admin client and make sure all are running. Call manager service may be running but something needed for phone control isn't.
0
skpruettAuthor Commented:
Everything appears to be running, but the problem continues. Restarting TFTP service did not appear to affect the issue. What other services are related to the actual push of a configuration to a phone?
0
bkepfordCommented:
The tftp server really should be it. Reseting the phone should be in the call manager service itself which of course you don't want to restart during production hours.
 Honestly as weird as the problems your having I'm going to guess a reboot is going to fix it all.
0

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
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

skpruettAuthor Commented:
I'll schedule one for this evening and update tomorrow am. I much appreciate the help bkepford.
0
skpruettAuthor Commented:
Bkepford, Instead of a full reboot, I started with your suggestion, restarting the call manager service. It worked like a champ. Many thanks for the help!

0
skpruettAuthor Commented:
After restarting the TFTP service on both the Call Manager Publisher and Subscriber, I scheduled a non-production time restart of the Call Manager service as suggested. This cleared the problem.
0
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.