Installation Guide

MediaProxy must run natively on the host operating system and not in a virtual environment.

You can install MediaProxy as Debian Package or from the source.

Binary packages are available for Debian on i386 and amd64 architectures.

Install as Debian Package

Add these lines to /etc/apt/sources.list (substitute unstable with your release name, like stretch, if you're not running unstable):

# AG Projects software
deb unstable main
deb-src unstable main

Install the AG Projects debian software signing key:

sudo wget -O /etc/apt/trusted.gpg.d/agp-debian-key.gpg

After that, run:

sudo apt-get update

Install MediaProxy packages:

sudo apt-get install mediaproxy-dispatcher mediaproxy-relay mediaproxy-web-sessions

Or you can install only the packages you actually need on that specific system.

Installing from source

Download and install dependencies

On non Debian installations you can install it from the source.

You will need the following dependencies:

For the database accounting module:

For the RADIUS accounting module:

Download and install Mediaproxy

You may run the software from its own directory or install it in a directory anywhere in the system.

The software is available as a tar archive at:

Extract it using tar xzvf mediaproxy-version.tar.gz and change directory to the newly created mediaproxy directory.

The source code is also managed using darcs version control tool. The darcs repository can be fetched with:

darcs get

To obtain the incremental changes after the initial get:

cd mediaproxy
darcs pull -a

After fetching install the software:

cd mediaproxy
sudo python3 install

More info about installing from source MediaProxy can be found in the INSTALL file.

Running the software

MediaProxy is meant to be used together with OpenSIPS' mediaproxy module.

To run the software, you will need a server running the Linux Operating System using a kernel version 2.6.18 or higher that has been compiled with connection tracking support (conntrack). IPtables 1.4.3 or higher is also required. Because of this dependency on Linux, other operating systems are not supported. This dependency only applies to the media relay component. The dispatcher component which runs on the same host as OpenSIPS, can run on any platform that has a python interpreter and supports the twisted framework.

Communication between the dispatcher and the relays uses TLS encryption and requires a set of X509 certificates to work. For more information about this please read tls/README which contains information about the sample certificates that are included as well as information about how to generate your own.

No STUN or TURN support are required in the clients.

The SIP User Agents must work symmetrically (that is to send and receive data on the same port for each stream), which is documented in RFC 4961.

To display the history of the media streams you may use CDRTool application.

For supporting ICE negotiation between end-points see ICE Support.

More info about running and setting up MediaProxy can be found in the README file.


This is a page maintained by a third-party for an older version: