ModifyMeetingRequest Element

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Modifies a meeting by sending a request to a conference center.

Syntax

<ModifyMeetingRequest
    newMid = "True" | "False">
    <StringQuery...></StringQuery>
    ...
    <FieldList>...</FieldList>
</ModifyMeetingRequest>

The following sections describe attributes, parent elements, and child elements.

Attributes

Element Information

Parent Element

Child Elements

Remarks

The StringQuery must match exactly one non-deleted meeting. The StringQuery element can query for values of the following options:

• mid

• name

• opaque1

• opaque2

• personalPlaceOf

At least one of the OptionListor RemoveListchild elements must be present.

The RemoveList element can contain any of the follow options:

• audienceACL

• audienceCustomFrameURL

• audienceList

• audienceListEmail

• audiencePassword

• billing

• endTime

• infoA

• infoP

• locale

• opaque1

• opaque2

• presenterACL

• presenterCustomFrameURL

• presenterList

• presenterListEmail

• presenterPassword

• recordingPhone

The OptionList can contain options corresponding to all the attributes and options specified in CreateMeetingRequest with the exception of tag and tagID, which cannot be changed through a ModifyMeeting request. If the requestor is an administrator, the OptionList element can also contain the owner option, in which case the owner of the meeting is changed to the value of the owner option. The value of the owner option must be the user ID of an organizer.

The enableAudioVOIP, enablePersonalRecordingAttendee, and enablePersonalRecordingPresenter options have been added to this element in Live Meeting service API Update for Live Meeting 2007. For more information about these options, see the CreateMeetingRequest and CreateUserRequest elements.

A conference center can be configured to permit only users in the Administrator role to set or change the billing option. When this is True, the request to change this option for a meeting is ignored and no fault message returns in the reply. When this is False, any Administrator or the owner of the meeting can change this option. You can request a change of this setting through the normal sales channel for your organization.

Removing the endTime option converts a meeting to an ongoing meeting.

Any uploaded slide sets and recordings for this meeting are not affected by this operation.

The FieldList child element can contain any option that can be returned in a MeetingReply element. This is the list of options you want to be returned in the reply to this modify request. It is recommended that you always include presenterPassword or audiencePassword in the FieldList if these options are being changed by the request.

Changing Owner

Including the ownerStringOption in the ModifyMeetingRequest reassigns the ownership of the meeting and its contents to the new owner. To use the owner option, the calling user must be an Administrator in the conference center.

The following code describes an example request.

<PlaceWareConfCenter authUser="apiuser" authPassword="Pa$$w0rd">
    <ModifyMeetingRequest>
         <StringQuery fieldName="name" operator="=" value="salesdemo1"/>
            <OptionList>
                    <StringOption name="owner" value="john" />
            </OptionList>
            <FieldList>
                    <Name>name</Name>
                    <Name>owner</Name>
            </FieldList>
    </ModifyMeetingRequest>
</PlaceWareConfCenter>

The following shows the reply returned from the conference center.

<PlaceWareConfCenter>
    <ModifyMeetingReply>
      <MeetingReply>
        <OptionList>
          <StringOption value="salesdemo1" name="name"></StringOption>
          <StringOption value="john" name="owner"></StringOption>
        </OptionList>
      </MeetingReply>
    </ModifyMeetingReply>
</PlaceWareConfCenter>

Fault Codes

The Client.BadMatch.Need1Got0.Meeting FaultCode is returned if the StringQuery does not match any existing meeting (for example, the meeting never existed, the meeting is deleted, or there is a typing mistake in the meeting name).

The Client.BadData.NoSuch.UserOrGroup.User FaultCode is returned when the new owner specified is not a valid user in the conference center, when one of the users specified in the audienceACL or in the presenterACL option does not exist, or when all the users specified in the audienceACL or in the presenterACL option do not exist and the partialSuccessOK attribute was set to True when the meeting was first created.

The Client.Authorization.NotOrganizer FaultCode is returned if the user is not an Organizer or Administrator.

See Also

Concepts

ModifyMeetingReply Element

ModifyMeeting Message

CreateMeetingRequest Element