Fuse-IP is a proprietary Tieline IP bonding technology which aggregates data by bonding multiple IP interfaces (peers) and establishing a “tunnel” between two Tieline codecs. A streaming connection can be established after the tunnel is created and Fuse-IP automatically distributes data over any two bonded interfaces.

 

Bridge-IT only has a single LAN interface, however it can still connect as a fuse Fuse-IP server or client. This means Bridge-IT can stream data between itself and another codec which is bonding over multiple IP interfaces.

 
There are several benefits in using Fuse-IP to aggregate data from multiple IP interfaces, including:

 

•The ability to create more stable connections with higher overall data bandwidth.

•Greater choice of encoding algorithms because of higher available bandwidth.

•Redundancy in case one IP connection is lost.

 

How does Fuse-IP work?

Fuse-IP is another Via interface you can use to dial, similar to selecting a LAN port or Wi-Fi.

 

 

Fuse-IP requires one codec to be a server and the other codec is the client. Normally the remote codec is configured as the client and the studio codec is the server, because it's generally easier to dial static IP addresses configured at the studio than interfaces at the remote site. Like SmartStream PLUS redundant streaming, you can use two IP interfaces at the studio for additional redundancy.

 

Prerequisites

Version 2.16.xx firmware is required to use Fuse-IP. Before configuring Fuse-IP you need:

 

•The IP address (or addresses) for the codec acting as the server at the studio.

•The serial number of the server codec to which you are connecting using Fuse-IP.

 

Configuring a Fuse-IP Server at the Studio

1.Press the SETTINGS button.

2.Use the down navigation button to select Fuse-IP and press the button.

 

 

 

3.Navigate down to Fuse-IP Mode and press the button to select Server if the codec is at the studio and not initiating the connection. Note: the server codec serial number will be displayed and needs to be entered into the Fuse-IP client codec.

 

       

 

4.Leave the default Fuse-IP Port as 8999 in most situations unless this port is already in use, e.g. you have multiple codecs behind a firewall using Fuse-IP, therefore you need to allocate a different port for each Fuse-IP tunnel. Note: the port number on the client and server codecs must be the same.

 

 

5.The codec is now configured to connect with a client codec over a Fuse-IP tunnel. Navigate up to Status and then press the button to create a Fuse-IP tunnel between the server and client codecs.

 

Configuring a Fuse-IP Remote Client

1.Press the SETTINGS button.

2.Select Fuse-IP and press the button.

 

 

 

3.Navigate to Fuse-IP Mode and press the button to select Client if it is a remote codec.

 

       

 

4.Leave the default Fuse-IP Port as 8999 in most situations unless this port is already in use, e.g. you have multiple codecs behind a firewall using Fuse-IP, therefore you need to allocate a different port for each Fuse-IP tunnel. Note: the port number on the client and server codecs must be the same.

 

 

5.Navigate to inactivity Timeout and press the button if you want to adjust the predetermined time period for turning the Fuse-IP tunnel off. Adjust the setting and press the button to store the new setting. Note: Inactivity Timeout can be configured from 0 to 1440 minutes. Enter 0 to disable the timeout.

 

 

6.Navigate to Srv. Address (server address) and press the button to enter a public static IP address associated with the bonded interfaces at the other codec, then press the button. Note: if the bonded interfaces have private addresses behind a firewall then port forwarding needs to be configured. See Installing the Codec at the Studio for more details on port forwarding.

 

       

 

7.Navigate to Server S/N (serial number) and press the button to enter the serial number of the server codec to which you are connecting, then press the button.

 

       

 

8.Navigate up to Fuse-IP Status and then press the button to create a Fuse-IP tunnel between the server and client codecs. Remember Fuse-IP must be enabled on both codecs. The Fuse-IP F symbol is displayed in the top right-hand corner of the screen to confirm two codecs have created an IP tunnel.

 

       

 

Please note: double-check all settings on both the server and client codecs if the message Started, waiting persists after starting Fuse-IP.

 

 

9.Select Fuse-IP as the Via interface with which to connect when creating a program using the front panel codec menus (see IP Via Mapping), or the HTML5 Toolbox Web-GUI Program Manager panel.