ccum 6.1

[vburshteyn]

Hi,

I have your typical setup one publisher and one subscriber, running ccum 6.1.  Both are talking to each other, and phones are being routed.

Yet for some reason, when i update information on the phone (name display, add another line) it does not get pushed to the phone.  I am also unable to reset the phones from the ccum.

any ideas where i can start looking for the problem?

Thanks,

[William Bell]

The obvious first step is to check database replication. There are several approaches. One using Cisco Unified Reporting:

1. Go to https:///ccmadmin and logon
2. From the Navigation drop down list, choose "Cisco Unified Reporting"
3. You are sent to a new page, on the left click on "System Reports" to drop down the menu
4. Select "Unified Database Status"
5. If  someone has ran a report in the past, you will see a link to the report  in the main page. If you choose this link you will see an "older"  report.  To generate a new report you must click on the bar graph icon in the top right of your screen.
6. When generating a new report, the main screen will show a progress bar
7. After the report is completed you can view the following to get an idea on replication health:
   • Unified CM Database Access
   • Unified CM Database Status

Another method and some mitigation techniques:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00809643e8.shtml

Now,  it is important to understand that your specific set of symptoms may be  related to db replication issues but that is not necessarily so.  Actually, your symptoms are related to real time replication of cached  configurations and is more likely related to DBL Monitor. The DBL  Monitor service is responsible for identifying db changes and notifying  specific services running on the CUCM publisher node. These  notifications are then sent to other nodes. This uses a separate set of  services, processes, and communication channels than is used for basic  db replication for the Informix database.

So, first resolve any db replication issues. Then check if a restart of the DBL Monitor service helps.

HTH.

Regards,
Bill