Preview Tool

Cisco Bug: CSCuq81822 - Security status not sent to all phones when endpoint drops from chained conf

Last Modified

Mar 29, 2017

Products (1)

  • Cisco TelePresence Conductor

Known Affected Releases


Description (partial)

The correct security status may not be updated on phones after an endpoint drops from a chained conference and CUCM consolidates the conferences

This issue was observed with this secenario:

Phone1, Phone2, Phone3 (all secure phones)
Phone4, Phone5, Phone6 (all secure phones except Phone6)

1) Phone 1 calls Phone2 & Phone3 and initiates a conference using Conductor. Due to all phones being secure phones, this conference is secure.
2) Phone 4 calls Phone5 and Phone6 and initiates a conference using Conductor. Due to presence of Phone6, this conference is non-secure.
3) Phone 1 conferences in Phone 4, and Phone 4 merges this call with the other conference it is participating in. Now both conferences are chained and overall status changes to non-secure

When Phone6 leaves the conference, the call status does not update to "encrypted" on all phones. Only Phone5 displays lock icon.
Bug details contain sensitive information and therefore require a 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.