I'm using UCM and IMP 9.1.2. All versions of Jabber v9.6 won't login in 'auto' mode, even though it can see my IMP server dns address has been identified to jabber via the SRV record. I must click 'manual setup' and then select Presence as the method and it then setup completes the login to the discovered IMP server.
I can clearly see it wants to use webex instead of presence as the method. Even the text says "Enter your WebEX ..." At least on the ipad version, the logs show it checking with Cisco's cloud webex server and finding our domain a valid webex domain. Why does v9.6 prefer webex and how do I stop it from doing that?
Ok, what is happening is that Jabber 9.6 is apparently now hard-coded to contact loginp.webex.com to check for webex licenses, which we have, so it never tries our IMP servers once it sees we have cloud webex enabled for our domain. The flowchart in the docs show this behavior.
What worked in our case for 9.6 for Windows was a combination of things. First one was to make sure we had the required internal DNS SRV records - _cuplogin and _cisco-uds. Second one was to use the SERVICES_DOMAIN=domain.com switch when installing the client with msiexe.exe (whether manually at a workstation cli or through an SMS flavored package.)
We did have to further tweak the SERVICES_DOMAIN switch just a little in our environment, to SERVICES_DOMAIN=internal DNS server ipv4 address.
We've had to go that way since our internal/external domains match up. Which seemed to be just enough to still let Jabber 9.6 reach our WebEx Connect site. Switching to IP address for SERVICES_DOMAIN seems to "trap" the lookup internally, at which point the Jabber client behaves as expected for auto-configuraiton.
You can get a good visual of whether it's going to work at the Jabber login screen. If it's hitting WebEx, youl'll see that reflected at the login screen. If it's hitting your internal records, you'll see a callout for Jabber voice services.
The problem for us was that Webex messenger was enabled in the Cisco cloud, and it shouldn't have been. Our rep got involved and had that deprovisioned in the Cisco cloud and now the simple login method works. If webex messenger is provisioned Jabber clients 9.6 and above will ignore on-premise presence servers with the auto method. Jabber 9.6 is hard-coded to check Cisco's CAS and ask for webex credentials if the check is successful. We do have webex meetingplace licenses but that is a separate thing from webex messenger.
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.