RTP tools change history

1.22 (July 2018)

Moved source to https://github.com/columbia-irt/rtptools
Listing only major changes, see details in git log.

1.21 (July 2016)
Yann E. MORIN (yann.morin.1998@free.fr): Buildroot [1] is a build-system targetting embedded devices. It is able to build toolchains for various architectures, based on the traditional GNU compiler collection gcc, the GNU binutils and various C libraries, such as GNU libc (glibc), uClibc [2] [3] or musl [4].

glibc is a feature-full C library, which has had support for Yellow Pages (and the rest of the SUN RPC stuff) for a long time. However, circa the 2.14 release, glibc stopped installing the RPC headers [5], on the principle that providing the RPC implementation would be better served by a third-party package, namely ti-rpc [6]. That did not happen in time, so installing the RPC headers from glibc was re-instated circa 2.16.

uClibc (no longer maintained, replaced by a fork, uClibc-ng) is a fully configurable C library for embedded systems. It entirely lacks a SUN RPC implementation altogether.

musl is standards-conforming, lightweight C library. It also entirely lacks a SUN RPC implementation.

TI-RPC is a stand-alone package. It may or may not be available (because the user may not need SUN RPC stuff on an embedded device, for example). Besides, it is not yet as feature-full as the implementation in glibc, though for all practical means, it is totally useable.

So, there are cases where a SUN RPC implementation is not available.

This patch makes it so that the use of Yellow Pages is conditional on the presence of a SUN RPC implementation, by checking at ./configure whether the required header is present, and disabling the corresponding code if the header is missing.

At the same time, the legacy, long unsupported AM_C_PROTOTYPES directive is also removed, as it makes recent-ish autoconf fail.

1.20 (October 2013)

Nick Birch (Nick.Birch@s-and-t.com): rtpsend -l (loop) flag does not work. Modified to rewind input file on feof if loop was set. Fails if length of line is greater than 2048 characters. Increased to 4096 (sufficient for typical MTU-sized message such as 7 MPEG TS packets)

rtpdump: Put space after ext_data=<hex extension data> so that it can be parsed by rtpsend. parse_header doesn't comprehend the possible extension header. As a consequence any extension header data is also dumped twice. Once in the ext_data report and then a second time in the data report. Modify parse_header to return hlen that comprehends the extension header if present.

The format for reporting contributing sources does not match the format accepted by rtpsend (i.e., reports "csrc[n] = xxxx" rather than "csrc[n]=0xxxxx"). Fixed. Note: the documentation is less than clear on the csrc syntax accepted by rtpsend.

1.19 (August 2010)
Krzysztof Burghardt (krzysztof@burghardt.pl): "Wireshark implemented "rtpdump" file format in a bit different way, so cooperation beetwen those program is a bit problematic. Moreover rtptools compiled on i386 and amd64 have different size of file header (size of long in timeval is different)."
1.18 (September 2002)
Changes made by Akira Tsukamoto unless otherwise noted.
1.17 (April 2001)
Added -o option to rtpdump, so that output can be directed to a file. This is necessary so that the file can be opened in binary mode. Also configured stdout on Win32 for binary mode, disabling the typical \n to \n\r translation. (hgs)
1.16 (July 2000)
1.15 (March 2000)
1.14 (October 1999)
1.13 (August 1999)
1.11 (January 1999)
1.10 (March 1998)
1.9 (August 1997)
1.8 (July 1997)
1.6 (October 1996)
1.0 (December 1995)

Last updated by Henning Schulzrinne