Publisher or Subscriber or either

[phifdd4305]

So from day one of my CUCM learnings I've always made changes on the Publisher that publishes changes to the subscriber(s). My colleague seems to think that he can make changes on the subscriber and it replicates to the other nodes as well. Is there any truth to this or should all changes be made on the publisher? If so then what are the implications with the changes he made on the sub?

Asking for a friend :)

[Jaime Valencia]

You can make changes in any server in the cluster and they all send the info to the PUB so it's then replicated to the DB on each server.

If the PUB is down or unreachable, only UFF work on the SUBs.

[Aeby Vinod]

Adding on to Jaime's reply. Lets say you have a publisher and subscriber in a cluster and replication is active between them and they servers are actively communicating with each other without a problem. When you are putting in the Subscriber's IP address and accessing the GUI, you are actually seeing the Publishers DB and not the subscribers, So essentially you are always making the changes on the Publisher DB irrespective of what node you access and the change is replicated to the subscribers. You will get the subscribers DB only when the sub can't reach the pub and the only change you can do the sub DB would be user facing features.

Please rate if you find this helpful.
Regards,
Aeby