Cisco Bug: CSCuo89949 - jabber edge (UCM failover) show connnection status not updated
May 29, 2018
- Cisco Jabber for Windows
Known Affected Releases
Symptom: When Jabber is registered using Mobile & Remote Access (MRA), the "Connection status" window shows connected address as primary Unified CM, even after a Unified CM fail-over has happened and the client is actually registered to the secondary Unified CM. Conditions: Jabber is configured with a device pool containing primary and secondary CUCM servers. While Jabber is registered using MRA, the primary CUCM fails.
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