From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 0/5] Call Counters
Date: Mon, 15 Nov 2010 17:13:10 +0100 [thread overview]
Message-ID: <1289837590.3266.125.camel@aeonflux> (raw)
In-Reply-To: <cover.1289819191.git.Andras.Domokos@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
Hi Andras,
> Here a proposal for call counters implementation for keeping track
> of the total incoming and outgoing call duration counters. Each
> established call instance is contributing to either of the call
> duration counters. The 2 counters are updated periodically when
> there is an established call and the information is stored in
> a file. The bookkeeping of the call duration counters are per IMSI
> number.
> The implementation makes use of the history framework which had to be
> expanded with a function for marking the beginning of a voice call.
> There is a D-Bus interface to call counters for reading and clearing
> the counters.
and where is the API documentation for such a D-Bus interface?
Regards
Marcel
prev parent reply other threads:[~2010-11-15 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 11:50 [PATCH 0/5] Call Counters Andras Domokos
2010-11-15 11:50 ` [RFC PATCH 1/5] history: expand history API include file Andras Domokos
2010-11-22 15:32 ` Denis Kenzior
2010-11-15 11:50 ` [RFC PATCH 2/5] history: expand history API Andras Domokos
2010-11-15 11:50 ` [RFC PATCH 3/5] voicecall: take into use the new history function Andras Domokos
2010-11-15 11:50 ` [RFC PATCH 4/5] voicecall: add call counters Andras Domokos
2010-11-22 15:34 ` Denis Kenzior
2010-11-15 11:50 ` [RFC PATCH 5/5] Makefile: add call counters to the build Andras Domokos
2010-11-15 16:13 ` Marcel Holtmann
2010-11-15 16:13 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1289837590.3266.125.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox