From: Arnaud Mouiche <arnaud.mouiche@invoxia.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: HFP gateway and new incoming connection
Date: Tue, 23 Aug 2011 11:08:15 +0200 [thread overview]
Message-ID: <4E536DFF.8050205@invoxia.com> (raw)
In-Reply-To: <CABBYNZLEkc8FWmJm9hU_n-KL2mhWeWPcUfxqX1jskH8ubU-aMw@mail.gmail.com>
Hi,
On 08/22/2011 09:58 PM, Luiz Augusto von Dentz wrote:
> [...]
> Yep, we have some plans to move the Agent registration to adapter
> path, so it gonna be per adapter. This is necessary to set the
> features bit properly in the record and probably gonna support both
> roles (with different agents). My initial idea was to use Media API,
> but perhaps is confusing since HFP is not entirely about audio but
> call control too (mostly) so perhaps we gonna have a different
> interface for it e.g. org.bluez.Telephony, in addition to that we are
> planning to pass the endpoint bus and path together in the
> NewConnection so the telephony agent (oFono) can communicate directly
> to endpoint in use (PulseAudio).
>
> Those are my plans, but none of this is set in stone and Im pretty
> open for ideas
>
what about using the org.bluez.Adapter / RegisterAgent API, and add:
- the possibility to setup multiple agents (maintain a list of agents)
- use the "capability" field as a filter definition to find the good
agent for the particular request
ex:
audio/gateway.c::agent_sendfd() will look for a agent in the list,
with a "HFP" capability to send the "NewConnection" request
Arnaud
next prev parent reply other threads:[~2011-08-23 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 16:48 HFP gateway and new incoming connection Arnaud Mouiche
2011-08-22 17:49 ` Gustavo Padovan
2011-08-22 19:58 ` Luiz Augusto von Dentz
2011-08-23 9:08 ` Arnaud Mouiche [this message]
2011-08-23 11:14 ` Luiz Augusto von Dentz
2011-08-23 11:53 ` Arnaud Mouiche
2011-08-24 11:03 ` Luiz Augusto von Dentz
2011-08-25 8:37 ` Arnaud Mouiche
2011-08-26 14:35 ` Frederic Danis
2011-08-26 14:39 ` Frederic Danis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E536DFF.8050205@invoxia.com \
--to=arnaud.mouiche@invoxia.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).