RE: [PATCH 0/5] Call Counters (2nd)

[Marcel Holtmann <marcel@holtmann.org>]

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

Hi Kai,

> > So I am actually thinking that doing that inside PulseAudio is a lot
> > more efficient solution.
> > 
> > The idea is that PA already runs in the user session and has to monitor
> > the uplink/downlink state (and additionally could monitor call states
> > as well if needed). So it knows when a call is active and it is active
> > anyway doing the audio processing. So it could just then go ahead and
> > write your call accounting into Tracker.
> 
> Pulseaudio (or the meego PA modules for voice) isn't really an option 
> for at least the following reasons:
>  - lots of modems still handle all audio and PA will know nothing
>    about calls at all with these modems

actually Denis raised the same question, but then again this is for a
product specific requirement. And for that product we know that PA will
do the audio processing.

>  - PA does not really care about individual calls, but whether 
>    the audio traffic channel is connected or not
> 	- multi-call cases, cases were traffic channel is reconnected 
>         mid-call, etc, etc, PA simply does not know enough (and should
>         not)

And that is my point (see other email). This should be tracking talk
time and not individual call time. And thus it would be fitting nicely
into PA in that case.

> I guess this could be done in higher layers on top of oFono (telepathy-ring,
> dialer app, policy framework, etc), but I don't really know enough about
> the call timer stuff to comment on the pro/cons of this.

Important for me is to weight the extra costs of IO and CPU consumption
when doing this inside oFono. And since ofonod itself would actually not
wake up during a phone call, I think this is not a good fit.

It could be that PA is not a good candidate either, but to me it looks
like a pretty smart place to handle this.

Regards

Marcel