I stand corrected. The latest Samsung mobile phones (like D500, E720, Z500, D600, etc.) have
OMA (SyncML) DS over OBEX (over data cable, infrared and Bluetooth). Samsung has bought both the client in the mobile phone as well the Windows PC software from
Teleca. Because of this both the infrared service and the Bluetooth service is not advertised in their corresponding databases. If that sales package did not mention SyncML DS so prominent, yes I would have oversaw it too. But because there is no OMA (SyncML) DS over HTTP or WAP client on the phone (why?), it had to be SyncML over OBEX.
Currently (one day so far) I am playing with it and I can say, it is buggy like ****. It was a good decision to take both the client and the server of that company, otherwise it would have been a lot of work. Oh, Nokia Series 40 SyncML implementation is heaven compared to this. Anyway the Samsung PC Studio - PC Sync software uses this SyncML client and it works. So there is way. The question is how long and hard that way is.
No, Apple iSync 2.1 does not detect it and I doubt it will ever because the mobile phone does not advertise its SyncML capabilities.