MediaSense v8.5(2) is now available with the following API Changes for version 8.5(2)
-Sessionids that were deleted or pruned are now grouped and sent as a batch.
-Event subscription has been enhanced to provide categories of events to subscribe to.
-URL timeout parameter added to download of recordings.
For additional information see the release notes
8.5(2) release notes
In general, Cisco MediaSense¿s Web 2.0 API set is considered to be forward compatible¿any enhancement or modification to the API does not impact the operation of any existing client. However, for performance reasons, a list of sessionids that were deleted or pruned are now grouped and sent as a batch, rather than as a series of individual events. The sessionIds parameter contains an array of sessions that have been deleted or pruned. Caution Client may need to modify the client code based on this change.4 Release Notes for Cisco MediaSense, Release 8.5(2) New and Changed Information Note Other session event actions, such as STARTED, UPDATED, and ENDED, still use the scalar sessionId field.
API Requests In Release 8.5(1), each client had only one event subscription, and could not specify the events. In Release 8.5(2), while a client continues to have only one subscription, the client can specify specific details on the kinds of events it wants to receive. Events are divided into the following categories: ¿ RECORDING_EVENTS (real-time recording session activities) ¿ CLEANUP_EVENTS (indicate which recording sessions are pruned or deleted) ¿ TAG_EVENTS (refer to session tagging activities) ¿ STORAGE_EVENTS (announce the crossing of storage space thresholds). Clients can subscribe to any or all event categories, to specific event types, or any combination of events. This can happen if a newer version of Cisco MediaSense (which defines additional event types within an existing category) is installed.
The following new API requests have been implemented:
1. subscribeToEvents¿similar to the original subscribeRecordingEvents, except for the additional subscriptionFilters parameter (allows clients to receive confirmation on the subscribed filters). A slight difference in the return code behavior indicates that it is no longer considered an error to re-subscribe. Re-subscription elicits a response code of 2006 (subscription updated) if the resulting list of filters has changed, or 2005 (already subscribed) if the action does not result in a changed list of filters.
2. unsubscribeFromEvents¿similar to unsubscribeRecordingEvents, except that as with subscribeRecordingEvents (allows clients to specify a list of event categories or types).
3. verifyEventSubscription¿similar to verifyRecordingEvents (allows clients to specify a list of event categories or types). Note The older API requests (subscribeRecordingEvent, unsubscribeRecordingEvent, and verifyRecordingSubscription) have been deprecated for future use, but will continue to function as before.
4. getSystemTime API¿returns the current system time in GMT. As all Cisco MediaSense servers are configured to a common NTP time source. The differences between their system clocks is not significant and consequently returns only one system time value.
5. deleteSessionTag API¿deletes a specified session tag.
Raw File Download
Cisco MediaSense 8.5(2) allows clients to download individual recordings using HTTP. The appropriate URL for each track in each session was provided in the downloadUrl parameter. Previously, clients used this URL directly, without modification. As of Release 8.5(2), clients can add the URL timeout parameter, if the network or the client is slow to consume the downloaded file. Cisco MediaSense automatically closes the TCP connection and aborts the download if it is unable to write data into the socket within the specified seconds. See the Playing Back Recordings section in the Developer Guide for Cisco MediaSense, Release 8.5(2) at http://developer.cisco.com/web/mediasense/docs.Release Notes