Conductor with scheduled conferences and virtual rooms on the MCU's
we deployed a conductor with 2 MCU's.
The MCU 1 was for the scheduled conferences and MCU 2 was intended for multiway / adhoc. Now we have to deploy the conductor(x.2.2.) for Adhoc/Multiway and Scheduled conferences about the TMS 14.3. Take out when I configure conducotr with the MCU's, the allow the nummeric registration on the MCU must be unchecked. But while I lose my existing registrations of the existing virtual rooms on the MCU's.
How i can handle a conductor using and existing virtual rooms or i must create about the conductor the virtual room?
Furthermore, as I stated in another topics, according to the Conductor's deployment guides, the CPL deployment model will be discontinued in a future release, then, I strongly recommend you to use the new B2BUA deployment model, so that you can avoid an effort in the future to migrate from the old deployment to the new one.
Please rate useful replies and remember to mark any solved questions as "answered".
Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.