Cisco Bug: CSCuj53227 - Jabber doesnt download jabber-config from new TFTP when settings changed
Feb 14, 2018
- Cisco Jabber for Windows
Known Affected Releases
Symptom: Jabber for windows registers to the wrong CUCM cluster if it alternatively connects to different clusters (Entirely different CUCM clusters) Jabber for windows will not update the JabberLocalConfig.xml file with new TFTP server when the connection setting are changed to the new cluster info. Conditions: Jabber alternatively connects to the 2 different clusters like lab and production. At some point in time, it will strict to connect to either of the setup even if we forcefully connect to other one by changing the connection info during the login.
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