From: robert <rbscott@cadvium.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] handsfree or headset support on pc
Date: Thu, 13 Sep 2007 23:22:34 -0700 [thread overview]
Message-ID: <FC45259F-96B7-4513-B655-21C1AE4867CC@cadvium.net> (raw)
In-Reply-To: <b5fcf2320709132217x50ce9cbbsb55bd39b4239db80@mail.gmail.com>
so here is a sample of the c part that I am writing. (from your
description, it seems that you and I are doing something similar).
This is a pretty primitive code sample, and there are examples
(probably better) in bluez-utils that do similar things.
Furthermore, this presently only handles the speaker, not the mic.
The second part is an easy addition.
http://www.cadvium.net/files/source/sco-manager.tar.gz
gpl
> make
## basically, you start it up with a file. (the bluetooth address is
ignored but should be formatted properly).
> sco-manager <bluetooth-address> <file-name>
This will listen for an sco connection on the first bluetooth device
that it finds. It will then take any data that it receives and write
it into the file specified on the command line. (I think it also
generates a tonne of debugging too).
This is more useful if you specify a pipe for the file:
> mkfifo test.sco
## Setup voice correctly
> sudo hciconfig hci0 voice 0x0060
> cat test.sco | aplay -f S16 &
> sco-manager <bluetooth-address> test.sco
At this point, if you make a call, it will send the audio through out
your speakers. (Make sure to turn them down, if something isn't
setup properly it makes a terrible noise).
hope this helps,
--robert
On Sep 13, 2007, at 10:17 PM, andrey larin wrote:
> ok here is what i think:
> there is no problem to create and communicate rfcomm
>
> i don't know what connection must be make to control the audio
> ( special rfcomm to audiogateway on phone or usual rfcomm to ssp
> on phone)
>
> must unreserched area is how to handle the audio managment ( open,
> support ,close, route audio from pc microphone to phone ,from phone
> to pc speakers)
>
>
> so
>
> when i connect on my phones spp
> and make call to my cell phone
> on terminal my phone says `RING`
> i need to command the to make an audio connection (SCO)
> and route this connections
>
> how to do this ?
>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-09-14 6:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 1:45 [Bluez-devel] handsfree or headset support on pc guoyun
2007-09-14 1:58 ` robert
2007-09-14 5:17 ` andrey larin
2007-09-14 6:22 ` robert [this message]
2007-09-14 7:39 ` andrey larin
2007-09-14 16:44 ` robert
2007-09-14 17:39 ` andrey larin
2007-09-14 17:48 ` andrey larin
2007-09-14 18:01 ` robert
2007-09-14 18:31 ` andrey larin
2007-09-14 20:37 ` robert
-- strict thread matches above, loose matches on Subject: below --
2007-09-13 19:34 andrey larin
2007-09-13 19:54 ` robert
2007-09-13 20:48 ` andrey larin
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=FC45259F-96B7-4513-B655-21C1AE4867CC@cadvium.net \
--to=rbscott@cadvium.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