I have 3 CUCM CTI server in my service profile.
I use Extension mobility to login to the device and control the deskphone.
when the jabber client logged in the CTI is working with the primary CUCM CTI.
I have notice when I stop the CTI Manager of primary CUCM the jabber client dont use the secondary CUCM CTI server.
it looks like the jabber client still trying to connect to the primary CUCM CTI server.
I have all the necessary access control groups in the end user.
When I log out and log in again the CTI is working with secondary CUCM CTI
please help me
Is this secondary able to be resolved by DNS?
Try this from the command line:
Your results should have all 3 of your nodes
I have the same issue.
I tried it on 2 environments and i got the same.
Is this a normal Cisco Jabber behavior?