Invalid request on unconfigured participant

[Diego Requena González]

I got this error recently in Janus service:

[ERR] [plugins/janus_videoroom.c:janus_videoroom_handler:4627] Invalid request on unconfigured participant

Any advice?

Never happened until I updated to 0.3.1 and I don't know if it is something related with session, handles and/or participant id timeouts or something like that. I store them in my database to reuse them if user reconnects to the videoroom.

Best regards.

D.

[Lorenzo Miniero]

Your first asynchronous request was not "join" or "joinandconfigure", which is an error.

L.

[Diego Requena González]

Sorry, I forgot to mention that it also runs this block of code in the client JS:

https://github.com/meetecho/janus-gateway/blob/master/html/videoroomtest.js#L235-L246

My rooms are supposed to be automatically closed by my APP when they reach 1 hour duration. Did you add any timeouts to videorooms? If that's the case, I need them to be created "forever", then my APP can handle where my rooms are getting closed.

Best regards.

D.

[Diego Requena González]

As far as I now, the first thing that my client JS does is a "join" request. I took the videoroomtest.js example.

[Lorenzo Miniero]

The error you're getting has nothing to do with room creation, and we have no timeouts there. It's an error you get when you send a user request (so not a "create", "destroy" or other synchronous requests) before joining and assigning the user a role. This is an error and your logic is broken somewhere.

L. 

[Diego Requena González]

Okay. Thanks for your time.

I will take a look to my logic as this error did not happen until I updated Janus, so probably in my older Janus version it was "less strict" and ignored the error or w/e, as it never happened before. Also, is kinda weird that it throws a "No such room" error together with a request error. It will be a hard job to find why it is throwing both errors together.

Best regards.

D.

[Diego Requena González]

To be honest, I cannot find the error. Although, It only happens sometimes and when the user is in the videoroom for about 15-30 minutes or so. It's really hard to debug it as it happens randomly, not always.

I also have fixed an error in this block of code (https://github.com/meetecho/janus-gateway/blob/master/html/videoroomtest.js#L601-L614) as it is called twice when a remote user joins in. For example, when a user refreshes the page, the first interval call (which was supposed to be overriden with the second one) is still working somehow. To fix this, I've added both intervals into an array of interval timers, then cleaned all intervals for that handle in the cleanup notification function. It is a surprise that it does not throw an "Invalid handle" error in your demos, but it does in my app, as it basically uses the same function, with some aggregations that does not interfere with the videoroom JS nor the Janus JS.

I will keep an eye on the logs and try to find if there is an error in my logic. I'll keep you updated.

Best regards.

D.

On Monday, 7 May 2018 17:39:24 UTC+2, Lorenzo Miniero wrote:

[Lorenzo Miniero]

Sounds like an issue with refreshes. That block of code cannot be called twice, as we have an addButtons boolean exactly for that. It's likely that the issues you're experiencing come from the same root: there's a refresh, users keep on sending messages as if they were connected, while they really weren't (they just reconnected), hence the error.

L.

[Diego Requena González]

I will take a look to all functions ASAP. We have another project and we are running out of time, so this is not a true problem for now.

As always, thanks for your time and your guides! :)

Best regards.

D.