syncml-obex-client fails with a Nokia phone fails with Forbidden (0x43)

[AlainKnaff]

Trying to sync the phone via Obex (USB Cable) fails with Nokia phone fails with Forbidden (0x43).

Synchronizing group "cable2pim"
The previous synchronization was unclean. Slow-syncing
contact sink of member 1 of type syncml-obex-client just connected
contact sink of member 2 of type kdepim-sync just connected
Main sink of member 2 of type kdepim-sync just connected
Main sink of member 1 of type syncml-obex-client just connected
All clients connected or error
Main sink of member 1 of type syncml-obex-client just sent all changes

Then, the local DB (KDE Pim) sends all changes, but the phone doesn't.

Afterwards, msynctool just hangs after displaying the following message:

contact sink of member 2 of type kdepim-sync just sent all changes
Main sink of member 2 of type kdepim-sync just sent all changes

At this time, the phone displays Sync complete, just as if everything was successful, but it isn't: neither changes from the phone to kaddressbook are performed, nor the other way round

[AlainKnaff]

Still broken in today's (Feb 9th) SVN version

[felixmoeller]

setting version to keep tracker clean.

[mario.bruckschwaiger]

I experienced the same thing with bluetooth after updating Nokia N95 Firmware from 20.0.015 to 21.0.016. Also tried it with libsyncml version 0.4.6 but still get "forbidden" and "System error" on the phone. And I also tried it with a new Sync-Profile instead of "PC Suite", but it is the same behavior.

[agran]

Hi,

I can reproduce that behavior with debian unstable, libsyncml 0.4.6, Nokia E90 Firmware 07.24.03, opensync 0.36

[agran]

sorry, forgot to include that I use bluetooth

[krei]

I get the same behaviour on a Nokia 5500, with both opensync 0.22 (debian stable) and 0.36 over bluetooth -- 0x43 forbidden returned, 'System error' on the phone, using PC Suite profile (and others). Hoping to investigate this further; any advice on where to start looking?? (debug logs didn't reveal much, but maybe I'm just not reading them right :))

[dgollub]

Could you try first the syncml-obex-client command line tool?

 http://libsyncml.opensync.org/wiki/obex-guide#Troubleshooting

[bellmich]

Sounds like the usual slow-sync problem.

Phone sends: alert 201 libsyncml sends: status 508 and alert 201

The problem is already fixed (please see bug #143 in libsyncml ticket system).

[krei]

This still fails with latest libsyncml from svn:

syncml-obex-client --sync 'text/x-vcard' Contacts -b '00:18:0F:8A:81:FD' 10 --identifier 'PC Suite' --version 1.1 --wbxml --dumpinfo

connection with device succeeded
Received an Alert for the DS Server at Contacts: Type: 201, Last , Next 20080613T181304Z
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing
Received an transport error: Forbidden (0x43)
Send the output below to the libsyncml developers

========================================
Man: NOKIA
Mod: 5500
FirmwareVersion: 
SoftwareVersion: V 04.40
HardwareVersion: 

ReceiveLimit: 0
MaxObjSize: 0
Connection used: OBEX Client
Identifier: PC Suite

Databases:
DB Locations: Contacts
DB Type: text/x-vcard
DB Slow: 0

Bluetooth: Yes
Wbxml: Yes
SyncML Version: 1.1
SupportsNumberofChanges: Yes
SupportsLargeObjects: Yes

[krei]

logs from syncml-obex-client

[bellmich]

Did you test this stuff after 2008-Jun-17? I added several fixes to get the code working with S60 and S80 mobiles and at minimum the E9500 works.

[tuju]

No comment in 30 days. closing.