[Opensync-users] need help with syncml-http-server config

[Jim M. <ja...@bt...>]

This is my current config but phone does not connect.  I've followed the 
instructions at
http://a925.albatorsk.com/

to connect the a925 via bluetooth.  After lots of trying I think the 
a925 has a dodgy obex client, can't find any info about it or by using 
syncml-obex-client -u .... just get no usb obex interfaces found!  I've 
attached the relative output from lsusb -v if anyone can tell me anymore 
from that but I can not find a syncml service ... :-(

Can anyone tell me how to complete this http-server config. It still 
will not connect when using
mysynctool --sync group

<config><username>myusername</username><password>mypassword</password><url>http://169.254.1.68</url><port>5079</port>
<usestringtable>0</usestringtable><onlyreplace>0</onlyreplace><recvLimit>0</recvLimit><maxObjSize>0</maxObjSize>
<contact_db>addressbook</contact_db><calendar_db>calendar</calendar_db><note_db>notes</note_db></config>


Thanks

Jim

Bus 001 Device 007: ID 22b8:4002 Motorola PCS A920/A925 UMTS Phone
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               1.10
   bDeviceClass            2 Communications
   bDeviceSubClass         0
   bDeviceProtocol         0
   bMaxPacketSize0        64
   idVendor           0x22b8 Motorola PCS
   idProduct          0x4002 A920/A925 UMTS Phone
   bcdDevice            0.01
   iManufacturer           1
   iProduct                2
   iSerial                 0
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength           62
     bNumInterfaces          2
     bConfigurationValue     1
     iConfiguration          3
     bmAttributes         0xc0
       Self Powered
     MaxPower               20mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           1
       bInterfaceClass         2 Communications
       bInterfaceSubClass      2 Abstract (modem)
       bInterfaceProtocol      1 AT-commands (v.25ter)
       iInterface              4
       CDC Header:
         bcdCDC               1.00
       CDC ACM:
         bmCapabilities       0x0f
           connection notifications
           sends break
           line coding and serial state
           get/set/clear comm features
       CDC Union:
         bMasterInterface        0
         bSlaveInterface         1
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x86  EP 6 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0040  1x 64 bytes
         bInterval             128
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        1
       bAlternateSetting       0
       bNumEndpoints           2
       bInterfaceClass        10 Data
       bInterfaceSubClass      0 Unused
       bInterfaceProtocol      0
       iInterface              5
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x82  EP 2 IN
         bmAttributes            2
           Transfer Type            Bulk
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0040  1x 64 bytes
         bInterval               0
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x01  EP 1 OUT
         bmAttributes            2
           Transfer Type            Bulk
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0040  1x 64 bytes
         bInterval               0

This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.