Cisco Bug: CSCur07836 - Screen capture & file transfer fail when JSM connection to JFT goes bad
Mar 18, 2015
- Cisco WebEx Connect IM
Known Affected Releases
Server side issue where certain JSMs get into bad state for this component. Symptom: Selected customers on a given cluster fail to send screen captures and file transfers which utilized the Jabber File Transfer servers. The receiver of the intended screen capture or file transfer, sees nothing but a spinning dial and never receives the data Checking client logs will reveal a XMPP query error with type code 400 and "Bad Request" as a starting symptom. Conditions: The JSM on which the user maps to on the Messenger back is in a state where it is bouncing the user's packets intended to the JFT server, as indicated with certain keywords in the log.
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