Configure your encoder for IAS

To use IAS, you need to send all ingested streams from the encoder to the IAS client, instead of directly to the Akamai servers.

Prefix the encoder's ingest URLs with the IP address and port number you set for an encoder listening point on the machine running the IAS client. Consider these points and requirements:

• You should choose ports higher than 1024 and exclude transient ports for a particular OS.

• For best performance, install the IAS client on the same system that's running the encoder. If you've done this, the IP address and port number will be a local host or local network address.

• All streams from the same encoder should use the same encoder listening point.

Here's an HLS example, if the encoder listening point is 127.0.0.1:1773 (IP address:port):

Here's an RTMP example, if encoder listening point is 127.0.0.1:1773 (IP address:port):

IAS ingest limits

To maintain a stable environment, IAS enforces ingest limits on streaming data coming from your encoders. There is an upper and a lower ingest limit. These are in place to define warning level and hard stop thresholds.

• The upper IAS ingest limit is 75 Mbps. This is averaged over a 30-second period. If this is exceeded, IAS displays bitrate is critical in the UI. Streaming stops and reconnects when the bit rate is lower than 75 Mbps.

• The lower limit is 50 Mbps. This is also averaged over a 30-second period. If this is exceeded, IAS displays bitrate is high in the UI. Streaming continues unaffected. The warning is to caution you to check that you have not set up your encoder to exceed this limit.

📘

Some encoders may burst higher bitrates than what is configured for short periods of time and this should be taken into consideration when configuring the total bit rate per port.

The IAS client is capable of handling up to 50 Mbps of incoming data on each IP/port listening point. If an encoder needs to ingest more than this, add and apply multiple encoder listening points so that each one is only handling about 50 Mbps. All the chosen IP/ports should then be added in the IAS UI. The interval between 50 Mb and 75 Mb is there to support short-term variations in bit rate. Don't leave IAS running indefinitely with the bitrate is high (50 Mbps) warning. See Performance warnings and error states for more details and recommendations.

IAS and firewall ports

IAS deviates from the standard encoder process, which may create difficulty if you're trying to install it behind a corporate firewall. Typically, the standard encoder process is to push video over RTMP (Port 1935), and push manifests, segments and keys over HTTP (Port 80). Ingest acceleration deviates from this standard.

We recommend that you install IAS on the same machine as the encoder, or on the same internal LAN as the encoder network. So, there are both internal (LAN) and external (WAN) requirements.

• Encoders ↔ IAS machines. TCP Port XXXXX - port configured in the IAS listener. You can configure this in the Ingest Acceleration UI.

• Management network ↔ IAS machines. TCP Port 11939 - Administration interface.

  • Edit the PORT and IP address value in the setup.xml file on a Linux machine. Here's an example setup.xml file.

      <?xml version="1.0"?>
      <config IasPm="ias" IasWorkerPm="ias_worker" Variant="IAS"
      HuginPm="" Broadcaster="true" PmMaxSessions="4" PmTimeOut="3m"
      IasIpp="127.0.0.1:11939">
       <log type="NORMAL" ratelimit="2000">
       <console enabled="false"/>
       <file enabled="true" rotationsize="10000000" rotationcount="5" nodate="false"/>  
       <server enabled="false"/>
       </log>
      </config>
  

  • You can change the LOCAL (127.0.0.1) IP address to an accessible IP address from a local network. This lets you to manage the IAS remotely via the web interface. If you change the IP address, you must update the preconfigured listening ports on the local host.

• IAS Machine(s) ↔ Akamai ingest target entrypoint

  • TCP and UDP Port 53. DNS resolution of entrypoint
  • UDP Port 123. Access to Akamai NTP servers
  • TCP and UDP Port 11938. Listening port for the server. It starts with UDP, and connects over TCP if UDP is blocked.
  • TCP Port 80. Backend services
  • TCP Port 443. Backend services