Guest

Preview Tool

Cisco Bug: CSCvi70823 - J4W not receiving incoming calls after it has attended 1st internal call from any Jabber

Last Modified

Aug 09, 2018

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

11.9(3)

Description (partial)

Symptom:
J4W not receiving incoming calls after it has attended 1st internal call from any Jabber

Conditions:
Condition 1: 

Jabber_1 received it's 1st call from any Jabber_2
Jabber_1 attends the call and then disconnect the call
Now if same Jabber_2 or any other Jabber client tries to reach Jabber_1 user then he can't. They will keep hearing ringing but Jabber_1 user is unaware that Jabber_2 is trying to reach them.
Jabber_1 user will never get an incoming call notification until and unless he signs out and sign in back.

Condition 2: Jabber on  Windows 10
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.