MediaProxy must run natively on the host operating system and not in a virtual environment.
You can install MediaProxy in the following ways:
- From a tar file
- From a Debian repository
- From the version control repository
1. From the tar file hosted at AG Projects downloads page¶
The software is available as a tar archive at:
2. From a Debian repository¶
Add the appropriate repository depending on your distribution. The location of repositories is here
After that, run:
sudo apt-get update sudo apt-get install mediaproxy-dispatcher mediaproxy-relay mediaproxy-web-sessions
to install all the packages, or you can install only the packages you actually
need on that specific system.
3. Installing from the version control repository (development branch)¶
The source code is managed using darcs version control tool. The darcs repository can be fetched with:
darcs get http://devel.ag-projects.com/repositories/mediaproxy
To obtain the incremental changes after the initial get:
cd mediaproxy darcs pull -a
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 this page ICE support.
This is a page maintained by a third-party for an older version: