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 some partners may prefer remote provisioning over manual provisioning, the this example is included because it is useful in demonstrating nevertheless useful because it introduces some important info while providing a fundamental demonstration of how our players function and is used to introduce some important info. It is also relatively . As the example is straightforward to replicate so users can , it enables users to easily follow along with their own player. Remote provisioning will be covered later in this packet.
As covered previously, provisioning a player involves applying a Setup and Player App to a player. You may recall that with the BrightSign Default Setup, 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 BrightSign Default Setup and copy a custom Player App to the player.