| OTA Settings and MS Smartphones |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| NZ Unregistered guest |
Hi, Is it possible to send ota settings to MS Smartphones (WM 2003 SE) with nowsms ? I've tried to send an XML file which works via ActiveSync, but nothing happened. Any solution ? Thanks. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4753 Registered: 10-2002 |
NZ, As far as I know, the answer is No. The problem is that the default security policy on an MS SmartPhone is to reject any OTA settings unless they come from a push proxy that is in the phone's trusted push proxy list. I believe that you could send an XML file via ActiveSync that adds a push proxy to this trusted list. Or you could send an XML file via ActiveSync that changes the policy restriction. But since that you have to do the above via ActiveSync, you might as well do all of the provisioning via ActiveSync. In another thread, I posted details about how to change the policy to allow an MS smartphone to receive WAP Push messages from a push proxy that is not in the trusted proxy list: http://support.nowsms.com/discus/messages/1/9063.html However, that particular policy setting only applies to WAP Push Service Indication (SI) messages. I believe there is a different policy number for OTA configuration messages. But I don't know the number. Based upon a quick web search, I believe that a policy number of 4111 instead of 4109 might do the trick. I also don't know what XML would add a push proxy to the trusted push proxy list. Normally, you would add a NAPDEF where the NAP-ADDRESS is the phone number that will be used as the SMS sender in the WAP Push messages ... and NAP-ADDRTYPE is "E164". And then you also include <parm name="TRUST"/> to indicate that this should be a trusted push proxy. Microsoft has published more info about all of their mysterious policy handling as it relates to Windows Mobile 5 (past information has not been as detailed). The question is how much of this information also relates to current versions. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mobilesdk5/html /wce51conSecurityRoles.asp Unfortunately, I have not had any time to do more experimentation with MS Smartphones, but these pieces of information might help point you in the right direction. -bn | |||
| NZ Unregistered guest |
Thanks a lot for the links. Well, I've tried to send the file encoded with both a Network PIN and a User PIN, then the phone says "Update successfull", but no new GPRS profile is created, which is quite strange... I will try to investigate the trusted proxy thing... NZ. | |||
| NZ Unregistered guest |
By the way, does nowsms handle new tokens introduced by Microsoft for their smartphones ? (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/DevGuideSP/html /sp_wce51congsmsmartphonepocketpcphoneeditionprovisioningwbxmlozup.asp) | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4787 Registered: 10-2002 |
Hi NZ, No, we haven't added support for the MS extensions to the provisioning document. But we would add them, if we could figure out what needs to be done to get the device to accept a provisioning message. Here is an example of configuration XML to enable a trusted push proxy (I'm not sure if it will work against an MS device): <?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="PXLOGICAL"> <parm name="PROXY-ID" value="Trusted_Proxy"/> <parm name="NAME" value="Trusted Proxy"/> <characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="Trusted_PhProxy"/> <parm name="PXADDR" value="999999"/> <parm name="PXADDRTYPE" value="E164"/> <parm name="TO-NAPID" value="Trusted_NAPID"/> <parm name="PUSHENABLED" value="1"/> <parm name="PULLENABLED" value="0"/> </characteristic> </characteristic> <characteristic type="NAPDEF"> <parm name="NAPID" value="Trusted_NAPID"/> <parm name="BEARER" value="GSM-SMS"/> <parm name="NAME" value="Trusted Proxy"/> <parm name="NAP-ADDRESS" value="999999"/> <parm name="NAP-ADDRTYPE" value="E164"/> </characteristic> Basically, you want to change the 999999 to the phone number that will be the sender address for the SMS OTA or push messages that you will send. | |||
| NZ Unregistered guest |
well, I've tried to send this XML file via SMS and it was rejected as it was malformed or something like that. Then via ActiveSync and it was ok. Then I tried with a provisioning file via SMS and it was also rejected... So I think that either the provisioning files should be encoded with the microsoft tokens to be understood by the phone, either there is still something else to change in the registry... | |||
