Q.:  Does Sagem support OMA SyncML DS over OBEX ? A.:  myX6-2 and its Vodafone version myV-76 support it. Although, SyncML is advertised in IrDA on the same channel as the default OBEX server, it is not advertised in Bluetooth and Bluetooth’s OBEX Push server gains no access to SyncML. You have to use the AT command interface which is available on traditional data cable, CDC (USB), IrCOMM (IrDA) and Dial-up Networking (Bluetooth). AT+CPROT=0 starts the internal OBEX server.   Because Sagem does not support Server Alerted Sync of OMA DS (SyncType 7 is missing in devinf11), how do you start? When you send a normal server alerted sync package, the Sagem will reboot. You have to send a GET request for the devinf11 which starts a normal SyncML session: XML, WBXML.   Sagem my301X, my401X (my401V), my501C, my500X, my501X, my600X (my600V), my700X and myX-8 are believed to support SyncML over OBEX, too. However, the latter might require a firmware update. Sagem > Menu > Connectivity > SyncML > Local menu item or SmartCom’s WellPhone DirectSync must be present on your computer. Other Sagem phones like the myX5-2 (myV-55) have AT+CPROT=0 and a SyncML service indication in IrDA but no SyncML over OBEX on board. Issuing AT+CPROT=0 on such a device will work with a cable connection but will reboot it over IrCOMM. The myW-7 (myV-85) seems not to have SyncML on board either.