A Firewall for Incoming Calls
TL;DR β¨
In networking, a firewall controls which traffic is allowed, denied, or inspected. The same mindset works surprisingly well for mobile calls.
Outgoing calls are usually less problematic because you are the one initiating them. Incoming calls are where the mess starts: spam, annoying sales calls, unknown foreign numbers, and general noise.
βοΈ Why Think About Calls Like a Firewall¶
In networking, a firewall controls which traffic is allowed, denied, or inspected. The same mindset works surprisingly well for mobile calls.
You can split phone communication into two basic flows:
- outgoing calls
- incoming calls
Outgoing calls are usually less problematic because you are the one initiating them. Incoming calls are where the mess starts: spam, annoying sales calls, unknown foreign numbers, and general noise.
So instead of treating the phone dialer as an untouchable default, the article approaches it like a tiny policy engine.
π€ Outgoing Calls¶
The default rule for outgoing calls is basically:
- allow all
That is normally fine because the phone is under your control and protected by lock screen security anyway.
The interesting improvement is not blocking outgoing calls, but logging and recording them better.
The original setup suggested an Android call recording app and then tuning a few basics:
- Connect cloud storage if you want to archive important recordings.
- Increase inbox size so you keep a larger call history.
- Define filters for contacts you do not want to record.
The broader point is simple: for outbound communication, the useful layer is usually visibility, not denial.
π₯ Incoming Calls¶
Incoming calls are where filtering matters much more.
GeoIP-Style Filtering for Phone Numbers¶
The recommendation here was to create a country-based allowlist:
- allow prefixes from countries that matter to you
- block the rest by default
That is not true GeoIP in the strict network sense, but for phone calls it is a practical equivalent: use international dialing prefixes as a coarse geographic filter.
The original article used an Android blacklist app to:
- enable blacklist mode
- block all calls by default
- define exceptions through a whitelist
Then, in the whitelist, you add prefixes you actually want to receive calls from.
For example, if you want to allow calls from the Czech Republic, you can whitelist numbers beginning with +420.
This kind of setup is not perfect, but it is effective if you already know the geographical scope of calls you actually care about.
Scheduler-Based Hardening¶
The filtering can be pushed further with time-based rules.
For example:
- allow normal calls only during working hours
- block everything else except trusted numbers
That turns your phone into something closer to a policy-driven endpoint instead of a permanently open interruption machine.
π¨ Community Spam Detection as a Small IDS¶
The last layer in the original setup used a community-driven spam-number database through the Czech app Nevolejte.cz.
The idea is similar to a lightweight intrusion detection system:
- known bad or suspicious callers are pre-flagged
- the app warns you before you answer
- you can choose whether to block outright or only warn
The conservative recommendation was sensible:
- do not blindly block everything
- prefer warning mode unless you really trust the quality of the shared database
That avoids overblocking and gives you a chance to judge ambiguous cases yourself.