Re: [RFC 0/2] Add org.bluez.Telephony interface

[Frederic Danis <frederic.danis@linux.intel.com>]

Hello Claudio,

Le 22/11/2011 17:41, Claudio Takahasi a écrit :
> Hi Frederic,
>
> On Tue, Nov 22, 2011 at 12:58 PM, Frederic Danis
> <frederic.danis@linux.intel.com>  wrote:
>> Hello Andrei,
>>
>> Le 22/11/2011 15:15, Andrei Emeltchenko a écrit :
>>>>
>>>> First patch add the new org.bluez.Telephony interface and remove
>>>> functions related to AT parsing from audio/headset.c.
>>>>
>>>> Second patch remove the telephony drivers (dummy, maemo5, maemo6
>>>
>>> is this really needed?
>>>
>>> Best regards
>>> Andrei Emeltchenko
>>>
>>
>> During latest BlueZ conf, it has been decided that telephony drivers should
>> be replaced by the telephony D-Bus interface for BlueZ 5.
>
> We will need also platform specific services/plugins to implement BLE
> GATT profiles. Phone Alert Status and Alert Notification need to get/set to
> platform specific information, such as incoming call, mute once, alert
> level, ...
>
> BT SIG designed BR/EDR and BLE GATT profiles avoiding(trying) features
> "overlap". However, from the development point of view the low layer will be
> shared by both. So, please keep the code flexible enough to be used by
> more than one profile.

The new telephony D-Bus interface is just in charge of performing SDP 
publication and RFComm connection. All Telephony related code is managed 
by the agent (i.e. oFono).

I take a look to the Phone Alert Status and Alert Notification and I 
thought that this should be implemented in the agent, or in a BlueZ 
service accessible by the agent through D-Bus.

Regards

Fred

-- 
Frederic Danis                            Open Source Technology Centre
frederic.danis@intel.com                              Intel Corporation