# Setting up an RTP push input RTP push input This section describes how to set up an upstream system that uses the RTP Push protocol to deliver source content from an upstream system that is in your VPC from Amazon VPC. It describes how to set up the source content on the upstream system, and how to create an input that connects the upstream system to MediaLive. With an RTP push source, the upstream system *pushes* the content to MediaLive. To perform this setup, you must work with an operator at the upstream system. **Topics** + [ # Obtain information ](setup-rtp-push-obtain-info.md) + [ # Create an input security group ](setup-isg-rtp-push.md) + [ # Create an RTP input ](setup-input-rtp-push.md) + [ # Ensure correct setup on the upstream system ](setup-uss-rtp-push.md) + [ # Result of this procedure ](setup-result-rtp-push.md) # Obtain information Step 1: Obtain information Obtain the following information from your contact person at the upstream system: + The public network IP addresses. You need two sets of IP addresses because an RTP input is always a [standard-class input](class-channel-input.md), even if your channel is a single-pipeline channel. For information about input classes, see [Choosing the channel class and input class](class-channel-input.md). These are the sets of IP addresses where the source or sources for the content will appear on the public network. You need this information to create the input security group. For example: + For one source: `203.0.113.19, 203.0.113.58, 203.0.113.25` + For the other source: `198.51.100.19, 198.51.100.59, 198.51.100.21` # Create an input security group Step 2: Create an input security group You must create an input security group. The security group must allow the *public network IP addresses* to push to MediaLive. Following from the earlier example, it must allow these addresses: 203.0.113.19, 203.0.113.58, 203.0.113.25, 198.51.100.19, 198.51.100.59, 198.51.100.21 For details about creating an input security group, see [Creating an input security group](create-input-security-groups.md). # Create an RTP input Step 3: Create input After you have created the input security group, you can create the RTP push input. **To create an RTP push input** 1. Make sure that you have the information from [step 1](setup-rtp-push-obtain-info.md). 1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/). 1. In the navigation pane, choose **Inputs**. On the **Inputs** page, choose **Create input**. 1. Complete the **Input details** section: + **Input** name – enter a name. + **Input type** – choose **RTP**. 1. In the **Network mode** section, choose **Public**. 1. In the **Input security group** section, specify a group to attach to this push input. You can choose an existing group, or you can create a group. For more information about security groups, see [Working with input security groups](working-with-input-security-groups.md). The security group must allow the public network IP addresses to push to MediaLive. Following from the example in step 1, it must allow these addresses: 203.0.113.19, 203.0.113.58, 203.0.113.25, 198.51.100.19, 198.51.100.59, 198.51.100.21 For more information about security groups, see [Working with input security groups](working-with-input-security-groups.md). 1. In the **Tags **section, create tags if you want to associate tags with this input. For more information, see [Tagging resources](tagging.md). 1. Choose **Create**. MediaLive creates the input and automatically creates two endpoints on that input. These endpoints include the port 5000. For example: `198.51.100.99:5000` `192.0.2.18:5000` Note that the IP addresses are addresses that MediaLive creates. They aren't the public addresses that you used in the security group. For a diagram that shows the role of all the IP addresses, see [Result of this procedure](setup-result-rtp-push.md) in the section about setting up an RTP push source. MediaLive always creates two endpoints: + If you will set up the channel as a standard channel, both endpoints will be used. + If you will set up the channel as a single-pipeline channel, only the first endpoint will be used. MediaLive won't expect to receive content at the second endpoint. 1. Provide the upstream system with the following information: + If you will set up the channel as a standard channel, provide both locations. The upstream system must push the video streams to these locations. + If you will set up the channel as a single-pipeline channel, provide only the first location. The upstream system must push its one stream to this location. For example, provide these addresses: `198.51.100.99:5000` `192.0.2.18:5000` **Result of this procedure** As a result of this setup, an RTP push input exists that specifies two URLs. These URLs are fixed for the lifetime of the input, regardless of changes that occur (such as modifying other information in the input, or attaching the input to a different channel). The upstream system pushes the source content to these endpoints. Keep in mind that with a push input, the upstream system must be pushing the video source to the input when you start the channel. The upstream system does not need to be pushing before then. For a description of this setup that includes a diagram, see [Result of this procedure](setup-result-rtp-push.md) in the section about setting up an RTP source. # Ensure correct setup on the upstream system Step 4: Set up upstream system You must make sure that the upstream system pushes content to the correct locations in MediaLive. **To set up for a standard channel** Follow this procedure if the MediaLive channel is a [standard channel](plan-redundancy.md). 1. Provide the operator with this information: + The two endpoints (URLs) that MediaLive generated when you created the RTP input. These endpoints are the addresses in the blue boxes in [the diagram after this procedure](setup-result-rtp-push.md). The URLs include port 5000. For example: `198.51.100.99:5000` `192.0.2.18:5000` 1. Make sure that the operator sets up properly for a standard channel. They must: + Deliver two sources that are identical in terms of video resolution and bitrate. + Make sure that the sources appear on the agreed IP addresses on the public network. For example: + For one source: `203.0.113.19, 203.0.113.58, 203.0.113.25` + For the other source: `198.51.100.19, 198.51.100.59, 198.51.100.21` You used these addresses when you created the input security group. If the upstream system doesn't use these addresses, MediaLive will refuse the push. + Push to the correct URLs on MediaLive. For example, they must push to: `198.51.100.99:5000` `192.0.2.18:5000` + Send over RTP, not UDP. The UDP protocol is not supported for an input into MediaLive. **To set up for a single-pipeline channel** Follow this procedure if the MediaLive channel is a [single-pipeline channel](plan-redundancy.md). 1. Provide the operator with this information: + Only the first of the two endpoints (URLs) that MediaLive generated when you created the RTP input. This endpoint is one of the addresses in the blue boxes in [the diagram after this procedure](setup-result-rtp-push.md). The URL includes port 5000. For example: `198.51.100.99:5000` 1. Make sure that the operator sets up properly for a single-pipeline channel. They must: + Make sure that the source appears on the agreed IP addresses on the public network. For example: `203.0.113.19, 203.0.113.58, 203.0.113.25` You used these addresses when you created the input security group. If the upstream system doesn't use these addresses, MediaLive will refuse the push. + Push to the correct URL on MediaLive. For example, they must push to: `198.51.100.99:5000` + Send over RTP, not UDP. The UDP protocol is not supported for an input into MediaLive. # Result of this procedure As a result of this setup, an RTP input exists that specifies one or two *endpoint* URLs. These endpoints are on MediaLive and are fixed for the lifetime of the input, regardless of changes that occur (such as modifying other information in the input, or attaching the input to a different channel). The upstream system has been set up to push the source content to the two endpoints (for a standard channel) or to the first endpoint (for a single-pipeline channel). An input security group has been associated with the input. This input security group has a CIDR block that covers the two URLs that the upstream system pushes, which ensures that MediaLive accepts the pushed content. Keep in mind that with a push input, the upstream system must be pushing the video source to the input when you start the channel. The upstream system does not need to be pushing before then. At runtime of the channel, MediaLive reacts to the content that is being pushed and ingests it. ![\[Upstream system diagram showing IP addresses, RTP inputs, and Input Security Group.\]](http://docs.aws.amazon.com/medialive/latest/ug/images/rtp-push-uss-input.png)