> 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/zoom-workplace/zoom-phone/expert-insights/emergency-services-best-practices/locations.md). # Locations In Zoom Phone, a **Location** is the configuration entity where administrators define the network parameters used to correlate a user's physical position to a specific emergency address. A Location is analogoU.S.to an **ERL (Emergency Response Location)** — a term used in the broader emergency services industry to describe a distinct physical area that maps to a unique dispatchable address. Each Location contains two key elements: * **Network parameters** — the BSSID, IP address range, or LLDP switch MAC + port combination that identifies the physical area. During an emergency call, the system compares the user's detected network data against these configured parameters to determine which Location the user is in. * **Emergency address** — the dispatchable address assigned to that Location. Once the system matches the user's network data to a Location, the emergency address configured for that Location is used when the user places an emergency call. Where applicable, the Location is also where the **ELIN** is configured. For deployments outside the U.S./Canada (or BYOC deployments), each Location is assigned an ELIN whose address has been pre-registered with the carrier. When a user at that Location places an emergency call, the ELIN is used as the outbound caller ID, and the PSAP retrieves the pre-registered address from the carrier's database. Locations are organized hierarchically within Zoom Phone sites: * **Site** → contains one or more Locations * **Location** → represents a distinct physical area (e.g., a building) with its own set of network parameters and emergency address * **Sub-location** → a more granular division within a Location (e.g., a specific floor or wing) with its own dispatchable address and network identifiers Each Location and sub-location must have a sufficiently detailed emergency address to enable first responders to locate the caller. The level of granularity depends on the physical layout — a single-story building may require only one Location, while a multi-floor building should have sub-locations for each floor or wing. --- # 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/zoom-workplace/zoom-phone/expert-insights/emergency-services-best-practices/locations.md?ask=&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.