** Description changed: == THINGS NEEDED TO REPRODUCE == Ubuntu 8.10 and Ubuntu 9.04 and their respective versions of Ekiga Ekiga.net account Diamondcard.us account Two consumer-grade routers (my case, a Buffalo AirStation WHR-G45S and Asus WL-520G, both running DD-WRT v24-sp1 (07/27/08) std) Set one router to connect to the Cable/DSL modem Set the second router to treat the the first router as a WAN Forwarding of ports 5000-5100 UDP so that the second router can receive SIP traffic and forward it to a particular internal IP address. == WORKING SOLUTION == Ubuntu 8.10 with Ekiga 2.0 (default version that ships with Ubuntu 8.10) Set up Ekiga with an Ekiga.net account Ekiga.net login works as expected Ekiga.net echo test works as exepected Setup Ekiga with a Diamondcard.us account Diamondcard.us login works as expected Diamondcard.us echo test works as expected == WORKING SOLUTION (UNCONFIRMED) == - (This is a past setup I cannot reproduce because the SVN has moved on) - - Ubuntu 8.10 with Ekiga 3.0 (SVN version) - Set up Ekiga with an Ekiga.net account - Ekiga.net login works as expected - Ekiga.net echo test works as exepected - Diamondcard.us login works as expected - Diamondcard.us echo test works as expected + [deleted July 10 2009 -- not needed] == UNTESTED SOLUTION == - (Currently Ekiga's SVN has no intrepid packages) - - Ubuntu 8.10 with Ekiga 3.2.4 (SVN version) - Set up Ekiga with an Ekiga.net account - Set up Ekiga with a Diamondcard.us account + [deleted July 10 2009 -- not needed] == NON-WORKING SOLUTION == Ubuntu 9.04 and Ekiga 3.2 (default version that ships with Ubuntu 9.04) Set up Ekiga with an Ekiga.net account Ekiga.net login works as expected Ekiga.net echo test fails (User not available) Set up Diamondcard.us account Diamondcard.us login works as expected Ekiga receives call through the Diamondcard.us account as expected During received calls, sound only comes in. The person calling in cannot hear the recipient behind Ekiga. + + ========== UPDATE JULY 10 2009 ========== + After some discussion, the problem I was having was not with a double-NAT set up but rather an MTU setting. If you have optimized your MTU packet size for a local gigabit LAN, chances are it is higher than the Internet standard of 1500. Currently, Ekiga 3.2.0 only supports communications using UDP packets, and they cannot be fragmented into smaller packets. TCP packets can be fragmented, but TCP is currently not implemented (though high on the TODO). If you issue the command ifconfig [interface] mtu 1500 (where [interface] is something along the lines of eth0) and everything starts working, then this was your problem. If you're still having problems, try the Ekiga Echo Test. If the Ekiga Echo Test works and the other SIP server/peer does not, chances are that you and this other SIP server/peer you are connecting to cannot negotiate a codec that will fit inside this limit. + =========================================
-- Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT https://bugs.launchpad.net/bugs/380091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
