> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/zoom-node/zoom-conference-room-connector-hybrid.md).

# Zoom 會議室連接器混合式

#### <mark style="color:藍色;">Zoom 會議室連接器混合式：會議室的混合式會議</mark> <a href="#vwn78dbs8d9m" id="vwn78dbs8d9m"></a>

Zoom 會議室連接器混合式與 Zoom 的 [會議混合式](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/zoom-node/zoom-meetings-hybrid.md) 解決方案類似，支援混合式和私人會議，但不支援 Zoom Workplace 應用程式，而是支援舊版 SIP 和 H.323 會議室系統。

使用此產品，多間會議室可連線至部署在本機的混合式 Zoom Node 設備，該設備可同時接收、多工處理並重新分發往返 Zoom 雲端的媒體串流；預設情況下，每個模組最多支援 8 間會議室同時進行高畫質會議。會議室連接器混合式模組也支援其他重要的會議體驗功能，包括會議中聊天、表情回應、版面配置控制，以及一鍵加入功能。

下圖展示會議室連接器混合式服務與會議混合式服務整合的範例，以及其他會議室連接器混合式功能，例如用於整合行事曆的 API 連接器混合式。

<figure><img src="https://2668295848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2Fgit-blob-f1ba193991649171c56f065cc7909c4ed5ec9213%2F10.png?alt=media" alt="Diagram depicting the Conference Room Connector Hybrid service connecting with the Zoom Cloud and Meetings Hybrid module" width="563"><figcaption><p>示意圖：會議室連接器混合式服務與 Zoom 雲端及會議混合式模組連線</p></figcaption></figure>

{% hint style="info" %}
**注意**

會議室連接器混合式不需要 Zoom 會議混合式；此處僅為示意用途而納入。
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/zoom-node/zoom-conference-room-connector-hybrid.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
