Thread: [Opensync-users] libsyncml internal error unknown response

Status: Beta

Brought to you by: azrael2, dfriedrich, dgollub_

opensync-users

[Opensync-users] libsyncml internal error unknown response

From: Ulrich B. <ubr...@t-...> - 2009-08-08 15:06:37

I compiled libsyncml from svn libsyncml 0.5.x branch on a Debian Lenny
system. I tested it with syncml-ds-tool with my Samsung SGH E250i
mobile. I got the following error message:
** Message: ERROR: An internal I/O error occured. Unknown response
(0x46)

I made traces, see https://libsyncml.opensync.org/ticket/246

I do not have any knowledge about syncml and do not know how to debug
further. Is there someone to help?

Regards

Uli

Re: [Opensync-users] libsyncml internal error unknown response

From: Michael B. <mic...@cm...> - 2009-08-10 09:46:22

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ulrich Brammer wrote:
> I compiled libsyncml from svn libsyncml 0.5.x branch on a Debian Lenny
> system. I tested it with syncml-ds-tool with my Samsung SGH E250i
> mobile. I got the following error message:
> ** Message: ERROR: An internal I/O error occured. Unknown response
> (0x46)
> 
> I made traces, see https://libsyncml.opensync.org/ticket/246
> 
> I do not have any knowledge about syncml and do not know how to debug
> further. Is there someone to help?

Samsung uses 5 different SyncML stacks and no one is fully standard
compliant. So there are two questions. First does your mobile really
supports SyncML? Second which implementation is used? Here is a good
impression:

http://www.traud.de/gsm/samsung.htm

Best regards

Michael
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkp/7JEACgkQ2L0ZGCAwWqvmvACg5N7mZoNwvZlwGGaSdJpaSUFa
d4IAn0ebSJ3AzE3l3dVj2VgKXCT38Twi
=Odmv
-----END PGP SIGNATURE-----

Re: [Opensync-users] libsyncml internal error unknown response

From: Ulrich B. <ubr...@t-...> - 2009-08-19 13:22:00

Am Montag, den 10.08.2009, 11:47 +0200 schrieb Michael Bell:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ulrich Brammer wrote:
> > I compiled libsyncml from svn libsyncml 0.5.x branch on a Debian Lenny
> > system. I tested it with syncml-ds-tool with my Samsung SGH E250i
> > mobile. I got the following error message:
> > ** Message: ERROR: An internal I/O error occured. Unknown response
> > (0x46)
> > 
> > I made traces, see https://libsyncml.opensync.org/ticket/246
> > 
> > I do not have any knowledge about syncml and do not know how to debug
> > further. Is there someone to help?
> 
> Samsung uses 5 different SyncML stacks and no one is fully standard
> compliant. So there are two questions. First does your mobile really
> supports SyncML? Second which implementation is used? Here is a good
> impression:
> 
> http://www.traud.de/gsm/samsung.htm
> 
> Best regards
> 
> Michael

I looked into the details of the problem to sync with a Samsung SGH
E250:
The phone understands the AT+CPROT=0  and answers with the message
CONNECT. The phone also respond to the obex connect command.

The problem is: syncml-ds-tool does not send a initialization package
which contains the target and sourceURI and the authentification. So the
commandline arguments to provide these information are not usable in
this case.


I analyzed the initialization package from the windows software with the
wbxml2xml tool. This is the xml-version of the initialization packet:

<?xml version="1.0"?>
<!DOCTYPE SyncML PUBLIC "-//SYNCML//DTD SyncML 1.1//EN"
"http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd">
<SyncML xmlns="SYNCML:SYNCML1.1">
 <SyncHdr>
  <VerDTD>1.1</VerDTD>
  <VerProto>SyncML/1.1</VerProto>
  <SessionID>0</SessionID>
  <MsgID>1</MsgID>
  <Target>
   <LocURI>AT$CGSN
XXXXXX 01 XXXXXX 0</LocURI>
  </Target>
  <Source>
   <LocURI>Teleca Desktop Synchronisation Server</LocURI>
  </Source>
  <Cred>
   <Meta>
    <Format xmlns="syncml:metinf">b64</Format>
    <Type xmlns="syncml:metinf">syncml:auth-basic</Type>
   </Meta>
   <Data>c2N0czpzY3Rz</Data>
  </Cred>
 </SyncHdr>
 <SyncBody>
  <Alert>
   <CmdID>0</CmdID>
   <Data>206</Data>
   <Item>
    <Target>
     <LocURI>CONTACTS</LocURI>
    </Target>
    <Source>
     <LocURI>CONTACTS</LocURI>
    </Source>
    <Meta>
     <Type xmlns="syncml:metinf">text/x-vcard</Type>
    </Meta>
   </Item>
  </Alert>
  <Final/>
 </SyncBody>
</SyncML>

The phone answers after a obex get command containing
"application/vnd.syncml+wbxml" with:

<?xml version="1.0"?>
<!DOCTYPE SyncML PUBLIC "-//SYNCML//DTD SyncML 1.1//EN"
"http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd">
<SyncML xmlns="SYNCML:SYNCML1.1">
 <SyncHdr>
  <VerDTD>1.1</VerDTD>
  <VerProto>SyncML/1.1</VerProto>
  <SessionID>0</SessionID>
  <MsgID>1</MsgID>
  <Target>
   <LocURI>Teleca Desktop Synchronisation Server</LocURI>
  </Target>
  <Source>
   <LocURI>XXXXXX 01 XXXXXX 0</LocURI>
   <LocName/>
  </Source>
  <Meta>
   <MaxMsgSize xmlns="syncml:metinf">3100</MaxMsgSize>
  </Meta>
 </SyncHdr>
 <SyncBody>
  <Status>
   <CmdID>1</CmdID>
   <MsgRef>1</MsgRef>
   <CmdRef>0</CmdRef>
   <Cmd>SyncHdr</Cmd>
   <TargetRef>AT$CGSN
XXXXXX 01 XXXXXX 0</TargetRef>
   <SourceRef>Teleca Desktop Synchronisation Server</SourceRef>
   <Data>200</Data>
  </Status>
  <Status>
   <CmdID>2</CmdID>
   <MsgRef>1</MsgRef>
   <CmdRef>0</CmdRef>
   <Cmd>Alert</Cmd>
   <Data>200</Data>
  </Status>
  <Put>
   <CmdID>3</CmdID>
   <Meta>
    <Type xmlns="syncml:metinf">application/vnd.syncml-devinf+xml</Type>
   </Meta>
   <Item>
    <Source>
     <LocURI>./devinf11</LocURI>
    </Source>
    <Data>    <DevInf xmlns="syncml:devinf">
     <VerDTD>1.1</VerDTD>
     <Man>Teleca Software Solutions AB</Man>
     <Mod>Teleca SyncML Client</Mod>
     <OEM>Teleca Software Solutions AB</OEM>
     <FwV>1.0</FwV>
     <SwV>1.0</SwV>
     <HwV>1.0</HwV>
     <DevID>XXXXXX 01 XXXXXX 0</DevID>
     <DevTyp>smartphone</DevTyp>
     <SupportNumberOfChanges/>
     <SupportLargeObjs/>
     <DataStore>
      <SourceRef>CONTACTS</SourceRef>
      <MaxGUIDSize>40</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>
      <DSMem>
       <MaxMem>0</MaxMem>
       <MaxID>1000</MaxID>
      </DSMem>
      <SyncCap>
       <SyncType>1</SyncType>
       <SyncType>2</SyncType>
       <SyncType>7</SyncType>
      </SyncCap>
     </DataStore>
     <CTCap>
      <CTType>text/x-vcard</CTType>
      <PropName>BEGIN</PropName>
      <ValEnum>VCARD</ValEnum>
      <PropName>VERSION</PropName>
      <ValEnum>2.1</ValEnum>
      <PropName>N</PropName>
      <PropName>TEL</PropName>
      <ParamName>WORK</ParamName>
      <ParamName>HOME</ParamName>
      <ParamName>CELL</ParamName>
      <ParamName>FAX</ParamName>
      <ParamName>PAGER</ParamName>
      <ParamName>PREF</ParamName>
      <PropName>EMAIL</PropName>
      <PropName>NOTE</PropName>
      <PropName>END</PropName>
      <ValEnum>VCARD</ValEnum>
     </CTCap>
    </DevInf>
</Data>
   </Item>
  </Put>
  <Alert>
   <CmdID>4</CmdID>
   <Data>200</Data>
   <Item>
    <Target>
     <LocURI>CONTACTS</LocURI>
    </Target>
    <Source>
     <LocURI>CONTACTS</LocURI>
    </Source>
    <Meta>
     <Anchor xmlns="syncml:metinf">
      <Last>1</Last>
      <Next>2</Next>
     </Anchor>
     <MaxObjSize xmlns="syncml:metinf">3000</MaxObjSize>
    </Meta>
   </Item>
  </Alert>
  <Final/>
 </SyncBody>
</SyncML>

Best regards

Ulrich

Re: [Opensync-users] libsyncml internal error unknown response

From: Michael B. <mic...@cm...> - 2009-08-19 14:08:15

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Ulrich,

I read your ticket and libsyncml sends a message to your mobile. You can
find it in Thread3079403264-4972.log of ticket #246.

Ulrich Brammer wrote:
>    <LocURI>AT$CGSN
> XXXXXX 01 XXXXXX 0</LocURI>

I have no idea what this is.

>   <Cred>
>    <Meta>
>     <Format xmlns="syncml:metinf">b64</Format>
>     <Type xmlns="syncml:metinf">syncml:auth-basic</Type>
>    </Meta>
>    <Data>c2N0czpzY3Rz</Data>
>   </Cred>

The OMA DS server authenticates itself to the mobile. Usually the scheme
is that the client authenticates to the server.

BTW Data is a clear text passphrase.

The other stuff looks quite normal. So there are two issues to clarify:

1. Which AT command is used as source?
2. Why does the server authenticates to the client?

Best regards

Michael
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqMB3YACgkQ2L0ZGCAwWqti+wCglJ1yAffmgM36iljT+n8NC1wQ
IKUAnj+fB/izaaqmEQ7eMUtCC8KX1Tx4
=H5DE
-----END PGP SIGNATURE-----

Re: [Opensync-users] libsyncml internal error unknown response

From: Ulrich B. <ubr...@t-...> - 2009-08-19 14:54:14

Am Mittwoch, den 19.08.2009, 16:08 +0200 schrieb Michael Bell:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi Ulrich,
> 
> I read your ticket and libsyncml sends a message to your mobile. You can
> find it in Thread3079403264-4972.log of ticket #246.
> 
I don't think that this message was really send. I tried to look into
the communication with strace. I found only the obex get command from
libsyncml. But the phone did not respond to this command. So the
communication was not succesfull after the obex connection sequence.  

> Ulrich Brammer wrote:
> >    <LocURI>AT$CGSN
> > XXXXXX 01 XXXXXX 0</LocURI>
> 
> I have no idea what this is.
> 
> >   <Cred>
> >    <Meta>
> >     <Format xmlns="syncml:metinf">b64</Format>
> >     <Type xmlns="syncml:metinf">syncml:auth-basic</Type>
> >    </Meta>
> >    <Data>c2N0czpzY3Rz</Data>
> >   </Cred>
> 
> The OMA DS server authenticates itself to the mobile. Usually the scheme
> is that the client authenticates to the server.
> 
> BTW Data is a clear text passphrase.
> 
> The other stuff looks quite normal. So there are two issues to clarify:
> 
> 1. Which AT command is used as source?
> 2. Why does the server authenticates to the client?
> 
> Best regards
> 
> Michael
> - --
The Teleca Desktop Synchronisation Server seems to work the other way.
The Synchronisation Server first reads the IMEI or serial-mumber of the
phone with 
"AT$CGSN\r". This AT-command gives at my phone the same result as 
"AT+CGSN\r". The answer from the AT$CGSN\r is used as TargetURI (the
identification of the phone). 
I did replace some of the numbers of the IMEI with XXX to not show it to
everyone.

I have no idea why in the windows software the server authenticates to
the client. But this may be one of the bugs of the Teleca syncml stack.
So is there a chance to handle this special behavior with libsyncml?

Best regards

Ulrich

Re: [Opensync-users] libsyncml internal error unknown response

From: Michael B. <mic...@cm...> - 2009-08-19 15:02:15

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ulrich Brammer wrote:
> Am Mittwoch, den 19.08.2009, 16:08 +0200 schrieb Michael Bell:
>>
>> I read your ticket and libsyncml sends a message to your mobile. You can
>> find it in Thread3079403264-4972.log of ticket #246.
>>
> I don't think that this message was really send. I tried to look into
> the communication with strace. I found only the obex get command from
> libsyncml. But the phone did not respond to this command. So the
> communication was not succesfull after the obex connection sequence.  

So the real problem is, why does libsyncml not send the message?

> I have no idea why in the windows software the server authenticates to
> the client. But this may be one of the bugs of the Teleca syncml stack.
> So is there a chance to handle this special behavior with libsyncml?

I think it is possible to do implement this but first I have to
understand why the message is not send.

Best regards

Michael
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqMFBoACgkQ2L0ZGCAwWqsVowCgyelX6Qt7f3v3R2nuA5+LiteP
YngAn0ro9F6cvImvaypqiBVCe7jj10vg
=lk5q
-----END PGP SIGNATURE-----

Re: [Opensync-users] libsyncml internal error unknown response

From: Ulrich B. <ubr...@t-...> - 2009-08-19 15:31:51

Am Mittwoch, den 19.08.2009, 17:02 +0200 schrieb Michael Bell:

> I think it is possible to do implement this but first I have to
> understand why the message is not send.
> 

OK, you are right, a short Put sequence was send. but it was quite
different from the one in windows with the authentication enclosed.
I looked into the communication of libsyncml and my phone with strace
--ff.
I got the following sequence:
The bytes are in octal. 

write(10, "ATZ\r"..., 4)                = 4
select(11, [10], NULL, NULL, {1, 0})     = 1 (in [10], left {0, 852000})
read(10, "ATZ\r"..., 100)               = 4
select(11, [10], NULL, NULL, {1, 0})     = 1 (in [10], left {0, 996000})
read(10, "\r\nOK\r\n"..., 96)           = 6
write(10, "AT+CGMI\r"..., 8)            = 8
select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {0, 996000})
read(10, "AT+CGMI\r"..., 100)           = 8
select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {1, 0})
read(10, "\r\nSAMSUNG\r\n"..., 92)      = 11
select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {1, 0})
read(10, "\r\nOK\r\n"..., 81)           = 6
write(10, "AT+CGMM\r"..., 8)            = 8
select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {0, 996000})
read(10, "AT+CGMM\r"..., 100)           = 8
select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {0, 996000})
read(10, "\r\nE250i\r\n"..., 92)        = 9
select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {1, 0})
read(10, "\r\nOK\r\n"..., 83)           = 6
open("/usr/lib/gconv/gconv-modules.cache", O_RDONLY) = 11
fstat64(11, {st_mode=S_IFREG|0644, st_size=25700, ...}) = 0
mmap2(NULL, 25700, PROT_READ, MAP_SHARED, 11, 0) = 0xb7e07000
close(11)                               = 0
futex(0xb7b8ea6c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
write(2, "\n** (process:5310): WARNING **: U"..., 96) = 96
write(10, "AT$TSSPCSW=1\r"..., 13)      = 13  
// I changed the normal AAT+CPROT=0 to this command, as it was used in
the windows software.
select(11, [10], NULL, NULL, {1, 0})     = 1 (in [10], left {0, 996000})
read(10, "AT$TSSPCSW=1\r"..., 100)      = 13
select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {1, 0})
read(10, "\r\nCONNECT\r\n"..., 87)      = 11
write(10, "\200\0\25\20\0\4\0F\0\16SYNCML-SYNC"..., 21) = 21
select(11, [10], NULL, NULL, {20, 0})     = 1 (in [10], left {19,
936000})
read(10, "\240\0\32\20\0\4\0\313\0\0\0\2J\0\16SYNCML-SYNC"..., 512) = 26

// OK you are right, here is a PUT sequence. The windows software
contains here the authentication sequence from the server.
write(10, "\202\0\337\313\0\0\0\2B\0 application/vnd.syncml"..., 223) =
223
select(11, [10], NULL, NULL, {20, 0})   = 1 (in [10], left {20, 0})
read(10, "\240\0\3"..., 512)            = 3
write(10, "\203\0(\313\0\0\0\2B\0 application/vnd.syncml"..., 40) = 40
select(11, [10], NULL, NULL, {20, 0})     = 1 (in [10], left {19,
952000})
// the phone E250i does not accept here. A phone E250 does not answer at
all at this place.
read(10, "\306\0\3"..., 512)            = 3
poll([{fd=5, events=POLLIN}], 1, 1)     = 0 (Timeout)
poll([{fd=5, events=POLLIN}], 1, 1) = 0 (Timeout)
poll([{fd=5, events=POLLIN}], 1, 1)     = 0 (Timeout)
poll([{fd=5, events=POLLIN}], 1, 1)     = 0 (Timeout)
poll([{fd=5, events=POLLIN}], 1, 1)     = 0 (Timeout)
poll([{fd=5, events=POLLIN}], 1, 1) = ? ERESTART_RESTARTBLOCK (To be
restarted)

Regards

Ulrich

Re: [Opensync-users] libsyncml internal error unknown response

From: Michael B. <mic...@cm...> - 2009-08-19 15:11:10

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Ulrich,

can you please sniff the communication of libsyncml with the mobile
again? I would like to see what the library is really doing. The traces
in the Trac ticket show that there was a PUT request and you wrote there
was only a visible GET request.

from log:

smlTransportObexClientSend: Done sending the put request


This sounds really obscure. After the PUT request usually a GET request
follows. If the first PUT request happens and only the GET request
failed then we have "only" to modifiy the first SyncML message.

Best regards

Michael
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqMFi0ACgkQ2L0ZGCAwWqv1GgCggQFSezgEHih8oNajawPNnx1Q
IOUAoOU3cVB5syhDUoJSKMPr7qfOCZ/c
=gx01
-----END PGP SIGNATURE-----

Re: [Opensync-users] libsyncml internal error unknown response

From: Michael B. <mic...@cm...> - 2009-08-19 15:54:48

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ulrich Brammer wrote:
> 
> OK, you are right, a short Put sequence was send. but it was quite
> different from the one in windows with the authentication enclosed.
> I looked into the communication of libsyncml and my phone with strace

Now it starts to be interesting ;)

> write(10, "ATZ\r"..., 4)                = 4
> select(11, [10], NULL, NULL, {1, 0})     = 1 (in [10], left {0, 852000})
> read(10, "ATZ\r"..., 100)               = 4
> select(11, [10], NULL, NULL, {1, 0})     = 1 (in [10], left {0, 996000})
> read(10, "\r\nOK\r\n"..., 96)           = 6
> write(10, "AT+CGMI\r"..., 8)            = 8
> select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {0, 996000})
> read(10, "AT+CGMI\r"..., 100)           = 8
> select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {1, 0})
> read(10, "\r\nSAMSUNG\r\n"..., 92)      = 11
> select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {1, 0})
> read(10, "\r\nOK\r\n"..., 81)           = 6
> write(10, "AT+CGMM\r"..., 8)            = 8
> select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {0, 996000})
> read(10, "AT+CGMM\r"..., 100)           = 8
> select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {0, 996000})
> read(10, "\r\nE250i\r\n"..., 92)        = 9
> select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {1, 0})
> read(10, "\r\nOK\r\n"..., 83)           = 6

This stuff is performed to get the necessary informations from the
mobile. We could implement every other AT command to get informations
from the mobile if we need it.

> write(2, "\n** (process:5310): WARNING **: U"..., 96) = 96

This should be the warning about an unknown Samsung mobile.

> write(10, "AT$TSSPCSW=1\r"..., 13)      = 13 
> // I changed the normal AAT+CPROT=0 to this command, as it was used in
> the windows software.
> select(11, [10], NULL, NULL, {1, 0})     = 1 (in [10], left {0, 996000})
> read(10, "AT$TSSPCSW=1\r"..., 100)      = 13
> select(11, [10], NULL, NULL, {1, 0})    = 1 (in [10], left {1, 0})
> read(10, "\r\nCONNECT\r\n"..., 87)      = 11

Any ideas what AT$TSSPCSW=1 means?

> // OK you are right, here is a PUT sequence. The windows software
> contains here the authentication sequence from the server.
> write(10, "\202\0\337\313\0\0\0\2B\0 application/vnd.syncml"..., 223) =
> 223
> select(11, [10], NULL, NULL, {20, 0})   = 1 (in [10], left {20, 0})
> read(10, "\240\0\3"..., 512)            = 3
> write(10, "\203\0(\313\0\0\0\2B\0 application/vnd.syncml"..., 40) = 40
> select(11, [10], NULL, NULL, {20, 0})     = 1 (in [10], left {19,
> 952000})
> // the phone E250i does not accept here. A phone E250 does not answer at
> all at this place.

The mobile does not answer and this means our message is wrong. So the
libsyncml OBEX code generally work we have just to modify it for your
Samsung E250.

First we need the correct AT command sequence. So do you know AT$TSSPCSW=1?

Michael

P.S. I go on holidays at Friday. So I think we cannot fix the issue
until September.
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqMIGQACgkQ2L0ZGCAwWquhzgCdHx6PkjiMSvlOHf0uoryw0gFV
M/8AmwXzdhiJQdYRRLl0Qn5Y3iBLdZhO
=RD9j
-----END PGP SIGNATURE-----

Re: [Opensync-users] libsyncml internal error unknown response

From: Ulrich B. <ubr...@t-...> - 2009-08-19 17:18:06

Am Mittwoch, den 19.08.2009, 17:55 +0200 schrieb Michael Bell:

> First we need the correct AT command sequence. So do you know AT$TSSPCSW=1?
> 
The AT command was send in the windows software just before the obex
communication started. So I think it is equivalent to AT+CPROT=0.

I found the AT-command also on this side:
http://tools.assembla.com/zsharp/wiki/AT
Samsung Z series AT command set

AT$TSSPCSW=1    Start OBEX connection 
AT$TSSPCSW=0    Terminate OBEX connection


> 
> P.S. I go on holidays at Friday. So I think we cannot fix the issue
> until September.

This is OK.

Ulrich