LstRecording
Allows users to see a list of all recordings within a certain date
range. Site Admin users can return the recording information for all
users on the site.
Request
The following schema diagram shows the structure of the elements in the lstRecording request message.
Figure 4-15 • Schema Diagram for lstRecording
The XML code below shows a sample request for recordings.
<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteName>sqdemo6</siteName>
<webExID>simon</webExID>
<password>P@ss1234</password>
<partnerID>webexpartner</partnerID>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.LstRecording">
<hostWebExID>auto243</hostWebExID>
<createTimeScope>
<createTimeStart>08/15/2018 8:0:0</createTimeStart>
<createTimeEnd>09/05/2018 7:59:59</createTimeEnd>
<timeZoneID>20</timeZoneID>
</createTimeScope>
<serviceTypes>
<serviceType>MeetingCenter</serviceType>
<serviceType>EventCenter</serviceType>
<serviceType>TrainingCenter</serviceType>
</serviceTypes>
<returnShareToMeRecording>true</returnShareToMeRecording>
</bodyContent>
</body>
</serv:message>
For descriptions of the global elements in the security context of the header, see Global Request Elements in Security Context.
For descriptions of the non-global elements, see Elements in the Event Session Service.
Response
The following schema diagram shows the structure of the elements in the lstRecordingResponse message.
Figure 4-16 • Schema Diagram for lstRecordingResponse
The XML code below shows a response to a lstRecording request such as the one above, and provides a list of recordings.
<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="ep:lstRecordingResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ep:matchingRecords>
<serv:total>2</serv:total>
<serv:returned>2</serv:returned>
<serv:startFrom>1</serv:startFrom>
</ep:matchingRecords>
<ep:recording>
<ep:recordingID>201127</ep:recordingID>
<ep:hostWebExID>auto243</ep:hostWebExID>
<ep:name>Auto Test243's Personal Room-20180831 0521-1</ep:name>
<ep:createTime>08/31/2018 06:03:17</ep:createTime>
<ep:timeZoneID>20</ep:timeZoneID>
<ep:size>27.704708</ep:size>
<ep:streamURL>https://sqdemo6.dmz.webex.com/sqdemo6/ldr.php?RCID=e12ffa3a8000d66d35b5bd844ee97d04</ep:streamURL>
<ep:fileURL>https://sqdemo6.dmz.webex.com/sqdemo6/lsr.php?RCID=be1b411e9eeaead8425b3ef30580dcfb</ep:fileURL>
<ep:recordingType>5</ep:recordingType>
<ep:duration>1106</ep:duration>
<ep:format>MP4</ep:format>
<ep:serviceType>MeetingCenter</ep:serviceType>
<ep:password>jTMNUvQ7</ep:password>
<ep:passwordReq>true</ep:passwordReq>
<ep:confID>104796956222555757</ep:confID>
<ep:shareToMe>false</ep:shareToMe>
</ep:recording>
<ep:recording>
<ep:recordingID>201257</ep:recordingID>
<ep:hostWebExID>auto243</ep:hostWebExID>
<ep:name>Auto Test243's Personal Room-20180831 0547-1</ep:name>
<ep:createTime>08/31/2018 06:26:00</ep:createTime>
<ep:timeZoneID>20</ep:timeZoneID>
<ep:size>37.968403</ep:size>
<ep:streamURL>https://sqdemo6.dmz.webex.com/sqdemo6/ldr.php?RCID=9f8482d9986775fd3452a625c97eb7fb</ep:streamURL>
<ep:fileURL>https://sqdemo6.dmz.webex.com/sqdemo6/lsr.php?RCID=c1f1dc84dfb1086523627277c07e9286</ep:fileURL>
<ep:recordingType>5</ep:recordingType>
<ep:duration>1385</ep:duration>
<ep:format>MP4</ep:format>
<ep:serviceType>MeetingCenter</ep:serviceType>
<ep:password>PbjjVxp2</ep:password>
<ep:passwordReq>true</ep:passwordReq>
<ep:confID>104842388980106331</ep:confID>
<ep:shareToMe>false</ep:shareToMe>
</ep:recording>
</serv:bodyContent>
</serv:body>
</serv:message>