Guest

Preview Tool

Cisco Bug: CSCvt64130 - Jabber4W stucks with using LSC for TLS even if it is configured to use SIPOAuth

Last Modified

Apr 17, 2020

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

12.6(1)

Description (partial)

Symptom:
J4W under special conditions does not utilize SIPOAuth even if correct CSFJABBER.cnf.xml file is fetched (with following lines: <sipOAuthMode>1</sipOAuthMode> and <sipOAuthPort>5090</sipOAuthPort>). It is keep trying to contact CUCM via port 5061 and NOT 5090. If CAPF certificate on CUCM gets expired and new LSC is NOT installed on Jabber client, phone services will not be connected.

Conditions:
J4W 12.6(1) that was configured in past to use Device Security Profile - Encrypted with TFTP Encrypted Config and establish TLS using LSC certificate.
Later, Device Security Profile was changed to SIP OAuth.
Additionally, if you regenerated CAPF certificate which was expired, updated CTL file, Jabber's phone services will not be connected.
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.