[cisco-voip] ng911

[Mark H. Turpin]

Lelio,

I believe Webex Teams will redirect a 911 call from a mobile device to the native phone capabilities of the iPhone/Android.  I'm personally fine with the cellular carriers taking responsibility for providing the details like lat/long for the mobile phone. The data is already there on the phone, so I don't see any reason for the softphone to be involved.

Regarding Teams clients on the laptops and phones registered to Webex cloud, though, I am kind of wondering when and how Cisco will address NG911 compatibility.



________________________________
From: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of Lelio Fulgenzi <lelio at uoguelph.ca>
Sent: Saturday, April 18, 2020 5:41 PM
To: cisco-voip at puck.nether.net <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] ng911

*** EXTERNAL EMAIL - DO NOT CLICK LINKS ***




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<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fdam%2Fen_us%2Fabout%2Fdoing_business%2Flegal%2FOfferDescriptions%2Fcisco_collaboration_flex_plan.pdf&data=01%7C01%7Cmturpin%40covene.com%7C3eb60d556bc442b13c2008d7e3e9bbdb%7C575b0cc755204e999cb37affbf511f45%7C1&sdata=7zpjktKruM9KrEeyU60trWzW1CAY8J1vldygC91iVp4%3D&reserved=0>) 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<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fconfigure-dynamic-emergency-calling&data=01%7C01%7Cmturpin%40covene.com%7C3eb60d556bc442b13c2008d7e3e9bbdb%7C575b0cc755204e999cb37affbf511f45%7C1&sdata=GsH8fiuVlFufQ7te1iXd%2F%2F1Tq86Rr9DR2SF2CXK80Q4%3D&reserved=0>



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/20200420/821cf1a4/attachment.htm>