No, as far as i know there is still no "final fix" for the problem.
However you can choose to decode as T.38 as follows:
The problem is that some RTP decoding is applied before the user Decode
As... choice is applied.
This is most likely due to H.225 or similar signalling which sets up the RTP
conversation.
So, to prevent automatic RTP decoding you might consider disabling the H.225
or similar protocol.
This will result in the corresponding RTP/T.38 packets not being decoded as
RTP (they will remain UDP).
Then you can enforce these conversations to be decoded as T.38
Lars
> Ethereal unfortunately decodes the T38 packets as "RTP packets version
> unknown"
> I tried the "Decode as..." functionality of ethereal in vain. The packets
> remained decoded as RTP.
>
> I tried to set the T38 UDP port in the "Preferences..." for T38. It did
not
> work. The packets remained decoded as RTP.
>
> I found a workoraind in the FAQs:
> "A temporar solution can be to use a display filter "rtp.version == 0" and
> save just those packets in a new file, and use "Decode As.."
> after loading in that file. However it would be nice to solve this problem
> in a better way."
>
> The workoround worked but I wonder whether there is final fix for the
> problem. (or a better workoraund.)
>
> best regards
>
> Lajos Morvai.
>
>
----------------------------------------------------------------------------
----
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-users
>