← Back to Articles
Manually configure downstream SCTE 55-1 OOB multiplexer
Last Updated: July 07, 2026
Create a transport stream and follow the procedure to configure input ports and their priorities to complete the OOBM configuration.
  1. Log in to the EM, https://<VPS #2_IP_address>:5557.
To configure OOBM TS
  1. Click OOBM tab on left navigation pane.
  2. Choose the specific server on which you want to create the OOBM transport stream from the drop-down list.
  3. Click Add icon to create a TS and configure the OOBM input and output interfaces for the TS.
  4. Click OOBM Config button and enter the values as necessary:
    ParameterDescription
    TS Name

    (Optional)

    Enter a unique descriptive name. The name is a case-sensitive string of up to 64 characters. Valid characters are:

    a-z, A-Z, 0-9, @, +, #, _ (underscore), and - (hyphen).

    Mute Output TS

    Unchecked or disabled by default. Check this box to prevent the output stream from being transmitted to the RPD or RMD. The mute function mimics an EQAM channel mute capability.

    DEPI

    Select the DEPI option, if the OOB Multiplexer output is intended to be transmitted to an RPD / RMD.

    Session ID

    (Range: 0x0 - 0xFFFFFFFF)

    Set a unique session ID for DEPI output stream. Use the session ID that matches the session ID of the downstream SCTE 55-1 channel for which the DEPI transport stream is destined.

    Destination IP

    Enter the destination IP address of the transport stream, as indicated in the site network plan. This may be a multicast IP or a destination IP for a unicast stream. Destination IP and Output interface have to be of the same type (IPv4 or IPv6).

    Destination UDP

    (Range: 1024-65535)

    Enter an UDP port in the case of IP (IPv4 or IPv6) output. If DEPI is enabled, then UDP port field is disabled.

    Output Interface

    Select the output interface IP from the drop down menu. This defines the output IP along with the VUE server to send the output stream. If VUE server is part of a redundancy cluster this must be a VIP.

    NOTE:

    If you have selected a specific VUE server from the drop-down list, then only the output interface IP of that server will be available.

    The type of IP selected (IPv4 or IPv6) must be the same as the type of destination IP entered. For example, if an IPv6 multicast destination IP was entered, the selected interface IP must be an IPv6 address. If the destination IP is an IPv4 address, then the selected interface IP must be an IPv4 address.

    MPEG/UDP Packing Count

    Set the value to the maximum number of MPEG packets to be transmitted in each UDP frame. Default count is 5. If DEPI is enabled, the range is 1 to 10. If the DEPI is disabled, the range is 1 to 7.

    An MTU configuration of 1500 supports DEPI output packets with up to 7 MPEG packets per Ethernet frame. An MTU configuration of 2000 supports DEPI output packets with up to 10 MPEG packets per Ethernet frame. Output MTU size in bytes.

    Input Interface

    Set Input Interface IP to receive OOB data. Input Interface acts as the control interface to receive OOB input streams (control interface should be on the OAM&P network in which the DAC is present).

    The OOBM Input Interface must be a unique IP for each VUE OOBM Pipe container. This IP is typically a VIP as only 1 OOBM pipe container can use the static management IP interface.

    If the VUE server is part of a redundancy cluster this must be a VIP.

    Enable PID Generator

    Check the box to enable PID Generator.

    The PID Generator is an internal input interface that can be enabled from the DAC to carousel data, such as during an EAS event. The PID Generator itself cannot be directly provisioned in the EM.

    PID Generator periodically inserts MPEG packets from its internal message store to the output transport stream.

    By default, PID generator is enabled.

    Access Control IP

    Enter the access control IP address (DAC IP Address). 0.0.0.0 indicates that no DAC is configured.

    Access Control TCP Port

    (Range: 1024-65535)

    Enter the access control TCP port (DAC Port). Default value is 5167.

To configure input port
  1. Click Input Port Config button to configure the input ports.
    You can configure a maximum of 14 input UDP ports.
  2. Click More options icon on the corresponding port to modify or enable the input port.
    1. Select Enable.
    2. Enter the values as necessary:
      ParameterDescription
      Input Name

      (Optional)

      Assign an input name to the port.

      Priority

      Select the priority of the port from the drop-down list (High, Medium, or Low). The default is Medium.

      UDP Port

      Enter the UDP port number.

      Multicast IP

      Enter the multicast input IP address.

      Source IP

      Enter the multicast input Source IP address.

      Configure Secondary Server Input (Initial Standby server)

      This option allows you to configure a secondary input stream to receive a mapping. Selecting this options allows you to enter a secondary input multicast IP, secondary input source IP, and secondary input UDP port. If this stream is configured on a server that is part of Redundancy Cluster these secondary parameters will be used on the initial standby server only. The input multicast, input UDP port, and input source will always be used on the initial active server.

      NOTE:

      This option is used only for HA 1:1 server redundancy.

      Secondary Input UDP

      Optional parameter when using HA 1:1 server redundancy. Input UDP port to receive the video data on the initial standby VUE server.

      Secondary Input Multicast

      Optional parameter when using HA 1:1 server redundancy. Multicast address to receive the video data on the initial standby VUE server. Leave blank for unicast reception.

      Secondary Input Source

      Optional parameter when using HA 1:1 server redundancy. Multicast input Source IP address (for IGMP v3 multicast reception) on initial standby VUE server. Leave blank for unicast reception.

    3. Click Add icon to add PID mappings.
      NOTE: By default, no PID mappings are configured. If no PID mappings are configured then all the traffic in the input TS is dropped.

      For more information about values to be configured for passthru mappings, block PIDs, and remap PIDs, see PID remapping/filtering.

    4. Enter Input PID and Output PID.

      Valid values can be -1 or any value from 0 to 8190 (The values can be decimal or hexadecimal).

      To modify or delete the PID mapping values click the More options icon icon for the corresponding PID. To delete all the PID mappings at once, click the Delete All button.

    5. Click OK to save the values or Cancel to cancel the configuration.
To configure MLM
  1. Click MLM Config.
  2. Select Enable MLM.
  3. Select the priority of the port from the drop-down list (High, Medium, or Low). The default is Medium.
    For example, set the priority for interactive and SDV traffic to High, RADD traffic to Medium, and code download to Low. The priority you set here overrides the priority you set for the logical port on the input.
  4. Click Add icon to add MLM PIDs.

    You can add up to 8 MLM PIDs. Valid PID values are 0 to 8190 (The values can be decimal or hexadecimal).

    To modify or delete the PID mapping values click the More options icon icon for the corresponding PID. To delete all the MLM PIDs at once, click the Delete All button.

    NOTE: MLM PID priority overrides the input port priority for MLM PIDs.
  5. Click Submit to save the values or Cancel to cancel the configuration.
To configure PBQ PIDs
  1. Click PBQ PIDs.

    OOBM allows you to enable Priority-Based Queuing on a per-PID basis, rather than on a per input port basis. Certain PID streams from RADD requires to be processed with high priority. EMM and Network PID traffic prioritizes over code download streams. You can prioritize and de-prioritize additional PIDs based on the system requirements.

  2. Select Enable PID Based PBQ.
  3. Click Add icon to add PID based priority queuing.

    You can add up to 10 PBQ PIDs. Valid PID values are 0 to 8190 (The values can be decimal or hexadecimal). Valid Input Port Number can be from 3 to 16.

    1. Enter Input Port Number and Output PID.
    2. Select the priority of the port from the drop-down list (High, Medium, or Low). The default is Medium.

      To modify or delete the PID PBQ values click the More options icon icon for the corresponding PID. To delete all the PID PBQ configuration at once, click the Delete All button.

  4. Click Submit to save the values or Cancel to cancel the configuration.
To configure EAS
  1. Click EAS Config.
  2. Enter the Proxy EAS Input Port Number and Input Port Number to Block.
    A valid Proxy EAS Input Port Number can be either 0, or any value from 3 to 16. The default value is 0, which means EA event cannot be triggered. When traffic is received in Proxy EAS Input Port Number, OOBM treats as Emergency Alert event.

    A valid Input Port Number to Block can be any value from 3 to 16. The default value is 0, which means no input port or PID has to be blocked.

    Enter the logical input port number in the Input Port Number to block field. This port carries traffic that should be blocked during an EAS event. Unless MLM is in use, generally this will be the RADD port.

    DAC allows you to block an input port during EAS event which is OM Port To Block parameter in DAC (in EAS service tunables). OOBM pre-defines the input port number for each input stream. You should only configure the input port numbers from 3 to 16 in DAC. Input port numbers, 1 and 2 are not supported in OOBM as 1 is prefixed for output and 2 is for internal PID generator.

  3. Enter the EAS Timeout (seconds).
    Timeout for EAS event begins after no input is received in Proxy EAS Input Port Number.
  4. Click Add icon to add the PID number to block.

    EAS supports up to 4 PID numbers. In Emergency Alert PID fields, enter the values of incoming PIDs that should be dropped and replaced with EAS information.

    As a general guideline, the specified PIDs should include two EMM PIDs and one network PID as used on your system to configure Emergency Alert. For future expansion, a fourth PID can be specified.

    To modify or delete the values of PID number to be blocked click the More options icon icon for the corresponding PID. To delete all the blocked PIDs at once, click the Delete All button.

  5. Click Submit to save the values or Cancel to cancel the configuration.