segfault when using jingle with public IP address
Any attempt to initiate jingle connection when using public IPv4 address segfaults gajim.
No matter who initiates.. I don't even have to agree (it segfaults after I am invited; before I accept the invitation)
console clue: something like "Address already in use"
related problem: calling somebody on the same 192.168.x.0/24 subnet (behind NAT) results in two "accept invitation" dialogs (both direct and through-NAT connections succeeded)