> 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/zoom-workplace/zoom-phone/zoom-phone-local-survivability-field-guide/confirm-the-zpls-module-is-operational.md).

# 确认 ZPLS 模块已正常运行

初始化 ZPLS 模块后，务必确认分配情况以及所需服务正在运行。要确认 ZPLS 模块的状态，请执行以下步骤：

1. 登录 Zoom Web门户。
2. 在 [**管理员中心**](https://zoom.com/account) 导航菜单中，单击 **产品配置**，然后 **电话系统**，然后 [**公司信息**](https://zoom.com/pbx/page/telephone/settings#/settings).
3. **找到站点名称** 您将 ZPLS 模块分配到的 **点击站点名称**.
4. 在以下屏幕上，点击 **设置** 选项卡，该选项卡显示在站点名称下方。

   <div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/rOqqyIkgjxX0yrkq0rKR/Unknown%20image" alt="" width="563"><figcaption></figcaption></figure></div>
5. 找到 **Zoom Node** 小节，然后单击 **管理** 旁边的 *本地容灾*.

   <div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/brfdE5trFmfNXhzKnQid/Unknown%20image" alt=""><figcaption></figcaption></figure></div>
6. 在下一页中，模块的状态应显示为 **运行中**，并显示模块的当前版本和 IP 地址。如果显示此屏幕，则表示该模块已成功配置并与 Zoom Phone 站点关联。

   <div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/A6VX3uUdxjZQlpxng5SL/Unknown%20image" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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/zoom-workplace/zoom-phone/zoom-phone-local-survivability-field-guide/confirm-the-zpls-module-is-operational.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.