Q.:  Does Nokia S60 support OMA SyncML DS over OBEX ? A.:  OMA DS 1.1 (WBXML) is supported over OBEX since 2nd Edition (except Nokia 6600). It is advertised in Bluetooth and USB with its own interface. Other OBEX Bluetooth services gain no access to SyncML and there is no support for AT+CPROT=0 to start SyncML over USB CDC ACM or IrCOMM or Bluetooth DUN. The server database source paths and even the server ID URI are fixed. It is possible to overcome this, by creating a new profile in Nokia > Menu > Connectivity or Tools > Sync > Options > New sync profile. However, adjusting such a setting manually is not deployable for end-users. Perhaps it would be possible to create such a new profile via OMA CP via WAP Push, nevertheless, it does not work via OBEX. Consequently, use the default PC Suite profile: XML, WBXML. Q.:  How to start OMA SyncML DS 1.2 over OBEX ? A.:  3rd Edition supports – besides 1.1 – version 1.2 requiring a new concept called Server Alerted Notification for starting the synchronisation: SAN. Still the URIs are fixed when using the default profile. Just like on Sony Ericsson’s SyncML 1.2 support, the digest is ignored, so just send 16 arbitrary bytes. In this example, the digest is calculated with empty password and nonce. Because Nokia has a bug (fixed in Feature Pack 1), you have to send SAN with the MIME media type of application/vnd.syncml+wbxml instead of application/vnd.syncml.ds.notification. Q.:  Why should OMA SyncML DS 1.2 be used ? A.:  The phone will fall back to 1.1 automatically. However, SMS, bookmarks (since Nokia N80), and email (since 3rd Edition Feature Pack 2) are hierarchical datastores in S60 and are supported only in 1.2. MMS work with 1.1, too. Nevertheless, the path for SMS is not set in the default profile, requiring the creation of a complete new profile.