The Wiert Corner – irregular stream of stuff

A while ago, I documented some links for In case I ever need to record calls on my Fritz!Box devices.

By now, I’ve done a bit more investigation: I’ve enabled the call monitor, did some port scans, installed domoticz and got deeper into fritzcap.

Oh and I got packet capturing to work too: Fritz!Box – capture network packets in Wireshark format or ISDN in dtrace format.

A small recap so I don’t forget what I did and what the effects were.

Enabling CallMonitor

[WayBack] Fritzbox – Domoticz showed how to enable the CallMonitor option in your Fritz!Box

• Dial #96*5* to enable (response “CallMonitor On”)
• Dial #96*4* to disable (response “CallMonitor Off”)
• It seems not possible to ask for the current state (enabled/disabled)
• After it is enabled, the TCP port 1012 on your Fritz!Box is available for tools like [WayBack] Domoticz and fritzcap.

Checking if port 1012 is now upen

After enabling the CallMonitor, this is a short version of what nmap showed on a [WayBack] FRITZ!Box Fon WLAN 7360 running [WayBack] FRITZ!OS 06.30:

PORT STATE SERVICE VERSION
53/tcp open domain
80/tcp open http FRITZ!Box http config
443/tcp open ssl/http FRITZ!Box http config
1012/tcp open unknown
5060/tcp open sip AVM FRITZ!OS SIP
8182/tcp open http AVM FRITZ!Box WLAN 7170 WAP http config
8183/tcp open http AVM FRITZ!Box WLAN 7170 WAP http config
44123/tcp open http AVM FRITZ!Box WLAN 7170 WAP http config
49000/tcp open http AVM FRITZ!Box WLAN 7170 WAP http config
49200/tcp open http AVM FRITZ!Box WLAN 7170 WAP http config
49443/tcp open ssl/http AVM FRITZ!Box WLAN 7170 WAP http config
57336/tcp open http AVM FRITZ!Box WLAN 7170 WAP http config

It means the port 1012 is now open.

Installing Domotics

[WayBack] Domoticz (Domoticz is a lightweight Home Automation System) is available for openSuSE:

Add repository and install manually

For openSuSE Tumbleweed run the following as root:

zypper addrepo http://download.opensuse.org/repositories/home:Guillaume_G/openSUSE_Tumbleweed/home:Guillaume_G.repo
zypper refresh
zypper install domoticz

For openSuSE Factory ARM run the following as root:

zypper addrepo http://download.opensuse.org/repositories/home:Guillaume_G/openSUSE_Factory_ARM/home:Guillaume_G.repo
zypper refresh
zypper install domoticz

[WayBack] software.opensuse.org: Install package home:Guillaume_G / domoticz

fritzcap

I did some more research:

If I go for fritzcap:

• [Archive.is] fritzcap: Tool für Etherreal Trace und Audiodaten-Extraktion v2.0
• [Archive.is] fritzcap: Tool für Etherreal Trace und Audiodaten-Extraktion v2.0 – Seite 15
• [Archive.is] fritzcap: Tool für Etherreal Trace und Audiodaten-Extraktion v2.0 – Seite 14 – needs extra steps for configuration other than default no-user configuration (i.e. only password, no username)
• [Archive.is] fritzcap: Tool für Etherreal Trace und Audiodaten-Extraktion v2.0 – Seite 11 – when the box is not named fritz.box
• [Archive.is] [Gelöst] LAN-LAN-Koppelung mit nur 1 öffentlichen IP – Seite 3 – how to store the capture locally
• [Archive.is] fritzcap FritzBox trace helper tool Project objectives
  • [Archive.is] fritzcap – issue #1
  • [Archive.is] fritzcap – issue #2
  • [Archive.is] fritzcap – issue #3
  • [Archive.is] fritzcap – issue #4

The Python fritzcap was cloned from Google Code code.google.com/archive/p/fritzcap/ to github  github.com/elpatron68/fritzcap (including migration of issues from Google Code).

To fix a few things, I have forked it to github.com/jpluimers/fritzcap which you can get through a git clone https://github.com/jpluimers/fritzcap.git

Initial tests showed it didn’t fully work in my situation, so I filed some issues in my repository and try to fix them while learning Python (as the issues on Google Code were still open). Hopefully those are fixed by the time this scheduled post is published.

–jeroen