> 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/u.s.-canada-pidf-lo-address-delivery.md).

# 美国/加拿大—PIDF-LO 地址传递

在美国和加拿大，当 Zoom 服务处理紧急呼叫时，检测到的地址会使用 PIDF-LO 协议直接嵌入到呼叫信令中。这与通话ID无关。

**美国/加拿大流程：** 用户拨打 911 **→** Zoom 通过网络数据检测位置 **→** 可调度地址通过 PIDF-LO 嵌入到呼叫中 **→** PSAP 直接接收地址：无需数据库查询。

#### 主要优势

* **无需 ELIN** — 地址随呼叫信令传输，而不是绑定到电话号码
* **实时地址更新** — 用户和管理员可通过 Zoom 门户更新地址；无需更新运营商数据库
* **仅分机用户得到全面支持** — 他们将使用 Emergency Number Pool 作为通话ID，但检测到的可调度地址仍会通过 PIDF-LO 直接发送
* **个人位置不限数量** — 远程工作者可以按需创建任意数量，并在近乎实时内启用

#### 美国/加拿大的 BYOC 客户

如果您将 BYOC 用于日常呼叫，Zoom 将提供紧急呼叫路由（无需额外费用）。强烈建议这样做，因为它可提供上述所有 PIDF-LO 优势。普通呼叫继续通过 BYOC 运营商；只有紧急呼叫经由 Zoom 路由。

#### 当没有位置匹配时的回退方案（美国/加拿大）

如果未找到网络匹配且设备没有 GPS：

* 如果用户之前已确认个人地址，则上报该地址
* 否则，位置将报告为“Unknown”，并且呼叫将路由到一个全国性清算中心，该中心会在连接到正确的 PSAP 之前通过口头方式确认通话者的位置。


---

# 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/u.s.-canada-pidf-lo-address-delivery.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.