NAME

       srt-multiplex - manual page for srt-multiplex 1.3.2-1

SYNOPSIS

       srt-multiplex <SRT URI> [-i INPUT...] [-o OUTPUT...]

DESCRIPTION

   SIPLEX is a program that demonstrates two SRT features:
              -  using  one  UDP  outgoing  port  for multiple connecting SRT sockets - setting a
              resource ID on a socket visible on the listener side

       The <SRT URI> will be input or output depending on the further  -i/-o  option.   The  URIs
       specified  as  -i INPUT... will be used for input and therefore SRT for output, and in the
       other way around if you use -o OUTPUT...  For every such URI you must specify additionally
       a  parameter  named  'id',  which  will  be interperted by the application and used to set
       resource id on an SRT socket when connecting or to match with the id  extracted  from  the
       accepted socket of incoming connection.  Example:

       Sender:
              srt-multiplex srt://remhost:2000 -i udp://:5000?id=low udp://:6000?id=high

       Receiver:
              srt-multiplex srt://:2000 -o output-high.ts?id=high output-low.ts?id=low

       Here  you  create  a  Sender  which will connect to 'remhost' port 2000 using multiple SRT
       sockets, all of which will be using the same outgoing port. Here the port is  autoselected
       by  the  first  socket when connecting, every next one will reuse that port. Alternatively
       you can enforce the outgoing port using 'port' parameter in the SRT URI.

       Then for every input resource a separate connection is made and  appropriate  resource  id
       will  be  set  to  particular  socket  assigned  to  that  resource  according to the 'id'
       parameter.  When the listener side (here Receiver) gets the socket accepted, it will  have
       the  resource  id set just as the caller side did, in which case srt-multiplex will search
       for this id among the registered resources and match the resource (output here) with  this
       id.  If  the  resource  is not found, the connection is closed immediately. This works the
       same way regardless of which direction is used by caller or listener