Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

4.1 Sample SMS Object

A user creates an SMS text message, types in some text, and sends it. The following is a description of what a client might do to accomplish the user's intentions and the responses a server might return. For more details about remote operations (ROPs), see [MS-OXCPRPT] and [MS-OXCMSG].

Before manipulating SMS objects, the client asks the server to map the named properties to property IDs by sending a RopGetPropertyIDsFromNamesROP request ([MS-OXCROPS] section 2.2.8.1).

Property

Property set GUID

NameID

PidNameOMSMobileModel (section 2.2.1.6)

{00020329-0000-0000-C000-00000000046}

OMSMobileModel

PidNameOMSAccountGuid (section 2.2.1.1)

{00020329-0000-0000-C000-00000000046}

OMSAccountGuid

PidNameOMSServiceType (section 2.2.1.3)

{00020329-0000-0000-C000-00000000046}

OMSServiceType

PidNameOMSSourceType (section 2.2.1.4)

{00020329-0000-0000-C000-00000000046}

OMSSourceType

The server might send a RopGetPropertyIDsFromNamesROP response with the following property IDs, which are used in the example that follows. (The actual property IDs are at the discretion of the server.)

Property

Property ID

PidNameOMSMobileModel

0x84C3

PidNameOMSAccountGuid

0x84C4

PidNameOMSServiceType

0x84C5

PidNameOMSSourceType

0x84C6

To create an SMS object, the client uses the RopCreateMessage ROP ([MS-OXCROPS] section 2.2.6.2).The server returns a success code and a handle to a Message object.

After the user inputs the content for the SMS object, the client transmits the data to the server by using the RopSetProperties ROP ([MS-OXCROPS] section 2.2.8.6).

Property

Property ID

Data type

Value

PidNameOMSAccountGuid

0x84C4

PtypString ([MS-OXCDATA] section 2.11.1)

{01234567-0123-0123-0123-0123456789AB}

PidNameOMSMobileModel

0x84C3

PtypString

(null)

PidNameOMSServiceType

0x84C5

PtypInteger32 ([MS-OXCDATA] section 2.11.1)

0x00000001

PidNameOMSSourceType

0x84C6

PtypInteger32

0x00000000

PidTagBody ([MS-OXCMSG] section 2.2.1.56.1)

0x1000

PtypString

What time is the meeting?

PidTagInternetCodepage ([MS-OXCMSG] section 2.2.1.56.6)

0x3FDE

PtypInteger32

0x0000FDE9

PidTagMessageClass (section 2.2.2.2)

0x001A

PtypString

IPM.Note.Mobile.SMS

PidTagNormalizedSubject (section 2.2.2.4)

0x0E1D

PtypString

What time is the meeting?

PidTagSubjectPrefix ([MS-OXCMSG] section 2.2.1.9)

0x003D

PtypString

(null)

When the user sends the message, the client commits the properties on the server by using the RopSaveChangesMessage ROP ([MS-OXCROPS] section 2.2.6.3) and then releases the SMS object by using the RopRelease ROP ([MS-OXCROPS] section 2.2.15.3). The client then submits the message to an SMS provider by using the RopSubmitMessage ROP ([MS-OXCROPS] section 2.2.7.1).

The values of some properties change during the processing of the RopSaveChangesMessage ROP, but the properties defined in this specification do not change.

Show:
© 2015 Microsoft