Skip to main content

Overview

APIs with the admin prefix require the host (.host) or co-host (.coHost) role; regular members who call them get a permission error from the server. Check before calling:
Once a control action takes effect, all members receive the corresponding room / member state event. You don’t need to change state manually on the initiating side; just refresh in the event handlers.

Room-level controls

The two switches of mute all

micDisabled and selfUnmuteMicDisabled mean different things, and together they determine the members’ experience:
When “mute all” is turned on, the microphones of non-host members are turned off automatically. Whether members can then turn their microphones back on themselves depends on selfUnmuteMicDisabled. The camera follows the same rules.

End the meeting

All members are disconnected, and the member side learns about it through meeting(_:didDisconnect:). The initiator also needs to take its own UI back out of the meeting.

Member management

The corresponding member state events: userNameDidChange, userRoleDidChange, userChatDisabledDidChange, userDrawDisabledDidChange (since 1.3.6). A removed member learns about it through didDisconnect. Read the current drawing permission from MeetingUserInfo.drawDisabled; when it changes, you receive:
For turning off a member’s microphone / camera and asking members to turn them on, see Raise hand and turn-on requests.

Change your own in-meeting display name

This action doesn’t require the host role:

Invitee management

Update the invitee list

Find out who hasn’t entered yet

Returns [NoEnterUserInfo], including nickname, phone number, avatar, role, and more.

Remind invitees to enter

When useSms is true, an SMS reminder is sent as well.

In-meeting calls

If the called users have enabled out-of-meeting messages, they receive the imCallCalling event; see Out-of-meeting messages.

Online member list


Invite devices into the meeting

Meetings support bringing external devices into the meeting, such as SIP, H.323, GB28181, RTSP / RTMP pull streams, and file playback. First, query the available devices:
Then send the invitation:
For AgentType values, see Types. Read a device’s current busy / idle status from AgentInfo.status.