Yeastar

Complete guide: STIR/SHAKEN compliance with Yeastar PBX

Find out how to obtain and apply STIR/SHAKEN certificates for your P‑Series Cloud PBX to secure your SIP calls and comply with FCC regulations.

GuideNovember 11, 2025

Complete guide: STIR/SHAKEN compliance with Yeastar PBX

Voice service providers must now authenticate caller identity to combat spoofing and fraud. Implementing STIR/SHAKEN may seem complex, especially for small businesses. Fortunately, Yeastar has integrated this framework directly into its P‑Series Cloud PBX, eliminating the need for third-party infrastructure. This guide takes you step by step, from checking your eligibility to the final configuration on the Yeastar platform.

Who needs a STIR/SHAKEN certificate

According to the FCC, any operator that originates SIP calls must sign its calls with an authorized STI certificate. This includes Tier 1 carriers, CLECs, and ITSPs with their own PSTN numbers. Resellers do not require their own certificate, but must register in the RMD database and declare their use of upstream certificates.

Four steps to obtain your certificate

1️⃣ Check your eligibility: register with the FCC (Form 499‑A) and obtain an identification number. 2️⃣ Obtain an OCN through NECA by submitting the required documents. 3️⃣ Register with Iconectiv, the official STI‑PA, to receive a SPC Token valid for one year. 4️⃣ Request your STI certificate from an approved CA by submitting your CSR and token. 5️⃣ Register in the RMD database to declare your compliance.

Integrated STIR/SHAKEN solution on Yeastar Cloud PBX

Once your certificate is uploaded to Yeastar Central Management, the system automatically signs every outbound call and verifies incoming calls. Signature and verification results are recorded in the CDRs, allowing you to track compliance and filter suspicious calls according to your predefined rules.

Benefits of the integrated solution

No need for external integrations or additional costs associated with a signing infrastructure. Regulatory compliance is ensured, caller trust is strengthened, and internal resources are freed up to focus on business development.

Additional resources

For more information on configuration or troubleshooting, consult Yeastar’s STIR/SHAKEN configuration guide. It provides detailed instructions and screenshots for every step.

The Yeastar team supports businesses and integrators in assessing their needs, selecting an architecture, and preparing for deployment.

Combating spoofing and fraudulent calls requires voice service providers to sign their SIP calls with a STIR/SHAKEN certificate. For operators, especially those with their own numbers or softswitch, implementation may seem complex. Yeastar simplifies this process with a framework integrated into its P‑Series Cloud PBX, eliminating the need for external infrastructure. This guide explains who needs to obtain a certificate, how to get one, and how to integrate it into your Yeastar system.

Who must hold a STIR/SHAKEN certificate

According to the FCC, any voice service provider that originates SIP calls must sign those calls with an authorized STI certificate. Tier 1 operators, CLECs, and ITSPs with their own PSTN numbers must obtain their own certificates. Resellers do not, but must register in the RMD database and declare their use of third-party certificates.

Step 1: Check your eligibility

You must first prove your legitimacy as a voice service provider in the United States: register with FCC Form 499‑A, obtain an FCC Filer ID, request an Operating Company Number (OCN) from NECA (475 $), and verify your NANP numbering resources. Without these items, you cannot be recognized as an authorized provider.

Step 2: Register with the STI‑PA Administrator

Iconectiv is the official STI‑PA Authority. You must create an account and provide your name, address, FCC Filer ID, OCN, and billing details. Once verified, you will receive a renewable SPC Token valid for one year, which authorizes you to request certificates.

Step 3: Obtain your STIR/SHAKEN certificate

With your SPC Token, submit a request to an approved Certification Authority (CA): provide your token, a CSR, and basic company information. The CA will issue an STI Certificate, which will be used to sign outbound calls and verify incoming calls. Annual fees generally apply.

Step 4: Register in the RMD database

All providers must register in the FCC Robocall Mitigation Database. Provide your FCC Filer ID, implementation type (Full, Partial, Gateway, Hosted), and mitigation details. If your carrier sends the signature for you, choose “Hosted”. The result is published publicly.

STIR/SHAKEN Certificate Application Checklist
Step	What you need to do	Links
Verify eligibility	• Register with the FCC and obtain a 499 Filer ID (Form 499-A) • Request an Operating Company Number (OCN) via NECA • Verify your NANP number resources	FCC Registration (Form 499-A), NECA OCN Application Information
Register with STI-PA	• Register with Iconectiv • Obtain the SPC token (valid for 1 year)	Iconectiv STI-PA – Get Started
Obtain the STIR/SHAKEN certificate	• Request the certificate from an approved Certificate Authority (CA) • Receive the STI certificate (used for signing and verification)	List of approved CAs
Register in the RMD	Provide robocall mitigation details if applicable	FCC Robocall Mitigation Database Portal

In-House STIR/SHAKEN Solution on Yeastar Cloud PBX

Once you have obtained the certificate, upload it to Yeastar Central Management. The PBX automatically signs every outgoing call and verifies incoming calls. If verification fails, predefined rules block or filter suspicious calls. All results are recorded in the CDRs for regulatory monitoring.

Configuration Summary

The P‑Series Cloud PBX handles the entire STIR/SHAKEN workflow—signing, verification, and logging—without an additional system. You save on infrastructure, meet FCC compliance requirements, and strengthen caller trust.