Author Topic: OPPServer on Widcomm and BlueSoleil  (Read 2828 times)

Offline vvsoles

  • Newbie
  • *
  • Posts: 10
  • Karma: 0
OPPServer on Widcomm and BlueSoleil
« on: June 04, 2011, 05:43:14 PM »
Hi,

When I create a OBEX server with a my own GUID, I see the following sdp record on Widcomm and BlueSoleil.
Service Name: Mobile OBEX Server
Service RecHandle: 0x10011
Service Class ID List:
  "UUID-128" (0xbb886aeb-36b5-4c85-8652-c823d300997e)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 12
  "OBEX" (0x0008)
Profile Descriptor List:
  "UUID-128" (0xbb886aeb-36b5-4c85-8652-c823d300997e)
    Version: 0x0100


On the Toshiba stack and on the Microsoft Stack I see the following for the server.

Service Name: Mobile OBEX Server
Service RecHandle: 0x10011
Service Class ID List:
  "UUID-128" (0xbb886aeb-36b5-4c85-8652-c823d300997e)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 12
  "OBEX" (0x0008)
Profile Descriptor List:
    "OBEX Object Push" (0x1105)
    Version: 0x0100

My question is why does Widcomm and BlueSoleil have a different Profile Desciptor List.  When I do a sdptool search --bdaddr addreess OPUSH it does not see my server since the Profile does not contain the "OBEX Object Push" in the Profile Descriptor List.  I know it is possible to set this when creating the sdp record.  Is there a way in the wCL SDK?

Thanks.


Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3053
  • Karma: 1000
    • Soft Service Company
Re: OPPServer on Widcomm and BlueSoleil
« Reply #1 on: June 05, 2011, 08:21:48 AM »
Hi,

It appears because MS and Toshiba allows to build SDP record as you want (byte by byte). BlueSoleil and WidComm does not allow you to build SDP record. You can just call few methods of BS and WD SDK and it builds SDP by itself without possability to control it.

 

Sitemap 1 2 3 4 5 6 7 8 9