This problem seems to have resolved itself . After setting up the Ekiga FAQ firewall the Druid (Damien ?) at first recognised it as symmetrical, needing NAT traversal, but now tells me "STUN test results: no NAT. You do not seem to be using a NAT router. STUN support is not required." Echo test for ekiga & pulver both work, but audio quality remains poor, analagous to the cookie muncher monster of Dr. Seuss - possibly due to libalsa using the classical , i.e. older, sample rate. One work-around may be to use alsa libraries & Ekiga from a mounted Ubuntu live CD Adam Bogacki, afb paradise net nz On Wed, Jul 05, 2006 at 09:43:03AM +0200 or thereabouts, Damien Sandras wrote: > Le mercredi 05 juillet 2006 ? 13:17 +1200, Adam Bogacki a ?crit : > > > .. but after enabling ONLY Capture for recording with GNOME ALSA > > > mixer, > > > aplay and gnome sound-recorder 2.14.2 worked after which > > > the Druid Audio Devices sound test also worked .. although calling > > > 'sip:500 ekiga net' and 'sip:613 fwd pulver com' terminated after 3-4 > > > beeps with "Abnormal call termination" ... hmm > > > > > > > NAT issue. What release of Ekiga? > > > > -- > > _ Damien Sandras > > > > Ekiga 2.0.2 > > > > I went through configuration druid completely this time (previously I > > was focusing on the audio devices page) and after the prompt 'Detect NAT > > Type' I received the message > > > ---------------> ----------------------------------------------------- > > "The detection of your NAT type is finished. > > > > STUN test result: Open NAT > > > > Your system does not need any specific configuration as long as you > > do not have a local firewall blocking the ports required by Ekiga". > ------------------> -------------------------------------------------- > > > > My firewall is configured to allow a local network running ltsp and I > > have been reluctant to tamper with it, although I have noticed your FAQ > > IPTABLES example. My version of IPTABLES might need some improvement but > > should not be the problem as I have previously had 2.0.1 and 2.0.2 running > > successfully with it. > > > > I have attached the output of > > > > ekiga -d 4 > ekiga_05072006.txt 2>&1 > > > > which includes the line > > > > "STUN could not create RTP/RTCP socket pair; trying to create > > RTP socket anyway." > > And then : > STUN could not create RTP socket either. > > So STUN doesn't work. Your policies might be too strict, or your router > blocks STUN. STUN works for registering though, so you might be limited > to a given number of bindings on the firewall. > > > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone: http://www.ekiga.org/ > v_/_ FOSDEM 2006 : http://www.fosdem.org/ > SIP Phone : sip:dsandras ekiga net > sip:600000 ekiga net > > ----- End forwarded message -----
Attachment:
signature.asc
Description: Digital signature