We have a UCCX HA cluster and can see all the cti port registered each of the servers, ports 1-20 UCCX_1 and 21-40 UCCX_2. The issue appears to the be the triggers or CTI Route Points. These appear to only be registered to UCCX_2 and if we reboot that server they don't fail over to UCCX_1. I have verified that these devices are associated with both uccx_telephony users.
This is normal behavior (sort of). It really does not matter which IP address appears in CUCM for the CTI RP. When CUCM gets a call for that RP, it sends the JTAPI messages to both UCCX servers as the trigger is associated to both CTI users. The server that is Engine master, responds and continues the call.
Sometimes, if RPs are reporting registered by the UCCX primary in CUCM, something will happen and it will report as registered by the secondary. This 'something' is not known, I looked into it once but after three weeks of waiting and checking every day finally gave up, as it is a cosmetic issue in CUCM and it will not affect call routing.
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 ...