Click here to get back home

[omadmclient] Why does not the device respond the DM server comman
 Home | NewsGroups | Search | About
Login Password
Register Now!
 microsoft.public.smartphone.developer    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
[omadmclient] Why does not the device respond the DM server comman YR Hong 01-21-2008
Get Chitika Premium
Posted by YR Hong on January 21, 2008, 1:27 am
Please log in for more thread options
 I'm trying to connect the WM6 device to the my test server (funambol dm
server 3.5.1), but the device always close the session after receiving the
server commands.
I want to know what is wrong and which should I check?

1) The device is successfully bootstrapped with a following OTA provisioning
message:
<wap-provisioningdoc version="1.1">
<characteristic type="APPLICATION">
<parm name="APPID" value="w7"/>
<parm name="PROVIDER-ID" value="funambol"/>
<parm name="NAME" value="funambol"/>
<parm name="DEFAULTENCODING" value="application/vnd.syncml.dm+wbxml"/>
<parm name="PROTOVER" value="1.2"/>
<parm name="ROLE" value="24"/>
<parm name="USEHWDEVID"/>
<parm name="USENONCERESYNC"/>
<parm name="INIT"/>
<parm name="ADDR" value="https://dm2.servebbs.com/funambol/dm"/>
<characteristic type="APPAUTH">
<parm name="AAUTHLEVEL" value="APPSRV"/>
<parm name="AAUTHTYPE" value="DIGEST"/>
<parm name="AAUTHNAME" value="funambol"/>
<parm name="AAUTHSECRET" value="funambol"/>
<parm name="AAUTHDATA" value="bnVsbA=="/>
</characteristic>
<characteristic type="APPAUTH">
<parm name="AAUTHLEVEL" value="CLIENT"/>
<parm name="AAUTHTYPE" value="DIGEST"/>
<parm name="AAUTHSECRET" value="srvpwd"/>
<parm name="AAUTHDATA" value="bnVsbA=="/>
</characteristic>
</characteristic>
</wap-provisioningdoc>

2) The DM server sent the notification message to the device to collect some
device information.

3) The device accpeted the notification message and connected to the server
sending following message:
<?xml version="1.0" encoding="UTF-8"?>
<SyncML>
<SyncHdr>
<VerDTD>1.2</VerDTD>
<VerProto>DM/1.2</VerProto>
<SessionID>1</SessionID>
<MsgID>1</MsgID>
<Target>
<LocURI>https://dm2.servebbs.com/funambol/dm</LocURI>
</Target>
<Source>
<LocURI>IMEI:351602000266970</LocURI>
<LocName>funambol</LocName>
</Source>
<Cred>
<Meta>
<Format>b64</Format>
<Type>syncml:auth-md5</Type>
</Meta>
<Data>+EdEwHSJYF7xOIYFaOpURw==</Data>
</Cred>
</SyncHdr>
<SyncBody>
<Alert>
<CmdID>2</CmdID>
<Data>1200</Data>
</Alert>
<Replace>
<CmdID>3</CmdID>
<Item>
<Source>
<LocURI>./DevInfo/DevId</LocURI>
</Source>
<Data>IMEI:351602000266970</Data>
</Item>
<Item>
<Source>
<LocURI>./DevInfo/Man</LocURI>
</Source>
<Data>LGE</Data>
</Item>
<Item>
<Source>
<LocURI>./DevInfo/Mod</LocURI>
</Source>
<Data>KS</Data>
</Item>
<Item>
<Source>
<LocURI>./DevInfo/DmV</LocURI>
</Source>
<Data>1.2</Data>
</Item>
<Item>
<Source>
<LocURI>./DevInfo/Lang</LocURI>
</Source>
<Data>en</Data>
</Item>
</Replace>
<Final></Final>
</SyncBody>
</SyncML>

4) The server sent the response message to the device:
<?xml version="1.0" encoding="UTF-8"?>
<SyncML>
<SyncHdr>
<VerDTD>1.2</VerDTD>
<VerProto>DM/1.2</VerProto>
<SessionID>1</SessionID>
<MsgID>1</MsgID>
<Target>
<LocURI>IMEI:351602000266970</LocURI>
<LocName>funambol</LocName>
</Target>
<Source>
<LocURI>https://dm2.servebbs.com/funambol/dm</LocURI>
<LocName>funambol</LocName>
</Source>
<Cred>
<Meta>
<Format>b64</Format>
<Type>syncml:auth-md5</Type>
</Meta>
<Data>FJI6dPTSAvgTcb8/242g+Q==</Data>
</Cred>
</SyncHdr>
<SyncBody>
<Status>
<CmdID>1</CmdID>
<MsgRef>1</MsgRef>
<CmdRef>0</CmdRef>
<Cmd>SyncHdr</Cmd>
<TargetRef>https://dm2.servebbs.com/funambol/dm</TargetRef>
<SourceRef>IMEI:351602000266970</SourceRef>
<Chal>
<Meta>
<Format>b64</Format>
<Type>syncml:auth-md5</Type>
<NextNonce>LiMqSFc6LyBIMDxedTNnTg==</NextNonce>
</Meta>
</Chal>
<Data>212</Data>
</Status>
<Status>
<CmdID>2</CmdID>
<MsgRef>1</MsgRef>
<CmdRef>2</CmdRef>
<Cmd>Alert</Cmd>
<Data>200</Data>
</Status>
<Status>
<CmdID>3</CmdID>
<MsgRef>1</MsgRef>
<CmdRef>3</CmdRef>
<Cmd>Replace</Cmd>
<Data>200</Data>
</Status>
<Get>
<CmdID>4</CmdID>
<Item>
<Target>
<LocURI>./DevDetail/FwV</LocURI>
</Target>
</Item>
</Get>
<Get>
<CmdID>5</CmdID>
<Item>
<Target>
<LocURI>./DevDetail/SwV</LocURI>
</Target>
</Item>
</Get>
<Alert>
<CmdID>6</CmdID>
<Data>1100</Data>
<Item>
<Data>MINDT=5&MAXDT=15</Data>
</Item>
<Item>
<Data>Funambol DM Demo</Data>
</Item>
</Alert>
<Final></Final>
</SyncBody>
</SyncML>

5) The device informed user of error message and the registry value of
sessionHRESULT was '2156068870 (0x80830006)'.

And one more question: As I know the funambole dm server stores the next
server nonce received from the device as received (it is B64 encoded format),
but the server stores the next server nonce by decoding B64. Can someone
explain this?

Thank you,
Young-Rae Hong
LGE Mobile Communication R&D Center

Posted by Sean Bowles [MS] on January 24, 2008, 7:04 pm
Please log in for more thread options
 I can't help you with the server issue, but cause of error 0x80830006 is
that the WBXML contains an invalid or unsupported public ID.

Can you send/attach the server package as WBXML?

Sean Bowles [MS]
This Posting is provided "AS IS" with no warranties, and confers no rights.

> I'm trying to connect the WM6 device to the my test server (funambol dm
> server 3.5.1), but the device always close the session after receiving the
> server commands.
> I want to know what is wrong and which should I check?
>
> 1) The device is successfully bootstrapped with a following OTA
> provisioning
> message:
> <wap-provisioningdoc version="1.1">
> <characteristic type="APPLICATION">
> <parm name="APPID" value="w7"/>
> <parm name="PROVIDER-ID" value="funambol"/>
> <parm name="NAME" value="funambol"/>
> <parm name="DEFAULTENCODING" value="application/vnd.syncml.dm+wbxml"/>
> <parm name="PROTOVER" value="1.2"/>
> <parm name="ROLE" value="24"/>
> <parm name="USEHWDEVID"/>
> <parm name="USENONCERESYNC"/>
> <parm name="INIT"/>
> <parm name="ADDR" value="https://dm2.servebbs.com/funambol/dm"/>
> <characteristic type="APPAUTH">
> <parm name="AAUTHLEVEL" value="APPSRV"/>
> <parm name="AAUTHTYPE" value="DIGEST"/>
> <parm name="AAUTHNAME" value="funambol"/>
> <parm name="AAUTHSECRET" value="funambol"/>
> <parm name="AAUTHDATA" value="bnVsbA=="/>
> </characteristic>
> <characteristic type="APPAUTH">
> <parm name="AAUTHLEVEL" value="CLIENT"/>
> <parm name="AAUTHTYPE" value="DIGEST"/>
> <parm name="AAUTHSECRET" value="srvpwd"/>
> <parm name="AAUTHDATA" value="bnVsbA=="/>
> </characteristic>
> </characteristic>
> </wap-provisioningdoc>
>
> 2) The DM server sent the notification message to the device to collect
> some
> device information.
>
> 3) The device accpeted the notification message and connected to the
> server
> sending following message:
> <?xml version="1.0" encoding="UTF-8"?>
> <SyncML>
> <SyncHdr>
> <VerDTD>1.2</VerDTD>
> <VerProto>DM/1.2</VerProto>
> <SessionID>1</SessionID>
> <MsgID>1</MsgID>
> <Target>
> <LocURI>https://dm2.servebbs.com/funambol/dm</LocURI>
> </Target>
> <Source>
> <LocURI>IMEI:351602000266970</LocURI>
> <LocName>funambol</LocName>
> </Source>
> <Cred>
> <Meta>
> <Format>b64</Format>
> <Type>syncml:auth-md5</Type>
> </Meta>
> <Data>+EdEwHSJYF7xOIYFaOpURw==</Data>
> </Cred>
> </SyncHdr>
> <SyncBody>
> <Alert>
> <CmdID>2</CmdID>
> <Data>1200</Data>
> </Alert>
> <Replace>
> <CmdID>3</CmdID>
> <Item>
> <Source>
> <LocURI>./DevInfo/DevId</LocURI>
> </Source>
> <Data>IMEI:351602000266970</Data>
> </Item>
> <Item>
> <Source>
> <LocURI>./DevInfo/Man</LocURI>
> </Source>
> <Data>LGE</Data>
> </Item>
> <Item>
> <Source>
> <LocURI>./DevInfo/Mod</LocURI>
> </Source>
> <Data>KS</Data>
> </Item>
> <Item>
> <Source>
> <LocURI>./DevInfo/DmV</LocURI>
> </Source>
> <Data>1.2</Data>
> </Item>
> <Item>
> <Source>
> <LocURI>./DevInfo/Lang</LocURI>
> </Source>
> <Data>en</Data>
> </Item>
> </Replace>
> <Final></Final>
> </SyncBody>
> </SyncML>
>
> 4) The server sent the response message to the device:
> <?xml version="1.0" encoding="UTF-8"?>
> <SyncML>
> <SyncHdr>
> <VerDTD>1.2</VerDTD>
> <VerProto>DM/1.2</VerProto>
> <SessionID>1</SessionID>
> <MsgID>1</MsgID>
> <Target>
> <LocURI>IMEI:351602000266970</LocURI>
> <LocName>funambol</LocName>
> </Target>
> <Source>
> <LocURI>https://dm2.servebbs.com/funambol/dm</LocURI>
> <LocName>funambol</LocName>
> </Source>
> <Cred>
> <Meta>
> <Format>b64</Format>
> <Type>syncml:auth-md5</Type>
> </Meta>
> <Data>FJI6dPTSAvgTcb8/242g+Q==</Data>
> </Cred>
> </SyncHdr>
> <SyncBody>
> <Status>
> <CmdID>1</CmdID>
> <MsgRef>1</MsgRef>
> <CmdRef>0</CmdRef>
> <Cmd>SyncHdr</Cmd>
> <TargetRef>https://dm2.servebbs.com/funambol/dm</TargetRef>
> <SourceRef>IMEI:351602000266970</SourceRef>
> <Chal>
> <Meta>
> <Format>b64</Format>
> <Type>syncml:auth-md5</Type>
> <NextNonce>LiMqSFc6LyBIMDxedTNnTg==</NextNonce>
> </Meta>
> </Chal>
> <Data>212</Data>
> </Status>
> <Status>
> <CmdID>2</CmdID>
> <MsgRef>1</MsgRef>
> <CmdRef>2</CmdRef>
> <Cmd>Alert</Cmd>
> <Data>200</Data>
> </Status>
> <Status>
> <CmdID>3</CmdID>
> <MsgRef>1</MsgRef>
> <CmdRef>3</CmdRef>
> <Cmd>Replace</Cmd>
> <Data>200</Data>
> </Status>
> <Get>
> <CmdID>4</CmdID>
> <Item>
> <Target>
> <LocURI>./DevDetail/FwV</LocURI>
> </Target>
> </Item>
> </Get>
> <Get>
> <CmdID>5</CmdID>
> <Item>
> <Target>
> <LocURI>./DevDetail/SwV</LocURI>
> </Target>
> </Item>
> </Get>
> <Alert>
> <CmdID>6</CmdID>
> <Data>1100</Data>
> <Item>
> <Data>MINDT=5&MAXDT=15</Data>
> </Item>
> <Item>
> <Data>Funambol DM Demo</Data>
> </Item>
> </Alert>
> <Final></Final>
> </SyncBody>
> </SyncML>
>
> 5) The device informed user of error message and the registry value of
> sessionHRESULT was '2156068870 (0x80830006)'.
>
> And one more question: As I know the funambole dm server stores the next
> server nonce received from the device as received (it is B64 encoded
> format),
> but the server stores the next server nonce by decoding B64. Can someone
> explain this?
>
> Thank you,
> Young-Rae Hong
> LGE Mobile Communication R&D Center



Posted by yrhong@yahoo.co.kr on January 28, 2008, 1:47 am
Please log in for more thread options
Hi Sean,

Thank you for your response.

I analized two server packages from the Windows Mobile update server
and the funambol server.
And I found the difference between two.
1) The WM Update server sends the pacakge starting "<b>02 A4 01 6A 00
6D 6C 71 03 31 2E 32 00 01</b> 72 03 44 4D 2F 31 2E 32 00 01 ..." (.?
j.mlq.1.2..r.DM/1.2)
2) The funambol server sends the package starting "<b>02 00 00 6A 1D
2D 2F 2F 53 59 4E 43 4D 4C 2F 2F 44 54 44 20 53 79 6E 63 4D 4C 20 31
2E 32 2F 2F 45 4E 6D 6C 71 03 31 2E 32 00 01</b> 72 03 44 4D 2F 31 2E
32 00 01 ..." (...j.-//SYNCML//DTD SyncML 1.2//ENmlq.1.2..r.DM/1.2)

Does not the WM6 support the DTD version string (.-//SYNCML//DTD
SyncML 1.2//EN)?

FYI when I set the DefaultEncoding as "application/vnd.syncml.dm+xml"
the WM6 works well.

Thanks,
Young-Rae Hong

On 1=BF=F925=C0=CF, =BF=C0=C0=FC9=BD=C304=BA=D0, "Sean Bowles [MS]" <sb...@o=
nline.microsoft.com>
wrote:
> I can't help you with the server issue, but cause of error 0x80830006 is
> that the WBXML contains an invalid or unsupported public ID.
>
> Can you send/attach the server package as WBXML?
>
> Sean Bowles [MS]
> This Posting is provided "AS IS" with no warranties, and confers no rights=
.
>
>
>
>
>
> > I'm trying to connect the WM6 device to the my test server (funambol dm
> > server 3.5.1), but the device always close the session after receiving t=
he
> > server commands.
> > I want to know what is wrong and which should I check?
>
> > 1) The device is successfully bootstrapped with a following OTA
> > provisioning
> > message:
> > <wap-provisioningdoc version=3D"1.1">
> > <characteristic type=3D"APPLICATION">
> > <parm name=3D"APPID" value=3D"w7"/>
> > <parm name=3D"PROVIDER-ID" value=3D"funambol"/>
> > <parm name=3D"NAME" value=3D"funambol"/>
> > <parm name=3D"DEFAULTENCODING" value=3D"application/vnd.syncml.dm+wbx=
ml"/>
> > <parm name=3D"PROTOVER" value=3D"1.2"/>
> > <parm name=3D"ROLE" value=3D"24"/>
> > <parm name=3D"USEHWDEVID"/>
> > <parm name=3D"USENONCERESYNC"/>
> > <parm name=3D"INIT"/>
> > <parm name=3D"ADDR" value=3D"https://dm2.servebbs.com/funambol/dm"/>
> > <characteristic type=3D"APPAUTH">
> > <parm name=3D"AAUTHLEVEL" value=3D"APPSRV"/>
> > <parm name=3D"AAUTHTYPE" value=3D"DIGEST"/>
> > <parm name=3D"AAUTHNAME" value=3D"funambol"/>
> > <parm name=3D"AAUTHSECRET" value=3D"funambol"/>
> > <parm name=3D"AAUTHDATA" value=3D"bnVsbA=3D=3D"/>
> > </characteristic>
> > <characteristic type=3D"APPAUTH">
> > <parm name=3D"AAUTHLEVEL" value=3D"CLIENT"/>
> > <parm name=3D"AAUTHTYPE" value=3D"DIGEST"/>
> > <parm name=3D"AAUTHSECRET" value=3D"srvpwd"/>
> > <parm name=3D"AAUTHDATA" value=3D"bnVsbA=3D=3D"/>
> > </characteristic>
> > </characteristic>
> > </wap-provisioningdoc>
>
> > 2) The DM server sent the notification message to the device to collect
> > some
> > device information.
>
> > 3) The device accpeted the notification message and connected to the
> > server
> > sending following message:
> > <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> > <SyncML>
> > <SyncHdr>
> > <VerDTD>1.2</VerDTD>
> > <VerProto>DM/1.2</VerProto>
> > <SessionID>1</SessionID>
> > <MsgID>1</MsgID>
> > <Target>
> > <LocURI>https://dm2.servebbs.com/funambol/dm</LocURI>
> > </Target>
> > <Source>
> > <LocURI>IMEI:351602000266970</LocURI>
> > <LocName>funambol</LocName>
> > </Source>
> > <Cred>
> > <Meta>
> > <Format>b64</Format>
> > <Type>syncml:auth-md5</Type>
> > </Meta>
> > <Data>+EdEwHSJYF7xOIYFaOpURw=3D=3D</Data>
> > </Cred>
> > </SyncHdr>
> > <SyncBody>
> > <Alert>
> > <CmdID>2</CmdID>
> > <Data>1200</Data>
> > </Alert>
> > <Replace>
> > <CmdID>3</CmdID>
> > <Item>
> > <Source>
> > <LocURI>./DevInfo/DevId</LocURI>
> > </Source>
> > <Data>IMEI:351602000266970</Data>
> > </Item>
> > <Item>
> > <Source>
> > <LocURI>./DevInfo/Man</LocURI>
> > </Source>
> > <Data>LGE</Data>
> > </Item>
> > <Item>
> > <Source>
> > <LocURI>./DevInfo/Mod</LocURI>
> > </Source>
> > <Data>KS</Data>
> > </Item>
> > <Item>
> > <Source>
> > <LocURI>./DevInfo/DmV</LocURI>
> > </Source>
> > <Data>1.2</Data>
> > </Item>
> > <Item>
> > <Source>
> > <LocURI>./DevInfo/Lang</LocURI>
> > </Source>
> > <Data>en</Data>
> > </Item>
> > </Replace>
> > <Final></Final>
> > </SyncBody>
> > </SyncML>
>
> > 4) The server sent the response message to the device:
> > <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> > <SyncML>
> > <SyncHdr>
> > <VerDTD>1.2</VerDTD>
> > <VerProto>DM/1.2</VerProto>
> > <SessionID>1</SessionID>
> > <MsgID>1</MsgID>
> > <Target>
> > <LocURI>IMEI:351602000266970</LocURI>
> > <LocName>funambol</LocName>
> > </Target>
> > <Source>
> > <LocURI>https://dm2.servebbs.com/funambol/dm</LocURI>
> > <LocName>funambol</LocName>
> > </Source>
> > <Cred>
> > <Meta>
> > <Format>b64</Format>
> > <Type>syncml:auth-md5</Type>
> > </Meta>
> > <Data>FJI6dPTSAvgTcb8/242g+Q=3D=3D</Data>
> > </Cred>
> > </SyncHdr>
> > <SyncBody>
> > <Status>
> > <CmdID>1</CmdID>
> > <MsgRef>1</MsgRef>
> > <CmdRef>0</CmdRef>
> > <Cmd>SyncHdr</Cmd>
> > <TargetRef>https://dm2.servebbs.com/funambol/dm</TargetRef>
> > <SourceRef>IMEI:351602000266970</SourceRef>
> > <Chal>
> > <Meta>
> > <Format>b64</Format>
> > <Type>syncml:auth-md5</Type>
> > <NextNonce>LiMqSFc6LyBIMDxedTNnTg=3D=3D</NextNonce>
> > </Meta>
> > </Chal>
> > <Data>212</Data>
> > </Status>
> > <Status>
> > <CmdID>2</CmdID>
> > <MsgRef>1</MsgRef>
> > <CmdRef>2</CmdRef>
> > <Cmd>Alert</Cmd>
> > <Data>200</Data>
> > </Status>
> > <Status>
> > <CmdID>3</CmdID>
> > <MsgRef>1</MsgRef>
> > <CmdRef>3</CmdRef>
> > <Cmd>Replace</Cmd>
> > <Data>200</Data>
> > </Status>
> > <Get>
> > <CmdID>4</CmdID>
> > <Item>
> > <Target>
> > <LocURI>./DevDetail/FwV</LocURI>
> > </Target>
> > </Item>
> > </Get>
> > <Get>
> > <CmdID>5</CmdID>
> > <Item>
> > <Target>
> > <LocURI>./DevDetail/SwV</LocURI>
> > </Target>
> > </Item>
> > </Get>
> > <Alert>
> > <CmdID>6</CmdID>
> > <Data>1100</Data>
> > <Item>
> > <Data>MINDT=3D5&MAXDT=3D15</Data>
> > </Item>
> > <Item>
> > <Data>Funambol DM Demo</Data>
> > </Item>
> > </Alert>
> > <Final></Final>
> > </SyncBody>
> > </SyncML>
>
> > 5) The device informed user of error message and the registry value of
> > sessionHRESULT was '2156068870 (0x80830006)'.
>
> > And one more question: As I know the funambole dm server stores the next=

> > server nonce received from the device as received (it is B64 encoded
> > format),
> > but the server stores the next server nonce by decoding B64. Can someone=

> > explain this?
>
> > Thank you,
> > Young-Rae Hong
> > LGE Mobile Communication R&D Center- =B5=FB=BF=C2 =C5=D8=BD=BA=C6=AE =BC=
=FB=B1=E2=B1=E2 -
>
> - =B5=FB=BF=C2 =C5=D8=BD=BA=C6=AE =BA=B8=B1=E2 -


Similar ThreadsPosted
Bootstrap a device to use an OMA DM server July 19, 2007, 5:34 am
Mobile as a server October 14, 2005, 5:41 am
Smartphone Client Server January 18, 2006, 3:37 am
Bluetooth OBEX server not up!! February 1, 2006, 1:24 am
Help about placing files on FTP server ! April 21, 2006, 2:26 am
Help about placing a file on a FTP server April 26, 2006, 8:17 am
Error when connecting to SQL Server April 5, 2007, 3:44 pm
LDAP - Cannot connect to a server July 13, 2007, 10:49 am
How to prevent to play WMV/WMA on streaming server June 13, 2005, 1:51 am
How to config Smartphone emulator to use OMA DM Server or other se August 25, 2006, 3:40 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap