Page Comparison

...

• BSN.cloud account, username, password, and group

• URL prefix for most stored URLs. This is the base URL for the recovery URL (for example, bsn.com), to which endpoints can be appended.

• Recovery/provisioning URL, error notification URL, crash report URL

• Timezone

...

1. The player connects to a network and obtains an IP address.

2. The player checks the storage device for an autorun. If an autorun is found, the player will execute the autorun and if it’s not none is found, it will proceed with the steps below.

3. If an IPv4 address exists, the player will attempt to provision over the network.

4. The player will check for a recovery URL (ru):

   • If a DHCP Option 43 recovery URL (ru) is found, it will override any registry value for ru until the end of the DHCP lease. This URL can be set through DHCP Option 43. See Option 43 to configure a DHCP server to communicate this URL to a BrightSign player.

   • If DHCP Option 43 ru is not found, the ru that is set in the registry will be used.

   • If there is no registry value for the ru, this step will be skipped.

5. If the recovery URL is blank, the player will attempt:

   • Well-known host provisioning: Also known as custom name mapping in your network's DNS server. If an IP address is mapped to brightsign-b-deploy, then the player will attempt to use the associated IP to provision itself automatically.

   • B-Deploy cloud provisioning: See B-Deploy/Provisioning APIs.

   • multicast DNS (mDNS): The player will automatically check the standard mDNS location (http://brightsign-b-deploy.local/) and if there is a server on your network with that address, the player will automatically provision itself. However, no other provisioning methods can be active if you want to provision with mDNS. See the Appendix for more information about this option.

6. The player will retry the provisioning process every 30 seconds until there is a successful response or interruption.

...