Menu
▾
▴
opensync-users
|
From: <gb...@co...> - 2006-10-26 11:47:13
|
Is anyone connecting successfully with this phone? I am using svn trunk version 1440. Via USB: kien ~ # syncml-obex-client -u 1 --identifier "PC Suite" --version "1.2" --wbxml --sync 'text/x-vcard' Contacts --dumpinfo Received an transport error: Request not successfull: 68 Received an transport error: Request not successfull: 67 Didnt receive the devinf though it was requested Via Bluetooth: g.bobbio@kien ~ $ syncml-obex-client -b 00:12:D2:xx:xx:xx 12 --identifier "PC Suite" --version "1.2" --wbxml --sync 'text/x-vcard' Contacts --dumpinfo Received an transport error: Request not successfull: 68 Received an transport error: Request not successfull: 67 Didnt receive the devinf though it was requested Ciao, Giovanni |
|
From: Jim M. <ja...@bt...> - 2006-10-27 07:38:34
|
Hi Giovanni, Several of us seem to be having the same problem, no solutions yet. Jim > > Today's Topics: > > 1. Nokia N80 (gb...@co...) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 26 Oct 2006 13:46:53 +0200 > From: gb...@co... > Subject: [Opensync-users] Nokia N80 > To: ope...@li... > Message-ID: <200...@co...> > Content-Type: text/plain; charset="iso-8859-1" > > Is anyone connecting successfully with this phone? > I am using svn trunk version 1440. > > Via USB: > kien ~ # syncml-obex-client -u 1 --identifier "PC > Suite" --version "1.2" --wbxml --sync 'text/x-vcard' > Contacts --dumpinfo > Received an transport error: Request not successfull: 68 > Received an transport error: Request not successfull: 67 > Didnt receive the devinf though it was requested > > Via Bluetooth: > g.bobbio@kien ~ $ syncml-obex-client -b 00:12:D2:xx:xx:xx > 12 --identifier "PC > Suite" --version "1.2" --wbxml --sync 'text/x-vcard' > Contacts --dumpinfo > Received an transport error: Request not successfull: 68 > Received an transport error: Request not successfull: 67 > Didnt receive the devinf though it was requested > > Ciao, > Giovanni > |
|
From: Keith P. <ke...@ke...> - 2006-10-27 18:06:02
|
On Fri, 2006-10-27 at 08:38 +0100, Jim Maas wrote: > Hi Giovanni, >=20 > Several of us seem to be having the same problem, no solutions yet. Yeah, I'm seeing similar issues on a 6131; error 68. -keith |
|
From: Erik G. <e-...@ru...> - 2006-10-30 16:48:58
Attachments:
signature.asc
|
Hello. I'm having the same problem. I have tried everything. USB, bluetooth, http (mlsync both client and server), but I'm unable to syncronize. I'm using Ubuntu with the packages from: deb http://www.in.fh-merseburg.de/~jahn/ dapper main deb-src http://www.in.fh-merseburg.de/~jahn/ dapper main So if anyone is able to syncronize in anyway. Please tell us all. Erik gb...@co... wrote: > Is anyone connecting successfully with this phone? > I am using svn trunk version 1440. >=20 > Via USB: > kien ~ # syncml-obex-client -u 1 --identifier "PC=20 > Suite" --version "1.2" --wbxml --sync 'text/x-vcard'=20 > Contacts --dumpinfo > Received an transport error: Request not successfull: 68 > Received an transport error: Request not successfull: 67 > Didnt receive the devinf though it was requested >=20 > Via Bluetooth: > g.bobbio@kien ~ $ syncml-obex-client -b 00:12:D2:xx:xx:xx=20 > 12 --identifier "PC=20 > Suite" --version "1.2" --wbxml --sync 'text/x-vcard'=20 > Contacts --dumpinfo > Received an transport error: Request not successfull: 68 > Received an transport error: Request not successfull: 67 > Didnt receive the devinf though it was requested >=20 > Ciao, > Giovanni >=20 > -----------------------------------------------------------------------= -- > Using Tomcat but need to do more? Need to support web services, securit= y? > Get stuff done quickly with pre-integrated technology to make your job = easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron= imo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > Opensync-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-users >=20 |
|
From: Ochal C. <oc...@ke...> - 2006-10-30 19:14:52
|
On Mon, 2006-10-30 at 17:48 +0100, Erik Gran wrote: > Hello. > > I'm having the same problem. I have tried everything. USB, bluetooth, > http (mlsync both client and server), but I'm unable to syncronize. > > I'm using Ubuntu with the packages from: > deb http://www.in.fh-merseburg.de/~jahn/ dapper main > deb-src http://www.in.fh-merseburg.de/~jahn/ dapper main > > So if anyone is able to syncronize in anyway. Please tell us all. For starters, syncml-obex-client only works over bluetooth (well, that's what i've been told anyway), so you can only use this over bluetooth. As for USB, you might have more luck with the gnokii plugin, *IF* your usb cable is supported (my pop-port cable (DKU-5 iirc) doesn't work under linux). When you setup syncml-obex-client over bluetooth, you need to obtain the hardware address of your phone with hcitool -scan, and the bluetooth channel with sdptool -browse <hardware address>, syncml should then be listed. Also, you might have to configure a username and password on the phone to be able to initialise communications. Please post your config of your syncml-obex-client |
|
From: Erik G. <e-...@ru...> - 2006-10-30 22:54:01
Attachments:
signature.asc
|
Ochal Christophe wrote: > On Mon, 2006-10-30 at 17:48 +0100, Erik Gran wrote: >> Hello. >> >> I'm having the same problem. I have tried everything. USB, bluetooth, >> http (mlsync both client and server), but I'm unable to syncronize. >> >> I'm using Ubuntu with the packages from: >> deb http://www.in.fh-merseburg.de/~jahn/ dapper main >> deb-src http://www.in.fh-merseburg.de/~jahn/ dapper main >> >> So if anyone is able to syncronize in anyway. Please tell us all. >=20 > For starters, syncml-obex-client only works over bluetooth (well, that'= s > what i've been told anyway), so you can only use this over bluetooth. >=20 > As for USB, you might have more luck with the gnokii plugin, *IF* your > usb cable is supported (my pop-port cable (DKU-5 iirc) doesn't work > under linux). >=20 > When you setup syncml-obex-client over bluetooth, you need to obtain th= e > hardware address of your phone with hcitool -scan, and the bluetooth > channel with sdptool -browse <hardware address>, syncml should then be > listed. >=20 > Also, you might have to configure a username and password on the phone > to be able to initialise communications. >=20 > Please post your config of your syncml-obex-client >=20 >=20 This is all my settings. I have tried to make it as readable as possible by splitting the text with "##########################". On my phone under sync i have these settings: Profile name: "PC Suite" Applications Contacts Include in sync: yes Remote database: "Contacts" Syncronisation type: Normal Calendar Include in sync: yes Remote database: "Calendar" Syncronisation type: Normal Connection settings Server version: 1.2 Server ID: "PC Suite" Data bearer: "Bluetooth" Host address: "PC Suite" User name: "erik" Password: "xxxx" Allow sync requests: yes Accept all sync requests: yes ################################################################ erik@ubuntu:~$ hcitool scan Scanning ... XX:XX:XX:XX:XX:XX NOKIA N80 ################################################################ erik@ubuntu:~$ sdptool browse XX:XX:XX:XX:XX:XX Browsing XX:XX:XX:XX:XX:XX ... Service Name: AVRCP Target Service Description: Audio Video Remote Control Service Provider: Symbian Software Ltd. Service RecHandle: 0x10000 Service Class ID List: "AV Remote" (0x110e) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 23 "AVCTP" (0x0017) uint16: 0x100 uint16: 0xf00 Service Name: Hands-Free Audio Gateway Service RecHandle: 0x10001 Service Class ID List: "Handfree Audio Gateway" (0x111f) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 28 Language Base Attr List: code_ISO639: 0x454e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "Handfree Audio Gateway" (0x111f) Version: 0x0101 Service Name: Headset Audio Gateway Service RecHandle: 0x10002 Service Class ID List: "Headset Audio Gateway" (0x1112) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 29 Language Base Attr List: code_ISO639: 0x454e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "Headset" (0x1108) Version: 0x0100 Service Name: SyncMLClient Service RecHandle: 0x10003 Service Class ID List: "Error: This is UUID-128" (0x00000002-0000-1000-8000-0002ee000002) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 10 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x454e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "Error: This is UUID-128" (0x00000002-0000-1000-8000-0002ee000002) Version: 0x0100 Service Name: OBEX File Transfer Service RecHandle: 0x10004 Service Class ID List: "OBEX File Transfer" (0x1106) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 11 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x454e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "OBEX File Transfer" (0x1106) Version: 0x0100 Service Name: Nokia OBEX PC Suite Services Service RecHandle: 0x10005 Service Class ID List: "Error: This is UUID-128" (0x00005005-0000-1000-8000-0002ee000001) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 12 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x454e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "Error: This is UUID-128" (0x00005005-0000-1000-8000-0002ee000001) Version: 0x0100 Service Name: Nokia SyncML Server Service RecHandle: 0x10006 Service Class ID List: "Error: This is UUID-128" (0x00005601-0000-1000-8000-0002ee000001) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 13 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x454e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "Error: This is UUID-128" (0x00005601-0000-1000-8000-0002ee000001) Version: 0x0100 Service Name: OBEX Object Push Service RecHandle: 0x10007 Service Class ID List: "OBEX Object Push" (0x1105) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 9 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x454e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "OBEX Object Push" (0x1105) Version: 0x0100 Service Name: Dial-Up Networking Service RecHandle: 0x10008 Service Class ID List: "Dialup Networking" (0x1103) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 2 Language Base Attr List: code_ISO639: 0x454e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "Dialup Networking" (0x1103) Version: 0x0100 Service RecHandle: 0x10009 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 1 Service Name: Imaging Service RecHandle: 0x1000a Service Class ID List: "Imaging Responder" (0x111b) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 15 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x454e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "Imaging" (0x111a) Version: 0x0100 ################################################################ erik@ubuntu:~$ msynctool --version This is msynctool version "0.90.19" using OpenSync version "0.19" ################################################################ erik@ubuntu:~$ msynctool --listplugins Available plugins: syncml-http-server syncml-obex-client file-sync kdepim-sync ################################################################ erik@ubuntu:~$ msynctool --showgroup n80_2 Groupname: n80_2 Member 1: kdepim-sync No Configuration found: This member has no configuration options Member 2: syncml-obex-client Configuration : <config> <bluetooth_address>XX:XX:XX:XX:XX:XX</bluetooth_address> <bluetooth_channel>10</bluetooth_channel> <interface>0</interface> <identifier>PC Suite</identifier> <version>2</version> <wbxml>0</wbxml> <username>erik</username> <password>xxxx</password> <type>2</type> <usestringtable>0</usestringtable> <onlyreplace>0</onlyreplace> <recvLimit>0</recvLimit> <maxObjSize>0</maxObjSize> <contact_db>Contact</contact_db> <calendar_db>Calendar</calendar_db> <note_db>Notes</note_db> </config> ################################################################ erik@ubuntu:~$ msynctool --sync n80_2 --wait Synchronizing group "n80_2" The previous synchronization was unclean. Slow-syncing (It just hangs. Nothing happens....) ################################################################ erik@ubuntu:~$ msynctool --sync n80_2 Synchronizing group "n80_2" The previous synchronization was unclean. Slow-syncing Member 2 of type syncml-obex-client had an error while connecting: Request not successfull: 79 Member 1 of type kdepim-sync just connected Member 1 of type kdepim-sync just disconnected All clients have disconnected The sync failed: Unable to connect one of the members Error while synchronizing: Unable to connect one of the members |
|
From: Keith P. <ke...@ke...> - 2006-10-30 22:27:13
|
On Mon, 2006-10-30 at 20:14 +0100, Ochal Christophe wrote:
> When you setup syncml-obex-client over bluetooth, you need to obtain the
> hardware address of your phone with hcitool -scan, and the bluetooth
> channel with sdptool -browse <hardware address>, syncml should then be
> listed.
Right, my phone lists SyncML as channel 11:
Service Name: SyncML Client
Service RecHandle: 0x1000e
Service Class ID List:
UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 11
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
> Also, you might have to configure a username and password on the phone
> to be able to initialise communications.
Where is this checked on the host side? I've set something on the phone
but don't know where the cooresponding host-side setting belongs.
> Please post your config of your syncml-obex-client
I'm using the syncml-obex-client application directly, having downloaded
and built the libsyncml library from subversion a few days ago.
I run syncml-obex-client with the following command line:
$ syncml-obex-client --sync text/plain Notes -b 00:17:4B:F1:2D:35 11 --wbxm=
l
The phone reports:
Initializing Synchronization
Then, it says:
Data transfer not possible
Finally, it says:=20
=20
Synchronization info:
Notes incomplete
Unable to process all
items.
0 sent. 0 received.
Notes updated on other
device:
New: 0
Removed: 0
Updated: 0
Notes updated on my
phone:
New: 0
Removed: 0
Updated: 0
Meanwhile, the syncml-obex-client reports:
connection with device succeeded
Received an Alert for the DS Server at Notes: Type: 201, Last 0, Next 0
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing
Received an transport error: Request not successfull: 68
--=20
kei...@in...
|
|
From: Erik G. <e-...@ru...> - 2006-10-30 23:06:17
Attachments:
signature.asc
|
> Right, my phone lists SyncML as channel 11:
>=20
> Service Name: SyncML Client
> Service RecHandle: 0x1000e
> Service Class ID List:
> UUID 128: 00000002-0000-1000-8000-0002ee000002
> Protocol Descriptor List:
> "L2CAP" (0x0100)
> "RFCOMM" (0x0003)
> Channel: 11
> "OBEX" (0x0008)
> Language Base Attr List:
> code_ISO639: 0x656e
> encoding: 0x6a
> base_offset: 0x100
Thats strange, since my phone lists SyncML as channel 10,
on the same phone model!?
Service Name: SyncMLClient
Service RecHandle: 0x10003
Service Class ID List:
"Error: This is UUID-128" (0x00000002-0000-1000-8000-0002ee000002)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 10
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Error: This is UUID-128" (0x00000002-0000-1000-8000-0002ee000002)
Version: 0x0100
|
|
From: Keith P. <ke...@ke...> - 2006-10-31 00:40:52
|
On Tue, 2006-10-31 at 00:06 +0100, Erik Gran wrote: > Thats strange, since my phone lists SyncML as channel 10, > on the same phone model!? No, sorry, this is a 6131 instead of the N80, but the errors being reported are very similar. I prefer Nokia series 40 phones to the Symbian-based ones as performance is far better. --=20 kei...@in... |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X