From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: H.323 behavior Date: Fri, 01 Jun 2007 17:38:22 +0200 Message-ID: <46603D6E.9040606@trash.net> References: <925A849792280C4E80C5461017A4B8A210B7F8@mail733.InfraSupportEtc.com> <465E506D.6060008@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: netfilter-devel@lists.netfilter.org, Greg Scott To: Jing Min Zhao Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org Jing Min Zhao wrote: > >> It would probably make sense to destroy the connection when we seen >> a CloseLogicalChannel or CloseLogicalChannelAck message to deal with >> this kind of problem. >> > > Sometimes when people change codec, for example, from voice to T.38 fax, > they also close channels and open channels, but the H.245 connection > doesn't diconnect. So better to wait for the connection disconnect > itself or at least disconnect upon EndSessionCommand. CloseLogicalChannel might not be the right message (its been a while since I last did something with H.323), but at least when we know for sure the connection is closed we could kill it instead of waiting for the timeout.