I would check the following - Are the 30% - 40% in another Device Pool as the others? --If yes check the CUCM Group configured in this Device Pool If the same phones sometimes register on the sub, and sometimes on the pub. You may want to check if they acctually cannot reach the sub and therfore fallback to the pub. Since only Wifi Phones are affected by this behavior I would check the wifi setup. An important step is to try to group the phones even more. Maybe there are phone which are never affected by this. If you find such a phone you can try to compare a affected phone with a “healthy” one.
We worked with TAC some more yesterday and they were (finally) able to capture packets and logs for a phone that registers with the Pub. Wasn't easy to duplicate since the issue is very sporadic. They are reviewing the logs now so I hope to hear something back soon. To answer your questions:
1. In the packet captures taken from the phones, what is seen? Are they seen to contact sub on tcp port 2000 and fail, then reach out to pub? TAC reviewing now.
2. What about the configuration files for those phones which have the issue? Do they show the right order of the call managers? When phones register to the Pub, sometimes they show the Sub as a second choice and sometimes they don't (just shows the Pub as the only choice).
3. What is the topology between the phones and CUCM? All sites and locations are in one big MAN. The Pub, Sub, and WLAN are all on different VLANS.
4. Is there something common between the phones that have the issue? Are they all located at one site? There is at least some logic to this. The only phones that are having problems are 7925s only that are on our main hospital campus, and also being served from the same wireless controller. We have 7925s at other sites served by different wireless controllers (also different VLAN) and they are not having the problem. But I am not the Wireless Network SME so that is all I can add on that subject.
Also - we migrated all of our DHCP and DNS onto InfoBlox last week and we believe that may coincide with the beginning of the problems, but it is hard to pin down.
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.