I think it is extra, because a "01" for pxphysical end is show in the example.
Anyway, now the mobile receive the setting OK.
At the begining it shows me the same message as you say.
Try the example at the end of document:
By the way,
in this example at the end of OMA-WAP-ProvCont ask for a settings PIN once it have received the settings.
I have tried: 1234, 12345, and many others but it does not work.
I receive OK the settings, but I am not able to save the settings.
Does any one knows which is the right setting pin I have to enter?
Where can I found another example that makes no use of security?
(SMS 1 out of 4)
0x0B; /* User data header length */
0x05; /* NBS command ports */
0x04; /* Lenght of ports */
0x0B; /* Data 1 - listener port */
0x84; /* Data 2 - listener port */
0x23; /* Data 3 - sending port */
0xF0; /* Data 4 - sending port */
0x00; /* Concat messages */
0x03; /* User data header length */
0x01; /* Reference number*/
0x04; /* Total Messages count */
0x01; /* This part number*/
< here comes part of nokia example>
This is standard stuff, and can be found on the internet,
but there are others options but it depends on how you are sending out SMS'es. The optional choice would be to use a Push Proxy Gateway, and forget about SMS headers. I for my self am sending SMS'es over UCP to a SMSC.
If you tell me how you are sending out the SMS'es I might
be of more help.
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 some string value gone wrong, but not the structure.
If it happens that you are splitting the SMS'es on a string value, and the payload is of wrong length, the MAC value is incorrecly calculated. Just a thought.