Cisco Bug: CSCut10632 - Jabber iDivert for a second incomming call continues to ring
Jun 08, 2015
- Cisco Jabber for Windows
Known Affected Releases
Symptom: Jabber Windows 10.6 with an active call, clicking iDivert for a second incomming call continues to ring until Jabber is restarted. Conditions: This defect is a symptom of Jabber not handling the ringOnce property. When ringOnce=True, Jabber ignores the ringOnce property and just rings as normal. This is not an obvious problem until a call is received while the user is already on a call and expects the ring to stop when the call is diverted.
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