From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: Connection issue with headset
Date: Sat, 29 Jan 2005 20:13:10 -0700 [thread overview]
Message-ID: <41FC50C6.1080600@xmission.com> (raw)
In-Reply-To: <4d34f3925fsbellon@sbellon.de>
stefan,
that's good sleuthing, but rfcomm.conf is used to bind a character
device in /dev (eg /dev/rfcomm1) to a bluetooth device. btsco does not
try to use a character device to interact with the headset... it makes a
straight l2cap connection for control signals and later a sco connection
for audio transport.
brad
Stefan Bellon wrote:
> Sebastian Roth wrote:
>
>
>>>nomade:/home/dh# btsco 00:0b:2e:06:01:2e
>>>Device is 1:0
>>>Voice setting: 0x0060
>>>RFCOMM channel 6 connected
>>
>>You have to press the headset button now!
>
>
> Sorry to hi-jack this thread, but I just noticed something regarding my
> problem when I read this.
>
> When I issue the above, the line "RFCOMM channel x connected" doesn't
> appear at all. You wrote that afterwards I have to press the headset
> button. That means, if that line doesn't appear, the problem isn't with
> the headset, but still with my Bluetooth/rfcomm configuration of the
> computer?
>
> In that case I got an idea. As I use Bluetooth in order to connect my
> SonyEricsson P900 to the computer as well, I have got set up a
> /etc/bluetooth/rfcomm.conf which looks like this:
>
> rfcomm1 {
> bind yes;
> device 00:0A:D9:E9:BB:0A;
> channel 1;
> comment "P900 Serial Protocol connection";
> }
>
> rfcomm11 {
> bind yes;
> device 00:0A:D9:E9:BB:0A;
> channel 11;
> comment "P900 p3nfsd connection";
> }
>
> Do I have to add something like ...
>
> rfcomm2 {
> bind yes;
> device 00:07:A4:21:1D:86;
> channel 2;
> comment "Jabra BT800";
> }
>
> ... in order to make it work with btsco? In any case, adding the above
> channel 2 configuration doesn't work. Or don't I have to touch the
> rfcomm.conf at all?
>
> Perhaps this gives some clues what I'm doing wrong?
>
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-30 3:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 9:32 [Bluez-users] Connection issue with headset administrator tootai
2005-01-28 15:53 ` [Bluez-users] " Sebastian Roth
2005-01-29 16:39 ` daniel huhardeaux
2005-01-29 16:43 ` administrator tootai
2005-01-29 17:29 ` Stefan Bellon
2005-01-30 3:13 ` Brad Midgley [this message]
2005-01-30 19:01 ` administrator tootai
2005-01-31 14:57 ` administrator tootai
2005-01-31 14:58 ` Marcel Holtmann
2005-01-31 15:30 ` administrator tootai
2005-01-31 15:55 ` Marcel Holtmann
2005-01-31 18:20 ` administrator tootai
2005-02-01 16:37 ` Sebastian Roth
2005-02-02 13:20 ` administrator tootai
2005-02-02 16:21 ` Sebastian Roth
2005-02-02 16:55 ` administrator tootai
2005-02-03 14:13 ` Sebastian Roth
2005-02-03 21:39 ` administrator tootai
2005-02-04 7:38 ` Sebastian Roth
2005-02-04 12:25 ` administrator tootai
2005-02-03 17:06 ` administrator tootai
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=41FC50C6.1080600@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-users@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