The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/9613083-playlists-content-switching-via-udp-receiver

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

The Korbyt Experiential add-on feature provides a variety of methods for triggering content from external devices.

The method described in this article utilizes Clever Playlists Triggers (under Playlist Settings) and Experiential rules with an embedded UDP Receiver to trigger content switching on specific media players.  

There are some requirements for this experiential feature to work

• The media player connected to the screen must be a Korbyt Windows Player running Korbyt version 3.40 or higher
• Your Korbyt Tenant must have the Korbyt Experiential Feature enabled
  • This is an add-on Korbyt service
• Third-party UDP sender device
  • For testing purposes, users can utilize an UDP sender software such as Packet Sender.
  • For permanent projects, a Crestron Processor could be a typical sender.
• Port 50003 must be open on the host network and both the sending and receiving UDP signals
• The Playlist that will be controlling the player must be a Clever Playlist

To Setup Content Switching

• In the Korbyt CMS build two separate Clever Playlists 
  • Clever Playlist 1 will be your Primary Playlist that is typically playing on your screens when the trigger has not been sent
    • This playlist MUST consist of 1 item set to zero seconds
    • It is possible to use the logic of a Takeover to create a single Layout Item that has an embedded playlist of multiple items
  • Clever Playlist 2 will be your Secondary Playlist that will take over screens when the UDP signal is sent
  • The actual playlist names in Korbyt can be any value as long as they are clear to you which is which
  • Add the relevant content to each playlist as normal
• Within your Primary Clever Playlist to be connected to your UDP device
  • Open the Primary Clever Playlist with the Pencil Icon
  • Click Playlist Settings in the Upper Right to open the settings side panel
    
  • Click the Experiential Rules builder tool at the bottom of the settings side panel
    
  • Within the Experiential Rules Builder on the left, Drag the TCP/UDP Receiver element from the left to the center builder
    
    • In the TCP/UDP Receiver box, enter the value to match the string value being sent from the UDP sender
      • On the UDP sender device, the UDP value must equal korbyt:<string>
      • Replace <string> with a string value of your choice. E.g., korbyt:1
  • Within the Experiential Rules Builder on the left
    • 1 – Switch from Triggers to Actions
    • 2 – Drag the Play a Playlist action to the builder space
    • 3 – Click the playlist name section to open the Properties sidebar
    • 4 – Configure the Properties for the Secondary Playlist 2 and the Player that should show it
  • Click save in the upper right to close the Experiential Builder and return to the Primary Playlist screen
  • Schedule your Primary Playlist to the applicable players
  • Click Save Playlist

When targeted players receive the UDP string value, the players will change from primary Playlist 1 to secondary Playlist 2.

For more information on third-party control scenarios like this, please see this article: https://kb.korbyt.com/article/remote-control-of-korbyt-players-and-content-from-external-devices/  

The post Playlists Content Switching via UDP Receiver appeared first on Korbyt Knowledge Base.

The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/6429043-korbyt-windows-player-kwp-requirements-and-installation

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

This article reviews how to install the KWP software on a Windows computer to turn it into a Korbyt Media Player.

This article review the process for KWP Software v3.20 and higher
For information on system requirements see Korbyt Windows Player (KWP) Minimum Requirements

• Obtain a download link for the latest KWP software installation package from Korbyt
  • You can email Support@Korbyt.com or contact your Professional Service team member
• You will receive a direct download link that will start the download of the zip package in your browser
• Extract the files from the zip folder
• Locate and run the KorbytBootStrap application and run it
  
  • Or use the command prompt as an admin to run the KorbytBootStrap.exe
•  When the installer opens you will be asked to select the version of the KWP application you would like to install
  
  • Standard is the preferred package as it will provide a full experience
  • For more information on the limits of a Lite configuration see KWP Limitations
• Confirm your selections and click Install
  
• Once the installer runs you will have to restart to have the Korbyt Application Launch
  
• Your computer will reboot and should automatically launch your Korbyt Media Player software
  • If you wish to access the desktop please see How to Access the Desktop of a KWP

If this is a new device you will need to provision the player to your service, for more information see Provisioning A Player

The post Korbyt Windows Player (KWP) Software Installation Process appeared first on Korbyt Knowledge Base.

The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/1175751-korbyttm-onprem-hardwaresoftware-minimum-requirements

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

This document outlines specific selected products and application usage to determine the recommended minimum configurations for Korbyt On-Premise and Hybrid server software. Unless otherwise specified, the customer is responsible for the provisioning and setup of any network/LAN devices and/or connections.

Hardware that does not meet the minimum requirements may result in varying degrees of performance degradation or failure to operate. Korbyt Technical Support may require bringing the hardware platform into compliance before support can be provided. Additional professional services may be required for hardware to meet the recommended minimum requirements.

Any recommendations made by Korbyt regarding the clients’ personal computers, servers, and applications are based on Korbyt’s experience and understanding of the intended use of Korbyt products. As with any computer-based system, individual requirements and performance may vary.

The optimal configuration of software and hardware may depend on a variety of factors including, but not limited to: the configuration of the installed Korbyt software, outbound message activity, the number of attached endpoints, the number and complexity of applications monitored, the size and complexity of the user program options selected, the amount and rate of delivery of the data to the personal computer where the Korbyt™ server system resides, and other computer systems.

Korbyt™ On-Premise Hardware and Software Requirements for Server

Hardware requirements may vary depending on the individual installation demands.  Examples of factors that result in increased hardware requirements are:

• Large content demands (i.e. a large number of videos)
• Large data collection demands
• A very low data collection interval
• A large number of media players

Supported Operating Systems

• Ubuntu 22.04 LTS 64-bit (Preferred)
  • Installed with no GUI
  • Minimal installation option

• or

• RedHat Enterprise Linux 8.6 – 8.8 (no support for 9.x)
  • RHEL requires approval by Korbyt
  • This is only supported where the Korbyt application controls the root account and the server is treated as an appliance and not a multi-purpose server.
  • If there are special requests and needs on the dedicated server, then the solution will need to be on Ubuntu 22.04.
  • The customer must provide a RHEL license key and/or login

For Full Server Requirements and Configuration Details please review the full document below
Can also be opened as a separate tab HERE where it can be downloaded from as well

The post Korbyt OnPrem and Hybrid Server Minimum Requirements appeared first on Korbyt Knowledge Base.

The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/8154797-brightsign-configuration-instructions-using-bsn-cloud

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

BrightSign devices have their own cloud control system, BSN Cloud, which is used to manage the hardware level settings, including installing the Korbyt partner application that will allow your device to connect to your Korbyt Tenant.

You will need to connect your player to a BSN Cloud account before it can be connected to Korbyt.

BrightSign BSN Resources

BrightSign provides guidance in videos and articles for creating or using your BSN Cloud to install a partner application.

• BrightSign Support Provisioning Article 
• Partner Application Setup
  • CMS Partner Provisioning Video from BrightSign
• If you have installed a Wi-Fi card in your Brightsign (not default equipment) you will need to Configure Network in BSN/Bright Auther

CAUTION: Ensure your Brightsign device is on an appropriate version of Brightsign Firmware
The Supported Hardware Article has a grid that reviews the current supported firmware version for different Brightsigns
If your Brightsign player’s Firmware is not on one of the supported versions, you may find that you lose some player functionality while using the Korbyt software.
If you need instructions for getting your player on the correct firmware please reference our firmware upgrade and downgrade article HERE

During this process, your player may restart several times.

Once your BrightSign has loaded the Korbyt Player Software, you should see the blue Korbyt provisioning screen with your player’s unique token.

Or if your player was provisioned in advance, it will be playing either default content or assigned content.
If you need assistance provisioning your player to Korbyt once the software is running, please see:

• Provisioning a Player
• Provisioning Bulk Players

The post BSN Cloud – Brightsign Configuration Instructions appeared first on Korbyt Knowledge Base.

The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/7273373-korbyt-player-network-connections

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

To have Korbyt Media Players provision successfully and reach Korbyt in the cloud, the following requirements must be followed:

• The Media Player needs to be assigned a DNS server from DHCP or manually.
• The Media Player needs to be able to reach a DNS server(step 1) that can resolve our external domain name (*.korbyt.com)
• Whitelist Korbyt.com – *.korbyt.com will need to be whitelisted in order for subdomains and external sources to be able to be accessed.
  • Note: Domain whitelisting must be used, as IP’s for Korbyt are dynamically assigned.

• Ports used for Cloud
  • Port 443 Outbound    – is required for the players to connect to Korbyt in the cloud.
  • Port 443 Inbound        – is required for access to the web interface of the players (from your INTERNAL network only, not inbound from the cloud)

• Ports used for Hybrid
  • Port 443 Outbound    – is required for the players to connect to Korbyt in the cloud.
  • Port 443 Inbound        – is required for access to the web interface of the players (from your INTERNAL network only, not inbound from the cloud)
  • Port 80 Outbound       – is required for Hybrid installs in addition to those listed above
  • Port 8081 Outbound – (Content Caching Service) is required for Hybridinstalls in addition to those listed above. This port is also used for communication from the players to the On-Prem server.
  • Port 8085 Outbound – (Web Services) is required for Hybrid in addition to those listed above This port is also used for communication from the players to the On-Prem server.

The ports above are Korbyt Standard Connections for Cloud and Hybrid Service

If you are using Brightsign Devices you may have to configure additional permissions in your network to allow Brightsign functionality.
This Brightsign support article provides details on their requirements – BrightSign Network – ports and URLs for the BrightSign players

If you have a custom configuration in your Korbty service, additional ports and whitelisting may also be required.

Fully On Premises Korbyt services require different port access

• Ports used for Full On-Premise
  • Standard
    • Port 80 Inbound – Access to player content and CMS interface
    • Port 8085 Inbound – Web Services
  • HTTPS (using a well-qualified certificate)
    • Port 443 Inbound        – is required for access to the web interface of the players (from your  INTERNAL network only, not inbound from the cloud)
      • All traffic from Port 80 & Port 8085 are redirected to Port 443

The post Whitelist and Port Access Requirements for Korbyt appeared first on Korbyt Knowledge Base.

The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/3283160-how-to-configure-the-korbyt-pwa-player-on-a-chrome

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

The post How To Configure The Korbyt PWA Player On A Chrome Device appeared first on Korbyt Knowledge Base.

The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/7949642-player-settings-controlling-and-configuring-media-players-in-the-cms#ai03ooqrkwe

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

Korbyt players use Chromium to display content.
Runtime is used to help Chromium execute tasks and events that are responsible for handling how content is displayed and scheduled to be displayed on players. 

Newer versions of Runtime allow newer features of Korbyt to Function Properly and keep all functions running smoothly.

If your players are not using the latest verion of PRT they may encounter errors or difficulty

To see which version of PRT your players are using

• Open the Mega Menu then in the Device Management column click on Players
  • Switch your player view to List View if it is not already
    
• In list view located the player you want to see (use the search box if needed)
• The PRT version is either listed in the PRT column or at the end of the Player Software version in brackets
  

Changing PRT Version

Changing the PRT version that the player is running requires access to the Player Configuration Page

If you do not have access to yoru Player Configuration Page or your device does not support a Player Configuration Page (KWP or Brightsign) please contact Korbyt Support at Support@Korbyt.com for assistance with changing yoru PRT version

In the Korbyt Player Configuration Page

• Login to your Player Configuration Page
• Select Advanced, then Settings
• Runtime is set using the Player Version dropdown menu at the bottom of this screen
• Select the latest version and click the blue Change Version button

Sometimes a player can be on the latest version, but still need that latest version to be redownloaded to the player. This can be done by either

• Donwgrading the PRT to an older (lower) version using the method above fully to lower the version, then following the process to upgrade to the latest again
• Using the Player Actions in the Korbyt CMS to send the Clear Cache command (CAUTION – this method will also cause all downloaded player content to also need to be redownloaded)

For more information on Chromium and Runtime please see

• Chrome for Developers – https://developer.chrome.com/docs/extensions/reference/api/runtime

The post Player Runtime (PRT) appeared first on Korbyt Knowledge Base.

The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/7954401-korbyt-anywhere-for-cisco-instructions

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

* Disclaimer: While Webex devices are rebranded to Cisco, please be aware that the instructions provided herein reflect the current setup requirements.

Korbyt Anywhere for Cisco enables Korbyt users to schedule and display content on any Cisco device. Use a Cisco device as any other digital signage endpoint to maximize your screen real estate.

Important! By using this feature, Korbyt will programmatically change your devices to enable Digital Signage mode and add the player URL automatically. (Image below is where Korbyt makes this change on your behalf).

Prerequisites:

• Must be signed in as Webex Admin
• Webex Devices provisioned to Webex account

How to provision Korbyt signage on your cisco devices:

1. Tag your Webex devices with ‘korbyt’ in the Webex Admin portal.
2. Go to your Korbyt tenant and sign in.
3. Click the gear icon in the top right of the homepage
4. On the setting page, navigate to the signage tab
5. Click connect in the webex section on the signage setting webpage 
   1. Please note, this currently will add Korbyt to all Webex RoomOS devices in your organization with the tag ‘korbyt’. Please make sure to tag your devices that should have their setting changed.
   2. If you would like to run a manual test on a few devices, skip this step and head to the bottom of the article.
6. Login into webex via the integration’s OAuth Authorization URL
7. Accept the request permissions
8. Once the browser redirects back to signage settings, the connect button will turn green and a “Download Bulk Provision CSV” button will pop up 
9. Click on bulk provision button to download a CSV with Korbyt provisioning info for each Cisco device in the webex account that you signed in with
   • If needed, modify the player metadata to be used in Korbyt later on
10. Click on the hamburger icon in the top left of the settings page
11. Under signage, click players
12. Click the bulk provision button 
13. Click choose file and select the downloaded csv
14. Click validate and preview
15. Click import

Now, you have successfully provisioned korbyt signage on your cisco device!

How to add the Korbyt player to a single device at a time, and not use bulk method:

1. Login to your Webex Admin Portal (admin.webex.com)
2. Navigate to the devices page.
3. Click on a registered device and capture the Mac Address of the device.
4. Go to the signage section of this device and enable digital signage. 
5. Then add your tenant specific Signage url (it will be ‘https://yoursubdomain.korbyt.com/pwa?mac=insert cisco device mac address without colons).

The post Korbyt Anywhere for Cisco Instructions appeared first on Korbyt Knowledge Base.

The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/6574281-korbyt-optics-service-to-control-digital-signage

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

Optics is a subscription-based Korbyt feature for Digital Signage that uses a USB camera attached to the media player controlling a screen so that the Korbyt System can track information about who is present in front of the screen.

Tracking information such as:

• The number of people present in front of the screen
• The time that people are dwelling in front of the screen

These data points above can also be used to adjust the content that is playing on the screen in real-time.

For example: A playlist of promotional content could be playing on a kioks, then when a person is detected infront of it, the kiosk switches to it’s home screen.

Media Player Requirements

For the Optics service to function, the Media Player should be either

• An Aries II or Aries III Korbyt Digital Appliance (KDA)
  • Or
• A Windows PC Running the Korbyt Windows Player (KWP)
  • The Windows PC should meet the Minimum System Requirements listed HERE

  • The KWP Software has to be installed in a non-lite configuration that allows the configuration page

The KDA or KWP also has to have Audience Analytics enabled in the player configuration page

USB Camera Requirements

To properly function, the USB Camera should have a

• 1080p Resolution or higher
  • Higher is not required
• Flat Lens
  • No fish-eye style view
  • A wide viewing angle is OK, as long as the lens does not introduce distortion

Considerations

• The USB Camera will need to be connected to the Media Player
  • If additional USB cables will be used to bridge the distance between the player and the USB Cable that came with your Camera you may need to use Active USB cables. Ones that provide assistance to the data and power being transmitted
• The USB Camera should be installed in a location that allows it to see who is in front of the screen
  • Thick of the Camera as “looking back” at the person who is viewing the screen
• The Media Players will need Adequate Ventilation
  • The devices capable of running Optics service generate more heat than a low-powered device and will require adequate ventilation to avoid malfunctions

The post Korbyt Optics Service for Digital Signage appeared first on Korbyt Knowledge Base.

The New Page landing page for the Knowledge Base is https://product.korbyt.com/help

The new version of this specific article can be found at: https://product.korbyt.com/help/articles/3617444-player-groups-and-access-permissions#fcob7wmlpq2

Please update any of your bookmarks to the new Knowledge Base

For assistance on using the new Knowledge Base, we have a Welcome to the New Korbyt Knowledge Base guide

The new Korbyt Product Page also has sections for submitting feedback on system improvements, a view of our Roadmap of upcoming enhancements, and a change log of all updates.

Korbyt supports alerting Content Management System (CMS) Users if a media player changes status becoming Inactive or Active.

This will require a Player Group to be created, as Notification is a setting available in a Player Group.

See Creating Player Groups for the steps to create a player group

Once the Player Group is Created, on the lower right expand the Player Notification Recipients section
In this section you can specify which users get notified about the player, for what status changes, and through what communication channels

• A player status change to Inactive is present and not shows as an option
  • The other status changes are optional
• The Email communication channel sends an email from “noreply@korbyt.com” through Korbyt email services
  • All other communication channels will need to be configured in the Tenant Settings > Delivery  setting up your accounts with those services

The notification email that is sent will include the status change that triggered the alert, the player group name, and the name of the individual player.

The post Media Player Alerts and Notifications appeared first on Korbyt Knowledge Base.