Cisco Bug: CSCvt58119 - Unity Connection reply 302/401 for voicemail request and cause CUCM tomcat CPU high
Aug 26, 2020
- Cisco Unity Connection
Known Affected Releases
Symptom: Primary Unity will send 302 to redirect to backup Unity if primary is busy/high CPU, but backup Unity could not handle it but reply 401 as the Cookie is not shared between Primary and Backup Unity, which trigger refresh SSO token frequently as Jabber think it is invalid token now. this is risk for CUCM tomcat or Unity tomcat. Conditions: Following are two conditions where customer can hit this issue 1) Jabber client is using Authz token for login and Authz Server configuration is missing at Unity Connection server 2) In Unity connection cluster deployemnt, publisher node sending 302 response to Jabber client and client is redirecting API request to secondary node using same jsessionID.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases