Call counters proposal (TODO patch)

Call counters proposal (TODO patch)

[Andras Domokos]

[-- Attachment #1: Type: text/plain, Size: 630 bytes --]

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.
+
+  Priority: Medium
+  Complexity: C2
+  Owner: Andras Domokos <andras.domokos@nokia.com>
+

Re: Call counters proposal (TODO patch)

[Marcel Holtmann]

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

Hi Andras,

> 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 did propose to use obexd for this task since it already has to handle
call history for PBAP anyway and it has a different backends already. So
if you don't wanna use tracker you can use EDS or others.

Regards

Marcel

Re: Call counters proposal (TODO patch)

[Aki Niemi]

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

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.

Cheers,
Aki

Re: Call counters proposal (TODO patch)

[Denis Kenzior]

[-- 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