> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stmlink.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> 对外开放的服务端接口有两组前缀，都用同一套鉴权：`/server/v1/...`（SRTC 与 SMeeting 的主接口）和 `/stm/srvapi/v1/...`（SMeeting 的用户体系，服务端极简对接会用到）。鉴权是 app_id + nonce + timestamp + signature 四个请求头，用 app_key 做 HMAC-SHA256 签名，只能从业务方自己的后端调用。除这两组前缀外的接口均为内部接口，不要建议客户调用。 Public server APIs use two path prefixes with the same authentication: `/server/v1/...` (the main APIs of both SRTC and SMeeting) and `/stm/srvapi/v1/...` (the SMeeting user system, used by server-side low-code integration). Authenticate with four request headers, app_id + nonce + timestamp + signature, where signature is HMAC-SHA256 keyed with app_key; call these APIs only from the customer's own backend. Any other path is internal: never suggest calling it.
> app_key 是服务端密钥，绝不能出现在客户端代码、前端配置或移动 App 里。客户端加入频道用的 token 必须由业务方后端签发后下发（SRTC 走 `/server/v1/channel/grant`，SMeeting 走 `/stm/srvapi/v1/member/grant`）。 app_key is a server-side secret and must never appear in client code, frontend config, or a mobile app. The token a client uses to join must be issued by the customer's backend and passed down to the client (SRTC: `/server/v1/channel/grant`; SMeeting: `/stm/srvapi/v1/member/grant`).
> SRTC 与 SMeeting 是上下两层不同的产品，术语不通用：SRTC 是音视频底座，说「频道 channel」「加入 / 退出」；SMeeting 建在 SRTC 之上，说「房间 room」「会议 meeting」「进入 / 退出」。回答时按用户所在的层用对应术语，不要把「房间」「会议」安到 SRTC 的接口上，也不要用「频道」「加入 / 离开」描述 SMeeting 的概念（接口标识符原样保留）。 SRTC and SMeeting are two separate layers with different terminology. SRTC is the audio/video foundation: it has channels, and users join and leave a channel. SMeeting is built on top of SRTC: it has rooms and meetings, and members enter and exit a meeting. Answer in the terms of the layer the user is working with: never apply "room" or "meeting" to SRTC APIs, and never describe SMeeting concepts in prose with "channel", "join", or "leave" (API identifiers such as `force_join` keep their literal names).
> 同一能力在各端 SDK 里的包名、类名、方法名并不相同。写示例代码时请使用文档中该端自己的 API，不要把一个端的写法套到另一个端上。苹果平台每个产品都有两套 SDK（Swift 原生与 Objective-C），两套 API 不能混用。 Package, class, and method names differ between platform SDKs for the same capability. In sample code, use the API documented for that platform; never carry one platform's code over to another. On Apple platforms each product ships two SDKs (native Swift and Objective-C) whose APIs must not be mixed.

# RollCallManager

> In-meeting roll call manager for the SMeeting Android SDK: start and end roll calls, call and confirm members as the host, answer as a member, and query or export details. Read this when building roll call features.

`RollCallManager` is obtained through `MeetingEngine.rollCallManager`, and all operations are bound to the Engine's current single meeting.

## Usage notes

* This property is a stable facade that you can keep before the meeting; when you are not in a meeting, all asynchronous methods return `MeetingErrorCode.SESSION_NOT_ACTIVE`.

* The `id` in the list and in the details mean different things: `RollCallBean.id` in the list is the roll call activity ID, while `RollCallUserBean.id` of a user in the details is the roll call user ID used for subsequent calls and answers.

* When `allMember` is `false`, you must provide `members`; each member item contains a UID and a nickname.

* Result callbacks stay on the network thread they come from; switch to the main thread before updating the UI.

## Methods

### listRollCall(page, perPage, callback)

```kotlin theme={null}
fun listRollCall(
    page: Int,
    perPage: Int,
    callback: MeetingValueResultCallback<MeetingPage<RollCallBean>>
)
```

Description: Queries the current meeting's roll call activities page by page.

Parameters:

| Parameter | Description |
| - | - |
| `page` | Page number, starting from `1`. |
| `perPage` | Maximum number of items per page. |
| `callback` | Callback that returns the paginated roll call activities on success. |

Returns: None (the asynchronous result is delivered through the callback).

### startRollCall(method, allMember, members, callback)

```kotlin theme={null}
fun startRollCall(
    method: RollCallMethod,
    allMember: Boolean,
    members: List<MemberRequestBean>?,
    callback: MeetingValueResultCallback<String>
)
```

Description: Creates and starts a round of roll call.

Parameters:

| Parameter | Description |
| - | - |
| `method` | Automatic or manual roll call method. |
| `allMember` | `true` calls the roll for all members; `false` calls only `members`. |
| `members` | List of specified members; required when `allMember=false`. |
| `callback` | Result callback that returns the new roll call activity ID on success. |

Returns: None (the asynchronous result is delivered through the callback).

### stopRollCall(rollCallId, callback)

```kotlin theme={null}
fun stopRollCall(rollCallId: String, callback: MeetingResultCallback)
```

Description: Ends the specified roll call activity.

Parameters:

| Parameter | Description |
| - | - |
| `rollCallId` | Roll call activity ID. |
| `callback` | End result callback. |

Returns: None (the asynchronous result is delivered through the callback).

### rollCallNamed(rollCallUserId, callback)

```kotlin theme={null}
fun rollCallNamed(
    rollCallUserId: String,
    callback: MeetingResultCallback
)
```

Description: The host calls the specified user in the roll call details.

Parameters:

| Parameter | Description |
| - | - |
| `rollCallUserId` | `RollCallUserBean.id`, not the meeting member UID. |
| `callback` | Call result callback. |

Returns: None (the asynchronous result is delivered through the callback).

### adminRollCallAnswer(rollCallUserId, clear, callback)

```kotlin theme={null}
fun adminRollCallAnswer(
    rollCallUserId: String,
    clear: Boolean,
    callback: MeetingResultCallback
)
```

Description: The host confirms or clears the specified user's roll call answer record.

Parameters:

| Parameter | Description |
| - | - |
| `rollCallUserId` | `RollCallUserBean.id`. |
| `clear` | `true` clears the existing answer record; `false` confirms the answer. |
| `callback` | Operation result callback. |

Returns: None (the asynchronous result is delivered through the callback).

### detailRollCall(rollCallId, callback)

```kotlin theme={null}
fun detailRollCall(
    rollCallId: String,
    callback: MeetingValueResultCallback<RollCallDetailBean>
)
```

Description: Queries the details of the specified roll call activity and the members' answer status.

Parameters:

| Parameter | Description |
| - | - |
| `rollCallId` | Roll call activity ID. |
| `callback` | Result callback that returns `RollCallDetailBean` on success. |

Returns: None (the asynchronous result is delivered through the callback).

### exportRollCallDetail(rollCallId, callback)

```kotlin theme={null}
fun exportRollCallDetail(
    rollCallId: String,
    callback: MeetingValueResultCallback<String>
)
```

Description: Requests an export of the specified roll call activity's details.

Parameters:

| Parameter | Description |
| - | - |
| `rollCallId` | Roll call activity ID. |
| `callback` | Callback that returns the server's export result string on success. |

Returns: None (the asynchronous result is delivered through the callback).

### userRollCallAnswer(rollCallUserId, callback)

```kotlin theme={null}
fun userRollCallAnswer(
    rollCallUserId: String,
    callback: MeetingResultCallback
)
```

Description: The current user answers the roll call.

Parameters:

| Parameter | Description |
| - | - |
| `rollCallUserId` | The current user's `RollCallUserBean.id` in the roll call details. |
| `callback` | Answer result callback. |

Returns: None (the asynchronous result is delivered through the callback).