[cisco-voip] Official Cisco E911 Guidance

[Pawlowski, Adam]

Yes, I noted that language which was probably carefully vetted for liability.

They also were careful about recommendations, suggestions, etc to avoid “Cisco said”.

There’s some interpretation that seems to be around “improvements”, but, I believe some of that is taking that word at face value and not referring back to the FCC’s clarification on it.

Certainly going to be a hot topic of discussion for a minute (and was in some circles leading up) depending on liability.

Still careful too to say sure we can monitor Jabber (*on wifi)

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Anthony Holloway
Sent: Tuesday, February 18, 2020 3:54 PM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com>
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Official Cisco E911 Guidance

I found this interesting:

Q: Do I need to upgrade UCM to be compliant?
A: No! Existing UCM deployments are configurable for Kari’s Law.

...

We strongly suggest that Cisco UCM customers evaluate other emergency safety add-ons through RedSky, Intrado, and Singlewire

On Tue, Feb 18, 2020 at 2:04 PM Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>> wrote:
This was just published:
https://blogs.cisco.com/collaboration/saying-yes-to-workplace-safety-how-ucm-customers-become-compliant-with-karis-law-and-ray-baums-act

https://www.cisco.com/c/dam/en/us/products/collateral/unified-communications/unified-communications-manager-callmanager/q-and-a-c67-743415.pdf








Matthew Loraditch​

Sr. Network Engineer


p: 443.541.1518<tel:443.541.1518>



w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>


[Helion Technologies]<http://www.heliontechnologies.com/>


[Facebook]<https://facebook.com/heliontech>


[Twitter]<https://twitter.com/heliontech>


[LinkedIn]<https://www.linkedin.com/company/helion-technologies>







_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200218/e765b18b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6875 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200218/e765b18b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 431 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200218/e765b18b/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 561 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200218/e765b18b/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 444 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200218/e765b18b/attachment-0003.png>