Linux bluetooth development
 help / color / mirror / Atom feed
From: Sebastian Hilbert <sebastian.hilbert@gmx.net>
To: linux-bluetooth@vger.kernel.org
Subject: multiple headsets for voice conference
Date: Fri, 14 Oct 2016 21:59:19 +0200	[thread overview]
Message-ID: <5473190.yLOflKejXQ@basti-thinkpad-t410> (raw)

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 

             reply	other threads:[~2016-10-14 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 19:59 Sebastian Hilbert [this message]
2016-10-14 20:23 ` multiple headsets for voice conference David Teller
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=5473190.yLOflKejXQ@basti-thinkpad-t410 \
    --to=sebastian.hilbert@gmx.net \
    --cc=linux-bluetooth@vger.kernel.org \
    /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