RE: OMA provisioning: incorrect pin
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=spuppassword=spupfrom=to=smsc=pgsmsec=userpinpin=type=oma-settingstext={$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
RE: OMA provisioning: incorrect pin
Hi list,
I've managed to solve the issue which, as it's always the case, was as easier
as they come.
max-messages in sendsms-user group needed to be set. I was of the idea that its
default value (when not set) was 10 but by checking the userguide I was clearly
wrong. Therefore 1 sms was not enough to push the entire binary setting to the
phone.
Thanks to Lamnt for his help,
Luca
-Original message-
From: Luca Valtulina | SpeakUp BV l...@speakup.nl
Sent: Wednesday 15th October 2014 13:06
To: Lam Nguyen Tuong lam...@outlook.com; users@kannel.org
Subject: RE: OMA provisioning: incorrect pin
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=spuppassword=spupfrom=to=smsc=pgsmsec=userpinpin=type=oma-settingstext={$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
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 OMA provisioning: incorrect pin 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
RE: OMA provisioning: incorrect pin
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
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 RE: OMA provisioning: incorrect pin 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//ENhttp://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
Re: OMA Provisioning
Your XML does not meet Nokia 6085's requirement. are you suing concatenated sms ? On Sun, Jul 6, 2008 at 11:44 AM, zillur rahman [EMAIL PROTECTED] wrote: Dear Users, I am trying to send OMA provisioning Messages to configure browser nokia 6085 http://10.1.4.25:13015/cgi-bin/sendota?type=oma-settingspin=1234sec=userpinusername=testpassword=testto=text=urlencoded(XML document) But in my phone i get error messages Invalid settings discarded I get the following data in smsbox log file 2008-07-06 12:35:33 [24659] [2] DEBUG: HTTP: Creating HTTPClient for `10.1.4.25'. 2008-07-06 12:35:33 [24659] [2] DEBUG: HTTP: Created HTTPClient area 0x950a810. 2008-07-06 12:35:33 [24659] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendota from 10.1.4.25 2008-07-06 12:35:33 [24659] [3] INFO: sendsms used by test 2008-07-06 12:35:33 [24659] [3] DEBUG: OTA service with XML document 2008-07-06 12:35:33 [24659] [3] WARNING: OTA compiler: Unknown attribute 'version' in OTA source, with value '1.0'. 2008-07-06 12:35:33 [24659] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'BOOTSTRAP'. 2008-07-06 12:35:33 [24659] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'APPLICATION'. 2008-07-06 12:35:33 [24659] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'PXLOGICAL'. 2008-07-06 12:35:33 [24659] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'PXPHYSICAL'. 2008-07-06 12:35:33 [24659] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'PORT'. 2008-07-06 12:35:33 [24659] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'NAPDEF'. 2008-07-06 12:35:33 [24659] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'NAPAUTHINFO'. 2008-07-06 12:35:33 [24659] [3] DEBUG: Octet string at 0x950b930: 2008-07-06 12:35:33 [24659] [3] DEBUG: len: 424 2008-07-06 12:35:33 [24659] [3] DEBUG: size: 1024 2008-07-06 12:35:33 [24659] [3] DEBUG: immutable: 0 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 01 06 2f 1f 2d b6 91 81 92 31 41 35 33 39 36 36 ../.-1A53966 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 35 41 44 33 45 32 32 36 32 44 42 41 44 36 34 30 5AD3E2262DBAD640 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 43 43 39 43 34 36 39 30 42 33 41 38 44 37 41 42 CC9C4690B3A8D7AB 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 31 00 01 01 6a 00 c5 01 c6 01 87 15 11 03 47 6e 1...j.Gn 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 75 00 01 01 c6 01 87 10 03 41 50 50 49 44 00 11 uAPPID.. 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 03 77 32 00 01 87 10 03 54 4f 2d 50 52 4f 58 59 .w2.TO-PROXY 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 00 11 03 50 52 4f 58 59 31 00 01 87 15 11 03 54 ...PROXY1..T 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 45 4c 47 50 52 53 00 01 01 c6 01 87 10 03 50 52 ELGPRSPR 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 4f 58 59 2d 49 44 00 11 03 50 52 4f 58 59 31 00 OXY-ID...PROXY1. 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 01 87 15 11 03 57 41 50 2d 4d 4d 53 00 01 c6 01 .WAP-MMS 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 87 10 03 50 48 59 53 49 43 41 4c 2d 50 52 4f 58 ...PHYSICAL-PROX 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 59 2d 49 44 00 11 03 50 52 4f 58 59 31 00 01 87 Y-ID...PROXY1... 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 10 03 50 58 41 44 44 52 00 11 03 31 39 32 2e 31 ..PXADDR...192.1 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 36 38 2e 31 34 35 2e 31 30 31 00 01 87 10 03 50 68.145.101.P 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 58 41 44 44 52 54 59 50 45 00 77 01 87 10 03 54 XADDRTYPE.wT 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 4f 2d 4e 41 50 49 44 00 11 03 57 41 50 2d 4d 4d O-NAPID...WAP-MM 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 53 00 01 01 c6 01 87 10 03 50 4f 52 54 4e 50 52 SPORTNPR 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 00 61 01 01 01 c6 01 87 10 03 4e 41 50 49 44 00 .aNAPID. 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 11 03 57 41 50 2d 4d 4d 53 00 01 87 12 11 03 47 ..WAP-MMS..G 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 53 4d 2d 47 50 52 53 00 01 87 15 11 03 54 45 53 SM-GPRS..TES 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 54 41 50 4e 00 01 87 10 03 4e 41 50 2d 41 44 44 TAPN.NAP-ADD 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 52 45 53 53 00 11 03 55 4e 4c 00 01 87 10 03 4e RESS...UNL.N 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 41 50 2d 41 44 44 52 54 59 50 45 00 11 03 41 50 AP-ADDRTYPE...AP 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 4e 00 01 c6 01 87 10 03 41 55 54 48 54 59 50 45 N...AUTHTYPE 2008-07-06 12:35:33 [24659] [3] DEBUG: data: 00 70 01 87 10 03 41 55 54 48 4e 41 4d 45 00 11
