From: Markus Adolfsson <markus.adolfsson@free2move.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Troubles with mulitple SCO connections (duplex)
Date: Wed, 04 Apr 2007 10:24:20 +0200 [thread overview]
Message-ID: <461360B4.1030509@free2move.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1459 bytes --]
Hi all,
I'd like to establish two SCO connections simultaneously using BlueZ
from my "coordinator" application that in the long run will connect /
mix the two SCO connections to let two headsets hear each other, as well
as letting the master controller-application I'm writing to hear both
headsets...
The app itself is fairly straight forward and I've gotten everything to
work properly besides one little tiny detail - One SCO connection works
fine, but once I connect the second SCO connection, all SCO connections
goes down (without any error from the socket / connect commands)...
Both SCO-connections are still there, the headsets only hear "noise" and
I have the fealing that the two headsets don't send any audio, but that
they _do receive_ on the SCO connections... Strange!
Is this a packet-type issue and if so - how can I set the packet-types
from "within" the BlueZ lib / my app?
Regards,
/Markus Adolfsson
--
------------------------------------------------------------------------
*Markus Adolfsson*
M.Sc.CE. Product Development
Mail: markus.adolfsson@free2move.net
<mailto:markus.adolfsson@free2move.net>
Phone: +46 35 152268 <callto:+4635152268>
Mobile: +46 707 165296 <callto:+46707165296>
*Free2move AB* -- /WIRELESS MADE EASY/
Phone: +46 35 152260 <callto:+4635152260>
Fax: +46 35 152269 <callto:+4635152269>
Web: www.free2move.net <http://www.free2move.net>
Address: Sperlingsgatan 7
SE-30248 Halmstad
Sweden
[-- Attachment #1.2: Type: text/html, Size: 2994 bytes --]
[-- Attachment #2: markus.adolfsson.vcf --]
[-- Type: text/x-vcard, Size: 269 bytes --]
begin:vcard
fn:Markus Adolfsson
n:Adolfsson;Markus
org:Free2move;Product Development
adr:;;Sperlingsgatan 7;Halmstad;;302 48;Sweden
email;internet:markus.adolfsson@free2move.net
title:M.Sc.C.E.
tel;work:+46 35 152268
url:http://www.free2move.net
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-04-04 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 8:24 Markus Adolfsson [this message]
2007-04-04 11:40 ` [Bluez-devel] Troubles with mulitple SCO connections (duplex) Jose Vasconcellos
2007-04-04 13:46 ` Markus Adolfsson
2007-04-04 14:06 ` Brad Midgley
2007-04-04 14:32 ` Markus Adolfsson
2007-04-11 8:16 ` Markus Adolfsson
2007-04-11 8:21 ` Mayank BATRA
2007-04-11 8:36 ` Markus Adolfsson
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=461360B4.1030509@free2move.net \
--to=markus.adolfsson@free2move.net \
--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