In this section, you will be guided through a hands-on example that demonstrates how our players can be manually provisioned to simultaneously display local, web, and streaming content.
While it is understood that most partners will not be opting for manual provisioning, the example is included because it is useful in demonstrating how our players function and is used to introduce some important info. It is also relatively straightforward to replicate so users can follow along with their own player.
As covered previously, provisioning a player involves applying a Player Config and Player App to a player. You may recall that by default, players are configured to look for a network connection via Ethernet and, if a connection is found, obtain an IP address using DHCP. In this example, we will maintain the player’s default Player Config and will copy a custom Player App to the player.