BSN.cloud Operations FAQs

All connected and healthy players establish and keep persistent WebSocket connections with bsn.Content. If a player has "BSN" setup type and an active subscription, it will receive events from the server when either its settings or schedule are changed by any user in BrightAuthor:connected. The event propagation should take not more than few minutes (typically one minute), and the player requests the new settings or schedule immediately after receiving such an event.

Note that changes in Dynamic Playlists, Tagged Playlists, Live Data Feeds and Live Media Feeds are propagated in different way. Each of these entities has an underlying mRSS feed and after retrieving them from the presentation, a player checks for changes in each feed separately with a frequency defined by the TTL property of Tagged Playlists and Live Media Feeds in BrightAuthor:connected.

You can look for the sync.checkforcontent.request message received entries in the player's system log (available via the RDWS) to monitor these events. If the player is disconnected and/or does not accept messages, the server repeats them multiple times with decreasing frequency and eventually stops. The player also checks for missed settings and schedule updates every six hours and retries if it cannot reach bsn.Content, and requests settings and schedule from the server after each reboot.

BrightSign does not initiate any contact with BrightAuthor:connected or players. Users initiate connections, send requests, or subscribe to events, and the server replies. There are no cases when a server sends a request to a player, which would be impossible in most cases anyway since players are behind firewalls/gateways.