osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

We have to look at RTSP packets regardless of whether we're generating a 

protocol tree or not, so that, on the first pass through the capture, we
see the SETUP requests that specify the ports to be used, and thus know
what the conversations for RTCP and RTP are.

svn path=/trunk/; revision=1887
This commit is contained in:
Guy Harris 2000-04-21 07:43:53 +00:00
parent 55900bbe9c
commit 9acdd80d4c
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
packet-rtsp.c
View File

@ -4,7 +4,7 @@
* Jason Lango <jal@netapp.com>
* Liberally copied from packet-http.c, by Guy Harris <guy@alum.mit.edu>
*
* $Id: packet-rtsp.c,v 1.11 2000/04/21 01:52:35 guy Exp $
* $Id: packet-rtsp.c,v 1.12 2000/04/21 07:43:53 guy Exp $
*
* Ethereal - Network traffic analyzer
* By Gerald Combs <gerald@zing.org>
@ -175,9 +175,6 @@ static void dissect_rtsp(const u_char *pd, int offset, frame_data *fd,
col_add_str(fd, COL_INFO, "Continuation");
}
if (!rtsp_tree)
return;
if (offset >= end_offset)
goto bad_len;
while (data < dataend) {
@ -265,8 +262,10 @@ static void dissect_rtsp(const u_char *pd, int offset, frame_data *fd,
/*
* Put this line.
*/
proto_tree_add_text(rtsp_tree, offset, linelen, "%s",
format_text(data, linelen));
if (rtsp_tree) {
proto_tree_add_text(rtsp_tree, offset, linelen, "%s",
format_text(data, linelen));
}
if (linelen > strlen(rtsp_transport) &&
strncasecmp(data, rtsp_transport,
strlen(rtsp_transport)) == 0)