I have recently moved our collaboration servers to a different VLAN, after updating all the IPs across the 3 servers (CUCM, CUPS, UNITY), it's all been working fine apart from the Jabber client.
Jabber for Mac and Windows is still seeing the old IP address of the CTI server, even after I've updated the XML file on the TFTP server and restarted services multiple times. Everything else from the XML file has been updated fine.
It's version 9.1 for CUCM, Unity Connection and CUPS. The DNS bit is fine, it's the IP address that shows up in the XML file. I am not sure where it's pulling it from when I have updated the on on the TFTP server.
Also, when I try and retrieve the XML file myself, it downloads the right one, with the right IPs.
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.