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 >
