There might be better ways to achieve this, but off the top of my head:
- You could assign some MCUs to the same IP Zone that the endpoints are assigned, these would be used for scheduled conferences, while the remaining MCUs are assigned to a different IP zone and used for ad hoc conferences. Using different IP Zones will keep the ad hoc MCU from being used by TMS in scheduled conferences.
- You could keep the IP Zone the same for all MCUs and endpoints, but disable the "Allow Booking" option for the ad hoc MCU, this will prevent the ad hoc MCUs from being used in scheduled conferences.
This is all assuming you're not scheduling the ad hoc calls, but just letting the user connect to the ad hoc MCU themselves from the endpoint. For monitoring, you can use CCC to monitor both scheduled and ad hoc conferences on the MCUs. See the "Routing" section on pg 32 and the"CCC" section on pg 181 in the TMS 15.2 Admin Guide.
Conductor would most likely be the best solution here to help manage the multiple MCUs.
