Which bridge solution requires Cisco TelePresence Conductor?

When the Cisco TelePresence Server is configured in remotely managed mode, it delegates conference management and resource allocation to Cisco TelePresence Conductor. Conductor acts as the external orchestrator that provisions and routes calls to the TelePresence Server, making it a mandatory dependency in this deployment model. Without Conductor, the Server cannot function in remotely managed mode.

In locally managed mode, the TelePresence Server handles its own conference management independently, without requiring an external Conductor component.

The Cisco TelePresence MCU does not use a remotely managed mode that integrates with Conductor; this managed-mode architecture is specific to the TelePresence Server product.

The Cisco TelePresence MCU in locally managed mode administers its own conferences natively and has no integration requirement with Cisco TelePresence Conductor.