Common Archiving Mistakes

The OpenTok archiving guide can be found here: https://tokbox.com/developer/guides/archiving/

This article is intended to help you avoid some common mistakes.

Attempting to initiate archiving of a session that is already being archived will result in an HTTP 400 level status from the REST API call that is used to start the archive or the start_archive call issued from a Server SDK. To avoid this, register a callback URL in your TokBox Account and check the status of the archiveId to determine if the archive was successfully started.  

Attempting to start archiving of a Relayed session will result in an HTTP 400 level status from the REST API call that is used to start the archive or the start_archive call issued from a Server SDK. To avoid this, make sure you create Routed sessions if you wish to archive a session.

Attempting to start archiving a session before the session has any connections will result in an HTTP 400 level status from the REST API call that is used to start the archive or the start_archive call issued from a Server SDK and it will fail to create an archive. To avoid this, sessions can be set for automatic archiving when the session is created. Alternatively, make sure at least one client has connected to the session before attempting to start archiving.

Attempting to start archiving a session using an API key and secret that is different than the key and secret that were used to generate the session ID will result in an HTTP 400 level status from the REST API call that is used to start the archive or the start_archive call issued from a Server SDK and it will fail to create an archive. To avoid this, make sure to use the same credentials for all REST, Server SDK, and token generation actions related to a project.

 

Have more questions? Submit a request