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.
rtpsend()
, the parse()
routine should store unsigned long
into n->num,
instead of int
. This caused an error for large SSRC
values. (Ping Pan)
parse()
routine in rtpsend()
. (Ping Pan)
packet.p.hdr.plen = ctrl ? 0 : len;[David M., davidm@cs.ucsb.edu]
rtpdump -f
file now shows a "from" address of
0.0.0.0:0.
rtpdump
changed from -f
to -F
for consistency.
-x
flag supported for dump format so that only
RTP/RTCP and media headers are logged.