Initiate the CLI First and foremost, you remotely access the CLI via a secure SSH session to the CUCM.If you do not have remote access to the CUCM via SSH, you can also gain access to the CLI via a locally attached keyboard and monitor.
Replication restarts after the database is overwritten.
This command may take some time for re-registration and synchronization with all product instances to complete.
Enables or disables the error log getting generated while any standard error occurs during communicating with the Jetty server.
Depending on the size of the replication folders, this operation may take several minutes.
Causes Connection either to start or to stop including a DSCP value of 18 in packets sent between the Connection servers in a cluster, so a router configured to prioritize packets based on their DSCP value can prioritize Connection data and voice messages. Run this command on subscriber and publisher servers before executing the CLI command utils dbreplication reset or utils dbreblication clusterreset.