Enabling Text Message Synchronization

4/8/2010

In the example presented here, a device is configured to enable text message synchronization.

Note

E-mail must also be synchronized in order for text messages to be synchronized.

Code Example

1. Sources GUIDs are generated at run time, so they will vary between devices. You need to first determine the Sources GUID before you can enable or disable text message synchronization. Use the following XML to query for the Sync "Sources": GUID:

   <characteristic type="Sync">
       <characteristic-query recursive="false" type="Sources"/>
   </characteristic>
   

2. Use the Sources GUID returned in step 1 to replace <{GUID}> in the following XML:

   <characteristic type="Sync">
       <characteristic type="Sources">
           <characteristic type="<{GUID}>">
               <characteristic type="Engines">
                   <characteristic type="{22C7DA12-F3FD-4875-8344-7786454F6534}">
                       <characteristic type="Providers">
                           <characteristic type="{A27A846D-CACE-4959-AD99-A0B470261143}">
                               <parm name="Enabled" value="1"/>
                           </characteristic>
                       </characteristic>                        
                   </characteristic>
               </characteristic>                
           </characteristic>
       </characteristic>
   </characteristic>
   

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 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.

See Also

Tasks

Sync Configuration Service Provider Examples for OMA Client Provisioning