http://mediaproxy.ag-projects.com/projects/mediaproxy/wiki/InstallationGuide

http://mediaproxy.ag-projects.com/

Description

MediaProxy is a media relay for RTP/RTCP and UDP streams that works in tandem with OpenSIPS to provide NAT traversal capability for media streams from SIP user agents located behind NAT. MediaProxy supports ICE negotiation by behaving like a TURN relay candidate and the policy can be controlled from OpenSIPS configuration.

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

This software is licensed according to the GNU General Public License version 2.

Background

MediaProxy 2.0 is the second generation media relay application, which is based on a completely new design that allows for major improvements in areas such as scalability (an order of magnitude more scalable than previous version) and security (communication between relay and dispatcher is encrypted).

New features have been added to support ICE (acts like a TURN relay) and call flows related to user mobility and fax transmission.

Features

• Scalability of thousands of calls per server
• TLS encryption between the relays and dispatcher
• T.38 fax support
• Graceful shutdown capability
• Automatic load balancing and redundancy among all servers
• Real-time sessions statistics
• Web page for media sessions with search capability
• Configurable IP and UDP port range
• Support for any combination of audio and video streams
• Radius accounting of IP network traffic
• Logging of complete media information into MySQL database
• Supports ICE negotiation by behaving like a TURN relay candidate
• Amazon EC2 ready (1 to 1 NAT)

Scalability

The most asked question about media proxy is how many concurrent calls can it handle. The absolute answer for this question can be found here.

Documentation

• Installation Guide

Support

MediaProxy is developed and supported by AG Projects.

AG Projects offers best-effort support for MediaProxy. "Best-effort" means that we try to solve the bugs you report or help fix your problems as soon as we can, subject to available resources.

You may report bugs to users@lists.opensips.org

The mailing list archive is available at: OpensSIPS users

Credits

Authors: Dan Pascu, Ruud Klaver, Saúl Ibarra

Installation Guide

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

You can install MediaProxy in the following ways:

1. From a tar file
2. From a Debian repository
3. 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:

http://download.ag-projects.com/MediaProxy/

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.

CentOS

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

http://kb.smartvox.co.uk/index.php/opensips/installing-mediaproxy-2-centos-5-64bit/