Home

Running rtpproxy on a different machine than SER

Keywords: nathelper

Contributed by norman.

RTPProxy can be run on a different machine than SER.

For example, if the remote machine has an IP Address of 192.168.1.1 (which isn't the same machine that SER is running on):

On the RTPProxy machine start rtpproxy with the following command:

/usr/local/bin/rtpproxy -l 192.168.1.1 -s udp:*:12345

Note1: 12345 is the port that rtpproxy will listen on. The default, if not specified is 22222. Note2: There is a -f option that will keep rtpproxy in for foreground. This will offer you the ability to watch the execution of rtpproxy in realtime.

On the SER machine add the following line to your ser.cfg

modparam("nathelper", "rtpproxy_sock", "udp:192.168.1.1:12345")

This is just a simple example. More complex configurations are possible by building on the above.normannorman

» login or register to post comments | printer friendly version

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Subject: It is also possible to set
From: samu
Date: 30 March, 2007 - 11:20

It is also possible to set not just one but several RTPproxyi "machines" and make load balancing and failover.

 Just c&p from the nathelper.c file:

  * 2005-02-24   Added support for using more than one rtp proxy, in which
 *              case traffic will be distributed evenly among them. In addition,
 *              each such proxy can be assigned a weight, which will specify
 *              which share of the traffic should be placed to this particular
 *              proxy.
 *
 *              Introduce failover mechanism, so that if SERi detects that one
 *              of many proxies is no longer available it temporarily decreases
 *              its weight to 0, so that no traffic will be assigned to it.
 *              Such "disabled" proxies are periodically checked to see if they
 *              are back to normal in which case respective weight is restored
 *              resulting in traffic being sent to that proxy again.
 *
 *              Those features can be enabled by specifying more than one "URIi"
 *              in the rtpproxy_sock parameter, optionally followed by the weight,
 *              which if absent is assumed to be 1, for example:
 *
 *              rtpproxy_sock="unix:/foo/bar=4 udp:1.2.3.4:3456=3 udp:5.6.7.8:5432=1"

 

» login or register to post comments
Home |  Recent changes |  Search |  Glossary |  Sitemap |  Login