Recent STIR/SHAKEN statistics

We’ve looked at call statistics from our ClearIP customers for the last 45 days to see whether they’re getting many calls that were signed using STIR/SHAKEN. Here’s what we found.

Verification statuses

What proportion of terminated calls were signed? Of the signed calls, were there any verification errors?

Of the calls received by ClearIP customers, fewer than 3% had a PASSporT.

Most of the PASSporTs with a verification status of Certificate chain error were signed with a self-signed certificate.

Most of the PASSporTs with a verification status of Calling number mismatch had a valid number in the orig claim of the PASSporT but had anonymous in the From and/or P-Asserted-Identity header.

Most of the PASSporTs with a verification status of Invalid info parameter in Identity header had an info paramater that contained an HTTP URL instead of an HTTPS URL.

Attestation levels

What attestation levels are originating service providers using?

Of the successfully verified calls received by ClearIP customers, more than 98% had an attestation level of A.

SHAKEN call proportions by originating service provider

Which originating service providers are sending signed calls? Of all successfully verified calls received by ClearIP customers, which OSPs originated the most signed calls?

Note that the above data reflect both call volume and SHAKEN activity. The data show the proportion of successfully verified calls received by ClearIP customers for each originating service provider as a percentage of all successfully verified calls. If a small number of calls were received from an originating service provider, then percentage of successfully verified calls received by ClearIP customers would be low, even if the originating service provider signed a high percentage of their outbound calls.

The above data include only originating service providers that had at least one successfuly verified call received by a ClearIP customer.

Certificate repositories

What are typical certificate latencies, i.e., time-to-fetch, and why?

Retrieving a certificate from a certificate repository takes time, or latency, which increases Post-Dial Delay (PDD). If a certificate is cached by the STI-VS, then it does not need to be retrieved.

A certificate repository can be configured to provide a Cache-Control HTTP header, which tells the STI-VS how long to cache the certificate after retrieving it. If a certificate repository does not provide the Cache-Control header, the STI-VS does not cache the certificate or caches the certificate for only a short time.

Note that the ClearIP STI-VS caches certificates for 60 minutes if the Cache-Control header is not set by the certificate repository or if the Cache-Control header contains a value of less than 60 minutes.

Summary

• Fewer than 3% of calls were signed.
• Fewer than 0.75% of signed calls had verification errors.
• More than 98% of successfully verified calls had an attestation level of A.
• Successfully verified calls were received from 26 originating service providers.
• 60% of certificate repositories did not include the Cache-Control header.

TransNexus solutions

We offer STIR/SHAKEN and robocall mitigation solutions in our ClearIP and NexOSS software platforms. We can make your STIR/SHAKEN deployment a smooth process.

In addition, we help service providers with all aspects of STIR/SHAKEN deployment, including registering with the Policy Administrator and filing their certification with the FCC.

Contact us today to learn more.