Hi, You actually need to register the SDP record for the Windows application to know what RFCOMM port to connect to. You need to use sdptool or better yet use the BlueZ DBUS API for registering SDP records. To get you started, if you're using obexftpd as a PUSH server, use: sdptool add --channel=<obexftpd rfcomm channel> opush or ftp, use: sdptool add --channel=<obexftpd rfcomm channel> ftp If you want to use the BlueZ DBUS API, use the AddServiceRecordFromXML and pass in the record in XML format. To get a sample of how the XML record looks like, you can run: sdptool get --xml <record handle, most likely 0x10000> For more, I suggest you read the BlueZ DBUS API documentation. Regards, -Denis > Hi, > > > I have the BlueZ utilities cross-compiled to a particular Arm- target, and > cannot get the openobex working. > > I start of the server, > $ hcid -s > $ hciattach -- with relevant parameters > $ hciconfig -a -- doesnt show any Service classes > $ obexftpd -c ./ -b -- throws up a msg waiting for connection > $ hciconfig -a -- now shows the Capturing, Object transfer as service > classes > > > But If I start an windows application, to connect to this device, it shows > services not found. > > Any other hints as to properly starting off obexftpd and using obexftp > client? > ----------------------------------------- Nokia Pty Ltd, Level 1, 53 Brandl St, Eight Mile Plains, 4113, Queensland, Australia -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
