Linux bluetooth development
 help / color / mirror / Atom feed
From: David Teller <dteller@mozilla.com>
To: Sebastian Hilbert <sebastian.hilbert@gmx.net>,
	linux-bluetooth@vger.kernel.org
Subject: Re: multiple headsets for voice conference
Date: Fri, 14 Oct 2016 22:23:51 +0200	[thread overview]
Message-ID: <f01abc0e-33c2-b4e8-c513-0951ee58f1a4@mozilla.com> (raw)
In-Reply-To: <5473190.yLOflKejXQ@basti-thinkpad-t410>

   Hi Sebastian,

 Newbie here: I have (very briefly) attempted to do something similar
and it was suggested to me that ofono, which is a higher-level API on
top of BlueZ, was a better starting point.

Hope this helps.

Cheers,
 David

On 14/10/16 21:59, Sebastian Hilbert wrote:
> Hi,
> 
> I was wondering if the following can be built using bluez. I would like two or 
> more people to communicate in something like a voice conference while wearing 
> BT headsets. 
> 
> I imagine that one can connect multiple BT dongles to a PC and pair each 
> headset with one dongle.
> 
> As far as I know ALSA can be used to setup the audio devices. Likely a 
> soundserver such as JACK2 can be used to manage the audio routing.
> 
> Is this the right path ? Or is there another/better way to establish a voice 
> connection between multiple headset units ?
> 
> Any pointers are appreciated.
> 
> Sebastian 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2016-10-14 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 19:59 multiple headsets for voice conference Sebastian Hilbert
2016-10-14 20:23 ` David Teller [this message]
2016-10-14 20:57   ` Sebastian Hilbert

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=f01abc0e-33c2-b4e8-c513-0951ee58f1a4@mozilla.com \
    --to=dteller@mozilla.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=sebastian.hilbert@gmx.net \
    /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