SpeedDial Configuration Service Provider Examples for OMA DM
4/8/2010
The following example can be used as a template to configure settings for the SpeedDial Configuration Service Provider.
The following code example shows extended provisioning XML. It specifies a speed dial entry and also names the speed dial key. In this example, pressing and holding the 2 key dials the telephone number shown.
Note
In general, the OMA DM standard defines <Item>...</Item> blocks as listable in any order in your provisioning XML. However, for the SpeedDial configuration service provider, you must be sure to place the block defining the Key parameter before the block defining the Tel parameter.
Note
For OMA DM, the SpeedDial Configuration Service Provider handles the Replace command differently from most other configuration service providers. For the SpeedDial Configuration Service Provider, Configuration Manager implicitly adds the missing part of the node to be replaced or any segment in the path of the node if it is left out in the <LocURI></LocURI> block.
Code Example
<Atomic>
<CmdID>1</CmdID>
<Add>
<CmdID>2</CmdID>
<Item>
<Target><LocURI>./Vendor/MSFT/SpeedDial/Firstname%20Lastname</LocURI></Target>
<Meta>
<Format xmlns="syncml:metinf">node</Format>
</Meta>
</Item>
<Item>
<Target><LocURI>./Vendor/MSFT/SpeedDial/Firstname%20Lastname/Key</LocURI></Target>
<Data>2</Data>
<Meta>
<Format xmlns="syncml:metinf">int</Format>
</Meta>
</Item>
<Item>
<Target><LocURI>./Vendor/MSFT/SpeedDial/Firstname%20Lastname/Tel</LocURI></Target>
<Data>4255550111</Data>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
</Item>
</Add>
</Atomic>
Remarks
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 SyncBody node in an OMA DM provisioning file. For more information about the syntax of the provisioning file, see OMA DM Provisioning Files.