Ethereal-dev: Re: [Ethereal-dev] h225 decoded as h245

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Andreas Sikkema <h323@xxxxxxxxxx>
Date: Mon, 08 Nov 2004 22:46:21 +0100
On Mon, 2004-11-08 at 18:32, Martin Regner wrote:
> I think that I understand what the reason for this is.
> Some of the H.225 messages include a h245address element
> Ethereal will set up "conversations" to catch the H.245 messages sent on that specific ip-address/port-number
> combination,
> but that port number will be used for H.225 messages later on in the capture.
> 
> Those messages will then be decoded as H.245 messages even if they are H.225 messages since "conversations" have
> higher priority.
> 
> I don't know right know how this problem could be solved in a good way.

I consider that a bug in the Telsey stack. It 's just plain wrong to
tell the world you're going to send H.245 messages from a certain point
and then do the complete opposite. For a receiving endpoint there's no
obvious way to distinguish between H.245 and H.225 messages when
received as a bitstream, apart from some evil heuristics.

-- 
Andreas Sikkema <h323@xxxxxxxxxx>