The customer setup consist of three call manager servers in a cluster - CCM1, CCM2 and CCM3. CCM1 and CCM3 are subscribers and CCM2 is the publisher. The CCM version is 3.1(4b) and phone load is 405.
We configured two call manager group - Group A consist of CCM1, CCM3 and CCM2. Group B consist of CCM3, CCM1 and CCM2. As you can see, the subscriber CCM are the active call manager servers and publiser is the standby call manager server.
Some IP phones were registered to Group A and some were registered to Group B.
We perform a proper server shutdown for CCM1, we noticed the IP phones registered to CCM1 started to reboot and comes up after 30 seconds. It is strange that the IP phones will reboot because the IP telephony redundancy should "kick in". My understanding was when the active CCM fails, the secondary CCM should take over.
Then we shutdown CCM3, the same thing happen, the IP phones registered to group B starts to reboot and comes up after 30 seconds.
We did the above mentioned test by just disconnecting the subscriber CCM from the network, this time, the IP Telephony redundancy works, the IP phones do not reboot but will register with the standby Call Manager server ( standby becomes active ), the IP phone screen did a refresh, a split second thing.
Anybody could advice me on whether it is proper the IP phone to reboot and rehome to the next Call Manager server when a proper server shutdown is carried out on the active CCM ?
I do not think you have that level of redundancy available. If a given CM goes down all phones registered to it will go get reset and will look for a new CM. So I would say this is a expected behaviour.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...