Introduction

This document contains the release notes for the RTPproxy 1.2.0 stable release. It describes recently added, changed, or deleted features of the RTPproxy compared to the previous stable version 1.1.

What's New

Support for the RTP session recording in the PCAP format

In addition to the ad-hoc recording format, which is more compact but isn't compatible with the third-party tools, the RTPproxy now supports recording of RTP sessions in the PCAP format supported by many existing tools, such as for example  Wireshark or  rtpbreak. The new feature can be activated with the -P option.

New option to record all RTP sessions

The new option to record all RTP/RTCP sessions going through the proxy has been added. It can be enabled by specifying -a option.

Independent RTP timeout mode

It is now possible to track RTP timeout independently on each call leg and tear down the session when either one happens. The new mode can be enabled by the -i option.

Support for notifying of external application about RTP timeout

The RTPproxy has been extended to allow notifying the external application in the case when RTP timeout happens. This feature allows implementing disconnect on no RTP features in various SIP B2BUA applications. Sippy B2BUA has been extended to use the new feature.

Security enhancements

To improve security and prevent potential guessing of the RTP port number by the attacker the RTPproxy now has the ability to randomize UDP port numbers that it allocates for RTP sessions. This mode of operation is the default in the version 1.2.0. For debugging purposes randomization could be disabled by definind SEQUENTAL_PORTS in the C preprocessor.

Syslog support

The RTPproxy now uses syslog operating system interface to log errors, warnings and debug messages when running in the background mode. The desired log level can be controlled via the new -d option.

Solaris compatibility

The software has been fixed to build clearly on Sun Solaris 10 and it has been confirmed to run properly on that operating system.

Session updates improvements

The session update logic has been improved to properly support cases when the call quickly traverses several destinations each of them generating early media. This could result in RTP from two endpoints being received by the RTPproxy at the same time confising RTPproxy as to which destination IP address should it use for sending traffic to. The version 1.2.0 should be able to handle such situations correctly.

Documentation updates

The documentation has been updated to reflect all new command line options.