Guest

Preview Tool

Cisco Bug: CSCun70579 - Jabber fails to reconnect if previously used VCS-e cluster goes down

Last Modified

Apr 29, 2014

Products (1)

  • Cisco Unified Mobile Communicator

Known Affected Releases

9.6(1)

Description (partial)

Symptom:
Summary:
If Jabber is not relaunched, Jabber will fail to reconnect to 2nd cluster when 1st cluster is down. 

Scenario:
1) configure 2 SRV records pointing to 2 vcse clusters

2) configure 2 A records in vcse cluster1, 1 A record in vcse cluster2

3) Client signs in via collaboration edge successfully through cluster1
4) VCS-e cluster1 that was used in first sign-in attempt goes down (becomes inaccessible via network)

Expected result:
Jabber should be able to sign in cluster2 for edge. 

Actual result:
Jabber client never attempts to use the cluster2  for edge.

Conditions:
Device: Galaxy S4 (OS: 4.2.2)
Network: Wifi+Edge
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.