0

Calling opentok.startArchive for two requests of mine. Both have valid room name values which are given for this method. Thus, I do not think that it is because of my request.

One error indicates that "Unexpected response from OpenTok", another error in the successful part. Not sure what specifically the problem is. JSON.stringify(err) gives me that much details. Any ideas how I can dig in? 

router.post('/startArchive', function (req, res, next) {

......
........
}).then(function (sessionId) { 
  console.log("#start_archive")
  opentok.startArchive(sessionId, {
    name: roomName,
    outputMode: "individual" //composed
}, function (err, archive) {
  if (err) {
    console.log("opentok error")
    res.json(err);
    res.end();
    return console.log(JSON.stringify(err));
  }
  else{
    /*SUCCESSFULL*/
  }
});
shamaleyte
  • 1,882
  • 3
  • 21
  • 38

1 Answers1

0

There are two major things to start an archive:

You can also check the validity of your account. Perhaps it's inactive?

Lucas Huang
  • 3,998
  • 3
  • 20
  • 29
  • My account is active and it works fine when I open a new session for my conference. The question would be to ask if it is right approach to generate new session for each conference? OR Should I use a static session id per person, and use it each time he opens a conference? What do you suggest? – shamaleyte May 03 '17 at 20:59
  • I have exactly the same problem while using the outputMode: 'individual' My session are routed and there is one connection. Working with `composed` but when i put `outputMode: 'individual'`, i reproduce the same crash as @shamaleyte – foufrix Apr 15 '20 at 10:09