Cisco Bug: CSCul02701 - Client does not reconnect back after network recovered
Jan 30, 2014
- Cisco Jabber for Mac
Known Affected Releases
Symptom: Client does not reconnect back after network recovered Conditions: When network changed, token invalid while resuming, jwcpp would request a new token but can't get response due to network change issue. In next resume, jwcpp did token request again and got a new one, reconnection succeeded finally. After then, former token request got response (failed one), sasl token was cleared, so when network changed again, resume hanged on because of empty token.
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