All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Greg Scott <GregScott@InfraSupportEtc.com>
Cc: netfilter-devel@lists.netfilter.org,
	Jing Min Zhao <zhaojingmin@users.sourceforge.net>
Subject: Re: H.323 behavior
Date: Thu, 31 May 2007 06:34:53 +0200	[thread overview]
Message-ID: <465E506D.6060008@trash.net> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A210B7F8@mail733.InfraSupportEtc.com>

Greg Scott wrote:
> Apologies - I never replied back to the list on how this turned out.
> Jing Min Zhao was kind enough to reply privately and we developed a
> theory. Jing was right.  The problem was, I had set up the Polycom codec
> here to use fixed ports - a legacy from before Jing's H.323 module.  So
> every time I hung up a call and tried again, the Polycom would try to
> call using the same ports.  But the firewall hadn't cleared them yet and
> that's why the strange behavior.  The cure - just get rid of fixed ports
> on the Polycom codec and use it as delivered from the factory.


It would probably make sense to destroy the connection when we seen
a CloseLogicalChannel or CloseLogicalChannelAck message to deal with
this kind of problem.

  reply	other threads:[~2007-05-31  4:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 23:18 H.323 behavior Greg Scott
2007-05-31  4:34 ` Patrick McHardy [this message]
2007-05-31 11:30   ` Jing Min Zhao
2007-06-01 15:38     ` Patrick McHardy
  -- strict thread matches above, loose matches on Subject: below --
2007-05-31  5:23 Greg Scott
2007-04-13 11:45 Greg Scott
2007-04-13 13:49 ` Jing Min Zhao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=465E506D.6060008@trash.net \
    --to=kaber@trash.net \
    --cc=GregScott@InfraSupportEtc.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=zhaojingmin@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.