The information given below explains the recording function on weConnect, what is supported/recorded and what are the boundaries of the system.

Requirements

The location should have:

• one main node
• exactly one camera manager node that has a teacher camera WITH audio configured (other camera manager nodes are not recorded)
• a valid configuration, either set on the room level directly or higher in the location hierarchy

Limitations

The recording of the primary source (camera manager node) includes the following streams:

• teacher camera+ teacher voice
• remote participants voice and remote hosts voice: by default if Digital audio mixing is enabled.
   
  Note: if Digital audio mixing is disabled, the DSP needs to get the audio from all remote participants and hosts, make a mix of it and feed that mix into the camera manager node (Audio IN: Loopthrough)!

The recording of the secondary source (main node) includes the following stream:

• shared content video + audio

Recordings will be split off in sessions, if the file size exceeds 4GB or if the duration exceeds 2 hours.

Supported recording services

Possible configurations that can be set in the Location settings tab under Locations: Panopto, Kaltura, and SCP.

If Panopto is used, SCP can be set as a backup mechanism. This is not working if upload Kaltura cannot be initiated, like if configuration is wrong. (NET0004-4415).

Credentials are validated from a random node in the room when applying new settings from the admin UI. It is the camera manager node that does the actual upload of the video files.

Supported formats

Panopto: supports the broadest range of video file formats, including AVI, MP4, MPG, WMV, MOV, QT, ASF, 3GP, WMA, MP3, M4V, and more.

Kaltura: supports .flv, . asf, . qt

SCP: mp4

Recording procedure

weConnect records a video/audio file from an active lecture in one way/format and we upload the file in different ways/formats. The format that is used for recording in weConnect is MP4 by default. This is a 'drawback' as MP4s are worthless when not properly finished. However, another format can be a good replacement such as .mkv.

Files recorded during a weConnect session are therefore uploaded using the following Cloud and local mechanisms. 

Configuration procedure

Panopto

Step 1: Create and configure an API client (if none are configured)

• Go to your Panopto cloud admin interface and log in: https://[institute].cloud.panopto.eu/panopto
• Click System > API-clients > New
• Fill in the following values on the form:
  • Client Name, e.g. weConnect integration
  • Client URL: client website (optional)
  • Client Type: Server-side Web Application
  • CORS origin URL: customer site or cloud address, e.g. https://edu.barco.com/
  • Redirect URL CORS: https://[institute site]/_panopto/verify , e.g. https://edu.barco.com/_panopto/verify (or cloud address can be used)
• Click Create API Client
• Note down the Client ID and Client Secret

Step 2: configure the weConnect admin UI

• Go to the admin UI of your institute
• Fill in the following values in the form:
  • Upload service: Panopto
  • URL: e.g. https://[your].cloud.panopto.eu/
  • API Client ID
  • API Client Secret
  • Default Folder ID: the ID from a Panopto folder
    The ID can be obtained by opening the desired folder location's Settings menu and selecting the Manage tab
• Click Save
• Log in to Panopto if asked for
• Start a lecture and click Start recording in the teacher user interface for a real test. 

Kaltura

Step 1: Get Kaltura API credentials

• Login to your Kaltura Management Console (KMC)
• Go to Integration Settings to find the necessary credentials

Step 2: configure the weConnect admin UI

• Upload service: Kaltura
• URL: https://kmc.kaltura.com
• User email: (optional if Account Type is Admin)
• User/Administrator Secret: available in KMC
• Account Type: [User, Admin]
• Partner ID: available in KMC
• Click Save
• Log in to Kaltura if asked for
• Start a lecture and click Start recording in the teacher user interface for a real test. 

SCP

Step 1: Set up a device with enough storage, which would allow ssh connections from weConnect devices

Step 2: configure the weConnect user interface

• Upload service: SCP
• URL: scp://[IP address e.g. 192.168.1.2]/path/to/folder
• Username
• Password

Since v3.15.2, you should be able to use the DNS name instead of the IP address if you prefer ?. (NET0004-6610)