From: Johan Uiterwijk Winkel <juw@dds.nl>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Problem connection to handsfree handset.
Date: Sun, 29 Jan 2006 20:38:45 +0100 [thread overview]
Message-ID: <43DD19C5.7050207@dds.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
Hello.
A few days ago I bought a bluetooth handsfree set, but my phone is not
supporting the uploading of phonenumber to the set. Not a big problem,
the set is functioning, but it would ofcource be nice to add the
phonebook to the handset.
As a programmer I thought it would be ease to upload the phonebook to
the handset with AT commands, but untill now I have not been able to
connect to the handset correctly.
The following problem exists (Using Suse Linux 10.0 with the standard
bluetooth tools (except hcidump ;-), downloaded version 1.24 ).
I think i have set up the connection correctly.
When I start minicom (setup to use /dev/rfcomm2, which is using channel
2) I get the response of the handsfree set in minicom as expected:
AT+BRSF=28 (As described in HANDS-FREE PROFILE 1.5).
>From that moment on it looks like the connection is dead. There is no
response on anything I type into minicom.
Is this a known problem with rfcomm, or is minicom not the correct tool
to talk with the handset ?
I've attached the output of hcidump.
Any help is welcome.
Bye.
Johan.
[-- Attachment #2: hcidump.txt --]
[-- Type: text/plain, Size: 5947 bytes --]
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
. . ` . . . . . . . . . .
> HCI Event: Command Status (0x0f) plen 4
. . . .
> HCI Event: Link Key Request (0x17) plen 6
. . ` . . .
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
. . ` . . . . > . ] . j Q . R O I , w R
. ;
> HCI Event: Command Complete (0x0e) plen 10
. . . . . . ` . . .
> HCI Event: Connect Complete (0x03) plen 11
. ) . . . ` . . . . .
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
) . . .
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> HCI Event: Command Complete (0x0e) plen 6
. . . . ) .
> HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
. . ` . . . .
> HCI Event: Max Slots Change (0x1b) plen 3
) . .
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0068 scid 0x0040 result 1 status 2
Connection pending - Authorization pending
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0068 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0068 flags 0x00 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 1024
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0068 flags 0x00 result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0068 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0068 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 4 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 1019 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 4 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 0
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0068 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 4 pf 1 ilen 0 fcs 0x96
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 4 pf 1 ilen 0 fcs 0x5d
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0068 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 4 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 4 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0068 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 4 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 4 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0068 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 4 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0068 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 4 pf 1 ilen 0 fcs 0x79 credits 33
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 4 pf 1 ilen 0 fcs 0xa3 credits 15
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 4 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> ACL data: handle 41 flags 0x02 dlen 19
L2CAP(d): cid 0x0040 len 15 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 4 pf 0 ilen 11 fcs 0xbf
A T + B R S F = 2 8 .
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0068 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 4 pf 0 ilen 1 fcs 0x65
A
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0068 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 4 pf 0 ilen 1 fcs 0x65
T
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0068 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 4 pf 0 ilen 1 fcs 0x65
Z
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0068 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 4 pf 0 ilen 1 fcs 0x65
.
> HCI Event: Number of Completed Packets (0x13) plen 5
. ) . . .
reply other threads:[~2006-01-29 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43DD19C5.7050207@dds.nl \
--to=juw@dds.nl \
--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;
as well as URLs for NNTP newsgroup(s).