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

# Confirm the ZPLS Module is Operational

After initializing a ZPLS module, it is essential to confirm the assignment and that required services are running. To confirm the ZPLS modules’ status, perform the following steps:

1. Sign into the Zoom web portal.
2. In the [**Admin center**](https://zoom.com/account) navigation menu, click **Product configuration**, then **Phone system**, then [**Company Info**](https://zoom.com/pbx/page/telephone/settings#/settings).
3. **Locate the name of the site** you assigned the ZPLS module to and **click the site name**.
4. On the following screen, click the **Settings** tab displayed under the site’s name.

   <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. Locate the **Zoom Node** subsection, and click **Manage** next to *Local Survivability*.

   <div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/brfdE5trFmfNXhzKnQid/Unknown%20image" alt=""><figcaption></figcaption></figure></div>
6. On the following page, the status of the module should show as **Running**, with the module’s current version and IP address. If this screen displays, the module is successfully configured and associated with the Zoom Phone site.

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