From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Call counters proposal (TODO patch)
Date: Mon, 25 Oct 2010 17:19:12 -0500 [thread overview]
Message-ID: <4CC60260.7010501@gmail.com> (raw)
In-Reply-To: <AANLkTinMPwjA1bSfWtZdP8Mfx7rSENXsVNNX3T7k_HJf@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Hi Aki,
On 10/25/2010 02:43 PM, Aki Niemi wrote:
> Hi,
>
> 2010/10/25 Marcel Holtmann <marcel@holtmann.org>:
>>> I am proposing adding Call counters to Voicecall. Here is the TODO patch:
>>>
>>> diff --git a/TODO b/TODO
>>> index d9a6580..89e180c 100644
>>> --- a/TODO
>>> +++ b/TODO
>>> @@ -329,6 +329,15 @@ Voicecall
>>> Complexity: C2
>>> Owner: Pekka Pessi <pekka.pessi@nokia.com>
>>>
>>> +- Call counters. Provide total outgoing and incoming call duration
>>> information.
>>> + Separate call counters will be maintained for each SIM card. Call
>>> counters
>>> + can be read and reset to 0, and must be backed up periodically to a
>>> + non-volatile storage place.
>>
>> what is wrong with using the history plugin API and working towards a
>> bridge to get these information into tracker.
>
> I think what Andras is suggesting here are per-IMSI properties. This
> can be done as a history plugin, sure, but probably a more natural
> place would be the voicecall atom.
voicecall atom is already pretty complicated, so if possible this should
be done outside of the voicecall atom. Or does the call tracking
require access to the call state information that history api does not
provide?
Regards,
-Denis
prev parent reply other threads:[~2010-10-25 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 13:02 Call counters proposal (TODO patch) Andras Domokos
2010-10-25 14:24 ` Marcel Holtmann
2010-10-25 19:43 ` Aki Niemi
2010-10-25 22:19 ` Denis Kenzior [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=4CC60260.7010501@gmail.com \
--to=denkenz@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.