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
It will be common to have migrations from either bbb-lti (or other custom applications such as bn-konekti or mconf-rooms), for which the LTI link needs to be the same (therfore thr resource_link_id is the same) although the meetingID produced is different.
One way to accomplish this is by adding a legacy_handler column to the room table. And using it as part of the gerRecordings request.
The text was updated successfully, but these errors were encountered:
jfederico
changed the title
include recordings produced by legacy LTI applications
Include recordings produced by legacy LTI applications
Nov 13, 2021
It will be common to have migrations from either bbb-lti (or other custom applications such as bn-konekti or mconf-rooms), for which the LTI link needs to be the same (therfore thr resource_link_id is the same) although the meetingID produced is different.
One way to accomplish this is by adding a
legacy_handler
column to the room table. And using it as part of the gerRecordings request.The text was updated successfully, but these errors were encountered: