|
> Date: Wed, 17 Mar 2010 17:00:06 +0100 > From: Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr> > Message-ID: <4BA0FC86 1070601 pu-pm univ-fcomte fr> > > Given the recent posts (and others), I have just written a page > http://wiki.ekiga.org/index.php/Understanding_NAT/firewall_issues_with_SIP_clients_%28eg_ekiga%29 > explaining the problems of VoIP clients with NATs. I am not 100% sure > of what I wrote, and it remain open questions. Please help to improve > it by making remarks/improving it. The Ekiga wiki is broken. It runs me in circles when I try to register, so I can't add to the discussion. (Don't bother to fix it for me. I don't really want to start contributing to the wiki anyway.) But since I can't add a comment, I'll post it here. The article says, "For that, before registering, A and B must discover their public IP addresses (corresponding to NATA and NATB respectively) and send it to ekiga.net, so that they can be contacted afterwards (*TODO why ekiga.net cannot simply use ip/port from ip packet header?*)". Indeed, this requires explanation. This is surely the job of the SIP server. I certainly do not need a separate STUN server to use a Web browser. The Web site has no trouble determining my external IP address. Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. Learn More. |