[Bluez-users] Did not proceed with 2nd OBEX Connect request

[Bluez-users] Did not proceed with 2nd OBEX Connect request

[Arch Sayo]

[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]

Hi Marcel,
   
  Yes, you're right. There was no OBEX Connect request following the SDP service request. What I was trying to ask is that supposed to be, there is another OBEX Connect request following the SDP service request. However as you have seen in the hcidump trace, this did not happen. The normal flow of the Bluetooth transaction on the client side is that after the SDP service request, there will be a 2nd OBEX Connect request (without a prior OBEX Disconnect request for the 1st OBEX Connect request). In this regard, is there something in BlueZ that prevents this from happening?
   
  Thank you so much,
  Arch
   
  > Supposedly, after the L2CAP disconnection, the 
Bluetooth device
> (mobile phone) will issue another OBEX Connect 
Request. However, as
> you may see in this trace, the 2nd OBEX Connect 
Request was not
> issued. I hope to know more about what happened to 
the connection and
> why doesn't the transaction proceed.

the first L2CAP is to PSM 3 to establish the RFCOMM 
connection and then
it establishes the OBEX connection on channel 5. The 
second L2CAP is to
PSM 1 for an SDP service request. There are no 
multiple OBEX connection
requests.

Regards

Marcel
  
 

		
---------------------------------
 Yahoo! Personals
 Skip the bars and set-ups and start using Yahoo! Personals for free

[-- Attachment #2: Type: text/html, Size: 1627 bytes --]

Re: [Bluez-users] Did not proceed with 2nd OBEX Connect request

[Marcel Holtmann]

Hi Arch,

> Yes, you're right. There was no OBEX Connect request following the SDP
> service request. What I was trying to ask is that supposed to be,
> there is another OBEX Connect request following the SDP service
> request. However as you have seen in the hcidump trace, this did not
> happen. The normal flow of the Bluetooth transaction on the client
> side is that after the SDP service request, there will be a 2nd OBEX
> Connect request (without a prior OBEX Disconnect request for the 1st
> OBEX Connect request). In this regard, is there something in BlueZ
> that prevents this from happening?

additional SDP request can happen every time. For example to get
information about a status channel or something else. Check the
Bluetooth core or profile specifications for more details.

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
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users