Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

How does BSN.cloud notify the player of new BrightAuthor:connected content?

...

Expand
titleExpand

You can look for the sync.checkforcontent.request message received entries in the player's system log (available via the remote DWS) 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. It also requests settings and schedule from the server after each reboot.

...

Do I need to configure my firewall to accept any inbound connections from BSN.cloud

...

?

Expand
titleExpand

No. 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.

The BSN.cloud Ports and URLs for Players and Software page lists the services and ports which BrightAuthor:connected and players access in outbound connections.

How can we identify HTTP calls on port 80 from the middleware vs. calls from elsewhere?

...

Expand
titleExpand

The BSN.cloud server expects each player to report its status every five minutes. If it does not, then player status is unhealthy (inactive?). The server does not talk to players to check how they are doing.