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

# (可选) 在生存性事件 & 活动 &直播期间启用呼叫转移

如 [前面所述](#_iyu0s6qx0yh)，为了在常规商业版操作期间保留 Zoom Phone 云路由，必须禁用用于存活性的呼叫转移。不过，在发生存活性事件 & 活动 &直播时，必须使用可用的互联网连接从 Zoom Web门户 启用呼叫转移。启用后，拨打到 Zoom Phone 已注册号码的呼叫将通过 PSTN 重新路由到本地 SBC。要启用呼叫转移，请执行以下步骤：

1. 登录 Zoom Web门户。
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/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.