Kaltura Meetings Integration Guide

Kaltura Meetings, via the acquisition of Newrow, allows for live video collaboration tools, such as classrooms, events, and webinars, to be built directly into your applications, using components of the Kaltura API.

This guide will walk you through the steps of creating a virtual meeting room URL, which you can embed into your webpage with an iFrame.

Before You Begin

To use the Kaltura API, you'll need a Kaltura account and credentials. The important credentials can be found in the Integration Settings in your KMC.

You might want to download a Kaltura Client Library of your choice, although you can also use the developer console for all the operations mentioned below.

This integration will be using your KAF endpoint, which should contain your Partner ID. If you're not sure whether you have a KAF endpoint or whether "Newrow" has been enabled on your account, speak to your account rep or email us at vpaas@kaltura.com.

Overview

A virtual meeting room is represented as a KalturaLocationScheduleResource. A scheduled session is represented by a KalturaRecordScheduleEvent. One resource can be used for many different events, but an event will only be associated with one resource. The room will be launched using an embed link that is made up of a Kaltura Session with specific configurations, all of which will be discussed below.

Creating an Admin Session

A Kaltura Session is an identification string that authorizes calls to the Kaltura API. You'll need one to create the resource and event objects. If you're logged into the developer portal, you're already authenticated. However, if you're calling the Kaltura API using a client library, you'll need to create the string yourself using the session.start API.

You can find the necessary credentials in your KMC Integration Settings. You'll use your ADMIN Secret for this operation.

Example

  $secret = "xxxxx"
  $userId = "your-email-address";
  $type = KalturaSessionType::ADMIN;
  $partnerId = 1234567;
  $expiry = 86400;

You'll set this KS on the Client that handles all the operations detailed below.

Creating a Resource

A schedule resource is created using the scheduleResource.add action, which will return a KalturaLocationScheduleResource object. The resource must have a name, and it should include tags of vcprovider:newrow in order to be recognized as a virtual meeting room.

Once created, the response will return an id, which you should hold on to. However, if you've lost track of it - no worries. You can see all of your scheduled resources by calling scheduleResource.list.

Note that you should be using an ADMIN Kaltura Session for this creation.

Required Parameters

name: (string) room name
tags: vcprovider:newrow

Optional Parameters

systemName: (string)
description: (string)

Example

    $schedulePlugin = KalturaScheduleClientPlugin::get($client);
    $scheduleResource = new KalturaLocationScheduleResource();
    $scheduleResource->description = "My first meeting room";
    $scheduleResource->name = "Room-1";
    $scheduleResource->tags = "vcprovider:newrow";

    $result = $schedulePlugin->scheduleResource->add($scheduleResource);

Response Object

{
  "id": 1100601,
  "partnerId": 1234567,
  "name": "Room-1",
  "description": "My first meeting room",
  "status": 2,
  "tags": "vcprovider:newrow",
  "createdAt": 1586100234,
  "updatedAt": 1586100234,
  "objectType": "KalturaLocationScheduleResource"
}

Creating an Event

You'll use the scheduleEvent.add action to create an event of type KalturaRecordScheduleEvent. This action must include a summary, startDate and endDate, and a recurrence type of NONE.

Required Parameters

startDate: (int) timestamp
endDate: (int) timestamp
recurrenceType: NONE [0]
summary: (string) event summary

Optional Parameters

organizer: (string) name of the organizer (string)
templateEntryId: (string) the entry used for session recording
ownerId: (int) in the case that templateEntryId is empty, this user will now own the recording
referenceId: (string) third party's corresponding event ID
location: (string) geographical location of the event
tags: (string) see below

The creation of the event will return an id. Hold on to that as well. And once again, if you've lost track of it, you can use scheduleEvent.list to see all of your created events.

Tags / Event Settings

An event can also include room settings, such as auto-recording, by passing tags as comma-separated key-value-pairs. Tags are optional, and can also be set on the resource. Note that any settings on the event will override those of the resource when using the event ID to join the room.

Key	Type	Default	Other
custom_rec_auto_start	boolean	off: Auto-start recording is disabled	on: Start recording automatically when instructor joins. Note that session recordings will be as long as the event duration.
custom_rec_set_reminder	boolean	off: Recording reminder is disabled	on: Enable recording reminder prompt once instructor has been in the room for two minutes
custom_rs_auto_clear_chat_end_of_session	boolean	off: Do not clear the room chat at the end of the session	on: Clear the room chat at the end of the session
custom_rs_class_mode	string	virtual_classroom: Set room to be in virtual meeting room mode, where users are automatically set to Live and prompted to activate webcams	webinar: Set room to webinar mode, where users are not live
custom_rs_enable_guests_to_join	boolean	on: Enable guests to join with invite link	off: Block guests from joining by invite link
custom_rs_enable_media_library	boolean	on: Show "Video Library" in tools	off: Hide "Video Library" in tools
custom_rs_hide_end_session	boolean	off: Show "End Session" button, which ends the session for all participants	on: Hide "End Session" button
custom_rs_hide_leave_session	boolean	off: Show "Leave Session" button, which ends the session for the user	on: Hide "Leave Session" button
custom_rs_show_chat	boolean	on: Enable chat for students and guests	off: Disable chat for students and guests
custom_rs_show_chat_moderators	boolean	on: Enable moderator chat	off: Disable moderator chat
custom_rs_show_chat_questions	boolean	on: Enable Q&A for students and guests	off: Disable Q&A for students and guests
custom_rs_show_invite	boolean	on: Show invite option for moderators and instructors	off: Hide invite option for moderators and instructors
custom_rs_show_language_selection	boolean	on: Show "Select Language" in options menu	off: Hide "Select Language" in options menu
custom_rs_show_ondemand_page_link	boolean	off: Hide "On Demand Course" in options menu	on: Show "On Demand Course" in options menu
custom_rs_show_participant	boolean	on: Show participant list for students and guests	off: Hide participant list for students and guests

Language Settings

Adding a tag of custom_rs_user_lang will force the locale language in the room. Supported languages:

fr-FR French (France)
de-DE German
ko-KR Korean
pt-BR Portuguese (Brazil)
ja-JP Japanese
en-US English (US)
zh-CN Simplified Chinese (China)
it-IT Italian
es-LA Spanish
he-IL Hebrew
en-VE (special locale for corporate-style events, where the education lingo is less relevant)

Example

    $schedulePlugin = KalturaScheduleClientPlugin::get($client);
    $scheduleEvent = new KalturaRecordScheduleEvent();
    $scheduleEvent->recurrenceType = KalturaScheduleEventRecurrenceType::NONE;
    $scheduleEvent->startDate = 1586185200;
    $scheduleEvent->endDate = 1586188800;
    $scheduleEvent->summary = "Tomorrow's Event";
    $scheduleEvent->tags = "custom_rec_auto_start:1,custom_rs_show_invite:1,custom_rs_user_lang:es-LA";

    $result = $schedulePlugin->scheduleEvent->add($scheduleEvent);

This event will take place on April 6th 2020 from 3-4pm GMT, with a Spanish interface. It will begin recording automatically and allows attendees to invite others.

Response Object

{
  "blackoutConflicts": [],
  "id": 3371011,
  "partnerId": 1234567,
  "summary": "Tomorrow's Event ",
  "status": 2,
  "startDate": 1586186820,
  "endDate": 1586190420,
  "classificationType": 1,
  "ownerId": "vpaas@kaltura.com",
  "sequence": 11,
  "recurrenceType": 0,
  "duration": 3600,
  "createdAt": 1586113200,
  "updatedAt": 1586113200,
  "objectType": "KalturaRecordScheduleEvent"
}

Creating an Event Resource

An event must be associated with a resource. As mentioned, the same resource (room) can be launched at many different times with different events. This allows you to keep specific resources inside a virtual room; for example, for the same class that is taught numerous times with the same lesson plan.

To associate a session with an event, use the scheduleEventResource.add action. This is where you'll need the resource Id and the event Id that you just created.

Example

  $schedulePlugin = KalturaScheduleClientPlugin::get($client);
  $scheduleEventResource = new KalturaScheduleEventResource();
  $scheduleEventResource->eventId = 3371011;
  $scheduleEventResource->resourceId = 1100601;

  try {
    $result = $schedulePlugin->scheduleEventResource->add($scheduleEventResource);
    var_dump($result);
  } catch (Exception $e) {
    echo $e->getMessage();
  }

This Scheduled Event will take place in Room-1 on April 6th 2020 at 3pm GMT.

Response Object

{
  "eventId": 3371011,
  "resourceId": 1100601,
  "partnerId": 2365491,
  "createdAt": 1586148953,
  "updatedAt": 1586148953,
  "objectType": "KalturaScheduleEventResource"
}

Creating a Kaltura Session

A virtual meeting room is authenticated by using a Kaltura Session (KS), which is what identifies the user and contains permissions.

We'll create the KS by using the session.start action. You'll need:

Your PartnerID from the integration settings in your KMC
The USER Secret from the integration settings in your KMC
userId, which can be any identifying string, but must be unique to each user in the room
privileges string, described below

Tip: if you're logged into the developer.portal, you can find your credentials by clicking your account at the top right corner and then View Secrets

The Privileges String

The virtual room settings will be passed into the privileges parameter, which is a comma-separated key-value string, much like the tags above. It contains information about context, privacy, and even user details.

In the context of virtual rooms, the string must include a role, and either a resourceId or an eventId. If only EventId is set, the resourceId will be retrieved automatically. If only resourceId is set, the outcome will be determined by the settings in userContextualRole. If the user is a moderator, this will allow entry to the room to prepare materials and content. For a regular attendee, entry will only be allowed if the moderator is already in the room.

Note: A user is able to join a Virtual Room directly by specifying the resourceId in the privileges parameter instead of eventId. Event creation is optional.

Key	Required	Description
eventId	yes, if `resourceId` not set	ID of the event
resourceId	yes, if `eventId` not set	ID of the resource
role	yes	`viewerRole` for attendees / `adminRole` for moderator
userContextualRole	no	0 for instructor / 3 for attendees/guests.
firstName	no	first name to appear in participants list
lastName	no	last name to appear in participants list

Note that userContextualRole is what determines a user's permissions in the virtual room. If userContextualRole is not set, the role will be set to attendee/guest.

Examples

Below are examples of creating a Kaltura Session in various scenarios. Their expiry time, which is currently set to 86400ms (one day), can be changed to accommodate the security settings of your application.

An Attendee Joining A Scheduled Event

  $secret = "xxxxx"
  $userId = "max@organization.com";
  $type = KalturaSessionType::USER;
  $partnerId = 1234567;
  $expiry = 86400;
  $privileges = "eventId:3371011,role:viewerRole,userContextualRole:3,firstName:Max";

  $result = $client->session->start($secret, $userId, $type, $partnerId, $expiry, $privileges);

A Moderator Joining A Scheduled Event

  $secret = "xxxxx"
  $userId = "speaker@organization.com";
  $type = KalturaSessionType::USER;
  $partnerId = 1234567;
  $expiry = 86400;
  $privileges = "eventId:3371011,role:adminRole,userContextualRole:0,lastName:Speaker";

  $result = $client->session->start($secret, $userId, $type, $partnerId, $expiry, $privileges);

A Moderator Preparing a Virtual Room Before an Event

  $secret = "xxxxx"
  $userId = "speaker@organization.com";
  $type = KalturaSessionType::USER;
  $partnerId = 1234567;
  $expiry = 86400;
  $privileges = "resourceId:1100601,role:adminRole,userContextualRole:0";

  $result = $client->session->start($secret, $userId, $type, $partnerId, $expiry, $privileges);

Creating the Virtual Meeting Room URL

The URL structure for the meeting room looks like this:

[KAF-ENDPOINT]/virtualEvent/launch?ks=[KS]

where the KS is the Kaltura Session and your KAF endpoint is [YOUR PARTNER ID].kaf.kaltura.com, which must be preconfigured on your account. If you're not sure whether newrow/KAF have already been set up on your account, email us at vpaas@kaltura.com.

Example

1234567.kaf.kaltura.com/virtualEvent/launch?ks=djJ8MjM2NTQ5MXxGbYGg6kZISSOJqeojxSl9-PRS78DLutFB3LZlbQef1n42zW5NHfkZKBmhHTTUe3aSf0eQg8FkA1SsKvsSz7evqm4VHzPP_Q0POLuKXKvuVDuSOjOeTBltskSaCRlclo1ZLHUXt4p1pMeQdo95jaY0ddYV1xJH7KMMCBNV-AMt2IqbwyWdTaeTlatZ0quTOACZ6uvzhq1v

You can navigate to this page directly, or you can embed it in your webpage using an iFrame, like so:

<!DOCTYPE HTML> 
<html>
<body>

  <iframe src="https://1234567.kaf.kaltura.com/virtualEvent/launch?ks=djJ8MjM2NTQ5MXxGbYGg6kZISSOJqeojxSl9-PRS78DLutFB3LZlbQef1n42zW5NHfkZKBmhHTTUe3aSf0eQg8FkA1SsKvsSz7evqm4VHzPP_Q0POLuKXKvuVDuSOjOeTBltskSaCRlclo1ZLHUXt4p1pMeQdo95jaY0ddYV1xJH7KMMCBNV-AMt2IqbwyWdTaeTlatZ0quTOACZ6uvzhq1v" wmode=transparent allow="microphone *; camera *; speakers *; usermedia *; autoplay *; fullscreen *; display-capture *;" width="1100px" height="700px"></iframe>

</body>
</html>

Note that in the iFrame you'll need to add https:// to the beginning of the URL

As a best practice, we recommend you embed the URL in an iFrame in the webpage, allowing your application to handle access to the given page. See more about security measures below.

Security and Privacy

It is the responsibility of your application to manage the security and permissions for each meeting room. As mentioned, it is encouraged to embed the URLs within iFrames in your application, to ensure that users are authenticated before arriving at the given webpage.

How can I ensure that users are not accessing the room outside of the event time? A Kaltura Session can be given an expiry of one day, one hour, even one minute. When the KS expires, that link will no longer be valid.

Can somebody use and share the room URL by viewing the source of the page? Reminder that userIds must be unique - meaning that a user who copies and shares an embed link would be kicked out of the room once somebody with an identical link joins the room.

How can I prevent users from inviting others by using the Invite option in the room? You can use tags=custom_rs_show_invite:0 on the resource or event creation to hide the Invite button in the room.

How can I allow users to securely invite others to the room? Assuming the Invite button is enabled, the invitation modal allows a password to be set on the invite link.

If Your Virtual Room is Not Working As Expected

Make sure you created the resource with tags = "vcprovider:newrow"
Check with us to ensure the feature is enabled on your account
Did you associate a resource with the event?
Did you pass role in the KS privilege string?

If you're still experiencing trouble, email us at vpaas@kaltura.com.

Room Analytics

Acquiring room analytics takes several steps, as outlined below.

API Endpoint

The URL structure for the analytics endpoint looks like this:

[KAF-ENDPOINT]/newrowkaf/index/api?ks=[KS]

where the KS is the Kaltura Session and your KAF endpoint is [YOUR PARTNER ID].kaf.kaltura.com.

Generating Kaltura Session

Kaltura Session (KS) generation is discussed previously, however for the analytics APIs, the generation will be slighlty different, particularly the privileges parameter.

We'll create the KS by using the session.start action. You'll need:

Your PartnerID from the integration settings in your KMC
The ADMIN Secret from the integration settings in your KMC
userId, which can be any identifying string
privileges string, described below

The Privileges String

The details of the analytics API call will be passed into the privileges parameter.

In the context of the analytics API, the string must include a role, an api, and either a resourceId or an eventId.

Key	Required	Description
eventId	yes, if `resourceId` not set	ID of the event to get the data about
resourceId	yes, if `eventId` not set	ID of the resource to get the data about. Do not populate both resourceId and eventId.
role	yes	set to `viewerRole`
api	yes	defines the API action to be executed. The value of this parameter is a URL encoded JSON string.

Privileges Example

JSON Object

{
  "method": "GET",
  "action": "analytics/sessions",
  "params": {
    "from_date": "1522153700",
    "to_date": "1522156000"
  }
}

JSON String

{ "method": "GET", "action": "analytics/sessions",  "params": { "from_date":"1522153700", "to_date": "1522156000" } }

URL encoded

%7B%20%22method%22%3A%20%22GET%22%2C%20%22action%22%3A%20%22analytics%2Fsessions%22%2C%20%20%22params%22%3A%20%7B%20%22from_date%22%3A%221522153700%22%2C%20%22to_date%22%3A%20%221522156000%22%20%7D%20%7D

The API privilege attribute is

api:%7B%20%22method%22%3A%20%22GET%22%2C%20%22action%22%3A%20%22analytics%2Fsessions%22%2C%20%20%22params%22%3A%20%7B%20%22from_date%22%3A%221522153700%22%2C%20%22to_date%22%3A%20%221522156000%22%20%7D%20%7D

The full privilege string

resourceId:YOUR_RESOURCE_ID,role:viewerRole,api:%7B%20%22method%22%3A%20%22GET%22%2C%20%22action%22%3A%20%22analytics%2Fsessions%22%2C%20%20%22params%22%3A%20%7B%20%22from_date%22%3A%221522153700%22%2C%20%22to_date%22%3A%20%221522156000%22%20%7D%20%7D

Each API request has pagination, each page gets 30 records max. The API return total_count of records and next_page. Empty next_page means that this is the last page.

Acquiring Session Analytics

Acquiring session analytics takes several steps, as outlined below:

First, get the session that took place in the particular room / scheduleResource of interest

NOTE: the data will be acquired for the resourceId (room) specified in the KS privilege field.

Action	Method	Description
/analytics/sessions	GET	Get a list of sessions that occurred in a room

API Parameters

Param Name	type	Is optional	Description
third_party_room_id	string	optional	Option to filter by third party room id (LTI Launch) - to get all room sessions. For rooms created using the Kaltura API (see here), use the resource id created using the scheduleResource service.
page	integer	optional	The current requested record set page Start from 0 to n Default is 0
from_date	string	optional	Option to filter sessions that started from specific date time. Date format: Unix Timestamp
to_date	string	optional	Option to filter sessions that started from specific date time. Date format: Unix Timestamp

API JSON Example:

{
  "method": "GET",
  "action": "analytics/sessions",
  "params": {
    "third_party_room_id": "1234567",
    "from_date": "1522153700",
    "to_date": "1522156000"
  }
}

API URL-encoded JSON

%7B%22method%22%3A%22GET%22%2C%22action%22%3A%22analytics%2Fsessions%22%2C%22params%22%3A%7B%22third_party_room_id%22%3A%221234567%22%2C%22from_date%22%3A%221522153700%22%2C%22to_date%22%3A%221522156000%22%7D%7D%0A

Result:

{
  "status": "success",
  "data": { 
     "sessions": [ { 
        "id": "16772",
        "room_id": "490",
        "third_party_room_id": "93839",
        "room_name": "Nir api test room",
        "date_start": "1522153776", 
        "date_end": "1522155274",
        "duration": "24.9667",
        "type": "room",
        "instructors": "{\"203\":{\"role\":\"admin\",\"name\":\"Denis Sicun\"}}", 
        "participants_count": "1", 
      } ], 
  "total_count": 1, 
  "next_page": "" } 
}

Next, get the session attendee count of the session acquired in previous step.

For customers integrating analytics into their own dashboards, make sure to include include_third_party_data = 1 to have SSO user id and email returned with the analytics.

Action	Method	Description
/analytics/sessions-attendees	GET	Get all attendees in a specific session

API Parameters

Param Name	type	Is optional	Description
session_id	integer	required	Object id of the desired session
page	integer	optional	The current requested record set page Start from 0 to n Default is 0
from_date	string	optional	Option to filter attendees that started from specific date time. Date format: Unix Timestamp
to_date	string	optional	Option to filter attendees that ended before specific date time. Date format: Unix Timestamp
include_third_party_data	integer	optional	Set to 1 to have the user id and email passed through the integrating 3rd party’s SSO, returned as well (lti_* fields)

API JSON Example:

{
  "method": "GET",
  "action": "analytics/session-attendees",
  "params": {
    "session_id" : "16772",
    "include_third_party_data": 1
  }
}

API URL-encoded JSON

%7B%22method%22%3A%20%22GET%22%2C%22action%22%3A%20%22analytics%2Fsession-attendees%22%2C%22params%22%3A%7B%22session_id%22%3A%2216772%22%7D%7D%0A

Result:

{
  "status": "success",
    "data": { 
      "session_attendance": [
      {
        "session_id": "16772",
        "user_id": "203",
        "lti_user_id": "denis",
        "user_type": "user",
        "user_name": "Denis Sicun",
        "user_email": "1610545059_c36129@lti-newrow.com",
        "lti_user_email": "denis@newrow.com",
        "time_joined": "1512657239", 
        "time_left": "1512657271",
        "duration": "0.5333",
        "attention": "34%" 
      },
        ..
        ..
    ],
    "total_count": 3,
    "next_page": ""
  } 
}

Name		Name	Last commit message	Last commit date
Latest commit History 34 Commits
README.md		README.md

Key	Type	Value
custom_cat_id	string	comma separated list of kaltura category IDs to which room recordings of the session will be published automatically
custom_company_logo	string	URL-encoded string of the logo URL
custom_live_entry	string	kaltura live entry ID to be pre-loaded into the Live Broadcast module, which allows for broadcasting contents of the room to an RTMP feed
custom_playlist_id	integer	Playlist ID to load in this resource
custom_reset_playlist_instance	boolean	on (default): creates a new playlist instance if the ID is already loaded in the room. off: does not reset playlist instance
custom_redirect_url	string	URL-encoded string of the URL to redirect to after the participant leaves the room
custom_rs_room_cap	integer	limits room capacity for the coming session, additional participants will get a "room is full" notification and will not be allowed into the room
custom_rs_show_logo	boolean	on (default): show company logo in top toolbar. off: Hide company logo in top top toolbar
custom_p_rtmp_url	string	Primary RTMP URL of the target broadcast service e.g. kaltura, facebook, youtube, etc.
custom_s_rtmp_url	string	Secondary RTMP URL of the target broadcast service e.g. kaltura, facebook, youtube, etc.
custom_rtmp_key	string	Unique broadcast key received from your broadcast service provider for the RTMP stream
custom_tp_playlist_id	integer	Third Party Playlist ID to load in this resource
custom_xl_room_max	integer	number of participants expected in the XL room mode session (300 (min), 400, 500, 600, 700 (max))
custom_xl_room_pres	integer	number of presenters that will require being 'LIVE' concurrently, publishing their audio/video streams
custom_xl_room_geo	string	choose a geo if all presenters are located in proximity of one of these geo locations or choose the global region if not. Enter us-east-1 (for USA), eu-central-1 (for Europe), ap-southeast-1 (for SE Asia ), ap-northeast-1 (for NE Asia), global

kaltura-vpaas/virtual-meeting-rooms

Folders and files

Latest commit

History

README.md

README.md

Repository files navigation

Kaltura Meetings Integration Guide

Before You Begin

Overview

Creating an Admin Session

Example

Creating a Resource

Required Parameters

Optional Parameters

Tags

Example

Response Object

Creating an Event

Required Parameters

Optional Parameters

Tags / Event Settings

Language Settings

Example

Response Object

Creating an Event Resource

Example

Response Object

Creating a Kaltura Session

The Privileges String

Examples

An Attendee Joining A Scheduled Event

A Moderator Joining A Scheduled Event

A Moderator Preparing a Virtual Room Before an Event

Creating the Virtual Meeting Room URL

Example

Security and Privacy

If Your Virtual Room is Not Working As Expected

Room Analytics

API Endpoint

Generating Kaltura Session

The Privileges String

Privileges Example

Acquiring Session Analytics

First, get the session that took place in the particular room / scheduleResource of interest

Next, get the session attendee count of the session acquired in previous step.

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Contributors 4

Packages