Using OPPServer and OPPClient on Toshiba Stack

[vvsoles]

Hi,

I'm seeing a problem when I have a OPPServer running and then use an OPPClient to send data from my PC to the mobile device.  I only create OPPClient when I need it and disconnect when I've finished sending the data.  What I see is when the OPPClient does a connect(), it creates another server with the same characteristics as my OPPServer. It also seems to create another server when I disconnect. This happens every time I do a connect and disconnect.  To confirm this was happening, the mobile device I am sending the data to runs Linux and I do a sdptool search --bdaddr PCaddress OPUSH from the device and it shows all the OBEX servers running on the PC.  I was able to reproduce using the demo app BluetoothOPPServer and BluetoothOPPClientDemo.  The BluetoothOPPServer is just listening and it is not receiving anything.  With the BluetoothOPPClientDemo I just do a connect to the mobile device.

I am seeing the problem on the Toshiba stack.  I do not see any problems on the Microsoft stack.

Is this a toshiba stack problem or is this a bug with the WCL SDK?

Thanks.

[Mike Petrichenko]

Hi,

Unfortunately I can't say why it appears because we have never faced such issue. We will try to reproduce the problem and then I'll back to you with more information. However, Client.Connect() doesn't call any server functions from Toshiba API so it looks as Toshiba issue. But we will check.

[vvsoles]

Do you have any update on this problem?

I did some testing using the OPPServer sample and a sample application from the Toshiba SDK.  My test consisted of having the OPPServer listening and using the TosBtOBEXApiTest.exe application to act as the client.  I send a file to my mobile device and I do not see multiple servers being created.  I don't think it is a toshiba stack problem.  It always happenings when using OPPServer and OPPClient.  I do not see the problem with any of the other stacks.

This problem is a showstopper for my application as a large amount of my customers use the toshiba stack.

Thanks

[Mike Petrichenko]

We are still on that.

WCL doesn't use any OBEX API from any stack as not all stacks have it. WCL uses just standard RFCOMM connection to a service and has its own OBEX implementation. However, we did tests and couldn't reproduce the issue yet. I will update you as we will have some news.

[Mike Petrichenko]

Hi,

We do lot of tests and couldn't reproduce your issue. As you know, Toshiba has its own OPP Server running. When you start WCL OPP Server it adds one more record in Toshiba SDP. When you start WCL OPP Client it doesn't add any records. When you close WCL OPP Server, then new added SDP Record has been removed (and of course toshiba one is still there).

So all works as expected.

[vvsoles]

Hi,

This problem happens ever time for me.  I've tested on multiple computers with the same result.  What toshiba stack did you test with and what program did you use to check the sdp records?  Can you please describe the steps for your testing and what OS it was tested on.  I have tried it on Windows 7 and XP.

Thanks.

[Mike Petrichenko]

I used BluetoothDiscovery demo with MS drivers (which allows to parse SDP records manualy) and Toshiba on other - all works as expected. We are not Linux (Bluez) programmers and never used one so I don't know how it works. May be there are some bugs/issues, who knows. But on Windows platforms WCL (and Windows is what WCL designed for) works as expected.

[vvsoles]

I think I need to clarify how I reproduce the problem.  My computer is running Windows XP SP3, I have an external bluetooth dongle which I install the latest toshiba stack. On this computer I run first the sample BluetoothOPPServer and press Listen.  I then run BluetoothOPPClientDemo on the same computer.  When I do a connect to my mobile device, I see another server created.  I originally had used my mobile device to look at the records on the PC but just recently I used the sample application from the toshiba SDK, TosBtAPITest.exe to look at all the service records on this computer.

I have not seen this problem with Microsoft, Widcomm, or BlueSoleil.

[Mike Petrichenko]

What exactly toshiba version do you use?

[vvsoles]

The toshiba stack I have tested with is 8.00.03.  I also have used an older version that came with my cirago dongle that is version 5.32.

[Mike Petrichenko]

Ok, The issue has been reproduced. In fact its not a WCL bug but its Toshiba issue (how it notifys about its events). It sends same events to ALL registered "recepients" not to only function caller. So all applications receive the same event even it appears in only one.

Not sure how to "workaround" that as there is no "function caller identifier" in toshiba events (actualy Toshiba uses Windows Messages as events (very stupid idea)). Will think what I can do with that.

[Mike Petrichenko]

It looks fixed now. Send me an e-mail and I'll send you fixed version back.