Hi, I have already tested with Kannel version 1.5.0 but the results are the same. So I think I might be doing something wrong in setting up the oma settings. What I do is: - parse the XML file that I've posted previously and concatenate its lines in a single string (I've tried both with each line terminated by "/r/n" and without); - urlencode the resulting string using utf8-encoding; - generate and send to kannel such URL: "http://{$kannel_uri}/cgi-bin/sendota?username=spup&password=spup&from=XXXX&to=XXXX&smsc=pgsm&sec=userpin&pin=XXXX&type=oma-settings&text={$url_xml}";
As I said Kannel receives the command and provides the SMS to the indicated SMSC. The configuration message is received by all the phones that support the feature but then some models fail to parse it while other (to be precise SONY handsets) fail to decrypt it (incorrect PIN). Maybe somebody sees something wrong in the steps indicated above? Thanks in advance, Luca -----Original message----- From: Lam Nguyen Tuong <lam...@outlook.com> Sent: Tuesday 14th October 2014 17:33 To: Luca Valtulina | SpeakUp BV <l...@speakup.nl>; users@kannel.org Subject: RE: OMA provisioning: incorrect pin Well, it works properly. So please try kannel version 1.5 as i'm using. It also should work with stable version 1.4.4 but i've never tested yet. ::Lamnt -------------------------------- Subject: RE: OMA provisioning: incorrect pin From: l...@speakup.nl To: lam...@outlook.com; users@kannel.org Date: Tue, 14 Oct 2014 16:26:06 +0200 Hi, I've tried a few but the one that I'm interested in is: <?xml version="1.0"?> <!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" "http://www.wapforum.org/DTD/prov.dtd";> <wap-provisioningdoc version="1.1"> <characteristic type="NAPDEF"> <parm name="NAPID" value="INTERNET"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAME" value="Choozze Internet"/> <parm name="NAP-ADDRESS" value="basic.internet.spmb.data"/> <parm name="NAP-ADDRTYPE" value="APN"/> </characteristic> <characteristic type="BOOTSTRAP"> <parm name="CONTEXT-ALLOW" value="0"/> <parm name="PROVURL" value="http://www.choozze.nu/"/> </characteristic> </wap-provisioningdoc> Cheers, Luca -----Original message----- From: Lam Nguyen Tuong <lam...@outlook.com> Sent: Tuesday 14th October 2014 16:16 To: Luca Valtulina | SpeakUp BV <l...@speakup.nl>; users@kannel.org Subject: RE: OMA provisioning: incorrect pin Can you share your OMA content that you are processing? I'll try on my system. Thank you. ::Lamnt -------------------------------- Subject: OMA provisioning: incorrect pin From: l...@speakup.nl To: users@kannel.org Date: Tue, 14 Oct 2014 15:17:15 +0200 Dear list, when trying to use Kannel's OMA provisioning with userpin as security, the phone receives the configuration settings but whatever pin is then inserted results in an "Incorrect PIN" message being displayed. This happens with different models/brands of modern and old mobile handsets. I have configured and built Kannel with openssl support and prior to that configured and built openssl with rca5 and multithread support. I have tried different stable versions of Kannel (inspired by the discovery that since version 1.4.1 Kannel was using ISO-8859 as default charset before moving to UTF-8 afterwards) but all gave the same result. Furthermore the binary messages are correctly received by the phones so I guess my configurations are correct and I can see as the possible culprit the HMAC calculation in file ota_prov.c (which is used only for the OMA case). But if needed I can provide the used configurations. Since I've been already looking back and forth in the lists and in general on the web and I've already tried various approaches my question here is: does Kannel supports this feature correctly? If yes which version does? Has anyone of you succeed in using OMA provisioning with userpin security? I thank you all in advance. Best regards, Luca
