[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
I can confirm with Alvin, insofar as I did not install any additional codecs (knowingly). Granted I haven't gone so far as to test a fresh install, so there exists a possibility that additional codecs were available to me as a side-effect of installing other packages on top of the default ubuntu install. Here's what I got (all enabled): * Speex 8/16 kHz, PCMA, PCMU, G726-16/24/32/40, GSM, MS-GSM, G722 Ekiga can connect to the Echo Test and work as expected when the local machine's MTU is set to 1500. Funny things happen when the the local machine's MTU is set too high (common on machines that are on a local gigabit network but also connect to the Internet.) I take exception with the view that Ekiga must honor the user's wish to use whatever codecs the user specifies. The view by itself is justified and agreeable, but ignores the ultimate wish of every user of every program ever in existence -- the user wants the program to actually work. If those two ideals happen to collide, the latter should take precedence over the former. Having said that, I don't think the following would be a problem: * Offer a checkbox that will offer to limit UDP packet sizes to the standard size found on the Internet in the same place where users can enable/disable codecs. * Warn users that this may disable the use of some codecs the user has chosen to use which might result in not being able to connect to some SIP servers/peers. * When the user makes a call and is unable to negotiate the use of a codec with the SIP server/peer, tell them so. Don't tell them user not available. That's how this thread started in the first place. Tell them with as much specificity as you can -- unable to negotiate codec with server or something similar. While Ekiga gets TCP support, there very well could be some servers that are UDP-only. This is the only reason I'm going into the diatribe. I've seen too many bug reports and release notes for SIP-related software/firmware. For varying reasons, shortcuts get taken. To the user, if one implementation works and another does not, the non-working implementation looks broken even when the non-working implementation is not at fault. And last but not least, I just want to make sure that it's understood that I'm not holding anyone personally responsible for my gripes with Ekiga -- Yannick or otherwise. After taking a few read-overs on this post, I realized what I wrote could be taken that way. ** Tags added: ekiga ** Tags added: 1500 mtu pdu udp -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
** 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
Alvin, AFAIK, Ubuntu ships only the free codecs and if you select them all it fits in UDP, the issue occurs when you add the non-free codecs. Do you use the package from Ubuntu? If so, does the PDU exceed 1500? Best regards, Yannick -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
Yannick, No I hadn't installed any non-free codecs (not knowingly anyway). I wanted to confirm this so I booted from clean live USB memory stick image (Jaunty). Selected ekiga for installation. Synaptic informs that the following are required: libgsm1, libopal3.6.1, libpt2.6.1, libpt2.6.1-plugins-alsa, libpt2.6.1-plugins-v4l2. (All of these come from the Main repository). Once above are installed: Ekiga has the same problem as described above (PDU exceed 1500) and same solution as you describe above also works. Out-of-the-box Audio codecs: G722, Speex(16kHz), PCMA, PCMU, G726-16, G726-24, G726-32, G726-40, gsm, ms-gsm, Speex(8kHz). Out-of-the-box Video codecs: h261, theora. So, in answer to your question, only using default packages from Ubuntu is sufficient for PDU to exceed 1500. -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
The following maybe the cause??: Running Ekiga 3.2 (on jaunty) using ekiga -d 5 out I see the following line: 2009/07/05 23:07:53.315 0:51.397 Housekeeper:0xbb90 SIP PDU is likely too large (1550 bytes) for UDP datagram. which is likely to be this known issue: http://wiki.ekiga.org/index.php/Troubleshooting#I_hear_the_ring.2C_but_the_communication_is_not_established and upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=341518 and for the record - test call to echo (5...@ekiga.net) fails with user is not available as reported above. ** Bug watch added: GNOME Bug Tracker #341518 http://bugzilla.gnome.org/show_bug.cgi?id=341518 -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
2009/07/05 23:07:53.315 0:51.397 Housekeeper:0xbb90 SIP PDU is likely too large (1550 bytes) for UDP datagram. is indeed an issue here. Solution: disable some codecs in preferences until the PDU is lower than 1500. -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
Alvin: Running ekiga -d 5 out, the output still goes to the console. If I remember anything correctly about C programming, ekiga is directly dumping output to the console instead of using stdout. You have to use ekiga -d5 2 out. Alvin Yannick Defais: The PDU 1500/1550 thing makes a heckuva lot of sense. The computer running Ubuntu 8.10/Ekiga 2 did not have it's MTU touched, so it's at the default 1500. The computer running Ubuntu 9.04/Ekiga 3 has its MTU set at 7500 because its /home is on an NFS share over gigabit networking. If I'm recalling this correctly (again), UDP packets don't support fragmentation while TCP packets do. After issuing ifconfig eth0 mtu 1500, Ubuntu 9.04/Ekiga 3 works as expected. But should users be expected to fiddle with MTU settings just for one program? Shouldn't Ekiga be able to pick up on the error and say, Oh, the packets are too big? Let's try smaller, standard ones. Or is the packet size completely out of the hands of the application? As it stands now, my options aren't nice: * take a 50%-66% hit in local gigabit network performance to run Ekiga all the time * run Ekiga with a script that'll change the MTU as needed (only dragging performance while Ekiga is running) * set up another computer just to run Ekiga all the time (which is a bit of a waste) * I don't have dual NICs, so setting one up for the local network and one for the Internet goes right out the window -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
BrainwreckedTech, Ekiga cannot try to reduce the packet size because of the SIP protocol: it has to deal with a codec negociation, and it respect user choice to present all codecs available (and there is many codecs available in Ekiga) and selected by the user. Reducing the packet will mean dropping some codecs. As you explained UDP packets cannot be fragmented, while TPC packets can. The SIP standard thus ask the application to switch to TCP if the packet size do not fit in UDP. The issue here is Ekiga do not support this feature yet, which lead to this bad situation. It was not an issue until Ekiga supported so many codecs as it is able to do nowadays. Supporting TCP as well as UDP is a main priority for the project (in fact for the OPAL lib ekiga uses). Until this bug is fixed, the best solution is to deselect some codecs in Ekiga until it fits the UDP packet size. Best regards, Yannick -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
Thanks Yannick. I understand the issue a lot better now. I wonder if there is a more immediate issue here with regard to Ubuntu packaging. On Jaunty (netbook remix) Ekiga comes 'out-of-the-box' with all codecs pre-selected which is not a working configuration. This may also be a nice config mod to be nominated for Karmic Koala. -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
Found this PPA for Ekiga 3.0 SVN and Ubuntu 8.10: https://launchpad.net/~sevmek/+archive/ppa Will try this when I can. Hopefully a working, easily-replicated scenario helps in narrowing things down a bit. -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380091] Re: Ubuntu 9.04 Ekiga 3.2.0 Does not work behind double-NAT
Scratch that. The PPA's version of Ekiga is 2.9.90. This version connects correctly, but incoming sound cannot be heard, much like non- working Ubuntu 9.04/Ekiga 3.2 setup with Diamondcard. Test cases are piling up, and as I used to have Ekiga 3.0SVN working on Ubuntu 8.10, I don't think this test case should be considered. Correct me if anyone thinks otherwise. ** 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 Ubuntu 8.10 version) + 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 == 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 == NON-WORKING SOLUTION == - Ubuntu 9.04 and Ekiga 3.2 (default Ubuntu 9.04 version) + 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. -- 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 Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
