It is on the list of considerations for sure.

If I'm reading (skimmed) Microsoft's document you linked, this works more or 
less how the traditional E911 systems work, and do nothing for you for home or 
roaming users. In a way I am surprised there aren't some more solutions on the 
table, but, at the same time these disclaimers and the wording in a lot of the 
documentation is to try and shy away from any sort of liability. If I go to 
Bing to figure out how to order a pizza, both it and the pizza places can tell 
where I am pretty darn close just based on my IP address. You'd think that sort 
of thing would be a start to a 911 solution, but, it is imperfect, imprecise, 
and can be wrong - and the liability there may force some to just say, look, we 
can't do it - implement at your own risk.

Absolutely waiting on this one to be more well developed, but, I hazard that 
the business address solutions are just fine for SMB and not Enterprise, which 
holds true for whole hog implementations of these systems in general at the 
moment. (Costs, ROI, feature set, etc)

Adam

From: cisco-voip <cisco-voip-boun...@puck.nether.net> On Behalf Of Mark H. 
Turpin
Sent: Saturday, April 18, 2020 3:15 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] ng911

Is anyone thinking about NG911 compatibility for pure Teams/Webex cloud 
calling? I understand Intrado/RedSky offerings for CER/on-prem/Jabber/hybrid 
calling.

The Webex Calling terms 
(https://www.cisco.com/c/dam/en_us/about/doing_business/legal/OfferDescriptions/cisco_collaboration_flex_plan.pdf)
 state pretty clearly Cisco isn't supporting it today.

Emergency Response Disclaimer
YOUR EMERGENCY RESPONSE LOCATION FOR PURPOSES OF EMERGENCY CALLS IS LIMITED TO
YOUR COMPANY ADDRESS. IT IS YOUR RESPONSIBILITY TO ADVISE YOUR AUTHORIZED USERS
TO ALWAYS PROVIDE THEIR CURRENT LOCATION WHEN CALLING EMERGENCY SERVICES.

That disclaimer is fine except when a user is calling 911 and can't speak to 
provide their address.

While Ray Baum's Act isn't in effect yet, it seems like Microsoft might have a 
leg up on this already with Dynamic Location Routing capabilities via their LIS 
and trusted IP architecture.
https://docs.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling

I don't have an answer yet, just starting the conversation.
-Mark
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to