Ethereal

Re: [Ethereal-users] Specifying a range or filter for "decode as"
Google
 
Web Ethereal.com

Home | Introduction | Documentation | Lists | FAQ | Development | Wiki | Bugs

Ethereal-users: May 2006


Hi,

Sure there's an easy way. Go to the protocol preferences of the RTP
dissector and tick the box "Try to decode RTP outside of conversations".

Thanx,
Jaap


On Wed, 3 May 2006, Sean Walberg wrote:

> I'm using Ethereal to analyze RTP streams sent between Avaya PBXes.  Upon
> viewing the capture file, it is not recognized as RTP which is
> understandable.  I'm able to right click and assign RTP to the port and get
> my analysis that way, but dealing with a million packets or so takes an
> absurd amount of time to do since Ethereal reprocesses all the packets every
> time I set up one session, and there are many sessions to do.
>
> The signalling protocol is proprietary, so Ethereal doesn't have the chance
> to figure out that the packets are supposed to be RTP by looking at the
> signalling.  I'm able to filter enough that everything on my screen I see
> should be RTP, but is there a more efficient way of telling Ethereal to
> decode everything as RTP, or to provide a range of UDP ports to decode as
> RTP?
>
> Thanks,
>
> Sean
>
> --
> Sean Walberg <sean@xxxxxxxx>    http://ertw.com/
>


Powered by MHonArc 2.6.10