Legal language aside, I see this as a HUGE area for VARs to get into civil 
torts with customers.

Ideally the end customer is the true owner and stakeholder of the MLTS however; 
when levied with a government fine (presumably how it would be handled), due to 
e911 malfeasance, who was the last one to touch it?

Document everything, get sign off on everything and proceed with caution :) 
brothers and sisters.

Sent from my iPhone

On Mar 7, 2018, at 22:10, Anthony Holloway 
<avholloway+cisco-v...@gmail.com<mailto:avholloway+cisco-v...@gmail.com>> wrote:

I'd be cautious with this one.

1) You penalize actual emergency calls from connecting as quickly as possible.  
Do you really want to be the person responsible for that?

2) You penalize the entire cluster by changing a global parameter, for the 
occasional accidental 911 call.

I think a better solution is to solve the human problem.  Just like we wouldn't 
tolerate our children playing on land lines or cell phones calling 911 (even my 
son has done it), we shouldn't tolerate adults doing it either.

Failing that, switch your PSTN trunk access code to another digit.  8 seems to 
be a popular second choice.

On Wed, Mar 7, 2018 at 3:41 PM NateCCIE 
<natec...@gmail.com<mailto:natec...@gmail.com>> wrote:
This might be a good time to talk about my favorite way to enable 911.

Set the interdigit timeout to a small value, like 3-5 seconds.  Then create a 
911 route pattern, and a 911! Pattern, that does not route to 911.  If the user 
dials 911 and stops, the call connects.  If they keep dialing which usually 
what happens on a miss-dial, they get whatever your 911! Pattern is configured 
to do, usually I like block this pattern.

-Nate

From: Bill Talley <btal...@gmail.com<mailto:btal...@gmail.com>>
Sent: Wednesday, March 7, 2018 2:22 PM
To: Matthew Loraditch 
<mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>>
Cc: NateCCIE <natec...@gmail.com<mailto:natec...@gmail.com>>; Ryan Huff 
<ryanh...@outlook.com<mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] e911

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 
<mloradi...@heliontechnologies.com<mailto:mloradi...@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<tel:443.541.1518>



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

 |

e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>


<image001.png>


<https://facebook.com/heliontech>
<image002.png>


<https://twitter.com/heliontech>
<image003.png>


<https://www.linkedin.com/company/helion-technologies>
<image004.png>







From: NateCCIE [mailto:natec...@gmail.com<mailto:natec...@gmail.com>]
Sent: Wednesday, March 7, 2018 3:58 PM
To: Matthew Loraditch 
<mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>>; 
'Ryan Huff' <ryanh...@outlook.com<mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@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-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Matthew Loraditch
Sent: Wednesday, March 7, 2018 1:36 PM
To: Ryan Huff <ryanh...@outlook.com<mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@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<tel:443.541.1518>



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

 |

e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>


<image001.png>


<https://facebook.com/heliontech>
<image002.png>


<https://twitter.com/heliontech>
<image003.png>


<https://www.linkedin.com/company/helion-technologies>
<image004.png>







From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Wednesday, March 7, 2018 3:11 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@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@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to