Third Party Multicast Configuration

This section describes how a network can make use of third party multicasting solution for content distribution.


Many large scale networks make use of IP multicasting to diffuse information. With IP multicasting, network bandwidth can be conserved because a single stream of information can be sent to many destinations. This can be used along with satellite broadcast technology to spread information throughout a network without using up bandwidth to repeatedly send information that has already been sent. There are multiple satellite broadcast solutions on the market at this time and it is possible to integrate these into a digital signage network using Broadsign Core.

The following illustration demonstrates how a network making use of a third-party satellite broadcast solution could look:

Third-Party Multicast

In the above illustration, two physically separate sites are shown, each with its respective edge server. When a player determines it needs new content, it will request the content from its associated edge server over port 10805. If the edge server does not have the content in question, it will request it from Broadsign Server over port 10805. Note that player control information will be communicated directly from the Server (not shown in the illustration), transmitted over port 10799.

When an edge server is associated to an upstream edge server through Broadsign Administrator, all requests for content which it does not have will be passed on to Broadsign Server. Broadsign Server will then transmit the requested content to the associated satellite broadcast server. The satellite broadcast server is then responsible for transferring the content to all associated edge servers, including the original edge server that made the request. When the edge server verifies it has received the content it needs, it will then transfer the content to the player that initiated the request.


Configuring a network to use a third party multicasting solution requires that at least one edge server and one player are properly configured as described in their respective configuration guides.


To configure a network to transmit content to edge servers through a satellite broadcast instead of directly over port 10805, you need to perform the following steps:

    • Step One: Register a satellite broadcast server with Broadsign.
    • Step Two: Configure the upstream Edge Server through the Administrator.
    • Step Three: Associate the upstream Edge Server to regular Edge Server(s).
    • Step Four: Configure the third party multicasting client on the Edge Server.
Step One: Register a Satellite Broadcast Server with Broadsign Support

The Registering a satellite broadcast server consists of providing Broadsign Support with the FTP site drop box which is monitored by the satellite broadcast server. This information can be sent to Broadsign Support by email at

Once the satellite broadcast server’s FTP site has been registered, a notification email will be sent in return and an upstream Edge Server representing the satellite broadcast server will be made available within the Edge Servers section of the Administrator.

Please note that the FTP site being registered with Broadsign Support must be configured to prevent simultaneous access to files to prevent incomplete files from being transmitted. Additionally, passive mode connections to FTP servers are not currently supported. Be sure that the FTP site in question accepts active, port mode connections.

For more information on upstream Edge Servers, see Broadsign Edge Server.

Step Two: Configure an Upstream Edge Server

Once the upstream Edge Server is available in your domain, edit the upstream Edge Server, navigate to the Protocol tab and enter the “Path to ad copies” which is the directory on the FTP server that is being monitored for content. If a username and password are needed, they can be entered at this time as well.

Step Three: Associate the Upstream Edge Server

Upstream location
Edge Servers that should receive content via satellite need to be associated to an upstream Edge Server through the Administrator. This association informs the Server that content requests from the Edge Server in question should be transmitted through the satellite’s FTP site instead of directly over the Internet.

To associate a Edge Server to an upstream Edge Server, edit the Edge Server in question, navigate to the Upstream tab and select the upstream Edge Server through which content transmissions should be made.

Step Four: Configue the Third Party Multicasting Client

The third party multicasting client should be installed and configured on the system running the Edge Server. For specific steps on how to install this client, please refer to the third party client’s installation manual for configuration information.

The following requirements must be addressed when configuring the client:

    • To allow the Edge Server to detect that new content is available, content needs to be saved to the Edge Server’s document root.
    • It is important that the multicasting client be configured to save temporary or incomplete files in a directory other than the Edge Server’s document root.
    • It is important that the temporary directory is selected be located on the same partition as the Edge Server’s document root to ensure that content is moved atomically to prevent the Edge Server from transferring partial files.