10-17-2017 01:41 AM - edited 03-18-2019 01:32 PM
Current I am working in a lab with CMS/Acano 2.0.6 version.
According to the API guide, the callProfile with participantLimit assign to a coSpace should work.
But it's failed in my lab, new guest participant through web client (WebRTC) could join the meeting/coSpace by the callId & passCode always and ignored the participantLimit value.
And the same failed testing result in the [locked=true] parameter in the callProfile. It didn't lock the meeting room like the guide's description. The user through WebRTC could enter to the meeting room directly, no matter what the value of the [locked] is true or false. It didn't need to wait in the meeting lobby, and no activation process needed.
But the parameter [messageBoardEnabled= true/false] belong to callProfile could work correctly, immediately at the same WebRTC environment.
If it is because the misunderstanding about both of the participantLimit & locked parameters' usage, please kindly let me know.
Thanks for any help.
Below is the relating configure.
callProfile - https://{{ServerHost}}/api/v1/callProfiles/4be17113-6c11-468f-83a4-59745d566de4
<callProfile id="4be17113-6c11-468f-83a4-59745d566de4">
<participantLimit>2</participantLimit>
<messageBoardEnabled>false</messageBoardEnabled>
<locked>true</locked>
</callProfile>
coSpace - https://{{ServerHost}}/api/v1/coSpaces/914ffb4b-d0de-4e10-9f0c-fd54d91abb10
<coSpace id="914ffb4b-d0de-4e10-9f0c-fd54d91abb10">
<name>Test Room</name>
<autoGenerated>false</autoGenerated>
<callProfile>4be17113-6c11-468f-83a4-59745d566de4</callProfile>
<callId>456789</callId>
<passcode>1111</passcode>
<secret>gTxu10sn.9FdGKG.T.5eZA</secret>
</coSpace>
calls - https://{{ServerHost}}/api/v1/calls/
<calls total="1">
<call id="99ef8aaf-e719-453f-bc0d-324198ed2b44">
<name>Test Room</name>
<coSpace>914ffb4b-d0de-4e10-9f0c-fd54d91abb10</coSpace>
<callCorrelator>7d944873-202a-4a35-8564-f1811ddd6d6e</callCorrelator>
</call>
</calls>
participants - https://{{ServerHost}}/api/v1/participants/
<participants total="3">
<participant id="79d85604-0922-4faa-aab2-8e6d6b9eb674">
<name>Joe</name>
<call>99ef8aaf-e719-453f-bc0d-324198ed2b44</call>
</participant>
<participant id="57db0d50-0090-4c67-ab0d-98651d56a66a">
<name>Bob</name>
<call>99ef8aaf-e719-453f-bc0d-324198ed2b44</call>
</participant>
<participant id="fdd627d2-ee99-4f1f-9b2f-c43387008412">
<name>Goat</name>
<call>99ef8aaf-e719-453f-bc0d-324198ed2b44</call>
</participant>
</participants>
10-19-2017 09:13 AM
I believe participantLimit is based on SIP calls, don't think it affects CMA, see Can I set a limit on the number of participants that are permitted to be in a meeting.
Locking a Space requires host and guess access, see How do I lock and unlock the meeting lobby.
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