> 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/locations.md).

# 位置

在 Zoom Phone 中， **位置** 是管理员用于定义网络参数的配置实体，这些参数用于将用户的物理位置与特定紧急地址关联起来。位置类似于 **ERL（紧急响应位置）** ——这是更广泛的紧急服务行业中使用的术语，用于描述可映射到唯一可调度地址的特定物理区域。

每个位置包含两个关键要素：

* **网络参数** ——用于识别物理区域的 BSSID、IP 地址范围或 LLDP 交换机 MAC 地址 + 端口组合。在紧急呼叫期间，系统会将检测到的用户网络数据与已配置的参数进行比较，以确定用户所在的位置。
* **紧急地址** ——分配给该位置的可调度地址。系统将用户的网络数据与某个位置匹配后，用户拨打紧急呼叫时将使用为该位置配置的紧急地址。

在适用情况下，位置也是配置 **ELIN** 的地方。对于美国/加拿大以外的部署（或 BYOC 部署），每个位置都会分配一个 ELIN，其地址已预先向运营商登记。当该位置的用户拨打紧急呼叫时，ELIN 将用作外拨通话ID，PSAP 会从运营商的数据库中检索预先登记的地址。

位置在 Zoom Phone 站点内按层级组织：

* **站点** → 包含一个或多个位置
* **位置** → 表示具有自己的一组网络参数和紧急地址的特定物理区域（例如一栋建筑）
* **子位置** → 位置内更精细的划分（例如特定楼层或区域），具有自己的可调度地址和网络标识符

每个位置和子位置都必须有足够详细的紧急地址，以便急救人员找到呼叫者。所需的细化程度取决于物理布局：单层建筑可能只需一个位置，而多层建筑则应为每层或每个区域设置子位置。


---

# 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/locations.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.
