OMA OTA Issues

[Stipe Tolj]

Hi Tunji,

please post such related questions about Kannel itself to the 'users' list. The 
'commercial' list if business related things only.

ceo at freshmail.mobi schrieb:
> 
> Greetings.
> You guys are doing great
> great work with Kannel.
> 
> I have an issue I'd like help on.
> 
> If I use lynx in a script to send OMA OTA Settings to new
> Sony-Ericsson or Nokia Devices, (with a TO-NAPDEF attribute), I get errors
> that the XML file contains undefined attributes, but they ARE defined in
> the ota_compiler.c file.
> 
> I had to modify the code to only
> recognise this type of OTA when compiling but that then excludes the older
> types.

more details here please... please use the CVS HEAD version instead of 1.4.1, as 
this is a 1.4.2RC and more accurate. If the "error" still remains with your test 
in a CVS HEAD build, then please a) send a bug report to http://bugs.kannel.org/ 
or b) notify the developers via the 'devel' mailing list... thanks.

> Secondly, can I define fields in a MySQL database and
> call these in the kannel .conf files to dynamically create OMA OTA
> settings for a phone.

no, we take the OMA OTA XML file via the smsbox interface. Kannel is here "only" 
the transport layer in this sense, and not doing the logics of the OTA 
provisioning application itself.

> Lastly, how about Windows Mobile? How can
> one provision those?

depends on what format they support. If they are OMA compliant then things 
should be fine, otherwise there are some "wild properietary" formats that are 
"not open" in terms of specs. Then you are running into hard times.

Stipe