Enable CMS and register with Kaltura

Kaltura CMS integration for Pearl devices

Applies to: Pearl-2, Pearl Mini, Pearl Nano, Pearl Nexus, except where a section states otherwise. Device-specific behavior and limitations are noted in each section.

Applies to: Pearl-2, Pearl Mini, Pearl Nexus, Pearl Nano.

The Pearl device is fully integrated with Kaltura Content Management Systems (CMSs) for a seamless video recording and webcasting experience. After it is registered, it appears as a resource in Kaltura's MediaSpace and can be selected for scheduled recordings and webcasts, as well as be used for unscheduled ad hoc events that you can create using the Admin panel (or from the Pearl device's touch screen). Registering it as a resource with the Kaltura Content Management System (CMS) only needs to be done once.

When CMS is enabled, use the Admin panel to register Pearl device as an encoder resource for Kaltura. After Pearl device is registered, you can assign it a unique name that appears in the list of resources when creating an event in Kaltura's MediaSpace. The default name includes the serial number of Pearl device to ensure the name is unique. If more than two other resources are already registered with the same name, you're prompted to choose a different name and try to register Pearl device again. If only one resource is registered with the same name, you're prompted to take over the events for that other resource. If you do, Kaltura transfers all scheduled events from that other device over to Pearl device. It may take some time for Kaltura to display a newly registered resource, depending on how busy the Kaltura system is when you register. There are two methods to register your Pearl device:

• Using your Kaltura partner ID and administrator secret
• Using an application token and the token ID A Kaltura application token can be created from the Kaltura developer website: www.developer.kaltura.com There are two types of Kaltura application tokens you can use with Pearl device: an administrative session type and a user session type. With an administrative session token, Pearl device uploads event recordings to the respective event owner's account in Kaltura as expected. A user session token requires the following permissions: KMC_ACCESS,KMC_READ_ONLY,BASE_USER_SESSION_PERMISSION,WIDGET_SESSION_PERMISSION,CONTENT_INGEST_BASE,CONTENT_INGEST_UPLOAD,CONTENT_MANAGE_BASE,cuePoint.MANAGE,CONTENT_MANAGE_SCHEDULE,CAPTURE_DEVICE_PERMISSION,CONTENT_INGEST_REFERENCE_MODIFY,disableentitlement Important considerations for user session application tokens
• Pearl device uploads all events (scheduled and ad hoc) to the user account ID associated with the user token.
• All event recordings (scheduled and ad hoc) upload to the Kaltura account of the user who created the event if there is no user ID associated with the token.
• Do not include a creation date for the user session token. A creation date in the token causes Pearl device to upload events only to the token creator. It also restricts login using the Pearl device's touch screen to only the token creator. Before you begin, you should already have:
• A Kaltura instance created
• Either of the following:
• Your Kaltura partner ID and administrator secret
• Your application token ID and token value Enable Pearl device as a resource and register with Kaltura using the Admin panel
• Log in to the Admin panel as admin.
• From the Configuration menu, click CMS. The Content management system configuration menu opens.
• From the Choose CMS drop down, select Kaltura and then click Apply.
• In the Authorization method field, select the authorization method and do one of the following:
• If you select Administrator secret, enter your Kaltura Partner ID and Administrator secret that you got from Kaltura.
• If you select Application token, enter the application Token ID and **Token value **. Ensure the Token hash type matches the hash type set in the application token. The default is SHA1.
• (Optional) Change the Resource name that appears for this device in Kaltura. The default resource name includes the serial number of Pearl device.
• Click Register device. Pearl device - A calendar icon appears on the touch screen of Pearl device to show that Pearl is in CMS mode. What's next Choose which Pearl device channels you want this resource to record, assign the channel to use for webcasting, setup authentication for ad hoc events, and specify default ad hoc event parameters.

After Kaltura is registered, proceed to check the VOD and webcasting event settings and set up authentication for ad hoc events.

Device differences

• Pearl Nano, Pearl Nexus: Do not include a creation date for the user session token. A creation date in the token causes Pearl device to upload events only to the token creator.
• Pearl Nano: An Events screen is added to the Pearl device's front screen.
• Pearl Nexus: Pearl Nexus has no screen, so no calendar icon is shown; CMS status can be seen using the Admin panel, Epiphan Edge, or third-party control.