Airport1 Fritzbox Tools

Short name a1fbox. This is a Fritz!Box tool set by [Airport1]. E.g. parse the call monitor, phonebook handling, automated call blocking. All is still in state EXPERIMENTAL (work in progress, "API" is not final). Use at own risk.

Setup

Use pip install -r requirements.txt (depending on your OS replace the start of this line with pip3 or python3 -m pip) to install dependencies. Adjust config.py to your Fritz!Box settings (hint: you can also set "fritz.box" instead of an IP). For an example implementation run python example.py (or, depending on your OS use python3 example.py to explicitely use the Python version 3, and not 2).

Requirements

Python >= 3.6 - as e.g. f'Hello, {name}!' is used
Packages requests and json5 and [fritzconnection] by Klaus Bremer aka kbr
A Fritz!Box, reachable within your network with your credentials, and if using call monitor or blocker:
- enabled call monitor - to enable dial #96*5* - and to disable dial #96*4
- either standard or dedicated user with password (set in config.py) and enough permissions
- an additional phonebook for cold calls, configured to block incoming numbers
It is assumed you are and run this in Germany, if not, please contact me so we can adapt it to your environment

Description

Idea was to create a call blocker for cold calls. I tried to build modules that were as independent as possible, having same naming, even same logging scheme. So they could be used as building blocks, combined in different ways. So you could run the call monitor alone, but also combined with the call blocker. Or you could just do rating for phone numbers or reverse search. Or add contacts to your phonebook. Feedback is highly appreciated.

Ingredients

FritzConn: small helper to use only one FritzConnection for all modules
- config.py file defines the paramters to connect (DO NEVER COMMIT/SHARE YOUR PASSWORD!)
CallMonitor: connect and listen to call monitor on port 1012 of the Fritzbox
- CallMonitorLine: line parser and phone number anonymizer
- CallMonitorLog: optional logger for lines, either one big file or daily files
CallBlocker: listen to call monitor and check RING events
- CallBlockerLine: line parser and phone number/name anonymizer
- CallBlockerLog: optional logger for actions, either one big file or daily files
CallInfo: examine an unknown phone number for rating or naming
- CallInfoType: e.g. Tellows for scoring or RevSearch for reverse search via dasOertliche
CallPrefix: retrieve and handle own area code and country code, resolve name, using data:
- ONB: (German) "Ortsnetzbereiche", area codes for Germany for landline numbers (from BNetzA)
- RNB: (German) "Mobile Dienste, zugeteilte RNB", codes for mobile numbers (from BNetzA)
- countryio-phone / -names: country codes and names (from country.io)
CallList: is not a module or class yet!
- Examples only, how to traverse and resolve last 400 calls
Phonebook: inherited and extended from [fritzconnection]'s FritzPhonebook
- Retrieve all contacts from a phonebook, but remove internal numbers, see [fc-issue-53], [fc-issue-55]
- Find a name for a number in phonebook, even if with/without area or country code
- Add contact to phonebook, see [fc-issue-50], but Umlauts are still a pain

Autostart on a Raspberry Pi

The following is an example which works here on a Raspberry Pi 4 with Raspberry OS 32. First retrieve the (your!) correct working directory, also check if your Python3 is addressed by python3. Then enter crontab -e and add this (adapt it to your needs):

@reboot (sleep 30 && cd /home/pi/work/a1fbox && /usr/bin/env /usr/bin/python3 /home/pi/work/a1fbox/example2.py >> /home/pi/work/fb.log) &

Then do a reboot. Check e.g. with ps -elf | grep python whether it works.

Explanation: the sleeping time seems to be mandatory, otherwise the script might fail to start (e.g. no network available at first). But the full pipe is sent to background, so it should not delay the booting process. The changing into the working directory is (currently) required, so it will create the log on the correct position. Optionally you could log the output as seen into fb.log.

License

MIT

Backstage

Alternatives

If you search an alternative in PHP for automated call blocking, check out [fbcallrouter]. This project by Volker Pueschel aka blacksenator gave me some impulses.

Data folder: ONB, RNB, CountryIO

Like previous mentioned project, this uses ONB = OrtsNetzBereiche (Vorwahlbereiche/Vorwahlen) aka local area codes. The list used is from the "BNetzA" (German "Bundesnetzagentur") and should be valid for a limited period of time. If you want to update them, then download the offered CSV file (see link titled "Vorwahlverzeichnis") from [BNetzA-ONB]. Unpack the archive (there can be an archive in the archive, unpack also this) and save the file, but renamed to onb.csv, in the ./data directory.

RNB are "Mobile Dienste, zugeteilte RNB, Stand: 07.07.2021". Data was copied from https://bit.ly/3jyZBU8 now - just replace the first space or tab with a semicolon.

Country data is taken from http://country.io/data/ - http://country.io/phone.json and http://country.io/names.json - downloaded 28th June 2020, but not sure how accurate the data is.

Further numbers used in Germany: https://www.bundesnetzagentur.de/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Nummerierung/Rufnummern/Rufnummern_node.html

ONB file provided here, was originally named: NVONB.INTERNET.20210728.ONB (no change to 2020)

Further sources are noted in internal code!

Guessed parameters for call monitor types (there is no official document?)

If anyone knows an official document please tell me!

date time;RING;connection_id;caller_number;callee_number;SIP1;\n
date time;CONNECT;connection_id;extension_id;caller_number;\n
date time;DISCONNECT;connection_id;duration_seconds;\n
date time;CALL;connection_id;extension_id;caller_number;callee_number;SIP1;\n

Raw call monitor line examples, received from a Fritzbox

These are real received lines, except for the 'xxx', the comments, and 3rd or 4th line was faked. I provide those as there is nearly no documentation or examples. Again: if anyone knows an official document please tell me!

16.06.20 12:25:42;RING;0;01755290xxx;732xxx;SIP1;  # Mobile calls land line
16.06.20 12:25:46;DISCONNECT;0;0;  # After rejected or after CONNECT, last number duration?
16.06.20 15:04:02;CALL;1;13;732xxx;01755290xxx;SIP1;  # Land line calls mobile
16.06.20 15:04:02;CONNECT;0;0;01755290xxx;  # Accepting a RING by caller from mobile

16.06.20 17:55:06;RING;2;07191732xxx;69xxx;SIP0;  # In-house-call from caller 732 to callee 69
16.06.20 17:55:09;CONNECT;2;10;07191732xxx;  # Call is accepted for caller (conn_id 2)
16.06.20 17:55:09;CONNECT;1;13;69xxx;  # Call is accepted for callee (conn_id 1)
16.06.20 17:55:15;DISCONNECT;2;6;  # Caller hangs up (conn_id 2), 6 seconds duration?
16.06.20 17:55:16;DISCONNECT;1;6;  # Callee is disconnected (conn_id 1), 6 seconds duration?

16.06.20 18:11:57;CALL;1;13;732xxx;01755290xxx;SIP1;  # Land line calls mobile

17.06.20 10:28:29;RING;0;07191952xxx;69xxx;SIP0; # Call from D 952 to 69
17.06.20 10:28:43;CONNECT;0;11;07191952xxx; # Connect from D accepted, 11 (extension id 11, not seconds?)
17.06.20 10:30:31;DISCONNECT;0;109; # Disconnect after accepting and talking 109 seconds?
17.06.20 10:30:57;CALL;1;11;69xxx;952xxx;SIP0; # Re-call to D, again 11 (extension id?)
17.06.20 10:31:00;DISCONNECT;1;0;
17.06.20 10:31:08;CALL;1;11;69xxx;952xxx;SIP0; # Trying several times..
17.06.20 10:31:13;DISCONNECT;1;0;
17.06.20 10:31:24;CALL;1;11;69xxx;952xxx;SIP0;
17.06.20 10:31:27;DISCONNECT;1;0;
17.06.20 10:31:54;CALL;1;11;69xxx;952xxx;SIP0;
17.06.20 10:31:58;DISCONNECT;1;0;
17.06.20 10:32:16;CALL;1;11;69xxx;952xxx;SIP0;
17.06.20 10:32:23;CONNECT;1;11;952xxx; # D accepts call
17.06.20 10:37:34;DISCONNECT;1;312; # Disconnect after 312 seconds of talking

Fritzbox's call monitor socket at port 1012 and TCP keep-alive

As written in the article [TCP-Keep-Alive-in-Wikipedia]: "Transmission Control Protocol (TCP) keepalives are an optional feature, and if included must default to off." So, why is this important here? Because it's off by default.

If you set up the call monitor socket just without additional configuration, few OS will make the socket a dead-end after about 2 hours (see deep-dive links below).

Why dead-end? Because no more call events are received from the socket, BUT: the socket seems to be still "up and running".

The solution is easy, at least in some other languages: e.g.:

Java: socket.setKeepAlive(true);
PHP: socket_set_option($socket, SOL_SOCKET, SO_KEEPALIVE, 1);
Python: see [TCP-Keep-Alive-in-Python], unfortunately not that "pythonic" (or do you know better?)

I tried to solve it that way, but I really need feedback from Mac and Linux users if it works for them, too!

Links:

[TCP-Keep-Alive-in-Wikipedia]
[TCP-Keep-Alive-in-Python]

More links - if you want to dive deeper:

https://stackoverflow.com/questions/5686490/detect-socket-hangup-without-sending-or-receiving
https://stackoverflow.com/questions/1480236/does-a-tcp-socket-connection-have-a-keep-alive
https://stackoverflow.com/questions/667640/how-to-tell-if-a-connection-is-dead-in-python

A1fbox

Install / Use

README