Cisco Bug: CSCus64674 - Jabber will not login if redirected from a 10.x node to a 9.x node.
Aug 25, 2016
- Cisco Jabber for Windows
Known Affected Releases
Symptom: If Jabber is redirected from a CUCM/CUPS 10.x node to a CUCM/CUPS 9.x node you will not be able to log in. The issue seems to stem from the version of the SSL on each version. CUCM/CUPS 10.x uses SSL 1.2 where CUCM/CUPS 9.x uses SSL 1.0. When this issue occurs the client will throw an error: 2015-01-19 15:21:02,481 ERROR [0x000003a0] [sets\adapters\imp\components\Log.cpp(35)] [JabberWerx] [IMPStackCap::Log::log] - [LoginMgr.dll]: #0, CLoginCup::OnLoginFailed err-code: 30, err-string: SOAP 1.2 fault: SOAP-ENV:Sender[no subcode] "SSL_ERROR_SSL error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number" Detail: SSL_connect error in tcp_connect() . request-token:0 Conditions: CUCM/CUPS 10.x redirecting to CUCM/CUPS 9.x. Either via a ClusterUser query when logging in via CUCM, or an Inter-Cluster Peer configuration when logging into CUPS.
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