Skip to content

Latest commit

 

History

History
69 lines (52 loc) · 3.19 KB

README.md

File metadata and controls

69 lines (52 loc) · 3.19 KB
Raw

Build Status

About

The RTPproxy is a high-performance software proxy for RTP streams that can work together with OpenSIPS, Kamailio or [Sippy B2BUA] (https://github.com/sippy/b2bua).

Originally created for handling NAT scenarios it can also act as a generic media relay as well as gateway RTP sessions between IPv4 and IPv6 networks.

The RTPproxy supports some advanced features, such as remote control mode, allowing building scalable distributed SIP VoIP networks. The nathelper module included into the OpenSIPS or Kamailio SIP Proxy software allows using multiple RTPproxy instances running on remote machines for fault-tolerance and load-balancing purposes.

Advanced high-capacity clustering and load balancing is available through the use of RTP Cluster middleware.

The software also supports MOH/pre-recorded prompts injection, video relaying and RTP session recording to a local file or remote UDP listener(s).

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

How it works

This proxy works as follows:

  • When SER receives INVITE request, it extracts call-id from it and communicates it to the proxy via Unix domain socket. Proxy looks for an existing sessions with such id, if the session exists it returns UDP port for that session, if not, then it creates a new session, binds to a first empty UDP port from the range specified at the compile time and returns number of that port to a SER. After receiving reply from the proxy, SER replaces media ip:port in the SDP to point to the proxy and forwards request as usually;

  • when SER receives non-negative SIP reply with SDP it again extracts call-id from it and communicates it to the proxy. In this case the proxy does not allocate a new session if it doesn't exist, but simply performs a lookup among existing sessions and returns either a port number if the session is found, or error code indicating that there is no session with such id. After receiving positive reply from the proxy, SER replaces media ip:port in the SIP reply to point to the proxy and forwards reply as usually;

  • after the session has been created, the proxy listens on the port it has allocated for that session and waits for receiving at least one UDP packet from each of two parties participating in the call. Once such packet is received, the proxy fills one of two ip:port structures associated with each call with source ip:port of that packet. When both structures are filled in, the proxy starts relaying UDP packets between parties;

  • the proxy tracks idle time for each of existing sessions (i.e. the time within which there were no packets relayed), and automatically cleans up a sessions whose idle times exceed the value specified at compile time (60 seconds by default).

Support

Open a ticket on the github issue tracker, or post a message on the mailing list

Commercial support is available from the Sippy Software, Inc. - visit http://www.sippysoft.com for details.