Hi,
There seems to be an incombatibility between kannel's wbxml and Nokia's. I
intend to fix it, but in a month or so. In the meantime you might want to
compile the message manually, as described by Pai Peng.
BR,
Nikos
----- Original Message -----
From: "Tomas Verbaitis" <[email protected]>
To: <[email protected]>
Sent: Monday, March 16, 2009 1:24 PM
Subject: sendota problems
Hello,
I want to configure synchronization for Nokia 6070 mobile phone. My
program generates this XML provisioning document:
<?xml version="1.0"?>
<!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN"
"http://www.wapforum.org/DTD/prov.dtd";>
<wap-provisioningdoc>
<characteristic type="BOOTSTRAP">
<parm name="NAME" value="SKLADDEVEL"/>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w5"/>
<parm name="TO-NAPID" value="INTERNET" />
<parm name="NAME" value="SKLADDEVEL"/>
<parm name="ADDR" value="http://megalogika.stp.lt/funambol/ds"/>
<characteristic type="RESOURCE">
<parm name="URI" value="card"/>
<parm name="NAME" value="Contacts DB"/>
<parm name="AACCEPT" value="text/x-vcard"/>
</characteristic>
<characteristic type="RESOURCE">
<parm name="URI" value="cal"/>
<parm name="NAME" value="Calendar"/>
<parm name="AACCEPT" value="text/x-vcalendar"/>
</characteristic>
<characteristic type="RESOURCE">
<parm name="URI" value="notes"/>
<parm name="NAME" value="Notes"/>
<parm name="AACCEPT" value="text/plain"/>
</characteristic>
<characteristic type="APPAUTH">
<parm name="AAUTHNAME" value="funUsrVe"/>
<parm name="AAUTHSECRET" value="funPassVe"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>"
When i send it via Kannel's /sendota, via this request:
/cgi-bin/sendota?password=######&username=######&type=oma-settings&sec=USERPIN&pin=1234&to=%2B37069953201&text=%3C%3Fxml+version%3D%221.0%22%3F%3E%0A%3C%21DOCTYPE+wap-provisioningdoc+PUBLIC+%22-%2F%2FWAPFORUM%2F%2FDTD+PROV+1.0%2F%2FEN%22%0A%22http%3A%2F%2Fwww.wapforum.org%2FDTD%2Fprov.dtd%22%3E%0A%3Cwap-provisioningdoc%3E%0A%3Ccharacteristic+type%3D%22BOOTSTRAP%22%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SKLADDEVEL%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22APPLICATION%22%3E%0A%3Cparm+name%3D%22APPID%22+value%3D%22w5%22%2F%3E%0A%3Cparm+name%3D%22TO-NAPID%22+value%3D%22INTERNET%22+%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SKLADDEVEL%22%2F%3E%0A%3Cparm+name%3D%22ADDR%22+value%3D%22http%3A%2F%2Fmegalogika.stp.lt%2Ffunambol%2Fds%22%2F%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22card%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Contacts+DB%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fx-vcard%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22cal%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Calendar%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fx-vcalendar%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22notes%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Notes%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fplain%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22APPAUTH%22%3E%0A%3Cparm+name%3D%22AAUTHNAME%22+value%3D%22funUsrVe%22%2F%3E%0A%3Cparm+name%3D%22AAUTHSECRET%22+value%3D%22funPassVe%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3C%2Fcharacteristic%3E%0A%3C%2Fwap-provisioningdoc%3E
it generates a single sms message:
0051000B9173x0xxxxxxFx0004A7870605040B840B8401062F1F2DB69181923738424536353833373946364436324435394544374431323831443536454141423541343346353500030B6A0045C65003424F4F54535452415000018705034E414D45000603534B4C4144444556454C000101C650034150504C49434154494F4E0001870503415050494400060377350001870503544F
which is successfully delivered to the handset which then claims that it
is 'Unable to save settings. Setttings discarded.'
I tried this via GET request and POST request as well (not XML post,
though, because I could not find anything concerning OMA CP in the
examples provided in Kannel user guide).
Meanwhile, NowSMS generates 3 messages:
0051000B917xx0xxxxxxFx0004A78C0B05040B8423F0000305030105062F1F2DB69181924144304542424539423642323245443636433746433236353435373437433036373243394243454300030B6A0C54657374310074657374310045C6560187070683000101C6000155018736000006037735000187220603494E5445524E455400018707068300018700013400000603687474703A2F2F6D
0051000B9173x0xxxxxxFx004A77D0B05040B8423F0000305030320444200018700012E00000603746578742F782D7663616C656E646172000101C600015901873A000006032E2F6E6F7465730001870706034E6F74657320444200018700012E00000603746578742F706C61696E000101C600015701873100000683060187000132000006830601010101
0051000B9173x0xxxxxxFx0004A78C0B05040B8423F000030503026567616C6F67696B612E7374702E6C742F66756E616D626F6C2F64730001C600015901873A000006032E2F636F6E7461637473000187070603436F6E746163747320444200018700012E00000603746578742F782D7663617264000101C600015901873A000006032E2F63616C656E64617200018707060343616C656E646172
which are successfully delivered to the phone and recognized by it as a
valid and working synchronization settings. Funnily enough, these three
messages are routed via the same kannel.
Therefore my questions are:
* is Kannel wrongly transforming my request into OMA settings provisioning
message?
* if so, is it because of my error or because of a bug in Kannel?
any other advice?
--
Tomas "Verbaitis" Verbaitis ** http://megalogika.lt
--- Begin Message ---
Hello,
sorry it should be problem by text encoding ( for 'TAB'), so here is it
again:
-------------------------------
<?xml version="1.0" encoding="UTF-8" standalone = "yes" ?>
<!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" "
http://www.wapforum.org/DTD/prov.dtd";>
<wap-provisioningdoc>
<!-- WLAN AP profile settings -->
<characteristic type="NAPDEF">
<parm name="NAME" value="wlanssid"></parm>
<parm name="NAPID" value="wlanssid"></parm>
<parm name="PROVIDER-ID" value="wlanssid"></parm>
<parm name="BEARER" value="WLAN"></parm>
<characteristic type="WLAN">
<parm name="PRI-SSID" value="wlanssid"></parm>
<parm name="NETMODE" value="INFRA"></parm>
<parm name="SECMODE" value="WPA-PRESHARED-KEY"></parm>
<parm name="WPA-PRES-KEY-ASC" value="password"></parm>
</characteristic>
</characteristic>
</wap-provisioningdoc>
-------------------------------
Regards
Pai
---------- Forwarded message ----------
From: Nikos Balkanas <[email protected]>
Date: 2009/2/25
Subject: Re: xml to wbxml compiler incorrect by 1.4.2!?
To: Pai Peng <[email protected]>, [email protected]
Hi,
No, it is not a problem for me to get it. Input string is the important
part. What is the deal with the BB's? I imagine they are not part of the
message. I have to implement something important now, but I will look at it
immediately after.
Thanx,
Nikos
----- Original Message -----
*From:* Pai Peng <[email protected]>
*To:* [email protected]
*Sent:* Wednesday, February 25, 2009 9:50 AM
*Subject:* Fwd: xml to wbxml compiler incorrect by 1.4.2!?
Hello Nikos,
so as example for WLAN Access Point OMA Provisioning for Nokia:
<?xml version="1.0" encoding="UTF-8" standalone = "yes" ?>
<!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" "
http://www.wapforum.org/DTD/prov.dtd";>
<wap-provisioningdoc>
<!-- WLAN AP profile settings -->
<characteristic type="NAPDEF">
Β Β Β <parm name="NAME" value="wlanssid"></parm>
Β Β Β <parm name="NAPID" value="wlanssid"></parm>
Β Β Β <parm name="PROVIDER-ID" value="wlanssid"></parm>
Β Β Β <parm name="BEARER" value="WLAN"></parm>
Β Β Β <characteristic type="WLAN">
Β Β Β Β Β Β <parm name="PRI-SSID" value="wlanssid"></parm>
Β Β Β Β Β Β <parm name="NETMODE" value="INFRA"></parm>
Β Β Β Β Β Β <parm name="SECMODE" value="WPA-PRESHARED-KEY"></parm>
Β Β Β Β Β Β <parm name="WPA-PRES-KEY-ASC" value="password"></parm>
Β Β Β </characteristic>
</characteristic>
</wap-provisioningdoc>
the encoded wbxml binary format can be read in debug mode of smsc. (encoded
by kannel with file ota_compile.c, not wmlsc or wmlsadm). Sorry I can't read
the binary format directly on this PC, and it shouldn't be a problem for you
to get it, istn't it?
As document:
http://www.forum.nokia.com/info/sw.nokia.com/id/1b4c4ecc-f788-44fa-98bc-1654042eb010/S60_Platform_OMA_Client_Provisioning_v2_1_en.pdf.html
Regards
Pai
---------- Forwarded message ----------
From: Nikos Balkanas <[email protected]>
Date: 2009/2/25
Subject: Re: xml to wbxml compiler incorrect by 1.4.2!?
To: Pai Peng <[email protected]>, [email protected]
Hi,
Β
It cannot be a problem by Nokia. Otherwise libwbxml2 wouldn't encode it.
More likely it seems to be a kannel hickup. Again I would appreciate if
someone could send input string, string encoded by kannel (wmlsc, wmlsadm,
etc.) and libwbxml2 so that I can track the problem. This could make things
easier for anybody involved, since you wouldn't have to create the
wbxmlΒ with libwbxml2 and then feedΒ it into kannel.
Β
BR,
Nikos
----- Original Message -----
*From:* Pai Peng <[email protected]>
*To:* [email protected]
*Sent:* Wednesday, February 25, 2009 1:30 AM
*Subject:* Fwd: xml to wbxml compiler incorrect by 1.4.2!?
Hello Zillur,
thanks for sharing your information, just after solved my problem. It is a
bit later for me, but should be not for the following people.
To Nikos:
What I can confirm is, that the encoded WBXML by Kannel can be decoded into
XMl by wbxml Library.
Only the Nokia looks like not to be compatible with Kannel by OMA
provisioning (WBXML).
There is no reference for Nokia WBXML standard, and I can't figure out the
problem on the Nokia device. But if I find something useful, i will share
with you to improve the Kannel by Nokia OMA provisioning.
Regards
Pai
---------- Forwarded message ----------
From: zillur rahman <[email protected]>
Date: Mon, Feb 23, 2009 at 6:31 PM
Subject: Re: xml to wbxml compiler incorrect by 1.4.2!?
To: Pai Peng <[email protected]>
Hi Pai,
I had a little bit of same probelem. I tried to send GPRS OMA
configuration Message through Kannel. But at the Nokia and all other
sets message come in invalid format. later Ξ’Β used xml2wbxml tool in
Linux and send the sms using UDH through Kannel. Now all nokia set
successfully received the configuration message. At that time i
studied on OAM configuation Message to configure GPRS,MMS etc. It
seems everything is possible by yourself.
Thanks
Zillur
On Wed, Feb 4, 2009 at 1:15 AM, Pai Peng <[email protected]> wrote:
> hello,
>
>
> i have dumped the wbxml data for a OTA-Prov XML into a binary file, which
> data is converted by ota_compiler.c.
>
> With libxbxml tool (convert wbxml back to xml) to check validity, I got
> error by wbxml2xml:
>
> ***************************
> Ξ’Β Converting file: output.wbxml
> (0) Parsed version: '0x1'
> (1) Parsed publicid: '0x6'
> (2) Parsed charset: '0x2F'
> (3) Parsing strtbl
> Ξ’Β Ξ’Β Ξ’Β Checking PublicID
> Ξ’Β Ξ’Β Ξ’Β PublicID token: 0x6
> Ξ’Β Ξ’Β Ξ’Β PublicID : '-//WAPFORUM//DTD SL 1.0//EN'
> (35) Parsing body
> (35) Parsing element
> (35) Parsing stag
> (36) Parsing content: '0x33'
> (36) Parsing element
> (36) Parsing stag
> (37) Parsing content: '0x34'
> (37) Parsing element
> (37) Parsing stag
> (38) Parsing content: '0x34'
> (38) Parsing element
> (38) Parsing stag
> (39) Parsing content: '0x39'
> (39) Parsing element
> (39) Parsing stag
> (40) Parsing content: '0x44'
> (40) Parsing element
> (40) Parsing stag
> (40) Parsing literalTag
> WBXML Parser failed at 41 - token: 34 (Invalid String Table Index)
> wbxml2xml convertion failed - WBXML Parser Error: Invalid String Table
Index
> Current allocations: 0 areas, 0 bytes
> Highest number of allocations: 33 areas
> Highest memory usage: 6001 bytes
>
> I can be sure, that the wbxml2xml works corretly.
> So my question is, if the kannel's implementation of wbxml is correct or
the
> compatibility protocol with libwbxml? has somebody got the same problem by
> XML to WBXML converting?
>
>
> Regards
>
> Pai
>
--- End Message ---
