<div dir="ltr"><div>I believe if you look at the footnote on the third point you will find that they have realized the problems it will cause. I don't know of anything providing a path around it yet, but at least they acknowledge the rule is not perfect?</div><div><br></div><div>"<span style="font-size:16.6px;font-family:serif">While the access limitation is reasonable, signing a given call should not be limited to only the pool of numbers </span><span style="font-size:16.6px;font-family:serif">available to the provider via direct access. In other words, per ATIS</span><span style="font-size:16.6px;font-family:serif">-100074, 5.2.3, under correct conditions a </span><span style="font-size:16.6px;font-family:serif">qualified </span><span style="font-size:16.6px;font-family:serif">service provider (</span><span style="font-size:16.6px;font-family:serif">SP) must be allowed to sign leased numbers as well as other numbers belonging to an </span><span style="font-size:16.6px;font-family:serif">OCN not assigned to that qualified SP insofar as the SP can properly verify the customer's authorized</span><span style="font-size:16.6px;font-family:serif"> use of that </span><span style="font-size:16.6px;font-family:serif">number."</span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 26, 2020 at 2:52 PM Zilk, David <<a href="mailto:David.Zilk@cdk.com">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 class="gmail-m_5373631907059382076WordSection1">
<p class="MsoNormal">There are three requirements for a Service Provider to be included in the SHAKEN ecosystem:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="gmail-m_5373631907059382076MsoListParagraph"><u></u><span>1.<span style="font:7pt "Times New Roman"">
</span></span><u></u>Service Provider must have an OCN<u></u><u></u></p>
<p class="gmail-m_5373631907059382076MsoListParagraph"><u></u><span>2.<span style="font:7pt "Times New Roman"">
</span></span><u></u>Service Provider must have a current Form 499-A filed with the FCC<u></u><u></u></p>
<p class="gmail-m_5373631907059382076MsoListParagraph"><u></u><span>3.<span style="font:7pt "Times New Roman"">
</span></span><u></u>Service Provider must have direct access to telephone numbers from the North American Number Plan Administrator (NANPA) and National Pooling Administrator (NPA)<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">My company meets the first two requirements as we have an OCN as an interconnected voice provider (IPES) and a current Form 499-A filed, however we obtain telephone numbers from our carriers, and don’t have our own numbers assigned from
NANPA and NPA. How do we determine if we are eligible to obtain numbers and thus be qualified to play in the SHAKEN ecosystem?<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>