[cisco-voip] e911

[Bill Talley]

Seems like there's two key aspects we need to be concerned with.  1) As I
think Matthew is pointing out, notifications are only required if
notifications are a native feature available "without improvement", i.e.
add-on components.  2)  We now MUST configure direct 911 access without
regard to customer complaints or PSAP complaints about accidental 911 calls.

To answer your question Matthew, I have only ever used CER and Singlewire
for notifications, sorry I can't provide more feedback.

On Wed, Mar 7, 2018 at 3:06 PM, Matthew Loraditch <
MLoraditch at heliontechnologies.com> wrote:

> As far as I know that feature doesn’t notify anyone internally.
>
> The part of the law I’m referring to is this:
>
>
>
> *“A person engaged in the business of installing, managing, or operating
> multi-line telephone systems shall, in installing, managing, or operating
> such a system for use in the United States, configure the system to provide
> a notification to a central location at the facility where the system is
> installed or to another person or organization regardless of location, if
> the system is able to be configured to provide the notification without an
> improvement to the hardware or software of the system.”*
>
>
>
>
>
>
>
> Matthew Loraditch
> Sr. Network Engineer
> p: *443.541.1518* <443.541.1518>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>  |
> e: *MLoraditch at heliontechnologies.com* <MLoraditch at heliontechnologies.com>
> [image: Facebook] <https://facebook.com/heliontech>
> [image: Twitter] <https://twitter.com/heliontech>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
>
> *From:* NateCCIE [mailto:nateccie at gmail.com]
> *Sent:* Wednesday, March 7, 2018 3:58 PM
> *To:* Matthew Loraditch <MLoraditch at heliontechnologies.com>; 'Ryan Huff' <
> ryanhuff at outlook.com>; cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] e911
>
>
>
> Um, I thought it did.
>
>
>
> https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-
> communications-manager-callmanager/200452-Usage-of-
> Native-Emergency-Call-Routing-F.html
>
>
>
>
>
> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> *On Behalf Of *Matthew
> Loraditch
> *Sent:* Wednesday, March 7, 2018 1:36 PM
> *To:* Ryan Huff <ryanhuff at outlook.com>; cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] e911
>
>
>
> To piggy back on this, while Cisco doesn’t have emergency notifications
> built in, as the law mentions, and thus they are not required, does anyone
> know of options beyond Singlewire that they are happy with? The installs
> would monitor up to 1000 or so handsets but the folks that would be
> notified would probably be fewer than 50.
>
>
>
>
>
>
>
> *Matthew Loraditch*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *MLoraditch at heliontechnologies.com* <MLoraditch at heliontechnologies.com>
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> [image: Twitter] <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net
> <cisco-voip-bounces at puck.nether.net>] *On Behalf Of *Ryan Huff
> *Sent:* Wednesday, March 7, 2018 3:11 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] e911
>
>
>
> I wonder how cloud-based phone system like Cisco spark will answer this?
>
>
>
>
>
> https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
>
> Sent from my iPhone
>
> _______________________________________________
> cisco-voip mailing list
> 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/20180307/a679a629/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 444 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180307/a679a629/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image970315.png
Type: image/png
Size: 8404 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180307/a679a629/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8404 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180307/a679a629/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180307/a679a629/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image031030.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180307/a679a629/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image247918.png
Type: image/png
Size: 561 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180307/a679a629/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 561 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180307/a679a629/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image787063.png
Type: image/png
Size: 444 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180307/a679a629/attachment-0007.png>