Hello Nikos,
sorry for so later response. Because I didn't get any helps at this problem, I am now using wbxml2 library for xml2wbxml converting instead of 'ota_compile.c' in the Kannel. After some tests, Now the OTA SMS Provisioning to Nokia device works properly. I don't know exactly what is not compatibility between Kannel's xml2wbxml and Nokia's wbxml. Anyway, I can work forward with Kannel. If anyone has the same problem, who can try to use xml2wbxml by converting. Regards Pai 2009/2/5 Nikos Balkanas <[email protected]> > Hi, > > Best address these questions to the list. As for myself I cannot address > much until next week, when I come back. > > BR, > Nikos > > ----- Original Message ----- > *From:* Pai Peng <[email protected]> > *To:* Nikos Balkanas <[email protected]> > *Sent:* Thursday, February 05, 2009 7:25 PM > *Subject:* Re: xml to wbxml compiler incorrect by 1.4.2!? > > hello Nikos, > > > (are you one of developers for Kannel?) > > anyway, thanks for your attention. > > > I must correct my statement, that the ota-compile is compilation to > libwbxml. > > I have dumped the wrong binary data (Msg->sms.msgdata, instead of > ota_binary) into the wbxml file. It means, the binary data includes 50 bytes > head. It makes the wbxml2xml error by converting. It's my mistake. > > > But still the Nokia Handy can't install the configuration. > > The converting binary data between xml2wbxml(libwbxml) and Kannel > (ota_comple) are different on: > > Kannel: in oma_ota_attributes[], the > { "VERSION", "INLINE", 0x45 }, > { "TYPE", "INLINE", 0x50 }, > { "TYPE", "NAPDEF", 0x55 }, > but libwbxml: > { "version", NULL, 0x00, 0x45 }, > { "type", NULL, 0x00, 0x50 }, > { "type", "NAPDEF", 0x00, 0x55 }, > > So in the wbxml of Kannel: > NAPDEF is inserted as string > > by libwbxml: > NAPDEF is encoded as 0x45. > > I don't know if this is the problem, that Nokia Symbian S60 3rd (E65) can't > config with the wbxml of Kannel. > > > PS: The OTA provisioning is still a job by SMS, not WAP. Only the content > of the SMS is a wap standart format. > > > > Have a nice trip!! > > Regards > > Pai > > On Thu, Feb 5, 2009 at 5:38 PM, Nikos Balkanas <[email protected]>wrote: > >> Hi, >> >> There are a couple of tools from kannel to help you test the wbxml >> compiler: >> >> wmlsc & wmlsdasm >> >> Check them out, they might help you. At present few people in kannel >> are interested in wap, most of them are in SMS. >> I am one of the few interested, but haven't been able to test it with a >> real phone yet. I am using winwap for tests, >> though, with no problems. >> >> After I return from my trip, I may have more time to look into it. >> >> BR, >> Nikos >> >> ----- Original Message ----- >> *From:* Pai Peng <[email protected]> >> *To:* [email protected] >> *Sent:* Thursday, February 05, 2009 5:48 PM >> *Subject:* Re: xml to wbxml compiler incorrect by 1.4.2!? >> >> hello Kannel Users&Developers, >> >> >> althrough in the change log for 1.4.1: >> >> Bugfixes: >> >> * ........... >> >> * >> >> * Fixed OTA compiler, within WBXML compilation. >> >> >> But with libwbxml, binary data converted by libwbxml is different than by >> kannel. >> >> The binary data converted by kannel can not be decoded back to XML by >> libwbxml: Error: wbxml2xml failed 'Invalid String Table Index'. >> >> The provisioning doesn't work on my Nokia Symbian 3rd, after SMS received. >> >> >> Please confirm me, if I am wrong or not. >> >> >> Regards >> >> Pai >> >> >> On Tue, Feb 3, 2009 at 8:15 PM, 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 >>> >> >> > ------------------------------------ > Nota: la información de este correo es confidencial y no debe > retransmitirse a personas no autorizadas. Si usted recibe información no > autorizada, por favor reportar a los telefonos 58-212-2008690 >
