<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Im moving towards using the NG911 service from west specifically
for this sort of case. <br>
</p>
<p>Essentially you provision an address and a number, but then in
the invite to west, you can add an XML body with address
information that will override the provisioned info (it still must
be provisioned and validated but the relationships are fungible),
so if, in this case your user is on their home ext you can detect
that in your platform and send alternate info. <br>
</p>
<p>You can also provide detailed intra-building routing info for
larger campuses and facilities such as floor, room etc. <br>
</p>
<div class="moz-cite-prefix">On 3/7/2019 10:03 AM, Carlos Alvarez
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAEu0Vi2k+a=SEt=34rDAG5=_xzrwzTQgCLdQ0Of7DtMOgDq=3Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">I'm wondering what people are doing, and their
interpretation of the laws, with companies where they have large
numbers of remote (home) users. So far we have only a few
really, and we provide 911 for each phone's own CLID. Now we
have a customer who wants to have a very large number, PLUS have
an office handset, home handset, softphone on a computer, and
softphone on a mobile. It makes little sense to put 911 service
on each of these.
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
</body>
</html>