MSFT PXLOGICAL CSP - overwrite existing settings(using mwid)

MSFT PXLOGICAL CSP - overwrite existing settings(using mwid) SearchSearch
Author Message
chenyuchang
New member
Username: Chenyu

Post Number: 1
Registered: 12-2008
Posted on Monday, December 22, 2008 - 11:04 am:   

I want to test behavior of client provisioning in WM , but I can't
provisioning successfully in PXLOGICAL when overwrite or add new settings.

The following two files can config successfully by rapiconfig.exe, but when
I using NOW SMS to send wap push , it's doesn't work.Could anyone help me?
Thanks!


First xml

<wap-provisioningdoc version="1.1">
<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="www.operator.com"/>
<parm name="NAME" value="DefaultProxy"/>
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="PROXY_WAP_1"/>
<parm name="PXADDR" value="10.138.255.129"/>
<parm name="TO-NAPID" value="chenyuADD_GPRS1" />
<characteristic type="PORT">
<parm name="PORTNBR" value="8080"/>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAPID" value="chenyuADD_GPRS1"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAME" value="cheny's GPRS Connection"/>
<parm name="NAP-ADDRESS" value="+XXXXXXXXXXX"/>
<parm name="NAP-ADDRTYPE" value="APN"/>
<parm name="LOCAL-ADDR" value="168.168.168.167"/>
<parm name="LOCAL-ADDRTYPE" value="IPv4"/>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="chenyu user"/>
<parm name="AUTHSECRET" value="chenyu's secret"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>


Second xml

<wap-provisioningdoc version="1.1">
<characteristic type="PXLOGICAL" >
<characteristic type="www.operator.com" mwid="1">
<parm name="NAME" value="DefaultProxy"/>
<!-- new setting -->
<parm name="DOMAIN" value="test.domain.com" />
<characteristic type="PXPHYSICAL">
<characteristic type="PROXY_WAP_1" mwid="1">
<parm name="PXADDR" value="10.138.255.129"/>
<parm name="TO-NAPID" value="chenyuADD_GPRS1"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="80"/>
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
chenyuchang
New member
Username: Chenyu

Post Number: 4
Registered: 12-2008
Posted on Tuesday, January 06, 2009 - 03:47 am:   

I know where the problem is. NowSMS can't encode attribute "mwid".
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7727
Registered: 10-2002
Posted on Wednesday, January 07, 2009 - 08:44 pm:   

You're correct. Any tag names or attribute names that are not defined in the OMA Provisioning Content XML schema are not encoded by NowSMS.

As Windows Mobile does define several additional tag and attribute names in its extensions to the OMA Provisioning Content, we should support them.

I've posted an update at http://www.nowsms.com/download/nowsms2009.zip. That version does encode any tag/attribute names.

-bn
chenyuchang
New member
Username: Chenyu

Post Number: 5
Registered: 12-2008
Posted on Thursday, January 08, 2009 - 01:49 pm:   

wow!
What a wonderful update!
I don't have to encode wbxml by myself any more.
thanks :-)