Re: [Opensync-users] Problem with USB Sniffeours

[Habib S. <hab...@ya...>]

> > > > > > Second question is that which tool does listen to USB port and
> > > > > > returns the results as an XML(no binary format)? For example,
> > > > > > usb-monitor is a powerful application. I could set it so that it
> > > > > > listened to all of above four ports, then I synced my mobile, the
> > > > > > tool generated the results but in binary format :-(,
> > > > >
> > > > > Any possibility to copy&paste the traffic in hex?
> > > > > Isn't there any export function - even HTML would be fine :P
> > > >
> > > > Dear Daniel,
> > > > I
> > > > finally could get data from the traffic. The attached file contains the
> > > > traffic information in 3 views (URB Basic View, URB Complete View,
> > > > Packet View).
> > > > I hope it can help. Please let me know if you find the problem....
> > >
> > > Thanks - brief check: SE is not using OBEX at all.. it's all SyncML 1.2
> > > via HTTP in WBXML :(
> >
> > Dear Daniel,
> > Using either OBEX or HTTP isn't important for me at all. But why the
> > command syncml-http-server doesn't work with P1i?
> 
> I see - but OBEX is easier for Desktop Distribution to integrate. Setting-up 
> IP connection with a mobile is not yet that trivial today..
> 
> How did you establish the IP connection?

It's very easy. The P1i supports WLANs perfectly. I set an IP address in it and make an Ad-Hoc wireless network between my laptop and the mobile. Please let me know if you need a more info.


> 
> >
> > > It's again a Teleca SyncML stack... this is also used on various Samsung
> > > mobiles. It would be interesting to try some on OBEX - if this works at
> > > all... but not quite sure if it's worth the pain - maybe it's completley
> > > broken and never tested by Teleca/SE.
> >
> > Can we use a special software written for Samsung in this case?
> 
> There is already one major different of Samsung and the SE on the OBEX 
> interface. Samsung does everything via the DUN interface - SE provides via 
> Bluetotoh a direct OBEX interface for SyncML - so there is already a major 
> difference. IIRC there used to be issues that the "Database"-name of the PC-
> side needs to reflect the same name as the one from the mobile for some 
> reason. At least i had to do so for some Telecal Samsungs mobile sometime 
> ago... but again not quite sure if it's worth a try. Direct Access to such a 
> phone would be more helpful...
> 
> best regards,
> Daniel