Strange Subscriber issues: Possible Replication Issue? Running CMv5.1
I have been running into several issues lately that I think revolve around replication between my Subs/Pubs.
High overview of my current setup: Clustering over the WAN with a Subscriber at my local site and a Sub/Pub at another site. The phones at my site are registered to the local Sub with the remote site's Sub/Pub as backup. Also have a local gateway for PSTN access.
The first issue I noticed was when we deleted a phone/DN from the CallManager (and it was completely gone from CM), when I called the number, it would still route to voicemail as if it still existed in CM and was set to CallForwardAll to Voicemail. There was no pattern matching the number of the user's phone that I removed. Eventually it fixed itself. Also a reboot of the local Subscriber would fix it.
The second issue I ran into was the phones where I am at unregistered to the local Subscriber and registered across the WAN to the Sub/Pub at a remote site. The local PSTN gateway stayed registered to this local Subscriber. The Subscriber was still up and services were still running but the phones weren't registered to it anymore. I had to reboot the Subscriber and that fixed the issue.
The last issue I noticed is the Active/Standby CMs displayed on the phone do not match up with the Call Manager Group configuration on CM. In the CM Admin pages, I have the list configured as: 1) Sub01 2) Sub02 3) Pub but the phones are showing Active/Standby/Tertiary in this order: 1) Sub01 2) Pub 3) Sub02. Again, these phones are currently registered to the local subscriber and it seems that all problems point back to this subscriber.
Would appreciate any info/advice/direction/solution I could get.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.