Recasting UDP->TCP

Unlike UDP, which is connectionless and lacks a persistent link between sender and receiver, TCP requires the establishment of a reliable connection before data exchange commences. This connection serves as a conduit for the organized and guaranteed delivery of data packets, mitigating the risk of loss or disorder inherent in UDP streams. While TCP ensures reliable data delivery, it introduces latency, making it less optimal for video streaming. Therefore, this streaming option should be viewed as a last resort, prioritizing use cases where data integrity takes precedence over potential latency concerns.

Configuration

Recasting a stream from UDP to TCP involves configuring the input channel to receive a UDP stream and the output channel to transmit the stream over a TCP connection. This process ensures reliable and connection-oriented delivery of previously connectionless data.

Input Configuration

To set up the UDP input for recasting to TCP, users must configure the application to receive the incoming UDP stream.

Output Configuration

To configure the TCP output channel for UDP-to-TCP recasting, users must define the destination for the recast stream and ensure a persistent TCP connection is established.

YAML Configuration

Here is an example of how to configure the recaster to receive a multicast stream on the address 227.1.1.1 and port 30120, then send it to a TCP target. Please note that the recaster will attempt to establish a connection with the specified TCP target before transmitting the data. If no connection can be established, an error message will be displayed at the target.

platforms:
  - name: UAV1
    description: First platform
    channels:
      - name: EO-IR
        description: First channel
        input:
          name: EO/IR
          description: EO/IR-1 camera
          url: udp://227.1.1.1:30120
        outputs:
          - name: EO/IR-1-OUT
            description: EO/IR-1 output
            url: tcp://192.168.1.2:1234