Hi Marcel,
I would like to ask if it is okay for a slave device to be the first to issue a disconnect command in the RFCOMM layer rather than the master device. Usually, after the OBEX Disconnect request of the master device and the corresponding response of the slave device, the master issues a disconnect command in the RFCOMM layer. However, the slave device (running on BlueZ) is the first one to issue a disconnect command in the RFCOMM layer, and the master device issues a disconnect command (RFCOMM) after that of the slave device. Is this okay?
Trace for this kind of transaction is as follows:
> ACL data: handle 41 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 10 pf 1 ilen 8 fcs 0xac credits 1
OBEX: Disconnect cmd(f): len 8
Connection ID (0xcb) = 0
< ACL data: handle 41 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 10 pf 0 ilen 3 fcs 0x6a
OBEX: Disconnect rsp(f): status 200 len 3
Status 200 = Success
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): DISC: cr 0 dlci 10 pf 1 ilen 0 fcs 0xc
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 10 pf 1 ilen 0 fcs 0x6d
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 10 pf 1 ilen 0 fcs 0x47
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 0 dlci 10 pf 1 ilen 0 fcs 0xc7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
Also, a client device issues an OBEX Connect request to a server device (running on BlueZ) and thereafter sends an SDP service request. Is this flow (1. OBEX Connect --- 2. SDP service request) okay with BlueZ? This is how the Sony Ericsson S700i and the Samsung D600 goes about their Bluetooth transactions. After the SDP service request, the mobile phones did not issue an OBEX Disconnect request.
The trace for this kind of transaction is attached with this email:
Thanks so much,
Arch
---------------------------------
Yahoo! Personals
Skip the bars and set-ups and start using Yahoo! Personals for free
Hi Arch,
> I would like to ask if it is okay for a slave device to be the first
> to issue a disconnect command in the RFCOMM layer rather than the
> master device. Usually, after the OBEX Disconnect request of the
> master device and the corresponding response of the slave device, the
> master issues a disconnect command in the RFCOMM layer. However, the
> slave device (running on BlueZ) is the first one to issue a disconnect
> command in the RFCOMM layer, and the master device issues a disconnect
> command (RFCOMM) after that of the slave device. Is this okay?
I don't see a problem here, besides that the other side is not reacting
on the DISC command.
> Also, a client device issues an OBEX Connect request to a server
> device (running on BlueZ) and thereafter sends an SDP service request.
> Is this flow (1. OBEX Connect --- 2. SDP service request) okay with
> BlueZ? This is how the Sony Ericsson S700i and the Samsung D600 goes
> about their Bluetooth transactions. After the SDP service request, the
> mobile phones did not issue an OBEX Disconnect request.
I think that I already told you that. SDP transactions can happen at
every time.
> The trace for this kind of transaction is attached with this email:
You are kidding me. Sending a Microsoft Word document is kinda rude.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users