[Ekiga-list] Newbie configuration experiences...
First of all: I actually got Ekiga 3.0.1 running to the point of a working call to the echo service on my Fedora 10 box which is a Good Thing. You are doing a great job! However, being a newbie I found it a little harder than it ought to be. If it's an objective that Ekiga should be easy to setup, here are some remarks: Sound device selection. - There is no support for testing the output devices (Play test sound) for output nor ringing device in the device selection menu. I think it should. - On my Fedora box, some selections makes Ekiga really weird e. g., it's possible to connect but not to disconnect. The bad thing is that there is no user feedback indicating that this is a problem with the sound devices, which makes it hard to figure out what's going on. NAT traversal and router setup: - My router is a NAT router with the dreaded Symmetric NAT. There *is* an error message when Ekiga is started which basically says that I have to configure the router manually. The crucial term Symmetric NAT is *not* mentioned in this message. I finally learned to start ekiga with debug output, and grep for 'stun' to reveal this fact. This should really easier, the information about Symmetric NAT should be displayed to the user. - Once I understood that my router was doing Symmetric NAT I configured port forwarding according to the docs (dynamic, triggered ports is not properly handled by my Thomson router). I came to a point with working connect/disconnect but no sound. - After some more reading, I understood that the stunnel stuff was in the way. So I needed to disable stunnel. There are no switches in the UI for this, and even in gconf there is no Use stunnel option. What I did was to set the stunnel host to a non-existing value. This created a lot of error messages, and a working Ekiga... This should be easier and more straightforward IMHO. The issue to setup Ekiga with a router doing symmetric NAT couldn't really be out of the box, I understand that. But I still think this process could be easier with better error messages and configuration options. Or, maybe, a Symmetric NAT wizard? Last but not least, I shouldn't have taken the time to write this unless I really appreciate what you are doing... --Alec ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Newbie configuration experiences...
Alec Leamas wrote: First of all: I actually got Ekiga 3.0.1 running to the point of a working call to the echo service on my Fedora 10 box which is a Good Thing. You are doing a great job! However, being a newbie I found it a little harder than it ought to be. If it's an objective that Ekiga should be easy to setup, here are some remarks: Sound device selection. - There is no support for testing the output devices (Play test sound) for output nor ringing device in the device selection menu. I think it should. - On my Fedora box, some selections makes Ekiga really weird e. g., it's possible to connect but not to disconnect. The bad thing is that there is no user feedback indicating that this is a problem with the sound devices, which makes it hard to figure out what's going on. NAT traversal and router setup: - My router is a NAT router with the dreaded Symmetric NAT. There *is* an error message when Ekiga is started which basically says that I have to configure the router manually. The crucial term Symmetric NAT is *not* mentioned in this message. I finally learned to start ekiga with debug output, and grep for 'stun' to reveal this fact. This should really easier, the information about Symmetric NAT should be displayed to the user. - Once I understood that my router was doing Symmetric NAT I configured port forwarding according to the docs (dynamic, triggered ports is not properly handled by my Thomson router). I came to a point with working connect/disconnect but no sound. - After some more reading, I understood that the stunnel stuff was in the way. So I needed to disable stunnel. There are no switches in the UI for this, and even in gconf there is no Use stunnel option. What I did was to set the stunnel host to a non-existing value. This created a lot of error messages, and a working Ekiga... This should be easier and more straightforward IMHO. The issue to setup Ekiga with a router doing symmetric NAT couldn't really be out of the box, I understand that. But I still think this process could be easier with better error messages and configuration options. Or, maybe, a Symmetric NAT wizard? Last but not least, I shouldn't have taken the time to write this unless I really appreciate what you are doing... --Alec ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list I second that. One thing you may find, if you are using a Thomson ST 585 V6 router as I am, is that once you have disabled STUN then the ST 585 appears to automatically open the RTP ports for you. ie you don't need to manually set the router to port forward them, at least on my setup ... It seems to also forward them to the correct host (I have a number of systems behind the ST586). See my message No Echo Test response: STUN Problem with Thomson ST585 Cheers Terry ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Newbie configuration experiences...
Terry Barnaby wrote: [snip] Indeed... there is no need to enable port forwarding for the RTP ports for the ST585 router. Thanks! This is nice, but also creates a strange feeling about this router.. is there anything else it forwards without letting me know? I second that. One thing you may find, if you are using a Thomson ST 585 V6 router as I am, is that once you have disabled STUN then the ST 585 appears to automatically open the RTP ports for you. ie you don't need to manually set the router to port forward them, at least on my setup ... It seems to also forward them to the correct host (I have a number of systems behind the ST586). See my message No Echo Test response: STUN Problem with Thomson ST585 Cheers Terry ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Newbie configuration experiences...
Le samedi 20 décembre 2008 à 15:51 +0100, Alec Leamas a écrit : Terry Barnaby wrote: [snip] Indeed... there is no need to enable port forwarding for the RTP ports for the ST585 router. Thanks! This is nice, but also creates a strange feeling about this router.. is there anything else it forwards without letting me know? The behavior is normal. It is actually a perfect router. NAT is something bad, as it rewrites the packets. The problem with NAT is that some protocols (like SIP) require you to change the private IP address inside the SIP packet. A good NAT implementation should be able to do it for most common protocols. Most NAT implementations can deal with FTP transparently for you. Unfortunately, until recently, that was not the case with SIP and you needed workarounds like STUN or port forwarding. But recently, more and more routers started to have a NAT implementation that supports SIP. In that case, no port forwarding, no STUN are required. That is the perfect situation. Please note that it only forwards RTP ports because it knows that is a connection you established yourself. It is able to understand what happens. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list