LstmeetingattendeeHistory
Allows meeting hosts or site administrators to request detailed attendee
information for any meeting session previously hosted on the site.
Note Host can only access the information of his or her own meeting
attendees, but site administrator can access the attendee information of
all the meetings previously hosted on his or her site.
Request
The following schema diagram shows the structure of the elements in thelstmeetingattendeeHistory request message.
Figure 9-5 • Schema diagram for lstmeetingattendeeHistory
The sample XML document lists detailed attendee information of
the meeting sessions hosted during the specified period of time.
<?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.history.LstmeetingattendeeHistory">
<startTimeScope>
<sessionStartTimeStart>03/28/2004 01:42:34
</sessionStartTimeStart>
<sessionStartTimeEnd>04/1/2004 02:42:34</sessionStartTimeEnd>
</startTimeScope>
<endTimeScope>
<sessionEndTimeStart>03/28/2004 00:42:34</sessionEndTimeStart>
<sessionEndTimeEnd>04/1/2004 02:42:34</sessionEndTimeEnd>
</endTimeScope>
<listControl>
<serv:startFrom>1</serv:startFrom>
<serv:maximumNum>10</serv:maximumNum>
<serv:listMethod>OR</serv:listMethod>
</listControl>
<order>
<orderBy>CONFID</orderBy>
<orderAD>ASC</orderAD>
</order>
<inclAudioOnly>TRUE</inclAudioOnly>
</bodyContent>
</body>
</serv:message>
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 History Service”.
Response
The following schema diagram shows the structure of the elements in thelstmeetingattendeeHistoryResponse message.
Figure 9-6 • Schema diagram for lstmeetingattendeeHistoryResponse
The sample XML document shows an example of a possible response to the
preceding request document.
<?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:history="http://www.webex.com/schemas/2002/06/service/history">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="history:LstmeetingattendeeHistoryResponse"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<history:meetingAttendeeHistory>
<history:meetingKey>94036066</history:meetingKey>
<history:confName>java schedule for XML</history:confName>
<history:ipAddress>172.16.244.151</history:ipAddress>
<history:clientAgent>WINDOWS,IE</history:clientAgent>
<history:name>java java</history:name>
<history:email>java@sz.com</history:email>
<history:joinTime>03/29/2004 02:42:34</history:joinTime>
<history:leaveTime>03/29/2004 02:49:31</history:leaveTime>
<history:duration>7</history:duration>
<history:participantType>ATTENDEE</history:participantType>
<history:voipDuration>0</history:voipDuration>
<history:confID>4702323</history:confID>
</history:meetingAttendeeHistory>
<history:matchingRecords>
<serv:total>1</serv:total>
<serv:returned>1</serv:returned>
<serv:startFrom>1</serv:startFrom>
</history:matchingRecords>
</serv:bodyContent>
</serv:body>
</serv:message>
The result and exceptionID global elements allow you to confirm that
an instantiation request was successful. They are described in "Global Response
Elements Showing Results and Errors”.