From: Arnaud Mouiche <arnaud.mouiche@inventel.fr>
To: "Williams, Richard" <Richard.Williams@VITRONICS.com>,
"Bluez-Devel (E-mail)" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] SCO question
Date: Fri, 09 Jul 2004 09:48:57 +0200 [thread overview]
Message-ID: <5.1.1.6.0.20040709094335.02436cc8@172.16.0.2> (raw)
In-Reply-To: <A1F0D47583A2D711919F00600819B3A45BDC65@goofy.vitronics.com >
At 16:11 08/07/2004 -0400, Williams, Richard wrote:
>Arnaud, Thank you.
>
>exactly right.... The channel for my headset is "2".
>
>hstest record t1.wav 00:0A:D9:74:97:19 2
>sets up the SCO channel correctly, and rings the headset.
>
>And I can see the various "AT" commands coming from the headset for volume
>control, etc.
>
>However, there is no audio. Neither "record" nor "play" appears to do
>anything.
>
>Next idea ??
the audio path is something that you should realy take care and look at the
possibiliites provided by your hardware.
- does your device can send/Receive audio through HCI ? and if yes, I
really thing you need to send vendor specific command to configure it (the
device has also the possibilities to use a analogic path, or a IOM one if
they are available)
- does your device support 16 bit PCM steaming ? If not, you should use
another setting for "hciconfig hci0 voice 0x0040" and hack hstest to accept
ulaw/alaw instead of PCM (if it's not already done)
arnaud
>BTW: I am using Bluez-utils 2.3 and bluez-libs 2.4. I don't know if that
>makes a difference.
>
>Best Regards,
>
>Rich
>
>
>
>-----Original Message-----
>From: Arnaud Mouiche [mailto:arnaud.mouiche@inventel.fr]
>Sent: Thursday, July 08, 2004 10:09 AM
>To: Williams, Richard; Bluez-Devel (E-mail)
>Subject: Re: [Bluez-devel] SCO question
>
>
>At 09:12 08/07/2004 -0400, Williams, Richard wrote:
>
> >Hi,
> >
> >I'm getting back to a BT headset <-> LINUX project that I had abandoned
> >some months ago. I have an X-scale single board computer running Linux
> >2.4.26 with the latest Bluez patches. I have a Sony Ericsson HBH-35
> >headset that I'm trying to get to work with my computer. I have an Anycomm
> >USB BT dongle.
> >
> >I have done the following:
> >modprobe hci_usb
> >modprobe rfcomm
> >modprobe sco
> >hcid
> >hciconfig hci0 up
> >hciconfig hci0 voice 0x0040
> >.... My Pin file is set up for a pin of "0000" - required by the headset.
> >
> >hcitool scan works OK and finds the headset
> >
> >l2ping works OK and pairs with the headset.
> >
> >hstest record t1.wav 00:0A:D9:74:97:19 1
>
>are you sure than "1" is the correct rfcomm channel ?
>you should perform a SDP request to get the correct one.
>
>arnaud
>
> ><<<This gives output:
> >Voice setting: 0x0040
> >RFCOMM channel connected
> >Can't connect SCO audio channel: Connection refused.
> >
> >I know that the socket connect statement in sco_connect() in hstest is
> >failing.
> >Any ideas of the cause of this ?
> >
> >
> >thanks very much,
> >
> >Rich
> >
> >
> >
> >Richard B. Williams
> >Vitronics, Inc.
> >3 Corbett Way
> >Eatontown, NJ 07724-2262
> >732-389-0244 x29
> >Richard.Williams@vitronics.com
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email sponsored by Black Hat Briefings & Training.
> >Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> >digital self defense, top technical experts, no vendor pitches,
> >unmatched networking opportunities. Visit www.blackhat.com
> >_______________________________________________
> >Bluez-devel mailing list
> >Bluez-devel@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by Black Hat Briefings & Training.
>Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
>digital self defense, top technical experts, no vendor pitches,
>unmatched networking opportunities. Visit www.blackhat.com
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next parent reply other threads:[~2004-07-09 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A1F0D47583A2D711919F00600819B3A45BDC65@goofy.vitronics.com >
2004-07-09 7:48 ` Arnaud Mouiche [this message]
2007-08-22 18:23 [Bluez-devel] SCO Question robert
2007-08-24 11:35 ` Mikael Bengtsson
2007-08-24 12:06 ` Marcel Holtmann
2007-09-06 11:03 ` Mikael Bengtsson
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 20:11 [Bluez-devel] SCO question Williams, Richard
[not found] <A1F0D47583A2D711919F00600819B3A4028BAE@goofy.vitronics.com >
2004-07-08 14:08 ` Arnaud Mouiche
2004-07-08 13:12 Williams, Richard
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=5.1.1.6.0.20040709094335.02436cc8@172.16.0.2 \
--to=arnaud.mouiche@inventel.fr \
--cc=Richard.Williams@VITRONICS.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