CMS Host and Guest scenario

[davidmongelli]

I followed these instructions to set up host and guest access.

https://kb.acano.com/content/7/69/en/how-do-i-set-up-host-and-guest-access.html

Created Cospace ccccc-ccccc

Uri=1010

CallID=1010

Create host callLegProfile aaaaa-aaaaa

• needsActivation=false
• defaultLayout=speakerOnly
• presentationContributionAllowed=true
• rxAudioMute=false
• rxVideoMute=false

Create guest callLegProfile bbbbb-bbbbb

• needsActivation=true
• defaultLayout=speakerOnly
• presentationContributionAllowed=false
• rxAudioMute=true
• rxVideoMute=true
• deactivationMode=disconnect

Associate guest callLegProfile with coSpace 

Create host accessMethod on coSpace

• uri=10100
• callLegProfile=aaaa-aaaaa
• callID=10100 

So my test scenario is:

• SIP endpoint (guest) calls 1010
• WebRTC (guest) calls 1010
• Both guests wait for the host to join.
• SIP endpoint (host) calls 10100
• Both guests are activated and put into the cospace with the host.

The Mic is muted on the guest SIP endoint, but neither the mic or the camera is muted on the Guest WebRTC.

I expected the Guest WebRTC would have had callLegProfile bbbbb-bbbbb applied, which mutes the audio and video of anyone calling 1010.

I think I'm missing something obvious. Any help would be appreciated

[Patrick Sparkman]

Using the API, check that the WebRTC client is using the correct callLegProfile?
It could also be that CMS can't control the mute/unmute state of CMA/WebRTC.

[davidmongelli]

I simplified things. I created a cospace with one calllegprofile which mutes the mics. I called in with two endpoints and confirmed their mics were muted. I connected with the WebRTC and it's mic was NOT muted. So It is incapable of controlling audio on a webRTC guest. Correct?

[Patrick Sparkman · Accepted solution]

Appears so, probably because CMA/WebRTC is an XMPP client and not a SIP endpoint.