Hi, Paul. I send OMA bootstrap configuration aside from kannel. I didn't test samsung, but I have different OMA for nokia, siemens and motorola.
First of all, do you use authentication (pin or imsi)? As I remember it is mandatory for some manufacters. Second, try to generate wbxml without string table. Some model doesn't handle it.
Here is working example for siemens OMA WAP configuration.
<?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="NAPDEF">
<parm name="NAPID" value="x">
</parm>
<parm name="NAME" value="x">
</parm>
<parm name="BEARER" value="GSM-GPRS">
</parm>
<parm name="NAP-ADDRESS" value="internet">
</parm>
<parm name="NAP-ADDRTYPE" value="APN">
</parm>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP">
</parm>
<parm name="AUTHNAME" value="">
</parm>
<parm name="AUTHSECRET" value="">
</parm>
</characteristic>
</characteristic>
<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="xxx.xxx.xxx.xxx">
</parm>
<parm name="NAME" value="x">
</parm>
<parm name="STARTPAGE" value="http://www.lmt.lv/wap/";>
</parm>
<characteristic type="PXPHYSICAL">
<parm name="PXADDR" value="xxx.xxx.xxx.xxx">
</parm>
<parm name="PXADDRTYPE" value="IPV4">
</parm>
<parm name="TO-NAPID" value="x">
</parm>
<characteristic type="PORT">
<parm name="PORTNBR" value="9201">
</parm>
<parm name="SERVICE" value="CO-WSP">
</parm>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w2">
</parm>
<parm name="NAME" value="x">
</parm>
<parm name="TO-PROXY" value="xxx.xxx.xxx.xxx">
</parm>
<characteristic type="RESOURCE">
<parm name="URI" value="http://www.lmt.lv/wap/";>
</parm>
<parm name="NAME" value="x">
</parm>
<parm name="STARTPAGE" value="http://www.lmt.lv/wap/";>
</parm>
</characteristic>
</characteristic>
</wap-provisioningdoc>
P.S. Siemens software version 9 supports only USERPIN auth and wap&mms must be configurated separatly.
Paul P Komkoff Jr wrote:
Hello developers!
Have you (anyone :)) made any progress in sending browser settings to OMA-compliant devices?
I was trying to do so here by 2 hours. Maybe I've picked wrong phone. I just ensured that all works with nokia phone and nokia OTA, then replaced all from WSP (including WSP header) to wbxml.
No luck.
I see three possible problems: 1. I am compiling wrong xml, or miscompiling right xml. I am using libwbxml (http://libwbxml.aymerick.com) to compile. Nokia OTA settings xml compiles by it just fine. 2. I am including wrong WSP header. I am trying to pass in minimalistic WSP header, e.g. '\x01\x06\x01\xb6'. second 01 here means length, and b6 means well-known type for application/vnd.wap.connectivity-wbxml. 3. I am picked a wrong phone to use in my experiments. I was using some flipflop samsung, borrowed from my colleague (because it was too late and thus I had no access to Secret Stash(tm))
Comments?
Maybe anyone have WORKING code, working xml, working headers, etc?
-- Vjacheslav Chekushin mailto:[EMAIL PROTECTED] Latvian Mobile Phone Company http://www.lmt.lv
