In this article, we will walk you through a typical SRT Listener configuration workflow to explain the various pieces that go into setting it up. We will look at the differences between ingress and egress and what that means in relation to the cloudSwXtch.
Step One: Setting up Your Aliases
The Aliases tab allows users to set friendly names or "aliases" for their streams and nodes so that it is easier to organize them in the Protocol Fanout tab. In this example, the user has named their stream SRT-listener -> MC 225.1.1.1:1599, inputting a stream IP of 225.1.1.1 and a Stream Port of 1599. This name is helpful for the user because it illustrates what they hope to do when setting up for Protocol Fanout. They are going to set up for an SRT to MC conversion using the stream IP and Stream Port assigned to the name.
.png?sv=2022-11-02&spr=https&st=2025-08-02T01%3A30%3A57Z&se=2025-08-02T01%3A42%3A57Z&sr=c&sp=r&sig=DldnGBdYb1rzSs9J4tv9V1aBLWG2qYi4JHqdQ4xtHPs%3D)
For more information about how aliases work, see the Aliases article under Configure cloudSwXtch with wXcked Eye.
Step Two: Adding Adaptors
In the Protocol Fanout Settings page, the user has set up two SRT Listeners. An SRT Listener configuration is telling the cloudSwXtch to listen for any incoming messages from endpoints ready to send/receive SRT data. This method of transmission is considered to be more user-friendly since a user will not have to worry about pointing to a specific IP address. It places the burden of targeting on the endpoint instead.
The user has set up SRT Listener for both Egress and Ingress using the Alias assigned earlier: SRT-Listener -> Multicast 225.1.1.1:1599. When differentiating between Egress and Ingress, always imagine it from the perspective of the cloudSwXtch:
SRT Listener Ingress
For Ingress, think about the cloudSwXtch Ingesting a stream. The user has set up an SRT Listener Ingress using the SRT-Listener -> Multicast 225.1.1.1:1599 stream with Listener Port 1599. That means that an endpoint will have to target port 1599 to send SRT traffic to the cloudSwXtch. Since it is ingress, the cloudSwXtch will automatically convert the SRT stream it receives into multicast.
Using the Topology in wXcked Eye, you can see how SRT Listener Ingress is set up in relation to the cloudSwXtch below.
The endpoints highlighted will then request and receive multicast traffic via IGMP join to 225.1.1.1:1599.
SRT Listener Egress
For Egress, imagine the stream EXITING the cloudSwXtch (->). In this example, the user has set up SRT Listener Egress using the SRT-Listener -> Multicast 225.1.1.1:1599 stream and opening Listener Port 6000. That means that an endpoint will have to target port 6000 and let the cloudSwXtch know that it would like to receive SRT traffic. Note that this is a 1:1 connection, meaning only one SRT endpoint can use the listener port. In the example below, an endpoint has requested the SRT traffic and the cloudSwXtch is sending it out 140pps via port 6000.
