From: "Jonas Tsang" <d99jots@stud.hh.se>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Using two sco-channels
Date: Wed, 22 Oct 2003 18:44:06 +0200 [thread overview]
Message-ID: <001301c398bb$b5aa9eb0$0300a8c0@neonmura> (raw)
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
Hi,
I'm trying to make an easy application to connect a bt-device with two different headsets through sco-channels. The application is mainly based on hstest. Connection to the first headset works fine, but as soon as I try to open another sco-channel to the 2nd headset, it fails.I get an error message saying: "address already in use". I found that an error occurs when I try to bind a new socket to the same source-address (the bt-device). Does anyone know if it's possible to use two sco-channels simultaneously? (I'm not using any bluetooth USB dongle and creating two different RFCOMM-channels works fine.) Any suggestions?
Thanks in advance.
/Jonas
[-- Attachment #2: Type: text/html, Size: 1269 bytes --]
next reply other threads:[~2003-10-22 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 16:44 Jonas Tsang [this message]
2003-10-22 18:59 ` [Bluez-devel] Using two sco-channels Marcel Holtmann
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='001301c398bb$b5aa9eb0$0300a8c0@neonmura' \
--to=d99jots@stud.hh.se \
--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