<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div dir="ltr">Mad props to the gang at nether.net for hosting this mail list! </div>
<br>
<div dir="ltr">David </div>
<br>
<div dir="ltr">Sent from Workspace ONE Boxer </div>
<br>
<div class="x_bx-html"><style>
<!--
.x_EmailQuote
{margin-left:1pt;
padding-left:4pt;
border-left:#800000 2px solid}
-->
</style>
<div class="x_bx-body">
<div class="x_quote">On Mar 27, 2020 2:20 PM, Mary Lou Carey <marylou@backuptelecom.com> wrote:
</div>
</div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Just wanted to give everyone an update on STIR / SHAKEN since it still
<br>
seems to be so confusing to everyone. I spoke with Brent Struthers from <br>
ATIS again today because I've been getting a lot of questions about how <br>
many LATAs Interconnected VOIP providers have to order NXXs in to <br>
qualify for a STIR/SHAKEN certificate.<br>
<br>
In case you didn't read our previous discussion, the original guidelines <br>
for getting a STIR / SHAKEN certificate state you need to meet the <br>
following 3 requirements:<br>
<br>
1. Have an OCN assignment for CLEC, ILEC, IPES, Paging, RBOC, or <br>
Wireless<br>
2. Be assigned a 499 Filer ID and submit 499 filings<br>
3. Direct Access to Numbering Resources through NANPA<br>
<br>
<br>
In talking with Brent today, I discovered that the FCC doesn't really <br>
care if you order any NXXs for your company. Brent said what they really <br>
expect is for every carrier to have an FCC License, Authorization, or <br>
State Certification. Below is the type of licensing each carrier type <br>
needs:<br>
<br>
- CLEC (State Certification)<br>
- ILEC (State Certification)<br>
- Paging (FCC License)<br>
- RBOC (State Certification)<br>
- Satellite (FCC License)<br>
- Wireless (FCC License)<br>
- VOIP (Interconnected VOIP Numbering Authorization from FCC)<br>
<br>
So the bottom line for all you VOIP providers is that EVERY VOIP <br>
PROVIDER must get an Authorization from the FCC so they can acquire <br>
their own STIR / SHAKEN certificate. You don't need to order any NXXs to <br>
get a STIR/SHAKEN certificate! Getting the FCC Authorization is much <br>
less work than turning up a LATA with your own NXX, so please don't let <br>
any DID service providers talk you into using their certificate. YOU <br>
NEED YOUR OWN STIR/SHAKEN certificate!<br>
<br>
One last thing regarding Interconnected VOIP Providers because I've also <br>
had a lot of questions regarding when it becomes beneficial to operate <br>
as an Interconnected VOIP Provider. First of all, let me explain the <br>
difference in architecture between the DID service provider and the <br>
Hosted PSTN Service provider. DID Service Providers allow you to order <br>
DIDs from anywhere in their service area. They charge per TN based on <br>
rate center and manage all the routing of the traffic as well as your <br>
NRUF reporting and number ports. Hosted PSTN service follows the same <br>
network architecture that the PSTN network does so it's only implemented <br>
by LATA / ILEC Tandem area. You get a CLLI and NXX for each LATA / ILEC <br>
tandem area so you can establish an LRN for that LATA. You can port a <br>
number from any rate center in that LATA / ILEC Tandem area to your LRN <br>
and you pay based on the type of traffic it is rather than the rate <br>
center classification. While the Hosted PSTN provider manages the <br>
routing of the traffic for you, you manage your own NRUF reporting and <br>
Number Porting. Below are my recommendations on when it becomes <br>
beneficial to move from a DID service in a particular LATA to a Hosted <br>
PSTN service in that LATA.<br>
<br>
1. You have a lot of TNs in a particular LATA: DID service charges <br>
anywhere from $0.05 to $0.50 per TN. The monthly recurring charge for a <br>
1,000 block in each LATA varies by month but currently averages about <br>
$1.40 per month. You also have to figure in a few other costs, but what <br>
you pay is determined by the Hosted switch provider you use.<br>
<br>
2. You port a lot of TNs in a particular LATA: DID service charges to <br>
port each TN. NPAC charges based on the number of ports. A port is any <br>
group of consecutive numbers within an NPA-NXX block. So if you wanted <br>
to port 100 consecutive numbers, the DID service would charge you for <br>
100 ports but NPAC would only charge you for 1 port. There are multiple <br>
options when it comes to the method of porting, so don't let that scare <br>
you. You can hire someone to do the porting for you or do your own <br>
through the NPAC LTI service, a hosted app, or a managed service that <br>
integrates the whole process for you.<br>
<br>
3. You have a lot of traffic in a particular LATA and want more control <br>
over which carrier you route your traffic through: When you use a DID <br>
service provider, your only option is to use the services of that <br>
carrier. When you manage your own porting, if there's an issue with <br>
traffic blocking you can re-route your traffic to the LRN of another <br>
carrier that you are set up with. When you have your own NXXs they are <br>
associated with your own OCN so it's easier to move your traffic from <br>
one carrier's network to another carrier's network should you ever need <br>
to down the road.<br>
<br>
So that's the scoop! Feel free to e-mail me privately if you have more <br>
questions.<br>
<br>
MARY LOU CAREY<br>
BackUP Telecom Consulting<br>
Office: 615-791-9969<br>
Cell: 615-796-1111<br>
_______________________________________________<br>
VoiceOps mailing list<br>
VoiceOps@voiceops.org<br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</div>
</span></font>
<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>
</body>
</html>