wiki:RTPproxy

28.05.10 Source code has been moved to Git at  SourceForge.

19.10.09 New stable version 1.2.1 of RTPproxy has been released. The new release includes several new features and numerous fixes and improvements.

23.03.09 New stable version 1.2.0 of RTPproxy has been released. The new release includes several new features and numerous fixes and improvements.

12.01.09 New beta snapshot of 1.2 version of RTPproxy has been released. This snapshot includes Linux build fix as well as some improvements in re-packetization feature.

24.12.08 New snapshot of development 1.2 version of RTPproxy has been released. This snapshot includes Sun Solaris fixes (now it should compile and run clearly) and improved disconnect notification feature.

04.11.08 New snapshot of development 1.2 version of RTPproxy has been released. This release includes many bug fixes and new features, including Solaris compatibility fixes, support for the new rtpproxy_stream2xxx() command in  SER, improved support for re-INVITE, port randomization support and syslog support.

Older Entries..

About Sippy RTPproxy

The Sippy RTPproxy is a high-performance software proxy server for RTP streams that can work together with  SIP Express Router (SER),  OpenSIPS,  Kamailio, Sippy B2BUA or  reSIProcate B2BUA.

The main purpose of RTPproxy originally had been to make the communication between SIP user agents behind NAT(s) (Network Address Translator) possible. Several cases existed when direct end-to-end communication is not possible and RTP streams have to be relayed through another host. The RTPproxy can be used to setup such a relaying host.

Later on it became apparent that there are many other possible uses for this software. It can be used in combination with signalling element (SIP Proxy or SIP B2BUA) to build complex VoIP networks, optimize traffic flow, collect voice quality information and so on. It can perform number of additional functions on RTP streams, including call recording, playing pre-encoded announcements, real-time stream copying and RTP payload reframing.

The RTPproxy supports some advanced features, such as remote control mode, allowing building scalable distributed SIP VoIP networks. The  nathelper module included into the  SIP Express Router (SER),  OpenSIPS or  Kamailio as well Sippy B2BUA allow using multiple RTPproxy instances running on remote machines for fault-tolerance and load-balancing purposes.

RTPproxy was developed by Maxim Sobolev and now is being actively maintained by the  Sippy Software, Inc.

Why RTPproxy?

Traditional PBX-like VoIP switching packages act as a hub, pinning both media and signalling in one place. Such place often becomes bottleneck or single point of failure. In the modern interconnected world handling signalling separately from media in a distributed manner is necessity to build any network of medium or large size.

Getting RTPproxy

Downloads

Current Versions

Archive Versions

Source code via read-only Git

To get the latest source code from the CVS use the following command:

git clone git://sippy.git.sourceforge.net/gitroot/sippy/rtpproxy

then do the usual: ./configure; make; make install

You can also browse the repository  here.

License

The Sippy RTPproxy is distributed under BSD-style license. You can find the full text of the license  here. For a license to use the software under conditions other than those described here, or to purchase support for this software, please contact  Sippy Software, Inc.

Documentation

The RTPproxy Control Protocol.

Getting Help

You can obtain free best-effort help from the RTPproxy community. To participate on the mailing list, subscribe at the following web address:  http://lists.rtpproxy.org/mailman/listinfo/users and stick to problem reporting guidelines. Discussion of development, new features and RTPproxy status as on CVS takes place at the following mailing list:  http://lists.rtpproxy.org/mailman/listinfo/devel.

Please make sure to check FAQ page before requesting help from the mailing list.

Links