Adding to everything that's been said:
Given that Jitsi does not currently have ICE with SIP you need to rely
on servers doing Hosted NAT Traversal  (HNT) for you. Most SIP
servers will do this and it will work reliably as long as UDP packets
are not completely filtered out by your firewall. Resorting to manual
port redirection could only be a problem.
Taking Jitsi out on a public IP address will not change many things:
as long as the remote end is also behind a NAT, the server would act
exactly the same way and provide HNT for you. If it didn't then we'd
have another problem because Jitsi does not do latching itself (that's
a server's job).
Now, what I'd advise you to do here is: rather than trying to find a
solution for your NAT problem, first try to determine whether you
actually have a NAT problem. Check the traffic and verify whether it
is in both directions at both sides. If it isn't, check out if one of
the endpoints could be streaming in the wrong direction.
You can also try other SIP servers like ippi.com and sip2sip.info.
On Mon, Jun 3, 2013 at 9:09 AM, Boris Grozev <firstname.lastname@example.org> wrote:
On 6/3/13 2:26 AM, Anthony Papillion wrote:
On 06/02/2013 06:05 PM, Lee Sharp wrote:
On 06/02/2013 04:21 PM, Anthony Papillion wrote:
I've tried Twinkle and Ekiga as well and they did the same thing so it's
likely not Jitsi. It's my network and that is going to be interesting to
Thanks again for the help! Much appreciated.
So, you may want to look into a firewall where you can more directly
control the NAT properties. Both m0n0wall and pfSense allow you to do a
lot of NAT customizing. Still not trivial, but do-able.
I've done one better. I've completely removed NAT from the picture. I've
called AT&T and got a few static public IP's for my use. Now, I hope, I
won't have these problems. I used IPTables to open the following ports
on my firewall:
Correct me if I'm wrong, bu unless you are talking about outgoing
connections, I don't think you need to open any ports at all. If you run
into problems again, you could temporarily open up everything in order to
rule out a filtering issue.