[sync] partial sync with nokia 6021

Jan Schneider jan at horde.org
Fri May 8 12:00:16 UTC 2009


Zitat von Hristo Hristov <ico.dimov at gmail.com>:

>> > 2) per user sync logging:
>> > syncml logs to be orderder in 'username' directories under /tmp/sync
>> > directory.
>>
>> Sync logging is a debug feature. There is no need for any fancyness.
>> You should turn it off in production anyway.
>
> Absolutely, but it can be also helpful for debuggin user problems, as almost
> every user uses different mobile device.

You should point the user that you want to debug to a test  
installation to make sure that he is the only one on that system at  
that moment.

>> > For the third thing i need a little description. Today I tested two
>> > more nokia
>> > phones, particularly '6300' and '5000d-2'.
>> > Both end syncml communication with the following error message 'Data
>> > Transfer Not Possible'.
>> > There was no errors in sync logs. But I noticed that both sides send
>> > different
>> > preferred 'devinfo' parameters.
>> >
>> > Sync logs can be found at:
>> > http://es2.nat.bg/~lisp/sync.Nokia-5000d-2/
>> >
>> > client say's:
>> >                     <DataStore>
>> >                         <SourceRef>/telecom/pb.vcf</SourceRef>
>> >                         <MaxGUIDSize>8</MaxGUIDSize>
>> >                         <Rx-Pref>
>> >                             <CTType>text/x-vcard</CTType>
>> >                             <VerCT>2.1</VerCT>
>> >                         </Rx-Pref>
>> >                         <Tx-Pref>
>> >                             <CTType>text/x-vcard</CTType>
>> >                             <VerCT>2.1</VerCT>
>> >                         </Tx-Pref>
>> >                         <SyncCap>
>> >                             <SyncType>1</SyncType>
>> >                             <SyncType>2</SyncType>
>> >                             <SyncType>4</SyncType>
>> >                             <SyncType>6</SyncType>
>> >                             <SyncType>7</SyncType>
>> >                         </SyncCap>
>> >                         <Rx>
>> >                             <CTType>text/x-vcard</CTType>
>> >                             <VerCT>3.0</VerCT>
>> >                         </Rx>
>> >                         <Tx>
>> >                             <CTType>text/x-vcard</CTType>
>> >                             <VerCT>3.0</VerCT>
>> >                         </Tx>
>> > 			...
>> > 			</DataStore>
>> >
>> > and server responds (on <Get> request):
>> >
>> >                     <DataStore>
>> >                         <SourceRef>contacts</SourceRef>
>> >                         <Rx-Pref>
>> >                             <CTType>text/directory</CTType>
>> >                             <VerCT>3.0</VerCT>
>> >                         </Rx-Pref>
>> >                         <Rx>
>> >                             <CTType>text/x-vcard</CTType>
>> >                             <VerCT>2.1</VerCT>
>> >                         </Rx>
>> >                         <Tx-Pref>
>> >                             <CTType>text/directory</CTType>
>> >                             <VerCT>3.0</VerCT>
>> >                         </Tx-Pref>
>> >                         <Tx>
>> >                             <CTType>text/x-vcard</CTType>
>> >                             <VerCT>2.1</VerCT>
>> >                         </Tx>
>> >                         <SyncCap>
>> >                             <SyncType>1</SyncType>
>> >                             <SyncType>2</SyncType>
>> >                             <SyncType>3</SyncType>
>> >                             <SyncType>4</SyncType>
>> >                             <SyncType>5</SyncType>
>> >                             <SyncType>6</SyncType>
>> >                         </SyncCap>
>> >                     </DataStore>
>> > Can this be the reason for misunderstanding and unsuccessfully
>> > communication between both sides?
>>
>> No.
>>
>> > So my 3rd point/proposal is for device specific 'devinfo' handling for
>> > different device types. One for Nokia (or more, if there are so much
>> > differences between different models) and another for Sony-Ericson.
>>
>> That's the purpose of devinfo. And it's a mandatory feature of syncml
>> servers.
>
> I suppose devinfo support is correctly implemented in horde's syncml backend,
> as it strictly follows SyncML specification. So I suppose the problem is in
> device software and my be update will fix the problem (or at lest I hope so).
>
> Where is situated the code which accounts user's device devinfo settings?
>
> As long as devinfo output form horde's side is implemented in
> /usr/share/php/SyncML/XMLOutput.php, do you think any  
> 'investigation' in terms
> of 'put back to nokia, what it expects' may be helpful?

Again, this is what devinfo is for. Of course we only return to the  
phone what it can handle, as advertised by devinfo.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/



More information about the sync mailing list