I have checked in a small patch to make the tap listener only be called for thos RTP packets that match the udp conversation.
It should make it less likely to trigger the bug. Ofcourse, if the same SSRC value is choosen for both directions, we are still stuffed. I also fixed the ICMP bug by just telling the RTP tap that it doesnt want to listen to any packets containing icmp ----- Original Message ----- From: "Martin Regner" Sent: Tuesday, March 11, 2003 8:10 AM Subject: [Ethereal-dev] RTP analysis. Same SSRC for several streams causes problems Hi, I got some strange result when using RTP Analysis on one capture file with several different RTP streams between different ip-addresses. The RTP Analysis complained about wrong sequence numbers. When I looked closer I noticed that when there are more than one RTP streams using the same SSRC value then the RTP Analysis will handle all RTP packets with that SSRC value as belonging to the same RTP stream. I think that there should be a check not just for SSRC value but also source address, destination address, source port number and destination port number to identify what packets are belonging to the same stream.
