Thanks a lot for your participation in the Recording private beta! We've found and eliminated a bunch of bugs thanks to your help, and we're excited to announce that Recording is now in Public Beta, meaning all LCCS users can try it out.
In the course of fixing bugs, we were forced to make some changes to the service - this means that NEW RECORDINGS WON'T WORK unless you update your client SDKs. While we're extremely cautious about backwards-compatibility for features that are out of beta, in this case we had to reserve the right to make changes before we come out of beta. Playback of existing recordings should be unaffected by this change. Please refer to our Recording sample app to get started (located inside the SDK folder). There is also a HowTo document attached to this posting.
We have one final round of work to do before we can declare Recording production-ready. This will be adding authentication to your recordings, as well as metering, quota management, and billing for those recordings. This will likely mean another set of changes to the service that may introduce compatibility issues, so please be aware of this up front, and thanks again for all the support.
Description: Registers a recording repository for the account by specifying a repository endpoint URL to use for storing and retrieving meeting recordings. The optional securityTokenparameter is currently unused.
repositoryEndpoint, the URL to the developer provided recording repository server to which LCCS should store meeting recordings
Yes, registering an archive repository endpoint with lccs.php should be possible. First thing is to ensure you have the most recent lccs.php which came with our latest SDK release. Are you running into any particular problem?