A customer requires scheduled Cisco TelePresence video conferencing and the capability for ad hoc conferencing. Which product would be recommended for the customer?

A single MCU shared between TMS-scheduled and ad hoc calls risks resource contention, and there is no call control platform specified to initiate ad hoc conferences.

Cisco TMS paired with an MCU provides the scheduling engine and resource management for pre-booked conferences, while Cisco Unified CM paired with a separate MCU enables on-demand ad hoc conferencing through call control - combining both covers the full requirement. Two distinct MCU integrations are needed so scheduled capacity does not conflict with ad hoc capacity. This is the standard Cisco reference architecture for mixed scheduled and ad hoc video deployments.

Two MCUs with only TMS provides redundant scheduled capacity but no mechanism for ad hoc conferencing initiation, which requires Cisco Unified CM.

Cisco Unified CM with two MCUs provides ad hoc capability but lacks TMS, so there is no scheduling or resource reservation for pre-booked video conferences.

Cisco Conductor manages and load-balances MCU resources but is not itself a scheduling tool and does not replace TMS for calendar-based conference booking.

Adding Conductor to TMS and an MCU introduces unnecessary complexity for this requirement and does not map to the standard recommended architecture for scheduled plus ad hoc video.