We have one user that is asking for a second phone in one of our other buildings. The ‘nice’ thing to do would be to add this as another device on his extension, so you’d get him by dialing one number. The only problem with this is that it breaks our 9-1-1 outbound rules, because that extension is set to go out on a specific route.
I hope that makes sense, and does anyone have thoughts on this?
What do you mean a specific route? A specific 911 route that all the phones use or a route specifically for this extension/device?
We have multiple buildings and each has it’s own outbound route for 911 calls, so this user’s primary extension goes out route A for 911, but their secondary phone should go out route B.
What do these routes do? Two different providers? Do you have individual 911 registration for each phone or just each location?
Same provider but different phone numbers, each configured to the correct address.
Maybe there is a better way to handle this but you could either:
1.) Use Device and User mode and create a new device (assigned to the same user) with a new emergency callerid assigned that has the correct address for e911
2.) Create a new extension for this person.
So all the phones, at each location, are in the same area? Single floor, etc?
No, they’re located throughout a 100,000 sq ft building, each location
Is it multiple floors? Are there multiple offices? Sections? Are there multiple ingress/egress (in/out doors) to the buildings?
Yes in one case. Yes. Yes. Yes but all access controlled.
You are not in full compliance with Ray Baum’s then. Ray Baum’s requires Dispatchable Locations down to the floor or area of the building they are in. This is true of large buildings and 100K sq feet is a large building.
If in one building the phone is on floor 2 in room B in the west side, you need to give as exact details as possible. The floor number is required, the room number is most likely required. A building this side with multiple entrances needs to indicate to the PSAP where emergency personal need to enter the building. If the call came from the East side and the EMS enter on the West side then have to spend 5 minutes crossing the building…you’re on the hook for anything bad.
Your buildings do not fit the requirements of one location to rule them all. You need to get your Ray Baum compliance sorted out.
Is there a guide as to how we get that information into FreePBX? Searching in the old Community gives lots of bits and pieces but if there’s somewhere that you can point me that’s ‘more complete’ then we’ll see what we can do.
And, thank you, your time is appreciated as always.
I’ll have to do some checking on my own. I haven’t had this scenario with a FreePBX system yet . I know there is things in place for this but look at it more.
In the mean time, you need to figure out how many of these phones need their own 911 location registration at both locations. You’ll need more DIDs it sounds like.
Some providers offer a way to set up multiple phones off a single DID. When dialing 911, you assign a special number associated with a specific phone to the account on the provider. So when the users dials 911, the provider will forward the location to 911 along with the actual phone number of the account.
So you may not need any more DIDs
Yes, it’s called Dynamic Location Routing. It’s the method we use for 911.
You basically need to use a unique alphanumeric identifier that is sent as the CID number along with a Geolocation header that contains information about a pre-registered location. You can also send geolocation data real time in the SIP packet.
Tom the only thing I would add here is I don’t know of any carrier for 911 that allows you to dynamically send any address in the SIP invite that has not been validated first as a proper 911 address. Even bandwidth requires that the address be pre validated. Which kind of defeats the purpose of sending the address in the SIP invite versus the pre defined Dispatchable Location.
Correct, you always have to pass a validated location. However, that location does not need to be registered but it must be an exact match to the validation results. So at some point the address needs to be passed through the validation process to get the exact results so those can be passed. Much like you, I find this a PITA and just use pre-registered locations.
The Lat/Lon options, however, are much more interesting. You still need to pass a pre-registered location but you can also pass lat, lon and radius values. If the lat/lon are within the defined radius (50 meters by default) then the pre-registered location is used. If the lat/lon are outside the radius, the closest matching address for the lat/lon is used for routing the call.
Have you tried to get them to enable lat/long yet on DLR. last time we talked with them it was reserved for mobile operators only.
I’d have to test again but I don’t recall if it needed to be turned on or not.
I haven’t tried to use it yet but Bulkvs say they support Dynamic 911 routing as does Bandwidth.com (who appears to be the Bulkvs backend.)