I feel that we are having this same issue as we were showing lots of UDS 401 issues in logs.
We use Jabber 11.9.3 but are going to migrate to 12.6.2 this year. I would like to hear of a work-around/fix for this.
I thought most of the errors are related to AD password being changed and then Jabber creds not being updated.
But, based on this BUG it is likely the 401 I have been seeing is this issue described below.
Cisco Tomcat > localhost_access or RTMT Alerts showing 401 responds to UDS requests
Conditions:
Jabber SSO enabled with CUCM
When jabber wakes from sleep, PC has IP connectivity but no internal network connectivity
ex) PC wakes up, gets an IP but VPN takes time to connect to internal services
Most likely affects any jabber version
Workaround:
This issue does not cause any major impact because 401 error goes away once jabber has established internal network connectivity. If workaround is needed, make sure VPN is connected before launching jabber.
