> 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/zoom-workplace/zoom-phone/zoom-phone-local-survivability-field-guide/before-you-begin.md).

# 開始之前

ZPLS 入門。

在網路中部署 ZPLS 之前，有幾項與使用者存取、站點設計、信令與媒體，以及 PSTN 整合相關的考量，應在部署前先行考慮。以下各頁將探討這些情境。閱讀後，您可望了解高階技術設計的影響，以引導您的推行部署。

***

{% content-ref url="/pages/a725bd7c2dd4bcf64111686d7247190b6c546ece" %}
[將角色存取權授予使用者](/technical-library/zh-tw/zoom-workplace/zoom-phone/zoom-phone-local-survivability-field-guide/before-you-begin/grant-user-access-to-roles.md)
{% endcontent-ref %}

{% content-ref url="/pages/8f5edb3002f679ee134a78ec901c553db19c7e9d" %}
[硬體部署注意事項](/technical-library/zh-tw/zoom-workplace/zoom-phone/zoom-phone-local-survivability-field-guide/before-you-begin/hardware-deployment-considerations.md)
{% endcontent-ref %}

{% content-ref url="/pages/d23c1cc1fb72981dbf931b6499dbcd6f3263a637" %}
[PSTN 整合注意事項](/technical-library/zh-tw/zoom-workplace/zoom-phone/zoom-phone-local-survivability-field-guide/before-you-begin/pstn-integration-considerations.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/zoom-workplace/zoom-phone/zoom-phone-local-survivability-field-guide/before-you-begin.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.