It works only if I change kBluetoothSDPUUID16ServiceClassSerialPort to kBluetoothSDPUUID16ServiceClassOBEXFileTransfer, but in that case it's a normal file transfer operation which doesn't list messages folder (it uses the service record named "OBEX File Transfer" and not "Nokia PC Suite").
Now you got me. I mixed Nokia Series 40 with Nokia Symbian and confused myself totally. In Nokia Series 40, like your Nokia 5000, you have to use the standard OBEX File Transfer (FTP) service as normal. However, to get the special folders like /Messages you have to use an additional Who header in the OBEX SetPATH operation. The value of that Who header is "PC Suite". Please note: The path of folders changes with the current language of the phone. In German it would be /Mitteilungen. Therefore for the start, please, change the language of your phone to English.
It seems that OBEXSession is not able to connect to Nokia PC Suite service even if I use a target uuid. I just wonder why. the SessionEvent type is kOBEXSessionEventTypeError the serverResponseOpCode is 0x88 (?) the errorData error is -21880 (kOBEXSessionTransportDiedError)
<https://developer.apple.com/downloads/>, in the search box, enter "PacketLogger". As of today, this gives "Hardware IO Tools for Xcode" (Late July 2012) and PacketLogger 4.0.9. The PacketLogger helps you to understand what is happening behind the scenes. But be warned: Its OBEX parser is a bit buggy and might decode in a wrong way. Then, just have a look at the raw bytes. OBEX is not that complicated.
Do I have to create my own OBEX client? I don't know where to start. Can you give me some hint?
Information about this is spare and it would be pure luck to find information on Google. Please, start at my webpage which gives an general overview how everything is related/connected: <http://www.traud.de/gsm/>. The later chapters are a starting point with many links: PC Suite <http://www.traud.de/gsm/nokia.htm> OBEX <http://www.traud.de/gsm/OBEX.htm> SyncML <http://www.traud.de/gsm/SyncML.htm> The trick is to read these specifications, find similar tools, and do reverse engineering.
I tried with target, then with target and who.
Target is only allowed in OBEX CONNECT. As client, Who is only allowed in operations which are not CONNECT. Or stated differently, the use of Target and Who headers is mutually exclusive. You use Who in the SetPATH operations. Target in the CONNECT operation.
The target I use is "f9ec7bc4-953c-11d2-984e-525400dc9e09".
That is the correct FTP target header. By the way: In Nokia Series 40, the Serial Port Profile (SPP, Nokia PC Suite) uses its own protocol which multiplexes AT commands and OBEX. I am not aware of a public documentation of that. It was called FBus once. If your legislation allows it, you have to reverse engineer that. Therefore, I recommended the Nokia PC Suite in Windows <http://nds1.nokia.com/files/support/global/phones/software/Nokia_PC_Suite_g er_web.exe> plus tools like from LogoManager <http://www.logomanager.co.uk/php/products.php?id=51>. An open source project are Gammu/Wammu <http://wammu.eu/docs/manual/faq/config.html#faq-config-nokia> and gnokii. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com