05-26-2018 02:06 PM - edited 03-18-2019 02:08 PM
As Telepresence server and Conductor would be out of support in few years, we are deploying the CMS to the Customer site. The customer has the below infrastructure deployed:
All The Telepresence Endpoints are registered to CUCM
Calls are routed via CUCM to VCS-Control.
Telepresence server / Conductor are configured as the conference bridge. 1 TP Conductor is used as ad-hoc bridge, another TP-conductor is used as rendezvous bridge.
Telepresence server has 12 screen licenses.
I have 2 questions.
1) While migrating from Telepresence Conductor To CMS, where CUCM is used for device registration and calls are routed via VCS-C and VCS-E, What apart from below should be configured ?
1. Is it OK to only configure CMS as the ad-hoc and Rendezvous conference bridge in CUCM and also add routing to CMS. Or what else needs to be configured so that we can use the CMS as the conference bridge in the same way as we are using the TS/Conductor.
2. Is it possible to partially migrate the Telepresence screen licenses to CMS SMP licenses, so that we can parallely use both CMS and TS/Conductor as the conference bridges.
Regards,
Amit
05-26-2018 02:25 PM
05-26-2018 02:41 PM - edited 06-11-2018 05:47 AM
Thanks.
Regards,
Amit
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide