> 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/gao-ji-qi-ye-fu-wu/conference-room-connector-explainer.md).

# 会议室连接器

会议室连接器 (CRC) 允许基于标准的 H.323/SIP 视频会议设备加入 Zoom Meetings 和网络研讨会。CRC 包含增强型 API 连接器，这是一个部署在您本地的应用程序，可启用可选功能，包括：

* 设备管理，
* 日历集成，以及
* 通过注册到 Zoom 的 SIP 代理进行呼叫控制。

通过为您的 Zoom 账户获取一个或多个 CRC 订阅，支持的视频会议设备可使用 SIP 或 H.323 拨号协议拨入 CRC 网关，从而加入 Zoom Meetings 和网络研讨会。通过将增强型 API 连接器部署到您的网络中，并在 Zoom Web门户中管理支持的视频会议设备，您的组织可以针对支持的 H.323/SIP 视频会议设备使用可选的日历集成和 SIP 代理注册功能。

本文档将概述为您的 Zoom 账户激活会议室连接器以及使用 SIP 和 H.323 拨号协议通过 CRC 网关连接至 Zoom Meetings 的流程。还将涵盖增强型 API 连接器的部署、可选 CRC 功能的配置、许可注意事项、支持的设备和软件版本，以及使用 CRC 的其他技术要求。本文将介绍从本地 H.323/SIP 运营过渡到会议室连接器的组织常用的集成流程。

如需了解有关将会议室连接器产品集成到您的商业版中的更多信息，请联系您的账户团队。

{% content-ref url="/pages/4798d0e35a3c8c14f2b9736cd4945e93a103578d" %}
[前提条件和注意事项](/technical-library/zh/gao-ji-qi-ye-fu-wu/conference-room-connector-explainer/prerequisites-and-considerations.md)
{% endcontent-ref %}

{% content-ref url="/pages/8a626e05d7a811ac7a882bf6e04f91b78873b572" %}
[网页控件和拨号流程](/technical-library/zh/gao-ji-qi-ye-fu-wu/conference-room-connector-explainer/web-controls-and-dialing-procedures.md)
{% endcontent-ref %}

{% content-ref url="/pages/df4e69712abdb5878de46c9bf964cc8262596e6a" %}
[会议室连接器的其他功能](/technical-library/zh/gao-ji-qi-ye-fu-wu/conference-room-connector-explainer/additional-conference-room-connector-features.md)
{% endcontent-ref %}

{% content-ref url="/pages/2bb20522e8ab2f85f4fdfa5d07ff92b867860891" %}
[增强型 API 连接器部署和功能](/technical-library/zh/gao-ji-qi-ye-fu-wu/conference-room-connector-explainer/enhanced-api-connector-deployment-and-functionality.md)
{% endcontent-ref %}

{% content-ref url="/pages/e87c5699b0ec37f847e17e3691a06b6c9163584d" %}
[常见集成场景](/technical-library/zh/gao-ji-qi-ye-fu-wu/conference-room-connector-explainer/common-integration-scenarios.md)
{% endcontent-ref %}

{% content-ref url="/pages/6f2aeb885365bac3adc1c714e832dc071175f7f7" %}
[会议室连接器信号流](/technical-library/zh/gao-ji-qi-ye-fu-wu/conference-room-connector-explainer/conference-room-connector-signal-flow.md)
{% endcontent-ref %}

{% content-ref url="/pages/6b3f9c3498af0df469349d56dff5f57fb2c70b06" %}
[Zoom 增强型 API 连接器（Cisco H.323/SIP 设备设置）](/technical-library/zh/gao-ji-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/gao-ji-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.