linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Puchol <mpuchol@sonar-security.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Multiple headsets with one dongle
Date: Fri, 13 Jan 2006 01:50:51 +0100	[thread overview]
Message-ID: <43C6F96B.6080402@sonar-security.com> (raw)

Hi everyone,

Firs, I'd like to introduce myself, having just joined the list. I'm the 
hardware engineer at Southwing, a Barcelona-based company that develops 
Bluetooth headsets and carkits. We do both software and hardware design 
in-house. We have a decent lab, and quite a nice range of phones, 
dongles and headsets for testing. Most of our designs are based on the 
BC3 AudioFlash, and now we're dwelling into the SiW3500 now, plus the 
BC4 External. As far as coding goes, I can understand C code, cannot 
really write it without following examples, and could modify code to do 
simple things.

I haven't studied the Bluetooth specs fully (not enough time!), but I 
have begun playing with Asterisk, a BT dongle and a couple of headsets.

Asterisk is configured OK, with a 2.6 kernel on a CentOS 4.2 distro, 
chan_bluetooth is working just fine, as is the BT stack. I have managed 
to have two headsets paired with the dongle, and thus visible to 
Asterisk, and either of them answer an incoming call, or dial a preset 
number, but what I haven't been able to get working is one headset 
calling the other. Well, actually, it *does* work, but the audio is 
totally unusable.

 From what I have been able to gather so far, the headsets are using 
RFCOMM channel 2 (sdptool search --bdaddr 0x111E), and so when both are 
communicating with the dongle at the same time, they most likely are 
interfering each other. My questions are:

1. Am I correct in thinking the RFCOMM channel is derived from the BT 
address/MAC? If so, I could change the MAC of one of the headsets so 
that it would use a different hop sequence.

2. If 1) is incorrect, *where* is this RFCOMM channel configured in the 
CSR pskeys?

3. The dongle, configured as master, *should* support up to three slaves 
using the handsfree profile?

Best regards,

Mike


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2006-01-13  0:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13  0:50 Michael Puchol [this message]
2006-01-13 17:10 ` [Bluez-devel] Multiple headsets with one dongle Brad Midgley
  -- strict thread matches above, loose matches on Subject: below --
2006-01-12 13:58 [Bluez-devel] AVDTP in BlueZ Martin Raspaud
2006-01-13 20:34 ` Brad Midgley
2006-01-13 22:54   ` [Bluez-devel] Multiple headsets with one dongle Southwing - Miquel Puchol

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=43C6F96B.6080402@sonar-security.com \
    --to=mpuchol@sonar-security.com \
    --cc=bluez-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).