yes, I am using the same xml structured document as for the 6220. No, I haven´t seen any 6600 specific text. I can however not delete the settings in the Nokia 6600 with the standard code...

The sample I am working on is working on standard ports. However, it accepts both OMA settings and NOKIA OTA 7.0 settings. Have you tried the "old" NOKIA OTA 7.0 format ?

regards,
///f.

The setup document that I used on Nokia 6220 did not do so great on the Nokia 6600. 6600 accepted the settings document, but rejected the MMS part and complains about a missing home page. So I...

ok -I know that you have figured it out by now,
But just for the records: The filler should be the last figure
if it is needed in the IMSI, so it would become the second to last figure in the key...

I am working in a Nokia 6220 and a 5100 both with a TCP/IP stack, and they both accept the above mentioned wbxml document. Even the T610 from Ericsson answered to ! and I suspect the P800 will also....

My guess would be that you insert a filler in the MCC/MNC part
of the IMSI. It also says that you need to GSM code the IMSI.

The IMSI 21407 650123456 becomes:
-> 21 4F 07 06 50 12 34 56
-> 12...

If f.x. you have two number like "213 03" that's coded in GSM format with fillers like this:

213 03 -> 21 3x 03 -> 21 3F 03 -> 12 F3 30

But now your IMSI is even, so do you need any fillers...

Hi seancronin


>>V 3.02 13-12-02 NPM-6.

I think you are using a standard 5100 handset i.e. a WAP 1.2.1
but not WAP 2.0 handset. It will accept standard Nokia OTA settings, but not WAP 2.0...

Hi koayst

In Section 4.3, Media type parameter. Page 16; OMA-WAP-ProvCont-v1_1-20021112-C, Version 12-Nov 2002.

MAC:
This parameter contains an even number of upper case hexadecimal digits.
...

>>NOTE: "0bb3bb ...." is transformed to "304242304243...."

In ProvCont, it is stated that the MAC value should be entered as a hexadecimal string so this is correct. My advise is for you to...

I am only using the information about the MAC value from the OMA specification ProvCont, and if I follow that specification I get the same MAC value as in example 1.

No, I don't have a SyncXML...

Hi koayst

You are using the rigth program.

>>according to the specification, I need to go thru the resulted >>string from HashCalc to the formula MOD 10 + 48.

Could you please explain what...

Great ! Satisfying isn't it.

I am not sure about the open source but there is a lot of code
out there in all kinds of languages. I would google for a program called HashCalc.

/f.

Hi koayst

I would take a gooood look at the binaries again or the lenght of the payload in the SMS headers. If the phone assembles the SMS'es correctly and shows "new settings received" it is...

Alrighty then, lets hope someone has donated you a SIM card
for use in testing.

Answer 1:
The specification in question is part of the WAP specifications, namely "Wireless Datagram Protocol" ...

Hi koayst,

I am using standard SMS headers:

fx.

(SMS 1 out of 4)
0x0B; /* User data header length */
0x05; /* NBS command ports */
0x04; /* Lenght of ports */

Hi,

I am curios. You don't mention if you are calulating the MAC value with the IMSI represented as a semi-octed as in GSM world.

Are you ?

/f

I have a Nokia 5100 USA version, and it happily accepts bootstrapping document like the Nokia 6220 model.

I have however not been able to use the PPG model, but I am down at the wbxml level. ...

Hi

I tried the example in ProvCont and got it working. Great ! finally.
I am able to save the settings, using the pin 1234.

If you change something in the ProvCont document, you would have to...

Are you sure that this extra "01" is not the end of PHYSISCAL ?

Anyways, I have this extra "01" + tried to remove it,
but both attempts failed i.e. I always get "failed to save received...

I have got so far as getting the phone to display "Can't save settings" but that's it. At least it seems to parse the document.
I haven't seen any pitfalls yet.

regards,
F.

This is all wrong !

>>0605040B8423F0000601B001066A008509037761702E776
>>17066722E6E6574000601

06 = length
05 = NBS ports
04 = port length
0B84 = listener port
23F0 = sending...

This is all wrong !

>>0605040B8423F0000601B001066A008509037761702E776
>>17066722E6E6574000601

06 = length
05 = NBS ports
04 = port length
0B84 = listener port
23F0 = sending...