Thanks for the hint. Unfortunately it didn't work out quit that way. When I use the Decode as feature, it decodes only all packets to / from the involved ports as SIP, but thats all, the only way to have RTP packets to be decoded seems to be to do this RTP recognition for every port beeing used for RTP.
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
From: jaap.keuter@xxxxxxxxx
To: haneugen@xxxxxxxx
Date: 14:59:03, 12.12.2009
Subject: Re: [Wireshark-users] RTP, SIP and RTCP
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
>>Hi,
>>
>> The trick would be to look for what you think is a SIP packet and then
>> use the Decode as feature. Once it sees the SIP/SDP it will find the
>> RTP/RTCP too.
>>
>> Thanks,
>> Jaap
>>
>> Send from my iPhone
>>
>> On 12 dec 2009, at 12:16, "hne" <haneugen@xxxxxxxx> wrote:
>>
>> > Hi,
>> >
>> > I have a stream of captured RTP, SIP and RTCP packets, is there a
>> > way to to have wireshark to recognize them, I mean their content,
>> > since it is only able to display the fields of the TCP and UDP
>> > headers.
>> >
>> > Thanks in advance.
>> >
>> > Cheers,
>> > hne
>> >
>> > ___________________________________________________________________________
>>
>>
>> > Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx
>> > >
>> > Archives: http://www.wireshark.org/lists/wireshark-users
>> > Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>> > mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>> ___________________________________________________________________________
>> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
>> Archives: http://www.wireshark.org/lists/wireshark-users
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>>
