IFB - Cube - Bond - Slice 100-500 series

To use IFB:

1. plug the mic / audio input into the headphone jack on the Cube Decoder

2. plug headphones into the headphone jack on the Cube Encoder

3. go to Video Setup -> Stream Settings, change to MPEG TS, and select the option to enable IFB

4. on the Decoder, go to Video Setup -> Decoder Settings, change to MPEG TS and enable IFB

The IFB port will be +10 for the port used for MPEG TS. Example:
(a) if you're sending to 9710/UDP on the Decoder, IFB will be on 9720/TCP
(b) if you're sending to 10040/TCP on the Decoder, IFB will be 10050/TCP

Note:
* the IFB will always be TCP, regardless of whether the main stream is UDP or TCP
* if your Cube Decoder has Wi-Fi, we suggest disabling Wi-Fi (if possible), as using IFB places a higher load on the Decoder at this point in time

-----------------

1. Here's physical information on what's needed for IFB:

* The IFB input (on the Cube Decoder side with the headset icon) uses Apple-compatible headsets such as the Apple EarPods (from the tip: Left / Right / Ground / Mic, respectively, for the four different conductors on the connection).

* The input is mono, unbalanced, mic level.

* Note that the same connector carries both output (for headphones) and input (for mic).

* We haven't tested headsets directly beyond the Apple EarPods, but other customers have reported back on using a Sony URX-P2, or the headset/mic included with their Samsung Galaxy Note 2 phone.

2. Below is network information on what's needed for IFB; We'd suggest first testing it on a local network (Cube Encoder to Cube Decoder) so you can see the workflow and not worry about firewalls getting in the way. Then, you can move on to testing with Sputnik.

Cube to Cube (LAN)

* The Cube Encoder will contact the Cube Decoder on a TCP port that's +10 on the MPEG TS port. This is regardless of whether the streaming protocol is UDP or TCP.

* For example, if the Cube Encoder is sending to port 9710/UDP on the Decoder, it will contact the Decoder at 9720/TCP for the IFB port.

* If the Cube Encoder is sending to port 8850/TCP on the Decoder (for streaming across the Internet), it will contact the Decoder on port 8860/TCP for IFB, so you'd need to have port forwarding rules set appropriately once you introduce firewalls.

With Sputnik:

Currently only Bond (Bond I+Cube, Bond II), and Bond Pro work with IFB for Sputnik.  The Bond devices must be in Bonding Mode.

*On the bond, if you send over a single Ethernet connection and they have a Cube + Bond, or Bond II/Pro, using a USB to Ethernet adapter and having the device in the Bonded mode will give better overall performance even over just that single connection, compared to in the standalone Single mode on those devices.

* if the Bond/Cube encoder  has set TCP Server Mode to enabled, then the IFB port will be +10 from the TCP Server port. For example, a TCP Server port of 5002/TCP will use an IFB port of 5012/TCP. Note that the proper ports (both hardware firewall in front of your LAN, and software firewall on the Sputnik server) must forward through the proper ports!

* if the Bond/Cube encoder does not have TCP Server Mode enabled and is just using a Push, it will be +10/TCP from the MPEG TS port you're pushing (either UDP or TCP). It will behave the same as in the standalone examples cited above.

* if the Bond/Cube encoder has both TCP Server Mode and Push mode simultaneously going, TCP Server mode and port will always take priority and will override the Push stream port, so always know that the IFB port is based off the TCP Server port when you have this enabled, and make sure the Decoder is set to use a TCP Pull in order for it to use IFB.

General notes:

* only one Encoder and one Decoder can work with IFB -- you can't pair multiple Decoders with IFB enabled to a single Encoder, or the opposite way around (multiple Encoders to a single Decoder with IFB enabled).

* To enable/disable IFB click Show Advanced Settings in the bottom right hand corner.