We can configure automatic archival feature in the mediasense. So, recordings meeting the specified archival criteria would be archived at specified locations.
So, how our application would be notified that particular recording has been archived or not. For example, Mediasense archived recording 'A'. After that our application query to mediasense to fetch recording 'A' (for example with sessionId) then which parameter in recording metadata sent back as a response would define recording's current state?
According to my current understanding, it always sends 'CLOSED_NORMAL' irrespective of either recording has been archived or not. So, how may we actually decide recording's current state?
P.S. I want to avoid manual check at our application side to check with same criteria that we mentioned in mediasense archival configuration.
There is no option to check that which recording is archived. There is no parameter in response from which you can identify that this recording is archived or not.
Also the state 'CLOSED_NORMAL' is state of recording which tells that this recording is recorded successfully.
JSON of archived recording is saved on SFTP server. When we search for archived recordings on search and play , it take JSON from SFTP server, parse it and then show recordings on search and play page.
Thanks for the all the clarifications.
So, mediasense can't help us on recordings distinction based upon it's current state.
anilve can you please note this point for future mediasense release to include this as a new feature that when a recording is archived by mediasense, subscribed application should get the notification.
We need clarification on one more point. When mediasense archives the recording into SFTP server then it still remains accessible in mediasense to play? A recording has been archived but it still can be played directly from mediasense with mp4Url.
The archival process is separate from the pruning process.
Archival send a copy of the recording to the secure FTP site.
Pruning removes the recordings from the MediaSense server.
So it is entirely possible that a recording can be archived but also available on the MediaSense server.
If the recording is archived but pruned from the MediaSense server, then the only way to play it back is finding the session using the search for archive recordings and using that play archive session API call to play it back. The MP4URL will work, but is is actually copying the file over to the MediaSense server and playing it back. So it can be slower than the playback of a file that is already on the box.