Send OMA settings

Send OMA settings SearchSearch
Author Message
Ivan Markoski
Posted on Wednesday, July 23, 2003 - 05:51 pm:   

I am unable to save the OMA settings on my Nokia 6610 (The message on the phone appears "Unable to save configuration setting")

Any idea why? I have read the OMA specs, and they talk about privileged and non-privileged contexts, protected by password (IMSI for the privileged and normal PIN for others). I could not see, on the OMA settings page of the NowSMS GW, any place to put any kind of PIN.
Bryce Norwood - NowSMS Support
Posted on Wednesday, July 23, 2003 - 06:18 pm:   

Hi Ivan,

I haven't had a chance to test on the 6610 yet.

We're still planning to implement the PIN support before the final release. I expect that we'll have this implemented around the middle of next week.

In the meantime, since you have the OMA Provisioning specs (Nokia also has a document that explains how they interpret them) ... you might want to try creating your own settings document and submitting it via the "Send XML Settings" option. I'd be curious if you can use an example settings document from the specs ... to determine whether the problem is related to the document that we auto-generate, or if it is that a PIN is required for all settings documents.

-bn
Ivan
Posted on Thursday, July 24, 2003 - 10:00 am:   

Bryce,

still the same problem. I sent the example from the Nokia document, resulting in the same error. Let me know the results of your testing with Nokia 6220 (or other OMA bootstrap compliant phone).

Hopefully it will get better in the final release.

Regards,

Ivan
Bryce Norwood - NowSMS Support
Posted on Thursday, July 24, 2003 - 01:48 pm:   

Ivan,

I'll post a note when we get a version together with the PIN support. I'll wager the Nokia phones require it.

-bn
Bryce Norwood - NowSMS Support
Posted on Monday, July 28, 2003 - 06:44 pm:   

Update: The "beta 2" release supports both USERPIN (user has to enter PIN to receive settings) and NETWPIN (bootstrap settings, recipient IMSI is the PIN) for sending OMA settings.
ManMan
Posted on Tuesday, August 26, 2003 - 09:13 am:   

Ivan,

With the support of USERPIN and NETWPIN, can you send the OMA settings to your handset (Nokia 6610) successfully??

For my case, i tried to send the OMA settings to Nokia 7650, 7250 and 6108 using 'Send XML Settings Document' web interface, but still failed to send to those handsets. The handsets didn't show any response and they seemed to discard the message. I guessed they may not know the format of OMA settings.

Does anyone know which handsets (already in the market currently) support OMA settings?? Is only Nokia 6220??

Thanks.
Anonymous
Posted on Wednesday, August 27, 2003 - 08:32 am:   

I 'm unable send the OMA Seting on the Phone Nokia 6220.I 'm send it same send sms message. but it is not appear. what did sent it with ?
Can any one tell me?

Thanks,
Bryce Norwood - NowSMS Support
Posted on Thursday, September 04, 2003 - 02:56 pm:   

The 7650 and 7250 definitely don't support the OMA settings. They still use the old style provisioning settings.

Try using the "Send XML Settings" option and send a settings document directly (the gateway will encode it into the appropriate WBXML encoding). Here is an example from Nokia documentation for the Nokia 5100. I would suggest trying it with a USERPIN specified:

<?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.0">
<characteristic type="BOOTSTRAP">
<parm name="NAME" value="Gnu"/>
</characteristic>
<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="timon.dk"/>
<parm name="NAME" value="Timon Proxy"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="8080"/>
</characteristic>
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="Timon_Proxy"/>
<parm name="PXADDR" value="timon.proxy.dk"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="timon_GPRS"/>
</characteristic>
</characteristic>
<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="gnu.dk"/>
<parm name="NAME" value="gnu Proxy"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="8080"/>
</characteristic>
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="gnu Proxy"/>
<parm name="PXADDR" value="gnu.proxy.dk"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="gnu_GPRS"/>
<parm name="TO-NAPID" value="gnu_CSD"/>
</characteristic>
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="Bison Proxy"/>
<parm name="PXADDR" value="bison.proxy.dk"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="gnu_GPRS"/>
<parm name="TO-NAPID" value="gnu_CSD"/>
</characteristic>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAPID" value="gnu_GPRS"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAME" value="gnu GPRS"/>
<parm name="NAP-ADDRESS" value="internet"/>
<parm name="NAP-ADDRTYPE" value="APN"/>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="Zimba"/>
<parm name="AUTHSECRET" value="Scar"/>
</characteristic>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAPID" value="gnu_CSD"/>
<parm name="BEARER" value="GSM-CSD"/>
<parm name="NAME" value="gnu CSD"/>
<parm name="NAP-ADDRESS" value="+5555555555"/>
<parm name="NAP-ADDRTYPE" value="E164"/>
<parm name="CALLTYPE" value="ANALOG-MODEM"/>
<parm name="LINKSPEED" value="9600"/>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="Pumba"/>
<parm name="AUTHSECRET" value="Sazu"/>
</characteristic>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAPID" value="timon_GPRS"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAME" value="timon GPRS"/>
<parm name="NAP-ADDRESS" value="internet"/>
<parm name="NAP-ADDRTYPE" value="APN"/>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="Rafiki"/>
<parm name="AUTHSECRET" value="Kiara"/>
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w2"/>
<parm name="TO-PROXY" value="gnu.dk" />
<parm name="NAME" value="Browser"/>
<characteristic type="RESOURCE">
<parm name="URI" value="http://wap.gnu.dk"/>
<parm name="STARTPAGE"/>
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w4"/>
<parm name="TO-PROXY" value="timon.dk" />
<parm name="ADDR" value="http://wap.timon.dk" />
</characteristic>
</wap-provisioningdoc>
Anonymous
Posted on Monday, September 08, 2003 - 07:05 am:   

I sent it using the 'Send XML Setting' follow by example .
sned from server to phone 6220(I encode Hexcode before sent ). but phone do not appear.
Why! Can any one tell me?


<?xml>
<!doctype>
<wap-provisioningdoc>
<characteristic>
<parm>
</characteristic>
<characteristic>
<parm>
<parm>
<characteristic>
<parm>
</characteristic>
<characteristic>
<parm>
<parm>
<parm>
<parm>
</characteristic>
</characteristic>
<characteristic>
<parm>
<parm>
<characteristic>
<parm>
</characteristic>
<characteristic>
<parm>
<parm>
<parm>
<parm>
<parm>
</characteristic>
<characteristic>
<parm>
<parm>
<parm>
<parm>
<parm>
</characteristic>
</characteristic>
<characteristic>
<parm>
<parm>
<parm>
<parm>
<parm>
<characteristic>
<parm>
<parm>
<parm>
</characteristic>
</characteristic>
<characteristic>
<parm>
<parm>
<parm>
<parm>
<parm>
<parm>
<parm>
<characteristic>
<parm>
<parm>
<parm>
</characteristic>
</characteristic>
<characteristic>
<parm>
<parm>
<parm>
<parm>
<parm>
<characteristic>
<parm>
<parm>
<parm>
</characteristic>
</characteristic>
<characteristic>
<parm>
<parm>
<parm>
<characteristic>
<parm>
<parm>
</characteristic>
</characteristic>
<characteristic>
<parm>
<parm>
<parm>
</characteristic>
</wap-provisioningdoc>
Anonymous
Posted on Wednesday, September 10, 2003 - 10:58 am:   

Hello
I am able to send the setting by OMA to nokia 6220.
If fact it is the sample at the end of doc PROV-CONT.
But, when trying to save the config at the phone, it ask for a setting pin, I have tried 1234, and many others (my SIM PIN), with no success.

Any one knows the right pin? or any other sample to send.

Thanks
ManMan
Posted on Wednesday, September 10, 2003 - 11:38 am:   

I have tried to use the 'Send XML Settings' option and send Nokia example to handset Nokia 6220.

By choosing User PIN and use '1234' as OTA PIN, the handset can receive and save the settings. Before saving the settings, the handset prompts to enter Setting's PIN. Then I entered '1234' and the settings can be saved into the handset successfully.

But when choosing Network PIN and use the SIM Card's IMSI (specified by the documents of Nokia) as the OTA PIN, the handset can receive the settings but still prompts to enter Setting's PIN. So, I tried to enter the IMSI of the SIM card. But the length of the field is limited, I couldn't enter the whole IMSI to the handset, so i only entered the partial IMSI. The handset returned me 'Verification failed, try again'. After 3 times of trial failure, the setting was discarded.

So, how can we save setting if it is sent by NETWORK PIN method?? Or I have used an incorrect PIN (i.e. the IMSI of SIM card) for the NETWORK PIN?? Please advise.

Thank you.
Anonymous
Posted on Wednesday, September 10, 2003 - 01:52 pm:   

Hello,
sorry, what is the 'Send XML Settings' option ?

Exactly which nokia example are you sending?
- the one at the end of doc prov-cont,
or
- the one in pdf oma client provisioning for series 40

- Can you show me the header you are using?
I am using the following:

0106
2f
1f2d
b6
9181
92
30424233424235353146
30413933333539454332
39453643454143313434
30453441363137343839
00

And so I receive the setting in the phone, but not able to save it, wron pin setting?

any idea?

thanks

Bryce Norwood - NowSMS Support
Posted on Wednesday, September 10, 2003 - 07:24 pm:   

Hi,

A couple of general comments. If you post any XML documents here, make sure to uncheck "Enable HTML code in message" when you post, otherwise our bulletin board software will mangle the message, like in one of the examples above.

Also, to answer another question that is asking what PIN you should use. When using a "user PIN" ... you specify a PIN for the settings when you send them out. This PIN is any PIN that you want to use, it does not have an existing relationship to any PIN that already exists on the phone. In order to receive and save the settings, the user on the phone needs to enter this same PIN.

I'll address ManMan's question in a separate posting.

-bn
Bryce Norwood - NowSMS Support
Posted on Wednesday, September 10, 2003 - 07:35 pm:   

ManMan,

There is a bug in our HTML templates in the current beta release (beta 2). The HTML forms related to OMA settings do not properly set the HTTP variable that tells the gateway to use the "network PIN" method. So even if you select "network PIN", the gateway sends the message out with "user PIN" specified.

You can download the updated HTML templates at http://www.nowsms.com/download/omasettings.zip. Use the contents of this ZIP file to replace the associated files in the HTML directory of the gateway installation.

-bn
Bryce Norwood - NowSMS Support
Posted on Wednesday, September 10, 2003 - 07:41 pm:   

To answer the following question on this thread:


quote:

sorry, what is the 'Send XML Settings' option ?

Exactly which nokia example are you sending?
- the one at the end of doc prov-cont,
or
- the one in pdf oma client provisioning for series 40




The "Send XML Settings" option is multipurpose.

If it finds the XML tag <CHARACTERISTIC-LIST>, then it assumes the old style Nokia/Ericsson WAP OTA settings.

If it finds the XML tag <SyncSettings>, then it assumes SyncML settings according to the Nokia/Ericsson WAP OTA settings.

If it finds the XML tag <wap-provisioningdoc>, then it assumes that it is OMA Provisioning Content.

The header is going to vary based upon the type of content.

In your example, it looks like you are using OMA provisioning, specifying a USERPIN. An incorrect PIN setting would be one reason that you might not be able to save the content (another would be malformed content).

-bn
ManMan
Posted on Thursday, September 11, 2003 - 02:59 am:   

For the question
--------------------------------------------------
Exactly which nokia example are you sending?
- the one at the end of doc prov-cont,
or
- the one in pdf oma client provisioning for series 40
--------------------------------------------------

The example that I used is the XML example 'Browser and MMS Example' in the document of 'OMA Client Provisioning for Series 40'.
Anonymous
Posted on Thursday, September 11, 2003 - 07:39 am:   

Hello
I would like to know which is the header I may use in order
to make oma provisioning without using the SEC and MAC.

So far I have tried with the following but the phone discard it,
can anyone help me.

01
06
03
1F
01
B6


Thanks

ManMan
Posted on Thursday, September 11, 2003 - 07:42 am:   

Bryce,

I have followed your suggestion to download the updated HTML templates and replace the associated files in the HTML directory of the gateway installation.

By choosing 'Network PIN' as 'OTA PIN Type' and using IMSI of the SIM card into 'OTA PIN' field,
the handset could receive the settings but immediately showed the message 'Verification failed, settings was discarded' and then disappeared.

Then, I tried to use another SIM card to receive the settings by choosing 'Network PIN', same failure message was resulted.

I have tried to send the SAME settings using 'User PIN' method to the SAME SIM cards, the settings can be received and saved successfully. So, did i use an incorrect PIN (i.e. IMSI of SIM card) for the 'Network PIN'?? Any other PIN choices i can use for the testing of 'Network PIN' method??

Thanks.


Bryce Norwood - NowSMS Support
Posted on Thursday, September 11, 2003 - 09:35 pm:   


quote:


I would like to know which is the header I may use in order
to make oma provisioning without using the SEC and MAC.




Good luck. Many phones require it to be present.

Bryce Norwood - NowSMS Support
Posted on Thursday, September 11, 2003 - 09:54 pm:   

ManMan,

You're right. I did some checking, and we're not encoding the MAC correctly when the IMSI is used.

Let me do some more checking on this.

-bn
Anonymous
Posted on Friday, September 12, 2003 - 09:54 am:   

Hello,
thanks Bryce for the answer.

So the best is always to send the settings to OMA phones using at least the USERPIN method (SEC=1).

Do you know which phones required this?

Thanks

Anonymous
Posted on Friday, September 12, 2003 - 01:09 pm:   

Hello,
I would like to have a simple xml OMA file to config GPRS connection; and another file with the settings for the GSM connection.

With only the necesary data for the connection.

For example for GPRS connection to MoviStar SPAIN
we have:
Start page http://wap.movistar.com
sesion mode: permanent
security: no
type bearer: GPRS
Connection GPRS: always in line
access point: wap.movistar.com
IP address: 192.168.080.021
auth type: normal
start session type: automatic
user and pass: WAPTM



Thanks



Bryce Norwood - NowSMS Support
Posted on Friday, September 12, 2003 - 03:28 pm:   

ManMan,

Another update. Download http://www.nowsms.com/download/imsifix.zip which contains two updated binaries to fix the MAC encoding problem when the network pin method is used with the IMSI as the PIN.

-bn
Bryce Norwood - NowSMS Support
Posted on Friday, September 12, 2003 - 03:35 pm:   


quote:

So the best is always to send the settings to OMA phones using at least the USERPIN method (SEC=1).

Do you know which phones required this?




I know the first releases of the SonyEricsson P800 required SEC and MAC parameters. I believe they removed that requirement with later releases of the firmware.

I'm not sure about the Nokia phones ... as there are a lot of different firmware versions floating about. The Nokia docs seem to suggest that there is always going to be a PIN associated with the settings, either a user pin method or a network pin method.

Personally, I think PINs are going to confuse end-users ... but I can understand that there were concerns with previous approaches where users would accept settings when they did not know where they came from.

-bn
Bryce Norwood - NowSMS Support
Posted on Friday, September 12, 2003 - 03:52 pm:   


quote:

I would like to have a simple xml OMA file to config GPRS connection; and another file with the settings for the GSM connection.

With only the necesary data for the connection.

For example for GPRS connection to MoviStar SPAIN
we have:




It will be a little bit easier when we put out the next update, where we've fixed some problems with the settings that are generated by our forms.

I would use the following:

<?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="BOOTSTRAP">
<parm name="NAME" value="MoviStar SPAIN"/>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAME" value="MoviStar SPAIN"/>
<parm name="NAPID" value="MoviStar_SPAIN"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAP-ADDRESS" value="wap.movistar.com"/>
<parm name="NAP-ADDRTYPE" value="APN"/>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="WAPTM"/>
<parm name="AUTHSECRET" value="WAPTM"/>
</characteristic>
</characteristic>
<characteristic type="PXLOGICAL">
<parm name="NAME" value="MoviStar SPAIN"/>
<parm name="PROXY-ID" value="192.168.80.21"/>
<parm name="STARTPAGE" value="http://wap.movistar.com"/>
<characteristic type="PXPHYSICAL">
<parm name="PXADDR" value="192.168.80.21"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="MoviStar_SPAIN"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="9201"/>
<parm name="SERVICE" value="CO-WSP"/>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w2"/>
<parm name="TO-PROXY" value="192.168.80.21"/>
<parm name="NAME" value="Browser"/>
<characteristic type="RESOURCE">
<parm name="URI" value="http://wap.movistar.com"/>
<parm name="STARTPAGE"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
ManMan
Posted on Monday, September 15, 2003 - 08:54 am:   

Bryce,

I am sorry that the OMA settings still could not be saved into nokia handset 6220 even I have updated the binary files from the download link http://www.nowsms.com/download/imsifix.zip.

But this time the response of the handset was a bit different. It didn't prompt out to request user to enter PIN and directly returned the error message "Failed to save received connection settings".

I think the handset could recognise the security method used by the OMA settings is NETWPIN this time but sill failed to complete the verification process.

Here is the example that I tried:
IMSI of my SIM card: 454163001940196

XML content:the "Browser and MMS Example" from the documentation of Nokia "OMA Client Provisioning for Series 40"

MAC code (collected from the log files)
44324137374338374644393339413831394641354537363930443344334239353045384237413942

Would you please kindly help to verify the correctness of this MAC code? Thanks.
Bryce Norwood - NowSMS Support
Posted on Monday, September 15, 2003 - 02:57 pm:   

ManMan,

I think we're making progress.

Previously, you said that the following occurred:


quote:

the handset could receive the settings but immediately showed the message 'Verification failed, settings was discarded' and then disappeared




Now, you're seeing:


quote:

...directly returned the error message "Failed to save received connection settings"




This suggests that the verification code (the HMAC) is ok. We'd need to see the complete provisioning message to re-calculate the HMAC, but since previously the phone was complaining about a failed verification, and it is not any more, I think we're past that problem.

You might want to enter in an invalid IMSI, and see if that results in the other message being displayed.

In the Nokia doc that you mention, it says that only one document can be received using the IMSI. Maybe that is the situation here?

Section 3.9 of the document has a procedure for deleting a settings set. Have you tried deleting existing settings before sending this set?

-bn
Anonymous
Posted on Tuesday, September 16, 2003 - 07:32 am:   

Thanks Bryce,
for the movistar oma config xml file.
But I am to able to save this file.
The example in nokia doc I am able to save with success.

Can you please tell me what can be wrong.
Or please give another example of GPRS configuration, and MMS configuraction.

Thanks



Anonymous
Posted on Tuesday, September 16, 2003 - 07:33 am:   

Hello
in the xml,
in the characteristic application,
what is w2 and w4 ?

thanks
Anonymous
Posted on Tuesday, September 16, 2003 - 02:24 pm:   

Hello,
finally I repair the xml to config setting for MoviStar.

Now the settings are received and saved OK.

But when I try to navegate using the phone,
it start saying: creating GPRS conexion for 5 seconds. Then it says: point of access not valid.

Please, any idea of what can be wrong in this configuration?

Thanks

<?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="BOOTSTRAP">
<parm name="NAME" value="MoviStar SPAIN"/>
</characteristic>

<characteristic type="NAPDEF">
<parm name="NAPID" value="MoviStarGPRS"/>
<parm name="NAME" value="MoviStar SPAIN"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAP-ADDRESS" value="wap.movistar.com"/>
<parm name="NAP-ADDRTYPE" value="APN"/>

<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="WAPTM"/>
<parm name="AUTHSECRET" value="WAPTM"/>
</characteristic>
</characteristic>


<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="moviproxy"/>
<parm name="NAME" value="MoviStarSPAIN"/>


<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="MoviStarSPAIN"/>
<parm name="PXADDR" value="192.168.80.21"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="MoviStarGPRS"/>
</characteristic>
</characteristic>


<characteristic type="APPLICATION">
<parm name="APPID" value="w2"/>
<parm name="TO-PROXY" value="moviproxy"/>
<parm name="NAME" value="Browser"/>
<characteristic type="RESOURCE">
<parm name="URI" value="http://www.dgt.es/index.wml"/>
<parm name="STARTPAGE"/>
</characteristic>
</characteristic>

</wap-provisioningdoc>

ManMan
Posted on Wednesday, September 17, 2003 - 06:20 am:   

Thanks Bryce,

I followed your instructions and now the OMA-settings using NETWORK PIN can be saved by the handset. Thanks a lot.

FYI, here is my test result:
1. If delete all settings, the OMA-setting can be saved directly.
2. If I enter a wrong IMSI for NETWORK PIN, the handset shows the message 'Verification failed, settings was discarded', instead of 'cannot save the settings.'

so, the above results prove your idea is correct. :-)
Anonymous
Posted on Wednesday, September 17, 2003 - 12:31 pm:   

Hello everybody,
I receive with success GPRS settings via OMa in a nokia 6220.

But when trying to access a wap page using gprs,
the phone says: creating gprs connection for 5 seconds and finally ends with errors.

The question is;
when receiving this settings, does it changes something in the MODEM GPRS Settings in the menu: Settings -Connectivity- GPRS MODEM ?

regards
Bryce Norwood - NowSMS Support
Posted on Thursday, September 18, 2003 - 03:15 pm:   


quote:

in the xml,
in the characteristic application,
what is w2 and w4 ?




W2 refers to settings specific to the WAP browser application. Basically, you're telling it which data connection to use ("TO-PROXY" value), and what to configure as the start page for the connection.

W4 refers to settings specific to the MMS client. Like with the WAP browser settings, "TO-PROXY" specifies which data connection to use. The "ADDR" value specifies the MMS Message Server (MMSC) URL.
Bryce Norwood - NowSMS Support
Posted on Thursday, September 18, 2003 - 03:42 pm:   


quote:

finally I repair the xml to config setting for MoviStar.




Before we get to the connectivity problems, I'm wondering what the significant part was to the changes that you applied in order to get the settings accepted by the phone.

I really need to get my hands on a Nokia 6220 phone myself.

I want to make sure that I understand which of the changes that you applied was significant. As I review the changes, here are the differences that I see between the settings that I suggested, and the settings that you finally got the phone to accept:

NAPDEF characteristic:
"NAPID" value changed from "MoviStar_SPAIN" to "MoviStarGPRS".

PXLOGICAL characteristic:
"NAME" value changed from "MoviStar SPAIN" to "MoviStarSPAIN" (space removed)
"PROXY-ID" changed from "192.168.80.21" to "moviproxy".

PXPHYSICAL characteristic:
"PHYSICAL-PROXY-ID" value inserted.
"TO-NAPID" value changed to match "NAPID" change in NAPDEF characteristic.
"PORT" characteristic section removed.

APPLICATION CHARACTERISTIC:
"TO-PROXY" changed to match "PROXY-ID" value change in PXLOGICAL section.
"URI" value changed.


I'm trying to determine which of these changes made a difference.

I don't think the NAPID (and TO-NAPID) or NAME changes would be of signifcance.

Changing the "PROXY-ID" also shouldn't be of significance. I used the IP address of the proxy as the ID because the OMA specs say that the value must be globally unique and should be a fully qualified internet domain name or a globally unique IP address.

Changing the "URI" for the start page also should not be of any significance.

That leaves us with the following changes that could be of potential significance:

Insertion of the "PHYSICAL-PROXY-ID" parameter. This could be of significance. I should have included this setting in my example.

Removal of the "PORT" characteristic section. This could also be of significance. The 6220 might assume port 9201 (connection oriented WSP) if this section is not specified. But other phones might make other assumptions. I would be curious whether you have to remove this section in order to get your settings to be accepted.

If you can spare the time to work through the changes that you made individually to determine which change was the magic change that made the settings be accepted by the phone, I would appreciate it.

My best guess is that the problem with the settings that I gave as an example is that they did not include the PHYSICAL-PROXY-ID value, and they should have.

-bn
Bryce Norwood - NowSMS Support
Posted on Thursday, September 18, 2003 - 03:57 pm:   


quote:

I receive with success GPRS settings via OMa in a nokia 6220.

But when trying to access a wap page using gprs,
the phone says: creating gprs connection for 5 seconds and finally ends with errors.

The question is;
when receiving this settings, does it changes something in the MODEM GPRS Settings in the menu: Settings -Connectivity- GPRS MODEM ?




If the setting is subsequently activated,(Services->Settings->Active Service Settings), then I would expect it to.

As I don't have a 6220 to test with directly, it would be helpful if you could download the "OMA Client Provisioning for Series 40" document from the Nokia web site (http://www.forum.nokia.com ... if you don't already have a login there, you'll have to register). Of course, now that I suggest this, I go to that site, and I can't find this document in any lists, but I did find it with a search. After you login to the site, go to the "Documents" section, and then do a search on OMA settings to find this particular document.

Section 3.4 and 3.5 show the settings that you should expect to see changed, with some similarity to the actual menus on the phone.

I'm wondering if the GPRS part is the problem, or if the problem is connecting to the proxy (because the PORT section was removed as I explain in another message in this thread). In any event, you should be able to see what the GPRS APN is that is specified, and verify that the user name and password are correct.

Actually, I just did a web search, and I think the APN that was provided above is incorrect. According to the following link it should be "wap.movistar.es", and NOT "wap.movistar.com". So the "NAP-ADDRESS" value should be changed accordingly.

http://www.gobcantabria.es/portal/page?_pageid=33,113792&_dad=interportal&_schem a=INTERPORTAL

-bn
Anonymous
Posted on Monday, September 22, 2003 - 10:31 am:   

Hello Bryce,
yes, it was the PHYSICAL-PROXY-ID param,
which it is compulsory.

Good news!
The settings works, but strange enough, it does not work in Spain, but yes in a different european state.

The fact is that, the mobile operator have to support TCP/IP back bone, as this phone 6220 is an tcp/ip phone.

Not quite sure about this.
If anyone have an explanation...

bye

Anonymous
Posted on Monday, September 22, 2003 - 02:34 pm:   

Hello
one question.
I see in doc OMa client provisioning for series 40,
in point 3.4.2, that user may received an oma settings and save it directly without being asked for a pin.
Security is based on the IMSI.
The question is, to obtain this result, which value of SEC shall I use? 1?

Bryce Norwood - NowSMS Support
Posted on Monday, September 22, 2003 - 08:17 pm:   


quote:

The question is, to obtain this result, which value of SEC shall I use? 1?




Please refer to the OMA Provisioning specifications. The binary encoding for NETWPIN is the appropriate value.
Bryce Norwood - NowSMS Support
Posted on Monday, September 22, 2003 - 08:26 pm:   


quote:

Good news!
The settings works, but strange enough, it does not work in Spain, but yes in a different european state.

The fact is that, the mobile operator have to support TCP/IP back bone, as this phone 6220 is an tcp/ip phone.

Not quite sure about this.
If anyone have an explanation...




Well, I personally find it a little surprising that Nokia would introduce a phone that didn't have the option of either WAP or HTTP, and forced the use of HTTP ... because a lot of operator networks are not ready for HTTP (and based upon performance that I see on GPRS with my operator, I think WAP works better, but that's another story).

Basically, when you connect into the GPRS APN, you usually will only get a private IP address assignment.

Some operators have multiple GPRS APNs for different types of access. For example, the standard WAP access APN only allows connections to the operator WAP gateway.

And they provide a different APN for internet access (normally to be used with a PDA or PC card), where the private IP address gets routed publicly through a NAT, so that you have the ability to connect anywhere on the internet (but not receive an externally initiated connection).

So, in your case, you either need an APN that has open internet access ... or you need the address of an HTTP proxy in the mobile operator network that is accessible when using the WAP APN (because even though the phone uses HTTP instead of WAP, it's still generally going to use a proxy, just using a different protocol).

Not sure if I explained this well or not, but hopefully it makes sense.
Anonymous
Posted on Tuesday, September 23, 2003 - 08:28 am:   

Thanks very much.
That is what I thought.

Now, i want to use NETWPIN method.

In ProvBoot says that:
Semi-octets have to be used.
If the IMSI
consists of an even number of digits the filler 0xF MUST be inserted.

So if my network code for movistar is:21407
and my tel number is: 650123456

My imsi = pin to hmac calculation is:
21407 650123456
I do not have to insert the country code??
If Imsi is: 21407 650123456
it consists of 14 digits, as it is even number,
I must use the filler 0xf; but where?
So should be my pin?
2=0010
1=0001
4=0100
......... and so on ?


















Bryce Norwood - NowSMS Support
Posted on Wednesday, September 24, 2003 - 09:55 pm:   

Your IMSI has nothing to do with your phone number, it is completely independent of that (although your mobile operator does have a table that maps your IMSI to your phone number).

You need to look at your physical SIM card, and there will be an IMSI printed on the SIM itself.

If you are using the "network PIN" method with the Now SMS/MMS Gateway, you simply enter the IMSI as is, with no conversion, as the PIN value.

If you are trying to do this yourself, then you need to convert the IMSI to semi-octet representation as defined in GSM 11.11. So you need to download the GSM 11.11 spec from the ETSI web site (www.etsi.org) to find the format information. Section 10.3.2 of that specification then defines the IMSI format, although you do need to refer back to the OMA PROVBOOT specification where it says:


quote:

The
length indicator byte and possible unused bytes (i.e. the IMSI is less than 15 digits) MUST NOT be used. If the IMSI
consists of an even number of digits the filler 0xF MUST be inserted.




Those statements make a lot more sense if you look at the defintion of the IMSI format in GSM 11.11.

-bn
koayst
Posted on Thursday, September 25, 2003 - 08:06 am:   

Hi Bryce,

Could you please provide an example on how to generate the MAC for NETWPIN method?

For example, if I have a IMSI as:
123 45 6789012345

What will be the MAC?
koayst
Posted on Thursday, September 25, 2003 - 09:38 am:   

Hi Bryce,

I meant what is the key and MAC value generated?
Bryce Norwood - NowSMS Support
Posted on Friday, September 26, 2003 - 08:39 pm:   

The MAC value depends on the content of the provisioning message, and the value of the key (shared secret).

Basically, the SHA-1 algorithm is used to compute a message digest based upon these two parameters.

The receiver validates this MAC digest by performing its own calculation based upon the shared secret (IMSI or user pin) and the content of the provisioning message.

Section 6.2.1 of the OMA Provisioning Bootstrap spec describes the general process.

To convert the IMSI value into the appropriate format to be used as the key (shared secret) for the HMAC cacluation, see Section 7.1 of the Provisioning Bootstrap spec, which has the quote that I highlighted a couple of messages earlier. That will refer you back to Section 10.3.2 of the GSM 11.11 spec which explains this semi-octet encoding of the IMSI.
Bernard
Posted on Tuesday, September 30, 2003 - 05:08 am:   

Does everybody know how create GPRS and MMS Settings using OMA to Siemens Mobile? Please give me the information. Thanks
Bryce Norwood - NowSMS Support
Posted on Tuesday, September 30, 2003 - 06:48 pm:   

I haven't had any feedback on Siemens phones that support OMA provisioning yet. Are you able to save GPRS settings for the WAP browser?

If so, you might want to try sending out a message where you do not include any browser settings in the same message (e.g., leave out any CHARACTERISTIC APPLICATION that has APPID=w2), as some phones might not be able to accept both browser and MMS settings in the same configuration message.
Anonymous
 
Posted on Monday, October 20, 2003 - 09:32 am:   

Hi Bryce,
what about nokia 6600?
Is it supported? have you tested id?

I suppose it will work exactly the same as nokia 6220, isn't it?

thanks

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 930
Registered: 10-2002
Posted on Tuesday, October 21, 2003 - 03:57 am:   

I haven't seen the 6600 yet.

One difference between it and the 6220 (and 6610) is that the 6600 is a Series 60 (Symbian OS) phone, whereas the others are Series 40.

Theoretically, everything should work the same. Based upon the documentation that I've seen, I would expect the same settings to work on the 6600.

Let us know!
Anonymous
 
Posted on Tuesday, October 21, 2003 - 07:14 am:   

OK thanks,
In a couple of weeks I am getting one,
let's see if it work the same.
The theory says so ;)

bye
Anonymous
 
Posted on Thursday, October 23, 2003 - 02:38 am:   

6220 settings for at&t or t-mobile....help
Anonymous
 
Posted on Monday, October 27, 2003 - 08:30 am:   

Finally I have the phone 6600, but a working setting on 6220 is not working in 6600.

The phone give the following message:
Can not open. Message format not supported.

Any idea?

Thanks

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 975
Registered: 10-2002
Posted on Tuesday, October 28, 2003 - 02:14 pm:   

I expect to also have a Nokia 6600 by the end of the week, so we'll see.

What is the XML document that you are using?
Anonymous
 
Posted on Wednesday, October 29, 2003 - 11:32 am:   

Hi,
this is what I am sending.
Please note, I have substitute some information
such user, pass, and IP with xxxx.yy , ABC.ABC.ABC.ABC




<?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.0">

<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="t2_gprsproxy"/>
<parm name="NAME" value="WAP HTTP"/>
<parm name="TRUST"/>
<parm name="PUSHENABLED" value="1"/>
<parm name="STARTPAGE" value="http://xxx.zzzzz.yy"/>
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="PROXY 1"/>
<parm name="PXADDR" value="ABC.ABC.ABC.ABC"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="t2_gprs"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="8080"/>
</characteristic>
</characteristic>
</characteristic>

<characteristic type="NAPDEF">
<parm name="NAPID" value="t2_gprs"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAME" value="Setting GPRS"/>
<parm name="NAP-ADDRESS" value="xxxxx.zzzzz.yy"/>
<parm name="NAP-ADDRTYPE" value="APN"/>

<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="xxxxx"/>
<parm name="AUTHSECRET" value="xxxxx"/>
</characteristic>
</characteristic>





<!-- MMS -->
<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="mmsproxy"/>
<parm name="NAME" value="T2_MMS_http"/>
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="PROXY 2"/>
<parm name="PXADDR" value="ABC.ABC.ABC.ABC"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="mms_GPRS"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="8080"/>
</characteristic>
</characteristic>
</characteristic>

<characteristic type="NAPDEF">
<parm name="NAPID" value="mms_GPRS"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAME" value="mms GPRS"/>
<parm name="NAP-ADDRESS" value="mms.xxxxxx.yy"/>
<parm name="NAP-ADDRTYPE" value="APN"/>

<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="xxxx"/>
<parm name="AUTHSECRET" value="xxxx"/>
</characteristic>
</characteristic>





<!-- applications -->
<characteristic type="APPLICATION">
<parm name="APPID" value="w2"/>
<parm name="TO-PROXY" value="t2_gprsproxy" />
<parm name="NAME" value="Browser"/>

<characteristic type="RESOURCE">
<parm name="URI" value="http://wap.xxxxxx.yy"/>
<parm name="STARTPAGE"/>
</characteristic>
</characteristic>

<characteristic type="APPLICATION">
<parm name="APPID" value="w4"/>
<parm name="TO-PROXY" value="mmsproxy" />
<parm name="ADDR" value="http://mmsc.xxxx.yy" />
</characteristic>

</wap-provisioningdoc>
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1030
Registered: 10-2002
Posted on Saturday, November 01, 2003 - 08:00 am:   

I've got my 6600 ... but unfortunately, I'm off for vacation. Will try some tests when I return ...
Yuwono Gunarto
Unregistered guest
Posted on Wednesday, November 12, 2003 - 05:35 am:   

Bryce,

Howto calculate the MAC for USERPIN ?
I've tried, but the result does not match with the MAC value on the sample (OMA-WAP-ProvCont-v1_1-20021112-C, Version 12-Nov-2002).

This is the wbxml :
030B6A054E41503100C54601C65101871506312E340001696E50726F78790001871C060368747470 3A2F2F7777772E62616E6B2E636F6D2F7374617274706167652E776D6C0001C659018719069C016E 616D650001706173737764000101C65201872F060350524F5859203100016E6B2E636F6D2F000137 2E35312E330001872106850187220603494E5445524E45540001872206830001C653018723060339 3230330001010101C65501871106830001871006AA01870706034D59204953502043534400018708 06032B333538303831323430303200018709068701870A069001C65A01870C069A01870D06037777 776D6D6D757365720001870E06037777776D6D6D736563726574000101C654018712060332323800 01871306033030310001010101

and the USERPIN is "1234".
Using HMAC calculation I get :
8C9D2E9DF1DD91E9ECCB5FBBCAED25575B166620

but on the document :

30424233424235353146
30413933333539454332
39453643454143313434
30453441363137343839

I use the wbxml as the data and the pin as the shared secret (key)

thanks
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1086
Registered: 10-2002
Posted on Wednesday, November 12, 2003 - 09:45 pm:   

Yuwono,

I don't have the time at the moment to run my HMAC generation routine against that data. But as a suggestion, I would suggest downloading the P800 OTA Provisioning document from the Ericsson web site, as this has another example that might be easier to follow.

The reason that your MAC is 20 bytes, and the example is 40 bytes is because of how the MAC is encoded as ASCII characters. But of course, even with that, your calculation does not match.

You are performing the HMAC against the data with the PIN in ASCII format, but the data in its original binary format, right?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1087
Registered: 10-2002
Posted on Wednesday, November 12, 2003 - 09:54 pm:   

Follow-up ...

I sent the settings from the "October 29, 2003 - 11:32 am" message above to my Nokia 6600, and the phone accepted them as a configuration message, and seemed to parse them correctly.

I still need to do some experiments to try with valid settings for my environment so that I can confirm that they are all set correctly, but it certainly appears to work on the Nokia 6600.
Yuwono Gunarto
Unregistered guest
Posted on Thursday, November 13, 2003 - 06:58 am:   

>>You are performing the HMAC against the data
>>with the PIN in ASCII format, but the data in
>>its original binary format, right?

Yes, in binary format. Thanks Bryce, will try to download document from Ericsson.
Anonymous
 
Posted on Monday, November 17, 2003 - 09:45 pm:   

hi,

how can i set the proxyport to port 5080?
my 6600 set it automaticly to port "0". i don´t know why...

"<!-- MMS -->
<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="mmsproxy"/>
<parm name="NAME" value="T2_MMS_http"/>
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="PROXY 2"/>
<parm name="PXADDR" value="ABC.ABC.ABC.ABC"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="mms_GPRS"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="5080"/>
</characteristic>"

thx

dvda
Enzo
Unregistered guest
Posted on Tuesday, November 18, 2003 - 04:49 pm:   

Hi Yuwono,

you missed some pieces copying the example from OMA-WAP-ProvCont-V1_1-20021112-C.pdf, as 033137302e3138372e35

please check
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1184
Registered: 10-2002
Posted on Thursday, November 20, 2003 - 01:42 pm:   

dvda,

This certainly has the appearance of being a bug in the 6600. If I set the port as 80, then it works. But other port values seem to get reset to 0.

It definitely needs some further investigation ...

-bn

Anonymous
 
Posted on Wednesday, November 26, 2003 - 09:35 pm:   

When I send an OMA XML setting document via the send XML settings interface it work (Basically cut and paste from my original document). If I submit the same document using the URL from the OTA directory, I get message submitted but it never seems to reach the phone. Any idea why?

Fred
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1272
Registered: 10-2002
Posted on Monday, December 01, 2003 - 08:34 am:   

Fred,

I believe you also contacted us via e-mail with this question.

When you reference an OMA XML settings document that is stored in the OTA subdirectory of the gateway, you need to use a URL parameter of OTAOMA=name to reference this document. (The example that I saw in the e-mail that you sent us had OMAOTA=name instead.)
Anonymous
 
Posted on Sunday, December 21, 2003 - 08:43 pm:   

Hi,

When sending oma bootstrap configuration to Nokia 6600 following message is displayed:

"Settings received but not saved. Unable to authenticate message. Message deleted."

This happens regardless of the security method I use.

If I use USERPIN method, shouldn't I be prompted to enter some pin? In my case this never happens.

Provisioning content is pushed via SMS (over GSM network).

Also, I think that I generate correct MAC value (e.g. for the Nokia's sample from 'OMA Client Provisioning for Series 40', I generate the same MAC). When using IMSI, it's semi-octet encoded and this should also work correctly.

Is it possible that this is not caused by invalid MAC generation, but has something to do with Push Validation (as described in 'Push Validation for Series 40' document), and I'm sending invalid configuration data?

TIA
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1449
Registered: 10-2002
Posted on Monday, December 22, 2003 - 10:43 pm:   

It's hard to say for certain.

But I expect the MAC is wrong, or there is some other type of header encoding error.

I haven't had to do anything special on a brand new Nokia 6600 to get it to accept settings messages using either IMSI or user pin.
c2j2
Unregistered guest
Posted on Wednesday, December 31, 2003 - 12:56 am:   

please help me and tell me if their is any way to send mms on my nokia 6600 on the t-mobile network in the U.S....I know about Zidango, but they are a LOT of money...any other way to program my phone???
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1476
Registered: 10-2002
Posted on Wednesday, December 31, 2003 - 06:50 pm:   


quote:

please help me and tell me if their is any way to send mms on my nokia 6600 on the t-mobile network in the U.S....I know about Zidango, but they are a LOT of money...any other way to program my phone???




Sorry, this has nothing to do with the original posting. Based upon what I have seen on other web sites, T-Mobile US does not currently support MMS from the Nokia 6600.
bojan
Unregistered guest
Posted on Sunday, January 04, 2004 - 12:43 am:   

i want to now mms address of this number +34686622...that is spain number.thanks
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1506
Registered: 10-2002
Posted on Monday, January 05, 2004 - 04:03 pm:   


quote:

i want to now mms address of this number +34686622...that is spain number.thanks




This also has nothing to do with an otherwise informative thread.

With MMS, the address is the phone number.

I suspect you are asking if there is an e-mail address that allows you to send an MMS by sending to an e-mail address.

Most mobile operators do not support such a capability. (This is because in most of the world, the sender pays for an MMS or SMS message, while the receiver does not pay anything. As there is no way for the mobile operator to charge an e-mail sender for the delivery, they do not offer the capability.)
Anonymous
 
Posted on Monday, January 12, 2004 - 08:02 pm:   

There is example about how to encode NETWPIN IMSI key:
http://ncsp.forum.nokia.com/downloads/nokia/documents/DP_2_0_for_Series_60_OMA_C lient_Provisioning_v1_0_en.pdf