SetMeeting

SetMeeting enables hosts to update the information for a scheduled meeting that they are able to edit.

Users can set meetings up to have end-to-end encryption (E2EE) using the supportE2E element. If E2EE is enabled, the networkBasedRecording, joinBeforeHost, and remoteComputer sharing features are automatically disabled.

SetMeeting also enables users to determine whether or not attendees can join the teleconference before the host does. This functionality is part of the schedule element and controlled by the joinTeleconfBeforeHost element. It provides support for:

Cisco Unified MeetingPlace audio conferencing.
Join Before Host Telephony for TSP and MP audio conferencing sessions.

Users can set up automatic recording of meetings as they are created using the autoRecord element. This element governs whether a meeting is automatically recorded if Automatically record all sessions using Network-Based Recording is not enabled (checked) on the Site Admin page. If the latter is enabled, it overrides autoRecord.

The result and exceptionID global elements confirm whether an instantiation request was successful. These elements are described in Global Response Elements Showing Results and Errors.

Note

When updating a meeting, SetMeeting ignores the emailInvitations and status elements because it does not send out any email messages nor change the status of the meeting.

For descriptions of the global elements in the security context of the header, please see Global Request Elements in Security Context.
For descriptions of the non-global elements, please refer to [Elements in WebEx XML Schema Definitions for the Meeting Service](_05-12

Request

The following schema diagram shows the structure of the elements in a setMeeting request message.

Schema Diagram for setMeeting

The XML code below shows a sample request to update a meeting with a key identification, or meetingkey, value of 48591508.

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <header>
        <securityContext>
            <webExID>hostid</webExID>
            <password>hostpassword</password>
            <siteID>0000</siteID>
            <partnerID>9999</partnerID>
            <email>johnsmith@xyz.com</email>
        </securityContext>
    </header>
    <body>
        <bodyContent
            xsi:type="java:com.webex.service.binding.meeting.SetMeeting">
            <metaData>
                <confName>test meeting.SetMeeting</confName>
                <meetingType>1</meetingType>
                <agenda>Test</agenda>
            </metaData>
            <participants>
                <maxUserNumber>4</maxUserNumber>
                <attendees></attendees>
            </participants>
            <enableOptions>
                <chat>false</chat>
                <poll>true</poll>
                <audioVideo>true</audioVideo>
                <supportE2E>TRUE</supportE2E>
                <autoRecord>TRUE</autoRecord>
            </enableOptions>
            <schedule>
                <startDate>06/01/2004 23:06:27</startDate>
                <duration>60</duration>
                <timeZone>GMT-05:00, S. America Pacific (Bogota)</timeZone>
                <joinTeleconfBeforeHost>TRUE</joinTeleconfBeforeHost>
            </schedule>
            <telephony>
                <numPhoneLines>0</numPhoneLines>
                <telephonySupport>NONE</telephonySupport>
            </telephony>
            <remind>
                <enableReminder>true</enableReminder>
                <emails>
                    <email>user@user.com</email>
                </emails>
            </remind>
            <attendeeOptions>
                <auto>true</auto>
            </attendeeOptions>
            <meetingkey>48591508</meetingkey>
        </bodyContent>
    </body>
</serv:message>

Response

The following schema diagram shows the structure of the elements in a setMeetingResponse message.

Schema Diagram for setMeetingResponse

The XML code below shows a possible response to a setMeeting request such as the one above, changing an existing meeting service instance.

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service"
    xmlns:com="http://www.webex.com/schemas/2002/06/common"
    xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting"
    xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="meet:setMeetingResponse"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <meet:iCalendarURL>
                <serv:host>https://www.webex.com/calendarurl1/j.php?ED=48591508&U
                    ID=BA24987F&ICS=MIFH&ST=12
                </serv:host>
                <serv:attendee>https://www.webex.com/calendarurl1/j.php?ED=485915
                    08&UID=BA24987F&ICS=MIFA&ST=12
                </serv:attendee>
            </meet:iCalendarURL>
        </serv:bodyContent>
    </serv:body>
</serv:message>