Comtech EF Data CME-5000 Manual - Manual (Page 53)

Digicast Micro Encapsulator (MENCAP) Revision A
Device Management via User Interfaces MN/MENCAPEDC.IOM
In normal mode, the routes are handled as either Multicast or Unicast routes.
In TCP-to-UDP mode, incoming routes are expected to be received as TCP on a
known port number and the UDP packets are extracted from the TCP packets and
forward as Multicast to the egress port. TCP-to-UDP allows the KenCast server
(Fazzt) to use TCP (a connection oriented protocol) to deliver UDP datagrams
over a reliable delivery method, resulting in minimum loss of data due to egress
overflow.
When used in conjunction with SMPTE 325M, this feature allows a multiplexer
to provide real-time (or near real-time) feedback to the MENCAP 50, which in
turn uses the TCP-to-UDP mechanism to flow control the flow of data. This
technique allows error free communication over a data link, while maximizing
the available bandwidth.
TCP to UDP Port
The TCP to UDP Port allows the user to configure the MENCAP 50 to listen to a
defined (unreserved) port number (>= 1,024), for that route, for a connection
request from the server.
VLAN
VLAN support options:
NONE – No VLAN traffic will be passed. Only traffic without a VLAN tag will
be passed
All – All traffic received with VLAN tags will be passed and all non-VLAN
traffic will be blocked
VLANID – ID must match the VLAN ID field. If the VLANID is set, only
traffic on the configured VLAN ID will be passed
VLAN ID
A valid VLAN ID for the desired route. The valid ranges of the VLAN ID are
0 to 4095.
Include PSI
Allows the user to select whether the route is present or not present in the PSI
table. The PSI must be enabled for the route to be included in the PSI table.
ZAP
Available only on the terminal or Telnet. This feature is used for customers who
need to modify a parameter on every configured route on the MENCAP 50.
4-15