From: Nils Ohlmeier <lists@ohlmeier.de>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: <netfilter-devel@lists.netfilter.org>
Subject: Re: conntrack manipulation
Date: Sat, 10 May 2003 00:21:24 +0200 [thread overview]
Message-ID: <200305100021.24860.lists@ohlmeier.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0305091431580.9035-100000@blackhole.kfki.hu>
On Friday 09 May 2003 14:36, Jozsef Kadlecsik wrote:
> On Thu, 8 May 2003, Nils Ohlmeier wrote:
> > phone1 ------ NAT ------- Internet ----- phone2
> >
> > Phone1 starts a call to phone2 (INVITE message). Phone2 confirms the call
> > (200 OK message) after the user picked up and starts to send RTP packets
> > to the public NAT address immediately. Now the comfirmation message hits
> > the SIP
>
> How can the user (phone1) send RTP packets before receiving the 200 OK
> message from phone2?
Not phone1 sends but phone2 sends RTP packets immediately after it send the
'200 OK' to confirm that the user at phone2 picked up the hearer.
So the problem is basicly that the callee phone starts to send packets to fast
(at least to fast for our solution).
It could also happen that that phone1 starts to send RTP packets before it
received the '200 OK' if it received '183 Session progress' with a SDP body
(which contains the IP and port of phone2). But this is not the normal case
and makes no difference to the 200 case because we can insert the rules also
on 183.
Greetings
Nils Ohlmeier
next prev parent reply other threads:[~2003-05-09 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 21:47 conntrack manipulation Nils Ohlmeier
2003-05-09 12:36 ` Jozsef Kadlecsik
2003-05-09 22:21 ` Nils Ohlmeier [this message]
2003-05-12 7:35 ` Jozsef Kadlecsik
2003-05-12 18:15 ` Nils Ohlmeier
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 23:35 Ian Latter
2003-05-13 13:52 ` Nils Ohlmeier
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=200305100021.24860.lists@ohlmeier.de \
--to=lists@ohlmeier.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@lists.netfilter.org \
/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.