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.
4/8/2010

SyncHdr includes the following information:

This information is used to by the client device to properly manage the DM session.

Code Example

The following example shows the header component of a DM message. In this case, OMA DM version 1.2 is used as an example only:

Note:
The <LocURI> node value for <Source> element in the SyncHdr of the device generated DM package should be the same as value of ./DevInfo/DevID. For more information about DevID, see DevInfo Configuration Service Provider.
Copy Code 
<SyncHdr>
	<VerDTD>1.2</VerDTD>
	<VerProto>DM/1.2</VerProto>
	<SessionID>1</SessionID>
	<MsgID>1</MsgID>
	<Target>
		<LocURI>{unique device ID}</LocURI>
	</Target>
	<Source>
	 
<LocURI>https://www.thephone-company.com/mgmt-server</LocURI>
	</Source>
</SyncHdr>

See Also