Cisco Bug: CSCuw52153 - Jabber won't register back if SessionPersistency is ON until reset on CM
Feb 02, 2017
- Cisco Jabber for iPhone
Known Affected Releases
Symptom: - Jabber devices will not register back with CUCM after an IP address change (or after some time of being idle) until reset manually from the CUCM device page. - The Jabber devices will still show as "Registered" from the CUCM GUI even when they really aren't and can't place/receive calls. Conditions: - Running CUCM version 9.x or earlier. (Version 10.0 and above aren't affected as support for Session Persistency was added for Jabber devices) - The "Time to Wait for Seamless Reconnect After TCP Drop or Roaming (seconds)" setting within the Common Phone Config and/or Enterprise Phone Config is not set to 0.
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