SipShield signs every call your switch originates with the correct A, B, or C attestation — driven by real KYC data, not guesswork. Stay in the Robocall Mitigation Database and keep your downstream interconnects intact.
The FCC requires originating VSPs to attest to the calls they sign. Get it wrong and your traffic gets blocked downstream. SipShield decides the correct level from your customer's KYC record, LOA, and number-ownership data — call by call.
You authenticated the customer, you assigned the number, and the customer is authorized to use it. Reserved for verified enterprise DIDs and known KYC-cleared traffic.
You authenticated the customer but cannot verify the calling number belongs to them (e.g. BYOC or trunk with unverified DIDs).
You are handing off traffic from an upstream provider you cannot fully authenticate. Common for international gateway calls.
We tie each attestation decision to the customer's KYC record so you can defend every signed call in an audit.
Sign INVITEs at line rate using your STI-CA certificate. No changes to your softswitch required.
Non-IP hops (TDM interconnects, legacy trunks) still get signed and verified via the SHAKEN out-of-band CPS.
Auto-downgrade attestation when a customer fails a re-KYC or a number falls out of their LOA — before a carrier complains.
Every signing event stored with attestation level, PASSporT, and KYC snapshot. Export directly into your Robocall Mitigation Plan.
Automated LOA / RespOrg / 499-A checks so you know when a customer can legitimately claim a DID.
Downstream carriers are legally required to block traffic from originating providers that misattest or fail to maintain a valid Robocall Mitigation Plan. Getting attestation wrong — even in good faith — puts your entire wholesale relationship at risk.
SipShield turns attestation from a manual, error-prone policy decision into a signed, logged, and defensible event that ties back to real customer identity data. That's the difference between a warning letter and a Section 214 revocation.