The least expensive and simplest way to set this up is as follows:
- Order a dedicated DID for each “zone” (area/floor of the building that law requires have it’s own identifier - this is usually done by floor and wing or floor and quadrant - depends on how many square feet each zone is and the logical way to break it down) - These DIDs become your ELIN’s (Emergency Location Information Number)…
- With the carrier, have them register each ELIN with the PSAP for the specific address, floor, area/zone that you are planning on the number representing…
- In FPBX, under each extension’s ADVANCED>EMERGENCY CID, assign the appropriate DID/ELIN for the area the phone is deployed in…
- Test a phone in each zone to make sure the proper ELIN is presented to the PSAP…
- Create inbound rules that route return calls back to a security desk or someone in authority at each floor/zone, so at least return calls can be handled…
- Grab a beer (I recommend this after any work - never before)
…
The other thing we do is create a dedicated outbound route, which is programmed to record all emergency (and emergency test) calls. That way, we have a record of it if there’s ever any question as to how the call was handled (same for the inbound ELIN callbacks)…
Lastly, if you get the Paging Pro module, it has a nice “emergency alert” feature - when a call is made using the emergency route, it can send alerts to groups of phones (similar to a pre-recorded page - but you can get creative and do more with it). If you’re designating a specific person (or security desk) to handle callbacks, the initial Paging Pro alert is helpful for them to know who initially called 911.
With the practices above, since your law notes 7000 sq. ft. as a limit, each zone is essentially limited to that. Since each zone is under 7000 sq. ft., you would only need 3 ELINs registered (basement, floor 1, floor 2).
Hope this helps…