when Jitsi uses a
port to send packets toward the Internet, your NAT will create a
single binding and allocat a single public port regardless of the
destination Jitsi is trying to reach.
As it seems not to be working my router at home is most likely not
advanced enough to do so,
This is not a sophisticated feature. Most NATs would behave this way.
Some don't however and maybe yours is one of them. If it is then port
forwarding is not necessarily going to change anything.
If you want to know for sure, just examine your pcap logs.
but i have forwarded every single port there
is to my computer. It still uses a relay.
I am not sure how else to say this but port forwarding really isn't
what you are looking for. I am not going to insist any more and only
explain it one last time. Jitsi is not a server. It does not use a
well known port to always receive packets on. When doing calls Jitsi
will not blindly send packets to a specific port on your NAT that you
can then forward to an internal IP. This is simply never happening.
Jitsi will send packets back to the ports that it is getting packets
In other words, when you make a call Jitsi will:
1. Allocate a port on your local host. This port would be between 5000
and 6000 although these numbers don't really matter.
2. This port will then be used to send packets outside of your network.
3. Your NAT will dynamically map a public port to that port.
4. The remote party will use the public port from step 3, the one they
see as source for incoming datagrams and send packets to it.
I've seen NATs where forwarding a port range to a specific internal IP
would actually cause the NAT to use ports outside of that range for
One way or another, if you want to really know what's happening - have
a look at your pcaps.
On Wed, Nov 28, 2012 at 10:19 PM, Yannik Völker <firstname.lastname@example.org> wrote:
Am 28.11.2012 22:10, schrieb Emil Ivov: