Cisco Bug: CSCun78136 - When downloading new Directory config Jabber requires sign out/in
Feb 07, 2017
- Cisco Jabber for Windows
Known Affected Releases
Symptom: Jabber for Windows tries to connect a previous LDAP server in the scenario described in the Condition enclosure below. Conditions: == Environment - There are 2 environment for the Jabber client to connect. For example) One is for testing and the other is for live network. - He uses not jabber-config.xml but jabber-windows-config.xml file as device configuration. jabber-windows-config.xml has information of LDAP server. == Steps 1. Jabber signs in the testing environment and works fine. "Last connection successful" on Help > Server Health menu shows LDAP server address of testing environment. 2. Signs out. 3. Jabber signs in the live network environment. Deskphone control and other features such as IM work fine but only LDAP search doesn't work fine. Jabber tries to connect the previous LDAP server (the one in the testing environment). "Last connection successful" on Help > Server Health menu shows LDAP server address of testing environment.
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