Time Servers

brightsign players use simple network time protocol (sntp), which is compatible with standard network time protocol (ntp) servers players can communicate with standard ntp servers, and players support setting their time using the http and sntp time protocols time server at startup, the player makes multiple attempts to connect to the time server (time brightsignnetwork com) the player must have internet access in order to sync the time with the brightsign timeserver if an attempt is successful, the player will set its clock and then communicate with the time server every 12 hours to re calibrate it if the initial attempt fails, and the response takes less than eight seconds, the player tries again immediately if the response takes longer than eight seconds, the player waits two minutes to try again each time there's a failure taking less than eight seconds, the player waits a little longer to retry a change to a player's time server settings through the bsn cloud causes the player to check the time server as soon as it downloads the updated sync file during the next point of communication between the bsn cloud and the player port 123 (for ntp) and port 80 (for http) must be open to set the time (see bsn ports & urls docid\ okihhduwqhkkikivn5vs7 ) modifying the time server the default clock update interval of 12 hours can be modified using the either the ronetworkconfiguration docid\ u6zceyqddlz9xdakttmjs brightscript api or the hostconfiguration docid\ p1dkloqhlm9wxsswmpeek javascript api ronetworkconfiguration docid\ u6zceyqddlz9xdakttmjs of the ronetworkconfiguration documentation describes methods that allow you to adjust the time server see hostconfiguration docid\ p1dkloqhlm9wxsswmpeek to update the time server in hostconfiguration url construction examples construction examples ntp\ //host uses ntp http //host\[ port] uses http \[with an optional port] https //host\[ port] uses https \[with an optional port] httpns\ //host\[ port] uses https \[with an optional port], but ignores cert failures setting the time server via https (using the https // prefix) is not recommended because the connection will fail due to missing/incorrect certificates if the player’s current time setting is invalid or too far off, and it won’t be able to correct its time setting without being able to connect to the time server, requiring manual intervention and possibly physical access to correct if https must be used, use the httpns\ // prefix (note the n before the s) and thoroughly test its functionality by performing a factory reset on the player and ensuring it is able to set its time afterward notes a time of 88 88 indicates that the time is not set properly on the player setting the time via https is also supported if the player is accessing the time server through a proxy server, then http should be used because it will honor the proxy settings sntp is a simplified implementation of the network time protocol (ntp) sntp interoperates with standard ntp servers if you have issues setting the time with ntp, see player troubleshooting docid\ cmgpupd usjwqq 6jgfs