Just wanted to give everyone an update on STIR/SHAKEN because the due
date to be compliant is June 30th and a few changes have been made to
the process recently (Last one was May 10th). I just spoke with Michael
Nemcik at the FCC on Friday and with Brent Struthers with the STI-GA
this morning to verify all this information because there's been a lot
of confusion about the process.
The first change is that EVERY CARRIER needs to sign up for the
mitigation database! Before you can comply with this final mitigation
database step, you'll need:
1. 499 account (and FRNs for each associated company)
2. Company Code (aka OCN)
3. Robocall Mitigation Database plan
NOTE: If you have not gotten a STIR/SHAKEN certificate AND/OR are not
100% compliant yet you'll have to submit the Robocall Mitigation Plan
when you register for the database. There are only guidelines as to what
your plan must include so you can write your own or get a consultant to
help you! Follow the process below to sign up for the Mitigation
Database.
There is no pre-registration process to qualify for a token. You'll
register and note that you are either fully compliant, partially
compliant or not compliant at all. Don't tell them what you plan to be
on June 30th - list what you are today. ONCE YOU ARE FULLY COMPLIANT,
THEN YOU CAN LOG BACK IN AND CHANGE YOUR STATUS!
Second change made earlier this year is that your company no longer
needs to be certified as a CLEC, ILEC, IPES, or Wireless Carrier to get
a STIR/SHAKEN certificate! If you' file 499s and have an agreement with
a DID provider, you can get an OCN assigned and qualify for the
STIR/SHAKEN certificate by completing the mitigation database process.
Once your name has been published on the FCC site for the mitigation
database, you can register with the STI-PA and work with a Certificate
Authority to get a token and test your traffic.
-------------------------------------------------------------------------
Below are the links for the Mitigation Database piece
-------------------------------------------------------------------------:
a. Associate your FRNs with your 499 filer ID.
https://apps.fcc.gov/cores/html/Associate_Username_to_FRN.htm
b. Sign up for Mitigation Database
https://www.fcc.gov/licensing-databases/fcc-user-login?fromURI=https%3A%2F%…
parm_uri%253D%25252Fnav_to.do%25253Furi%25253D%2525252Frmd%2525253Fid%2525253Drmd_landing
1). Answer your current status: (fully compliant,
partially compliant, non-compliant)
2). Submit your "Robocall Mitigation Plan"
4. Register with the STI-PA
https://authenticate.iconectiv.com/service-provider-authenticate
5. Select a Certificate Authority to assign your token and test with:
https://authenticate.iconectiv.com/certification-authority-authenticate
6. If you have not filed as 100% compliant, go back into the mitigation
database when you are done testing and revise your status to "100%
compliant!"
If you have any questions, just give me a call!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
I've had a CMAS alert relayed to me this afternoon saying that 9-1-1 service
is inop in Berkeley, Charleston, Colleton and Dorchester counties, South
Carolina... which seem *suspiciously* alphabetical to me -- and no, that's
not intended as humor.
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
