> ## 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.

# Soft SIP / H.323 endpoint

> An Android app that turns large displays, all-in-one units, and boxes into standard SIP / H.323 video endpoints: point-to-point calls, registration to a SIP server or gatekeeper, entering our meetings, screen sharing, and whiteboard. Covers features, setup, and how to get it.

The **Soft SIP / H.323 endpoint** is an Android app (titled "会议室连接器" (*Room Connector*) inside the app). Install it on a meeting room's Android large display, all-in-one unit, or set-top box, and that device becomes a
**standard SIP / H.323 video conferencing endpoint**—without buying a separate hardware endpoint, it can call and be called by endpoints and
MCUs from brands such as Huawei and Kedacom, and enter meetings on our platform.

![Soft endpoint home](https://mintcdn.com/freewind/EF59QLb6N-9opFfC/zh/product/terminals/images/softsip-home.jpg?fit=max\&auto=format\&n=EF59QLb6N-9opFfC\&q=85\&s=707e70ed88202d9af894df79cfd895e8)

***

## Use cases

* The meeting room already has an Android large display / all-in-one unit and you want to connect it to an existing SIP / H.323 video conferencing system at low cost
* A video wall or command-center display needs to join a higher-level organization's video conference as an endpoint
* Use it with our meeting platform: register to the device gateway and dial the meeting ID to enter; see [Room Connector](https://docs.stmlink.com/en/product/device-access/sip-h323.md)

***

## Main features

| Feature | Description |
| - | - |
| **Point-to-point calls** | Choose SIP or H.323 and enter the other endpoint's IP, E.164 number, or name to call; audio + video or audio only |
| **Answer incoming calls** | Answer / decline from the incoming-call pop-up; **auto-answer** is available for unattended large displays |
| **Registration** | Register to a SIP server or H.323 gatekeeper, with H.460 NAT traversal |
| **In-meeting controls** | Mute, video on/off, switch camera, mirror video, speaker / equal-split layouts |
| **Screen sharing** | Start and receive sharing (available on H.323 calls) |
| **Whiteboard** | Start a whiteboard during the meeting or join with a service code; pen, text, shapes, undo, and save |
| **Call history** | One-tap redial |

**In-meeting view**:

![In-meeting view](https://mintcdn.com/freewind/EF59QLb6N-9opFfC/zh/product/terminals/images/softsip-meeting.jpg?fit=max\&auto=format\&n=EF59QLb6N-9opFfC\&q=85\&s=9189c63bfcc829f1981b378d647fad48)

**Whiteboard**:

![Whiteboard](https://mintcdn.com/freewind/EF59QLb6N-9opFfC/zh/product/terminals/images/softsip-whiteboard.png?fit=max\&auto=format\&n=EF59QLb6N-9opFfC\&q=85\&s=3d525fc9e0f1e71fd7dd2115b3753896)

***

## How to use it

1. Install the app and complete **software activation** (we provide the activation details)

2. Configure **Settings** as needed:

   | Settings page | Contents |
   | - | - |
   | SIP service | Whether to register, server address, port, account, password |
   | 323 service | Gatekeeper address, E.164 number, H.460 NAT traversal, port |
   | Whiteboard service | Whiteboard server address |
   | Network | Local network information |
   | General | Display name, auto-answer, get logs |

   ![SIP service settings](https://mintcdn.com/freewind/EF59QLb6N-9opFfC/zh/product/terminals/images/softsip-settings.png?fit=max\&auto=format\&n=EF59QLb6N-9opFfC\&q=85\&s=70f6c3180ab2531b1362db5617b9cbdb)

3. Go back to the home page, choose a protocol, enter the other party's address, and tap **Call**; or wait for an incoming call

To enter meetings on our platform, point the SIP / 323 service at the device gateway (create the account in the admin console), then dial the **meeting ID** on the home page.
The steps are exactly the same as for [hardware endpoints](https://docs.stmlink.com/en/product/device-access/sip-h323.md).

***

## Get it

The soft endpoint is delivered per project. **For the installation package and activation, [contact us](https://www.stmlink.com/en/contact)**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.