> 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/optional-tasks/optional-enabling-call-forwarding-during-a-survivability-event.md).

# （選用）在生存能力事件期間啟用來電轉接

如 [先前所述](#_iyu0s6qx0yh)，為保留 Zoom Phone 雲端路由，例行營運期間必須停用用於存活能力的通話轉接。不過，發生存活能力事件時，必須使用可正常運作的網際網路連線，從網頁入口網站啟用通話轉接。啟用後，撥打至已註冊 Zoom Phone 的號碼時，通話會經由 PSTN 重新路由至內部部署的 SBC。若要啟用通話轉接，請按照下列步驟操作：

1. 登入 Zoom 網頁入口網站。
2. 在 [**管理中心**](https://zoom.com/account) 導覽功能表中，按一下 **產品設定**，然後按一下 **電話系統**，然後按一下 [**公司資訊**](https://zoom.com/pbx/page/telephone/settings#/settings).
3. **從清單中選取網站名稱** （若為單一網站設定，則按一下 **帳戶設定** ）。
4. 選取該網站的 **設定** 索引標籤。
5. 在下一個畫面中，找到 **Zoom Node** 子區段，以及 **本機存活能力通話轉接**設定。按一下 **管理** 以載入新頁面。

   <div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/tY9z4eP6l2Sy0kWDPqPb/Unknown%20image" alt="" width="563"><figcaption></figcaption></figure></div>
6. 在下一頁中，選取個別號碼，或勾選最上方的核取方塊以選取頁面上顯示的所有號碼，然後按一下 **啟用轉接**.

   <div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/B8hoHqdwxt4hKvPmA03D/Unknown%20image" alt=""><figcaption></figcaption></figure></div>
7. 畫面會出現快顯視窗，確認是否啟用通話轉接。按一下 **啟用** 以確認。
8. 來電轉接現已針對所選使用者啟用。視需要對適用的多個使用者或頁面重複此程序。
9. 存活能力事件結束後，重複此流程直到步驟 6。此時改為按一下 **停用轉接** 並在出現提示時確認，以移除所選號碼的通話轉接。


---

# 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/optional-tasks/optional-enabling-call-forwarding-during-a-survivability-event.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.
