| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Existing SHA1 digests verified, all found to be the same on the
machine holding the existing distfiles (morden). Existing SHA1
digests retained for now as an audit trail.
|
|
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
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)."
|
|
|
|
|
|
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The rtptools distribution consists of a number of small applications that
can be used for processing RTP data.
|
