Dispatch Locations Module Documentation
Table of Contents
Section titled “Table of Contents”- Navigation & Access
- Screenshots & Visual Interface
- Module Overview (Technical)
- Module Overview (Commercial/Business)
- Module Overview (End User/Administrator)
- Configuration Fields Reference
- Address Components
- Common Scenarios & Examples
- Limitations & Important Notes
- Model Context Protocol (MCP) AI Integration
- Troubleshooting Tips
- Glossary
Navigation & Access
Section titled “Navigation & Access”To access the Dispatch Locations module:
- Log in to the Ring2All Web Portal (
https://<domain-or-ip>/login). - In the left navigation sidebar, expand PBX Engine.
- Under Emergency Calls, click Dispatchable Locations (
/pbx/emergency/locations). - To add a new dispatchable address record, click the + Add Location button (
/pbx/emergency/locations/new).
Screenshots & Visual Interface
Section titled “Screenshots & Visual Interface”Dispatchable Locations Directory
Section titled “Dispatchable Locations Directory”Central repository of physical locations, showing registered premises, location code, formatted street addresses, city, state, postal code, and emergency validation status.

Dispatchable Location Definition & RAY BAUM’S Compliance Form
Section titled “Dispatchable Location Definition & RAY BAUM’S Compliance Form”Granular physical location form allowing configuration of street, building, floor, suite/room, wing, Emergency Location Identification Number (ELIN), and on-site contact coordinates.

1. Module Overview (Technical)
Section titled “1. Module Overview (Technical)”What Are Dispatch Locations?
Section titled “What Are Dispatch Locations?”Dispatch Locations are dispatchable address records that provide precise physical location information for E911 compliance. They support RAY BAUM’s Act requirements by associating detailed location data (street, building, floor, room) with extensions, devices, or trunks.
Architecture
Section titled “Architecture”┌─────────────────────────────────────────────────────────────────┐│ Dispatch Locations System │├─────────────────────────────────────────────────────────────────┤│ ││ ┌──────────────────────────────────────────────────────────┐ ││ │ Dispatch Location Record │ ││ │ │ ││ │ Location Name: Main Building - 3rd Floor East │ ││ │ │ ││ │ Assignment: │ ││ │ ├─ Type: Extension │ ││ │ └─ Extension: 1001 │ ││ │ │ ││ │ Address: │ ││ │ ├─ Street: 123 Main Street, Suite 300 │ ││ │ ├─ City: Miami │ ││ │ ├─ State: FL │ ││ │ └─ ZIP: 33131 │ ││ │ │ ││ │ Building Details: │ ││ │ ├─ Building: Main Building │ ││ │ ├─ Floor: 3 │ ││ │ ├─ Room: 310 │ ││ │ └─ Wing: East │ ││ │ │ ││ │ Emergency: │ ││ │ ├─ ELIN: +13055551234 │ ││ │ └─ Contact: John Smith (305) 555-9999 │ ││ │ │ ││ └──────────────────────────────────────────────────────────┘ ││ │ ││ ▼ Used during 911 calls ││ ┌──────────────────────────────────────────────────────────┐ ││ │ Emergency Call Routing │ ││ │ │ ││ │ Extension 1001 dials 911 │ ││ │ → Lookup dispatch location by extension │ ││ │ → Override Caller ID with ELIN │ ││ │ → Include dispatchable location in call │ ││ │ → Route to PSAP │ ││ │ │ ││ └──────────────────────────────────────────────────────────┘ ││ │└─────────────────────────────────────────────────────────────────┘2. Module Overview (Commercial/Business)
Section titled “2. Module Overview (Commercial/Business)”Business Value
Section titled “Business Value”Dispatch Locations provides E911 location compliance:
| Without Dispatch Locations | With Dispatch Locations |
|---|---|
| Generic address | Building/floor/room |
| Delayed response | Pinpoint accuracy |
| Compliance risk | RAY BAUM’s compliant |
| Manual updates | Centralized management |
Regulatory Compliance
Section titled “Regulatory Compliance”| Regulation | Requirement | Solution |
|---|---|---|
| RAY BAUM’s Act | Dispatchable location | Floor/room/wing data |
| NG911 | Precise coordinates | Lat/long support |
| Kari’s Law | On-site notification | Emergency contact |
Use Cases
Section titled “Use Cases”-
Multi-Floor Buildings
- Per-floor location records
- Room-level precision
-
Campus Environments
- Multiple buildings
- Building-specific ELINs
-
Remote Workers
- Home office addresses
- Per-device locations
-
Multi-Tenant Systems
- Tenant-specific locations
- Shared building compliance
Feature Highlights
Section titled “Feature Highlights”| Feature | Benefit |
|---|---|
| Full Address | Complete street address |
| Building Details | Floor, room, wing |
| ELIN Support | Location-specific callback |
| GPS Coordinates | Precise positioning |
| Assignment Types | Extension, device, trunk |
| Special Instructions | First responder notes |
3. Module Overview (End User/Administrator)
Section titled “3. Module Overview (End User/Administrator)”What Can You Do?
Section titled “What Can You Do?”- Create location records with full addresses
- Add building/floor/room details
- Assign locations to extensions or devices
- Configure ELIN numbers
- Add emergency contact info
- Include special instructions
🎯 User Roles & Key Capabilities
Section titled “🎯 User Roles & Key Capabilities”| Role | Key Capabilities |
|---|---|
| Super Admin | Configures global emergency location taxonomies, verifies platform-wide RAY BAUM’s Act compliance, and manages system address validation standards. |
| Tenant Admin | Creates and manages physical premises, campuses, buildings, floors, suites, and rooms; assigns ELIN numbers and sets domain-level default locations. |
| Facility / Safety Manager | Maintains building-level emergency details, entry instructions, hazardous material notes, and on-site security dispatch contact information. |
| End User / Extension | Inherits precise dispatchable address metadata and assigned ELIN upon dialing 911, ensuring first responders are directed to the exact room or floor. |
Dispatch Location Form
Section titled “Dispatch Location Form”┌─────────────────────────────────────────────────────────────────┐│ Create Dispatch Location │├─────────────────────────────────────────────────────────────────┤│ ││ Section: Basic Information ││ ├─ Location Name: Main Building - 3rd Floor East ││ ├─ Location Code: MB-3E ││ └─ Enabled: ✓ ││ ││ Section: Assignment ││ ├─ Assignment Type: [User/Extension ▼] ││ └─ Extension: [1001 - John Smith ▼] ││ ││ Section: Street Address ││ ├─ Street Number: 123 ││ ├─ Street Name: Main ││ ├─ Street Suffix: Street ││ ├─ Unit Type: [Suite ▼] ││ ├─ Unit Number: 300 ││ ├─ City: Miami ││ ├─ State: FL ││ ├─ ZIP Code: 33131 ││ └─ Country: US ││ ││ Section: Building/Room Details ││ ├─ Building Name: Main Building ││ ├─ Floor: 3 ││ ├─ Room: 310 ││ └─ Wing: East ││ ││ Section: Emergency Information ││ ├─ ELIN: +13055551234 ││ ├─ Contact Name: John Smith ││ ├─ Contact Phone: (305) 555-9999 ││ └─ Special Instructions: Enter through main lobby... ││ ││ [Save] [Cancel] ││ │└─────────────────────────────────────────────────────────────────┘Quick Tips
Section titled “Quick Tips”[!TIP] Be Specific: Include floor, room, and wing for large buildings.
[!TIP] Update Regularly: Verify locations when employees move.
[!CAUTION] Critical Data: Inaccurate locations delay emergency response.
4. Configuration Fields Reference
Section titled “4. Configuration Fields Reference”Basic Information
Section titled “Basic Information”| Field | Description | Example |
|---|---|---|
| Location Name | Descriptive name | Main Bldg - 3rd Fl East |
| Location Code | Short identifier | MB-3E |
| Enabled | Active status | On/Off |
Assignment
Section titled “Assignment”| Field | Description |
|---|---|
| Assignment Type | User/Extension, Device, or Trunk |
| Extension ID | Associated extension |
| Device MAC | Device MAC address |
| Site ID | Site identifier |
Street Address
Section titled “Street Address”| Field | Description | Example |
|---|---|---|
| Street Number | Building number | 123 |
| Street Name | Street name | Main |
| Street Suffix | Type | Street, Avenue |
| Unit Type | Unit category | Suite, Floor |
| Unit Number | Unit value | 300 |
| City | City name | Miami |
| State | State code | FL |
| ZIP Code | Postal code | 33131 |
| Country | Country code | US |
Building/Room Details
Section titled “Building/Room Details”| Field | Description | Example |
|---|---|---|
| Building Name | Building identifier | Main Building |
| Floor | Floor number | 3 |
| Room | Room number | 310 |
| Wing | Building wing | East |
| Latitude | GPS latitude | 25.7617 |
| Longitude | GPS longitude | -80.1918 |
Emergency Information
Section titled “Emergency Information”| Field | Description |
|---|---|
| ELIN | Emergency Location ID Number |
| Contact Name | On-site emergency contact |
| Contact Phone | Contact phone number |
| Special Instructions | First responder notes |
| Validated | Address verified |
5. Address Components
Section titled “5. Address Components”Unit Types
Section titled “Unit Types”| Type | Usage |
|---|---|
| None | No sub-unit |
| Apartment | Residential apt |
| Suite | Office suite |
| Floor | Entire floor |
| Office | Specific office |
| Building | Entire building |
| Department | Dept area |
| Penthouse | Top floor unit |
| Basement | Below ground |
Assignment Types
Section titled “Assignment Types”| Type | Description |
|---|---|
| User/Extension | Assigned to extension |
| Device | Assigned to MAC address |
| Trunk | Assigned to SIP trunk |
6. Common Scenarios & Examples
Section titled “6. Common Scenarios & Examples”Scenario 1: Single Floor Office
Section titled “Scenario 1: Single Floor Office”Location:
| Field | Value |
|---|---|
| Name | Miami Office |
| Street | 123 Main Street |
| Suite | 300 |
| City/State/ZIP | Miami, FL 33131 |
| ELIN | +13055551001 |
| Assigned To | All extensions |
Scenario 2: Multi-Floor Building
Section titled “Scenario 2: Multi-Floor Building”Per-Floor Locations:
| Location | Floor | ELIN |
|---|---|---|
| Main Bldg - 1st Floor | 1 | +13055551001 |
| Main Bldg - 2nd Floor | 2 | +13055551002 |
| Main Bldg - 3rd Floor | 3 | +13055551003 |
Scenario 3: Campus with Multiple Buildings
Section titled “Scenario 3: Campus with Multiple Buildings”Per-Building Locations:
| Building | Address | ELIN |
|---|---|---|
| Main Building | 100 Campus Dr | +13055551100 |
| Warehouse | 200 Campus Dr | +13055551200 |
| Annex | 300 Campus Dr | +13055551300 |
Scenario 4: Remote Worker
Section titled “Scenario 4: Remote Worker”Home Office Location:
| Field | Value |
|---|---|
| Name | John Smith - Home Office |
| Street | 456 Oak Lane |
| City/State/ZIP | Fort Lauderdale, FL 33301 |
| ELIN | +19545552001 |
| Assigned To | Extension 1050 |
7. Limitations & Important Notes
Section titled “7. Limitations & Important Notes”Technical Notes
Section titled “Technical Notes”[!IMPORTANT] RAY BAUM’s Act: Dispatchable locations required as of January 2022.
[!WARNING] Accuracy Critical: Wrong location = delayed emergency response.
[!NOTE] ELIN Required: Each location needs unique callback number.
Validation Requirements
Section titled “Validation Requirements”| Field | Requirement |
|---|---|
| Street Number | Required |
| Street Name | Required |
| City | Required |
| State | Required |
| ZIP Code | Required |
| Country | Required |
Best Practices
Section titled “Best Practices”- Verify Addresses: Validate with USPS/carrier
- Update Regularly: When employees move
- Unique ELINs: One per location
- Contact Info: Current emergency contact
- Special Instructions: Access codes, hazards
8. Model Context Protocol (MCP) AI Integration
Section titled “8. Model Context Protocol (MCP) AI Integration”The Ring2All Platform Copilot connects directly with the Dispatchable Locations directory via the Model Context Protocol (MCP) to manage physical corporate addresses, verify postal dispatch data, and register emergency locations compliant with RAY BAUM’s Act.
Exposed MCP Tools
Section titled “Exposed MCP Tools”| Tool Name | Operation | Primary Parameters | Description |
|---|---|---|---|
list_dispatch_locations |
Directory Query | search (string, optional) |
Lists all physical dispatch addresses registered in the active domain, including city, state, postal code, and validation status. |
create_dispatch_location |
Location Registration | locationName (string), streetNumber (string), streetName (string), city (string), state (string), postalCode (string) |
Registers a verified physical address for E911 emergency response. |
delete_dispatch_location |
Location Removal | identifier (string or ID) |
Deletes a dispatch location record by name or ID. |
Location Name Uniqueness & RAY BAUM’s Act Safeguards
Section titled “Location Name Uniqueness & RAY BAUM’s Act Safeguards”- Domain-Scoped Uniqueness: The
location_namemust be unique across the tenant domain (SELECT id FROM dispatch_locations WHERE domain_id = :domain_id AND location_name = :location_name). Duplicate friendly names (e.g., creating multiple “Building A Floor 2” entries) are rejected. - Mandatory Civic Address Elements: In compliance with RAY BAUM’s Act, the system requires Street Number, Street Name, City, State/Province, and Postal/ZIP code before any dispatch location can be marked valid or assigned to an extension’s Emergency Location Identification Number (ELIN).
Example MCP Payloads
Section titled “Example MCP Payloads”1. Registering a New Office Dispatch Location (create_dispatch_location)
Section titled “1. Registering a New Office Dispatch Location (create_dispatch_location)”{ "locationName": "Headquarters - 4th Floor Suite 400", "streetNumber": "100", "streetName": "Biscayne Blvd", "city": "Miami", "state": "FL", "postalCode": "33132", "country": "US"}Response:
{ "success": true, "data": { "message": "Dispatch Location \"Headquarters - 4th Floor Suite 400\" registered successfully!", "locationName": "Headquarters - 4th Floor Suite 400", "id": 23, "address": "100 Biscayne Blvd, Miami, FL 33132" }}2. Querying Registered Locations (list_dispatch_locations)
Section titled “2. Querying Registered Locations (list_dispatch_locations)”{ "search": "Miami"}Copilot Natural Language Prompts
Section titled “Copilot Natural Language Prompts”- “List all physical dispatch locations registered for our PBX.”
- “Add a new dispatchable location for our Austin Branch: 500 Congress Ave, Suite 300, Austin, TX 78701.”
- “Verify if our headquarters location has been marked as validated by the E911 carrier.”
- “Delete the old warehouse dispatch location that was vacated last month.”
9. Troubleshooting Tips
Section titled “9. Troubleshooting Tips”Common Issues
Section titled “Common Issues”| Symptom | Possible Cause | Solution |
|---|---|---|
| Location not used | Not assigned | Assign to extension |
| Wrong location | Outdated record | Update location |
| No ELIN | Missing field | Add ELIN number |
| Address rejected | Invalid format | Use standard format |
| Not validated | Not verified | Validate with carrier |
Diagnostic SQL
Section titled “Diagnostic SQL”List dispatch locations:
SELECT id, location_name, street_number, street_name, city, state, building_name, floor, room, elin, enabledFROM public.dispatch_locationsWHERE domain_id = [domain_id];Find location by extension:
SELECT dl.*FROM public.dispatch_locations dlJOIN public.sip_extensions se ON dl.extension_id = se.idWHERE se.extension = '1001';10. Glossary
Section titled “10. Glossary”| Term | Definition |
|---|---|
| Dispatchable Location | Precise physical address with floor/room |
| ELIN | Emergency Location Identification Number |
| RAY BAUM’s Act | US law requiring dispatchable locations |
| NG911 | Next Generation 911 |
| PSAP | Public Safety Answering Point |
| GPS Coordinates | Latitude/longitude location |
Documentation last updated: January 2026

