topic Re: Don't put co-hosts on hold in Webex for Developers

Don't put co-hosts on hold

PassePartout — Fri, 26 Jan 2024 10:13:57 GMT

when there are multiple co-hosts, the first one to start a meeting must then approve the other co-hosts upon joining. These co-hosts can no longer join directly, like the first one did, even if they are co-hosts. How do I make it so that all authorized co-hosts can join without asking the first co-host to start the room for approval again?
In the photo you can see the first co-host (left) who started the classroom. The second co-host who tries to enter must go through the authorization of the first co-host who started the room

Re: Don't put co-hosts on hold

Janos Benyovszki — Mon, 29 Jan 2024 10:06:36 GMT

@PassePartout can you provide a bit more details about how you are reproducing this? Do you have a full API request that you are making to create the meeting / webinar? How are users joining the meeting, do they use https://developer.webex.com/docs/api/v1/meetings/join-a-meeting ?
NOTE: if this is a generic query about joining a meeting and does not involve the APIs, I would recommend reaching out to our Generic Support / TAC here https://www.cisco.com/c/en/us/support/web/tsd-cisco-worldwide-contacts.html .

Re: Don't put co-hosts on hold

PassePartout — Wed, 31 Jan 2024 15:03:31 GMT

Here's my first problem:
When I create a meeting with the API and go to the Webex site to edit the newly created meeting, in the "advanced options" space, under "Co-organizers", I find the third item checked (See Photo). I would like the first item to be selected. How can I use the API to reproduce this setting?

A thousand thanks

Re: Don't put co-hosts on hold

sandiban — Thu, 01 Feb 2024 05:49:57 GMT

Thanks for your patience @PassePartout !
I think you can actually try to modify this setting from Webex Control Hub and could you kindly check this settings in your Webex Control Hub account please following the instruction - https://help.webex.com/en-us/article/2lrm1k/Allow-users-to-choose-an-alternate-host-or-a-cohost-on-your-Webex-site#task_w4t_y4g_14b

Kindly check if those toggles are disabled in your Webex Control Hub settings and if yes, then please enable those.
That should enable the first option under "Cohosts" in your Webex Site UserHub as well.

Let us know how it goes.
Regards!
Sandip

Re: Don't put co-hosts on hold

PassePartout — Thu, 01 Feb 2024 17:14:52 GMT

I solved the first problem by changing in the API call https://webexapis.com/v1/meetings:
the "allowAnyUserToBeCoHost" value from true to false

Now the second problem.

When I insert multiple invitations (Giuliano and Emiliano) with the API call https://webexapis.com/v1/meetingInvitees/bulkInsert
I find myself 2 co-hosts on the WEBEX site. So far everything is correct, see attachment 01.png

when both co-hosts try to log in (different browsers in anonymous mode) to start the meeting, (for both I use the "startLink" parameter obtained from the API call https://webexapis.com/v1/meetings/join)
both co-hosts can start the classroom
see attachment 02.png
Giuliano (right) enters first and Emiliano (left) enters second. While Giuliano immediately becomes "organizer", the second co-host who enters (Emiliano) must ask for permission because he is a user "non verificato" (user not verified).
see attachment 03.png

With roles reversed, if Emiliano enters first, then Giuliano must be authorized to enter.

I want both to be able to enter without asking anyone's permission

Re: Don't put co-hosts on hold

sandiban — Mon, 05 Feb 2024 08:13:46 GMT

Hi @PassePartout,
Before trying to answer the actual error, could you kindly check with both these 2 users - Giuliano and Emiliano, and asked them if they've received a Webex verification email to get their account verified.
There should a 6 digit token inside a verification email and they need to use it first to get their profile verified.

Once that verification part is solved, I don't think this error should come up again.
Currently it's showing because the User profile verification looks to be still not completed and that's possibly the root cause.

Kindly check on this part and confirm please.

Regards!
Sandip