You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using a little cluster of BBB backend and a scalelite load balancer. We have configured to backend to record all possible sources (presentation, audio, video, screenshare, notes) by installing the corresponding plugins.
It seems that the API between the server side and the web client only supports a single link; in case of our setup we need a list of links for the different types. The thumbnails are also broken in most cases, since they also only refer to the first link without taking its format into account.
The text was updated successfully, but these errors were encountered:
Indeed, in our setup the Podcast is always the first recording returened and therefore will be linked here. I created a fix which displays different types. I can create a pull request if you would like to.
Our setup is also not a simple BBB, but a scalelite load balancer and several BBB endpoints. The API requests to retrieve the recordings are sent to scalelite; maybe the API or the scalelite collector uses a different order in the underlying XML file.
We are using a little cluster of BBB backend and a scalelite load balancer. We have configured to backend to record all possible sources (presentation, audio, video, screenshare, notes) by installing the corresponding plugins.
The plugin works in this setup, but only uses the first available format. In most cases this is not the expected one (see https://github.com/blindsidenetworks/mattermost-plugin-bigbluebutton/blob/master/server/responsehandlers.go#L544).
It seems that the API between the server side and the web client only supports a single link; in case of our setup we need a list of links for the different types. The thumbnails are also broken in most cases, since they also only refer to the first link without taking its format into account.
The text was updated successfully, but these errors were encountered: