https://github.com/irtlab/rtptools

RTP Tools
https://github.com/irtlab/rtptools

protocol qos real-time rfc3550 rtcp rtp rtptools streaming teleconference telephony transport video

Last synced: 8 months ago
JSON representation

RTP Tools

• Host: GitHub
• URL: https://github.com/irtlab/rtptools
• Owner: irtlab
• License: other
• Created: 2017-12-04T18:00:01.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2024-02-04T09:26:13.000Z (over 2 years ago)
• Last Synced: 2025-10-21T03:57:45.898Z (8 months ago)
• Topics: protocol, qos, real-time, rfc3550, rtcp, rtp, rtptools, streaming, teleconference, telephony, transport, video
• Language: C
• Homepage: http://www.cs.columbia.edu/irt/software/rtptools/
• Size: 35.4 MB
• Stars: 181
• Watchers: 10
• Forks: 64
• Open Issues: 14
• Metadata Files:
  • Readme: README.md
  • Changelog: ChangeLog.html
  • License: LICENSE

Awesome Lists containing this project

README

          
# RTP Tools

RTP Tools is a set of small applications

that can be used for processing RTP data.

Refer to the individual manpages for details.

* **rtpplay**

	play back RTP sessions recorded by rtpdump

* **rtpsend**

	generate RTP packets from textual description,

	generated by hand or rtpdump

* **rtpdump**

	parse and print RTP packets,

	generating output files suitable for rtpplay and rtpsend

* **rtptrans**

	RTP translator between unicast and multicast networks

* **multidump**

	Start multiple rtpdumps simultaneously.

* **multiplay**

	Start multiple rtpplays simultaneously.

## Installation

RTP tools should compile and run on any POSIX compatible system,

as well as on Windows. Some operating systems also provide

a prebuilt package of RTP tools.

On UNIX, the usual `./configure && make` should work.

Read on for the details.

### configure

Run `./configure` to configure the build for your system.

This will produce three files:

* `config.h` containing the `#include` and `HAVE_` lines

* `config.log` containing the details of autodetection

* `Makefile.local` which defines `CC`, `PREFIX` and the like

Read the standard output and `Makefile.local`.

If these look different from what you expected,

read `configure.local.example`, create `configure.local`,

and run `./configure` again.

The `./configure` script is accompanied by a set of simple programs

autodetecting the availability of system functions

(e.g. [`have-err.c`](have-err.c)), and whether extra libraries need to be

involved (e.g. `-lnsl` for [`have-gethostbyname.c`](have-gethostbyname.c)).

For C functions that might not be present in the system,

we provide autoconfiguration tests and `compat-*.c` implementations.

(e.g. [`compat-strtonum.c`](compat-strtonum.c)).

Please report any that turn out to be missing.

Read `config.log`, which shows shows the compiler commands used

to test the libraries installed on your system, and the standard

output and standard error output these commands produce.

Failures are most likely to happen if headers or libraries

are installed in unusual places or interfaces defined

in unusual headers. You can also look at `config.h` and

check that the `#define HAVE_*` lines match your expectations.

### build

Once the source is configured as above, run `make` to build RTP tools.

Any POSIX-compatible make, in particular both BSD make and GNU make,

should work. If the build fails, read `configure.local.example` again.

### install

Run `make -n install` and check where everything will go.

If that differs from your expectations, set the `*DIR` variables

in `configure.local` and go back to running `./configure`.

Install the binaries and the manpages with `make install`.

Depending on the `PREFIX` (which is `/usr/local` by default),

you might need to `sudo make install` or `doas make install`.

### Windows

Open `rtptools.sln` on MS Visual Studio and press F7 to build.