Install the Media Flow Engine

Install the Media Flow Engine on a separate machine from your Converged Application Server.

The IP address must be reachable by both the RTP Proxy and the Converged Application Server.

Note:

Oracle recommends using two separate IP addresses: one for control traffic from the Converged Application Server, the other for receiving RTP packets from the RTP Proxy.

Download the Media Flow Engine installer tarball.
Set the JAVA_HOME variable to the path of your JDK 25. Then update your PATH variable to include the bin directory of your new JAVA_HOME.
```
export JAVA_HOME=/usr/lib/jvm/jdk-25.0.2-oracle-x64
export PATH="$JAVA_HOME/bin:$PATH"
```

Extract the Media Flow Engine file.

tar xf media-flow-engine-8.3.0.0.0.tar.gz

Navigate to the media-flow-engine-8.3.0.0.0-MFE/MFE_HOME/config directory and update the two IP address parameters in the application.yaml file to match the IP address of the server where you will deploy the MFE.
- application.ip-address – The IP address which Converged Application Server uses to communicate with the Media Flow Engine over HTTP or HTTPS.
  When configuring Media Flow Engines in the Remote Console, use this IP address for the Management IP field.
- Gst.Ip-address – The internal IP address used for receiving RTP packets from the RTP Proxy.
```
application:
  media-session:
    base-path: /media/v1/session
  ip-address: "127.0.0.1"
  custom-metrics:
    endpoint-path: /metrics

Gst:
 Ip-address: "127.0.0.1"
```
Navigate to the media-flow-engine-8.3.0.0.0-MFE/MFE_HOME/bin directory.
```
cd ../bin
```
Start the MFE.
```
sh startMFE.sh
```

To verify the MFE has started, open a browser and navigate to http://<IP address>:9090/metrics. The Converged Application Server uses port 9090 for health checks.