On this page, you will find reference material to help you configure BroadSign Core with various networking parameters.
|DSCP: BroadSign Control Information||10799||TCP||Outgoing||BroadSign Server Cluster (see “Destination Hostnames” below)|
|CTP: BroadSign Content Downloads||10805||TCP||Outgoing||BroadSign Server and Edge Server Cluster (see “Destination Hostnames” below)|
If you require BroadSign Creator content, you will need to configure the following networking parameter:
|HTTP: BroadSign Creator Content||80||TCP||Outgoing||BroadSign Creator|
|RDP: Windows Remote Desktop||3389||TCP||Incoming||Player’s IP|
|FTP: BroadSign Remote Diagnostics||21||TCP||Outgoing||BroadSign Remote Diagnostics Server|
|HTTP: BroadSign Crash Reporting||80||TCP||Outgoing||BroadSign Crash Report Server|
BroadSign Server Cluster (Port 10799 and 10805)
- bss.broadsign.com (for users of Broadsign Administrator)
Crash Reporting Server (Port 80)
BroadSign Remote Diagnostics Server (Port 21)
Sometimes, a site’s IT policy will require that BroadSign Server’s IP addresses be explicitly hard-coded into the firewall rules. We understand that sometimes it is necessary to comply with a third-party IT policy when piggybacking on another network. However, please take note of the warning below.
If absolutely required, the IP range of the primary BroadSign Server is:
- 18.104.22.168 to 22.214.171.124 (i.e. 126.96.36.199/24 in CIDR notation)
In addition, the following IPs are for disaster recovery purposes and should also be added to any firewall IP-based firewall rules: