LstmeetingattendeeHistory fails

[uvsity_webex]

I created a meeting with following details

Time Zone :GMT+05:30, India (Bombay)

Start Time:02/01/2015 12:41:11

Then the host and the attendee joined the meeting with meeting key=625161648

After the end of meeting I use LstmeetingattendeeHistory XML service to fetch the attendee details.

I use

<startTimeScope>

<sessionStartTimeStart>02/01/2015 00:00:11</sessionStartTimeStart>

<sessionStartTimeEnd>02/01/2015 20:15:11</sessionStartTimeEnd>

</startTimeScope>

<endTimeScope>

<sessionEndTimeStart>02/01/2015 00:00:11</sessionEndTimeStart>

<sessionEndTimeEnd>02/01/2015 20:15:11</sessionEndTimeEnd>

</endTimeScope>

The service fails and shows the following response

<?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>FAILURE</serv:result><serv:reason>Sorry, no record found</serv:reason><serv:gsbStatus>PRIMARY</serv:gsbStatus><serv:exceptionID>000015</serv:exceptionID></serv:response></serv:header><serv:body><serv:bodyContent/></serv:body></serv:message>

I started the meeting using GMT+5:30 so I searched the meeting with GMT 00:00:11 to 20:15:11 but still it fails.

Can you please shade some light?

Thanks

[uvsity_webex]

I used the following date range

<startTimeScope>

<sessionStartTimeStart>01/01/2015 00:00:11</sessionStartTimeStart>

<sessionStartTimeEnd>02/01/2015 20:15:11</sessionStartTimeEnd>

</startTimeScope>

<endTimeScope>

<sessionEndTimeStart>02/01/2015 00:00:11</sessionEndTimeStart>

<sessionEndTimeEnd>02/01/2015 20:15:11</sessionEndTimeEnd>

</endTimeScope>

It pulled in a old meeting but still my 2/1 meeting is not listed.Can you please let me understand if I'm missing anything?

Thanks,

Shalav

[nmorrow]

Hello,

     History service has a small delay of up to 72 hours before data is available. This allows the report database to gather all related details of the session. You should also look at using either sessionEndTime OR sessionStart time for filtering, and not both. Using both could prevent some results being shown if they start during the timespan, but end after (or start before and end during), as both filtering options would need to be met.