Obex Configuration Service Provider
The Obex Configuration Service Provider configures the Obex server, which performs Bluetooth and infrared beaming. If the device is being run by the Obex server and has the associated hardware, the device can receive Bluetooth and infrared beams.
Note This Configuration Service Provider is not available on Windows Mobile-based Pocket PCs.
This Configuration Service Provider can be managed over both the OMA Client Provisioning (formerly WAP) and the OMA DM protocol.
Note Access to this Configuration Service Provider is determined by Security roles. Because OEMs and Mobile Operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. For more information about roles, see Security Roles and Default Roles for Configuration Service Providers.
The following image shows the management object used by OMA DM.
.gif)
The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.
.gif)
Characteristics
- HKLM\Software\Microsoft\Obex
This characteristic must be present to change the Obex mode.
Parameters
IsEnabled
This parm is used in the HKLM\Software\Microsoft\Obex characteristic to set the Obex mode. It can be true or false.Value Description 0 False. Obex is off; the device cannot receive beams. 1 True. Obex is on; the device can receive infrared and Bluetooth beams if the relevant hardware is present and turned on. The following table shows the default settings.
Permissions Read/write Data type Boolean Roles allowed to query and update setting Manager Authenticated User
Microsoft Custom Elements
The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.
| Elements | Available |
|---|---|
| parm-query | Yes |
| noparm | No |
| nocharacteristic | No |
| characteristic-query | No |
Use these elements to build standard OMA Client Provisioning (formerly WAP) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to generally use the Microsoft custom elements, see Provisioning XML File Examples.
For information about OMA Client Provisioning, see OMA Client Provisioning Files.
The following topics provide examples for the Obex Configuration Service Provider:
- Obex Configuration Service Provider Examples for OMA Client Provisioning
- Obex Configuration Service Provider Examples for OMA DM
See Also
Configuration Service Provider Reference for Windows Mobile-Based Devices | Obex Configuration Service Provider Examples for OMA Client Provisioning
Send Feedback on this topic to the authors