cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2430
Views
2
Helpful
7
Replies

Recordings Not Appearing

We have nearly hit our 50GB capacity for storage.  Since there isn't a UI for managing this, we are using the APIs.

We have previously used the APIs successfully with the exact same script to retrieve a list of recordings, who they belong to and their size etc.

As of now, we are only able to return 44 recordings with a total of around 4GB in capacity.

Does anyone know what has changed to cause this issue?

We're using POST to https://oursitename.webex.com/WBXService/XMLService


<?xml version="1.0" encoding="UTF-8"?>

<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">

<header>

  <securityContext>

    <webExID>username</webExID>

    <password>password</password>

    <siteID>siteid</siteID>

  </securityContext>

</header>

<body>

  <bodyContent xsi:type="java:com.webex.service.binding.ep.LstRecording">

    <listControl>

      <startFrom>0</startFrom>

      <maximumNum>500</maximumNum>

    </listControl>

  </bodyContent>

</body>

</serv:message>

Headers are:

Accept:application/soap+xml,application/dime,multipart/related,text/*

Content-Type:text/xml;charset=utf-8

SOAPAction:""

Many thanks,

D.

1 Accepted Solution

Accepted Solutions

Hello,

     There was a recent change to XML API to improve database performance. As a result, LstRecording results are limited to a 4 week timeframe. To retrieve results for LstRecording, you will need to specify a <= 4 week timeframe that overlaps the creation time of the recordings, using createTimeScope and its children createTimeStart and createTimeEnd. The cause of missing values for getNBRConfIdList has not yet been identified.

View solution in original post

7 Replies 7

I'm also getting none listed using getNBRConfIdList either.  Just the following:

<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

    <soapenv:Body>

        <ns1:getNBRConfIdListResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="nbrXmlService">

            <getNBRConfIdListReturn href="#id0"/>

        </ns1:getNBRConfIdListResponse>

        <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:Document" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="nbrXmlService">

            <NBRConfIDList/>

        </multiRef>

    </soapenv:Body>

</soapenv:Envelope>

nmorrow
Cisco Employee
Cisco Employee

Hello,

     LstRecording is the better method for retrieving a list of NBR recordings on the site. If you authenticate as a host, you will only retrieve recordings belonging to that host user. Authenticating as a site admin or read-only site admin will allow you to see results from all users on the site. If you have other files stored on WebEx, such as uploaded presentations or downloaded and then reuploaded recordings (this changes their format), they would not be visible in LstRecording. Also note that XML API does not use SOAP, so SOAPAction would not be a necessary header value, NBR API does use SOAP.

     If you can provide your WebEx site URL, further investigation can be performed. If you do not want to provide it publicly, you may send your question and site URL to webex-meetings-api-dev@cisco.com.

There may be some sort of issue retrieving all recordings at this time, engineering is investigating a related issue. I would still recommend providing your WebEx site URL for further investigation and to confirm this issue affects your site, and that it is resolved when resolution is reached.

Hello,

     There was a recent change to XML API to improve database performance. As a result, LstRecording results are limited to a 4 week timeframe. To retrieve results for LstRecording, you will need to specify a <= 4 week timeframe that overlaps the creation time of the recordings, using createTimeScope and its children createTimeStart and createTimeEnd. The cause of missing values for getNBRConfIdList has not yet been identified.

Oh! Well that would explain it.  Thanks.

Is there any way I can determine the oldest recording so that I might at least know where to start from? Also, I can no longer rely the total returned to identify how many recordings I'm looking for either?

As it is, I might need to start from 2007 and try every four weeks since then just to get a full list.  I can't use an empty set to determine this since there could be a 4 week window where there were no recordings.

This is really bad!  Are there any other ways I should be managing this?  It seems crazy that there isn't a UI at least to manage storage?

Thanks again for your feedback.

Kind regards,

D.

I could suggest pushing a feature request through your WebEx account manager to add some sort of Site Admin UI mechanism to batch download recordings. Engineering is considering a change to this update that will allow a 1 year search window for sites with less than a currently undefined maximum value of recordings, this could tentatively be implemented during Q1 calendar year 2018.

Sorry, I forgot to update you on the NBR API missing data, that was due to a site configuration being disabled, getNBRConfIdList is intended to be used with getMeetingXml, which retrieves a chat transcript of the meeting. Engineering's official stance is that LstRecording should be used for to retrieve record ID for downloading.