MMM-FRITZ-Box-Callmonitor

garbleflux

@Sandy2503 thank you for your kind reply. I already did create a useraccount. But with this data (User: raspi, password: xxxxxxxx) I do not have an access. So it is neccessary to disable the general Fritz!box password? Regards Mike

Sandy2503

Have you edit the fritz.box config ? I mean like in post #1.

rf0620

Like some other people here I wasn’t able to to read out the content of any phonebook from fritzbox. Only phone numbers were presented.
Also the command line didn’t work:

“python fritz_access.py -p password -u user -i ip-of-fritzbox”

Traceback (most recent call last):
File “fritz_access.py”, line 77, in
main(args)
File “fritz_access.py”, line 63, in main
handle.download_phone_book()
File “fritz_access.py”, line 22, in download_phone_book
result = self.fc.call_action(“X_AVM-DE_OnTel”, “GetPhonebookList”)
File “/usr/local/lib/python2.7/dist-packages/fritzconnection/fritzconnection.py”, line 405, in call_action
action = self._get_action(service_name, action_name)
File “/usr/local/lib/python2.7/dist-packages/fritzconnection/fritzconnection.py”, line 378, in _get_action
raise ServiceError('Unknown Service: ’ + service_name)
fritzconnection.fritzconnection.ServiceError: Unknown Service: X_AVM-DE_OnTel:1

Today I found a very simple answer: The used protocol TR-064 wasn’t activated on my fritz box!
According to this site I had to enable support for it. It worked for my FBF 7390 immediately. This setting has a different location than user mangament on current firmware versions.

Zinkeler

Hello,
can someone tell me if it´s possible to sort the Output?
E.g. i see a call 3 days ago in the first line, then a call from 2 hours ago (second line), a call 2 day ago in 3rd line,…
I would like to see the youngest in the first line and the oldest in the last line.
Thanks for hints.

barnosch

@paviro
i have the problem currently that
MMM-FRITZ-Box-Callmonitor is not working anymore.
So the overlay when someone calls is not showing anymore.

The current call works without problems.
Nothing was changed. No idea what happened.
Fritzbox settings wasn’t changed nor a firmware upgrade was done

What do i need to check?

2fingers

@rf0620 i have tried to install the module and i had unnbekannte fehler (unknown issue) error . i followd all the steps but i have another error now:

pi@raspberrypi:~ $ sudo pip install fritzconnection --upgrade
Requirement already up-to-date: fritzconnection in /usr/local/lib/python2.7/dist-packages
Collecting requests>=2.2.0 (from fritzconnection)
Downloading requests-2.18.4-py2.py3-none-any.whl (88kB)
100% |████████████████████████████████| 92kB 763kB/s
Collecting lxml>=3.2.5 (from fritzconnection)
Using cached lxml-4.1.1.tar.gz
Collecting urllib3=1.21.1 (from requests>=2.2.0->fritzconnection)
Downloading urllib3-1.22-py2.py3-none-any.whl (132kB)
100% |████████████████████████████████| 133kB 880kB/s
Collecting idna=2.5 (from requests>=2.2.0->fritzconnection)
Downloading idna-2.6-py2.py3-none-any.whl (56kB)
100% |████████████████████████████████| 61kB 1.5MB/s
Collecting chardet=3.0.2 (from requests>=2.2.0->fritzconnection)
Downloading chardet-3.0.4-py2.py3-none-any.whl (133kB)
100% |████████████████████████████████| 143kB 983kB/s
Collecting certifi>=2017.4.17 (from requests>=2.2.0->fritzconnection)
Downloading certifi-2017.11.5-py2.py3-none-any.whl (330kB)
100% |████████████████████████████████| 337kB 629kB/s
Building wheels for collected packages: lxml
Running setup.py bdist_wheel for lxml … /^error
Failed building wheel for lxml
Running setup.py clean for lxml
Failed to build lxml
Installing collected packages: urllib3, idna, chardet, certifi, requests, lxml
Found existing installation: urllib3 1.19.1
Not uninstalling urllib3 at /usr/lib/python2.7/dist-packages, outside environment /usr
Found existing installation: idna 2.2
Not uninstalling idna at /usr/lib/python2.7/dist-packages, outside environment /usr
Found existing installation: chardet 2.3.0
Not uninstalling chardet at /usr/lib/python2.7/dist-packages, outside environment /usr
Found existing installation: requests 2.12.4
Not uninstalling requests at /usr/lib/python2.7/dist-packages, outside environment /usr
Found existing installation: lxml 3.7.1
Not uninstalling lxml at /usr/lib/python2.7/dist-packages, outside environment /usr
Running setup.py install for lxml … |^canceled
Can’t rollback lxml, nothing uninstalled.
Operation cancelled by user

Cyberdyne

Please read this befor you update your Fritzbox with a new FritzOS!

I upgraded my Fritzbox 6490 to the new FritzOS 7 and the callmonitor stoped working. I tried to but I could not reactivate the callmonitor. Nothing seemed to work and I thought I did something wrong. I contacted AVM to help and got a realy bad answer: They told me that AVM has removed the callmonitor functionality. I asked them how I could downgrade the OS to get the functionality back but they told me that there is no downgrade option. They also told me that they are going to remove the callmonitor functionality from all of their routers OSs.
Warning to everyone: If you want to keep on using the callmonitor do not install FritzOS updates without checking if the new OS still supports the callmonitor. I would aks AVM befor updating.

I am not sure if it helps but maybe everyone should write them an email and ask to keep or bring back this feature?!

With this plugin I now can only see incomming calls (only the number) but no list with history of calls anymore. :o(

Sandy2503

@Cyberdyne - Hmmmm thats strange. I am using a 7590 with the actual AVM OS7.01 from 20th September (and early Beta Versions) and the Call Monitor and Current Call works (with the 7590 and 7490) very well …

Sandy2503

Cyberdyne

I can only say what AVM has told me. Callmonitor is removed from the 6490 with the OS 7.0 and they also told me that they will remove it from all other boxes as well. They did not tell me in which version on which box. Hete are some emals:

"Sie schildern, dass Sie den Callmonitor nicht mehr aktivieren können und möchten wissen, wieso dies der Fall ist. Ich bedauere diesen Umstand und nehme mich gerne der Sache an.

Der Callmonitor wird mittlerweile nicht mehr von den FRITZ!Boxen unterstützt. Wenn Sie mit mitteilen, was genau Sie vorhaben, kann ich Ihnen ggf. Alternativen aufzeigen. "

"Sie möchten wissen, bei welchen FRITZ!OS der Callmonitor noch unterstützt wird und wie Sie Ihre FRITZ!Box 6490 entsprechend downgraden können. Gerne beantworte ich Ihnen Ihre Frage.

Ab welchen FRITZ!OS der Collmonitor nicht mehr unterstützt wurde, kann ich Ihnen nicht sagen, da dieser aufgrund der unterschiedlichen FRITZ!OS der verschiedenen FRITZ!Box-Modellen sukzessiv geschehen ist.

Ein Downgrade von dem FRITZ!OS bei FRITZ!Box Cable ist leider nicht möglich."

Just be carefull and better ask befor you make an other update if you want to keep on using the callmonitor! It does not work here anymore and no way back. :(

darklight89

Hi guys,
how can I hide the call history, since the Fritz-Boxes Callmonitor seems to be deactivated in OS 7 and I want to keep at least the alert pop-up.