[cisco-voip] ng911

[Lelio Fulgenzi]

What I find funny is that the MPAA can find you if you download a movie, but emergency responders can't? Cellular service aside (and in that case, I hope that Webex calling has a "route out cell phone" option like Jabber does), if you have an IP address, you have to exist somewhere.

Why I gotta pay thousands of dollars more to make this work? They are shifting responsibility to end users rather than coming up with a way to make this work out of the box.

Ugh.

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Mark H. Turpin
Sent: Saturday, April 18, 2020 3:15 PM
To: cisco-voip at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200418/14ddf9d4/attachment.htm>