Call counters proposal (TODO patch)
I am proposing adding Call counters to Voicecall. Here is the TODO patch:
TODO +1 -0
@@ -329,6 +329,15 @@ Voicecall Complexity: C2 Owner: Pekka Pessi <[email protected]> +- 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 <[email protected]>
+
Hi Andras,
Quoted 14 lines
I am proposing adding Call counters to Voicecall. Here is the TODO patch:
TODO +1
-0@@ -329,6 +329,15 @@ Voicecall Complexity: C2 Owner: Pekka Pessi <[email protected]> +- Call counters. Provide total outgoing and incoming call durationinformation.
+ Separate call counters will be maintained for each SIM card. Call counters
TODO
Quoted 2 lines
TODO +2
-0+ 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
Hi,
2010/10/25 Marcel Holtmann <[email protected]>:
Quoted 10 lines
Quoted 10 lines
I am proposing adding Call counters to Voicecall. Here is the TODO patch:
TODO +0
-0@@ -329,6 +329,15 @@ VoicecallComplexity: C2
Owner: Pekka Pessi <[email protected]>
Quoted 9 lines
Quoted 6 lines
+- 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
Hi Aki,
Quoted 23 lines · Aki Niemi
Hi,
2010/10/25 Marcel Holtmann <[email protected]>:
Quoted 10 lines
Quoted 10 lines
I am proposing adding Call counters to Voicecall. Here is the TODO patch:
TODO +0
-0@@ -329,6 +329,15 @@ Voicecall Complexity: C2 Owner: Pekka Pessi <[email protected]>Quoted 9 lines
TODO
Quoted 6 lines
TODO +1
-0+- Call counters. Provide total outgoing and incoming call durationinformation.
+ Separate call counters will be maintained for each SIM card. Call countersTODO +2
-0+ 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.
Quoted 3 lines
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