An engineer has transitioned over to Telepresence-managed scheduling from direct- managed conference bridges in TMS and has begun to see failed calls and double- bookings of conferences. What should…

Setting the TelePresence Conductor as the preferred MCU is a resource selection configuration that does not resolve conflicts arising from unmigrated legacy scheduled conferences on bridges.

When the management mode changes, previously scheduled future conferences remain associated with the old direct-managed booking method. If those conferences are not migrated to the new TelePresence-managed scheduling system, TMS will attempt to book the same bridge resources through two different management paths simultaneously, causing resource conflicts, double-bookings, and failed calls.

Manually configuring a variable field is not a recognized troubleshooting step for resolving double-booking conflicts caused by a scheduling management mode transition in TMS.

Enabling cascading is a feature for linking multiple MCUs to support large conferences and is unrelated to resolving double-bookings caused by unmigrated scheduled conferences after a management mode change.