first of all I would like to thank the developers
and contributors of jitsi, it's a nice piece of
software. I like it very much.
Now, back to my question/issue.
I've the following:
One Linux PC with iptables running.
One Windows PC (I guess W7), with firewall disabled,
The Linux PC is connected to internet via a
The Windows PC is connected to interneti directly,
If I connect the two PCs to the router/firewall,
that is both are in the internal LAN, after opening
port 5060/5061 TCP/UDP and ports 5000-5031 UDP on
iptables, it is possible to call one each other
(p2p connection) and run normal VoIP communication.
So, it seems, from this setup, there's no issue
in p2p connectivity, once the above ports are open.
Now, if the Windows PC is on the other side of the
router/firewall, i.e. it is on open internet, after
opening the same ports in the router (with forwarding),
trying to call the other (Linux) PC results in ringing,
but, after answering, the whole connection waits with
"Initiating Call", until it gives up.
The FAQ mention this could be due to UDP packets
not being passed properly (size issue).
The reccomendation is to use TCP (I wonder, then,
Question is: how to use SIP with TCP?
Furthermore, what would a good way to debug this
Note that I cannot access the Windows PC anymore,
so that side cannot help (except for calling and
reporting the results).
Final note, the router/firewall has its own SIP/RTP
rules, so ports 6060/6061 TCP/UDP are forwarder to
port 5060/5061 TCP/UDP of the Linux PC.
This does not seem to be a problem, since the call
ring is received properly.
The caller uses, of course, the :6060 extension.
The router/firewall has a DNS entry.
Thanks for any help and sorry for the lengthy
explanation, but maybe better more than less...