Preview Tool

Cisco Bug: CSCup34360 - Update web help with more detail on encryption after changes in 14.4

Last Modified

Jan 12, 2015

Products (1)

  • Cisco TelePresence Management Server

Known Affected Releases


Description (partial)


There were undocumented changes to how Cisco TMS handle encrypted conferences in version 14.4.

Starting with 14.4, secure conferences work like this:

- If an MCU/TS/Conductor is scheduled, endpoints can always be booked in "secure: yes" without their encryption settings being checked, force encryption on the bridge.
- Conductor should have force encryption implemented in TMS.
- If you're booking a p2p/multisite/legacy MCU conference, TMS needs to know that every leg of the call is secure or you won't be able to book "secure: yes".




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.