[VoiceOps] STIR SHAKEN requirement due by June 30th

Mary Lou Carey marylou at backuptelecom.com
Mon May 24 20:46:01 EDT 2021


You just submit your Articles of Incorporation, a contract with a DID 
provider, and a sample contract with one of your clients for services 
and they will assign you an IPES OCN. I can help you submit the 
paperwork if you want.

MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111

On 2021-05-24 07:32 PM, Calvin Ellison wrote:
> Hi Mary Lou,
> 
> This is very helpful, thank you. Can you add some detail about getting
> an OCN without the FCC Numbering Waiver?
> 
> Calvin Ellison
> 
> Systems Architect
> 
> calvin.ellison at voxox.com
> 
> +1 (213) 285-0555
> 
>  [1]
> 
>  [2] [3] [4] [5]
> The information contained herein is confidential and privileged
> information or work product intended only for the individual or entity
> to whom it is addressed. Any unauthorized use, distribution or copying
> of this communication is strictly prohibited. If you have received
> this communication in error, please notify me immediately.
> 
> On Mon, May 24, 2021 at 4:51 PM Mary Lou Carey
> <marylou at backuptelecom.com> wrote:
> 
>> 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%2Ffcc-ext.okta.com%2Fapp%2Fservicenow_ud%2Fexkfhf7wsY5PvdJv4296%2Fsso%2Fsaml%3FSAMLRequest%3DnVPvb9owEP1XIn8nP1ygxAIkBprG1HURsErbl8nYl2I1sTOfE%252Bh%252FPyfQQqUVTf0W%252Bd7dvffuZYy8LGjFZrXb6RX8qQFdcCgLjexYmZDaamY4KmSal4DMCbaefbtjNIxZZY0zwhQkmCGCdcroudFYl2DXYBsl4MfqbkJ2zlXIoigXwnfIEI81bfanLwyFKSPNm4o%252FQigNCRaeiNK8nfimvwcHF5onx7sOXlXRedjvWkZweMp3%252Be0efw6yRn5t%252BjQdRogmauWQ4LOxAjqxE5LzAoEEy8WErO%252FnST%252FhWzpMUhrLNElvtjThoxjiYR9SEDDyQMw4omrg3IpYw1Kj49pNCI1p0osHPdrfUMoGt%252BwmCUej9BcJspNNn5SWSj9e93R7BCH7stlkvez7etMNaJQEe%252B%252FRH7LzASx2VvoNZDrubss6%252Bvby3NeZ8Zcbk%252Bn%252FURhHl4tOayvWqlguMlMo8RzMisLs5xa488qcraE7Usnd%252B1ySMOlelOzlHZRByVUxk9ICIoleF50CDbK7uE%252Bm8%252BkJ5qasuFXY2gEHLtyrIZeweeHlriD%252FkD1XYYKJdrZ%252FbvO0N1a2%252BQDheW4s11gZ616c%252Bxej6an4jr5z%252BfKnnv4F%26RelayState%3Dhttps%253A%252F%252Ffccprod.servicenowservices.com%252Fsaml_redirector.do%253Fsysparm_nostack%253Dtrue%2526sys
>> 
> 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
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> 
> 
> Links:
> ------
> [1] http://voxox.com
> [2] https://www.facebook.com/VOXOX/
> [3] https://www.instagram.com/voxoxofficial/
> [4] https://www.linkedin.com/company/3573541/admin/
> [5] https://twitter.com/Voxox


More information about the VoiceOps mailing list