From: Daniel G. <dg...@su...> - 2008-12-15 12:28:27
|
On Monday 15 December 2008 12:16:30 Robin Atwood wrote: > On Monday 15 Dec 2008, Daniel Gollub wrote: > > On Monday 15 December 2008 11:26:43 Robin Atwood wrote: > > > On Sunday 14 Dec 2008, Daniel Gollub wrote: > > > > Could you provide the output of "sdptool browse $MAC"? > > > > If you run "sdptool search SYNCML", make sure the MAC is matching your > > mobile. Very likely the result on channel 3 was the result of your > > neighbor's mobile. You can also run: sdptool --bdaddr=$MAC SYNCML to just > > search for a certain Service on a certain device. Without parameter it's > > checking all devices. > > # sdptool search --bdaddr=00:1C:A4:5A:73:D8 SYNCML > Searching for SYNCML on 00:1C:A4:5A:73:D8 ... > Service Name: SyncMLClient > Service Description: SyncML BT client > Service RecHandle: 0x1002c > Service Class ID List: > UUID 128: 00000002-0000-1000-8000-0002ee000002 > Protocol Descriptor List: > "L2CAP" (0x0100) > "RFCOMM" (0x0003) > Channel: 6 > "OBEX" (0x0008) > > It's my phone alright! Uuuuuuuuuh... that's interesting... > > > I saw traces of m-Router SDP records ... > > You don't have to waste time with trying SyncML via OBEX. You need to > > establish an IP connection and then fire-up SyncML http over this IP > > connection. > > Thanks, I will give it a try. Stop. There is OBEX.... The SYNCML SDP record doesn't seem to be "visible" when doing regular (broadcast) SDP query. Could you try latest syncml-ds-tool with "obex" transport on channel 6 via Bluetooth.. Please forget about the IP/m-Router stuff for a second... best regards, Daniel |