Cisco Meeting Server - Locking down Spaces to a specific CODEC

[CatsAndIT]

Hello all!

Looking for some guidance on the title.

Basically, we have clustered CMS2K/1Ks that were previously hosting scheduled conferences for a significant amount of Webex room-series CODECs. We've moved to building out individual Spaces for each CODEC to make conferencing more accessible to our users.

We still do want to allow the conference chair/host to maintain control over their conferences with Active Control using callLegProfiles, so we have provided each CODEC with a PIN to gain access to the host callLegProfile for their assigned Space, while all other attendees to conferences hosted in the space join into the lobby and then get admitted by the host.

The issue that we're concerned about, is that if someone from Site A travels to Site B, there is nothing to stop them from using Site A's Space/Host PIN in Site B's CODEC... regardless of if Site A is hosting a meeting during that time.

So what I would like to configure:

1. Configure a Space that is explicitly tied to a CODEC's e.164 alias/SIP URI
2. Make it so that when the CODEC that is tied to the space joins/hosts a conference in that space, they are automatically assigned the host callLegProfile
3. Make it so that any other CODEC/participant who joins that space automatically gets assigned the guest callLegProfile
4. Make it so no other CODEC/participant can gain access to the host callLegProfile

Is this possible? And if so, what are the steps to do so?

Thanks!

[b.winter]

Hi,

1) There is nothing, that checks, who is the calling number in CMS. Anyone who has the space number can dial into the space.

For you host / guest stuff:
Either use different space numbers / uris with different profiles assigned and / or use different PINs.

E.g.
1000 for Space 1 is for Host access and 1001 for Space 1 is for Guest access
Or
1000 for Space 1 with PIN 1234 for Host access and PIN 2345 for Guest access.

But whoever knows the space uri / number for the host or the host PIN, will be able to join the meeting as host.

[CatsAndIT]

So literally what we're already doing.

I'm digging into the documentation and noting that it says something about cospace users, tenants, etc. Is this a possible avenue to accomplish what I'm wanting to do, or is that something that is only for Web Console users?

[b.winter]

As it is not possible, you won't find anything in the documentation.
As already said, there is no logic, to check the calling party. CMS doesn't care, who is the calling number / device.

If you want to use a specific space from a specific device, then you always have to dial the number of this space.

If the endpoint is registered in CUCM, then you could use the call routing options in CUCM, to route calls based on the calling number.

[Meddane · Accepted solution]

Cisco CMS always lookup in the called party (URI) either using the incoming table to connect the participants to a space or using the outgoing table to route out the call to another call control system.

For the coSpaceUsers option available in the coSpace API configuration, the purpose is:

By default if a user tries to access the space using the Cisco Meeting Web APP (web browser) the CallLegProfile Guest is applied by default, therefore Cisco Meeting Server puts jdoe user in a lobby room waiting for the owner to join in even if the jdoe user is the owner of the space.

To allow the user to access his space using Cisco Meeting Web APP, we need to use the concept of the coSpaceUsers.

The coSpaceUsers allows users to access their spaces using the Cisco Meeting Web APP as the owner.