E911 Locations & Network¶
Workbook: RX3 Zoom Phone E911 Location and Network Capture · Tabs: Emergency Locations, Network Subnets, Network Identifiers, 911 Notifications
You columns are yours to complete. RX3 columns we complete. An asterisk marks a required field.
Before you start¶
- What drives this workbook
- Two federal requirements shape the build. Kari's Law requires that 911 be dialable directly with no prefix, and that an on-site notification reach somewhere a person is likely to see or hear it. RAY BAUM's Act requires that a dispatchable location - street address plus the detail needed to find the caller inside the building - be conveyed with the call. Confirm your specific obligations with counsel; this workbook captures what the platform needs to meet them.
- How locations are matched
- Zoom Phone determines an on-network caller's location from network identifiers. A subnet is the usual identifier, which is why the Network Subnets tab exists and why it keys directly to a location row. Other options are based on the switch or access point the user is connected to.
- Off-network callers are prompted to confirm a personal location instead.
- The most common blocker
- A single voice VLAN spanning several buildings or floors cannot produce a dispatchable location, because every caller on it looks identical to the platform. If that is the current design, note it on the Network Subnets tab - per-switch or per-AP identifiers become part of the project scope, and that is better discovered now than during acceptance testing.
- Fixed analog endpoints
- Elevator phones, area-of-refuge stations, and courtesy phones have no client and cannot report a location. Each needs its own location row with Location Type set to Fixed Analog Endpoint, cross-referenced to the Analog Ports tab of the device capture workbook.
- Column ownership
- AMBER headers are completed by the customer. NAVY headers are completed by RX3. An asterisk (*) marks a required column.
- Testing
- Every device on the Zoom Phone platform can call 933 to hear the location read back to the caller. Ensure that every location/building/subnet has a 933 test call made to ensure accurate emergency response location.
Do not dial 911 unless there is an actual emergency
Dialing 911 to test emergency services may be against local laws and regulations. Always use 933 to test.
Emergency Locations tab¶
One row per dispatchable location. A dispatchable location is a street address PLUS enough detail for responders to find the caller inside the building - typically building, floor, and wing or room range. For a multi-story campus that means one row per floor per building, not one row per campus.
| Field | Filled in by | Allowed values | Example |
|---|---|---|---|
| Location Name * | You | — | Science Bldg - Floor 2 East |
| Site * | You | — | Main Campus |
| Location Type * | You | Company Location · Personal Location · Fixed Analog Endpoint |
Company Location |
| Address Line 1 * | You | — | 1060 N West Rd |
| Address Line 2 | You | — | Second Floor East |
| City * | You | — | Colorado Springs |
| State * | You | — | CO |
| ZIP * | You | — | 80905 |
| Address Validated | RX3 | Pending · Validated · Failed · Corrected |
Pending |
| Validation Notes | RX3 | — | — |
| Notes | You | — | Floor-level location - one per floor per building |
Network Subnets tab¶
One row per subnet that phones or softphones can appear on. Location Name must match the Emergency Locations tab exactly. Subnets are how Zoom Phone determines where an on-network caller physically is, so a subnet spanning three buildings cannot produce a dispatchable location - if that is the current design, flag it in Notes and expect a network change to be part of the project.
| Field | Filled in by | Allowed values | Example |
|---|---|---|---|
| Location Name * | You | — | Science Bldg - Floor 2 East |
| Network Address * | You | — | 10.24.20.0 |
| Prefix Length * | You | — | 24 |
| Subnet Mask | You | — | 255.255.255.0 |
| CIDR * | You | — | 10.24.20.0/24 |
| VLAN ID | You | — | 220 |
| VLAN Name | You | — | VOICE-SCI-2 |
| Purpose * | You | Voice · Data · Wireless · Guest · Management · Converged Voice and Data |
Voice |
| Site * | You | — | Main Campus |
| Building * | You | — | Science Building |
| Floors Served * | You | — | 2 |
| DHCP Scope Name | You | — | SCI-VOICE-F2 |
| Public Egress IP * | You | — | 198.51.100.14 |
| Wireless * | You | Y · N |
N |
| Overlaps Another Location | RX3 | Y · N · Under Review |
— |
| Validated | RX3 | Pending · Validated · Failed |
Pending |
| Notes | You | — | Wired voice VLAN - one VLAN per floor per building |
911 Notifications tab¶
Who is alerted when someone on this tenant dials 911.
| Field | Filled in by | Allowed values | Example |
|---|---|---|---|
| Site * | You | — | Main Campus |
| Recipient Name * | You | — | Campus Safety Desk |
| Role * | You | — | 24x7 security dispatch |
| Notification Method * | You | Email · SMS · Email and SMS · Zoom Chat · Call |
Email and SMS |
| Email Address | You | — | safety@customer.edu |
| Phone / SMS Number | You | — | +17205551911 |
| Coverage Hours * | You | — | 24x7 |
| Escalation Order * | You | — | 1 |
| Configured | RX3 | Not Started · Configured · Tested |
Not Started |
| Notes | You | — | Staffed desk - primary recipient for all 911 events |