Local Recording is handled completely locally in the host's browser and browser cache.
Our Local Recording feature has not been built specifically for Embedded solutions, and as such is limited in functionality. We recommend that this isn't used in a live production environment without significant internal testing. Recordings are only created and stored locally. Whereby cannot recover any lost or corrupted recordings.
With the Recording feature you'll need to ensure that several different conditions are met so your room hosts are able to see and use the feature.
- 1.You're generating and the host is using a
- Only a room host will be able to Record in the room so you need to provide this type of link to the host.
- When generating this be sure to note that a
hostUrlis only valid between the meeting creation and
endDatethat you set during your request. These times are in UTC and not your local time zone, unless a timezone was specified in the request.
- 3.You've enabled Local Recording from the “Configure” → “Recording” section of your dashboard and are using
?recording=onin your room URLs. Or you've set the recording type to
localduring the API request.
- 4.Your hosts are selecting only the tab your meeting is embedded on. If users select the entire screen or app window it can cause files to be corrupted and unable to be downloaded.