<div dir="ltr">I believe that the stickers on home phones may not really cover the liability. The wording is something like: A phone or device that a person would reasonably assume can call emergency services." So the softphone is obviously different, but a physical phone at home seems like it must still work properly.<div><br></div><div>I have NOT been able to get anyone to tell me this for sure, and I've had various trainings on the matter. So I think the answer is "nobody knows" and the answer will cost some company tens of millions of dollars in court.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 23, 2020 at 10:42 AM Brian Heinz <<a href="mailto:brian.e.heinz@gmail.com">brian.e.heinz@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>1. Most PBX/UC platform vendors can send a different CLID for emergency calls. Normally this is called the ELI or CESID in the PBX. This emergency CLID of course needs to be set up with the PSAP with the appropriate location information, which is usually handled through the carrier. Granularity requirements vary by state, but the best advice I've heard is to provide enough detail so the first responders know which door to break down.</div><div><br></div><div>2. Again, most PBX/UC platforms can handle this without issue, the outgoing CLID does not necessarily have to match an incoming DID, and different CLID can be sent on emergency calls.</div><div><br></div><div>3. Generally, softphones are not able to place emergency calls. Make the users sign a disclaimer stating as such. Some softphones can display a reminder message on launch stating they are not to be used for emergency calls. If a remote user has a physical phone at home, disclaimer and a sticker on the phone stating it cannot place emergency calls.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 23, 2020 at 12:11 PM Zilk, David <<a href="mailto:David.Zilk@cdk.com" target="_blank">David.Zilk@cdk.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal">For those that don’t know, RAY BAUMS Act is a new regulation that impacts Emergency Calling. It mandates that a “Dispatchable Location” be included with information to the PSAP when a 9-1-1 call is made in the US. The deadline for compliance
is August 1, 2020 (or August 1, 2021 for some scenarios).<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Dispatchable Location is defined as “the street address of the calling party, and additional information such as room number, floor number, or similar information necessary to adequately identify the location of the calling party.”
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">How are people planning on complying with this? Particularly:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p><u></u><span>1)<span style="font:7pt "Times New Roman"">
</span></span><u></u>When several lines at a site don’t have DIDs, and uses a common site phone number for their CLID. How do you provide different location information for them.<u></u><u></u></p>
<p><u></u><span>2)<span style="font:7pt "Times New Roman"">
</span></span><u></u>When there are shared lines on devices in different locations at a site using the same DID. How do you distinguish the correct location of an emergency call made from one of them.<u></u><u></u></p>
<p><u></u><span>3)<span style="font:7pt "Times New Roman"">
</span></span><u></u>When the caller uses a softphone that doesn’t have a fixed location.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">David<u></u><u></u></p>
</div>
<hr>This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.<br>
</div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>