DEV Community

FilterMyCalls
FilterMyCalls

Posted on Originally published at filtermycalls.com

STIR/SHAKEN, Carrier Apps, and Smartphones: What Each Layer Actually Stops

"We have all this technology — why do scam calls still get through?" The honest answer: every layer in the anti-robocall stack catches a specific slice of traffic, and the documented gaps are the design, not footnotes. No system catches every unwanted call, and the regulators and vendors say so themselves.

STIR/SHAKEN — what the signature does and does not prove

The FCC's caller-ID authentication regime (mandated from June 2021) attaches an encrypted attestation token to IP-based call setup — full, partial, or gateway-level. What it does not do is authenticate the caller's honesty: the signature vouches for the originating carrier, so a digitally signed call can still carry a spoofed number. Signatures cannot travel over legacy network segments, and a complicit provider willing to sign bad traffic can defeat the scheme — which is why the FCC added token revocation and robocall-mitigation-plan enforcement.

Carrier tools — network blocking, labeling, and the apps

FCC rules let providers auto-enroll customers in network-level blocking with an opt-out; calls from unassigned or invalid numbers and Do-Not-Originate numbers can be blocked outright, while analytics-based blocking requires an opt-out. The consumer apps ride on top: AT&T ActiveArmor offers fraud-call blocking and nuisance alerts; T-Mobile's network-level tools put "Scam Likely" labels on suspect calls; Verizon's Call Filter flags spam and can route high-risk calls to voicemail. The FCC's own guide notes most major carriers provide some free screening and does not endorse any listed product.

Smartphones — silence, screen, and live voicemail

On iPhone, Silence Unknown Callers sends numbers outside Contacts and recent calls straight to voicemail while logging them, and Live Voicemail transcribes an unknown caller's message on screen. On Android, the Phone app's caller ID and spam protection is on by default with "Suspected spam caller" warnings, and Google's Call Screen answers unknown calls on-device to ask who is calling and why. Built-in tools reduce interruptions; they do not verify intent.

Third-party apps — databases, answer bots, and tradeoffs

Independent apps work from large spam databases, community reports, and increasingly answer bots that question unknown callers before your phone rings. The tradeoffs are real: number rotation outpaces blocklists, and database apps only know numbers already reported. Review privacy policies before installing — some apps request contacts access.

Why spoofing keeps the pipeline open

Spoofing is free and unlimited: any name or number can appear on the screen, including local-looking ones — neighbor spoofing copies your area code and first digits precisely so the call feels familiar. Labeling and blocking catch reported numbers; spoofed fresh numbers walk past them.

How to stack the layers without over-trusting any

  • Let network blocking and labeling handle the known-bad traffic.
  • Use your phone's silence/screening built-ins for the unknown middle.
  • Screen what remains: ask who is calling and why before the phone rings.
  • Verify every sensitive request with a callback you initiate to a known number.
  • Report what gets through — reports feed blocklists, tracebacks, and enforcement.

Full guide with all sources: STIR/SHAKEN, Carrier Apps, and Smartphones: What Actually Stops What

Top comments (0)