nikeee / fritz-callmonitor

Provides a Node.js wrapper for the call monitor api of the AVM Fritz!Box.

fritz-callmonitor

Provides a Node.js wrapper for the call monitor api of the AVM Fritz!Box. Written in TypeScript.

Installation

npm install fritz-callmonitor

TypeScript Usage

You need TypeScript 2. Just install the NPM package and you're ready to go!

Enabling the API

The network API is disabled by default. To use this, call #96*5* on a phone which is managed by the FRITZ!Box.

Sample

"use strict";

import { CallMonitor, EventKind } from "fritz-callmonitor";

const cm = new CallMonitor("192.168.178.1", 1012);

cm.on("ring", rr => {
	console.dir(rr);
	console.log(`${rr.caller} calling...`);
});

cm.on("call", rr => console.dir(rr));
cm.on("pickup", rr => console.dir(rr));
cm.on("hangup", rr => console.dir(rr));

cm.on("phone", evt => {
    // gets called on every phone event
    switch(evt.kind) {
        case EventKind.Ring:
        case EventKind.Call:
            console.log(`${evt.caller} -> ${evt.callee}`);
            break;
    }
});

cm.on("close", () => console.log("Connection closed."));
cm.on("connect", () => console.log("Connected to device."));
cm.on("error", err => console.dir(err));

cm.connect();

fritz-callmonitor's Issues

Symbols for Events

See title.

Can I use this script to record calls on my FritzBox 7590 FW 7.21 ?

I managed to install the script and it works. Just a question to clarify some things regarding call recording. I need to record calls. Can I do this with this script ? Or this is only for monitoring ? Ty so much !

Changed event.kind ?!

This error is thrown for Model 7490:

case _fritzCallmonitor.EventKind.Ring:
^

TypeError: Cannot read property 'Ring' of undefined
at CallMonitor. (/home/suther/scripte/fritz_callMonitor/index.js:19:14)
at emitOne (events.js:96:13)
at CallMonitor.emit (events.js:188:7)
at CallMonitor.processLine (/home/suther/scripte/fritz_callMonitor/node_modules/fritz-callmonitor/dist/fritz-callmonitor.js:34:14)
at LineStream.reader.on (/home/suther/scripte/fritz_callMonitor/node_modules/fritz-callmonitor/dist/fritz-callmonitor.js:18:43)
at emitOne (events.js:96:13)
at LineStream.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:176:18)
at LineStream.Readable.push (_stream_readable.js:134:10)
at LineStream.Transform.push (_stream_transform.js:128:32)

The event seems to changed. The response of FritzBox-Callmonitor looks now like this:

Connected to device.
{ rawData: '09.12.16 09:24:43;RING;0;017678011111;002275911111;SIP1;',
date: 2016-12-09T08:24:43.000Z,
connectionId: 0,
kind: 1,
caller: '017678011111',
callee: '002275911111' }
{ rawData: '09.12.16 09:24:43;RING;0;017678011111;002275911111;SIP1;',
date: 2016-12-09T08:24:43.000Z,
connectionId: 0,
kind: 1,
caller: '017678011111',
callee: '002275911111' }
017678013804 calling...
{ rawData: '09.12.16 09:24:45;DISCONNECT;0;0;',
date: 2016-12-09T08:24:45.000Z,
connectionId: 0,
kind: 4,
callDuration: 0 }
{ rawData: '09.12.16 09:24:45;DISCONNECT;0;0;',
date: 2016-12-09T08:24:45.000Z,
connectionId: 0,
kind: 4,
callDuration: 0 }

So:
kind 1 = incomming call
kind 4 = hangup by client
don't find any description what the other kind-states could be.

Error on startup : Unexpected token import

Node: v7.2.0

If I start the example-Script you post at npm-page, I got this error:

import { CallMonitor, EventKind } from "fritz-callmonitor";
^^^^^^
SyntaxError: Unexpected token import
at Object.exports.runInThisContext (vm.js:78:16)
at Module._compile (module.js:543:28)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.runMain (module.js:605:10)
at run (bootstrap_node.js:420:7)
at startup (bootstrap_node.js:139:9)
at bootstrap_node.js:535:3