PhoneBlock dongle New
An intelligent answering machine in the guise of an IP phone. The size of a thumb, it plugs into the router's USB port, registers as an additional SIP phone - and intercepts commercial calls before your actual phone rings. Works regardless of the router model, even without a Fritz!
In this video, you'll see in just a few minutes how to order, install, plug in, and set up the PhoneBlock dongle. The video won't load until you click on it on YouTube; when you do, your browser will send data to YouTube/Google (see Privacy Policy). Alternatively, open the video on YouTube.
The idea in one sentence
The PhoneBlock dongle logs on to your router like an additional IP phone. Every time a call comes in, it asks the PhoneBlock database at lightning speed: "Is this spam?" If so, it answers the call itself, plays a short announcement if desired and hangs up again. Your real phone has not even rung at that moment. In contrast to the cloud answering machine, all call processing takes place locally at your home.
1st call comes in
The router signals the incoming call to all registered phones—including the PhoneBlock dongle. It takes a brief moment anyway before your “real” phones actually ring—enough time for the PhoneBlock dongle to do its job.
2. flash check
The PhoneBlock dongle asks PhoneBlock at lightning speed whether the number is known to be spam. The query runs via encrypted HTTPS and only transmits a hash of the number. Calls from contacts in your phone book are not even checked - they never leave your home network.
3. get rid of it
If the number is spam, the PhoneBlock dongle picks up, plays an announcement and hangs up. The telephone in the living room remains silent. If the number is not known spam, the PhoneBlock dongle simply does nothing - the call goes through normally.
Universally applicable
The dongle runs stable with all Fritz!Box routers regardless of the telephone provider (it should also work with really old Fritz!Box models - but of course without guarantee).
The dongle runs stable on all Deutsche Telekom connections regardless of which router you use.
The dongle also works without a Fritz!Box router, but at least one of the two points must be fulfilled:
- Your router allows you to register a VOIP phone (most modern routers can do this - but the "EasyBox" from Vodafone, for example, cannot). It is best to check the operating instructions for your router beforehand.
- Your telephone provider allows the direct registration of a VOIP telephone directly to its infrastructure - then your router model does not matter. (Deutsche Telekom allows this, Vodafone does not, for example. It is best to ask your provider).
The dongle does not work on Vodafone connections in combination with an EasyBox from Vodafone.
If you run into any problems during setup or have a question, you'll find the right place to turn to below.
Are you already running Home Assistant or a Linux device like a Raspberry Pi? If so, you don't need a dongle: You can also host the software yourself.
This is where it gets practical: the instructions guide you step-by-step through ordering and setup - around €10 hardware, just a few minutes' work.
Step 1 - Order dongle
Order this USB dongle ("ESP32 developer board"). Don't worry, you don't have to "develop" anything, just install the finished PhoneBlock software from the browser.
Delivery from China - approx. 2 weeks delivery time. Price currently approx. 10 € including shipping.
These offers are in no way related to PhoneBlock and PhoneBlock is in no way involved in the profits. This is only about the hardware. You install the PhoneBlock software (firmware) yourself after receipt (see below).
No tinkering required: the "LILYGO T-Dongle-S3". Starting with firmware version 2.0, PhoneBlock also runs on the T-Dongle-S3 (ESP32-S3 with 16 MB of flash memory). It has a USB-A connector and plugs directly into the USB port on the Fritz!Box. The colored LED indicates the status, and the small display shows the PhoneBlock logo and, when a call comes in, the caller’s name.
Also supported are boards with the ESP32-C3, whose USB port is connected directly to the chip—for example, the "C3 Super Mini"—and, starting with firmware version 2.0.1, the "ESP32-S3 Super Mini" in the 16MB Flash variant (N16R8); the versions with 4 MB of flash memory are not compatible. All other variants (e.g., ESP32-S2, -C2, -C5, -C6, -H2, or -P4) are not supported: In those cases, the browser installer will terminate with the message “Your … board is not supported.”
Therefore, make sure the listing says "ESP32" (without any additional specifications), "ESP32-C3," or "ESP32-S3" with 16MB of flash memory. An ESP32-S3 with less flash memory can be flashed, but it will not boot.
Do you like to tinker and already have an ESP32 lying around in a drawer? PhoneBlock will almost certainly work on your board as well, provided it’s a standard ESP32, an ESP32-C3 with at least 4MB of flash memory, or an ESP32-S3 with 16MB of flash memory. For the ESP32-C3, the USB port must be connected directly to the chip (without a separate USB-to-serial chip); otherwise, the Wi-Fi setup in the browser won’t work. Other variants (S2, C2, C5, C6, H2, P4, …) are not supported. You may need a different USB-to-serial driver, or you may need to reconfigure the pin assignments so that the status LED flashes—for this, it’s best to check out the project page.
Step 2 - Prepare the dongle
You need to load the PhoneBlock software onto your dongle once. To do this, plug the dongle once into a free USB port on your computer. Don't have a computer? Just ask a friend if they can prepare the dongle for you. You can also set it up later in your network from a cell phone. You won't need any other devices for operation.
This browser cannot flash the dongle. To prepare your dongle for use, you need a Google Chrome or Microsoft Edge browser on a computer (not on a smartphone). Open this page with Chrome or Edge and try again.
Click on the button. The browser then asks which connected device it may address. Select the entry with "USB-SERIAL CH340" (Windows) or "USB Single Serial" or "wch.cn" (macOS/Linux) in the name and confirm with "Connect".
A list of all serial devices on the computer appears in the selection dialog. If several CH340 devices are displayed because another device with this chip happens to be connected, remove the others for the moment.
Confirm the security prompt "Install PhoneBlock dongle?" with "Install". The PhoneBlock software will now be loaded onto the dongle - this will take about a minute. Do not unplug the dongle during this time.
Computer does not recognize the dongle? Driver hints
The dongle uses the CH340 USB serial chip. Current Windows, macOS and Linux versions usually already include the driver - in this case, you don't need to do anything. However, if your computer does not display the dongle in the device selection, the following instructions will help:
Boards with an ESP32-C3 or ESP32-S3 (e.g., the T-Dongle-S3) do not require a driver: They are recognized directly as a USB device ("USB JTAG/serial debug unit").
- Windows: Download the CH340 driver from wch-ic.com, execute
CH341SER.EXEand click on "INSTALL". No restart necessary. - macOS: As of macOS Big Sur, the driver is included in the system - no installation step necessary.
- Linux: The kernel driver is built-in. On Ubuntu, the BRLTTY service may take over the CH340, so you won't see the device file—in that case, uninstalling BRLTTY will help:
sudo apt remove --purge brltty. Your user must also be a member of thedialoutgroup:sudo usermod -aG dialout $USER(on Arch Linux, the group is calleduucp). Both steps are described in detail in GETTING_STARTED.md.
Step 3 - Plug the PhoneBlock dongle into the router
When the browser reports "Installation complete!", remove the PhoneBlock dongle from the computer and plug it into a free USB port on your router (or any 5 V USB power supply within WLAN range).
Step 4 - Add the PhoneBlock dongle to the WLAN (WPS)
The PhoneBlock dongle does not yet have any Wi-Fi access data and is waiting for you to connect it to your Wi-Fi. The LED flashes quickly (about five times per second) and signals "Pairing mode active".
Now press the WPS button on the router. On the Fritz!Box, this is the "Connect / WPS" button on the top of the device - press briefly until the Wi-Fi LED on the router itself starts to flash. Other routers label the button "WPS" or "Pair". Within a few seconds, the router transmits your Wi-Fi access data to the PhoneBlock dongle, which saves it and connects.
Well done: The LED now flashes slowly (about once per second) - the PhoneBlock dongle is in the WLAN, has received an address and is waiting for configuration (next step).
Did not work Check in the router settings whether WPS is activated (on the Fritz!Box: WLAN → Security → WPS). If the WPS window was too short, the PhoneBlock dongle automatically restarts the pairing - then simply press the WPS button again.
Your WLAN does not have WPS? Some access points (e.g. UniFi) do not have a WPS button. Then enter the WLAN access data directly in the Flash dialog: Leave the PhoneBlock dongle on the computer for this (or plug it back in), click on "Flash now" at the top of step 2 and connect to the dongle - instead of a new installation, the dialog now offers "Configure Wi-Fi". Select your network from the list and enter the Wi-Fi password; the dialog will ask for it immediately after the initial installation. Then plug the PhoneBlock dongle into the router as in step 3.
Step 5 - Register as a phone and set up PhoneBlock access
In order for the PhoneBlock dongle to intercept calls, it still needs two things: your SIP access data (so that it can log in as an additional phone) and a PhoneBlock token (so that it can query the spam database). You enter both in the web interface of the PhoneBlock dongle. You can also do the rest of the setup from a cell phone.
Open in the browser:
If this link does not work, look in the device list of your router for a device with the name answerbot, make a note of its IP address and call it up in the browser - e.g. http://192.168.178.xxx/.
Enter in the web interface:
- SIP access data - user name, password and registrar address. For a Fritz!Box, create an additional connection under Telephony → Telephony devices → Set up new device → Telephone (with and without answering machine) → LAN/WLAN (IP telephone). Enter the access data assigned there here and enter
fritz.boxas the registrar. - PhoneBlock token - create an API token in your PhoneBlock settings and copy it into the corresponding field.
Save → the LED is now permanently lit → the PhoneBlock dongle is ready for use. Spam calls will now be silently intercepted before your phone rings.
Security Note: Use the dongle exclusively on your local home network. It must not be accessible from the Internet—do not set up any port forwarding or an “Exposed Host”/DMZ entry for the dongle in your router. A dongle that is accessible from the Internet will be detected and attacked by automated scanners; a password on the web interface does not protect against this, because the mere fact that it is accessible poses a risk.
Something is not working, you are using Firefox/Safari, Linux with peculiarities or another board? The detailed instructions with all options, Linux pitfalls and the ESP-IDF toolchain can be found in the repo: GETTING_STARTED.md.
Without a dongle: Self-hosting
The PhoneBlock dongle's software also runs as a Linux service on a Raspberry Pi, mini-PC, or NAS that you already have set up. The web interface, settings, and version are the same as for the ESP32 dongle; you don't need to order any hardware for this. Everything is set up in the browser, just like in Step 5.
- Home Assistant: The PhoneBlock app for Home Assistant installs the same software as an app (add-on) on amd64 and aarch64 installations. It is a community project.
- Docker: The
phoneblock/answerbot2image is available for amd64, arm64, and arm/v7. A ready-madecompose.yamlfile is available on the answering machine page. - Debian package: The APT repository provides packages for Bookworm and Trixie on amd64, arm64, and armhf.
Help and Error Reports
Mesh network with multiple Fritz!Boxes: If the dongle gets stuck on a remote Mesh box after reconnecting (the web interface is unreachable, but it’s listed as connected in the Fritz!Box), a short USB extension cable (about 30 cm) plugged into the same USB port on the router will help: This moves the dongle out of the antennas’ immediate range. The router’s USB port remains the recommended location.
It's best to ask questions about setup, routers, and internet service providers in the GitHub Discussions—other Dongle users will help you there, and the answers will remain accessible to everyone.
If something isn't working as it should, please report the issue on GitHub.
Source code of the firmware: phoneblock-dongle on GitHub.