STIR/SHAKEN is the caller-ID authentication framework for IP calls in the United States. The originating provider signs a token, the PASSporT, naming the calling number, the called number, the time and an attestation claim; the terminating provider checks that signature against the signer's certificate. The Pallone-Thune TRACED Act (47 U.S.C. 227b) directed the Federal Communications Commission (FCC) to require voice service providers to implement STIR/SHAKEN in their IP networks. RFC 8588 defines the attestation claim as A, B or C, with the meanings set in the SHAKEN standard, ATIS-1000074, published by the Alliance for Telecommunications Industry Solutions (ATIS).
Trust · Call signing
STIR/SHAKEN at Koda Voice: calls signed under our own Service Provider Code
Koda Voice LLC is an authorized STIR/SHAKEN service provider under Service Provider Code 583H, with its own Secure Telephone Identity (STI) certificate from an approved STI Certification Authority. Calls originated on Koda's network are signed under Koda's own identity, not a reseller's. Attestation A, B or C follows the SHAKEN standard, ATIS-1000074, and Koda's verification of you and your numbers.
Framework
What is STIR/SHAKEN and why do carriers sign calls?
Koda's identity
Koda's STIR/SHAKEN identity: Service Provider Code 583H and its own certificate
-
STI-PA
Authorized service provider
Authorized with the STI Policy Administrator (STI-PA), the role iconectiv holds for the United States, under Service Provider Code (SPC) 583H, which is also Koda's Operating Company Number (OCN).
-
STI-CA
Own STI certificate
Issued to Koda Voice LLC by an approved STI Certification Authority after the STI-PA cleared Koda for a token. A signature made with it traces to Koda and no one else.
-
Signing
Signed at origination, under 583H
Calls originated on Koda's network are signed under Koda's own Service Provider Code, not a reseller's certificate, with the attestation claim set by the ATIS-1000074 conditions.
Under its SPC Token Access Policy, the Secure Telephone Identity Governance Authority (STI-GA) requires a current FCC Form 499-A, an Operating Company Number and an FCC robocall-mitigation certification listed in the Robocall Mitigation Database (RMD) before a provider is cleared for certificates. Koda's Filer ID (839032), OCN (583H) and RMD listing are in the Trust Center with verification links.
Attestation
What do attestation levels A, B and C mean for your calls?
ATIS-1000074 defines three attestation levels. The originating provider decides the level; a downstream carrier cannot raise it.
| Level | ATIS-1000074 name | What the signing provider has established | What it means for your calls |
|---|---|---|---|
| A | Full attestation | Originated the call, has a direct authenticated relationship with the customer and can identify them, and has verified the customer's association with the calling number. | Koda knows who you are and has verified the number is yours to use. |
| B | Partial attestation | Originated the call and has a direct authenticated relationship with the customer, but has not verified the association with the calling number. | Koda vouches for you, not for your right to that number. |
| C | Gateway attestation | No relationship with the originator of the call, for example an international gateway. | The signer cannot say who placed the call, only where it entered its network. |
Source: ATIS-1000074, attestation-level definitions. Longer walk-through: STIR/SHAKEN attestation levels explained.
Getting to A
What does Koda need from you to sign your calls at A?
Full attestation is the outcome of verification, not a setting on the account.
- 01
Complete the Know-Your-Customer (KYC) review
Legal entity, address, an officer's identity, use case and traffic profile: the direct authenticated relationship the standard requires. See what a carrier KYC review asks for.
- 02
Call from numbers Koda can verify
Numbers provisioned or ported to your Koda account are associated with you at provisioning; numbers held elsewhere need documented authorization, such as a letter of authorization.
- 03
Originate on Koda's network
The conditions apply to the originating provider. Calls entering Koda from another provider are not Koda-originated and cannot be signed as if they were.
- 04
Keep the account in good standing
Later numbers go through the same check; the acceptable-use policy applies throughout.
When those conditions hold, Koda signs at A; when it knows the customer but cannot confirm the number, B. Koda does not promise a level ahead of verification.
Own certificate
Why does signing under the carrier's own certificate matter?
A STIR/SHAKEN signature carries the identity of whoever holds the certificate. A provider that does not hold its own certificate relies on an upstream carrier to sign, so the signature names the upstream carrier rather than the provider the customer contracted with.
Under the Federal Communications Commission's caller-ID authentication rule, 47 CFR 64.6301, a voice service provider obtains a Service Provider Code token from the STI Policy Administrator and uses it to obtain its own STI certificate; a provider that uses a third party to sign must still sign with its own certificate and make every attestation-level decision for the calls it originates. Koda's own credentials are the same three items in the same order: the STI-PA authorization, the SPC token, the certificate.
| What the verifying carrier asks | Signed under Koda's own certificate | Signed under another provider's certificate |
|---|---|---|
| Whose identity does the signature carry? | Koda Voice LLC, SPC 583H | The certificate holder's, not the provider you contracted with |
| Who decided the attestation level? | Koda, from its own KYC and number records | The certificate holder, from what it was told |
| Who answers a traceback? | Koda directly, at compliance@kodavoice.com | The certificate holder first, then the reseller, then you |
Koda is new, and that shows: every credential was issued in 2026 in Koda Voice LLC's name under the current own-certificate rule, with no inherited arrangement. The program behind the signature is described in Koda's robocall mitigation summary.
Labels
Does STIR/SHAKEN stop calls from being labeled Spam Likely?
STIR/SHAKEN does not decide whether a call is labeled Spam Likely. The signature proves which provider vouches for the calling number and how strongly, nothing about consent, calling hours or call pattern. Labels come from call-analytics engines run for the terminating carriers, which score each number on call behavior and complaints.
The signature is not a reputation score. Analytics vendors describe scoring numbers on call patterns and complaint reports, so the traffic behind the number is what you control: a stable set of calling numbers, consent from the called party, a business identity a carrier can check, and calls placed inside the 8 a.m. to 9 p.m. called-party window that 47 CFR 64.1200(c)(1) sets for telephone solicitations. See phone numbers and why calls get flagged Spam Likely.
Verify
How can you verify Koda's STIR/SHAKEN authorization?
- Search the STI-PA's Authorized Service Providers list for Koda Voice LLC. iconectiv publishes company names, not codes.
- Check the STI-GA prerequisites: Form 499 Filer ID 839032 in the FCC Form 499 Filer Database, OCN 583H and the RMD listing, all linked from the Trust Center.
- Ask compliance@kodavoice.com to arrange a signed test call to a number you control during interconnection testing, so your verification service can inspect Koda's certificate and attestation claim.
- Run the rest of the checklist in how to verify a VoIP carrier.
FAQ
Frequently asked questions
Does Koda Voice sign calls with its own certificate or a reseller's?
Koda Voice LLC signs under its own STI certificate, issued by an approved STI Certification Authority after the STI Policy Administrator authorized Koda under Service Provider Code 583H. Calls originated on Koda's network carry Koda's identity in the signature, so the certificate a terminating carrier checks is Koda's, not an upstream carrier's.
Does every call sent through Koda receive A attestation?
Attestation is decided per call against the ATIS-1000074 conditions, so no carrier can promise a level in advance. Koda signs at A when it has verified you as a customer and your authorization to use the calling number; when the number cannot be verified, it signs at B.
Does A attestation stop my calls from being labeled Spam Likely?
A attestation does not remove a Spam Likely label. The signature tells the terminating carrier that Koda vouches for your use of the number; the label comes from call-analytics engines that score call patterns and complaints. The signature is not a reputation score; consent, calling hours and consistent number use are the inputs you control.
How can I check the attestation level on my calls?
Attestation level travels inside the PASSporT that Koda attaches to calls originated on its network, in the SIP Identity header, and the terminating provider verifies it. Ask compliance@kodavoice.com to arrange a signed test call to a number you control during interconnection testing, then read the result on the terminating side. Koda can also confirm the level it applied.
Interconnect with a carrier that signs in its own name.
Tell us what you send and which numbers you call from. We come back with an interconnection plan, the KYC list and a rate deck.