Le dimanche 22 janvier 2006 à 21:02 -0500, Allan a écrit : > On Sunday 22 January 2006 14:18, Damien Sandras wrote: > > > With symmetric NAT, you will get random results, sorry. Try to turn that > > symmetric NAT into Cone NAT by correct port forwarding. > > > You keep saying that but as far as I know, I have forwarded all of the > reports > mentioned in the documentation. Here is what my modem reports on port > forwarding: > > <quote> > Name Protocol Port Redirected to IP > Address > > Custom Configuration TCP 5235 - 5236 192.168. 2. 10 * > Custom Configuration UDP 5237 192.168. 2. 10 > Custom Configuration UDP 5000 - 5100 192.168. 2. 10 > Custom Configuration TCP 5060 192.168. 2. 10 > Custom Configuration TCP 30000 - 30010 192.168. 2. 10 > Custom Configuration UDP 8000 - 8005 192.168. 2. 10 > MSN Netmeeting > Microsoft Messenger Service > CU-SeeMe H323 > AOL Instant Messenger TCP 1720 192.168. 2. 10 > Custom Configuration UDP 16384 - 16391 192.168. 2. 10 >
There are more ports than required, but it "looks" correct. [...] > For SIP: > <quote> > If it reports "Symmetric NAT" and that you are not using GNU/Linux, then you > are not part of the 99% of lucky users. You will have to forward UDP ports > 5000 to 5100 to your internal machine. Run the test again, it should report > "Cone NAT" or "Port Restricted NAT". > <endquote> > That is correct. > To confirm my understanding, I next went the GM site and consulted the FAQ > once more. I can find no references to ports other than the ones listed in > the two quotes and in the listing from my modem. > The FAQ there is for 1.2.2, not for 2.00. > So what gives? Are there other ports which need to be opened which are not > listed in the documentation? > No. > Finally, if I have not forwarded ports correctly, how is it possible that FWD > is able to call me? > The port used for incoming calls is correctly forwarded. Which doesn't mean other ports are correctly forwarded. To be honest, I don't understand what the problem is. That is something I never have encountered before, except when port forwarding is not correctly done, or except when there is a local firewall. I'm sorry, but I have nothing to suggest you :( As all ports are forwarded, and as you are sure of that, you can also stop using STUN, and use IP Translation. IP Translation only works if all ports are forwarded, and if they are, and if STUN is wrong, then you are sure all calls will work. I will add something to the FAQ for that. -- _ Damien Sandras (o- //\ GnomeMeeting: http://www.gnomemeeting.org/ v_/_ FOSDEM 2006 : http://www.fosdem.org SIP Phone : sip:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] _______________________________________________ GnomeMeeting-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
