Log Message:
Update 1.18 to 1.20
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)."