EULA "No emergency communications"

[treefiddy]

Upon installing the windows softphone client for the Nth time I noticed that the first paragraph in the EULA is:

NO EMERGENCY COMMUNICATIONS
LICENSEE (AS DEFINED BELOW) ACKNOWLEDGES THAT THE SOFTWARE (AS DEFINED BELOW) IS NOT DESIGNED OR INTENDED FOR USE TO CONTACT, OR COMMUNICATE WITH, ANY POLICE AGENCY, FIRE DEPARTMENT, AMBULANCE SERVICE, HOSPITAL OR ANY OTHER EMERGENCY SERVICE OF ANY KIND. THE SOFTWARE DOES NOT SUPPORT CALLS TO “911,” POISON CONTROL CENTERS OR TO ANY OTHER EMERGENCY NUMBER AVAILABLE IN YOUR COMMUNITY. 3CX DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR SUCH USES.

This is concerning to run for a business to rely on...

 

[leejor]

It is probably a legal requirement, that lets 3CX off the hook, if something (lawsuit worthy) happens because someone did not provision their PBX, to correctly handle emergency calls.

 

[SMF Media]

There are so many issues with 911. First of all with the windows client the end user needs to have a working speaker and microphone. Windows sound settings can be confusing for end users. The location information is also an issue. You could be anywhere with that windows phone connected to your system. An accidental hang up to 911 would send emergency responders to the location listed tied to your phone number. ANI/ALI is very tricky. I work for a Municipality the Police and Fire are our co-workers and this is always an issue. I mandate a POTS line be in every building so if there is an issue with the PBX there is always a way to call 911 that is tied to the location.

 

[TBWD]

3CX is just protecting themselves, as you know a mobile device can be located anyplace. When you call 911, the phone number may be listed to an address that you are not currently at,thus on a 911 hangup the police would not know where to find you. 3CX is letting you know upfront not to use the mobile app for this type of calling.