Yes, I've tried that, thanks. Wireshark shows the packets as RTP but does not know the payload type.
I would like to make modifications to the source so that Wireshark will understand the CODECs specified in the IOS5 signaling and then subsequently call another dissector for RFC3558. Thanks. -- Michael Lum Principal Software Engineer 4600 Jacombs Road +1.604.276.0055 Richmond, B.C. Canada V6V 3B1 Star Solutions -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Abhik Sarkar Sent: November 15, 2008 1:53 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] How do you get RTP recognized by Wireshark ? Hi Michael, I don't know much about RTP, but I think I remember someone answering a similar question recently... have you already trying turning on the preference for RTP protocol called "Try to decode RTP outside of conversations"?. HTH Abhik. On Fri, Nov 14, 2008 at 10:06 PM, Michael Lum <[EMAIL PROTECTED]> wrote: > Hi, > > I have RTP streams that are set up with an unrecognized signaling > protocol. I.e. not SIP/MGCP, etc. > > Can somebody give me a quick run down on what to change so that the > streams can be recognized as RTP ? > > I thought all I might have to do was add a call to > rtp_add_address() with the correct IP address, port, payload, etc. > but it doesn't appear to work. > > Any help would be great. > > Thanks. > > -- > Michael Lum Principal Software Engineer > 4600 Jacombs Road +1.604.276.0055 > Richmond, B.C. > Canada V6V 3B1 > Star Solutions > _______________________________________________ > Wireshark-dev mailing list > [email protected] > https://wireshark.org/mailman/listinfo/wireshark-dev > _______________________________________________ Wireshark-dev mailing list [email protected] https://wireshark.org/mailman/listinfo/wireshark-dev _______________________________________________ Wireshark-dev mailing list [email protected] https://wireshark.org/mailman/listinfo/wireshark-dev
