Partial Telepresence Screen License Migration to CMS SMP+ license

[amit611988]

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

[R0g22]

1. You can use the same CMS for rendezvous and ad-hoc bridge in CUCM. From a configuration perspective CUCM will need to have SIP route pattern and/or route patterns depending upon how you want to route the call. On CMS, routing is a little different. All CMS cares about is the domain so you need to create inbound rules to allow calls to whatever domains you have for your spaces etc. If CMS fails to match anything in incoming and forward rules, it will reject the calls by default.
For outbound calls, you would need to set up rules as well depending upon the domain that you want to route to and the proxy that needs to be used.

2. I believe you should be able to migrate your screen licenses to SMP+ and/or PMP+ but that would come at a reduced cost sure. Best to talk to your Cisco Sales Rep or Partner for this.

[amit611988]

Thanks. 

Regards,

Amit