> 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/expert-insights/emergency-services-best-practices/emergency-calling-number-capability.md).

# 紧急通话号码能力

并非所有电话号码在每个国家/地区都支持紧急通话。在配置紧急服务之前，请确认正在使用的号码——或正在购买的号码——具备拨打紧急呼叫的能力。

#### 尚未购买的号码

在购买电话号码之前，请确认它们在目标国家/地区支持紧急通话。号码功能因国家/地区和号码类型而异。请在以下网址查看各国家/地区号码的功能 <https://www.zoom.com/en/phone-number-requirements/>.

#### 已购买的号码

对于已经购买的号码，管理员可以在 Zoom 管理员门户中确认对紧急通话的支持。导航到 **号码管理 > 电话号码** 并找到相关号码。支持紧急通话的号码会显示一个 **SOS 图标** 位于号码下方的 **功能** 列中。如果未显示 SOS 图标，则该号码不支持紧急通话，不应将其作为紧急服务的依据。

#### 紧急呼叫可能无法路由时

以下配置或条件可能会阻止紧急呼叫路由到 PSAP。管理员应在部署过程中审查这些场景，以确保所有需要紧急通话功能的用户都已正确配置。

<table data-header-hidden="false" data-header-sticky><thead><tr><th>#</th><th>场景</th><th>呼叫失败原因</th></tr></thead><tbody><tr><td>1</td><td>管理员为没有本地电话号码的分机设置了“不要将紧急呼叫路由到 PSAP”，且未配置内部安全响应团队（ISRT）回退</td><td>策略明确阻止仅分机用户到达 PSAP，且没有可作为替代目的地的内部安全响应团队</td></tr><tr><td>2</td><td>用户级策略“紧急呼叫到 PSAP”已禁用</td><td>分机级紧急通话策略已关闭，阻止用户向 PSAP 拨打紧急呼叫</td></tr><tr><td>3</td><td>“路由到 PSAP”选项已禁用，且没有用于内部安全响应团队（ISRT）的呼叫队列成员</td><td>管理员已禁用“路由到 PSAP”选项，且未为 ISRT 配置呼叫队列成员。</td></tr><tr><td>3</td><td>站点没有专用紧急号码，且站点紧急池为空</td><td>没有可显示给 PSAP 的通话ID——系统若没有有效的外拨号码便无法发起呼叫</td></tr><tr><td>4</td><td>通话ID方法未在站点或账户设置中配置</td><td>未为紧急呼叫定义通话ID方法，因此系统不知道应使用哪个号码作为外拨通话ID</td></tr><tr><td>5</td><td>账户级紧急号码池功能已禁用，且站点级池为空</td><td>不存在全局回退路径——无法使用账户级池，且站点没有可用的本地池号码</td></tr><tr><td>6</td><td>美国/加拿大以外的站点，其紧急池中未配置 ELIN</td><td>在美国/加拿大以外，紧急呼叫必须使用 ELIN——没有 ELIN，系统就没有可显示给 PSAP 的通话ID</td></tr></tbody></table>

**建议：** 完成紧急服务配置后，请检查每个站点和用户策略，确认没有任何分机落入上述任一场景。请特别注意仅分机用户以及美国/加拿大以外的站点，因为这些是最常见的紧急呼叫路由可能被无意阻止的情况。


---

# 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/expert-insights/emergency-services-best-practices/emergency-calling-number-capability.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.