[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

an email:MessageClass element (as specified in [MS-ASEMAIL] section 2.2.2.13) that has a value
of "IPM.Schedule.Meeting.Request", and its airsync:ApplicationData element (section 2.2.3.10)
contains an email:MeetingRequest element (as specified in [MS-ASEMAIL] section 2.2.2.14).
When the client displays the meeting request message, the client SHOULD offer the options of
accepting, declining, or tentatively accepting the meeting. If one of these actions is selected, the
client sends a MeetingResponse command to the server.
If the response to the meeting is accepted or is tentatively accepted, the server will add or update
the corresponding calendar item and return its server ID in the meetingresponse:CalendarId
element (section 2.2.3.17) of the response. If the response to the meeting is declined, the response
will not contain a meetingresponse:CalendarId element because the server will delete the
corresponding calendar item. If the client had created a tentative meeting calendar item, the client
updates that item with the returned server ID (if accepted or tentative). The client MUST also
change the busy status on the client calendar item from tentative to busy if the meeting request
was accepted. Note that, if the client synchronizes the Calendar folder after responding to a meeting
request, the calendar item in question will be in conflict if the client also sends the changed item
change for it back to the server. This conflict is resolved according to the conflict resolution rules
that are specified by the client in the Sync command request.
If the meeting request was accepted, the Calendar folder MUST be synchronized for the client to
obtain the new calendar item. The new calendar item for the accepted meeting is added here and
MUST be added to the client's calendar.
The following table lists the command sequence for receiving and accepting meeting requests. The
asterisk (*) in the Order column means that a step can be repeated multiple times.
Order Client action Server action
1 The client sends the Sync command request for
the Inbox collection with the value of the
airsync:SyncKey element (section 2.2.3.156.4)
set to zero (0).
2* The client sends a Sync command request,
specifying the airsync:GetChanges element
(section 2.2.3.72) and the airsync:SyncKey
element for the Inbox folder. The command
SHOULD include the airsync:WindowSize
element (section 2.2.3.172), the recommended
value for which is 100.
The server responds with the
airsync:SyncKey for the collection, to be
used in successive synchronizations.
The server responds with airsync:Add
elements (section 2.2.3.7.2) for items in the
Inbox collection, including a meeting request
item. If the response contains the
airsync:MoreAvailable element (section
2.2.3.99), this step is repeated.
3 The user chooses to accept, decline, or
tentatively accept a meeting request that is
displayed in the client UI.
4 The client sends a MeetingResponse command
request (section 2.2.2.9.1) to the server, which
specifies that the meeting was accepted,
declined, or tentatively accepted, and provides
the server IDs of the meeting request message
and its parent folder.
5 If a response was requested by the organizer,
the client SHOULD use a SendMail command
(section 2.2.2.15) to send an appropriately
formatted meeting response.
The server sends a response that contains
the MeetingResponse command request
status along with the ID of the calendar item
that corresponds to this meeting request if
the meeting was not declined.
If the message was sent successfully, the
server returns an empty response as
specified in section 2.2.2.15.2. Otherwise,
the server responds with a Status element
(section 2.2.3.152.8) that indicates the type
of failure.
270 / 369
[MS-ASCMD] — v20110315
ActiveSync Command Reference Protocol Specification
Copyright © 2011 Microsoft Corporation.
Release: Tuesday, March 15, 2011