[VoiceOps] Hotel Phone

Fri Apr 5 10:56:58 EDT 2019

Not only must you look at federal law, but many states have specific
requirements also.  For example, UT has had something stronger than the
proposed new federal laws since 2017.  They specifically require that the
PSAP be able to call the person back no matter what, and to give floor,
suite, and room info (not just for hotels, for all users).  At this point
you should assume that either every phone gets a DID (in a large setting)
or at the minimum, the callback number is a ring group for the entire
office (what we've done for years in small spaces).

All of us need to be seriously looking at all of these new regulations and
compliance, and you really need to get on it now.  It won't be long before
fines start coming down, or worse, you find yourself with a dead person's
estate's lawyer at your door.  Kari's law was written on a headstone.

This is going to cost you money.  It is my understanding that some of these
costs can be passed on, some are just going to be your operational costs.
We completely re-wrote our 911 processing a couple years ago, expecting
things like this to come about.  Now we're going through it again to
respond to the specific things that have changed, which weren't all that
different from what we expected.  We are charging a per-number 911 charge
just like our carriers charge us, and the customary per-DID charge for the
people who had to have more DIDs added.  At this point, we will not turn up
a new customer without DIDs unless they are very small.  The days when a 50
person company could be behind a single DID are over.

On Fri, Apr 5, 2019 at 6:08 AM Mark Lindsey <lindsey at e-c-group.com> wrote:

> Re 911 requirements -- The SIPNOC conference discusses this kind of thing
> annually. Eric Burger, CTO of the FCC, did a presentation and Q&A session
> on it last year. Here are his presentation notes (though without the Q&A):
>
>
> https://www.sipforum.org/download/a-discussion-about-karis-law-act-of-2017/?wpdmdl=3555
>
>
> Currently, the requirements are not fully defined. The FCC is in the
> rulemaking phase, and has published this Notice of Proposed Rulemaking:
>
> https://docs.fcc.gov/public/attachments/FCC-18-132A1.pdf
>
>
>
>
>
>    - A Discussion about Kari’s Law Act of 201712.11.2018
>    <https://www.sipforum.org/download/a-discussion-about-karis-law-act-of-2017/?wpdmdl=3555>
>
>    Presented by Dr. Eric Burger, FCC CTO. H.R. 582, commonly known as
>    “Kari’s Law Act of 2017,” amends the Communications Act of 1934, and is
>    named in honor of Kari Hunt Dunn whose tragic death in 2013 alerted the
>    nation to the dangers of requiring a dialing prefix to access 911. Due to
>    the advocacy of Hank Hunt, Kari’s father, Americans across the land will
>    benefit from easier access to 911 when connecting to the service from
>    certain private phone systems. Kari’s Law requires multi-Line telephone
>    systems, like Unified Communications (UC) platforms, to allow users to dial
>    911 without requiring any prefix, post-fix or trunk access code. In
>    addition to the direct dialing provision, Kari’s Law also requires that
>    on-site notifications be issued when someone calls 911. Current FCC CTO Dr.
>    Eric Burger will provide more information about this new law, the
>    requirements under the law, and its impact on individuals and businesses
>    today.
>
>
> My company also has an upcoming class on laws/regulations for Voice
> network engineers & technicians that will cover Kari's Law, though from an
> engineering perspective, not a lawyer's. I am not a lawyer.
>
>
> *Mark R Lindsey, SMTS *
> *+1-229-316-0013*
> *mark at ecg.co <mark at ecg.co>*
> *http://ecg.co/lindsey/ <http://ecg.co/lindsey/>*
>
>
>
> On Apr 4, 2019, at 12:08 PM, Jason Kuylen <kuylenj at eastex.com> wrote:
>
> I’ve never heard of any other 911 requirement for hotel or business phones
> outside of not have to dial 9 to dial 911, ie 9911. Kari’s Law.
>
> Can anyone provide a link with more information?
>
> Thanks.
>
> Important/Confidential: This communication and any files or documents
> attached to it are intended only for the use of the person(s) or entity to
> which it is addressed. It contains information that may be confidential and
> exempt from disclosure under applicable law. If you are not the intended
> recipient of this communication, you are hereby notified that the copying,
> disclosure, distribution, storage, retransmission or other use of this
> communication is strictly prohibited. If you have received this
> communication by mistake, please notify the sender immediately and destroy
> all forms of this communication (electronic or paper).
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
>
> *Mark R Lindsey, SMTS *
> *+1-229-316-0013*
> *mark at ecg.co <mark at ecg.co>*
> *http://ecg.co/lindsey/ <http://ecg.co/lindsey/>*
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190405/eace823c/attachment-0001.html>