Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Changes to phone devices in CUCM admin console not being configured on phone

I can log in to the CUCM admin page and make changes to phone devices. The changes made are reflected in both the PUB and both SUBs. Devices do not take changes however. Reset and restart commands from admin page on devices do not actually reset or restart devices. Physically resetting device by unplugging switch port on phone does not help reflect configuration changes. Verified TFTP settings are correct and reset the TFTP service on servers. Troubleshooted on Cisco phone 7945 and 8945. Any help on how to resolve this?

CUCM ver. 9.1.2

Phones 7945 Phone Load 9-3-1SR3-1S

Phone 8945 Phone Load 9-3-4-17

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

CCM service should not be

CCM service should not be restarted during Production hours as it will impact call processing and other important functions. You can schedule it during off hours.

Manish

4 REPLIES
Cisco Employee

Hi,This points to some

Hi,

This points to some database issue, the database replication may be broken. Please check through RTMT  and see if the database replication state is 2 for all the servers. You can try a 'utils dbreplication stop' on all servers followed by a 'utils dbreplication reset all' on the Publisher. Another quick fix would be a restart of the ccm service.

HTH

Manish

New Member

Hi Manish, I forgot to

Hi Manish, I forgot to mention that I did check DB replication and all looks good. Attached, screenshot. Will try restarting CCM service. what kind of issues should I expect by restarting these services in production during business hours??

Cisco Employee

CCM service should not be

CCM service should not be restarted during Production hours as it will impact call processing and other important functions. You can schedule it during off hours.

Manish

New Member

Manish, restarting the CCM

Manish, restarting the CCM service on the three CUCM servers fixed the issue for a very short period of time before it reoccured.

However a full cluster reboot corrected the issue fully. Thanks for your help.

85
Views
0
Helpful
4
Replies