[Ekiga-list] problem compiling Ekiga 3.0.1 under Kubuntu 8.04.1 LTS
Hi!
Everything went fine but in the almost end compiling help gave error:
Making all in help
make[2]: Entering directory `/data/soft2/ekiga/ekiga_3-0-1/ekiga-3.0.1/help'
if ! test -d bg/; then mkdir bg/; fi
if [ -f "C/ekiga.xml" ]; then d="../"; else
d="/home/edmund/soft2/ekiga/ekiga_3-0-1/ekiga-3.0.1/help/"; fi; \
(cd bg/ && \
`which xml2po` -e -p \
"${d}bg/bg.po" \
"${d}C/ekiga.xml" > ekiga.xml.tmp && \
cp ekiga.xml.tmp ekiga.xml && rm -f ekiga.xml.tmp)
/bin/bash: line 2: -e: command not found
make[2]: *** [bg/ekiga.xml] Error 127
make[2]: Leaving directory `/data/soft2/ekiga/ekiga_3-0-1/ekiga-3.0.1/help'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/data/soft2/ekiga/ekiga_3-0-1/ekiga-3.0.1'
make: *** [all] Error 2
Is it problem, that /home/edmund/soft2/ is a symlink to /data/soft2/ ??
Could not find the file bg/ekiga.xml
I installed additional components:
flex bison pkg-config intltool libgtk2.0-bin libgtk2.0-dev libsigc++-2.0-dev libxml2-dev
libgnome2-dev libgnomeui-dev libebook1.2-dev libldap2-dev libxv-dev libdbus-glib-1-dev libsdl1.2-dev
xsltproc
Certainly, I compiled before and suggestions at https://help.ubuntu.com/community/CompilingSoftware
are clear.
Also I followed instructions at http://wiki.ekiga.org/index.php/Linux_Users
All other components compiled and installed fine. It seems like /'m quite close to get all
components compiled but such a error occured.
Thank you in Advance for helping,
Edmund Laugasson
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Logitech Quickam Pro 9000 and ekiga
Hello, I have a Logitech Quickcam Pro 9000, work fine in skype and other programs under linux, but don't work with ekiga. Logitech pro 9000 uses uvc driver and uvc only uses V4L2 API, however, ekiga try to use V4L1 with my logitech webcam. how can I say to ekiga that it uses V4L2 with my webcam? claudio ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Re (2): failure in registration of sip account
Eugen and others, > Please try ekiga 3 if possible, it is available on debian experimental. Right oh; thanks. Now I should retreat to lists.debian.org but the discussion started here and this is the consequence. The ekiga here is 2.0.12 and Debian is lying to me. dalton:/etc/apt# apt-get -t experimental install ekiga Reading package lists... Done Building dependency tree Reading state information... Done ekiga is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. dalton:/etc/apt# According to http://www.debian.org/doc/manuals/apt-howto/ch-apt-get.en.html "3.8 How to keep a mixed system", this line is in /etc/apt/sources.list. deb-src http://linux.csua.berkeley.edu/debian/ experimental main non-free contrib Seems that I am not using apt properly or upgrade of ekiga is blocked by a dependency. Thanks for any ideas, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Thank you
On Sat, Dec 20, 2008 at 8:55 AM, Bill Collins wrote: > Darren, > Would be nice if you detailed your install steps for the timid ones. > BC > I used the following PPA: https://launchpad.net/~tlbdk/+archive The page above will have the proper entries for your sources.list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] \"remote user cleared the call\" problem
> > A fix has been put into the stable branch and into TRUNK. Is that > > something you can test ? > Tried to test snapshot from 18th and 19th but none of them compiled. The (first) error message was: ../../../../lib/engine/components/opal/sip-endpoint.cpp: In member function `virtual void Opal::Sip::EndPoint::fetch(std::string)\': ../../../../lib/engine/components/opal/sip-endpoint.cpp:313: error: `Dialog\' is not a member of `SIPSubscribe\' Can you please let me know which code can I use for testing. Palo > Sounds good! I should be able to test it within a few days. > Of course I\\\'ll post the results here as soon as I have them. > > Palo > > > -- > > _ 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 > > > __ > http://kultura.sme.sk/ - Informačný server o kultúre a šoubiznise > > > ___ > ekiga-list mailing list > ekiga-list@gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > __ http://zabava.sme.sk/ - Stránka čo usmeje ti tvár ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] output of "ekiga -d 4 > output.txt 2>&1" for failed call attempt
Damien Sandras wrote: Le samedi 20 décembre 2008 à 10:28 -0500, Andre Robatino a écrit : Damien Sandras wrote: Le jeudi 18 décembre 2008 à 14:50 -0500, Andre Robatino a écrit : Attached is output.txt when my father attempts to call me. We are both using Fedora 10 with ekiga-3.0.1-4.fc10 from the Fedora repo. We have identical PCs, USB headsets, and webcams. He has a symmetric NAT router, and I have a port restricted NAT router. The call drops after a few seconds without audio or video ever being established. Each of us can make normal echo test calls. With Symmetric NAT, it can not work. You really need to do something so that it is not a Symmetric NAT. Perhaps port forwarding or something else. Are you also 100% sure your router does not support SIP ? His router is a Motorola 2210-02-1006 which is what AT&T is providing now for new DSL customers. With Ekiga 2.0.12, it was initially detected as a symmetric NAT router, and he could call me, but I couldn't reach him. After putting in the port triggering rule, it was detected as a port restricted NAT router, and we could connect in both directions. Now, with Ekiga 3, we can't communicate in either direction (except for a brief connection without audio or video when he calls me). Nothing has changed except for Fedora 9 -> 10 and Ekiga 2 -> 3. The reason is the symmetric NAT. However, I do not understand why the NAT did not appear as symmetric with Ekiga 2.00. The STUN code did not really change between 2.00 and 3.00 :( It DID initially appear as symmetric NAT with Ekiga 2 (according to Ekiga 2's Configuration Druid). Then, after setting up port triggering in the router according to http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#Symmetric_NAT:_Dynamic_navigation_of_NAT_routers the Configuration Druid saw it as a port restricted NAT router. This is exactly the behavior described at http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#SIP_only so the behavior with Ekiga 2 is as expected, it's the behavior with Ekiga 3 that is confusing. smime.p7s Description: S/MIME Cryptographic Signature ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router
Le samedi 20 décembre 2008 à 19:24 +0100, Alec Leamas a écrit : > Damien Sandras wrote: > [snip] > > You could report a bug concerning the impossibility to "try" sound > > events. > > Done, http://bugzilla.gnome.org/show_bug.cgi?id=565196 Thanks! -- _ 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
Re: [Ekiga-list] output of "ekiga -d 4 > output.txt 2>&1" for failed call attempt
Le samedi 20 décembre 2008 à 10:28 -0500, Andre Robatino a écrit : > Damien Sandras wrote: > > Le jeudi 18 décembre 2008 à 14:50 -0500, Andre Robatino a écrit : > >> Attached is output.txt when my father attempts to call me. We are both > >> using Fedora 10 with ekiga-3.0.1-4.fc10 from the Fedora repo. We have > >> identical PCs, USB headsets, and webcams. He has a symmetric NAT > >> router, and I have a port restricted NAT router. The call drops after a > >> few seconds without audio or video ever being established. Each of us > >> can make normal echo test calls. > > > > > > With Symmetric NAT, it can not work. You really need to do something so > > that it is not a Symmetric NAT. Perhaps port forwarding or something > > else. > > > > Are you also 100% sure your router does not support SIP ? > > His router is a Motorola 2210-02-1006 which is what AT&T is providing > now for new DSL customers. With Ekiga 2.0.12, it was initially detected > as a symmetric NAT router, and he could call me, but I couldn't reach > him. After putting in the port triggering rule, it was detected as a > port restricted NAT router, and we could connect in both directions. > Now, with Ekiga 3, we can't communicate in either direction (except for > a brief connection without audio or video when he calls me). Nothing > has changed except for Fedora 9 -> 10 and Ekiga 2 -> 3. The reason is the symmetric NAT. However, I do not understand why the NAT did not appear as symmetric with Ekiga 2.00. The STUN code did not really change between 2.00 and 3.00 :( -- _ 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
Re: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router
Damien Sandras wrote: [snip] You could report a bug concerning the impossibility to "try" sound events. Done, http://bugzilla.gnome.org/show_bug.cgi?id=565196 --alec ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router
Damien Sandras wrote: Le samedi 20 décembre 2008 à 16:25 +0100, Alec Leamas a écrit : Damien Sandras wrote: Le vendredi 19 décembre 2008 à 22:54 +, Terry Barnaby a écrit : Hi, [snip] It appears that the ST585 is doing something special when it sees SIP protocol requests and forwarding the ports automatically, but the use of the STUN system messes this up. If this is the case, It would be useful to be able to disable STUN support in the standard user preferences dialogs of the Ekiga app and to note this in the error dialog window. Also I guess it may be possible to fix the STUN support if there is an issue here ... It is one of the things I want to work on for 3.20 : detect if STUN is required or if the router supports SIP. OK, this would resolve most issues mentioned in my first post labeled "Newbie configuration experience". In the short run, updating the docs with how to disable stunnel support would make sense. Also, please note my remarks about the sound device selection (I know, the post is long, sorry...) You could report a bug concerning the impossibility to "try" sound events. I am about to try and get a Windows Version (3.0.2) of Ekiga working for my mother in laws computer. I suspect that her router will also support SIP as it is relatively new. How can I disable the STUN support in Ekiga in Microsoft Windows so that Ekiga will work with a router that implements automatic SIP port forwarding ? Cheers Terry ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router
Le samedi 20 décembre 2008 à 16:25 +0100, Alec Leamas a écrit : > Damien Sandras wrote: > > Le vendredi 19 décembre 2008 à 22:54 +, Terry Barnaby a écrit : > > > >> Hi, > >> [snip] > >> > >> It appears that the ST585 is doing something special when it sees SIP > >> protocol > >> requests and forwarding the ports automatically, but the use of the STUN > >> system > >> messes this up. > >> > >> If this is the case, It would be useful to be able to disable STUN support > >> in > >> the standard user preferences dialogs of the Ekiga app and to note this in > >> the > >> error dialog window. Also I guess it may be possible to fix the STUN > >> support if > >> there is an issue here ... > >> > > > > It is one of the things I want to work on for 3.20 : detect if STUN is > > required or if the router supports SIP. > > > OK, this would resolve most issues mentioned in my first post labeled > "Newbie configuration experience". In the short run, updating the docs > with how to disable stunnel support would make sense. Also, please note > my remarks about the sound device selection (I know, the post is long, > sorry...) You could report a bug concerning the impossibility to "try" sound events. -- _ 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
Re: [Ekiga-list] Ekiga cannot register with ekiga.net - Asterisk can
Hi, Le dimanche 14 décembre 2008 à 20:21 +0100, Bent a écrit : > Hi > > I have been unsubscribed to this list for a while so some > advertisements may have posted regarding my problem. There is, > however, not anything like it in the archives as far as I have been > able to determine. > > Anyway, my problem is stated in the subject line. Here are some details: > > Asterisk runs on my gateway/firewall. My ekiga softphone (which is > 2.0.12 - the latest issued by Gentoo) runs on a workstation behind the > firewall. I use no proxy, but the firewall (another box running Gentoo > Linux) has the SIP ALG enabled. > > Asterisk registers fine with ekiga.net: > > b...@yosie ~ $ tshark -r ekiga-asterisk.trace > Running as user "bent" and group "users". > 1 0.00 86.48.49.19 -> 86.64.162.35 SIP Request: OPTIONS sip:ekiga.net > 2 0.024013 86.64.162.35 -> 86.48.49.19 SIP Status: 484 Address Incomplete The Address Incomplete thing has just been fixed. It was a bug in the Kamailio configuration. > 3 0.093378 86.48.49.19 -> 86.64.162.35 SIP Request: REGISTER > sip:ekiga.net > 4 0.116927 86.64.162.35 -> 86.48.49.19 SIP Status: 401 > Unauthorized(0 bindings) > 5 0.117983 86.48.49.19 -> 86.64.162.35 SIP Request: REGISTER > sip:ekiga.net > 6 0.142500 86.64.162.35 -> 86.48.49.19 SIP Status: 200 OK(1 bindings) > b...@yosie ~ $ > > whereas Ekiga the softphone doesn't: > > b...@yosie ~ $ tshark -r ekiga.trace > Running as user "bent" and group "users". > 1 0.00 86.48.49.19 -> 86.64.162.35 SIP Request: REGISTER > sip:ekiga.net > 2 0.009675 86.48.49.19 -> 86.64.162.35 SIP Request: SUBSCRIBE > sip:be...@ekiga.net > 3 0.023790 86.64.162.35 -> 86.48.49.19 SIP Status: 606 Not > Acceptable(0 bindings) > 4 0.033924 86.64.162.35 -> 86.48.49.19 SIP Status: 202 OK > b...@yosie ~ $ Apparently, you are trying to register a private IP. Perhaps you have STUN enabled and the gateway replaces the public IP it sees by a private IP ? > Several questions arise: > > 1. Why do I get '484 Address Incomplete' when my Asterisk asks for options? > > 2. Why does my Ekiga get a '606 Not Acceptable' when it tries to register? See above. > 3. Why is the subscribe accepted '202 OK'? It is how it should be ;-) -- _ 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
Re: [Ekiga-list] output of "ekiga -d 4 > output.txt 2>&1" for failed call attempt
Damien Sandras wrote: Le jeudi 18 décembre 2008 à 14:50 -0500, Andre Robatino a écrit : Attached is output.txt when my father attempts to call me. We are both using Fedora 10 with ekiga-3.0.1-4.fc10 from the Fedora repo. We have identical PCs, USB headsets, and webcams. He has a symmetric NAT router, and I have a port restricted NAT router. The call drops after a few seconds without audio or video ever being established. Each of us can make normal echo test calls. With Symmetric NAT, it can not work. You really need to do something so that it is not a Symmetric NAT. Perhaps port forwarding or something else. Are you also 100% sure your router does not support SIP ? His router is a Motorola 2210-02-1006 which is what AT&T is providing now for new DSL customers. With Ekiga 2.0.12, it was initially detected as a symmetric NAT router, and he could call me, but I couldn't reach him. After putting in the port triggering rule, it was detected as a port restricted NAT router, and we could connect in both directions. Now, with Ekiga 3, we can't communicate in either direction (except for a brief connection without audio or video when he calls me). Nothing has changed except for Fedora 9 -> 10 and Ekiga 2 -> 3. smime.p7s Description: S/MIME Cryptographic Signature ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router
Damien Sandras wrote: Le vendredi 19 décembre 2008 à 22:54 +, Terry Barnaby a écrit : Hi, [snip] It appears that the ST585 is doing something special when it sees SIP protocol requests and forwarding the ports automatically, but the use of the STUN system messes this up. If this is the case, It would be useful to be able to disable STUN support in the standard user preferences dialogs of the Ekiga app and to note this in the error dialog window. Also I guess it may be possible to fix the STUN support if there is an issue here ... It is one of the things I want to work on for 3.20 : detect if STUN is required or if the router supports SIP. OK, this would resolve most issues mentioned in my first post labeled "Newbie configuration experience". In the short run, updating the docs with how to disable stunnel support would make sense. Also, please note my remarks about the sound device selection (I know, the post is long, sorry...) --alec ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] output of "ekiga -d 4 > output.txt 2>&1" for failed call attempt
Le jeudi 18 décembre 2008 à 14:50 -0500, Andre Robatino a écrit : > Attached is output.txt when my father attempts to call me. We are both > using Fedora 10 with ekiga-3.0.1-4.fc10 from the Fedora repo. We have > identical PCs, USB headsets, and webcams. He has a symmetric NAT > router, and I have a port restricted NAT router. The call drops after a > few seconds without audio or video ever being established. Each of us > can make normal echo test calls. With Symmetric NAT, it can not work. You really need to do something so that it is not a Symmetric NAT. Perhaps port forwarding or something else. Are you also 100% sure your router does not support SIP ? _ 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
Re: [Ekiga-list] LDAP Support in Ekiga Windows Version 3.0.0
Le jeudi 18 décembre 2008 à 11:55 +0530, Archna Mittal a écrit : > > Hi All, >I am new to Ekiga and installed windows version 3.0.0 on my > machine. > > I want to integrate Microsoft LDAP server with Ekiga. Is it feasible? > > If yes, please let me know how? I have entered the server address and > other parameters after asking to my admin. But it is not working, it > is not retrieving any value from the address book.Is there anything > else I should do to enable this. It should work. However, 3.20 will have a far better LDAP implementation. -- _ 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
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
Re: [Ekiga-list] Thank you
Le vendredi 19 décembre 2008 à 23:12 -0500, Darren Albers a écrit : > I have been following the list for awhile and just now got around to > trying Ekiga 3.x and I am VERY impressed. The UI is nice and easy to > use, the setup was a breeze and everything just worked! > > Thank you to everyone who has put the time and effort into making this > great application! Thank you for the compliment :-) -- _ 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
Re: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router
Le vendredi 19 décembre 2008 à 22:54 +, Terry Barnaby a écrit : > Hi, > > I have been trying to get Ekiga working on a Fedora 8 based system. > I am using Ekiga 3.0.1 build from a Fedora 10 source RPM. > This is being used at home through a ST585 router in NAT configuration. > > When ever I tried to run Ekiga I would get the error message in a dialog > window: > > "Ekiga did not manage to configure your network settings automatically. You > can > still use it, but you need to configure your network settings manually. > Please see http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually for > instructions" > > After this the echo test would fail in the receiving direction. I tried to > enable port forwarding on my ST585 router to no avail. > > Strangely it was working at work were we use the same ST585 router, but > without > NAT enabled (A Linux box does the firewall). > > After a lot of playing around I used gconf-editor to clear the "stun_server" > entry for Ekiga. This cured the problem. > What is strange is that Ekiga now also works without the port forwarding > enabled in the router ... > > It appears that the ST585 is doing something special when it sees SIP protocol > requests and forwarding the ports automatically, but the use of the STUN > system > messes this up. > > If this is the case, It would be useful to be able to disable STUN support in > the standard user preferences dialogs of the Ekiga app and to note this in the > error dialog window. Also I guess it may be possible to fix the STUN support > if > there is an issue here ... It is one of the things I want to work on for 3.20 : detect if STUN is required or if the router supports SIP. -- _ 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
Re: [Ekiga-list] Need info regarding Ekiga Teleconferencing
Le jeudi 18 décembre 2008 à 16:23 +0100, Mansoor Hyder a écrit : > Hi, > Would anyone guide me weather Ekiga supports Teleconferencing. I mean > if there are 6 people at 6 different locations (or any number of > poeple more than 2)of the world and want to have conversation would it > be possible for them using Ekiga? > I am student and would like to work enhancing Ekiga having 3D sound > support. Ekiga requires an external server to do that. -- _ 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
Re: [Ekiga-list] could not register : behind a router
Le jeudi 18 décembre 2008 à 15:43 +0300, Fedor vonBock a écrit : > How do i disable it? > If it is enabled, it is in the Network Settings page. -- _ 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
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...
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] Thank you
Darren, Would be nice if you detailed your install steps for the timid ones. BC On Fri, Dec 19, 2008 at 11:12 PM, Darren Albers wrote: > I have been following the list for awhile and just now got around to > trying Ekiga 3.x and I am VERY impressed. The UI is nice and easy to > use, the setup was a breeze and everything just worked! > > Thank you to everyone who has put the time and effort into making this > great application! > ___ > 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
[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
