Call fboxIncomingCall “Incoming call: [%1$s to %2$s]” { fritzboxtr064=“callmonitor_ringing” }
I can’t see any log message of the call monitor being started on starting openHAB, however. Neither can I see an open connection to the FritzBox in netstat output apart from the TR64 connection:
You should see a log entry in your openhab log like
2016-05-13 08:20:33.033 [INFO ] [.service.AbstractActiveService] - FritzboxTr064 Refresh Service has been started
I don’t use call monitoring, but according to the wiki you have to set:
Enable TR064: In the webui goto “Heimnetz” -
“Netzwerkeinstellungen”: enable option “Zugriff für Anwendungen
zulassen” (enabled by default)
Only if you want to use the call monitor feature (items starting
with callmonitor_…), enable the interface by dialing #965 You may
disable it again by dialing #964
I followed all the steps documented in the wiki. I had it working with the old fritzbox binding. I also have the message you posted above in my log, I would expect to see a log message telling me that a connection to the call monitor port has been opened though. (TCP/1012)
I have version 6.51 installed on the 7490. I had the call monitor running since a few weeks ago while running the Fritzbox on version 6.50. If I recall correctly AVM removed telnet before 6.50. Furthermore the call monitor is not using telnet acess, but an officially supported service of the FritzBox using a specific port.
If I connect to the port by telnet I can see calls coming in:
Ralphs-MacBook-Pro-2:Downloads ralle$ telnet 192.168.x.y 1012
Trying 192.168.y.x…
Connected to fritzbox
Escape character is ‘^]’.
16.05.16 10:54:36;RING;0;017xxxxxxx;35xxxxxx;SIP0;
I still think the only thing missing here to make it work as it did before is openhab connecting to the call monitor port of the fritz box.
Hi,
I encountered the same problem.
In the end I decided to write a short shell script and use the exec binding.
Works for me although I would prefer to use the “official” Fritzbox-tr64 binding.
Cheers
Björn