> 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/conference-room-connector-explainer.md).

# 會議室連接器

會議室連接器（CRC）可讓符合標準的 H.323/SIP 視訊會議裝置加入 Zoom Meetings 和 Webinars。CRC 包含 Enhanced API Connector，這是一款部署於您內部環境中的軟體應用程式，可啟用下列選用功能：

* 裝置管理、
* 行事曆整合，以及
* 透過向 Zoom 的 SIP Proxy 註冊來控制通話。

為您的 Zoom 帳戶取得一或多個 CRC 訂閱後，支援的視訊會議裝置即可使用 SIP 或 H.323 撥號通訊協定撥入 CRC 閘道，加入 Zoom Meetings 和 Webinars。將 Enhanced API Connector 部署至您的網路，並透過 Zoom 網路入口網站管理支援的視訊會議裝置後，貴組織即可為支援的 H.323/SIP 視訊會議裝置使用選用的行事曆整合和 SIP Proxy 註冊功能。

本文件將說明如何為您的 Zoom 帳戶啟用會議室連接器，並使用 SIP 和 H.323 撥號通訊協定，透過 CRC 閘道連線至 Zoom Meetings。文件也將涵蓋 Enhanced API Connector 的部署、CRC 選用功能的設定、授權考量、支援的裝置與軟體版本，以及使用 CRC 的其他技術需求。此外，也會介紹從內部部署的 H.323/SIP 作業轉換至會議室連接器時，常見的整合程序。

如需將會議室連接器產品整合至貴公司的詳細資訊，請聯絡您的客戶團隊。

{% content-ref url="/pages/c1f151b605ca9174cfd85ae77d8c0ee49f5ef523" %}
[先決條件與注意事項](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/conference-room-connector-explainer/prerequisites-and-considerations.md)
{% endcontent-ref %}

{% content-ref url="/pages/7b4c26566710cde560e607b9fb086afe281b7d8b" %}
[網頁控制與撥號程序](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/conference-room-connector-explainer/web-controls-and-dialing-procedures.md)
{% endcontent-ref %}

{% content-ref url="/pages/41181866d2f0570d60161b639ef2b8b9c61d8d56" %}
[其他會議室連接器功能](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/conference-room-connector-explainer/additional-conference-room-connector-features.md)
{% endcontent-ref %}

{% content-ref url="/pages/71e1f42f8a79456c14fc1bcf1469b3bb4be06f16" %}
[增強型 API 連接器部署與功能](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/conference-room-connector-explainer/enhanced-api-connector-deployment-and-functionality.md)
{% endcontent-ref %}

{% content-ref url="/pages/ce633cc3bdad01bb54fc350aff8574a4aeae9c20" %}
[常見整合情境](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/conference-room-connector-explainer/common-integration-scenarios.md)
{% endcontent-ref %}

{% content-ref url="/pages/19aa7c7dcbc3927b6f1ecc6889353eded5fcce58" %}
[會議室連接器信號流程](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/conference-room-connector-explainer/conference-room-connector-signal-flow.md)
{% endcontent-ref %}

{% content-ref url="/pages/e010585803236ba3b92000c5a3b268cc7849b5db" %}
[Zoom 增強型 API 連接器（Cisco H.323/SIP 裝置設定）](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/conference-room-connector-explainer/zoom-enhanced-api-connector-cisco-h.323-sip-device-settings.md)
{% endcontent-ref %}


---

# 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/conference-room-connector-explainer.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.
