Configuring a Media Playback Service

The media file you want to upload, it must be in MP4 video format and H.264 encoded.

We recommend the file is encoded using the "baseline" profile and "fastdecode", for example:
ffmpeg -i '<media file>' -c:v libx264 -preset slow -profile:v baseline -tune fastdecode 'baseline-fastcpu-720p.mp4'

Individual files up to 2 GB may be uploaded, and the cumulative size of all files together may be up to 10 GB.

Later, when you configure the Media Playback Service, you should set the Maximum call quality setting to match the resolution of the media files.

If enabled, the playlist is shuffled so that all media items are played in a random order (media items’ specified positions are not used).

If the playlist contains an item with a play count greater than one, each instance is shuffled and played once. For example, if an item has a play count of 3, all 3 instances are shuffled among the other media items.

If both shuffle and loop are enabled, all iterations of the playlist play in the same order.

Every item must have a unique position specified. This refers to the order in which in the Media Library Item is played relative to the other items in the playlist. Please note that Position is only used when shuffle is off.

When editing an existing playlist, if you want to change the position of multiple playlist items, you need to make each edit and save it individually.

The theme for use with this Media Playback Service. For more information, see Customizing conference images and voice prompts using themes.

Note that watermarks are not applied to the playlist videos.

Default: <use Default theme> (the global default theme is used).

This defines what happens when the playlist finishes. The user can be disconnected or transferred elsewhere (to a VMR for example).

If the action is left blank, the video ends with the final frame remaining in view.

The completion action is specified in JSON format.

To disconnect the user, enter: {"disconnect": true}

Alternatively, to transfer the user, the format is:

{ "transfer": {"conference": "<alias>", "role": "<role>"}}

You must provide an alias to transfer the user to — this is typically the alias of a VMR.

Role is optional. If not supplied or if you specify a role of "auto", the user is transferred to the next service with the same role they had on accessing the playback service, unless:

• no PINs are used to access the playback service, in which case users are transferred as Host by default
• you specify "host" or "guest" role, in which case all users are transferred using the specified role.

For information about how the role for the Media Playback Service is determined see Participant authentication.

The playback service's configuration needs to take into account the security requirements of the service that users are transferred to, if appropriate. This is because users are prompted only once for PINs / authentication details, based on the configuration of the playback service.

• PINs must use the digits 0-9 only.
• PINs may optionally end with #.
• PINs must be between 4–20 digits long, including any #.

Set this to Yes if you want to configure a Guest PIN in addition to a Host PIN.

Guest/Host roles are treated the same in the playback service, but may be relevant if the user is subsequently transferred to a VMR.

Default: No.

This optional field allows you to set a secure access code that must be entered before the user can access the playback service. This would give the user Guest rights if they were subsequently transferred to a VMR, unless a different role is specified in the completion action.

• Host PINs and Guest PINs must be different.
• PINs must use the digits 0-9 only.
• PINs may optionally end with #.
• PINs must be between 4–20 digits long, including any #.
• If the Host PIN ends in # and a Guest PIN is used, the Guest PIN must also end with #.
• If # is not used, Host PINs and Guest PINs must have the same number of digits.
• You cannot configure a Guest PIN unless you have already configured a Host PIN.

The set of Identity Providers to be offered to Hosts to authenticate with, in order to use the service. If this is blank, Hosts are not required to authenticate.

For more information, see see About participant authentication.

Default: none selected

The set of Identity Providers to be offered to Guests to authenticate with, in order to use the service. If this is blank, Guests are not required to authenticate.

For more information, see About participant authentication.

Default: none selected

(Available when an Identity Provider Group has been selected)

Determines whether participants joining a SSO-protected service from devices other than the Connect web app (for example SIP or H.323 endpoints) are allowed to dial in to the service.

• Disallow all: these devices are placed in a waiting room where they must wait to be admitted by a Host.
• Allow if trusted: these devices may join the service if they are locally registered. They must still enter a Host PIN or Guest PIN if either is required. All other devices are placed in a waiting room where they must wait to be admitted by a Host.

For more information, see About participant authentication.

Default: Disallow all

Controls the maximum call quality for participants connecting to this service. This should be set to match the resolution of the playback video. For example, set it to HD if the playback videos are 720p and set it to Full HD if the videos are 1080p.

A failure to match the video resolution with the playback room call quality may degrade performance.

The alias that, when received by Pexip Infinity, is used to route the call to this service.

The alias entered here must match the alias as it is received by Pexip Infinity. Wildcards and regular expressions are not supported.

In most cases, the alias received by Pexip Infinity is the same as the alias that the participant used to call the service, but there are some exceptions, described in About aliases and access numbers.

You may also want to define multiple aliases for the same service to ensure that it can be accessed by devices and protocols that enforce specific alias formats — for more information, see Using multiple aliases to access the same service.