Conductor-like functionality of CMS

[Anthony T]

With Conductor, you could configure it in such a way that calls could 'invisibly' be made to the endpoints, but would instead go through the TPS and automatically continue on to the endpoint, thus creating a multipoint-enabled call with a system that does not (or cannot) have MS licensing.

Is this possible with a CMS setup?

I have a client looking for this kind of functionality, because they basically don't do any call scheduling in their environment and the users setup calls themselves. They are now installing systems for which the can't get MS licensing (DX systems, SX10), and thus are forced to look at CMS....and are hoping this can still be hands-off administratively.

If not...any recommendations?

Thanks.

[Patrick Sparkman]

Are you referring to the ability of an endpoint connecting to a conference and the conference bridge (ie: Conductor) automatically call out to other pre-configured endpoints?

[Anthony T]

Yes, that is what I'm recalling.  You could use that and, in essence, all endpoint calls actually went to the bridge.

[Justin Ferello]

Sounds like he is really talking about Multiway....

[Patrick Sparkman]

I thought of Multiway, but if they're systems are running CE software, than that wouldn't be possible as it's a TC software feature. Unless they have CUCM and are utilizing ad hoc conferencing.
CMS alone to my knowledge, doesn't support this type of feature, as it requires other components such as CUCM ad hoc conferencing for example. If this is something you'd like to have out of the box with CMS, you'd have to submit a feature request to your Cisco Account Manager.
A workaround is to use the Cisco Meeting App, user could log into it and make outbound calls from their space to each endpoint that would need to be connected in the conference, or each user can simply dial into the space from their endpoint when it's time for the meeting.

[Jaime Valencia]

They could also script that via API, or create a front end page for their users where they can input the DN/URI and send the API request to call the endpoints. Similar to what CMM has.

[Anthony T]

Hmm.  Interesting idea, but I think likely too complex.  They would have to contract resources to create this interface/scripting solution.

[Anthony T]

I wish Multiway was still a supported feature.

Thanks for the answer.  I think rendezvous style conferences are likely going to be the answer here.  It's still going to require a learning curve on the user's part.

I think using CMA for the sole purpose of dialing out is likely a bit too complex for these users.

[Nick Halbert-Lillyman]

Are the endpoints registered to CUCM?  If so, you can do Ad-Hoc conferencing with CMS.  The call flow is different to Multiway, but it more or less looks the same to the user, e.g.:

User 1 calls user 2

User 1 presses "add", calls user 3, user 2 gets put on hold

user 1 presses "Merge", all calls are redirected to CMS

[Anthony T]

No, endpoints are registered to VCS.  No CUCM in play.  May need to consider it though.