FreePBX New E911 Compliance Features


(Jared Busch) #23

Unless you become the next 10 states no…


(Tom Ray) #24

I would check within Canada as they have ng911 and it seems there are some new things happening with that from some quick searches I did a few weeks back.


(Joshua Cadman) #25

How would it be possible to setup an extension or group to be paged when someone calls 911 on any phone in the organisation as spoken about sending notifications to front desk or security office?


(Jared Busch) #26

Update your System, that is already a standard feature now.


(Joshua Cadman) #28

I have updated it and now see I can choose notification. Is there a way to send sms and email when someone calls 911/999 instead of just paging


(Lorne Gaetz) #29

Not without custom dialplan. See this post for how to create an extension that sends an email: Email notification of incoming/missed call


(Greg Kujawa) #30

I placed this section in my extensions_custom.conf file and it works fine. The mail recipient can essentially be an SMS recipient by using the proper cell provider’s mail domain for this. In my example below, I am using AT&T’s.

[macro-dialout-trunk-predial-hook]
exten => s,1,ExecIf($["${OUTNUM}"="911"]?System(echo "Ext ${AMPUSER} - ${AMPUSERCIDNAME} just placed a 911 emergency call on ${STRFTIME(%C%m%d%y%H%M)}" | mailx -r "sender@domain.com" -s "911 Alert from ext ${AMPUSER} - ${AMPUSERCIDNAME}" 10digitNumber@txt.att.net))
exten => s,2,ExecIf($["${OUTNUM}"="933"]?System(echo "Ext ${AMPUSER} - ${AMPUSERCIDNAME} just placed a 933 test call on ${STRFTIME(%C%m%d%y%H%M)}" | mailx -r "sender@domain.com" -s "933 Alert from ext ${AMPUSER} - ${AMPUSERCIDNAME}" 10digitNumber@txt.att.net))
exten => s,n,MacroExit()

#31

I wonder how compliance is possible with softphone apps on mobile devices. This seems, at least in part, like a technology law written by people who still think the internet is a ‘series of tubes’.


#32

It would take a strange combination of circumstances for this to matter. Normally, a SIP app routes 911 as a mobile voice call.

I suppose it’s possible that if you are in a location with no cellular coverage at all, but you do have Wi-Fi, and your mobile carrier does not support Wi-Fi calling, you could override normal behavior to make an emergency call.


#33

As with any specifics such as these, it is recommended you check with your local laws to see if further information can be found. Having said that, I feel that softphones on mobile devices that are away from the main location would qualify as “off-premises” end users, which fall under what’s being discussed around paragraph 159 in this doc:


Which starts with:

159. In contrast, we conclude that MLTS providers should not be subject to the same location
requirements for off-premises MLTS calls to the extent compliance is not technically feasible. When an
MLTS end user is off-premises, the MLTS does not typically control or have access to location
information. 

And paragraph 160, which goes on to say:

160. In light of these factors, we conclude it is premature to prescribe specific standards for
location of off-premises MLTS calls when compliance with our on-site requirements would not be
technically feasible, and we therefore adopt a flexible approach that avoids imposing impossible
requirements. For off-premises 911 calls, the MLTS operator or manager must provide (1) dispatchable
location, if technically feasible, or, otherwise, either 2) manually-updated dispatchable location, or
(3) enhanced location information, which may be coordinate-based, consisting of the best available
location that can be obtained from any available technology or combination of technologies at reasonable
cost. This requirement will take effect two years from the effective date of rules adopted by this order.
The flexibility inherent in this requirement should lessen the burden and the amount of time it will take to
comply. We recognize that as a practical matter, MLTS providers are unlikely to be capable of providing
dispatchable location for most off-premises calls, and that “best-available” location information may be
limited in the near term. Nevertheless, over time this requirement will encourage development of
improved location capabilities for off-premises MLTS 911 calls. 

These are just excerpts. Please see the doc for further details and context.

I agree with your second point with a lot of this stuff. In this case, it’s like they acknowledge some devices can’t meet the current requirements based on technical feasibility, but their solution is to just give these situations a later deadline.

From a practical stance, I’d advise all mobile softphone users to consider using the cell phone’s service, or a local phone when calling 911 instead of through the softphone if feasible. Or at least have them understand the difference. Although, that type of explanation would be a good idea regardless of these new rules.


closed #34

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.