----- Message d'origine -----
do me a favor and try not to break the threading next time.
When I am away from my laptop, I use whatever MUA I can. This is obviously not deliberate
I am getting a bit sick of this secrecy. oFono is for all intense
purposes open source.
And I am sick of arguing for something as simple and obvious as exposing the call
direction in the calls list.
So if you want a proper discussion here then
please list the AT command in question.
Operator requirements are typically confidential. Since they are copyighted by their
originator, not by me or my employer, I cannot fix that. Or rather, I can try (it is
ongoing) but I cannot promise anything.
But this is only a side issue. We have a working AT commands DCE implementation that
supports both cellular/oFono stuff and all the other that we need. Open-sourcing as much
as we can is an ongoing process. I am not interested in rewriting that (and the BlueZ HFP
code) into oFono just for the heck of it.
Furthermore providing some useful features (like call direction) only via a would-be oFono
AT commands but not via the _preferred_ D-Bus interface seems silly and counter-productive