If one does not already exist, specify a web application password in Cisco Unity Connection for the applicable user accounts." These accounts are LDAP sync'd so I can't set/change the web application password. Has anyone got this working and did you have to do anything special to make it work? I've attached an image of the setting on the client and the thing that really sticks out to me is the port only shows -- ; does anyone have a working client they can look at to tell me if this is where my problem may be?
From the screen capture, it looks like Jabber is configured to connect to Unity over HTTPS, rather than Unity Connection over IMAP. So it'll attempt to connect to the Unity patner mailstore server (10.2.200.23 from your screen capture) to download the voicemail messages to the Mac for playback. The protocol seems to be set to TLS without a port, so it should default to port 143. But if your partner Exchange server isn't listening on that port, then you'd need to update the Mailstore configuration in CUPS to reflect the correct port, and verify the user is associated with that profile in CUPS. Then when you re-authenticate with Jabber, it should retrive the new configuration.
I mentioned it looks like it's trying to connect to Unity rather than Unity Connection because the display string in the server window is printing out "Unity Address" rather than "Unity Con Address". But if the client has never been able to establish a connection, I believe it will always default to "Unity"; then change to "Unity Con" when/if it's able to validate it's a Unity Connection server.
Your configuration on CUPS seems correct. The only other thing I'd check in CUPS is if the end-user is associated with the Voicemail Profile that is using those two configurations. You can also verify the Mailstore settings for the Inbox Folder, etc. It that all looks correct, you may want to check if UC is listening on port 7993.
Other than that, you may want to verify the end-user credentials in the Accounts settings on the Jabber Mac client. You could also try changing the Server Settings to Manual and type in your Unity Connection server there to see if that has any difference. Otherwise, we'd probably need to get a PRT from the client experiencing this problem to see what the diagnostics are attempting to do when it's attempting a connection to the server after a fresh login.
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.