Ethereal-users: Re: [Ethereal-users] RTP Analysis: Error: "Can't save in afile:Unsupported codec

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Lars Ruoff" <Lars.Ruoff@xxxxxxxxxx>
Date: Wed, 16 Mar 2005 15:44:59 +0100
Yes, please include the capture file.

regards,
Lars Ruoff.

----- Original Message ----- 
From: "Erik Naslund" <erik.naslund@xxxxxxxxx>
To: <ethereal-users@xxxxxxxxxxxx>
Sent: Wednesday, March 16, 2005 3:38 PM
Subject: Re: [Ethereal-users] RTP Analysis: Error: "Can't save in
afile:Unsupported codec!"


> I will try your display filter suggestion and post my results later
> this evening. Also, if you like i can include a capture file for any
> coder who may want to address the issue directly in the product.
>
> Thank you all for your replies.
>
> -Erik
>
>
> > I guess that the RTP-stream contains not just packets with payload type
0 (G.711 U-law) or payload type 8 (G.711 A-law)
> > but also packets with another payload type.
> > When DTMF digits are sent then they can be sent with a special codec
(RFC 2833 RTP Events).
> > Probably there is packets with a dynamic payload type in the range 96 to
127.
> >
> > You could probably avoid the problem by first using a display filter to
only select the other packets that you
> > need and then save only the displayed packets with "Save As..." and then
load that file and analyze it.
> >
> > The filter could maybe look something like:
> > sip or sdp or h225 or h245 or rtp.p_type==0 or rtp.p_type==8
> >
> > However not a really nice solution, so we should probably try to find a
real solution to your problem (e.g.
> > alerting the user that the stream contains a mixture of payloads and
that only the G.711 packets will be saved to
> > the au-file).
> >
> >
>
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-users