|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.|
The NetworkPolicy Configuration Service Provider example below can be used to disable the Bluetooth network interface.
In this example, the Bluetooth network interface is disabled since the "Disabled" parameter value is set to "1".
If any other value had been specified, or if the "Disabled" parameter were missing altogether, the Bluetooth network interface would be enabled.
<characteristic type="NetworkPolicy"> <characteristic type="Bluetooth"> <characteristic type="Settings"> <parm name="Disabled" value="1"/> </characteristic> </characteristic> </characteristic>
One provisioning XML file typically contains configuration information for multiple configuration service providers. To use this example, you must replace the values as appropriate, and add the node as a child of the wap-provisioningdoc element in an OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.
This example could be extended to disable Wi-Fi and IrDA as well. Simply replace "Bluetooth" with "Wi-Fi" or "IrDA" as applicable. To disable multiple network interfaces, duplicate the XML from lines 2-5 for each network interface.