See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Windows Mobile devices can be bootstrapped by means of an OTA WAP push. This method is useful if the mobile operator prefers to bootstrap the device over the air at the point of sale or after purchase. In this method, a provisioning document that uses the format defined in the WAP Provisioning specifications can be pushed to the device over the air through the WAP connectionless nonsecure push mechanism over the Mobile Terminated Short Message Service (SMS) bearer.
 Note: |
|---|
| OTA bootstrapping is disabled by default in Windows Mobile devices. Before you can bootstrap or continuously provision the device OTA you must enable OTA bootstrapping. For more information, see Enabling OTA Bootstrapping. |
The content of the push message is a WAP provisioning XML file. For more information about the WAP connectivity parameters that can be used in a provisioning XML file, see WAP Connectivity Bootstrap Message. For information about additional custom configuration parameters that can also be put in the provisioning XML file, see Configuration Service Providers.
- Benefits
-
The mobile operator does not need to preconfigure the device at manufacture. Operators can bootstrap the device with the configuration data in demand on the fly.
- Drawbacks
-
The mobile operator's network must support the WAP push and the WAP provisioning bootstrap requirements. Only the mobile operator can use this method because only the mobile operator knows the device's network PIN.
For more information about how to provision OTA through a WAP push, see Pushing XML OTA Using an OMA Client Provisioning Server.