i have a CUCM 7.1.5 cluster (1 PUB and 2 SUB), i had all phones ( currently 30) registred in the PUBLISHER wih is also the 1st TFTP server.
i had noticed some radom problems shuch as:
- sometime new configuration on phones does not take effect even after resenting the and restarting TFTP sevice
- some phone once they logout their device profile, the phone display an other phone configuartion wich not compatible with it config in CUCM
- some other phone keep the device profile parametres after logout, howver the Phone secreen show that the device profile had been unloaded.
i don't what could cause those kind of problem, do i have a database problem? and how can i deal whit this?
thx for valuable help
Make sure all changes are made on the Publisher? If you make changes on the Subscriber they will not take effect as they do not have write access to the database.
Can you confirm that you are making changes on the Pub?
we have faced same issue with 6.x, and the root cause was dbreplication issue due to link failure between ccm pub n sub. use rtmt n check db replication realtime status n report. check bug toolkit for ur cucm version too.
Sent from Samsung tablet
Apologies for any typo
i checked replications on the 3 servers, it's in "good" state on all of them and the have the same Number of Replicates Created.
what is the complete call manager version you are running?
Do you face the issue all the time or is it intermittent?
When the issue occurs, can you check your DB replication status? you check this under Cisco Unified Reporting >> Cisco DB Status
thx for your response
im running 18.104.22.16800-6 version, i m facing this issue intermittently. it happened this morning when i checked the DB replication it was good.
I had this same issue once where DB Replication was fine but phones did not get updates. Turns out the RIS service was the culprit. You can try to restart it but sadly I've found that generally a cluster reboot is in order.
do you mean "Cisco RIS DATA Collector"? is restart it resolve the issue? because i already reboot the whole the cluster but it did not resolve the issue.
Sounds to me like you need to have TAC look at this issue. Without some more detailed analysis I cannot say what is going on. However, I will share what comes to my mind as troubleshooting steps that I would take next.