OMA provisioning for Windows Mobile 2003

OMA provisioning for Windows Mobile 2003 SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through July 14, 2005 » OMA provisioning for Windows Mobile 2003 « Previous || Next »
Author Message
Matt
Unregistered guest
Posted on Tuesday, December 28, 2004 - 10:40 am:   

Hi
i'm a newbie in OTA provisioning and i'm trying to configure e-mail settings on some Windows Mobile 2003 devices (smartphone 2003, pocketPC phone edition). but for some reason this does not work using NowSMS. i tried to sign the message by USERPIN and NETWPIN. in every case the device receives the settings but then nothing happens. only NETWPIN signed message sending onto a pocketPC results in a 'config error message' as a reaction.

does microsoft using an own extension of OMA standard which is not supported by NowSMS?

i would like to send the XML below:
<wap-provisioningdoc>
<characteristic type="Sync">
<characteristic type="Connection">
<parm name="Server" value="testserver"/>
<parm name="User" value="testuser"/>
<parm name="Password" value="testpassword"/>
<parm name="Domain" value="testdomain"/>
<parm name="SavePassword" value="1"/>
<parm name="UseSSL" value="1"/>
<parm name="AllowSSLOption" value="1"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>

thanks for any hints!

regards matt
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3837
Registered: 10-2002
Posted on Friday, December 31, 2004 - 05:49 pm:   

Hi Matt,

Windows Mobile defines some extensions to the OMA provisioning specification.

Normally, the way that this would work, is that if we encounter an attribute value that does not have an OMA-defined token value ... we encode it as text.

But Microsoft has gone and defined additional token values for their specific attributes.

And my suspicion is that they only support the binary tokens.

We have been studying the MS documentation for all of this. However, we have yet to implement.

It is not a lot of work. But the primary thing is that we will need to require that you include an XML header that tells us that you are using Microsoft's DTD instead of the OMA's. The bigger issue is that it is difficult for us to test without sending directly to an MS SmartPhone.

I suspect we are going to have to purchase an MS SmartPhone model for testing in order to implement correctly. Do you have any recommendations on what model would have all of the latest features?

-bn
Matt
Unregistered guest
Posted on Wednesday, January 05, 2005 - 03:36 pm:   

hi bryce

thanks for your answer.
a good description of these additional tokens can be found in the 'Mobile Operators Guide' from microsoft. but i guess this document will be provided under NDA only. i don't know if this information can be found somewhere on the net.

device recommendation:
- the motorola MPx220 which runs on windows mobile smartphone 2003 platform has all the latest features. but i suggest to get an 'open' device where no security policy features are set by default to avoid any start problems.
- the QTek9090 pocketPC uses another security concept (less security) but supports the same features/tokens as talked about before.

Matt
Matt
Unregistered guest
Posted on Monday, January 10, 2005 - 02:50 pm:   

in the meantime i've found a link to the DTD definition:
http://whidbey.msdn.microsoft.com/library/default.asp?url=/library/en-us/amo_ppc /htm/smartphone_provisioning_document_format_zatm.asp

does this help to complete the tokens for MS provisioning?

Matt
Matt
Unregistered guest
Posted on Monday, January 10, 2005 - 02:52 pm:   

sorry i was too fast. this one might be helpful too:
http://whidbey.msdn.microsoft.com/library/default.asp?url=/library/en-us/amo_ppc /htm/code_page_3_odja.asp

Matt
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3918
Registered: 10-2002
Posted on Monday, January 17, 2005 - 10:26 pm:   

Hi Matt,

Sorry, I've been a way for a bit. Those links help. But there are so many code pages ... argh (that generally means lots of testing).

Let me study those in a bit more detail.

Meanwhile, I'm going to look into getting an unlocked MPx220.
kent eriksson
New member
Username: Lynxlynx

Post Number: 1
Registered: 02-2005
Posted on Friday, February 11, 2005 - 06:35 pm:   

How is it going?
I just found your site and its just what I am looking for!
I am trying to work out how to sen xml/wbxml data to smartphones(mob2003)
I can get it to work just fine with it docked...but having problems finding and good gateways to use to send it out OTA.
So please say this is worked out and its just to download and try it ??!!
:-)

alot of thanks for a good site and an even better forum! alot of questions answered just browsing it!
kent eriksson
New member
Username: Lynxlynx

Post Number: 2
Registered: 02-2005
Posted on Monday, February 14, 2005 - 08:14 pm:   

anyone?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4068
Registered: 10-2002
Posted on Tuesday, February 15, 2005 - 04:19 pm:   

Hi Kent,

I never did follow up on purchasing that phone for testing. I'm away at the 3GSM conference this week, so I will have to try to follow-up on getting one of these phones.

Our "Send XML Settings" interface would be the way to go. However, we are going to perform the WBXML conversion with the non-standard Microsoft specific tags being encoded as text strings instead of the MS specific binary codes. It appears that MS does not support the text string encoding in the WBXML (at least that was my impression based upon the above discussion), which is why I need to see one of these phones so we can run some tests.

What Smartphone model would you recommend we purchase for testing?

-bn
kent eriksson
New member
Username: Lynxlynx

Post Number: 3
Registered: 02-2005
Posted on Wednesday, February 16, 2005 - 09:40 pm:   

Hi there!
Thanx for the answer!!!

It would be so nice if you could get this to work,smartphones/ppc rely heavy on xml so a working product would be a feather in your hat I think.
on the subject on what phone to get I can recommend any win mob 2003 phone edition.
I pesonally use qtek 9090 and 8010 but there are so many new ones coming out so I dont know what to say...If I was u I would talk to microsoft or a supplier ...they should be able to supply you with a phone! I is in their best interest is it not??
You guys are from the uk right? what do you have over there O2 or orange or something...I am from sweden so it might be sold under a different name there...

Good luck! and have fun at the 3gsm conference!!

Anonymous
 
Posted on Wednesday, February 23, 2005 - 06:48 pm:   

How is it coming along with the ms mobile 2003 gateway?
Did you guys figure it out yet?
I am so looking forward to try this out!
Would a day with a smartphone be enough...if so I could lend you mine....
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4090
Registered: 10-2002
Posted on Thursday, February 24, 2005 - 06:07 pm:   

Sorry for the delay. I've got a QTek 9090/imate PDA2K on order, so we'll try to get something sorted in the next couple of weeks.

We probably could talk to somebody about getting a loaner or eval. But it takes so much time talking to a vendor. I appreciate the loaner offer, but I also figure that we'll need to support it going forward. And we need to explore other possibilities with this platform. So it's a good investment.

I just wasn't too excited about the MP220x. I guess you could say that the original Orange SPV left a very bad taste in my mouth. But these other devices do look interesting.

I'll post some follow-up as we start testing.

-bn
kent eriksson
New member
Username: Lynxlynx

Post Number: 4
Registered: 02-2005
Posted on Friday, February 25, 2005 - 01:43 am:   


I am looking forward to trying it out!!!
If you need any feedback or someone to try it out pls tell me!
I have access to 9090 and 8010 and several more soon I think.
(we are working on a mobile platform at work u see....)
Anonymous
 
Posted on Friday, March 11, 2005 - 12:44 am:   

any news?

/kent
Anonymous
 
Posted on Friday, March 11, 2005 - 08:04 pm:   

Hmm A Qtek 9090.. I've got one and I'm not 100% happy with it (as a phone). WiFi and Bluetooth sucks on it. Also.. Other's who call you have problems understanding you (got something todo woth the mick)

Still It's nice to have all in one. I give it a 6 out of 10.

N
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4176
Registered: 10-2002
Posted on Tuesday, March 15, 2005 - 08:12 pm:   

Hi Kent,

I've got a device now, but it seems that by default these devices will only accept provisioning content over WAP Push if the content has been signed by both a user PIN and a network PIN, where the network PIN is the IMSI of the SIM card in the device.

We are going to try to implement an option to allow such signing (currently we allow one or the other, but not both simultaneously). But the bad news seems to be that in order to send a provisioning message out to one of these devices, you need to know the IMSI of the SIM that is in the device. This can be very difficult to manage unless you are a mobile operator.

-bn
Anonymous
 
Posted on Wednesday, March 16, 2005 - 07:48 pm:   

No u can send with IMSI signing only. U need to set the security level for WAP in the registry to support this. IMSI is "silent" expect for success/failure message in the SMS inbox, u can't stop the later; well u can but its a long story.

U can always send cab/cfp with provisioning in it via service load/indication (no signing needed).. it will be autmatically actioned once the file has been downloaded assuming that the handler is running under the security level that has the rights to implement the content of your provisioning.
Key thing is setting the correct security levels in the registry.
Anonymous
 
Posted on Wednesday, March 16, 2005 - 07:53 pm:   

MS specific Encoding Tags. If used I found they work fine. If not used also works fine. Note there is one clash with one of the Public tags I seem to remember..I just patched out the Public tag since it has little relevance on an MS device
lynx
Unregistered guest
Posted on Thursday, March 17, 2005 - 06:47 am:   

ok some progress I see...not a working 100% yet but you will get there I am sure :-)

about the signings and registry...is that preset by ms or by the operator/phonedealer ?
I know several have their own settings but is there a default level ?
The phones I have are not operator dependant so I am hoping that they will be "unlocked" to the default level....
I will look into it but if anyone have the answer pls tell me :-) !!!

about the phone being 6 out of 10 ...there are patches that make the mic/sound better and what phone is better? I have booth a 8010 and a 9090 and I am trying a motorola mpx220..that moto have very bad sound compared to qtek´s !
and it shuts down when fiddling with the BT settings too :-( hopefully they will patch it soon...

/kent
Anonymous
 
Posted on Thursday, March 17, 2005 - 06:55 am:   

Quote:
"U can always send cab/cfp with provisioning in it via service load/indication (no signing needed).. it will be autmatically actioned once the file has been downloaded assuming that the handler is running under the security level that has the rights to implement the content of your provisioning.
Key thing is setting the correct security levels in the registry."
/quote
I would be intersted in how you set up your gateway to do this!
We are new to nowsms and would really like to use it if we only could get it to work :-)
Best regards
/kent

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4248
Registered: 10-2002
Posted on Monday, March 28, 2005 - 08:28 pm:   

Kent,

It wasn't me that posted the other responses.

I would love to know how to do this myself, but I don't know how to set security levels in the registry of a Windows mobile device.

I can't get my Windows mobile device to accept an SI/SL (service indication/load) push message at all ... or at least, I can't get it to present it in the user interface. If I could get past that problem, then we could probably make some real good progress.

-bn
Anonymous
 
Posted on Thursday, March 31, 2005 - 11:57 am:   

HKLM\security\policies\policies .... u will need to have the MS Smartphone SDK documentation to hand as there to much info to detail here ... set Service Load, and if u require Service Indication (seperate registry settings ) to 64 .. u will need to enable the WapPush setting ... u will also need regedit tool and if at all possible a developer environment, unlocked phone vital for testing/dev
It's all detailed in the SDK ...once u have read it, it will all be clear ... without the above u will be pissing in the wind ... I had the above and still got very wet !
Anonymous
 
Posted on Monday, May 09, 2005 - 02:15 pm:   

For Windows Smartphone, it works for the SI/SL but not for "non standard" content types or AppId.

For SL or SI, you have to put your PPG number in the registry. (to be considered as a trusted PPG)

I can't find a way to have non standard Push messages processed by the Push Router.
Anonymous
 
Posted on Monday, May 09, 2005 - 04:51 pm:   


quote:

For SL or SI, you have to put your PPG number in the registry. (to be considered as a trusted PPG)




How is this done?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4484
Registered: 10-2002
Posted on Monday, May 09, 2005 - 05:11 pm:   

I've been able to get an SI to the phone by changing the SmartPhone configuration settings to accept SI from untrusted gateways.

You need to do it with the phone connected to the USB cradle ... and I've only found out so far how to do it via the SDK. Details in the following thread:

http://support.nowsms.com/discus/messages/1/9063.html

I haven't seen how to update the list of trusted push proxy gateways though. Normally you would send an OTA message to add a trusted PPG ... but since it will only accept OTA from trusted PPG, it's a catch 22.

Maybe you could add the trusted PPG via USB interface?
Anonymous
 
Posted on Thursday, May 12, 2005 - 11:24 am:   

anyone got the solutions yet of how to "unlock" the untrusted gateways for PPC series to receive WAP PUSH message?
Frank Kurka
New member
Username: Fkx

Post Number: 2
Registered: 05-2005
Posted on Thursday, May 12, 2005 - 02:19 pm:   

I'm jsut researching this topic now. I assume you are asking because you have not been able to get a wap push to a ppc connected to a carrier.

Are you sure the network that the ppc is on supports wap push?

So far it looks like of all the carries in the US who support pocket PC only TMobile allows wap push.

Is this consistet with what you have found? or are my assumptions incorrect for your situation?

Sorry if I am "missing the boat".
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4544
Registered: 10-2002
Posted on Wednesday, May 18, 2005 - 08:51 pm:   

This link explains how to unlock a Pocket PC so that it can receive WAP Push messages from a PPG that is not on its trusted list:

http://support.nowsms.com/discus/messages/1/9063.html

I purchased a Smartphone that was unlocked (not locked to any particular carrier SIM), but it still could not receive any WAP Push messages.

I don't know if that means that the Smartphone has an empty trusted PPG list, or if it has a list that was associated with a carrier that the phone might have originally been locked to.

In the US, you have issues that there are different mobile network technologies. GSM technology is very widespread around the world, and WAP Push can be sent using binary SMS formats.

However, it is next to impossible to get an SMS service provider connection that supports binary SMS into a CDMA carrier.

So WAP Push is pretty much limited to the GSM carriers ... T-Mobile, Cingular/ATTWS. For CDMA operators, such as Sprint and Verizon, you need to connect to the operator's WAP Push Proxy Gateway in order to send any WAP Push messages.
Anonymous
 
Posted on Wednesday, May 25, 2005 - 03:08 pm:   

Hi,
I have this xml file to configure OMA MMS settings for terminal like nokia 6230:

<!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="MMS GPRS"/>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAPID" value="MMS GPRS"/>
<parm name="NAME" value="MMS GPRS"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAP-ADDRESS" value="mms.xxx.xx"/>
<parm name="NAP-ADDRTYPE" value="APN"/>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value=""/>
<parm name="AUTHSECRET" value=""/>
</characteristic>
</characteristic>
<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="xxx.xxx.xxx.xxx"/>
<parm name="NAME" value="MMS GPRS"/>
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="MMS GPRS"/>
<parm name="PXADDR" value="xxx.xxx.xxx.xxx"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="MMS GPRS"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="9201"/>
<parm name="SERVICE" value="CO-WSP"/>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w4"/>
<parm name="TO-PROXY" value="xxx.xxx.xxx.xxx"/>
<parm name="ADDR" value="http://xxx.xxx.it/xxx/mms"/>
</characteristic>
</wap-provisioningdoc>

My application take this file in input, convert it in wbxml standard like wapforum suggest with prov.dtd and all work fine.

Now this don't work with i-mate PDA2K can you help me? What do I modify for my i-mate?

Thanks in advance for your suggestions.
best regards
Lisa


Login Login / Register Logout Logout Search Last 30 Days Topics Topics