iDirect Evolution X1, Installation Manual

Page: 72 / 130

56 iDirect Satellite Router Installation and Commissioning Guide
iDX Release 3.3
Loading Options Files with Web iSite
10.2 Downstream Template
Evolution X1, X7, and e150 Satellite Routers support the Downstream Template feature in Web
iSite. The Downstream Template is provided as an option to speed commissioning of large
numbers of remote sites by avoiding the requirement for the installer to obtain and manage a
large number of individual options files. This feature also allows the Satellite Router to
receive its remote software package over-the-air from the NMS as part of the commissioning
procedure.
The Downstream Template contains the minimum information necessary to enable reception
of the downstream broadcast from the hub. Remote sites with a common downstream
channel, e.g., Inroute Groups using the same network and remote site LNB parameters, can
use a single Downstream Template file to enable reception on all the Satellite Routers in that
network. Once the Downstream Template is loaded and the Satellite Router locks to the
downstream carrier, the Network Operator can use iBuilder to download the remote software
package and the remainder of the site-specific options data over-the-air from the NMS. A
separate Downstream Template file is required for each discrete downstream channel or
network.
Note: The downstream template is only available for X1 Satellite Routers already
running iDX Release 3.2 or later. The software version is displayed on the Web
iSite dashboard. See
Figure 29 on page 48 .
Note: In the absence of a downstream template, the downstream parameters can be
entered manually on the Web iSite Downstream Configuration page ( Figure 37 ).
The Downstream Template file is produced by the Network Operator. It is a text file in JSON
format that can be viewed and edited with a text editor such as Notepad. Downstream
Template files must have the .json file extension in the file name.
Figure 36 shows an
example of a Downstream Template JSON file.
Figure 36. Downstream Template: Example
To Load the Downstream Template: